Related
Is anyone having issues with security setting under personal? When I select it, the settings application force closes with Unfortunately, Settings has stopped. Thanks in advance for any suggestions. Standard Verizon note 4. no root.
Played around a bit and decided to do a settings reset which corrected issue.
Sent from my SM-N910V using XDA Free mobile app
I had the same issue, factory reset fixed it but now 2 days later the problem has returned. Can't access the security settings without it force closing.
Sent from my SM-N910V using XDA Free mobile app
Thanks for the feedback. Reset settings worked for me. Only had to change a few things back from default. Did not have to redo apps. I spoke with Verizon and a patch may be coming in Jan. Some apps and wireless charging have been causing an issue with the security setting.
Sent from my SM-N910V using XDA Free mobile app
Yeah just tried resetting the settings and it didn't fix it for me. Thanks for the suggestion though.
Sent from my SM-N910V using XDA Free mobile app
Problem returned for me last night. This time I had to reset. Did the problem come back again for you?
Resetting the settings didn't work for me and I don't feel like factory resetting my phone every couple days so I guess it's gonna stick around a while.
Sent from my SM-N910V using XDA Free mobile app
I had to start in safe mode to get security settings to open up for me. Not a great long term solution but it worked so I could change the unknown sources setting.
Thanks for the reply, how do you start in safe mode?
These are the instructions for the Note 3 but they work:
With the device powered off, press and hold the Power button until the Samsung Galaxy Note 3 logo appears then release.
With the logo on the screen, press and hold the Volume down button until Safe mode appears in the lower left of the screen then release.
Note This may take up to 45 seconds.
Thanks!
plyle said:
These are the instructions for the Note 3 but they work:
With the device powered off, press and hold the Power button until the Samsung Galaxy Note 3 logo appears then release.
With the logo on the screen, press and hold the Volume down button until Safe mode appears in the lower left of the screen then release.
Note This may take up to 45 seconds.
Click to expand...
Click to collapse
Thank you. Just got this device today, and one of the first things I tried to do was install an app I am testing. It kept crashing trying to get to security. I tried Safe Mode, and it worked great. Thanks again.
KeylanHalfdan said:
Thank you. Just got this device today, and one of the first things I tried to do was install an app I am testing. It kept crashing trying to get to security. I tried Safe Mode, and it worked great. Thanks again.
Click to expand...
Click to collapse
No problem. Glad I could help. I was very frustrated with it. Hope they send an update to fix this soon.
Sent from my SM-N910V using Tapatalk
That kept happening to me and I finally figured out a solution! I kept having my apps reinstalled from Google and, whenever an app that I had previously used that required root access was installed, Settings would crash whenever I tried to open Security. So, it was a long process but I reinstalled only those apps that didn't need root access. Afterwards, I kept testing to make sure I could still access Security without the crash and, when something was installed that caused the crash again, I knew which app it was, uninstalled it, and all was fine again. I had to reset the phone 6 times to figure this out but all's good now!
terryr97 said:
That kept happening to me and I finally figured out a solution! I kept having my apps reinstalled from Google and, whenever an app that I had previously used that required root access was installed, Settings would crash whenever I tried to open Security. So, it was a long process but I reinstalled only those apps that didn't need root access. Afterwards, I kept testing to make sure I could still access Security without the crash and, when something was installed that caused the crash again, I knew which app it was, uninstalled it, and all was fine again. I had to reset the phone 6 times to figure this out but all's good now!
Click to expand...
Click to collapse
Glad you got it working. Would you be able to tell me what app it was? I have the same problem.
I had so many apps that needed root that it just made sense to not have Google install my apps after resetting. I really can't recall specifically which one it was. What I do suggest, which will take a while but is so worth the time, is to make a list of what's on there now and only reinstall like 3 at a time and then check to make sure that everything's ok. If it is, install a couple more, etc. That way, if one screws it up, you'll know which one to uninstall rather than having to reset it all over again. At least if you do install one that needs root and, therefore, screws it up for you, you can just uninstall that one program. Good luck! Let me know how it goes. ☺
Was finally able to figure this out (for me anyway). Its my S View cover. With the cover off I have no problem getting into security put it back on and it forcecloses. I went to Best Buy and tried 2 others and they both caused the security to forceclose as well.
Was chatting with a Samsung Rep where they remotely control your phone and she came up with the conclusion that it is a bad app and wants me to do a factory reset and add the apps back 1 at a time. I will wait till I flash a ROM and do it then. I am leaning towards that it is a app. If every Note 4 with a S View cover had this issue then it would be more widely known.
I had the S cover and that wasn't the problem. Like I said, it was cos I was having Google automatically install my old apps, some of which were apps that needed root like Titanium Backup, Rom Toolbox, etc.. I was able to put Apex as my home, just not apps that needed root. Titanium is the reason I want root so much. Being able to clean up or delete apps I don't use.
Yes, i had the same problem with my s view cover. Once i took it off, i was able to go back into the security settings.
skillzo1 said:
Yes, i had the same problem with my s view cover. Once i took it off, i was able to go back into the security settings.
Click to expand...
Click to collapse
I figured out the app that was causing the issue for me. I use Nova and also TelsaUnread. I uninstalled Telsa and no more problem even with the S View cover.
If any of you are having Lag, slowness, signal issues, bad battery life, etc. and/or other weird glitches after the lollipop update you need to factory reset your phone.
This is a know bug with updating from Kitkat to lollipop. It has happened on many devices, Nexus 5, nexus 7, Shield tablet, N910A etc.
Just factory reset your phone and re-set it up and most if not all of the problems will be gone.
From my brief understanding it has to do with some downloaded apps not switching from davlink to ART correctly during the OTA process. Facebook on my shield tablet was a notorious culprit.
Just an FYI hope it helps a few people out.
Sent from my SM-N910T using XDA Free mobile app
We did have one person factory reset to attempt to solve the "heart rate light turning on" bug, and it did not solve the problem.
Have you noticed this bug or used S Health yet?
One list I always go through is: update, update all apps, boot into recovery, wipe cache, and reboot twice. Works great and I know a bunch of others see similar results
Sent from my SAMSUNG-SM-N910A
ShrekOpher said:
If any of you are having Lag, slowness, signal issues, bad battery life, etc. and/or other weird glitches after the lollipop update you need to factory reset your phone.
This is a know bug with updating from Kitkat to lollipop. It has happened on many devices, Nexus 5, nexus 7, Shield tablet, N910A etc.
Just factory reset your phone and re-set it up and most if not all of the problems will be gone.
From my brief understanding it has to do with some downloaded apps not switching from davlink to ART correctly during the OTA process. Facebook on my shield tablet was a notorious culprit.
Just an FYI hope it helps a few people out.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Luckily I was already running ART prior to the update to 5.0.1, so I haven't seen any of these issues yet, and hope none crop up. :good:
Luckily I haven't had any of the glitches a few people have mentioned. However, my friend with an S5 needed to factory reset hers after being pushed the lollipop update and it smoothed everything out. Just like when flashing a ROM guys...starting fresh helps a lot.
Anytime there is a major change to an OS, whether it be on my PC/Mac or my phone, I always factory reset and start over. ALWAYS. Too many little bugs and quirks pop up in software upgrades for me to waste my time with that stuff. I'd always rather start fresh...plus then I can weed out the apps I don't use anymore.
As an old habit, I always do a system reset after a major upgrade. I did the same with this upgrade and it has been running pretty smooth for me.
I am now experiencing lag in a bunch of places, yet I did a factory reset.
greekunit690 said:
One list I always go through is: update, update all apps, boot into recovery, wipe cache, and reboot twice. Works great and I know a bunch of others see similar results
Sent from my SAMSUNG-SM-N910A
Click to expand...
Click to collapse
I did this right here cause I noticed my battery was draining a good amount when the phone wasn't being used. After this and a full charge, the phone went back to how it was before.
I wiped cache and factory reset 3 times and I haven't experienced any of the aforementioned issues.
greekunit690 said:
One list I always go through is: update, update all apps, boot into recovery, wipe cache, and reboot twice. Works great and I know a bunch of others see similar results
Sent from my SAMSUNG-SM-N910A
Click to expand...
Click to collapse
This is what I did. I had absolutely no issues with the update.
The minor issue is the quick note app pops up very slowly. But that is fairly minor, and not significantly different from kitkat.
factory reset
I rebooted a couple of times after the update, and wiped cache in recovery. Still experienced lag all over the place, especially w/ the dialer. I factory reset last night and it's been running more smoothly since.
Has anyone noticed that when booting into recovery, it says "installing system updates"? I even got a message, before the recovery screen popped up, that "no command found". After that popped up briefly, the phone went into recovery and all seemed fine.
PhonoRoboto said:
I rebooted a couple of times after the update, and wiped cache in recovery. Still experienced lag all over the place, especially w/ the dialer. I factory reset last night and it's been running more smoothly since.
Has anyone noticed that when booting into recovery, it says "installing system updates"? I even got a message, before the recovery screen popped up, that "no command found". After that popped up briefly, the phone went into recovery and all seemed fine.
Click to expand...
Click to collapse
Yup,
Dead Andy then into recovery. Weird...
This update to lollipop on the note 4 has been the best update experience that I've had on any phone. Love it. And yes, factory reset solved many issues that were honestly minor and I really didn't feel I had to, but I did bc I'm crazy. ..but it was worth it.
Back up phone via kies, I am impressed it worked great.
Sent from my SAMSUNG-SM-N910A using Tapatalk
I'm going to try this again. I've already done it before but hopefully this will fix my problem.
On 4.4 I went 2 days with heavy usage. It was insane! I use my phone a ton at work for RDP, videos, and other IT related stuff. Now I can barely go 1 good full day.... Really hope this fixes it.
My update went well without any troubles, but now I am few weeks into using Lollipop and I definitely notice faster battery drain. I also have disappearing icons, just like others complained (Google Hangout and Phone icon disappeared).
I'm not experience a lot of major issues....but I did do a recovery reset....but I reinstalled via kies. I'm planning on doing a recovery flash again....but this time I'm not going to have it install the apps.
Sent from my SAMSUNG-SM-N910A using Tapatalk
It seems like my battery is continually getting worse with lollipop. I even tried a factory reset and it still did not fix my issue. I miss the days of 6hrs of SOT.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
falcons2 said:
It seems like my battery is continually getting worse with lollipop. I even tried a factory reset and it still did not fix my issue. I miss the days of 6hrs of SOT.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
I'm not experiencing this I'm actually getting very good battery life. Don't know if you have disabled the system apps you don't use???
Also something I always used to do when I had the T-Mobile note 4 rooted of course, I always disabled Samsung push services it was always recommended. Don't know if it would make any difference but you can give it a shot.
I have all the apps I don't use disabled and it still hasn't been helping. I'm thinking about calling ATT and getting an exchange
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
I used the OK1 tar through ODIN, then did a factory reset then took the 6.0.1 update. Yesterday I got probably 2 random reboots and now this morning I have had 4 one after another probably 5 minutes apart from each other. I am using the I heart radio app to listen to a local radio show and the phone keeps rebooting. I thought maybe it was the app causing this so I uninstalled and reinstalled it and the phone keeps rebooting. I recently purchased a replacement Anker battery and have been using it for a week now with no issues. Anyone have something similar like this happening? Anyway to fix this besides the obvious wipe everything clean and try again?
EDIT: It's the app, others are reporting the same issue with newer phones running Marshmallow.
Same problem. Sprint is getting me a replacement
Sent from my Nexus 5 using Tapatalk
Same here with I Heart Radio app.
xbmoyx said:
I used the OK1 tar through ODIN, then did a factory reset then took the 6.0.1 update. Yesterday I got probably 2 random reboots and now this morning I have had 4 one after another probably 5 minutes apart from each other. I am using the I heart radio app to listen to a local radio show and the phone keeps rebooting. I thought maybe it was the app causing this so I uninstalled and reinstalled it and the phone keeps rebooting. I recently purchased a replacement Anker battery and have been using it for a week now with no issues. Anyone have something similar like this happening? Anyway to fix this besides the obvious wipe everything clean and try again?
EDIT: It's the app, others are reporting the same issue with newer phones running Marshmallow.
Click to expand...
Click to collapse
Same Here...
Mine does as well!
Sent from my SM-N910P using XDA-Developers mobile app
I don't use the app, and my phone does not restart.
random45 said:
I don't use the app, and my phone does not restart.
Click to expand...
Click to collapse
Correct, it's the app causing the reboots. I have reverted back to LP for now since there's no issues.
Sent from my SM-N920P using XDA-Developers mobile app
Samsung Note 4 reboots randomly in IHeart app
Mine has shut down automatically when listening to IHeart App, but not with other apps, so I assume it's that app that is causing it. I did uninstall & reinstall app. Did not help. I cleared system cache. Did not help. I initially did soft reboot with battery out and in after 10 seconds. Did not help. I have not contacted sprint yet, but that is my next option. Any help would be appreciated.
KarenLMarcum said:
Mine has shut down automatically when listening to IHeart App, but not with other apps, so I assume it's that app that is causing it. I did uninstall & reinstall app. Did not help. I cleared system cache. Did not help. I initially did soft reboot with battery out and in after 10 seconds. Did not help. I have not contacted sprint yet, but that is my next option. Any help would be appreciated.
Click to expand...
Click to collapse
If your set on remaining on MM, use a different radio app and uninstall IHeartRadio for now until they fix the problem.
Sent from my SM-N920P using XDA-Developers mobile app
KarenLMarcum said:
Mine has shut down automatically when listening to IHeart App, but not with other apps, so I assume it's that app that is causing it. I did uninstall & reinstall app. Did not help. I cleared system cache. Did not help. I initially did soft reboot with battery out and in after 10 seconds. Did not help. I have not contacted sprint yet, but that is my next option. Any help would be appreciated.
Click to expand...
Click to collapse
FYI if you download the IHeartRadio app through the Galaxy Apps store it doesn't reboot the device.
Sent from my SM-N910P using XDA-Developers mobile app
I uodate Flashed N910p With 6.0.1 now phone is restarting randomly after 10 to 16 seconds. Fkashed with another firm with 5.1.1 But still restarting. Any body please help.
I have this problem but don't use that app. ....
For me I am getting the soft reboot every 20 mins or so... bloody annoying! !!
MSK1 said:
I have this problem but don't use that app. ....
For me I am getting the soft reboot every 20 mins or so... bloody annoying! !!
Click to expand...
Click to collapse
Rooted? Are you seeing a pop-up for the reboot (prompt)? Screenshots or logs?
How did you upgrade to marshmallow? What update are you on? What ROM are you running? Custom kernel? If rooted stock with custom kernel, have you fully removed ItsOn and Knox? Did you wipe or factory reset? Include your steps to get an idea of what is causing the reboot issue.
(If stock un-rooted, you may have some residual data from Lollipop. If rooted with custom kernel, you may have files from ItsOn or Knox causing issues. Basically, un-rooted and rooted have their own set of concerns. Need more info to offer suggestions.)
Sent from my SM-N910P using Tapatalk
samep said:
Rooted? Are you seeing a pop-up for the reboot (prompt)? Screenshots or logs?
How did you upgrade to marshmallow? What update are you on? What ROM are you running? Custom kernel? If rooted stock with custom kernel, have you fully removed ItsOn and Knox? Did you wipe or factory reset? Include your steps to get an idea of what is causing the reboot issue.
(If stock un-rooted, you may have some residual data from Lollipop. If rooted with custom kernel, you may have files from ItsOn or Knox causing issues. Basically, un-rooted and rooted have their own set of concerns. Need more info to offer suggestions.)
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Not rooted.
Best description I can give is that at night when my nighclock is on. ...
the light on back and menu button will come on...
simultaneously the my note edge message will flash on the edge replacing the night clock for a few seconds (this is the background soft reset I think)...
the phone is not functional for these few seconds ie if i press a button to wake screen up then it will wait and hi locker won't let fingerprint work after this happens.
Rinse and repeat every few minutes.
MSK1 said:
Not rooted.
Best description I can give is that at night when my nighclock is on. ...
the light on back and menu button will come on...
simultaneously the my note edge message will flash on the edge replacing the night clock for a few seconds (this is the background soft reset I think)...
the phone is not functional for these few seconds ie if i press a button to wake screen up then it will wait and hi locker won't let fingerprint work after this happens.
Rinse and repeat every few minutes.
Click to expand...
Click to collapse
Not an answer but how many of these applications you mention are third party applications?
Typically, lock-screen is only available a few seconds and screen is forced off; deep sleep may eventually occur but you have only a small amount of control to prevent deep sleep; that's usually a good thing. These apps may not be remaining fully functional when conflict results in screen going off unexpectedly or deep sleep trying to save your battery kicks in.
Dunno what compatibility is expected with multiple apps active while trying to keep lock-screen on or wake frequently? My use of lock-screen apps is limited to my third party alarm. I'm happy that it wakes to alarm; I can snooze and allow screen to go off quickly and wake for snooze until I dismiss the alarm (without having to unlock screen). That's about all I'm familiar with lock-screen applications.
My only suggestion would be to try to limit the third party apps used in lock-screen mode to find the maximum compatibility. Dunno, if those are third party applications conflicting, it's just a guess.
Maybe one or more of these applications aren't fully compatible with marshmallow?
On the subject of waking phone being slow, I think it was reported by non rooted users that factory reset cured that for some users. It's possible that if phone wasn't factory reset coming to Marshmallow from Lollipop, that factory resetting now would help.
Sent from my SM-N910P using Tapatalk
Please register your request for a response from the Top software team at Samsung here....
https://us.community.samsung.com/t5...-Issue-Mods-Need-To-Escalate/m-p/50403#U50403
Before anything, sorry if there is a solution already for this, I did look this up here and no one seems to have an answer.
I was running stock up to about June, and my imprint was working fine, albeit sometimes it would give my issues. I then unlocked bootloader, installed twrp, and flashed a few roms, including omni and cm13. I stuck with cm13 but on both roms the imprint option still worked. It worked from June up until last month around the 15th. I noticed I was getting more and more errors with it. Specifically the one that says imprint not available or something like that. Then I rebooted and the option was completely gone. My finger also wasn't recognized when placing it on the sensor. I wiped my system and it did nothing, I reverted back to an older build of cm, and still nothing. I tried different roms and nothing. I then flashed stock nougat and during the initial setup I saw the option for imprint was there but the sensor would read my finger. I went to the options to see if I could find imprint but it was gone again. I didn't purchase my phone through Google so an exchange is not an option. I saw a post on here of someone who fixed it but he did not go into specifics on how he fixed it. He just mentioned after flashing nougat he went to developer options and changed the encryption. Anyways I hope someone has the answers because imprint is life now.
Sent from my Nexus 5X using XDA-Developers mobile app
HyDRo1X said:
Before anything, sorry if there is a solution already for this, I did look this up here and no one seems to have an answer.
I was running stock up to about June, and my imprint was working fine, albeit sometimes it would give my issues. I then unlocked bootloader, installed twrp, and flashed a few roms, including omni and cm13. I stuck with cm13 but on both roms the imprint option still worked. It worked from June up until last month around the 15th. I noticed I was getting more and more errors with it. Specifically the one that says imprint not available or something like that. Then I rebooted and the option was completely gone. My finger also wasn't recognized when placing it on the sensor. I wiped my system and it did nothing, I reverted back to an older build of cm, and still nothing. I tried different roms and nothing. I then flashed stock nougat and during the initial setup I saw the option for imprint was there but the sensor would read my finger. I went to the options to see if I could find imprint but it was gone again. I didn't purchase my phone through Google so an exchange is not an option. I saw a post on here of someone who fixed it but he did not go into specifics on how he fixed it. He just mentioned after flashing nougat he went to developer options and changed the encryption. Anyways I hope someone has the answers because imprint is life now.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I can tell you that Nougat included new firmware for the touchscreen sensor, but it sounds like you are having hardware problems with the sensor.
Some people have reported similar behavior when some moisture got on the sensor, sweat, condensation from humidity, etc.
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.
https://support.google.com/pixelphone/thread/14074635?hl=en
Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.
So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.
I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.
I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.
@MeetFace, yes! Same here since the November update. Something isn't right.
I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.
darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!