Database Info

Auto/background sync stops after battery dies

I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?

WibblyW said:
I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?
Click to expand...
Click to collapse
Are you sure that this simply isn't they power save feature kicking in?
This can be configured using various settings from within
Settings > Power > Power save
Sent from my HTC Desire S using XDA App

Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.

WibblyW said:
Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.
Click to expand...
Click to collapse
Oh, must admit that I have not noticed this, although I do use tasker application to enable and then disable my various radios and sync settings based on time in order to save battery
Sent from my HTC Desire S using XDA App

This is happening on my Desire S too.
Have you found a solution as of yet?

frosticus said:
This is happening on my Desire S too.
Have you found a solution as of yet?
Click to expand...
Click to collapse
Nope. There's a LOT about the Desire S that kinda half works properly. I find its implementation really kind of sloppy. Definitely NOT a phone I go round recommending to anyone.
To ben_pyett's comment I considered Tasker. Apart from the fact that there are lots of comments that some of it's functionality is broken in 2.3 because Google messed with their APIs, when I thought about it I was pricipally going to get it to try and fix/work around all the stuff that doesn't work well in the Desire S, rather than add functionaliy. E.g.
- Auto display brightness always has the brightness too high (esp in dim ambient light) and there's no way to adjust its 'gain'
- Cycling Buetooth and WiFi and GPS availability (using various strategies based on location and time) only to mitigate poor battery life in the standard product
- Getting it to out of power save mode properly
- Stopping it making the SMS received notification noise when it was just receiving a txt delivery receipt
Sadly there's other stuff Tasker can't 'fix'.
I find myself rebooting the phone manually every two or three days when it begins to exhibit weird behaviour. It might be crashing and rebooting between those times too. I used to have a SIM PIN activated, but it would prompt for that before allowing me to even get calls after a crash, so I missed important calls before I noticed it was in that state. Now with the SIM PIN disabled it might still be crashing but I don't spot it at least.
I was a Blackberry user for years, and should never have changed. At least the BB was stable and all its features seemed to work properly (and had excellent battery life even with WiFi and Bluetooth on 24/7). I though the extra Google integration with Android was attractive and would be worth it. How wrong I was. :-(

push notifications intermittently fail to come through while screen is off

This problem shows up periodically when I leave my S7 stationary on a desk or table while in discharge mode. I found an xda thread describing the exact symptoms, but for the S6. My phone is an S7, of course. That S6 thread is here: http://forum.xda-developers.com/galaxy-s6-edge/help/push-notifications-stop-screen-off-t3071248
I have my device set so notifications will appear on the lock screen. And under Settings > Notifications I have about 5 apps set for priority mode. That works consistently to bring notifications from those apps to the top of the notification list. The problem is that occasionally when the screen turns off --not consistently-- all push notifications are suppressed until I turn on the screen again. At this point, all of the suppressed, pending notifications fire off their associated alert sounds and each of their alert banners pop onto the lock screen. I can never know when the notifications are going to be suppressed like this when I toggle off the screen or when it times out on its own.
Am I the only one who experiences this issue on the S7? I had possession of some other S7's some months back and at least two of them demonstrated similar intermittent push notification behavior. However, I had no idea exactly what was happening at the time (i.e, whether it was the individual apps malfunctioning or perhaps a lagging issue with the servers/networks they were using). But from my experience to date, it appears that the absence of notifications on those devices during screen off mode may have been the same issue.
There was a great deal of concern about this within the S6 thread I've cited above. But no definite solutions were given; the general hope was that a future update would correct the problem on the S6 and that the S7 with android 6 marshmallow would hopefully not include the intermittent notification problem. If I've missed an informative thread on this issue relevant to the S7 (or the S7 edge) please direct me accordingly.
Thanks

Used to happen with my S5, afaik it's Marshmallows new low power mode, 'Dose' that causes it as it didn't happen with Lollipop

*Detection* said:
Used to happen with my S5, afaik it's Marshmallows new low power mode, 'Dose' that causes it as it didn't happen with Lollipop
Click to expand...
Click to collapse
In that case, how is the best way to disable this mode? Package Disabler perhaps? And why am I the only one who seems to have posted about this matter as far as the S7? Timely notifications are pretty important... so I would think that if this were a typical power saving side effect on the S7 that many S7 owners would be speaking out about the notification lapses. It's fairly puzzling.
Thanks

Dose being the cause is just my take on it, I couldn't think of anything else it could be with my S5 either, and as I said it never happened with Lollipop, and Dose only arrived with Marshmallow, so I put two and two together
Not sure you can disable Dose, other than have something running in the background causing a wakelock, which would drain your battery
Might be something else causing it, but I couldn't see any other explanation
Something I did notice though was if the phone was on 4G Data instead of WiFi, notifications were instant, but I was only on 4G while I was out, and when the phone is moving, dose doesn't work, it has to be completely stationary

*Detection* said:
Dose being the cause is just my take on it, I couldn't think of anything else it could be with my S5 either, and as I said it never happened with Lollipop, and Dose only arrived with Marshmallow, so I put two and two together
Not sure you can disable Dose, other than have something running in the background causing a wakelock, which would drain your battery
Might be something else causing it, but I couldn't see any other explanation
Something I did notice though was if the phone was on 4G Data instead of WiFi, notifications were instant, but I was only on 4G while I was out, and when the phone is moving, dose doesn't work, it has to be completely stationary
Click to expand...
Click to collapse
Hmm... in my case it is happening exclusively on 4G without wifi running. So maybe it's something else. Most of the time notifications come though immediately. I'd say that during only about 10 or 20% of the phone's stationary time they are repressed until screen on.

Have a solution!
Faced the same issue, you have to exclude the apps you need notification at 2 places in the settings.
For the doze settings, go to settings, battery, battery usage, more ( top right), optimize battery usage , select all apps and select the apps you need to show notifications.
Second place, settings, battery, go down to app power saving, click details, set app you wish notifications to disabled.

Explanation of Nougat Battery Consumption and Workarounds for Better Battery Life

Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!

Doze is problem for me. I don't have push notification by the night.

darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.

Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem

darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.

I did everything what I can without succes.

furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?

xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.

I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.

antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...

Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)

Thank szgfg,
Both are already well configured, but still closing the app.

mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk

Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0

After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.

[Guide] My Battery Optimization Guide for OnePlus 6

Hello everyone,
This guide is for non-rooted, stock-firmware phones. It is geared more towards getting good stand-by times, but of course this will also benefit screen-on time. It has some OnePlus-specific things but also many non-specific to one manufacturer. It does not contain miracle information, but from my experience it can help quite a bit. It assumes that you keep phone, mobile data, Wi-Fi and sync enabled at all times. Those are core features of any phone and are not means to save battery. The optimization steps are listed in the order which I think impacts battery life. You may or may not apply some or all of the things listed, depending on your own needs.
So:
1. Go to Settings->Battery->Battery optimization->[tap on the 3 vertical dots on the upper right corner] and enable the phone's "Advanced Battery Optimization" (aka. Aggressive Doze) feature, while at the same time whitelisting apps from which you need instant notifications, like Whatsapp or Outlook, etc. For other apps notifications may be delayed. Some applications like AdBlock Plus for Samsung browser also need whitelisting to work properly. Just go by trial and error with finding which applications need whitelisting.
2. Enable "Developer Mode" by going to Settings->About Phone and tapping 7 times on the "Build Number". Then go to Settings->Developer Options and enable the "App Wi-Fi Multi/Broadcasting Filter" option. I did not find any app impacted negatively by this, even casting to Chromecast works fine.
3. Go to Settings->Display->Ambient Display and disable the "Lift up display" and "Wake screen on notifications" options (which are useless compared to a true Always-On Display option anyway), and instead put the phone's RGB notification LED to good use. The Light Flow (one of many, but in my opinion the best) app can customize the LED color for different types of notifications, as well as setting a priority or cycling between colors. Since the LED's "always-on" nature, it is actually much more useful than a dead screen that only wakes up when lifted. When I use Light Flow, I set the LED blinking speed to "Always On" and a diffent color for each app. Works much better than any "ambient" mode.
4. Go to Settings->Display->Themes and enable the "Dark Theme". It reduces power consumption for OLED displays such as the one from the OnePlus 6.
5. Social media apps (especially Facebook) are battery hogs because they need to continuously gather your personal data and usage information. If you are only an occasional user, prefer uninstalling those apps and instead using the browser to access your account. This will also benefit you in other areas, like productivity
6. Keep Location off until you need it. This will ensure that the system does not wake up the GPS due to some obscure request from an app that can also work without knowing your location.
7. Go to Settings->Apps->Application list, tap on each app and review permissions. Remove Location permission for apps that you don't want to unknowingly wake up your GPS and draining your battery. I prefer to only allow Location access to Google Maps and Waze but your mileage may vary.
8. Disable Face Unlock. Activating the front camera so often does consume quite a bit of battery, as can be seen in battery stats. And as you may have read, it is not very secure anyway. As the rear-placed fingerprint sensor makes it almost unusable for me (for example I cannot unlock it while in the car cradle or on the desk), I chose to use the Smart Lock features with my Bluetooth smartwatch and my home Wi-Fi network and my phone stays unlocked while my smartwatch is around, which eliminates the necessity for both face unlock and fingerprint reader.
9. Prefer using software from companies that do not live from user data (like Google and Facebook). Collecting as much user information as possible requires wide system access and takes up a lot of battery. I like to replace Gmail with Microsoft Outlook (even for my Gmail addresses) and I use Samsung Internet instead of Chrome. The Samsung browser seems to be the most battery-efficient browser available, way above Firefox. Microsoft Edge may also be a good alternative.
10. Use an ad-blocker if supported by your browser. Animated ads and additional loading of ad-related content contributes quite a bit to the web browsing battery drain.
11. Go to Settings->Accounts->Google and for each Google account, tap on it and then disable syncing for information that you do not need synced. Clicking on a Google account shows you sections of info to be synced. Disable what you don't need. For example, you may only need Contacts syncing for your primary Gooogle account and not all of them. Same with Google Fit data, pictures, etc.
12. Go to Settings->Apps->Special Access->Usage Access and disable this access for OnePlus Switch and Google Play Store (not for Google Play Services, it may have unwanted side effects). This stops these apps from consuming system resources and battery to continuously collect usage data.
13. Go to Settings->Apps->Application list and disable applications that you don't need and can be disabled (some cannot be disabled).
14. Opt out of (do not enable) the "send diagnostic information" checkboxes whenever you are asked for, unless you are really selfless and want to give [a percentage of your battery life] to the community Go from app to app and see if it has this or similar setting (sometimes these settings are sugarcoated into "enhance your experience by sending your data to us"). Disable if found.
15. Do not enter your OnePlus account information. This will activate all kinds of data-sending services that will contribute to the battery drain.
16. Wipe cache after each update, especially if you notice worsened battery drain. To wipe cache, turn off the phone, then hold Power + VolDown buttons continuously until it starts, keep holding until a menu appears. After you enter your phone password you can choose "Wipe Cache/Data" section which brings another menu, choose "Wipe Cache" then after confirmation, choose Reboot.
17. If you are not using the landscape mode a lot, prefer to lock the phone rotation in portrait mode (the toggle is present among the quick toggles) and only unlock the rotation when needed. From what I have read, somehow the auto-rotation seems to unnecessarily cause some activity (even wake-locks), and from my experience I did see a bit of improvement from this tweak, looks like more than placebo.
18. If you already have a OnePlus 6, this does not apply. But if you are after ultimate battery life, keep in mind, less chips means less power draw if all else is equal, and RAM memory needs continuous refresh, so a model with 6GB of RAM may be a bit more power-efficient than one with 8GB RAM, especially given the fact that still-large 6GB of RAM virtually guarantees that there will be no extra overhead related too app reloading.
Hopefully this will help some people.
Below you will find some of my usual stand-by times after the optimization. Since update 5.1.7 battery life seems to be improved even further (see last 2 screenshots - with 5.1.7 and 5.1.8).

Thanks for all this. Most of the things I already did myself, but some of them actually make a lot of sense but I've never thought about it before.
Already very happy with the battery life I'm getting, but very curious if it will be even better now.

Thanks for this nice pice of guide!

All of this means nothing if you have really bad cell reception like me. -105 to -112 dBm at the office. Drains like hell in standby.

Cst79 said:
1. Go to Settings->Battery->Battery optimization->[tap on the 3 vertical dots on the upper right corner] and enable the phone's "Advanced Battery Optimization" (aka. Aggressive Doze) feature, while at the same time whitelisting apps from which you need instant notifications, like Whatsapp or Outlook, etc. For other apps notifications may be delayed. Some applications like AdBlock Plus for Samsung browser also need whitelisting to work properly. Just go by trial and error with finding which applications need whitelisting.
Click to expand...
Click to collapse
By Whitelist you mean changing it to "Not Optimize correct?

mesajoejoe said:
By Whitelist you mean changing it to "Not Optimize correct?
Click to expand...
Click to collapse
Correct !

well done on post [emoji106]

Dumb question, is Advanced Optimization (with some apps not optimized as needed) definitely more efficient than normal, with every app set to optimize as by default (and everything works)?
Why isn't there 3 settings for every app: not optimized, optimized, and advanced optimized?

and i got this today... now charging...

Muntasir Mahmud Saif said:
and i got this today... now charging...
Click to expand...
Click to collapse
Looks pretty great ! Did you use the optimizations from this guide ? Any other tips ?

Cst79 said:
Looks pretty great ! Did you use the optimizations from this guide ? Any other tips ?
Click to expand...
Click to collapse
no bro...i always make my own optimization...no offense though... I'll post the guide later on...

Cst79 said:
15. Do not enter your OnePlus account information. This will activate all kinds of data-sending services that will contribute to the battery drain.
Click to expand...
Click to collapse
Hi Bro,
Sorry that i not so understand what this item 15 means.

xiah1512 said:
Hi Bro,
Sorry that i not so understand what this item 15 means.
Click to expand...
Click to collapse
As you may know, especially if you purchased your phone or accessories from the OnePlus website or accessed the OnePlus forums or support, you can create a OnePlus account online. At phone setup, OnePlus asks you to optionally enter this account for various benefits. Do not enter this information when/if asked. Or, if already entered, you can delete it from Settings->Accounts.

Cst79 said:
As you may know, especially if you purchased your phone or accessories from the OnePlus website or accessed the OnePlus forums or support, you can create a OnePlus account online. At phone setup, OnePlus asks you to optionally enter this account for various benefits. Do not enter this information when/if asked. Or, if already entered, you can delete it from Settings->Accounts.
Click to expand...
Click to collapse
Ok, Thanks bro.

For those suggestions that cut down on network chit-chat, this also serves as a partial data usage optimization guide. Thanks for taking time to enumerate all these suggestions. I found a few slam-dunks in this list.

Cst79 said:
As you may know, especially if you purchased your phone or accessories from the OnePlus website or accessed the OnePlus forums or support, you can create a OnePlus account online. At phone setup, OnePlus asks you to optionally enter this account for various benefits. Do not enter this information when/if asked. Or, if already entered, you can delete it from Settings->Accounts.
Click to expand...
Click to collapse
What does adding that account allow you to do?

Muntasir Mahmud Saif said:
no bro...i always make my own optimization...no offense though... I'll post the guide later on...
Click to expand...
Click to collapse
how did you fix the massive overnight drain eventually?
I'm getting 8% drain overnight, I dont think that's normal.

-marco- said:
how did you fix the massive overnight drain eventually?
I'm getting 8% drain overnight, I dont think that's normal.
Click to expand...
Click to collapse
You are on 5.1.6?

Joyarup said:
You are on 5.1.6?
Click to expand...
Click to collapse
I am, yes.

-marco- said:
I am, yes.
Click to expand...
Click to collapse
I was also facing this weird issue, then I noticed that the phone wasn't deep sleeping for some reasons, I rebooted it before going to sleep and it went to deep sleep fine and the drain was around 2% on LTE standby overnight. I will try different kernels too, currently using EX.

A couple strange things

Given the less friendly finger print reading I have taken to double tapping on the screen to turn it on. But relatively often it does not respond to a double tap. Is anyone else experiencing that?
The other one is that at many web sites I go to a pop up message box will come up asking if they can read my device's location. The answer box NEVER responds to a click. The screen will be dim. I have to back up 1 screen which closes the query box. I actually expect that one of my apps that have privileges to over write other apps is the culprit, but I don't see why they would mess with that one function, especially when at that moment those apps aren't being brought up. Any thoughts on this?

Increase screen sensitivity if you haven't already.

Yes I've experienced the double tapping unresponsiveness and decided to have AOD on all the time instead despite additional battery drain just to bypass this issue.

boogiecornejo said:
Yes I've experienced the double tapping unresponsiveness and decided to have AOD on all the time instead despite additional battery drain just to bypass this issue.
Click to expand...
Click to collapse
That's what I do on the 10+
Battery drain is slightly less than 1% @ hour.
For me it runs best/most efficiently with no power management* running other than the system power setting to optimized.
*some apks are package blocked otherwise all buckets show as active in Developer Options. If this is not the case unwanted power management is active.
I'm running Pie; not sure how Q will respond. I found it's best to let Android handle power management exclusively other than blocking serial power hogs like Google Backup Transport and Framework Services Framework. I don't use these.

blackhawk said:
Increase screen sensitivity if you haven't already.
Click to expand...
Click to collapse
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.

ewingr said:
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.
Click to expand...
Click to collapse
I keep my phone with me at all times, don't let others use it and never lock it. Makes life easier.
It's a steep learning curve with these devices... make sure it has the permissions it needs like being able to change system settings.

blackhawk said:
That's what I do on the 10+
Battery drain is slightly less than 1% @ hour.
For me it runs best/most efficiently with no power management* running other than the system power setting to optimized.
*some apks are package blocked otherwise all buckets show as active in Developer Options. If this is not the case unwanted power management is active.
I'm running Pie; not sure how Q will respond. I found it's best to let Android handle power management exclusively other than blocking serial power hogs like Google Backup Transport and Framework Services Framework. I don't use these.
Click to expand...
Click to collapse
Hmmm... The setting to read it loud is a system setting itself (in Accessibility settings). I don't think there are any permissions to make. I did just look and nothing is apparent.

ewingr said:
Thanks for the suggestion. It is already active.
Here's another interesting thing: every now and then (actually several times during the course of a day) after turning the screen on the bio didn't with nor the location, and it forces me to enter the pin to get into the phone. I even have it set to not lock if hooked to my hearing aids and it still happens.
Click to expand...
Click to collapse
ewingr said:
Hmmm... The setting to read it loud is a system setting itself (in Accessibility settings). I don't think there are any permissions to make. I did just look and nothing is apparent.
Click to expand...
Click to collapse
Permission to change system settings is in it's own listing apart from permissions in each app settings.
Could be more than one apk needed to make all work right.
Make sure power management not doing it.
In Developer Options>Standby Apps, all apps listed there should show as having their buckets as "active" if they not, power management is active.
You don't want that.

ewingr said:
I actually expect that one of my apps that have privileges to over write other apps is the culprit
Click to expand...
Click to collapse
one of the apps is interfering as you correctly suspect