Related
hi all,
i m new user for Nexus one, i wonder what is the best task apps to auto kill when the phone in sleep mode in order to save battery. My phone havent ROOT yet, shall i do it? After i have update the Android 2.1 i found it very good compare with iphone.
thank you very much
Killing tasks won't help to save battery... don't buy the hype. Android will manage your apps for you.
No killing tasks can help your battery. There are many apps on the market that are poorly written and drain battery.
McFroger3 said:
No killing tasks can help your battery. There are many apps on the market that are poorly written and drain battery.
Click to expand...
Click to collapse
Well that makes sense... but I don't run any poorly written apps. And neither should you.
If you absolutely have to have a task killer, just download Astro File Manager. You'll need a file manager on this phone anyway, and Astro has a built in configurable task killer and can also back up apps to SD.
uansari1 said:
Well that makes sense... but I don't run any poorly written apps. And neither should you.
If you absolutely have to have a task killer, just download Astro File Manager. You'll need a file manager on this phone anyway, and Astro has a built in configurable task killer and can also back up apps to SD.
Click to expand...
Click to collapse
I try not to. But sometimes I get curious and download some random apps haha.
I use Advance Task Manager since I bought it when I had a Cliq.
It works good when I need to kill something to restart it or if I need to do a batch uninstall.
Astro is amazing and no one should have an android phone without it.
Thks all,
If so, i shall just leave as it is and not install any of those task killer or auto task etc......
But anyway to min the battery drain since there are so much apps running on RAM when the phone is in sleep mode. My battery can only last for 8 hrs from 9am till 5pm (i am so distracted, i do turn on my BT and talk on phone for at least 100mins-150mins a day.)
Thank you
chocodip said:
Thks all,
If so, i shall just leave as it is and not install any of those task killer or auto task etc......
But anyway to min the battery drain since there are so much apps running on RAM when the phone is in sleep mode. My battery can only last for 8 hrs from 9am till 5pm (i am so distracted, i do turn on my BT and talk on phone for at least 100mins-150mins a day.)
Thank you
Click to expand...
Click to collapse
Keep the screen brightness as low as you can. Also having a lot of widgets can contribute to battery drain.
uansari1 said:
Killing tasks won't help to save battery... don't buy the hype. Android will manage your apps for you.
Click to expand...
Click to collapse
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Which task killer you use?
rossiscatch said:
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Click to expand...
Click to collapse
My screen always in lowest light mode......i will try to install the advance task....hope it deos help abit.
McFroger3 said:
Keep the screen brightness as low as you can. Also having a lot of widgets can contribute to battery drain.
Click to expand...
Click to collapse
chocodip said:
My screen always in lowest light mode......i will try to install the advance task....hope it deos help abit.
Click to expand...
Click to collapse
Advance task manager also lets you set a timer for auto closing all open apps except for the ones you have on your exception list.
chocodip said:
hi all,
i m new user for Nexus one, i wonder what is the best task apps to auto kill when the phone in sleep mode in order to save battery. My phone havent ROOT yet, shall i do it? After i have update the Android 2.1 i found it very good compare with iphone.
thank you very much
Click to expand...
Click to collapse
Try Juice Defender,is free on the market and everytime you turn the screen to sleep it kills the background data to save battery and @ wake-up its normal again.Read the reviews.
rossiscatch said:
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Click to expand...
Click to collapse
I've got over 400 hours of uptime without closing ANY apps with a task killer, and haven't had ANY sluggishness. So if you're really noticing your phone slowing down (and be honest), then I'd exchange it. Frankly, I think a lot of people just "think" their phone is slowing down...
Cyanogen says don't use a Task killer!
Paul22000 said:
Cyanogen says don't use a Task killer!
Click to expand...
Click to collapse
So if cyanogen says jump of a bridge you would? lol
Just messing with you.
I ve installed the Juicedefender and advance task manger......hope meanwhile there will be sthg better. Battery usage is killing me....
uansari1 said:
I've got over 400 hours of uptime without closing ANY apps with a task killer, and haven't had ANY sluggishness. So if you're really noticing your phone slowing down (and be honest), then I'd exchange it. Frankly, I think a lot of people just "think" their phone is slowing down...
Click to expand...
Click to collapse
Yeah, I'm sure you're right.. it's all in my head.
Couple of things OP:
1. Bluetooth is a battery hog!
2. How frequent do you have email update, weather update, et al set to?
3. Did you properly calibrate your battery meter when you got your N1? (Two ways to do it, 1) follow the in box guide and charge the phone before using or 2) run down the battery until the phone shuts itself off, pull battery out, put it back in. Now, without turning it back on, put it on the charger and leave it on for a couple hours past the green light coming on, take off charge, finally turn back on)
4. Do you have WiFi running? GPS? Streaming anything?
Have you downloaded any apps from the market just on a quim? There are some pretty bad apps that will never close until you uninstall and do a soft reset, and sometimes uninstall again.
Killing apps is actually going to hurt your battery. It takes more juice to power up the CPU to open an app then it does to hold it in the RAM, unless it is a crap written app that keeps running, and running, and running... but you shouldn't be using those apps anyways.
rossiscatch said:
Yeah, I'm sure you're right.. it's all in my head.
Click to expand...
Click to collapse
It most likely is... even when apps sit idle in RAM, the CPU usage for them is 0% in almost every case. Like I said... I don't have those issues at all, so it's either in your head or you have a dud.
uansari1 said:
It most likely is... even when apps sit idle in RAM, the CPU usage for them is 0% in almost every case. Like I said... I don't have those issues at all, so it's either in your head or you have a dud.
Click to expand...
Click to collapse
I don't think it's a problem with my phone. If you don't notice then good for you. I notice it and it bothers me. Your finger pointing is neither helpful or needed.
I'm newbe to android. I have problem my x10a ruuning out of juice in 12 hours. I'm using Advance Task Killer to kill the apps when screen is off but not sure which I need to put in Ignore List and which one I can kill safely. Here list of apps currently running and Ignore list
Currently Running Apps
com.Sonyericcson.larningclient
com.qualcomm.wiper
com.sonyericsson.android.contentmanager.service.facerecognition
com.sonyericsson.android.timeescape.pluginmanager.framework.application
com.sonyericsson.android.accountprovider
com.google.android.partnersetup
com.sonyericsson.android.contentmanager.service.timescape
com.sonyericsson.android.fota
com.sonyericsson.android.bootinfo
com.google.android.googleapps
com.sonyericsson.android.mediascape.pluginmanager.framework.application
DocumentToGoFullVersionKey
Maps
Pure Calender widget
com.sonyericsson.android.timescape.pluginmanager.framework.application
com.android.providers.calendar
com.sony.uwlop.launcher
eBay
com.google.android.apps.uploader
com.android.providers.downloads
com.billyfrancisco.photogallerywidget
voice dialer
com.sonyericsson.android.pccompanioninstaller
com.sonyericsson.android.digitalclock
3G Watchdog
Superuser Permissions
Barnacle wifi Tether
com.levelup.beautifulwidgets
settings
Ignore List
setting profiles
Advance task Killer
Timescape
Battery Status Ultimate
Gmail
Smart Keyboard Pro
Moxier Mail
Email
MyBackup Pro
Thanks is advance
I've had started a collection over here:
http://forum.xda-developers.com/showthread.php?t=707878
Have you tried not running Advanced Task Killer??? I'm running on f/w R2BA020 with no task killer and no startup auditor etc... and after a day of average use I down to about 40% after c.15 hours... I tried ATK and various others and in the end ditched them cos they were making the battery slightly worse, and making the phone slower cos it had to keep restarting app/ background processes that it uses..
Your power consumption will very much depend on what your running etc.. do you have any widgets that are updating regularly, or possibly faulty and preventing your phone from sleeping.. try using juice plotter for a while to see what your discharge profile looks like - you should see it going almost flat when you have a period of non use..
PS.. I've had bluetooth on (but not connected), wifi on, and 3G/ GPRS on all day today and after 11 hours I'm now on 52%.. have used the phone a reasonable amount.. maybe 20 texts, email syncing hourly, contacts and calendar on auto sync with google... no widgets on my home screen which sync, and no use of timescape.. used mediascape for about 30 mins, internet for about 20 mins, XDA app for about an hour.. played games for about 30 mins too..
I'm using Task Manager.
It pushed me up to 46hrs Standby, coming from 20hrs, when the battery is fully charged.
Thanks Guys
@McKebapp - It is good thread but need add info like one of the guys sugesting, which are ok to kill and Do NOT Kill
@ im_iceman - The problem is if you don't have ATK or other Task Manager, most application keep running once you clicked on them. I was looking Battery Use, this tell me its and Display and Standby but detail which program was using during standby
Hi - Yes some apps will sit in the background, but they should be sleeping and not actually doing anything, unless they've been badly written.. Android, based on Linux, manages the memory so that it's running on almost full most of the time and therefore is quicker to resume something which you were previously running, or is stored in memory awaiting use.. killing these things will mean that the processor has to work harder reloading them into memory all the time..
@Mckebapp - That may well be because it's killing a dodgy app that you've got running which isn't/ wasn't sleeping properly.. trouble is it may well be killing other stuff you need too..
Each to their own though..
GPdhillon said:
Thanks Guys
@McKebapp - It is good thread but need add info like one of the guys sugesting, which are ok to kill and Do NOT Kill
@ im_iceman - The problem is if you don't have ATK or other Task Manager, most application keep running once you clicked on them. I was looking Battery Use, this tell me its and Display and Standby but detail which program was using during standby
Click to expand...
Click to collapse
The absolute "NOT TO KILL" ones are written.
All other ones depend on the individual usage.
To me: I kill each one, that is killable
What about continuing my collection and making it more precise?
McKebapp said:
The absolute "NOT TO KILL" ones are written.
All other ones depend on the individual usage.
To me: I kill each one, that is killable
What about continuing my collection and making it more precise?
Click to expand...
Click to collapse
Sure, I'm glad to help but I'm newbe just tell me what to do
So I searched and could not find a thread that compiled tips and tricks people use to increase their battery life and get the most ram or memory available.
This way we can put everything together so you don't have to search through a bunch of threads or posts to get information.
I'll start with mine first.
Battery and memory usually go hand in hand, but specifically for the battery I use Juice Defender (Ultimate). I got it to last 31 hours before with minor use. Even the free one said it increased my life 1.5x
I use Titanium Backup to freeze certain programs that run in the background, like the social networking ones since I dont use those along with wallpapers and non-essential system services like the Weather and date/time services. It would be nice to compile a list of all the services you can freeze without messing up the phone, I usually freeze a couple and then test my phone out.
Not having a lot of widgets or background programs running also helps.
I found programs that prevent start-up programs usually fail, the app starts anyways. Task killers also don't seem to work, the app just starts back up. The only one I have used with some success is "Free Memory", it seems to work.
I'm interested in other peoples methods, along with their normal battery life and how much free memory they have.
Somehow I went from having around 450MB free to only having 250MB, which really gets bad if I want to use the webtop and have a bunch of crap open. I might try to reflash it and start over, I went a little app crazy for a few days.
If people want, list the (system) apps you were able to safely remove along with ones you were able to freeze and I can make a list in this post. I would add mine but my phone is acting up right now.
http://cgi.ebay.com/ws/eBayISAPI.dl...26699&_sacat=See-All-Categories&_fvi=1&_rdc=1
No, I'm not kidding either. I have three batteries for the Atrix. I go through about two a day. I run them all the way down, phone shuts off, I replace, and I have a 100% ready to go. Saved me in many instances. It sounds really convoluted, but it works.
I recommend installing widgetsoid and actively managing wifi.
Check out an app called Watchdog.
Basically what you should have instead of a task killer.
Instead of killing tasks wantonly, Watchdog simply monitors the CPU % each task/app/element running is consuming. You can custom set detection thresholds or leave the defaults, but whenever that threshold is crossed, you can get a little alert for it (customizable too). It tells you the app that's been acting up and give you the option of killing, ignoring, or "whitelisting" (permanent ingore, basically) it. The paid version also allows you to "blacklist" processes (permanent kill).
I would definitely recommend it.
Hi, I am using watchDog to try to see what processes start while the phone is in sleep mode. But I cannot find anything on WatchDog that tells me what is consumming battery.
I hope I make it clear.
The situation is the following.
When the phone is sleeping, with no 3g or wifi, it takes around 10% in 8 hours. Just iddle. This happens at night. When sleeping.
As soon as I wake up, I turn on 3g. And the battery starts draining. I understand this is normal. But should the phone be awake all the time just by having 3g on?
The awake bar is almost full. Eventhough the phone is locked. This happens only when I turn 3g or wifi on.
That's basically my question. Sorry if it is misleading or something.
Regards
the phone will be awake if you installed some rogue app that connects to the net every 2 minutes to check something, or just some badly coded app.
So I should start uninstalling each app to see which is the one? Or can I use an application that will tell me that? Itried watchdog, but got no success.
Any ideas?
I've found eBuddy to keep my Awake bar completely solid... EVEN if I'm completely exited out of it. It has to do with the fact that like any other app, Gingerbread keeps a cached version of the process in the background. But in eBuddy's case, staying cached causes the phone to stay awake, so the only way to resolve this is to completely kill eBuddy and any of its cached processes.
That's why I still run ATK at 30 minute kill intervals. Getting great battery life. Here's my original post on this issue:
http://forum.xda-developers.com/showthread.php?t=1094666
almorsol said:
So I should start uninstalling each app to see which is the one? Or can I use an application that will tell me that? Itried watchdog, but got no success.
Any ideas?
Click to expand...
Click to collapse
You can start by going into settings -> applications -> running services
Tap the "menu" button and make sure you are looking at only "show services in use" as opposed to all services including cashed.
You will get a list of about 10-30 (depending on what you installed and how you configured the phone)
Then go to settings -> accounts and sync, and under "manage accounts", see what accounts you created that sync up with somehting. make sure the icons (round circles) are green only for the accounts you truly want to sync.
Also tap through each account you do want to sync and check the sync settings . If there is an account that is set to sync every 2 minutes, or is set to sync at an unreasonable short time, change that. There could also be a bunch of account you what to totally switch into "manual sync" mode, for example email addresses you do not care about.
cmd512 said:
I've found eBuddy to keep my Awake bar completely solid... EVEN if I'm completely exited out of it. It has to do with the fact that like any other app, Gingerbread keeps a cached version of the process in the background. But in eBuddy's case, staying cached causes the phone to stay awake, so the only way to resolve this is to completely kill eBuddy and any of its cached processes.
That's why I still run ATK at 30 minute kill intervals. Getting great battery life. Here's my original post on this issue:
http://forum.xda-developers.com/showthread.php?t=1094666
Click to expand...
Click to collapse
I will install ATK and follow your steps buddy. Will let you know how this worked for me.
Regards.
I will do the same. Thank you!
Have a query, What Auto Kill level should I set and what's the difference between Crazy-Aggressive-Safe? I atm at Agressive!
ithehappy said:
Have a query, What Auto Kill level should I set and what's the difference between Crazy-Aggressive-Safe? I atm at Agressive!
Click to expand...
Click to collapse
I do Crazy, 30 minutes, and Low level so that I can see all processes (including system level). I then run my phone as usual and add any/all system related processes to the ignore list.
Good luck, and hope it works for you as well.
I just made a test, and found that the app that makes my phone to be awake all the time is the MSN Talk Pro.
I disabled it, and everything went to normal.
Is this normal in IM apps, since the other person was having the issue with ebuddy?
How could I have the IM app running without having my phone awake all the time?
The task killer would definetly work, but then I would not be able to get msn messages.
Is this the only option?
Thank you.
almorsol said:
I just made a test, and found that the app that makes my phone to be awake all the time is the MSN Talk Pro.
I disabled it, and everything went to normal.
Is this normal in IM apps, since the other person was having the issue with ebuddy?
How could I have the IM app running without having my phone awake all the time?
The task killer would definetly work, but then I would not be able to get msn messages.
Is this the only option?
Thank you.
Click to expand...
Click to collapse
Let me try to explain the situation.
If you have an IM client and you want it to be ready to accept messages from your buddies, it has to be in "listening" state to "hear" from your buddies. How that "listening" state is implemented by the developer defines how much batt power the application is eating.
Two opposite example:
1) Some stupid developer coded the IM client to always stay in foreground on your phone, actively pinging the servers on the internet , asking the servers if you have new messages. Your battery is wasted big time man.
2) A smart developer coded the IM client to use Google's C2DM interface (Cloud to Device Messaging framework). Such an app will stay dormant on the phone, and will be woken up by the android core processes whenever a new message arrives for you - Google servers will wake up the app on your phone. Such an app will not waste battery much.
There are a number of variations that go in between (1) and (2) above. So there is no clear-cut good or bad app. All depends on the implementation, and also on the way you configure your phone and the app on it.
Latest version of eBuddy was supposed to use C2DM too.
Ad the new Trillian is using C2DM. I never tried any of these though, can't vouch for any.
Just keep trying various IM apps until you find one that does not stay awake.
cmd512 said:
I do Crazy, 30 minutes, and Low level so that I can see all processes (including system level). I then run my phone as usual and add any/all system related processes to the ignore list.
Good luck, and hope it works for you as well.
Click to expand...
Click to collapse
It has worked for me mate, worked well I should say. You deserve a Thanks mate.
I set it on Aggressive mode, with Auto kill at an interval of 1 hour, and NO apps but only my Power Schedule app in Ignore list, and I kept the Network On (Normally I use Flight Mode at night time), and after 9½ hours the battery drained just 2%, from 90% to 88%. Usually on Flight Mode I used to have a 3-4% drain overnight, so it's a big improvement.
BUT there are still two small but solid Awake bar present there while the Screen was off! What could be the reason? Is it because ATK was running and caused the Awake bar by itself or other apps? Take a look at the pic.
I have another query,
If I don't add any system apps (those come by default) to the Ignore list will there be any problem?
Regards.
kreoXDA said:
Let me try to explain the situation.
If you have an IM client and you want it to be ready to accept messages from your buddies, it has to be in "listening" state to "hear" from your buddies. How that "listening" state is implemented by the developer defines how much batt power the application is eating.
Two opposite example:
1) Some stupid developer coded the IM client to always stay in foreground on your phone, actively pinging the servers on the internet , asking the servers if you have new messages. Your battery is wasted big time man.
2) A smart developer coded the IM client to use Google's C2DM interface (Cloud to Device Messaging framework). Such an app will stay dormant on the phone, and will be woken up by the android core processes whenever a new message arrives for you - Google servers will wake up the app on your phone. Such an app will not waste battery much.
There are a number of variations that go in between (1) and (2) above. So there is no clear-cut good or bad app. All depends on the implementation, and also on the way you configure your phone and the app on it.
Latest version of eBuddy was supposed to use C2DM too.
Ad the new Trillian is using C2DM. I never tried any of these though, can't vouch for any.
Just keep trying various IM apps until you find one that does not stay awake.
Click to expand...
Click to collapse
Thanks man.
I will keep trying some of them. Starting with the ones you said.
almorsol said:
Hi, I am using watchDog to try to see what processes start while the phone is in sleep mode. But I cannot find anything on WatchDog that tells me what is consumming battery.
I hope I make it clear.
Regards
Click to expand...
Click to collapse
I have recently removed watchdog and noticed that battery consumption rapidly reduced...
My background with android is long and rocky.
A long time ago in a galaxy far away, I had a Samsung Galaxy S, then a S2.
I can remember a Google Nexus phone in there somewhere.
Then at some point I switched over to Windows Mobile for many years.
A couple of hears ago I came back to android with a Samsung Galaxy S8+ and I hated it.
Recently I upgraded to a OnePlus 6T McLaren and here I am.
I had been expecting to see android happily use up 7, 8 or even 9GB of ram before the background task manager would begin to kill tasks.
Except that I seldom saw android use much more than 5GB of ram.
And worse, background tasks were being killed on a regular basis.
Widgets would stop working overnight, or even in just a few hours.
Spotify would close while a playing a playlist.
A quick search on XDA reveals that many users believe that Android will just use up as much ram as your phone has.
However, that is simply not true.
And so, I began my quest to have Android use as much ram as the phone could provide.
In my case, 10GB.
- I understand that there is an inherent trade-off between keeping background apps running and battery usage. I can live with extra battery usage in exchange for keeping my widgets running or Spotify running for an entire playlist.
- I realized very quickly that in order to achieve the results that I was looking for that the phone would have to be rooted. So rooting was one of the first things that I did.
Step 1.
I started with the basic stuff that a quick google search would provide;
- Settings -> Battery -> Battery Saver (off)
- Settings -> Battery -> Adaptive Battery (off)
- Settings -> Battery -> Battery Optimization -> widget app (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Spotify (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Deep Optimization (off)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Sleep standby optimization (off)
- Settings -> Apps -> Widget app -> Battery -> Background Restriction (app can use battery in background)
- Settings -> Apps -> Spotify -> Battery -> Background Restriction (app can use battery in background)
This helped but not enough to make the widgets or Spotify usable.
Step 2.
I supposed that my specific background tasks that I wanted to keep running were being killed because of the many other apps that were running in the background.
I searched for and found Tomatot DeBloater scripts for the Oneplus 6.
Excellent! Just what I was looking for.
I chose the Tomatot-Debloater-OOS-Light-2.3.zip and installed it.
This helped some more but not enough to make the widgets or Spotify usable.
Step 3.
I realised that there were still some apps running in the background that I didn’t use or want.
So I used Titanium Backup to freeze the following apps;
- Calendar
- Calendar Storage 9
- Contacts (O+)(I replaced with google contacts)
- Dashboard
- Drive
- Face Unlock
- Gboard
- Gmail
- Google
- Google partner setup 9
- Google play music 8
- McLaren AR
- Messaging (O+)(replaced with google messaging)
- OK google enrollment 9
- Oneplus system 1
- Youtube
Perfect! These apps were no longer competing for phone resources with the apps that I wanted to run.
This helped some more but not enough to make the widgets or Spotify usable.
This did make the phone feel faster and smoother.
The phone is much more responsive and fluid to my input.
This made me realize that the apps were being closed not due to a lack of phone resources, but a background task manager being aggressive.
Presumably for battery saving purposes.
I changed my focus to adjusting that background task manager.
Step 4.
Enable the recent screen ‘LOCK’ on the widget app and Spotify.
This didn’t do anything for me.
Everything that I’ve read on it says that it just stops the task from being killed when you click on kill all tasks.
The lock doesn’t lock the task from being killed by the background task manager.
Step 5.
Further google searching led me to believe that the OEM kernel was limiting background tasks.
I choose ElementalX-OP-3.09 and the EX Kernel Manager.
I had to read a lot of google university material to make any sense of the settings in here.
I’m not sure that I fully understand even now.
Eventually, I ended up with the following settings;
Memory
- Adaptive Low Memory Killer (disabled)
- dirty ratio (20)
- dirty background ratio (5)
- min free kbytes (12398)
- vfs cache pressure (100)
Memory -> Low Memory Killer
- apply on boot
- Foreground app (72mb)
- Visible apps (90mb)
- Secondary server (108mb)
- Hidden apps (200mb)
- Content Providers (587mb)
- Empty apps (783mb)
This helped a lot.
This almost made the phone usable to the state that I wanted.
But the widget and Spotify would still stop running overnight and by morning the apps would have to be reopened to get them to run again.
At least the apps would run most of the day without being killed.
Still not the behaviour that I expected from a phone with 10GB of ram.
Ram usage was still not going much over 5.5Gb even if I opened up many apps at once.
Can I ever get ram usage up to the 10Gb that I have?
Step 6.
The last thing that I tried yesterday afternoon was to increase the background task limit in the build.prop.
ro.vendor.qti.sys.fw.bservice_limit=5 (changed it to 60)
ro.vendor.qti.sys.fw.bservice_age=5000 (changed it to 10000)
Yes, I know that I am on PIE and there isn’t supposed to be any effect.
No, I don’t know yet if this had any effect.
I am hopeful.
The widget app didn’t close last night, but Spotify did.
I am getting closer!
This is the best that I could do on my own without asking for help.
So here I am posting my question and asking for help.
How do I get the apps that I want to run to not be killed by the background task manager?
OR
How do I get the phone to use the 10GB of ram?
I feel that I am missing something.
With any luck, one of you smarter persons will be able to point it out to me.
As an aside from all of these changes the phone feels very smooth and fluid.
Except for apps closing that I don’t want to, this phone is a great experience and a pleasure to use.
Apps that I want to run are staying open much longer then before I started.
It’s now just an overnight issue.
And getting the phone to use over 6Gb of ram.
I would suggest that I am 90% happy with it now.
KERNAL: ElementalX-OP6-3.10
ROM: STOCK OOS 9.0.11
PHONE MODEL: 6013 O+6T McLaren
Tomorrow I may try making this change to the build.prop file;
ro.vendor.qti.sys.fw.bservice_enable=true to false
Don't know if it will help or not.
Wow dude, interesting read, i will sign up for notifications from this thread hoping you get your answer because i have the exact same problem but with my work app, throwing it all out of whack and making me a target to big fines (in the $1,000's) and potentially reducing my marketability!
The attached screenies are from before i realized that the app getting killed in the background is what causes the problem (I've left it in the foreground HOURS a few times and it works perfectly!)
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
geeksquad2 said:
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
Click to expand...
Click to collapse
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
UPDATE:
I am a silly goose.
I broke a cardinal rule while troubleshooting.
I may have had a few too many wobbly pops and made two changes at a time, thus when change was affected, I was unable to determine properly which change caused the affect.
The rule is, "only make one change at a time when testing".
Yes, all of my apps stay open all the time.
I am getting the behaviour that I was looking for.
However it wasn't necessarily changing the build.prop bgservice_limit from 60 to 120 that did it.
Let me back up a bit.
Earlier I had suggested that locking an app to the recent screen didn't do anything for me, and that in my reading it only locks the app from being killed by you when you try to close it manually.
However in reading up on the oneplus framework-res.apk I found a reference to an oneplus whitelist of apps that will never be killed, and a reference to the recent screen app lock that suggests that oneplus will add a locked app to the whitelist and not kill it.
In the course of a single day, I had inadvertently edited the build.prop and locked the widget app to the recent screen thus breaking the one change at a time rule.
So the next morning and the following days when all apps were staying open I attributed it to changing the build.prop not realizing that it could also have been the app lock.
Last night I realized my mistake.
I unlocked the widget app from the recent screen and went to bed.
When I woke up this morning the widget app was not running for the first time in days.
Also the notifications that I was receiving about the widget app consuming excessive battery have stopped.
It would appear that I was wrong in my earlier observations regarding the app lock mechanism.
It appears to be very useful for keeping apps running all the time.
Did changing the build.prop have any affect on keeping apps open?
Maybe?
I have noticed that my battery life has gone for a complete ****.
I can barely get 24 hours out of the phone.
Worse is that it doesn't matter if the screen is on or not, battery usage remains the same.
i.e. with the screen off and the phone put down, battery life appears to be used at the same rate as when the phone is in use.
I had expected the battery life to be not as good, but I didn't expect it to go to for a **** that badly.
There must be a balance between aggressive app management and acceptable battery life.
The phone didn't display this behaviour until I changed ro.vendor.qti.sys.fw.bservice_enable=true to false.
I think that today I will change ro.vendor.qti.sys.fw.bservice_enable= back to true and observe the battery tomorrow.
kantjer said:
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
Click to expand...
Click to collapse
I think that ro.vendor.qti.sys.fw.bservice_limit= and ro.vendor.qti.sys.fw.bg_apps_limit= are essentially the same thing, except for android versions.
ro.vendor.qti.sys.fw.bg_apps_limit= is for Android 7: Nougat and below.
ro.vendor.qti.sys.fw.bservice_limit= is for Android 8: Oreo and above.
Someone more knowledgeable than me should chime in here though.
Do you think any of this could have to do with the way the phone keeps disabling push in Gmail? (Every other day I need to set my O365 exchange in Gmail back to push because it automatically changes to the default of checking every 30 mins.)
Any conclusion?
Did you guys manage to solve this issue please by editing the build prop?
Latest smurf kernel rc14b seems to have solved the RAM management issue. I haven't had any apps closing in background since using it.
thank you for the thread!
What did you find in the end?
How did you set this ?
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
So what's the verdict on the buildprop edits? Do they make a difference?
I notice that sometimes my on-going weather notification doesn't update, or gets killed off. I also have an app that controls rotation per app, and that also seems to stop doing it's thing after a while.
Just want to share. If you are rooted with Magisk, try appsystemizer module. System apps don't get killed by oneplus as aggressively. Tried it with accubattery and it works.
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
scloss84 said:
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
Click to expand...
Click to collapse
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
popy2006 said:
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
Click to expand...
Click to collapse
I'm actually Oneplus 6, OOS 9.0.9.
I also read that it doesn't work on Android 10 because magisk doesn't mount /system in Android 10, but there is a magisk module workaround that you can use. And hopefully magisk will update in the near future to fix that. Just google "Android 10 can't edit build.prop" and you'll find heaps of info.
This is what I have in my build.prop file and it seems to help. I have Oreo it works great on my phone I don't know about later versions of Oreo.
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
ro.sys.fw.bg_apps_limit=64