So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...
Okay, got it. T'was a problem with the opengapps. I used to flash mini. I flashed nano and everything's good now...
Nope. Not working.
Come on, you guys...52 views and not one person answered?
Looks like you've tried almost all possible things. is all sensor detection is turned off? such as pocket detection hand wave? maybe try turning of those. also the ambient display too.
if it still doesn't works then i think we might have this issue on all pie roms such as we had screencast issue on all pie roms.
livingongh325 said:
Nope. Not working.
Come on, you guys...52 views and not one person answered?
Click to expand...
Click to collapse
Maybe there is no solution... xD
I've experienced the same issue for a long time on the LOS 15.1 build where System usage is high despite long Phone Idle time and low usage.
The battery report actually does not make sense, but my battery life is certainly not what it should be compared to what some other users are getting.
It would be great if an expert can provide a solution on the deep sleep problem to extend battery life with these custom ROM's or a way to identify the culprit that keeps my phone awake.
metelhammer said:
Looks like you've tried almost all possible things. is all sensor detection is turned off? such as pocket detection hand wave? maybe try turning of those. also the ambient display too.
if it still doesn't works then i think we might have this issue on all pie roms such as we had screencast issue on all pie roms.
Click to expand...
Click to collapse
Yes.
I turned them off on the outright.
Which ROM are you using by the way?
livingongh325 said:
Yes.
I turned them off on the outright.
Which ROM are you using by the way?
Click to expand...
Click to collapse
I am using Havoc OS 2.6 20190609 build (which is latest one as i am writing). and i must say battery backup is great on stock kernel.
metelhammer said:
I am using Havoc OS 2.6 20190609 build (which is latest one as i am writing). and i must say battery backup is great on stock kernel.
Click to expand...
Click to collapse
Have you installed viper4android?
livingongh325 said:
Have you installed viper4android?
Click to expand...
Click to collapse
No, i haven't.
livingongh325 said:
So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...
Click to expand...
Click to collapse
Check if "pocket mode" is on, or "double tap to wake" or things like that, some months ago I lost one week trying to figure out, but was just the "pocket mode".
livingongh325 said:
So, I've tried all Pie ROMs. PixelExperience to Syberia and Havoc OS. None of them enter deep sleep. I've tried everything posted wherever I can find on the internet:
1. Change ROM
2. Change CPU governor.
3. Change Kernel.
4. Make changes to those values which govern the time it takes for the phone to enter deep sleep.
Nothing worked!
Any suggestions? I shifted to MIUI 10, which DOES enter deep sleep. But I don't want MIUI, not right now, at least...
Click to expand...
Click to collapse
Maybe you can use these apps to track what application(s) make your phone awakes: BetterBatteryStats, Wakelock Detector or Simple System Monitor.
I ever used TWRP 3.2.1 + Pixel Experience 8.1 (Oreo), and my phone never entered deep sleep state. I moved to MIUI 9.2.4 and the state was back to normal.
Now I use OrangeFox 9 recovery + Pixel Experience 9 (Pie) and the phone can sleep like a baby. It's been 2 weeks and still acts normally. Love it!
CalveinX said:
Check if "pocket mode" is on, or "double tap to wake" or things like that, some months ago I lost one week trying to figure out, but was just the "pocket mode".
Click to expand...
Click to collapse
Where do you find the "pocket mode" setting ?
Xiaomi Warrior said:
Where do you find the "pocket mode" setting ?
Click to expand...
Click to collapse
I am using Havoc and had the same problems until I decativated everything that reads motion or proximity sensors. Now I can go 4 days without charge.
The most options are in the havoc menue in "Inactivity screen -> Ambient Options" (I am not completly sure about the english labels, as I am using an other language.) "Pocket mode" is the last one in the list, but I have deactivated everything there.
theBoatman said:
I am using Havoc and had the same problems until I decativated everything that reads motion or proximity sensors. Now I can go 4 days without charge.
The most options are in the havoc menue in "Inactivity screen -> Ambient Options" (I am not completly sure about the english labels, as I am using an other language.) "Pocket mode" is the last one in the list, but I have deactivated everything there.
Click to expand...
Click to collapse
Pocket Mode for LOS15.1 it is under Settings -> Display -> Advanced -> Ambient Display or Settings -> Battery -> Ambient Display
I have turned all of this unnecessary trash off.
My phone still drains about 8-10% during night while in airplane mode which I do not think is normal.
I have even gone as far as disabling "Keep Awake" for installed apps under Privacy Guard.
Related
Hello guys, first of all thanks to xda for making me redescover and love my phone! =)
My problem is that i'm using the sleep time app to wake up in the morning. This app uses the accelerometer of the phone to decide if u're in a deep rem phase or not and wakes you up when you're not. Until i was using the samsung 4.1.2 rom the app worked ok, but on other roms like all the cyanogenmod roms (tried all of them, 10.1, 10.2, 11), pacman, paranoid, carbon, ecc. the app stops receiving data from the accelerometer sensor when the screen goes off and it becomes a simple alarm clock. The only workaround that i found until now, is to enable the "keep the screen on while loading" in the developer settings. Is there any way to solve this problem, maybe to find out why in the samsung stock rom it's working and put that in the other roms.
Thanks in advance to everyone and sorry if i made any mistake in english, it's not my native language.
ps. A special thanks to all the developers here (i owe all of you a beer =)), love all the roms i found here, and keep up the awesome work:good:
Accelerometr works fine while screen is off. I am using sleep as android - similar sleep monitoring alarm as you, and it works fine while screen os off. I was using it on CM 10.1, 10.2 and now 11 by maclaw.
Check app settings. My app have sth like 'monitoring while screen is off' and when I run this option it checks if accelerometr works with screen off for like 2 minutes. Then it shows 'supported' or 'not supported' as test result. Mine said 'supported' and I can see nice graphs of how well I slept during that night when I wake up in the morning
Sent from my SGS Adv. using xda-developers app.
i guess the problem is the app then. thanks for the answer :good:, i'm gonna try your alarm clock
Were you able to keep getting the accelerometer values after the screen goes off? I have an app that loses the accelerometer values about 2 minutes after the screen goes off. Is there a way to keep getting the values after screen is off?
Thanks,
Norm
NormR1 said:
We're you able to keep getting the accelerometer values after the screen goes off? I have an app that loses the accelerometer values about 2 minutes after the screen goes off. Is there a way to keep getting the values after screen is off?
Thanks,
Norm
Click to expand...
Click to collapse
Maybe set deepsleep to 1. You need to be rooted with CoCore kernel or on some of CM based.
echo 1 > /d/cpuidle/deepest_state
But it will drain your battery faster. And I am not 100% sure if it will work. Reboot resets value to 3.
If it is working with 1, try 2 too.
shut_down said:
Maybe set deepsleep to 1. You need to be rooted with CoCore kernel or on some of CM based.
echo 1 > /d/cpuidle/deepest_state
But it will drain your battery faster. And I am not 100% sure if it will work. Reboot resets value to 3.
If it is working with 1, try 2 too.
Click to expand...
Click to collapse
Thanks for the response.
I don't want to "root" my system. There is another app: Shake that is able to do what I want on my system. I was hoping to be able to do what Shake does, but with less battery drain.
Norm
I have a Moto G6, Android 8.1, rooted, and I'm having an annoying issue I haven't been able to Google the solution to. When my screen goes to sleep the audio stops almost right away. This is true for both streaming music and downloaded content (podcasts, audiobooks), so I think it's some battery saving setting I can't find rather than network related. Let me know if any of you have solved this issue or have suggestions. Thanks!
slacktheplanet said:
I have a Moto G6, Android 8.1, rooted, and I'm having an annoying issue I haven't been able to Google the solution to. When my screen goes to sleep the audio stops almost right away. This is true for both streaming music and downloaded content (podcasts, audiobooks), so I think it's some battery saving setting I can't find rather than network related. Let me know if any of you have solved this issue or have suggestions. Thanks!
Click to expand...
Click to collapse
Are you using Magisk? If so, try disabling it and listen to audio while the screen is off. If it doesn't stop, it's Magisk.
I had a similar issue on a Pie GSI where the audio would skip while the screen is off. I haven't used Magisk since.
Yeah, I'm using Magisk. Tried uninstalling it but the issue is still happening. After screen goes black audio is fine for about 30s then skips and stops. Not sure what else it could be...
slacktheplanet said:
Yeah, I'm using Magisk. Tried uninstalling it but the issue is still happening. After screen goes black audio is fine for about 30s then skips and stops. Not sure what else it could be...
Click to expand...
Click to collapse
Check in the specific apps setting under settings, apps, whichever app, and check to see if it says battery optimization. If it's optimized, try switching to not optimized[
Or if you have ambient display disabled, switch it on, worked for me
Starkiller2 said:
Check in the specific apps setting under settings, apps, whichever app, and check to see if it says battery optimization. If it's optimized, try switching to not optimized[
Or if you have ambient display disabled, switch it on, worked for me
Click to expand...
Click to collapse
I've got battery optimization turned off for the 3 apps I'm testing this with, but still having the same problem. I'm not finding "ambient display" in my settings (Android 8.1), but I went into "LiveDisplay" and I have a setting called "Display mode" that was set to "automatic." I switched this to "Off" and the problem went away! Thanks for your help.
slacktheplanet said:
I've got battery optimization turned off for the 3 apps I'm testing this with, but still having the same problem. I'm not finding "ambient display" in my settings (Android 8.1), but I went into "LiveDisplay" and I have a setting called "Display mode" that was set to "automatic." I switched this to "Off" and the problem went away! Thanks for your help.
Click to expand...
Click to collapse
I spoke too soon and the problem persists. Any other ideas what might be causing this? It stutters a bit and then goes silent right after the screen goes black. Real deal breaker for listening to podcasts and audiobooks on my long commute, so I'd appreciate any solution you all can think of. Thanks!
slacktheplanet said:
I spoke too soon and the problem persists. Any other ideas what might be causing this? It stutters a bit and then goes silent right after the screen goes black. Real deal breaker for listening to podcasts and audiobooks on my long commute, so I'd appreciate any solution you all can think of. Thanks!
Click to expand...
Click to collapse
It sounds like what was happening to me with YouTube. Every time my screen would go to sleep, it would start stuttering. I guess it was doze causing it and whitelisting it made it stop. I wonder if switching live display to on would be any different? What magisk modules are you using? I know GMS doze and sysconfig patcher will cause that, because YouTube is a Google app
Starkiller2 said:
It sounds like what was happening to me with YouTube. Every time my screen would go to sleep, it would start stuttering. I guess it was doze causing it and whitelisting it made it stop. I wonder if switching live display to on would be any different? What magisk modules are you using? I know GMS doze and sysconfig patcher will cause that, because YouTube is a Google app
Click to expand...
Click to collapse
I seem to have it resolved right now. I've got live display OFF and I exempted my 3 audio apps from battery optimization. I've completely uninstalled Magisk though, so I'm not sure if I'll cause the problem again when I re-root. Maybe I should go back to using SuperSU rather than Magisk (?)
slacktheplanet said:
I seem to have it resolved right now. I've got live display OFF and I exempted my 3 audio apps from battery optimization. I've completely uninstalled Magisk though, so I'm not sure if I'll cause the problem again when I re-root. Maybe I should go back to using SuperSU rather than Magisk (?)
Click to expand...
Click to collapse
Good luck using SuperSU on Oreo
madbat99 said:
Good luck using SuperSU on Oreo
Click to expand...
Click to collapse
Exposing my ignorance. I'll flash Magisk and hopefully my audio problem won't come back!
slacktheplanet said:
Exposing my ignorance. I'll flash Magisk and hopefully my audio problem won't come back!
Click to expand...
Click to collapse
It works in a few rare instances on Oreo. Definitely not pie. SuperSU has been dead and not updated for a long time now.
madbat99 said:
It works in a few rare instances on Oreo. Definitely not pie. SuperSU has been dead and not updated for a long time now.
Click to expand...
Click to collapse
This audio problem is back. I didn't change any settings. Live Display is off, audio apps are not optimized in terms of battery. All I did was reboot my phone. Was working fine. I can't figure out what I'm missing but it's a really annoying problem. Any ideas?
When you move the phone slightly the underdisplay fingerprint glows, can anybody tell me how to turn it off? I want it to goow only when I press on the phone, is this possible?
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
I'd you mean the fingerprint icon that shows up when you pick the phone up, you can't disable it currently.
Ahmad Shawawreh said:
When you move the phone slightly the underdisplay fingerprint glows, can anybody tell me how to turn it off? I want it to goow only when I press on the phone, is this possible?
Click to expand...
Click to collapse
RedWave31 said:
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
Click to expand...
Click to collapse
Mohammed779 said:
I'd you mean the fingerprint icon that shows up when you pick the phone up, you can't disable it currently.
Click to expand...
Click to collapse
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
Damn, i might flash this rom just for this feature, it's super annoying at night, and it keep activating the screen in my pocket.
Can you flash it over the global rom, or does it require a wipe? (probably..)
Gokh said:
Damn, i might flash this rom just for this feature, it's super annoying at night, and it keep activating the screen in my pocket.
Can you flash it over the global rom, or does it require a wipe? (probably..)
Click to expand...
Click to collapse
Hmm given the rom is different, I'd say you may run into issues. But with that said, worth a shot! If dirty flashing, perhaps wipe system and the caches, then flash rom and magisk (if rooting), and keep those fingers crossed!
Any issues then yeah do a clean install
RedWave31 said:
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
Click to expand...
Click to collapse
Does seem somewhat like this because if that and the ambient display is disabled, the fingerprint doesn't respond from screen off. But if that and/or ambient display is enabled, it works. But at least something has to be turned on keeping at least some part of the screen awake.
I chose to enable ambient but disable fingerprint icon because ambient goes around the whole screen giving me peace of mind from burn in unlike the icon
Sent from my Xiaomi MI 9 using XDA Labs
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
I'm running on the global room not the EU one
Would you recommend me installing the EU room?
I like everything about the phone, but if they would tweak the SOT usage
Ahmad Shawawreh said:
I'm running on the global room not the EU one
Would you recommend me installing the EU room?
I like everything about the phone, but if they would tweak the SOT usage
Click to expand...
Click to collapse
Yeah I recommend the weekly EU roms for sure. I've not tried the global ones, but this EU one is great, with weekly updates and great features. Definitely worth a try!
Check my battery thread on the Discussion area on XDA for my battery saving tips
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
Ohhh man, I have been looking to switch this annoying feature off for ages and you just showed me how to do it. Awesome and thank you
perryano said:
Ohhh man, I have been looking to switch this annoying feature off for ages and you just showed me how to do it. Awesome and thank you
Click to expand...
Click to collapse
You're welcome!
Alot of phones are getting this. Anyone know if this will or is being worked on for our 3t?
cell2011 said:
Alot of phones are getting this. Anyone know if this will or is being worked on for our 3t?
Click to expand...
Click to collapse
For Android 9 and 10 we started seeing custom ROMs based on LineageOS showing up in November/December and stable, daily use versions a couple of months after that.
I expect Android 11 will follow a similar timeline.
Sent from my OnePlus 3T using XDA Labs
Luckily it's quicker this time, 3-4 alpha / beta releases are already there and basic stuff is working pretty good on them.
cell2011 said:
Alot of phones are getting this. Anyone know if this will or is being worked on for our 3t?
Click to expand...
Click to collapse
Arrow OS works fine
I like android 11, I try the Arrow OS and it's amazing, but I'm getting huge battery drain, in android 10 I'm getting 4 to 5 hours SOT, in android 11 it's like 2 hours, the phone is warm all the time, I did try some gapps, NIKGapps, FlameGapps, Bitgapps, Stock, full, basic, core, all of them, but its the same. Need to wait a bit longer so they fix that.
MrJohnOliver said:
I like android 11, I try the Arrow OS and it's amazing, but I'm getting huge battery drain, in android 10 I'm getting 4 to 5 hours SOT, in android 11 it's like 2 hours, the phone is warm all the time, I did try some gapps, NIKGapps, FlameGapps, Bitgapps, Stock, full, basic, core, all of them, but its the same. Need to wait a bit longer so they fix that.
Click to expand...
Click to collapse
Yip, been experiencing the same. Tried all 11 ROMs. As soon as gapps (play services) get installed, sensor_SMD wakelock kicks in permanently. Deep sleep almost never happens. Tried disabling all location options; no go.
raz123 said:
Yip, been experiencing the same. Tried all 11 ROMs. As soon as gapps (play services) get installed, sensor_SMD wakelock kicks in permanently. Deep sleep almost never happens. Tried disabling all location options; no go.
Click to expand...
Click to collapse
I was trying to figure out that. I installed bbs and the sensor_SMD is on all the time, and getting like 1 % deep sleep. Sometimes less than that. What rom are you using now?
MrJohnOliver said:
I was trying to figure out that. I installed bbs and the sensor_SMD is on all the time, and getting like 1 % deep sleep. Sometimes less than that. What rom are you using now?
Click to expand...
Click to collapse
News.
Google play services is the issue.
Fix
0. Rooted device (prerequisite)
1. Install App Manager (from F-Droid store)
2. Open the app and search for Google play services
3. Long press on it to select it, then press on the 3 dots at the bottom right of the screen, and press on Disable Background
4. Reboot device
5. Done
Optional step (to have the phone go into deep sleep faster):
1. Install ForceDoze (from F-Droid store)
2. Open ForceDoze and activate service
3. Open ForceDoze settings and tick "Disable Motion Sensing for Doze"
4. Done
Note: these changes may substantially delay push notifications, but at least deep sleep reliably works.
Edit: "fix" randomly stops working. More research needed.
After installing Naptime by Franco, deep sleep issue is resolved. Posting my settings if need be.
https://imgur.com/a/o0KKAo5
raz123 said:
News.
Google play services is the issue.
Fix
0. Rooted device (prerequisite)
1. Install App Manager (from F-Droid store)
2. Open the app and search for Google play services
3. Long press on it to select it, then press on the 3 dots at the bottom right of the screen, and press on Disable Background
4. Reboot device
5. Done
Optional step (to have the phone go into deep sleep faster):
1. Install ForceDoze (from F-Droid store)
2. Open ForceDoze and activate service
3. Open ForceDoze settings and tick "Disable Motion Sensing for Doze"
4. Done
Note: these changes may substantially delay push notifications, but at least deep sleep reliably works.
Edit: "fix" randomly stops working. More research needed.
Click to expand...
Click to collapse
You can try this:
Turn off all power management except the screen power setting if any. All buckets should show as active.
Google Backup Transport, Backup Framework package block.
Goggle Play Services firewall block when not needed.
Clear data of all 3 as needed.
Use a firewall to block the Android Services as well. Karma Firewall uses almost no battery and runs well.
Adaptive power management never worked for me in Pie and it took a lot of playing around on my AT&T Note 10+ Pie variant to tone it down into a cool running machine. It's staying on Pie.
I have zero confidence in 10 at this point... and afraid 11 will be more of the same scoped storage nonsense along with other issues.
raz123 said:
Yip, been experiencing the same. Tried all 11 ROMs. As soon as gapps (play services) get installed, sensor_SMD wakelock kicks in permanently. Deep sleep almost never happens. Tried disabling all location options; no go.
Click to expand...
Click to collapse
MrJohnOliver said:
I was trying to figure out that. I installed bbs and the sensor_SMD is on all the time, and getting like 1 % deep sleep. Sometimes less than that. What rom are you using now?
Click to expand...
Click to collapse
I've found that the sensor_SMD wake lock only starts after I've fully charged the phone. And a quick restart stops it.
So now I recharge the phone, reboot, and I'm good to go till the next recharge.
Also, a partial charge doesn't trigger the sensor_SMD wake lock for me.
I'm using Arrow 11 and Open Gapps.
Update: while a reboot after recharging works well, I've also found that the sensor_SMD wake lock can kick in all of its own. I've been using the phone for about 4 hours and just now I'm seeing the sensor_SMD wake lock again. Go figure!
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
stuatrb04 said:
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
Click to expand...
Click to collapse
chinese version?
brunolongo said:
chinese version?
Click to expand...
Click to collapse
nah uk
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
blackhawk said:
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
Click to expand...
Click to collapse
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
stuatrb04 said:
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
Click to expand...
Click to collapse
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
blackhawk said:
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
Click to expand...
Click to collapse
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
stuatrb04 said:
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
Click to expand...
Click to collapse
Feels good when you track it down.
I've tracked (and caused, oops) a few bizarre ones down
Stock Androids are generally very robust platforms.
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
dtvenom said:
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
Click to expand...
Click to collapse
Welcome to XDA.
Tap on works fine for me and uses less battery. Constantly looking at the time when you should be sleeping is counterproductive and a bad habit to get into. For me the novelty wore off after about a year as I find it now annoying.
It's the same on OnePlus 8T, Oxygen OS 13. At least after midnight, maybe earlier, the screen turns black with AOD always on after roughly 25-30 minutes if non use. Double tap or more activates it again.
It's broken for people who is working nights and/or is awake and active after midnight.
There's gotta be a setting fixing this through root or adb shell.