Not for the faint of heart!
I'm not responsible for damage to your device as this requires root to work.
1)you have to remove htcresetnotifer.apk and htcresetnotifer.odex from system/app/ - this will allow you to edit system without the phone resetting itself
2)open system/customize/ACC/default.XML in a file editor
3)You need to find "<app name="Tethering_provision"> <item type="integer" name="TetheringGuard_Rule">1</item> </app>" its near the bottom
4) change the "1" to a "0" and save
5) I used sense toolbox to soft reset. Don't do a full reboot or setting will go back as we don't have s-off yet
Be advised this is a hack. Bugs may exist. I do know that if you turn off the hotspot another soft reboot will be necessary as the hotspot hangs when trying to turn it back on.
Sent from my Nexus 7 using Tapatalk
I assume you would need s-off for this to stick?
Sent from my HTC M8, Verizon style.
Yah, how does this work if system is still write protected?
Sent from my HTC6525LVW using Tapatalk
Yes but to make it easier I've just uploaded an XML to drive that also has a fix for the bug that made the hotspot hang when restarting.
https://docs.google.com/file/d/0BwzzxOrAR3FvaTdDMUsxeG5MY28/edit?usp=docslist_api
You can move to and overwrite system/customize/ACC/default.xml
Just make sure you remove the previous apps and then soft reboot
Sent from my Nexus 7 using Tapatalk
So you can make changes to system but normally a hard reboot will revert those changes. The htcresetnotifier is supposed to hard reboot the phone when a change to system is discovered hence why its the first thing we remove then we can edit system. The soft reboot allows the services to restart without reverting the changes. Same as in the way we can get xposed to work without full system rw. This will work as perm solution as soon as s-off is achieved.
Sent from my Nexus 7 using Tapatalk
murryrulz said:
So you can make changes to system but normally a hard reboot will revert those changes. The htcresetnotifier is supposed to hard reboot the phone when a change to system is discovered hence why its the first thing we remove then we can edit system. The soft reboot allows the services to restart without reverting the changes. Same as in the way we can get xposed to work without full system rw. This will work as perm solution as soon as s-off is achieved.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
What about using
Code:
pm disable com.htc.resetnotify
The disable stays even through a hard reboot.
Haven't tried but you will still have to modify the xml after reboot
Sent from my HTC6525LVW using Tapatalk
murryrulz said:
Haven't tried but you will still have to modify the xml after reboot
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Right, disabling the reset apk will only eliminate the reboots when you edit a system file.
Just confirmed that you can disable the resetnotify apk, restart, and it will stay gone. You can modify system .xml files without having the phone restart on you. You will still need to do a soft reboot to enable the changes. A hard reboot will wipe out the changes but the resetnotify apk will stay disabled. One could get clever and use tasker or another automation service to automate the process of copying the modified xml file. Looks like this could be done with an xposed module as well.
working
First post here. Wanted to confirm that this working. I used the pm disable notify code. I did have to reenable the the tethering guard I had disabled beforehand. I also downloaded the xml doc provided. For soft reboot I used the feature provided in the xposed framework. Not the sense toolbox.
Yea I'm pretty sure an xposed module can do it too. Just not sure how to code that. Not 100% sure how those hooks work.
Sent from my Nexus 7 using Tapatalk
Working great here too! Just curious, what is different in the file u posted to fix the "bug that made the hotspot hang when restarting?" And can you elaborate on what the bug was?
Sent from my HTC6525LVW using Tapatalk
I would also like to know what the changes are in the .XML that keeps the hotspot from "hanging on restart" I have made other changes to my .XML and do not want to replace the entire file.
gberryhill said:
I would also like to know what the changes are in the .XML that keeps the hotspot from "hanging on restart" I have made other changes to my .XML and do not want to replace the entire file.
Click to expand...
Click to collapse
in the same default.xml posted in the OP do that edit AND
Code:
<item type="boolean" name="tethering_guard_support">[B][COLOR="Red"]true[/COLOR][/B]</item>
TO
Code:
<item type="boolean" name="tethering_guard_support">[B][COLOR="Red"]false[/COLOR][/B]</item>
andybones said:
in the same default.xml posted in the OP do that edit AND
Code:
<item type="boolean" name="tethering_guard_support">[B][COLOR="Red"]true[/COLOR][/B]</item>
TO
Code:
<item type="boolean" name="tethering_guard_support">[B][COLOR="Red"]false[/COLOR][/B]</item>
Click to expand...
Click to collapse
Thanks to murryrulz for the op and andybones for this. Works great!
Thanks for this. Works perfectly.
Sent from my HTC6525LVW using Tapatalk
i edit the file to enable languages but when i restart the phone all setting same as before
can you give me the link which tool you use for soft rest
Does this still work on Lollipop?
hippopo said:
Does this still work on Lollipop?
Click to expand...
Click to collapse
Yes.. i have a flashable for it in my RUU thread as well that enables this and couple things.
Thanks for the tethering guard = false tip. I was having that hanging issue on 4.17.605.9
Related
Anyway to get the notification leds/button lights to flash when a text received on 2.3.3 like it does on cm7?
EDIT: found this, works perfectly.
phburks said:
There is an app in the Market called LG 2X/Black/3D Notifications that works with the G2X. It worked without root with 2.2 but apparently it requires root with 2.3.3 due to some changes LG made to the phone.
Click to expand...
Click to collapse
Anyway to have this app manually grant permission? I am rooted with stock 2.3.3 and it was working before for me but its not granting su permission
Sent from my LG-P999 using Tapatalk
Does your battery drain after you installed this app?
saotua said:
Does your battery drain after you installed this app?
Click to expand...
Click to collapse
Yessss
Thanks. i thought it just my phone.
Hi, I'm new here and I this is my first droid, so i need some help. I have done an extensive search and looks like I'm the only one with this problem.
I've rooted my g2x (2.3.3), etc, installed the notification led, change permissions to rw-rw-rw (sys/devices/plataform/star_touch_led/wled), so far so good. But when I reboot (turn off/turn on) the phone my permissions get back to rw-rw-r. So every time I turn on the phone I have to change it manually.
What am I doing wrong? Am I missing something? Phone problem?
one4one said:
Hi, I'm new here and I this is my first droid, so i need some help. I have done an extensive search and looks like I'm the only one with this problem.
I've rooted my g2x (2.3.3), etc, installed the notification led, change permissions to rw-rw-rw (sys/devices/plataform/star_touch_led/wled), so far so good. But when I reboot (turn off/turn on) the phone my permissions get back to rw-rw-r. So every time I turn on the phone I have to change it manually.
What am I doing wrong? Am I missing something? Phone problem?
Click to expand...
Click to collapse
Well for one, when you install the app there's no need to change its permission like that. Maybe that's why it switches back after a reboot..
Sent from my LG-P999 using Tapatalk
noodles2224 said:
Well for one, when you install the app there's no need to change its permission like that. Maybe that's why it switches back after a reboot..
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
That's on Froyo.
On gingerbread, this app doesn't work that way. If I dont change the permissions it will never work. It's like when I turnoff/turn on the phone the permissions get back to "factory data reset".
Anyone with the same problem?
---
Well, finally it's solved. Dunno how, but the permissions doesn't' change anymore. Thank anyway.
noodles2224 said:
Anyway to have this app manually grant permission? I am rooted with stock 2.3.3 and it was working before for me but its not granting su permission
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Do you have the latest version from the Market. It detects whether or not the file is readable and asks you if it can make changes, and then gets superuser permissions. It must set the file settings every time the phone boots. If you do have the latest version try going into the program interface itself and see if there are options for this. If you cannot find them, simply uninstall the program (delete its data first) and then reinstall it. The first time you run it the program should go through whatever it needs to do to get su permissions, etc. You must be rooted on GB for this app to work.
I am rooted, I know how to use that apparently but fir some reason it doesn't detect anymore. But I got a modified version from the Dev and it skips the detection part. The dev said he figured out why it was doing it. Might be an update or something ..
Sent from my LG-P999 using Tapatalk
Is there an app or mod that will make the notification light blink for more than 5 min? Or does installing a rom fix that?
KoolKidd_23 said:
Is there an app or mod that will make the notification light blink for more than 5 min? Or does installing a rom fix that?
Click to expand...
Click to collapse
I have edited the /system/customize/ACC/default.xml file before to disable the 5 minute timeout. I believe you change the value of NMS_feature_led_flash_timeout from 5 to 0. Try it and let us know how it works.
Ok thanks, it won't let me do it right now and I'm sure it's because I'm not rooted yet. I'll root and let you know
shortstuff_mt said:
I have edited the /system/customize/ACC/default.xml file before to disable the 5 minute timeout. I believe you change the value of NMS_feature_led_flash_timeout from 5 to 0. Try it and let us know how it works.
Click to expand...
Click to collapse
Ok thanks, it won't let me do it right now and I'm sure it's because I'm not rooted yet. I'll root and let you know
shortstuff_mt said:
I have edited the /system/customize/ACC/default.xml file before to disable the 5 minute timeout. I believe you change the value of NMS_feature_led_flash_timeout from 5 to 0. Try it and let us know how it works.
Click to expand...
Click to collapse
I've been looking for the answer to this since I bought this phone. Shortly after it was released. Asked and searched but never got or found an answer. Tried this and it worked. Thanks a bunch. :good:
robocuff said:
I've been looking for the answer to this since I bought this phone. Shortly after it was released. Asked and searched but never got or found an answer. Tried this and it worked. Thanks a bunch. :good:
Click to expand...
Click to collapse
Which file manager did you use? I'm trying to do it but I'm either getting an error or permission denied
KoolKidd_23 said:
Which file manager did you use? I'm trying to do it but I'm either getting an error or permission denied
Click to expand...
Click to collapse
Root Explorer. Have to set it to R/W before doing the edit. It may be that the system is mounted as read only in the app you're using. You may have to change it in the settings of the app you're using. In Root Explorer, there's a small button. Upper right side of the screen while viewing the folders. If the system is mounted R/O, it'll say "mount R/W". Press on it and then do the edit.
You do have to be rooted for it to work though.
robocuff said:
Root Explorer. Have to set it to R/W before doing the edit. It may be that the system is mounted as read only in the app you're using. You may have to change it in the settings of the app you're using. In Root Explorer, there's a small button. Upper right side of the screen while viewing the folders. If the system is mounted R/O, it'll say "mount R/W". Press on it and then do the edit.
You do have to be rooted for it to work though.
Click to expand...
Click to collapse
Ok I just did it and it made a back up xml file, just delete the original and it should work I assume?
No need to delete anything. You can delete the backup if you want though. It's up to you.
robocuff said:
No need to delete anything. You can delete the backup if you want though. It's up to you.
Click to expand...
Click to collapse
Still not working for me, I changed it to 0 then my phone reboots and when I go back to root explorer it still says 5
Edit: Nvm I got it, thanks
Are you rooted? If so, check your superuser app to see if Root Explorer has root permissions. Also, if it's still set to 5 when you reboot, is the backup file there or not? If not, it sounds like a root problem of some sort to me.
It should look like this before I edit correct? And yea I'm rooted
Sent from my HTC6525LVW using XDA Free mobile app
KoolKidd_23 said:
It should look like this before I edit correct? And yea I'm rooted
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
Yes
I can't get it to work either. Change stuck even after reboot ?
Yes. But, you need to click on that button that says mount r/w before you do the edit. If you do that and it still doesn't work, something isn't right with your root.
Are you permanently rooted or are you using weak sauce for root? If the latter, the changes won't stick if you do a normal reboot. Rebooting is necessary for the setting to take effect. With weak sauce, you have to do a hot reboot for things to stick. Things will only stick if you do a hot reboot. A normal reboot will result in your change or changes reverting back to the original meaning you'll have to do it over again. It'll work as long as you only hot reboot. If you're using weak sauce for root, you really should consider getting permanently rooted.
This worked, thanks!
Ahhhh ok makes sense. Yea I'm only weak sauce rooted so I'll get it permanently rooted then
Sent from my HTC6525LVW using XDA Free mobile app
I'm pretty sure I have it mounted correctly but I can't edit the file. What am I doing wrong. I'm using root Explorer and it's mounted r/w
dmrnhs said:
I'm pretty sure I have it mounted correctly but I can't edit the file. What am I doing wrong. I'm using root Explorer and it's mounted r/w
Click to expand...
Click to collapse
You need system read write as far as I know. Weak sauce root won't suffice.
Sent from my HTC6525LVW using Tapatalk
I have that. I'm running CleanRom. Do we have to enable certain permissions? I've followed all these steps. I not new to rooting and tweaks like this but then again I'm no expert
Hi I was messing around with my phone and I deleted the Carrier IQ files but upon reboot it immediatly gives me a Android System has stopped working. I need the files since i've tried decompiling tot file with no luck. :/
Here are the files I need if anyone would be so kind to upload. Thanks.
system/app/LADDM.apk
system/lib/libiq_client.so
system/lib/libiq_service.so
Here you go!
Glad to help out! Let me know if you need anything else!
Hyperrunner said:
Hi I was messing around with my phone and I deleted the Carrier IQ files but upon reboot it immediatly gives me a Android System has stopped working. I need the files since i've tried decompiling tot file with no luck. :/
Here are the files I need if anyone would be so kind to upload. Thanks.
system/app/LADDM.apk
system/lib/libiq_client.so
system/lib/libiq_service.so
Click to expand...
Click to collapse
Gotta get rid of the system calls for the files before removing them and rebooting
Sent from my LG-D850 using Tapatalk 2
screwyluie said:
Gotta get rid of the system calls for the files before removing them and rebooting
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
I removed the files first then removed them from android tuner. Maybe that was my mistake :/ ..
Hyperrunner said:
I removed the files first then removed them from android tuner. Maybe that was my mistake :/ ..
Click to expand...
Click to collapse
or perhaps you missed one? could've been anything really, but the removal of CIQ shouldn't cause any problem on your system if done correctly.
also, always backup system files, even if it seems like you'd never need them back, like in this case
If you do it correctly there are no issues. I removed mine a while ago and my phone is just fine.
This is what I would do:
Deactivate carrier iq processes with android tuner, freeze LADDM with titanium and do a reboot.
Remove lib files along with LADDM.apk and do a final reboot.
So I found this many many months ago on 950U root and Xposed not being completely compatible with our s8,Like in previous Xposed versions Wanam and such have modified Xposed To properly work on Galaxy devices... Btw Thank you Wanam and Rovo for All the hard work. :good::good::good:
So What it comes down to is this is not a @partcyborg Rom issue.....
It is even talked about Here on github on Xposed
https://github.com/rovo89/Xposed/issues/294
Now there are files here for a possible fix But please be-aware that I have tried them out right many times today in different combinations today and from total FC to no boot To now Bluetooth just not turning on after reboots I have bricked every which way with these modified as they are as now.....
Some have had reports of fixing this issue Which is very similar to previous Samsung Models and root and forgetting WiFi upon each reboot if some of you remember correctly....
But Either way I figured I would toss this up for all to check out to put our heads together to get something possibly going....:good::good::good::good:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
bradical711 said:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
I did to I got as far as good reboots but Bluetooth wouldn't turn on. I ended up doing a stock system img with root. Unbloated and no xposed Bluetooth works great now. Since no xposed
Working Solution
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Followed your steps and worked like a charm on s8+. Thanks!
Tried @nationalicon 's method and it worked flawlessly on Cyborg's (BQL1) ROM. I was a bit skeptical to try it on my s8 since when I had tried it the first time this didn't work but I hadn't tried this method. But after following these steps perfectly, everything works flawlessly. One less issue now with my ROM overall and it's even better than before. WiFi and Bluetooth connections were all lost at first but after repairing with them all and rebooting, everything is still connected now and works. Thank you!
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
Thats weird I havnt had really any drop offs unrooted stock,Part cyborg rom,Or pure stock rooted.
Just paring loss upon reboots...
I actually commend Samsung for the most part.
My Bluetooth has been quite exceptional.
Maybe something is interfering and cutting yours out
I run several speakers 2 gear s2 watches My car and prob a few other items,Was actually looking into pairing my PS Vita with it and see what it will do
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Smithfolk4 said:
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Click to expand...
Click to collapse
That is the problem. It drops sync. When restarting. Also dropping for no reason. This is after playing all day. Both phone and Bluetooth device are right next to each. And not just on Bluetooth device and/or s8. It happens on one that has never been rooted. Only factory OTA updates.
https://www.google.com/amp/s/forum....lp/bluetooth-issues-oreo-update-t3765757/amp/
It is an issue.
Works thanks
jj972 said:
Followed your steps and worked like a charm on s8+. Thanks!
Click to expand...
Click to collapse
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Just wanted to confirm it does work follow steps. Only had to clear cache. I left the xposed installer installed and had no mods installes. Copy pasted the correct files files, edited the prop restarted into recovery. Then deleted only cache. Restarted paired with speaker then restarted one more time to test and boom.
Thanks for the help
dmosley said:
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Click to expand...
Click to collapse
Not sure, but I don't think there is any harm in trying. You can always delete the files later.
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
we87 said:
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
Click to expand...
Click to collapse
Thats what I did
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
This worked for me. I didn't uninstall xposed. I just disabled all my mods. from xposed and followed the instructions.
Can confirm, worked for me as well. Even survived a factory reset.
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
matthewd769 said:
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
Click to expand...
Click to collapse
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
bradical711 said:
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
Click to expand...
Click to collapse
thanks for the reply .... VERY helpful. I did find it.
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Thank you! This saved me from several hours of tweaking this stupid samsung security.
Thank you @Chamelleon! I was about to get in to a full reflash stock, reroot, reinstall situation. Damn, I love xda!
BTW, the thing I did differently was to remove the three lines inclusive of
<disabled-components>
<item name="com.samsung.android.kgclient.receiver.KGAgentReceiver" />
</disabled-components>
...and changed enabled="3" to enabled="1" in this line
<pkg name="com.samsung.android.kgclient" ceDataInode="2643" enabled="1"
Probably not required, but thought I'd mention it.
Galaxy Tab S6
Android 9
Stock-Rooted
i cant find the line even if i search it
I tried attempted to debloat an S8 (running Pie), but I started receiving this message afterwards. There's no “com.samsung.android.kgclient” in the package-restrictions.xml file. Is there any other place this restriction could be enforced?
Found Another Way 2
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
I went in and deleted package-restrictions.xml and the bak file, I can reboot now and get in with the message, I initially uninstalled payment services, I tried flashing a zip of payment services apk couldn't get that going, now I'm getting android set up pop ups and my twrp won't boot to the recovery loader from within the app, and super su has lost all the settings for applications!?¿ rlly don't want to do a clean flash and re root ... bloody system packages arggghf help
Wow, this was easy. Thanks!
harismuntazir said:
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
Click to expand...
Click to collapse
Hi..how to restart system ui within so limited time
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
i cant find this xml anywhere, please help
Any advice if twrp isn't yet installed but device is already rooted?
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
JoshReuben said:
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
luckily factory reset solves it. i was already getting anxious about paying "ransomware" to samsung service oof
thanks
but my TWRP doesnt mount data
CANDco said:
but my TWRP doesnt mount data
Click to expand...
Click to collapse
Only hard reset can fix Your phone then. If TWRP can't mount data it means that your phone is encrypted and without full wipe you won't be able to unlock it.
Thanks! I just fixed my m51 with this method. I was thinking about restoring full TWRP backup or flashing stock rom as last resort. So glad I found this thread.
I don't know what is wrong with my phone. I disabled the app, and got the message. I did what you suggested and rebooted. but the app re-enabled itself. I tried disabling again and the message came up again. I checked and that line is no longer in my package-restrictions.xml
Luckily for me, just rebooting unlocks my phone, but I think that defeats the purpose....
I kinda want to get rid of that app
adb shell pm enable com.samsung.android.kgclient
will solve the problem
jafferkhan said:
i cant find this xml anywhere, please help
Click to expand...
Click to collapse
Man, that was a trip to do, but on my unlocked S9+, it worked! I could only see the exact file when I opened the .xml file with wordpad on my Win. 10 to edit it, otherwise it's very hard to spot scrolling in TWRP on the device, particularly since the long package list can freeze up while you scroll down.
I should add, that I used an OTG USB Bridge with a type C connector to paste the copied .xml file to the connected flash drive I mounted in TWRP (just scroll up through the directories for "OTG USB' to find the drive to paste it), then put it on my PC, this made the process go even faster.
But it's better to proactively check what apps can be disabled, removed, or in my case frozen with Titanium Pro, before ever having to deal with such a scare as this!
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" />line from the file. It can have different values butIpackage name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
What are procedures on how to remove the file after disabling the package, my Samsung A03 CORE can't mount. So kindly assist me here..