So I have set my power saving mode to come on at 30% and for it to disable everything except wifi. The problem is that after I charge my phone back up, those settings remain disabled even though power saving mode is turned off, so I have to manually enable them each time. Is there a way around this?
apollero said:
So I have set my power saving mode to come on at 30% and for it to disable everything except wifi. The problem is that after I charge my phone back up, those settings remain disabled even though power saving mode is turned off, so I have to manually enable them each time. Is there a way around this?
Click to expand...
Click to collapse
What ROM and kernel is on your phone?
If you enable user specified power saving with your customized settings (30% battery => shut down everything accept wifi), and you did not disable this power saving mode, when exactly is the power saving mode disabled?
As soon as you plug in the power cable?
And is it not re-enabled automatically, after pulling the power cable out?
Sorry, but I did not exactly understand your issue.
"those settings remain disabled even though power saving mode is turned off" => Yes, that's correct. If the power saving mode is turned off, all power saving settings should be disabled.
This sounds to me like "normal" behavior.
Maybe I misunderstood something in your description.
It_ler said:
What ROM and kernel is on your phone?
If you enable user specified power saving with your customized settings (30% battery => shut down everything accept wifi), and you did not disable this power saving mode, when exactly is the power saving mode disabled?
As soon as you plug in the power cable?
And is it not re-enabled automatically, after pulling the power cable out?
Sorry, but I did not exactly understand your issue.
"those settings remain disabled even though power saving mode is turned off" => Yes, that's correct. If the power saving mode is turned off, all power saving settings should be disabled.
This sounds to me like "normal" behavior.
Maybe I misunderstood something in your description.
Click to expand...
Click to collapse
I'm on stock 2.3.3 and KG2
And I meant that these settings do not revert themselves after I finish charging the battery. For example, at less than 30%, my power saving mode turns off syncing. But once I finish charging my phone back to 100%, the syncing is remained off, so essentially, my power saving mode never really turns itself off even after charging.
I noticed the same thing - it's very annoying to set my screen timeout to 2 minutes, and when power-save mode comes on, it gets reset to 30 seconds and stays there.
I ended up turning off almost all of the power-saving features, and setting the threshold to 5%. I'm running the stock rooted kernel with NoCIQ, so I already have a pretty substantial battery life (~24-30 hrs with normal usage and wifi at home).
apollero said:
I'm on stock 2.3.3 and KG2
And I meant that these settings do not revert themselves after I finish charging the battery. For example, at less than 30%, my power saving mode turns off syncing. But once I finish charging my phone back to 100%, the syncing is remained off, so essentially, my power saving mode never really turns itself off even after charging.
Click to expand...
Click to collapse
Have a look at MyProfiles app from the Market.
Maybe it can help you to switch between different profiles based on system triggers.
Or use AutomateIt app to define rules when to toggle wifi, bt, gps, etc.
Just worth a try...
Sent from my GT-I9100 using XDA App
It_ler said:
Have a look at MyProfiles app from the Market.
Maybe it can help you to switch between different profiles based on system triggers.
Or use AutomateIt app to define rules when to toggle wifi, bt, gps, etc.
Just worth a try...
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Thanks for the suggestion, but I kinda want to get to the root of the problem here as opposed to installing an app to mask it. Does anyone else know what's wrong with my phone?
There's nothing wrong, that's just the way it works, it change your setting when activates but doesn't change them back.
I no longer use it, since I have GPS/wifi/BT disabled unless I use them anyway.
From what i know, the max is 10mins?
You're correct, 10 minutes is the maximum. I imagine you could modify a system file in order to hack your way around this, but I'm afraid I don't know which one - also you'd need to be rooted.
You could have smart stay on and keep looking at it, then it wont switch off
No need for root or shady tools.
Install the app 'Keep Screen on' and done
Apps can use the permission to keep your screen on even if they are not in active usage.
I usually set it to "Until I turn it off" so it won't stay on when plugging it into a charger.
Very handy app when keeping it for Skype communications next to the computer.
You can also use Power Widget Lite to create toggles on your homescreen to keep the screen awake.
I have xposed and gravitybox installed and I have set the low battery notifications to OFF, but I still have a notification sitting here that I'm at 10% and asks me if I want to enable STAMINA mode. Is there any way to completely get rid of these notifications?
The other annoying notification with 6.01 is everytime I boot the phone up I get a notification that mobile data is enabled. This is ridiculous, it's a phone, mobile data is nearly always enabled. Is there any way to disable that? I saw that someone modified an apk file for a z3c but I figured it wouldn't work to flash that on my z5c. Any ideas?
Those and the headphone notifications are very annoying. Try to bump this idea around the gravitybox area.
1ste world problems.
ive yet to figure this out as well. ill let you know if i do!
Disable notifications for system ui. No more low battery warning. Still get low battery LED and sound. Idk what else it has disabled with it but time will tell.
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Brokk said:
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Click to expand...
Click to collapse
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Scott said:
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
Click to expand...
Click to collapse
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
Scott said:
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Click to expand...
Click to collapse
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
I concur. Same happens to me.
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
termdj said:
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
Click to expand...
Click to collapse
I'm curious. Do you have any of the power saving modes turned on? Do you use "always on display"?
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
termdj said:
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
Click to expand...
Click to collapse
AoD could be keeping your phone awake, preventing Doze. The power saving features talks about putting apps to sleep, so unless you use them, that could also be disabling Doze. I could try changing the power saving settings, though it seems like a shame. I have zero interesting in AoD for multiple reasons, so it's not worth it for me to use that to solve my problems.
Thanks for the information!
Doze changed in Nougat, I believe, so that motion no longer prevented Doze from working. Since most men, at least, carry their phone in their pocket Doze hardly ever kicked in, greatly limiting its power saving capability.
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
Yes, I am confusing Doze with the Samsung power saving options. Blah!
I know the battery life will decrease with aod, but I have noticed that even without aod on my battery drop 2% per hour, so I leave it on...There are days that I can go 1 day and 8 hours before charging, but then my sot is only 2 hours....In general I'm happy with the battery life
meyerweb said:
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Click to expand...
Click to collapse
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Brokk said:
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Click to expand...
Click to collapse
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them. Doze (the pretty much hidden option in Apps), lets the apps wake up on their own, when you start using the phone, even if you don't access those particular apps.
I'm not sure why the Doze setup is buried so deep in settings, though. I guess Google (or Samsung?) really doesn't want you interfering with it.
meyerweb said:
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them.
Click to expand...
Click to collapse
I made a mistake of putting an app to sleep that I use to keep my screen awake. It uses a widget to toggle it on/off, but will shut off along with the screen if you intentionally shut your screen off. After putting that app to sleep, the widget stopped working. I had to go find the actual app, start it, then quickly flip back to my home screen and click on the widget. I couldn't undo my "sleep" action on that app. I changed it to "unmonitored", so that the S9+ would never put it to sleep. I rebooted. I shut off the power saving options. Nothing worked. Everytime I would go to the widget (unless I just started the actual app), it wouldn't react to clicking on the widget.
I finally gave up and uninstalled the app from my phone. Rebooted. Reinstalled it and now it works fine. So I'm not sure I agree with "puts the app to sleep in 3 to 7 days". Maybe 3-7 minutes...
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
meyerweb said:
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
Click to expand...
Click to collapse
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Brokk said:
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Click to expand...
Click to collapse
Samsung does bury things....
Settings / Device maintenance, click Battery at the bottom.
Then click the 3 dot menu at the top, and Advanced Settings.
Tap App power monitor (the text, not the toggle).
Tap Put unused apps to sleep (again, the text).
You can set the slider anywhere between 3 days and 7.
I spent several days just wandering through every settings option I could find after I setup the phone. Discovered all kinds of hidden things. Sometimes I can even remember where I saw them.
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more