A
Android Central Question
I was 'experimenting' with my rooted LG G3 running android 4.4.2 and I accidentally managed to make my Bluetooth a ‘system app’ (and hence unusable, greyed out) while using 'ROM Toolbox' App.
I then converted it back to a user app using Titanium Backup Pro, but it still remained greyed out. I then tried using ADB to turn it back on using the following from another post;
adb shell service call bluetooth_manager 6' (I've tried a few numeric variables but none seem to work),
then I tried;
‘adb shell’
‘su’
‘am start -a android.bluetooth.adapter.action.REQUEST_ENABLE’
That didn't work either as I got this error 'app_process has text relocations, this is wasting memory' etc......I think this is because I have Xposed Framework installed also.
Next I tried sQlite,
‘sQlite3 settings.db’
‘update global set value=1 where name='bluetooth_on';’
Then I got the error..... ‘no such table: global’
I'm not a developer but I do enjoy messing around with these things, until it all goes wrong of course......I know I could un-root and see what happens, but I'd rather try and figure this out rather than go through the hassle of un-rooting & rooting again...Anyone have any ideas how to turn my Bluetooth back on, (preferably with an ADB Command)? Thanks......
I then converted it back to a user app using Titanium Backup Pro, but it still remained greyed out. I then tried using ADB to turn it back on using the following from another post;
adb shell service call bluetooth_manager 6' (I've tried a few numeric variables but none seem to work),
then I tried;
‘adb shell’
‘su’
‘am start -a android.bluetooth.adapter.action.REQUEST_ENABLE’
That didn't work either as I got this error 'app_process has text relocations, this is wasting memory' etc......I think this is because I have Xposed Framework installed also.
Next I tried sQlite,
‘sQlite3 settings.db’
‘update global set value=1 where name='bluetooth_on';’
Then I got the error..... ‘no such table: global’
I'm not a developer but I do enjoy messing around with these things, until it all goes wrong of course......I know I could un-root and see what happens, but I'd rather try and figure this out rather than go through the hassle of un-rooting & rooting again...Anyone have any ideas how to turn my Bluetooth back on, (preferably with an ADB Command)? Thanks......