Several months ago, I started experiencing an annoying issue on my Nexus 6 running LOS 14.1 where the silent mode setting would get disabled on its own even when the "Until you turn this off" option was chosen. I had posted on the LOS subreddit as well as here on XDA about it multiple times and someone had stated that the maintainer for shamu was likely ignoring it because they were busy working on 15.1. So naturally, I was disappointed to find out after upgrading to the first LOS 15.1 release that the issue still persists.
What do I do? My phone's been doing this since January and I tried everything I could think of to fix it, including wiping the phone and reinstalling everything and even that did not work.
Here are some important things to note about my installation:
Running LOS 15.1 (upgraded from LOS 14.1)
Using the stock Open GApps package
Rooted with Magisk 16.0 (latest version at the time of this post)
(I'm going to tag @Elektroschmock since as far as I am aware, he's the person we have to thank for keeping our shamus alive and well and would therefore be most likely to able to help me out.)
I wasn't ignoring it, I just wasn't able to reproduce it.
If this really is a common problem then it is not specific to Nexus 6.
Elektroschmock said:
I wasn't ignoring it, I just wasn't able to reproduce it.
If this really is a common problem then it is not specific to Nexus 6.
Click to expand...
Click to collapse
Ah, alright. That's unfortunate. The thing that's frustrating about this is that I cannot find any reports from anyone else having this issue. Not just the Nexus 6, but for any phone.
David B. said:
Ah, alright. That's unfortunate. The thing that's frustrating about this is that I cannot find any reports from anyone else having this issue. Not just the Nexus 6, but for any phone.
Click to expand...
Click to collapse
In cases where you seem to be the only one affected, make a backup and try to do a clean install.
Elektroschmock said:
In cases where you seem to be the only one affected, make a backup and try to do a clean install.
Click to expand...
Click to collapse
I already tried that though. In fact I tried it multiple times. It keeps happening though.
David B. said:
I already tried that though. In fact I tried it multiple times. It keeps happening though.
Click to expand...
Click to collapse
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
Yes I have, and I am afraid that I did not find anything useful there. Even though you could not reproduce the issue, did the catlog that I posted on the LOS Jira help? (https://jira.lineageos.org/browse/BUGBASH-1373)
Even though that post applies to LOS 14.1, the issue is occurring in the same way in LOS 15.1.
It's also worth noting that I tried installing a fresh copy of LOS 14.1 to fix it, but when I upgraded to 15.1, I did not do a fresh install. Do you think it would be worth the effort to try it?
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
I had some time last night, so without waiting for a reply, I decided to do a fresh install and I am so glad I did. So far, silent mode has not disabled itself, and I am hoping this stays that way. Additionally, my phone's performance in general seems a lot better. I am not sure if it's in my head or not, but either way, I am satisfied. If the issue pops up again, I'll be sure to let you know so that we can keep looking for alternative solutions.
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
Last night I had some time, so I decided to do a full wipe and reinstall without waiting for a response. I am so glad I did. The issue appears to finally be resolved, as it has not happened yet, and on top of that, my phone feels like it's running faster. I am not sure if it actually is or if it's just a placebo, but either way, I am satisfied.
If the issue does end up returning, I will let you know so that we may continue looking for a way to stop it from happening.
David B. said:
Last night I had some time, so I decided to do a full wipe and reinstall without waiting for a response. I am so glad I did. The issue appears to finally be resolved, as it has not happened yet, and on top of that, my phone feels like it's running faster. I am not sure if it actually is or if it's just a placebo, but either way, I am satisfied.
If the issue does end up returning, I will let you know so that we may continue looking for a way to stop it from happening.
Click to expand...
Click to collapse
Thanks for the feedback.
If you have time can you provide feedback on jira when you think it has been solved?
Elektroschmock said:
Thanks for the feedback.
If you have time can you provide feedback on jira when you think it has been solved?
Click to expand...
Click to collapse
You're welcome! I posted this on the Jira submission. Is that good?
David B. said:
You're welcome! I posted this on the Jira submission. Is that good?
Click to expand...
Click to collapse
Yes thanks! I'll leave the ticked open a few more days and close it then.
We can reopen it anytime.
Elektroschmock said:
Yes thanks! I'll leave the ticked open a few more days and close it then.
We can reopen it anytime.
Click to expand...
Click to collapse
Alright, sounds good. Thank you for working so hard to keep my Nexus 6 up to date.
Related
You can get it here: http://get.cm/?device=quincytmo&type=RC
Seems stable. Everything working so far.
I guess I need to go check it out. I'm still on the latest monthly.
As far as I can tell, it is caught up with the nightlies as far as features go: Camera timer, stylus gestures, whatever else is new. Everything I've tested so far works, wifi tether, bluetooth etc,
Yeah, so far so good. It seems pretty stable and fluid. Haven't checked battery life. I noticed on the last nightly that it took longer to charge the battery.
Battery life here seems very good. Very smooth, not getting lagginess that was in a couple of nightlies.
Had a couple of instabilities with a couple of apps. Reinstalling them seems to have fixed the problem. Time will tell.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Going back to M3. Having too many instabilities, random reboots, lock ups.
srpanadero said:
Going back to M3. Having too many instabilities, random reboots, lock ups.
Click to expand...
Click to collapse
I was about to say that I haven't seen any bugs with this latest release, but then I thought for a second and remembered that I had a weird screen issue where my screen was flickering, and then went black until I restarted the phone. It only happened once, so I didn't think much of it. I expect a few bugs with any ROM no matter how stable/baked it is.
Here is a bug report for graphical issues. Now is the time to report any bugs that you see.
https://jira.cyanogenmod.org/browse/CYAN-1057
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Now there's an RC2. Trying it now.
fraughtsigewulf said:
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Click to expand...
Click to collapse
So then could you and anyone else who've seen the issue sign up and vote on the bug report here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1125
Either that or add your own comment and log if you have. Hopefully the devs will then see and fix the problem.
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
hogasswild said:
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
Click to expand...
Click to collapse
Now i'm getting freezes and reboots 5-6 times a day. Today I could hardly use my phone. And that was even after doing a full wipe this morning and reinstalling the latest nightly and Gapps. I think i'm gonna roll back to a version from a couple of months ago if I can find one and see if that helps.
I did go to that dev page that was suggested earlier in the thread and signed up and voted up this issue. I hope it gets the ball rolling.
I'm kinda disappointed. I know these are nightlies and aren't supported, but i'm really used to Cyanogenmod putting out solid builds, even for their nightlies. A few bugs I can deal with, but this is unusable.
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
error when installing
when I try to install the zip file I get this error "assert failed: getprop("ro.product.device)...." this is just the beginning the type is small and its hard to read- any suggestions? Some searches I've done say this error shows when the ROM is for the wrong phone, but don't see how that can be. I have the T-Mobile Galaxy Note for sure. Thanks for any help that I can get. Since it seems like T-Mobil is never going to upgrade OTA to Jelly Bean I really would like to get this ROM.
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod. Here is the links. http://get.cm/?device=quincytmo&type=snapshot
srpanadero said:
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod.
I was using Clockwork MOD. I will admit I'm a bit of a Newb with this custom recovery stuff. I went to install Goomanager on my phone, but when I reboot it reboots it into Clockwork MOD. So do I need to uninstall clockwork MOD somehow? I will try the other ROM you mentioned, but I think I had tried that one as well and got the same error. Of course this was using clockwork MOD.
Thanks,
John
Click to expand...
Click to collapse
This is the twrp page for this phone.
http://teamw.in/project/twrp2/113
It lists several ways to install it. Try them all, one will work.
srpanadero said:
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
Click to expand...
Click to collapse
So M3 is stable enough to use? I couldn't remember whether it was M2 or M3.
Yes M2 and M3 are stable enough for daily use. Actually any nightly from that time is good too. It wasn't until after M3 that things took a dive, and didn't get any better with RC1 and 2.
Only problem I'm aware of is a bug with the Bluetooth on off toggle that affects some. If it happens reboot or force close Bluetooth share.
Hi!
I've installed Maclaw 4.4.4 ROM and my phone always restarts.. Why?!
Ask Maclaw on his site.
Powered by CM11 M9 snapshot
please we could use some help
R_a_z_v_a_n said:
Ask Maclaw on his site.
Powered by CM11 M9 snapshot
Click to expand...
Click to collapse
I have the same problem as the op, but unfortunately maclaw hasn't got a forum. (they are setting up one but it isn't launched yet)
So i decided to ask here too, since you guys have knowledge about pretty much everything.
please, maybe you or anyone else could point out what the possible cause of this problem could be.
In my case, the phone restarts after a while, but only when the device is on battery, and when the screen is locked.
Everything works fine when it's on charger and/or unlocked.
(maybe this description defines the problem somewhat better)
Is this a common problem or does it have a well known cause?
Thanks in advance for your efforts.
beertjen said:
I have the same problem as the op, but unfortunately maclaw hasn't got a forum. (they are setting up one but it isn't launched yet)
So i decided to ask here too, since you guys have knowledge about pretty much everything.
please, maybe you or anyone else could point out what the possible cause of this problem could be.
In my case, the phone restarts after a while, but only when the device is on battery, and when the screen is locked.
Everything works fine when it's on charger and/or unlocked.
(maybe this description defines the problem somewhat better)
Is this a common problem or does it have a well known cause?
Thanks in advance for your efforts.
Click to expand...
Click to collapse
Try to ask here in comments.
Solution found!!
Gun22 said:
Hi!
I've installed Maclaw 4.4.4 ROM and my phone always restarts.. Why?!
Click to expand...
Click to collapse
Okay, with a little help i found an answer myself. This is for ppl struggling with the same problem: To prevent those random restarts, you only have to experiment with your energy profile and your minimum clockspeed. change your CPU.(at least this worked for me) By default, min. clock is set at 100MHz and energyprofile is balanced. you've got to change either ONE of these. (or both if you like) I had to bump clockspeed up to 200MHz(still pretty big underclock) or change profile to powersaver. Never got the restart problem after this change, nor a problem with the dialer or the youtube app. Maybe cpu governor could be a solution too, but this did the trick for me. To unlock those options, if you can't find'em, google "unclock cm11 developer options." once you have them unlocked, head to 'performance' and apply said changes.
Hope it helps for you too.
I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
jooniloh said:
I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
Click to expand...
Click to collapse
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
zz1049 said:
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
Click to expand...
Click to collapse
YES! YES! I never thought the laggy installs were related too! I didn't even get around to testing that because the SMS issue was frustrating me so much. The experimental version of xposed installer doesn't fix anything. I've just stuck my SIM in my note 3 for now until a fix is released.
Interesting thing. The guy on this thread has the same issue on as s5, but he says a kernel update fixed it . . .
EDIT:
The following threads all document similar, if not the same issues:
http://forum.xda-developers.com/xposed/xposed-touchwiz-stock-messaging-app-t2795905
http://forum.xda-developers.com/xposed/issues-xposed-n915p-sprint-galaxy-note-t2947850
http://forum.xda-developers.com/note-edge/help/n915p-cf-auto-root-fails-t2944539
http://forum.xda-developers.com/xposed/xposed-note-4-t2928864
Find a fix yet zz1049?
jooniloh said:
Find a fix yet zz1049?
Click to expand...
Click to collapse
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
zz1049 said:
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
Click to expand...
Click to collapse
ugh. well I guess whatever works. I was rather dependent on greenify's xposed features and wanam. I hope someone figures out a fix soon.
try this guys
Just disable secure storage in Wanam this fixes the lag as others mentioned
Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.
http://besttopics.net/link/189924_fix-how-to-fix-xposed-framework-lag-on-note-4
Having a small issue with call quality, had it on every version of OOS yet. People I call or who call me complain that either a) my voice quality is not great, or b) they can hear an echo of themselves for the first 30-60 seconds or so, then it goes away. This is on AT&T in the US. Anyone else seeing anything like this, or is it likely a hardware problem I should contact OP about?
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
bird333 said:
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
Click to expand...
Click to collapse
Do you have file or url by any chance.. have been trying to find it
bird333 said:
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
Click to expand...
Click to collapse
I am completely stock right now, can it be flashed through stock recovery?
ram4ufriends said:
Do you have file or url by any chance.. have been trying to find it
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70097082&postcount=96
Again I don't know if this will work for a stock rom. If you try it report back.
TXRangerXDA said:
I am completely stock right now, can it be flashed through stock recovery?
Click to expand...
Click to collapse
did you try to flash the zip file on stock ROM? is it working?
Honestly don't remember. I ended up sending it back to OP, they sent it back saying they couldn't reproduce the issue. A month later I sent it back again, because it was really unusable for me. No one could hear me on most calls. Voip worked fine. They still couldn't reproduce it, but refunded the cost of the phone to me. Bought a Samsung s8+ a few months later.
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(