I've updated to Android 11 a few days ago and since then my phone freezes multiple times a day. The screen is still partially usable and I can invoke the restart menu with long power button press but it doesn't do it. I always have to use the very long power button press to reset it.
I'm using Nova Launcher, but it also froze with the stock Google launcher. I did the update with the factory image and used Magisk Canary to unlock.
I'm pretty puzzled what's going and can't find anything on the internet, except mentions of that on earlier Android 11 versions.
Does someone have similar experiences or tips how to fix this?
I experienced the same thing yesterday. I had to do a reset like you did. I'm also rooted with Magisk Canary and use Nova like you. I'm wondering if at some point I will have to do a full clean install.
Rick
Sent from my Pixel 3 XL using Tapatalk
Yup, same here, also rooted. Literally happened 2 minutes ago. There's no pattern to it either - so not when I use a particular app or anything.
Not on nova though, just the stock launcher.
Same here. Froze this morning while it was sitting on the counter charging. Takes power button long press to get it to restart. Then, it hangs right after I enter my pin. I have to restart it 4 times before it gets past the "hang".
I'm having the same issue here. Phone has frozen multiple times after rooting. Other times it works fine. Can't seem to figure out the cause. Also no particular apps being used. I'm on Nova.
Sent from my SM-N976U 5G using XDA-Developers Legacy app
---------- Post added at 10:02 PM ---------- Previous post was at 09:45 PM ----------
After disabling all Magisk modules, it worked fine and booted. I'll report back if I have issues again. Maybe it's a module causing it. I had Viper, systemless Host and WiFi Bonding. Not sure if one of these was causing it.
Sent from my SM-N976U 5G using XDA-Developers Legacy app
newkydawg said:
Same here. Froze this morning while it was sitting on the counter charging. Takes power button long press to get it to restart. Then, it hangs right after I enter my pin. I have to restart it 4 times before it gets past the "hang".
Click to expand...
Click to collapse
Interesting you mention charging... I had just put mine on charge last night when it happened.
same thing, was locked up and only option was to hold power/ volume up to reset. it would reboot and do it again, this happened 4 times in a row and then I noticed I was not able to get into my app drawer so on the 5th time I quickly went into titanium and froze nova launcher and I am in. My Magisk I have Props config, busybox and systemless hosts for modules. I see there is an update for props config and magisk manager so will try that. I was debating flashing back to 10 if this keeps up
[/COLOR]After disabling all Magisk modules, it worked fine and booted. I'll report back if I have issues again. Maybe it's a module causing it. I had Viper, systemless Host and WiFi Bonding. Not sure if one of these was causing it.
Sent from my SM-N976U 5G using XDA-Developers Legacy app[/QUOTE]
Seems there is an issue with the Systemless Host module and that's the only module I have enabled. There are several posts in the XDA Adaway thread that point to it. It's been reported on GitHub and in the Magisk thread, too.
I have had this also. Finally today I found the module, at least for me. It is the systemless hosts module. Makes sense...they moved that around a bit in 11.
TonikJDK said:
I have had this also. Finally today I found the module, at least for me. It is the systemless hosts module. Makes sense...they moved that around a bit in 11.
Click to expand...
Click to collapse
Ty!
What i did was just install systemless hosts module after install any other modules and reboot. No more freezing for me. Hope it works for you!
I can't see any modules in my Magisk. I can click on 'Systemless hosts' in Settings, but I can't deactivate them. I disabled Superuser access for AdAway and so far the phone hasn't crashed.
Thanks for the tip!
Update: it just froze
Has anyone read about any updates to this issue?
Sent from my Pixel 3 XL using Tapatalk
C5Longhorn said:
Has anyone read about any updates to this issue?
Click to expand...
Click to collapse
Nothing happening on GIT. But the issue is still open so he will fix it. I know there is major release coming for Magisk so that is probably taking priority.
I can't see any modules, so I switched Magisk to 'Magisk Core Only Mode' but my phone is freezing every few hours. I have to downgrade to Android 10 to be able to use it.
I had it without root and clean install, just fully stock but sadly it's very buggy. Gboard lags, Sistem UI glitches while in landscape and full screen mode, it's unstable to play games and will break some elements like settings, general ui, unresponsive navbar even in gestures and in some cases will lag the phone completely.
My overall experience it's like walking in a forest full of landmine, admiring how the new small feature helps and satisfy but once you enjoy much of it you suddenly step in a landmine with tons of bugs
With AdAway 5.09 I only had one freeze yesterday. I have since disabled Systemless Hosts and no freezes so far.
2Wires said:
With AdAway 5.09 I only had one freeze yesterday. I have since disabled Systemless Hosts and no freezes so far.
Click to expand...
Click to collapse
I'm on adaway v4, deleted systemless hosts, install my modules, reboot, install systemless hosts, reboot AND no more problems for me. Hope it works for you if you need adaway.
The only thing that helped for me is disabling the systemless hosts module.
No combination of clean re-imaging, installing different versions of magisk, or module enable/disable reboot manipulation helped.
This is with adaway 5.0.9. To be clear, I can clean boot with these fixes people have suggested, but after 1-3 days, you'll end up frozen and need to reboot again, hopefully without missing calls or sms in the process.
Hopefully there's a fix sooner than later, but as a workaround you can use vpn based ad blockers. It looks like adaway has an option for this on 5.0.9, but it's greyed out. I assume it's available if you deny it root access to the app.
Glad I wasn't the only one having this issue, I thought after updating to October monthly update it'd be resolved but nope. Kinda bummed that the main reason I root is to use adaway and now I have to disable systemeless host. Hopefull there'll be a stable fix soon
I had enough with it too so caved and factory reset , re rooted and back to where I was.
1 day, so far no glitches! And it does seem smoother and less battery drain .
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.
I can't install 3rd party sources all of a sudden. I can load the Install or Cancel screen. Cancel works, but it won't let me install, what could be wrong? Obviously unknown sources is check.
Edit: it seems that the UI for install is broken. I can't active device administrator apps either, can't cancel or activate. I am 100% stock rooted.
roberto15359 said:
I can't install 3rd party sources all of a sudden. I can load the Install or Cancel screen. Cancel works, but it won't let me install, what could be wrong? Obviously unknown sources is check.
Edit: it seems that the UI for install is broken. I can't active device administrator apps either, can't cancel or activate. I am 100% stock rooted.
Click to expand...
Click to collapse
Try deactivating any screen related apps like LUX, or any screen filter apps
I agree with the previous post. I've experienced this exact issue in the past with other phones and it was frustrating until I finally figured out what was happening. I've had it happen with Lux and CF.lumen (though not with CF.lumen in quite some time). Temporarily disabling these apps should enable the install button.
dcdruck1117 said:
I agree with the previous post. I've experienced this exact issue in the past with other phones and it was frustrating until I finally figured out what was happening. I've had it happen with Lux and CF.lumen (though not with CF.lumen in quite some time). Temporarily disabling these apps should enable the install button.
Click to expand...
Click to collapse
Lol yupp, it was at night was using screen filter lmao!
Hi,
I have a OnePlus 3 which is about 7 months old now. I'm running stock 6.0.1 (OOS 3.2.7) with Xposed. ElementalX kernel and TWRP recovery (if that matters) ... I use Kernel Adiutor for a few misc tweaks (vibrator, LED, hostname) and AKT Profiles is set to Fusion Conservative - which limits GPU as well. I have been using various Xposed modules without any issue until the following happened.
I had installed Parallel Space - an app which allows dual WhatsApp capability. I started experiencing random soft reboots and shutdowns. So I uninstalled it. Then I cleared cache and ART cache. I also uninstalled a few apps that I had installed in the past month.
I am still experiencing reboots and I cannot pinpoint the cause. The reboots/shutdowns occur when the screen is off. Always when the screen is off.
I'm bad at reading logs, so can't figure out from the logcat either.
Anyone who can help me out, will be greatly appreciated! I will provide all logs as necessary.
[EDIT] Solution: Do not let any app make use of the proximity sensor to manipulate the screen. For example, apps which switch off the screen when flipped might be the culprit.
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
cl0g said:
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
Click to expand...
Click to collapse
Nope, no Magisk. Only Xposed.
Providing logs from logcat. Will provide anything else if required.
A few more logs containing fatal errors.
I thought the problem was solved by uninstalling this app called "Pixoff", but no, it still persists. Also, the LED is glowing orange, without any notification pending. During screen on as well as off.
Can you please flash stock ROM and check once if the same problem persists?
hrishikeshgramani said:
Can you please flash stock ROM and check once if the same problem persists?
Click to expand...
Click to collapse
That is what I'll have to do if changing settings or regular fixes don't work... But I don't want to jump to it right now because there's a lot of tweaks I'm running and they will be destroyed.
Also, it was running perfectly until last week. I have uninstalled all apps that I got in the last month. Cleared ART cache and normal cache. Haven't restored to factory settings yet.
I'm experimenting with disabling Xposed modules one by one, although I don't think it's a module problem - because I've had them since eternity.
What I have concluded is - I downloaded a rogue app from the Play Store which has left it's data and that is the cause of reboots... I might be wrong though.
Hence, I would really appreciate if someone would go through the logs and figure it out.
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
cl0g said:
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
Click to expand...
Click to collapse
Will do that next time, thanks!
Okay, so I figured this out. Proximity sensor is having issues. I had enabled "Proximity wake" in GravityBox and that was causing problems. Disabled it and Everything was fine as ever.
To verify that proximity sensor was at fault, I tried Pixoff's flip to Black screen feature - it uses the proximity sensor to figure whether device is in pocket or flipped... And yes, phone rebooted there too.
Phone is running fine as long as the sensor is used only during calls (to switch screen off)
But what I cannot understand is why this is happening in the first place! I mean, proximity sensors are supposed to be used in this manner only, right?
Nevertheless, if anyone wants to help, they are welcome. Otherwise my issue is solved.
Finally, I've been pulling my hair out trying to figure out why when I unlock/turn the phone on the screen wouldn't come on. I'd get feedback when I touch the screen but it would remain on a black screen I would have to hard reset the phone to get it back up only for it to do it again a few seconds later. We'll come to find out it was the Root "Magisk" that was the culprit so unfortunately I had to remove Magisk and I haven't a problem since. Just thought this may help someone who's having a similar issue.
I don't have this problem with Magisk and haven't heard of anyone else having it either. Could it be a Magisk module rather than Magisk itself?
JimSmith94 said:
I don't have this problem with Magisk and haven't heard of anyone else having it either. Could it be a Magisk module rather than Magisk itself?
Click to expand...
Click to collapse
IDK all I know is since I've uninstalled the Root I haven't any issues but once I flash Magisk to reinstall Root the problem returns
Wow I just had that same problem. Man i thought i was going crazy. I resorted to a factory reset but reinstalled Magisk. I haven't had the problem yet. So if it does happen again I'm uninstalling it until the nest update. But thanks for letting me know. Now does anyone know why after the 8.1 update it takes my screen a good second to turn on using power button and fingerprint scanner. I hate that delay.
mikepopo99 said:
Now does anyone know why after the 8.1 update it takes my screen a good second to turn on using power button and fingerprint scanner. I hate that delay.
Click to expand...
Click to collapse
I don't know why it happens, but I've read several articles that say that Google is aware and working on the issue.
Sent from my Pixel 2 XL using XDA Labs
So... I just upgraded my Pixel 2XL to Android 9.0, Pie.
I "dirty flashed" through TWRP, re-installed TWRP, installed ElementalX Kernel, and then Magisk.
Everything was working fine, but I missed the custom column count that I had for 8.1, so in Magisk I installed "Persistent Quick Settings Tiles for Oreo", and that only changed the "minimized" QuickLaunch, and set it statically to 10. I decided I didn't like it, and deactivated and removed the module via Magisk. The problem is, now my minimized Quick Launch bar has 10 icons across, and I couldn't get it back to normal. After that I installed "Shortcutter Quick Settings, Sidebar & Shortcut's" from the Play store, which manually let me set the size to anything else (indicating it's experimental, etc.), so I set it to 8, which is awesome.
Now for the problem.
Today, when I woke up, the minimized Quick Launch Tiles are completely blank. They function, because the last one is screen rotation, and if I tap the empty space it toggles the setting, but it's completely blank all the way across. I took a screenshot that I can post later.
Any idea on how to remedy this? I've tried rebooting, and changing with Shortcutter to a different value, I even tried re-flashing Pie over my existing installation, but no dice... I'd really like the functionality back, and ideally I'd REALLY like to not have to factory reset.
Here is the screenshot...
Sorry to revieve a year+ old thread, but this just happened to me on my Pixel XL. Was there any solution you found to correct it? I plan to update from 9.0 to 10 tonight, but have the fears it wont fix it as well.
jsylvia007 said:
So... I just upgraded my Pixel 2XL to Android 9.0, Pie.
I "dirty flashed" through TWRP, re-installed TWRP, installed ElementalX Kernel, and then Magisk.
Everything was working fine, but I missed the custom column count that I had for 8.1, so in Magisk I installed "Persistent Quick Settings Tiles for Oreo", and that only changed the "minimized" QuickLaunch, and set it statically to 10. I decided I didn't like it, and deactivated and removed the module via Magisk. The problem is, now my minimized Quick Launch bar has 10 icons across, and I couldn't get it back to normal. After that I installed "Shortcutter Quick Settings, Sidebar & Shortcut's" from the Play store, which manually let me set the size to anything else (indicating it's experimental, etc.), so I set it to 8, which is awesome.
Now for the problem.
Today, when I woke up, the minimized Quick Launch Tiles are completely blank. They function, because the last one is screen rotation, and if I tap the empty space it toggles the setting, but it's completely blank all the way across. I took a screenshot that I can post later.
Any idea on how to remedy this? I've tried rebooting, and changing with Shortcutter to a different value, I even tried re-flashing Pie over my existing installation, but no dice... I'd really like the functionality back, and ideally I'd REALLY like to not have to factory reset.
Click to expand...
Click to collapse
Salithox said:
Sorry to revieve a year+ old thread, but this just happened to me on my Pixel XL. Was there any solution you found to correct it? I plan to update from 9.0 to 10 tonight, but have the fears it wont fix it as well.
Click to expand...
Click to collapse
So... I did solve this issue, and for the life of me I can't remember what I did. I think I had to mess with substratum. I wish I could be of more help. For what it's worth, I upgraded my Pixel 2XL to 10 and haven't seen any issues.
Are you rooted / with substratum, etc?
Thanks for your reply. I am rooted (Magisk) but I don't use substratum. I use the swift installer. Im still going to update. I just wish I knew what the cause of this was.
jsylvia007 said:
So... I did solve this issue, and for the life of me I can't remember what I did. I think I had to mess with substratum. I wish I could be of more help. For what it's worth, I upgraded my Pixel 2XL to 10 and haven't seen any issues.
Are you rooted / with substratum, etc?
Click to expand...
Click to collapse
Salithox said:
Thanks for your reply. I am rooted (Magisk) but I don't use substratum. I use the swift installer. Im still going to update. I just wish I knew what the cause of this was.
Click to expand...
Click to collapse
I know this isn't going to be helpful, but I do remember that the solution was odd. I'm pretty sure that it wasn't related to anything that would make sense with the quick launch icons. I remember it being some odd piece of software that I was using and I removed it, and everything went back to normal. Maybe that jobs your memory?
I was wondering if it was an app that updated today. But i ruled it out as to why would that cause it ya know. But if you recall it being odd. I'll start there and see what happens.
jsylvia007 said:
I know this isn't going to be helpful, but I do remember that the solution was odd. I'm pretty sure that it wasn't related to anything that would make sense with the quick launch icons. I remember it being some odd piece of software that I was using and I removed it, and everything went back to normal. Maybe that jobs your memory?
Click to expand...
Click to collapse
I remember it being something that I would have assumed was completely unrelated.