Database Users

Excessive CPU usage on X10

Hi
I've just recently bought an XPERIA X10 and one issue I have found is its apparent heavy CPU usage. I would go so far as saying that the phone is close to unusable when it has just booted. So here goes my findings...
I've installed a program called CPU Usage (quite logically) which monitors CPU usage for various tasks on the phone. Here is what I get when the phone has just been booted:
PID / Name / CPU Usage
954 / Sync Feeds/Checking Service/Setting Storage/Android System / 39-58% (No, I'm not kidding)
1054 / Download Manager/DRM /23-31% (still not kidding)
1171 / Face Recognition Service / 11-12% (not as bad, but still, why is it even there???)
The worst thing is that these services don't stop using the CPU - no, they keep on running and using CPU in the designated ranges, unless I kill them.
So I go and kill them using another program I installed.
I found out that if I kill the Face Recognition Service, the CPU usage of the DRM service disappears as well. So everytime I start the device, I have to go kill this service so I can actually use the phone.
The Sync Feeds/Checking/Android service I can't kill, but even though CPU usage reports it as using between 40 and 60% CPU, it seems that another task manager do not report this CPU usage. I can also live with this, if it's a kind of background service that doesn't actually use half your CPU all the time.
So I guess my biggest problem with this is that the Face Recognition service that is run on startup takes many CPU resources, and I have to manually kill it so the phone is running at an acceptable speed. I can't explain why I get different reports for CPU usage on the Sync Feed/Android service, but maybe others can explain...
regards, Artur

You don't need to kill the background processes every time you start up, there is a program that lets you customize which programs and services start on boot, it name is startup auditor. It alseo lets you kill moxier services and timescape

If you use TaskManager you'll se that Moxier doesn't use much CPU at all. It's probably the system in general that uses it.

Which apps I can kill?

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

Difference in Autorun Killer and Starup Auditor

Hi!
I have Autorun Killer and Startup Auditor installed and both show me different apps that are supposedly starting up on their own.
Autorun Killer has also two entries for some apps, like Autokiller for instance, while Startup Audito has only one.
Can somebody recommend a good startup manager? I'm also wondering which apps can be removed from the automatic startup.
Would be great if someone could clarify that for me.

i use this one Startup Manager
http://forum.xda-developers.com/showthread.php?t=765081
it's safe, and it doesn't close application randomly, because you only disable the software that you don't want
it's very easy to use

Startup auditor let's you disable apps and drivers/services from starting. Good for turning off email if you use third party app like k9. Also good for services like samsung social network hub as i don't use it and wastes ram just running. I use" startup manager" too. I think everyone does
Sent from my GT-I9000 using Tapatalk

I just though that since Autorun Killer is from the same guy as Autokiller it might be just as good...

How do you save your battery from draining

As all our custom roms are in devlopment there is still battery draining issue but i found a some ways to maximise the battery
1 setcpu
use setcpu and set minimum frequency to 128 in stock rom it is set as 245 so change it also i think some of us dont know the profile function in setcpu i have set as when the screen turns off the cpu should run on minimum frequency ie 128
2 titanium backup
use this app to freeze some of the application that starts automatically on startup
you can also use diffrent freezing apps that are available in the market i use this app
3 cyanogenmod settings
in the performance setting disable all the options ie use of jit compiler , surface dithering etc and also set VM heap size to 24 or 16 belive me or not this is not affecting the performance to much extent still i am getting quadrant score greater than 1000
4 use of 3g
with diffrent experiments i have learnt that wifi consumes more battery than 3g i
am also not sure this is true or not
this are some of the setting you can use to increase your battery you can also
use automatic task killer, decrease brightness,turnoff background sync,disabling live wallpaper, use of 2g connections etc etc.
with this setting i am able to save my battery for more than a day
also guys tell me what you do to save your battery
if you like my post pls thank

Its a shame that the battery capacity is too low in these phones. Anyways this is what I do to extend the battery:
1. Use auto-brightness (in froyobread ROM)
2. Use automatic data disabling applications
3. Only 1 application gets internet connection for auto-sync when phone is idle (so the other ones can use that gap to sync too)
That's all.... you may want to set your account auto-sync off... but that's no good if you rely in gmail, google calendar, etc...

I have read somewhere that task killers "kill" the battery!
Don't use them! You'd better use apps like Fast reboot!
And about titanium backup..
Freeze (or delete) the Email.apk not Gmail.apk.
Also the Maps.apk if you don't need it!

anant123 said:
I have read somewhere that task killers "kill" the battery!
Don't use them! You'd better use apps like Fast reboot!
And about titanium backup..
Freeze (or delete) the Email.apk not Gmail.apk.
Also the Maps.apk if you don't need it!
Click to expand...
Click to collapse
Advanced Task Killer does that on my x8.

I use some tips from here: http://forum.xda-developers.com/showthread.php?t=726381
and use powermax from the market.

in my experience,in the night my battery 40% left i let my data traffic turned off and 2g only network, i let the music played with phone speaker 50% volume.
im falling a sleep, and in the morning i still hear the music and the battery 8% left.
i use froyobread

How to disable/adjust the background task limit?

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