Database Develop

Nexus One never sleeping

I have tried searching the forums but have found nothing yet, so I was hoping someone could help me. I am currently using Enomther's rom, but this has happened on every rom I've tried (Desire, Cyan, etc.). My problem is the Nexus One is running 100% of the time. In comparison, the screen was on for 5.2% of the time. And I have definitely noticed the battery. Even if in standby, it loses 10-20% battery an hour. By the time I make it home from school, I have about 20% battery left, with almost no usage whatsoever. I've checked to see if it's any apps that won't close, but my highest used app was only a few minutes according to spare parts. Cpu usuage is barely visible as well in spare parts.
List of Apps:
Advanced Task Killer
AK Notepad
Any Cut
Astrid
ASTRO
aTrackDog
Barcode Scanner
Battery Graph
Beautiful Widgets
Call Meter NG
Classic Simon
Mathpad
Contacts Clean-up
Dictionary.com
eBuddy
Engadget
FMyLife Official
FotMob 4.6
Funny Jokes
Google Sky Map
Google Translate
GPS Status
jkAppSwitch
Maps
Meebo IM
Metamorph
MountUSB
Movies
MyBackup Pro
Opera Mini 5 Beta
Paypal
Picsay
Pkt Auctions eBay
Places Directory
Quick System Info
Quick Uninstaller
Replica Island
Robo Defense
Rom Manager
Screebl Lite
SetCpu
Shazam
ShopSavvy
SMS Backup & Restore
Solitaire
Speed Test
Timeriffic
Titanium Backup
TTS Serivce Extended
Tube Downloader
Urban Dictionary
Urbanspood
WikiMobile
Wireless Tether For Root Users
World War
XDA
Zedge

Looks like an application is holding the wake lock. Instant Messengers are good candidates for draining the battery. In my experience, Meebo loses connection frequently, and eBuddy has a mode to keep the connection, but it drains the battery very fast (AFAIR it has a mode that's easier on the battery by checking for messages every 15 minutes, but that's not all that instant anymore).

Good job you have AnyCut installed.
Use it to place a shortcut to the 'Testing' app (or dial *#*#4636#*#*), and use that to look at your battery history.
This will be able to confirim if your N1 is indeed staying awake, and if you use the 'partial wake usage' drop down box, it will tell you what's keeping it that way.

For partial wake usage, the only thing that pops out Android System which has a full bar. Nothing else is above a sliver.

Since you have titanium backup, why not make a backup, completely wipe your phone, and see if the problem persists? Then, add components at a time and see when the problem reappears. ie ROM -> a few apps -> a few apps -> etc. This will narrow down your search and hopefully pinpoint the problem.

You also might wanna look at logcat (e.g. via aLogCat), sometimes there are a lot of messages of runaway applications.

Here's my logcat
pastebin.com/2fj74zPn

No spare parts?
Downlaod it and try setting the end button behavious to go to sleep.
Seems like an obvious thing, but its worth a shot if you haven't already tried it.

izmar said:
No spare parts?
Downlaod it and try setting the end button behavious to go to sleep.
Seems like an obvious thing, but its worth a shot if you haven't already tried it.
Click to expand...
Click to collapse
Yep, of course I have spare parts. I set that, but what exactly is the end button?
Edit* I've uninstalled every app on my phone, and yet the problem still persists. Running 100% of the time. What the heck is wrong with my phone?

panzival said:
Yep, of course I have spare parts. I set that, but what exactly is the end button?
Edit* I've uninstalled every app on my phone, and yet the problem still persists. Running 100% of the time. What the heck is wrong with my phone?
Click to expand...
Click to collapse
I think your best bet us to just wipe everything, and reinstall the rom. That should get things going smoothly.

do you have trackball succession mod? that may be the reason.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

SiNJiN76 said:
do you have trackball succession mod? that may be the reason.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
No, but I did have trackball wake enabled. Would that matter? Also, I've installed Cyan and the problem seems to be gone, although battery still isn't great :/

I would figure that trackball wake will keep waking your phone when you accidentally hit the trackball when the phone is in your pocket or bags?

panzival said:
No, but I did have trackball wake enabled. Would that matter? Also, I've installed Cyan and the problem seems to be gone, although battery still isn't great :/
Click to expand...
Click to collapse
One thing to check that I've run in to twice (unfortunately) is constant "syncing" of email. I only noticed it because the email app constantly showed the syncing circle (not in the notification bar, in the app). Clearning the storage/settings for email cleared it up, but it took a few days to find out what was causing it to never sleep.

Grooby97 said:
I would figure that trackball wake will keep waking your phone when you accidentally hit the trackball when the phone is in your pocket or bags?
Click to expand...
Click to collapse
Yes but my phones running 100% of the time and my screens running 1/20 of that time. Surely my screen on time would increase as well? As well I'm sitting in class half the day and know for sure that I'm not hitting the trackball.
krohnjw said:
One thing to check that I've run in to twice (unfortunately) is constant "syncing" of email. I only noticed it because the email app constantly showed the syncing circle (not in the notification bar, in the app). Clearning the storage/settings for email cleared it up, but it took a few days to find out what was causing it to never sleep.
Click to expand...
Click to collapse
Thanks, I'm going to look into this. Would this correspond to UID 10014 or Media having extremely high network usage as well? I just noticed these two things constantly have full network usage bars but don't know exactly what either are. How would I clear the settings/storage? I'm using a Desire Rom now if it matters.

[Q] Quick question

When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance

Which rom are you using?
I get what I call ghost notifications of text messages kind of the same way. I'll look at the message which clears the notification bar. When I turn off my phone at night and then back on in the morning I sometimes get a notification of the message I have all ready looked at. I think this was a problem in the international 2.2 roms hence the update to 2.2.1.
Oh, I'm using Cognition 4.1.1 ..... for now.

I am using the stock one. I haven't messed with the phone at all.
Oh ok thanks, to me it only happens when i turn it off it resends txts that i previously sent. It's kind of annoying not a big deal but gets old after a while. Thanks

I never had this problem with all ROMs I flashed. Or possibly I never noticed that happening. But I have to say that sometimes I still get double notifications for messages I have received previously after rebooting. personally I don't know why. I've tried cognition, phoenix, serendipity and now on firefly.
Sent from my SAMSUNG-SGH-I897 using XDA App

droid_07 said:
When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Click to expand...
Click to collapse
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?

modest_mandroid said:
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
Click to expand...
Click to collapse
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.

droid_07 said:
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
Click to expand...
Click to collapse
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.

modest_mandroid said:
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
Click to expand...
Click to collapse
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help

droid_07 said:
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
Click to expand...
Click to collapse
I don't know the specific range, but I remember hearing that if you bought your phone before Nov 2010, you were eligible for a replacement. I could be wrong though.. I think there's a thread about it in the general section.

Battery Saving with Deep Sleep Battery Saver

So, I know the whole discussion around task-killers and Android - let's try and avoid that here.
I rediscovered this app last week, I had an old version but it updated from Playstore. I stopped using task killers a long time ago, but I'd forgotten that the approach Deep Sleep Battery Saver takes is slightly different: it makes sure that the phone is REALLY asleep when the screen is off.
Now people have said that it's wake locks clash with Android own.
I went ahead and tried it on the highest setting - slumber - and it's fantastic in both my P7 & P6, and also on my Lg2.
The only thing I have to remember is that when I'm downloading files that take longer than say, 2mins, I have to change my screen-on time to accommodate, otherwise it will stop the download as soon the screen goes off.
I found this is a small thing to remember given the battery savings.
I mean the difference is sooo large I can't tell you.
I put it down to this - we all have a variety of apps on our phones and we really don't know what keeps running in the background.
The Huawei Music app for example, is notorious, as is the Camera ago on the Lg2.
Deep Sleep Battery Saver shuts everything down, period. And it works. I'm absolutely stunned by how much later into the night I can use my phones with a single charge in the morning.
It's a little like GREENIFY but as I don't root my phones anymore, this was a great alternative.
Actually even better is that I don't have to go through my entire list of apps picking and choosing.
I just select SLUMBERER.
The results have been so fantastic on my P6 & P7, that I had to share.
The Lg2 is great with battery WHATEVER you through at it.
The P6 & P7 are gorgeous phones - with anemic batteries...it's always been the case.
With this app, I have discovered a while new sense of respect and use for my P6&P7.
Of course, once your actually using the phone, the drain is as fast as always, it's just that the savings you make in between are phenomenal.
Just saying.
DS Battery Saver can be found FREE on playstore.
Sent from my HUAWEI P7-L10 using XDA Premium HD app
P.S. Oh! Just remember to turn off 'enable logging' in settings-general, leave the 'show persistent notifications' ticked in notifications& language, and turn off ALL the 'battery notifications' in notification& language.
Those are the things responsible for wake-locks.

To save battery it works quite well indeed and I thank you for that. The only tiny issue is that I don't receive the calls anymore, only a text that says that somebody tried to reach me. No ring, no move, just missing calls. I could also turn off my phone to save battery...

goby92 said:
To save battery it works quite well indeed and I thank you for that. The only tiny issue is that I don't receive the calls anymore, only a text that says that somebody tried to reach me. No ring, no move, just missing calls. I could also turn off my phone to save battery...
Click to expand...
Click to collapse
I receive ALL my phone calls, ALL my texts, as they are, when they come in, as usual, asap, otherwise what's the point.
My email, Facebook, whatsapp etc comes in soon as I turn on my screen.
The App doesn't touch your ability to make OR receive calls EVER. Something else is going on with you.
Sent from my HUAWEI P7-L10 using XDA Premium HD app

This app is extremely useless once you install an anti-theft program.
When you install this program, programs like Cerberus, Kaspersky Internet Security anti-theft function or Lookout won't work as they should when you lose your phone (and the screen is off).

vEEGAZ said:
This app is extremely useless once you install an anti-theft program.
When you install this program, programs like Cerberus, Kaspersky Internet Security anti-theft function or Lookout won't work as they should when you lose your phone (and the screen is off).
Click to expand...
Click to collapse
Yes.
If you're using an always on, anti-theft application, you're not really worried about conserving battery.
This app works if you need to get more life out of your charge.
Alot more.
That's how it works.
Sent from my LG-D802 using XDA Premium HD app

Does it stop alarm clock from working?
I really hope it doesn't...

GawDroid said:
Does it stop alarm clock from working?
I really hope it doesn't...
Click to expand...
Click to collapse
No it doesn't actually! The alarm clock over rides everything short of actually switching your phone off... And in some ANDROIDS even this isn't enough.
You'll be awoken, don't worry.
You'll also be amazed at the amount of battery life you suddenly have... I'm loving it! Just don't forget the p.s. end of post #1
Sent from my LG-D802 using XDA Premium HD app

kolembo said:
No it doesn't actually! The alarm clock over rides everything short of actually switching your phone off... And in some ANDROIDS even this isn't enough.
You'll be awoken, don't worry.
You'll also be amazed at the amount of battery life you suddenly have... I'm loving it! Just don't forget the p.s. end of post #1
Sent from my LG-D802 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I can confirm everything is working as intended.

auto closing high power usage apps bug?

Does anyone experience any problems with this setting on 4.1.3? On my phone if i switch it off it sometimes switches itself back on. It also seems to close down apps without notifying me. They are just greyed out and cannot be cleared or removed. (Podcast republic and swipe). Those two apps are also the reason i want it switched off as they stop functioning properly if on.
It seems to be linked to the power saving auto rotate switch-off bug as it tends to happen most of the time when the auto rotate isn't switched on again when i charge the phone. Anyone else experiencing this?
Phone is not rooted and run on stock rom

Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Sent from my ONEPLUS A3000 using Tapatalk

i snort flour said:
Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Click to expand...
Click to collapse
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.

Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
Grab a catlog off of the play store they are fairly simple to figure out and they are free. I can't remember for sure but I believe I liked logcat the best as it provided a better ui with a more detailed and easier to read log.
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 01:46 AM ---------- Previous post was at 01:35 AM ----------
Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
That's weird that it keeps turning back on hopefully it's not a hardware issue. Most likely due to a rogue incompatible app. Also if you haven't already done so check for an update and make sure you have the latest version and if that don't work the last thing I could think of to try would be to download the latest update and put it on your phone somewhere you can remember, reboot into recovery and erase your cache and perform a factory reset followed by another cache wipe just to be sure. Then select install update from zip file, navigate to it's directory and open it, allow it install the update and after it completely has finished booting don't use it but keep the screen from turning off for about 2 minutes
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 01:46 AM ----------
Sorry I can't be of more help to you but I just got my phone today and I'm on the oos 4.1.3 and mine is doing just fine so far but I don't sync mail, push notifications, or use any social media which drain your battery like a hooker with your bank account. So far I'm at 10+ hrs uptime with 4 hrs of sot sitting at 66% battery life with an estimated 20 hrs left.
hope you find your problem or at least know where you got take your issue to which will be discovered in your cat log so you will know if it's the apps, kernels, os or hardware that is to blame and be able to address it to the proper source.
Sent from my ONEPLUS A3000 using Tapatalk

Background processes killing. Is it problematic for you?

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...