Database Info

Gear 2 losing notification access on phone reboot

I'm on the latest leaked lollipop rom for s4 and upon reboot my gear 2 loses notification access. Has anyone else experienced this? Hard resets, factory resets and updates of both phone and gear don't seem to make a difference.

albiGib said:
I'm on the latest leaked lollipop rom for s4 and upon reboot my gear 2 loses notification access. Has anyone else experienced this? Hard resets, factory resets and updates of both phone and gear don't seem to make a difference.
Click to expand...
Click to collapse
Have you tried going in Security/notification access and allowing gear manager ? I don't have lollipop but I just thought about this...

Yes, in the lollipop rom I'm using the notification access is under sounds and notifications, and it's enabled, until I reboot. Then it loses access.

albiGib said:
Yes, in the lollipop rom I'm using the notification access is under sounds and notifications, and it's enabled, until I reboot. Then it loses access.
Click to expand...
Click to collapse
Have you also tried wiping cache partition and Dalvik cache ?

Indeed, plenty of times,including full wipes of both phone and gear, to no avail. I'll keep trying out solutions and eventually I'll get one.

albiGib said:
Indeed, plenty of times,including full wipes of both phone and gear, to no avail. I'll keep trying out solutions and eventually I'll get one.
Click to expand...
Click to collapse
Well you seem to know what you are talking about so I would say that you ROM seems not to be compatible with the G2, I have no formal knowledge though

I'm beginning to suspect as much. I'll flash another version of LL at home later and see if it's the rom I'm using at the moment (which is giving me umpteen reboots and seems to act like a thermal power plant lol)

*update* flashed different kernel and even though the permission on reboot still occurs, I now get notifications, where as before I didn't,and my phone is cool. I'll post my findings when I flash a new rom.

Same issue here.
I9505 using leaked lollipop. Original Gear running latest OTA Tizen.
Disconnect reconnect and turning off blyeooth does not trigger the issues but full reboot does.
Have tried latest Gear Manager APK leaked from S6 but did not fix.
Hoping for fix soon as its very annoying

Yep, Im pretty much on the same boat as you, latest gear OTA, using latest lollipop leak also, with exactly the same gear manager and issue. I'll certainly keep at it and post a solution, if I find one, here.

By the way, is Svoice working on your gear?

*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.

albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
Hello,
I flashed the last official lollipop touchwiz rom on my GT-I9505.
I have the same problem: After reboot the settings for notification access are lost, only the "glanceview mk" has access.
I have to reenable all other checkboxes (eg. "Tasker", "Tesla Unread",...) until next reboot...
Because I have no root, do you have other solutions?
Regards,
Alexander

same issue for me.
i noticed that happens after rooting my galaxy s4.
i tried reboot the phone before rooting and the permission for gear manager remain.
(sorry for the english)
Regards
Fabio

spam, delete

It happened me the same on note 4 lollipop. I fixed it disabling talkback.Apk
Check what applications remain turn on in the notification access after reboot, once you know them disable them throw application manager, and after that turn on gear manager as notification.
Sent from my SM-N910F using XDA Free mobile app

Bump. This is my problem too on 5.0

solved
albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
Thanks! Your advice eliminate the issue!

albiGib said:
*SOLVED*
freeze 'glance view mk' in titanium backup. No more permission loss.
Click to expand...
Click to collapse
any way to solve this on non rooted phone?

Whatsapp not worrking after Android 6 update

Hi,
I have Smasung Galaxy S6 SM-G920F
I recently updated from Andriod 5.1.1 to 6.0.1. After this update my whatsapp and viber calls are dropping after few seconds.
I tried to change app permissions and power saving features, but didnt solve it.
Please let me know if anyone can help
Thanks...

Did you uninstall and reinstall?

meboy said:
Did you uninstall and reinstall?
Click to expand...
Click to collapse
yes i tried but didnt solve...and even viber has the same issue..
i think its something to do with samsung's recent update...

Shafraz1986 said:
yes i tried but didnt solve...and even viber has the same issue..
i think its something to do with samsung's recent update...
Click to expand...
Click to collapse
Much more likely a software issue on your phone specifically.
Tons of people have recently updated to MM and there would be massive reports around the web if WhatsApp broke for a good number of them.
If you're rooted you could try manually removing the app data for the apps after uninstalling. Then reinstall. Could clear cache, etc. Otherwise a factory reset might be needed.

It happen to me something like that , I flashed custom rom(6.0.1) , I cant remember which rom and I flashed another custom rom (6.0.1) , this time everything was ok so it is not about android 6 update . Try to change rom

KaramAndroid said:
It happen to me something like that , I flashed custom rom(6.0.1) , I cant remember which rom and I flashed another custom rom (6.0.1) , this time everything was ok so it is not about android 6 update . Try to change rom
Click to expand...
Click to collapse
my phone is rooted, so i might try on it. the same exact thing happened for my girl friend's phone, which isnt rooted.
would appreciate if you can also give me an alternative for that.

Ya happened me but I had a titanium backup of WhatsApp. So I uninstalled it and restored it. Worked perfectly.
When I got the MM update (stock) I then did a fresh install of Xtrestolite ROM and that ultimately sorted any issue I had

Phone won't boot up after google play crashes, been fine for 7 days til now (rooted)

Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa

The same thing happened to me out of nowhere. I've read elsewhere of this happening to other people. I don't know what causes it. A clean install should fix your problem, but no telling when or if it will happen again.
Sent from my SM-G930T using Tapatalk

MacTheRipperr said:
The same thing happened to me out of nowhere. I've read elsewhere of this happening to other people. I don't know what causes it. A clean install should fix your problem, but no telling when or if it will happen again.
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
You were rooted right? has this ever happened while you were stock?

I was rooted, the only thing that may have been different than the op, was the I had xposed installed. But as I said. After the clean install of the most recent firmware the crashes and boot loop stopped ave battery life improved as well. Also this has never happened to me until I rooted my device.
Sent from my SM-G930T using Tapatalk

btort1 said:
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Click to expand...
Click to collapse
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.

Corwinder said:
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.
Click to expand...
Click to collapse
how long have you been rooted and without any problems? that thread has tons of pages, are you sure this works 100%? its security policy updates 4.1.69 right?

btort1 said:
how long have you been rooted and without any problems? that thread has tons of pages, are you sure this works 100%? its security policy updates 4.1.69 right?
Click to expand...
Click to collapse
lol No I'm not sure it works but someone else is sure it works. I'll be honest with you. This is my third attempt at rooting this phone. I rooted when the option first came out and 1 week later I got bootlooped so I went back to stock and rerooted. A week later bootloops. That's when I gave up until more information surfaced on my problem. And behold it did. That's when I learned about freezing the security policy update. And it makes sense to me too.

Corwinder said:
You need to use Titanium backup to freeze the Security policy update agent. I've had the same problem and after doing a search I found this thread with a lot of useful information.
Click to expand...
Click to collapse
Corwinder is absolutely right. I read through that thread as well. AS SOON as you take that POLICY UPDATE that it tells you to accept, you're done. From that point on its only a matter of time before you experience a BOOTLOOP. NEVER UPDATE THE SECURITY POLICY WHEN IT POPS UP. DISABLE SECURITY POLICY. Haven't had a bootloop in 4 days now.
Corwinder I'm actually on my third root as well, hah. Third time is a charm. I just want to restate that it's not just disabling security policy.... If you accept that security policy update pop up which happens probably ~5mins after you rooted, you're going to bootloop. You can also disable security policy updates in settings. Do this as soon as you root. Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.

Thank you guys for this thread / help.
Woke up today and wanted to see what offers were available on T-Mobiles Tuesday App. Said that the app needed updated, then Google.playstore keep crashing. Reboot phone and ran into the famout bootloader screen / process.
Saw this thread days ago and followed the steps and I "think" im good now.
Step that I took :
Reflashed PG1 through Odin v3.12 (Prince Comsy)
Reapply root / SuperSU
Disabled security policy settings by going to Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.
Downloaded TitaniumBackup / Flashfire
Applied fix+debloat script via Flashfire
Deleted more Bloatware through Titanium Backup.
Enjoying fast, responsive phone
#rooton

Eighthourblink said:
Thank you guys for this thread / help.
Woke up today and wanted to see what offers were available on T-Mobiles Tuesday App. Said that the app needed updated, then Google.playstore keep crashing. Reboot phone and ran into the famout bootloader screen / process.
Saw this thread days ago and followed the steps and I "think" im good now.
Step that I took :
Reflashed PG1 through Odin v3.12 (Prince Comsy)
Reapply root / SuperSU
Disabled security policy settings by going to Settings -> Lock Screen & Security -> Other security Settings -> Security Policy Updates -> Turn off automatic updates.
Downloaded TitaniumBackup / Flashfire
Applied fix+debloat script via Flashfire
Deleted more Bloatware through Titanium Backup.
Enjoying fast, responsive phone
#rooton
Click to expand...
Click to collapse
It won't remove com.dmpolicy but if you disabled it you're fine.

nwg5817 said:
It won't remove com.dmpolicy but if you disabled it you're fine.
Click to expand...
Click to collapse
its not coming up in Titanium Backup, is there another way to make sure its disable / deleted?

nwg5817 said:
It won't remove com.dmpolicy but if you disabled it you're fine.
Click to expand...
Click to collapse
edit

SHealth & Private Mode with rooted Nougat

Hey guys,
It sounds like that neither SHealth nor private mode is working when the phone is rooted. In MM I just used XTouchwiz and made the device status official. What needs to be done to get both working in rooted Nougat? I´ve already seen some roms which figured out, but I want to know how it is done so can use a rooted stock rom.
Thanks in advance

Why not deinstall SHealth as a system-app and reinstall it using the Samsung app-shop. It worked for me on MM.

gedhe said:
Why not deinstall SHealth as a system-app and reinstall it using the Samsung app-shop. It worked for me on MM.
Click to expand...
Click to collapse
Is it really that simple on Nougat? Some users report that a tripped knox is preventing SHealth from starting. I´d be suprised if this method tricks the system.

gedhe said:
Why not deinstall SHealth as a system-app and reinstall it using the Samsung app-shop. It worked for me on MM.
Click to expand...
Click to collapse
Not worked for me =(

GerasVille said:
Is it really that simple on Nougat? Some users report that a tripped knox is preventing SHealth from starting. I´d be suprised if this method tricks the system.
Click to expand...
Click to collapse
I am rooted, so Knox definetly is ticked and SHealth was deinstalled and then reinstalled using the Samsung app-shop (as written above). And SHealth is happily counting steps and stuff. So, for me it is working on a rooted S7!

gedhe said:
I am rooted, so Knox definetly is ticked and SHealth was deinstalled and then reinstalled using the Samsung app-shop (as written above). And SHealth is happily counting steps and stuff. So, for me it is working on a rooted S7!
Click to expand...
Click to collapse
Probably it worked on MM and doesn't work on Nougat anymore.

GerasVille said:
Probably it worked on MM and doesn't work on Nougat anymore.
Click to expand...
Click to collapse
I am using Nougat 7.0 beta 3 and the phone is rooted and SHealth is working fine and counting steps all day long. No issues at all with running it.

zimcommando said:
I am using Nougat 7.0 beta 3 and the phone is rooted and SHealth is working fine and counting steps all day long. No issues at all with running it.
Click to expand...
Click to collapse
Hmm OK. But did you also update SHealth from the Samsung app store? Did you debloat your device and delete knox? Can you check if private mode still works?
Thanks for your replies guys.

I confirm, since I updated to official Nougat BTU yesterday, S-Health doesn't work anymore. Knox tripped but 100% official installation without root anymore (on top, factory reset done before moving to Nougat).
When I open the app, it says the device security has been compromised and that Knox cannot work. Samsung just decided to limit the usage or our phone if Knox is tripped, even if the phone isn't rooted!!

Hi!
My phone has tripped KNOX, S Health didn't working on fresh Nougat install.
After I rooted my S7 with Nougat, I deleted the current S Health files in system/app and I download an older (4.8 maybe) version of program from apkmirror and install it as "normal" application, then this updated with newest one from play store and it working good.
Sorry for my English

Jul84 said:
I confirm, since I updated to official Nougat BTU yesterday, S-Health doesn't work anymore. Knox tripped but 100% official installation without root anymore (on top, factory reset done before moving to Nougat).
When I open the app, it says the device security has been compromised and that Knox cannot work. Samsung just decided to limit the usage or our phone if Knox is tripped, even if the phone isn't rooted!!
Click to expand...
Click to collapse
Same problem

Hi,
i was not able to successfully root the nougat S7, any help from you ? Which method have you used? I tried last Autoroot (~20min Bootloop) and TWRP+SU zip, the same.

thorium666 said:
Hi,
i was not able to successfully root the nougat S7, any help from you ? Which method have you used? I tried last Autoroot (~20min Bootloop) and TWRP+SU zip, the same.
Click to expand...
Click to collapse
Hi! You would try this:
https://forum.xda-developers.com/showpost.php?p=70618589&postcount=8960
It's working to me...

Thanks,
my phone is encrypted (i want it encrypted) and has the SD card configured as internal storage. They explaining here to wipe, this is not an option as this costs too much time to get it back to current state. All steps excepted the wiping i tried. resulted in >20min loop.

thorium666 said:
Thanks,
my phone is encrypted (i want it encrypted) and has the SD card configured as internal storage. They explaining here to wipe, this is not an option as this costs too much time to get it back to current state. All steps excepted the wiping i tried. resulted in >20min loop.
Click to expand...
Click to collapse
In this method the wipe is necessary. I can't find other working root solution at this time
While the device is not rooted actually, (KNOX Warranty Void 0x1 already) S Health can't working, that is must have to me.
Or Or

Warranty is not complete void by EU Law. Samsung can only void what they offer beside the minimum regulations.
I have right now also a phone i can not really use for Internet (ads) and it is carrying some social-media-bloatware. Need to wait for updates of CF Autoroot or what else.

Also S Health working fine in LineageOS 14.1 for me. Install Health Service APK (Google) ans S Health from Playstore

Just download version 4.8 and it works like a charm with nougat if you're rooted, have to uninstall the original s health with maybe titanium backup and then download from here
https://f.apk4fun.com/f.php?p=10204...ppRU1xZz09&d=ajk0Q0FnMXZHcmVSNVdvYUNRYjVodz09.
Have fun

Try set ro.config.tima to 0 in your build.prop. If that doesn't work then you'll need a patched AuthFramework.

Caution, Nov update causes SystemUI FC if you use Substratum.

So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..

Same thing happened to me. Even after I uninstalled all the themes and substratum I still got the FC.
Sent from my SM-N950U using Tapatalk

How did you reset the phone after the system ui crash?

chaztro1892 said:
How did you reset the phone after the system ui crash?
Click to expand...
Click to collapse
Through recovery
Sent from my SM-N950U using Tapatalk

Circlel05 said:
Through recovery
Click to expand...
Click to collapse
Cool. Thanks. So none of the substratum themes will work I assume.

You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.

ShrekOpher said:
You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.
Click to expand...
Click to collapse
Can the themes be reinstalled after the update?

chaztro1892 said:
Can the themes be reinstalled after the update?
Click to expand...
Click to collapse
Yeah I am running swift black with no issues right now.

ShrekOpher said:
Yeah I am running swift black with no issues right now.
Click to expand...
Click to collapse
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?

newguy15 said:
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?
Click to expand...
Click to collapse
I never used the system UI technically that is not supported on any Samsung devices with out root. It worked before, but was never officially support.

My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.

eXtremeDevil said:
My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.
Click to expand...
Click to collapse
Use adb to uninstall the Substratum overlay apks. I think the system ui overlay apk is the most important one to uninstall.
Then it should reboot fine

I dont have adb

eXtremeDevil said:
I dont have adb
Click to expand...
Click to collapse
You can set it up on a PC really easily.
You could try booting into "safe mode" and uninstall ingredients the overlay apks that way.

I meant on the phone, activated. I do have adb on my phone and my computer.
Safe mode didn't work eigther.
I ended up performing a factory reset.
Thanks anyway to all

This happened to me last week. I called AT&T and they ran through all their BS, they didn't have a clue what was causing it so they had me take my phone to a Samsung Experience Store AKA Best Buy. The tech there was useless I knew more about Samsung phones than he did so I ended up doing a factory reset. After getting my phone all set up and my apps downloaded I rebooted my phone and the same, thing so I called AT&T and they sent me a new phone priority which took 7 days ?. I got my new phone set it up download my apps did the update yesterday and boom same thing. My first mistake was not coming to this forum and not doing a search.

(This 'Should' be common knowledge when using substratum or any third party overlay that interacts with system files.)
But you should always uninstall any system overlay before performing a software update.
Otherwise you risk facing the SystemUI Force close issue.
If you are rooted you can recover via recovery (TWRP)
if you are not rooted the only way to recover without loosing your data is to try this:
How to recover?
You will have to boot up in Safe Mode (comes default on every device)
Reboot your device
Hold down the Volume Down key while booting up
You are now in Safe Mode
Go into Settings -> Apps, then find the overlay you think is messing up and uninstall!
How to recover if the above doesn't work? (Credits to Evozi)
You will have to boot up in Safe Mode (comes default on every device)
Turn on screen and press power button. It will show "Shutdown", "Restart", "Emergency Mode"
Turn on "Emergency Mode", keep spam the checkbox so you can tick the checkbox to proceed the agreement. (phone is super lagging)
While you are in emergency mode, you have very limited access. Open any system app and go to recent task list.
Long press the app task, press the info icon and app detail page will appear.
Hit the back button and it will show your whole app list.
Find your overlay and remove all its storage and phone permissions.
Deactivate Emergency Mode and now you are back to TouchWiz.
Uninstall the overlay app.
Click to expand...
Click to collapse
I was testing new and old system overlays when the Note 8 first came out to see what worked and what didn't, the ones that didnt gave me this problem.
You will most probably find the first one does not work and the second is a pain to get working, but personally i have had the Emergency mode method work for me after a few trys. I gave up at one point and started downloading firmware files to be honest but i gave it another shot while waiting and it worked.
Hope this helps - Hit thanks so this post gets shown to other users coming here looking for help

jdmsohc22 said:
So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..
Click to expand...
Click to collapse
Awesome thanks for the heads up. Literally just got the substratum 2 days ago and am loving it so far.

I ended up factory reseting for this very reason
Sent from my [device_name] using XDA-Developers Legacy app

Has anyone on ATT but bought their phone unlocked from Samsung? On here