Related
Moto X, 4.2.2 stock, rooted
When receiving a an email, message, or whatever (e.g., Gmail, snapchat, kakaotalk, google voice), the active notification appears as normal (vibrate/sound + screen display), but then the phone repeatedly displays the notification until it's unlocked. I do want the initial notification, but just the one. After the initial notification, further notif. only display the screen (no sound/vibrate).
When there isn't a notification, it doesn't display the clock over and over again as if I'm picking it up, so it's not like it's being moved around or something.
It did not used to do this, but I'm not sure exactly what setting/app/whatever would have caused this.
'Active notifications' has an option to disable certain apps or turn off completely, but there are no 'repeat' or 'lockscreen' settings located there, or in individual apps.
When I googled/searched for the issue (key words: active, notifications, repeat, stop, android, alert), I found these related posts, which seem to describe what I'm experiencing (albeit on different phones). Edit: ah, I can't post links yet, if you would like to look at them, please google the parts-of-the-url below
s4-active-message-notification-doesnt-stop-coming-up-lock-screen
android-kit-kat-moto-x-repeated-notifications-for-the-same-email
Has anyone else had this problem? What settings, if any, can I check for to disable these unwanted (repeated) notifications or how else might I go about it?
This isn't a bug or an issue, it's a feature. It's something called "breathing" notifications.
Every so often, the phone will give you the notification again just to be sure you saw it the first time. There is no way to remove or alter this feature through Active Display's settings.
If you are looking for an equivalent to Active Display, a good one (and the only one I know of) is DynamicNotifications by GreatBytes.
Have you tried swiping the notification to the side? That should dismiss it.
Sent from my XT1053 using Tapatalk
It seemed to me it wasn't normal behavior, as I don't remember it happening when I first got the device, but if you say it's intended, I'll go with that.
DarkWolffe: you say "every so often". The notifications are appearing every 5 seconds or so. Is this inline with what your own experience? If I can't change that interval from the native settings, might the app you linked be able to? It seems that DynamicNotifications is made for devices that don't already have Active Notifications. (perhaps I'm supposed to disable AN and only use DN?) Thank you for the link, though, I'll check it out.
scottjb: Ah, I figured that out sometime after making this post, but thank you for that tip. It's useful when I may actually see the phone, but when I'm away from the phone or sleeping, for example, I'd prefer it not to behave that way. I realize it's an AMOLED screen, so the battery really shouldn't be affected too much, but it doesn't feel right to have it turn on over and over again so often.
Knowing they're called "breathing notifications" has allowed me to better search for related topics. It seems that turning the phone over or putting it in a pocket will stop the breathing. I'd still prefer if I could change the interval somehow, but I'm satisfied to have figured most of how it works out.
The interval of the notifications seems to change over time. When you first get a text message etc it seems to flash the notifications more often, after some time I believe it slows down a little. You can have the feature disabled at night, my ringer is silent from midnight to 9 am and my active notifications are disabled from 1 to 7 am. When disabled at night it only stops it from displaying on its own, if you move the phone it will still display the clock and any notifications.
LG Pulse with KitKat 4.4.2 same issue
I don't have a Moto X, I have the LG Pulse from Virgin Mobile Custom. My notifications do that, too! I have KitKat 4.4.2. I have never experienced this and I certainly would NOT make it a default nor intended action. Mine start out at the first notification + sounds, then 10 seconds later, 15 seconds later, 20 sec, 25 sec, etc. It is very annoying and there is no option in the system settings nor individual app settings to stop that behavior. I may just have to turn off notification sounds as this is ridiculous.
You can try setting the "sleep at night" option, and adjust the time to be on all the time (1am to 12am).
I believe this setting is supposed to suppress the breathing notifications. Though, it won't stop it from showing if you move the phone around... I know this cause my phone charges on my bed at night and when I roll around, it triggers AD, even though I have sleep mode on.
Hope it helps!
tapa'd on my moto x
Damn Tapatalk, won't let me edit..
tapa'd on my moto x
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Wife has had her phone for a few days now, and only has a few complaints. I told her about you all and she wanted me to ask this:
She is only getting notifications part of the time. She is getting nothing after 2:00am. When she starts using her phone in the morning, all of the notifications start flooding in. Is there any setting that is responsible for that? I took a cursory glance at her phone and couldn't find anything, but might not have looked in the right place. This phone is so much more advanced that my Note 4.
usmaak said:
Wife has had her phone for a few days now, and only has a few complaints. I told her about you all and she wanted me to ask this:
She is only getting notifications part of the time. She is getting nothing after 2:00am. When she starts using her phone in the morning, all of the notifications start flooding in. Is there any setting that is responsible for that? I took a cursory glance at her phone and couldn't find anything, but might not have looked in the right place. This phone is so much more advanced that my Note 4.
Click to expand...
Click to collapse
Yes. At least in my case, I have Do Not Disturb set up between midnight and 0600. It's a button on the notification slide, but the actual setting menu has time you can manually enter.
Could be other stuff but try that first.
Sent from my SM-N950U using Tapatalk
Thanks. I just checked her phone and do not disturb is disabled. Must be something else.
it is the app battery optimization. go into settings and turn off all the apps you want notifications for.
it's been an issue on the note 8, this won't fix it 100% but at least you get some instead of none.
Too late, nevermind!
Reading this https://dontkillmyapp.com/oneplus I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
For instance, I've been using for several years this app, Stay Alive: https://play.google.com/store/apps/details?id=com.synetics.stay.alive
It gives you the option of having the screen not turning itself off when charging. It's crucial in the car, where I have a dock mounted and use the phone for navigation, music playback, etc.
On my previous Nexus 6P the app worked flawlessly. With 6T sometimes the screen turns off and then it turn itself on once more, as if the process got killed and then restarted.
I have the "don't optimize" option activated for Stay Alive.
There are other strange behaviours I'm seeing, with Tasker for instance. And the nagging feeling that they might depend on background process handling at the OS level.
I recently did turn off Battery/Battery Optimisation/Advanced Optimisation/Deep Optimisation and Sleep standby optimisation, hoping to get better results. I still haven't reached a conclusion about it.
I have to say that it's pretty annoying to have the phone decide for you what should be happening for apps. For instance, I had Firefox in the "Don't optimize" category but it still had problems with opening new pages after a while. Turning off the above two options seems to have cured the problem but if that is needed I wonder what the heck "Don't optimise" mean for OnePlus.
I hope to get to the bottom of this as, quite frankly, not having the phone "act on his own" behind the scenes is exactly why I chose Android as my OS.
gorman42 said:
Reading this https://dontkillmyapp.com/oneplus I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
For instance, I've been using for several years this app, Stay Alive: https://play.google.com/store/apps/details?id=com.synetics.stay.alive
It gives you the option of having the screen not turning itself off when charging. It's crucial in the car, where I have a dock mounted and use the phone for navigation, music playback, etc.
On my previous Nexus 6P the app worked flawlessly. With 6T sometimes the screen turns off and then it turn itself on once more, as if the process got killed and then restarted.
I have the "don't optimize" option activated for Stay Alive.
There are other strange behaviours I'm seeing, with Tasker for instance. And the nagging feeling that they might depend on background process handling at the OS level.
I recently did turn off Battery/Battery Optimisation/Advanced Optimisation/Deep Optimisation and Sleep standby optimisation, hoping to get better results. I still haven't reached a conclusion about it.
I have to say that it's pretty annoying to have the phone decides for you what should be happening for apps. For instance, I had Firefox in the "Don't optimize" category but it still had problems with opening new pages after a while. Turning off the above two options seems to have cured the problem but if that is needed I wonder what the heck "Don't optimise" mean for OnePlus.
I hope to get to the bottom of this as, quite frankly, not having the phone "act on his own" behind the scenes is exactly why I chose Android as my OS.
Click to expand...
Click to collapse
Thank you for this.
I've been feeling stupid having all these issues of pass getting killed in the background.
For me proper working phone is more important than battery life. I can easily get one whole day 6AM-11PM with around 30% battery left.
I would be ok if the apps won't get killed and I have say, 10% battery left at the end of the day.
I also don't understand this, it's what I really dislike about the OnePlus phones. In earlier Android versions it was always adviced not to use app killers because the Android OS knows best when to kill an app. Now OnePlus is doing exactly this, and then call it an optimization... [emoji848]
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?
rmaathuis said:
I also don't understand this, it's what I really dislike about the OnePlus phones. In earlier Android versions it was always adviced not to use app killers because the Android OS knows best when to kill an app. Now OnePlus is doing exactly this, and then call it an optimization... [emoji848]
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?
Click to expand...
Click to collapse
I want to say you're right but it's not only OnePlus that has too aggressive background killing. Google put optimization into Android a couple of years ago and they can't seem to hit a perfect medium between both. I'm sick of switching apps and then going back into an app a couple of minutes later to just have to start at the top of the feed again. It's annoying and it's happened with my 6t, Moto z, Droid turbo, lg g4, and my Galaxy s6 when they were all in their "prime". I think it boils down to Google ultimately
Turn off adaptive battery and on your apps you absolutely want untouched selectDon't optimize under battery > battery optimizations. After doing that I have what is consider a normal experience.
rmaathuis said:
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?
Click to expand...
Click to collapse
Yes, I am. But the screen dims. It doesn't turn off but it dims. For in car navigation that is clearly undesired.
I wonder whether rooting would give me back the control I need through some third party modification...
Aridon said:
Turn off adaptive battery and on your apps you absolutely want untouched selectDon't optimize under battery > battery optimizations. After doing that I have what is consider a normal experience.
Click to expand...
Click to collapse
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.
Whats solitions.
İ open accebility settings for any app and closed automatical..
Whyy
I'm sorry for my bad english
gorman42 said:
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.
Click to expand...
Click to collapse
You find solitions ?
I'm sorry for my bad english
gorman42 said:
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.
Click to expand...
Click to collapse
What most of the times work for for me is open the app, then go to recent app management, click on the 3 dots in the upper right corner above the app and choose lock.
And thanks for the tip of this app, because of company policy "stay awake" was disabled on my device and this app overrides it (Earlier I tried 2 or 3 similar apps but they didn't work, this one does).
gorman42 said:
I wonder whether rooting would give me back the control I need through some third party modification...
Click to expand...
Click to collapse
You really shouldn't have to modify your phone to, by chance, fix what OnePlus did (same could be said about other OEMs too, but that's besides the point right now). OnePlus needs to fix this issue, which has been an ongoing thing in their ROMs for over two years.
It's a shame that it takes a few app devs getting bad reviews on their apps to come up with a website pointing out the offenders of aggressive app management, with OnePlus being number 2 on the list for this issue to pick up traction, despite numerous users reporting about it on their forum and via in-app feedback for so long.
I said it before, and I'll say it again: Compared to OxygenOS on the 3T, OxygenOS nowadays has become so nice to use on the 6T that I don't have a need to root anymore. It's just this issue that really hampers it.
I fell in love with OnePlus when I bought my very first OnePlus phone, the OnePlus 3T. I've since then owned the OnePlus 5T and 6T. Unfortunately I've been disappointed with both because of this specific issue. If they don't resolve this issue within the lifetime of my 6T I feel obligated to start looking for something other than a OnePlus phone next Such a shame, as I love everything else about OnePlus and OxygenOS.
While investigating this I stumbled upon a setting in Developer Options.
Here’s the description and explanation: https://www.techrepublic.com/article/how-to-use-android-pie-standby-apps/
Problem is, with 6T all apps are stuck to ACTIVE status, you can’t modify their status. I guess this could point to OnePlus messing with regular Android power management.
gorman42 said:
While investigating this I stumbled upon a setting in Developer Options.
Here’s the description and explanation: https://www.techrepublic.com/article/how-to-use-android-pie-standby-apps/
Problem is, with 6T all apps are stuck to ACTIVE status, you can’t modify their status. I guess this could point to OnePlus messing with regular Android power management.
Click to expand...
Click to collapse
Are you sure you can't modify the settings, I've tried it and let's me change as per the link you posted?
I agree with you guys the app management is pretty aggressive.
wilpang said:
Are you sure you can't modify the settings, I've tried it and let's me change as per the link you posted?
I agree with you guys the app management is pretty aggressive.
Click to expand...
Click to collapse
Yeah, I tried before writing here.
It happens when you disable Adaptive Battery. If Adaptive Battery is enabled, those settings are active.
I have the same issues with several apps (Tasker, Gravity Screen, Whatsapo (Web)...). The apps was running perfectly on my old lg g4 but on the OPO 6T they gets killed too often. Also disabled adaptive Battery and set those apps to dont optimize. But this doesnt helps....
In previous OOS on the 5T there was an setting for background apps count in developer options, this is sadly gone on our 6T. Is there a way to use this option also when removed from dev options?
(maybe editing some files).
Thx
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Yes this is very unfortunate.. sometimes I even miss calls and they straight to voicemail
gorman42 said:
Reading this I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
[Snapped]
Click to expand...
Click to collapse
Yes, it is a problem for me. Never had a phone with such aggressive battery management. It even periodically kills my wifi for no reason.
There are 3 settings under Settings > Battery:
1. Battery Saver
2. Battery optimization
3. Adaptive Battery
I have been able to get a somewhat 'normal' experience after turning all 3 options off for Whatsapp, Tasker, etc... For some programs, it seems that it needs to be started, and left running without closing the program in 'Recentd's..
I am rooted and use Greenify to close programs that I want killed when in the background..
@gorman42
Why do you need this staying-alive app?
Google Maps and Waze already make the device's screen stay awake while navigating...
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.