Related
Could some kind soul please tell me what the following processes do?
sensorserver_ya
drexe
rild
events/0
mmcqd
pvr_workqueue
Thank you!
I saw your posts in the battery life thread and dig some digging after looking at my SystemMonitor results. These are pretty much all showing up in my System Processes list as well. Here's what I've found so far:
sensorserver_ya - Tied to the use of the accelerometer. This was showing constant CPU usage while ShootMe was running because it actives by shaking. As soon as I stopped ShootMe, this disappeared.
drexe - This one was showing almost constant 1% CPU usage. According to this thread, drexe and another process are both for some Samsung software called NPS(New PC Studio,) which I have never used and don't plan on using. I took the advice of the post and disabled them using adb. I'll report back results after a day or so.
Let me know if you've found out anything about the rest. Maybe bumping this thread up will get some more eyes on it
Gix0r said:
I saw your posts in the battery life thread and dig some digging after looking at my SystemMonitor results. These are pretty much all showing up in my System Processes list as well. Here's what I've found so far:
sensorserver_ya - Tied to the use of the accelerometer. This was showing constant CPU usage while ShootMe was running because it actives by shaking. As soon as I stopped ShootMe, this disappeared.
drexe - This one was showing almost constant 1% CPU usage. According to this thread, drexe and another process are both for some Samsung software called NPS(New PC Studio,) which I have never used and don't plan on using. I took the advice of the post and disabled them using adb. I'll report back results after a day or so.
Let me know if you've found out anything about the rest. Maybe bumping this thread up will get some more eyes on it
Click to expand...
Click to collapse
Hi Gix0r,
Sorry for the late reply; I have not been spending much time in the forums these days.
Good job with the "digging" to find the purpose of the system tasks. What was your result from disabling drexe?
Thanks,
Bruce
Safely Dis-ablable System Processes
Although it applies to an earlier model phone, here is another link that underscores your last comment and has other ideas:
http://einartysen.se/tweak-your-android/
sensorserver_ya also works with GPS... Had this running while running the gps test thing.
TheManii said:
It's widely known that the s7 has pretty weak battery life.
In general all qisda dell devices do (the s5/s7/venue).
Many of the bugs exist in the phone/ril and some exist in the logging systems.
In a bug free rom these workarounds should be completely meaningless, but stock roms are not at all bug free.
Recommendation one: Enable airplane mode on wifi s7's
The wifi and 3/4g roms are nearly identical, including the fact that wifi roms still have a full RIL. It apparently is also still enabled even in wifi s7's. Turning airplane mode on while leaving wifi/bluetooth on (as desired) does in fact affect the system.
Ways of checking: with airplane mode off on mine, the s7 has major issues going into sleep mode. Even with the screen off if you check the battery graph it's still active most of the time. Airplane mode more or less fixes this.
Potential gains: 20-30% or so more life, I've only been testing this for half a day or so but it seems to be draining signifigantly slower in sleep.
Recommendation two: (this one is more valid for the s5 then the s7) Connect the s7 to a pc with the android SDK installed and run 'adb logcat'
The qisda devices are known to have far too much logging enabled and included in stock roms. Virtually all the custom roms for the s5/7 have it removed, but there is a known bug with logging.
If you run logcat so the output is directed to it, afterwards it takes care of another one of the bugs. I have not actually tested this specifically on the s7, but it likely is equally valid as the differences from AOSP (ie the customizations qisda does to the roms) are pretty similar in the s5 and s7.
Potential gains: nearly triple battery life after logcat and avoiding a yet different ril bug on the s5. The s5 can go from potentially 10%/hour to 0.3%/hour due to all/no bugs being active. The s7 MAY be a valid target too, but I havnt actually tested this one on the s7.
Roms used to compare:
S7: Stock 506-wifi
S5: Custom 406 based rom
Click to expand...
Click to collapse
Crosspost from the S7 forum, both are valid on the s5.
The largest battery bug is in the RIL, way of activing the bug: make a call. If you reboot everytime after making a call the battery life is much better then if you dont restart. Depending on how often you make calls though this is completly unacceptable to reboot after each call.
Are you saying that removing logcat daemon would give more battery life?
If I am not mistaken, that seems a obvious thing, am I wrong?
But if you remove the logcat daemon, then you can't hunt the bugs anymore, so for custom Roms that would be a very high price to pay for so little gain.
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
So redirecting output from /dev/null to /dev/tty1 improves battery life ? Seems highly unlikely to me.
Can you explain the methodology used in your tests, bcs we can go somewhere this way, bcs s5 seems to have not a good battery life, and some strange things i have observed too in this device.
It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.
TheManii said:
It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.
Click to expand...
Click to collapse
2-3 % standby per hour is way too much , i am running the latest DSC 0.64b on top of 407 BB and have around 1-1.5 % , but that seems too much for me , you should check the background processes i think.
I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.
TheManii said:
I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.
Click to expand...
Click to collapse
So then something wrong with my system then, what Rom you running ?
TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?
It's a heavily modified SD 2.4.4
The RIL bug seems to be more noticible in GB, I dont recall if it existed in 3xx roms. The logcat one is possible in 3xx or newer roms.
lunadomain said:
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?
Click to expand...
Click to collapse
It's really voodoo/magic, attaching it for <some unknown amount of time> will fix it for <some random amount of time>
For me it seems I just attach it until the battery is charged (as I would charge it anyway) and it seems to last for a day to a couple days. It's as voodoo as it sounds.
It doesnt stick past a reboot and more importantly the RIL bug is the more noticable one anyway.
It's only really noticible when the ril bug isnt active, as then you're going from 2-3% to 0.3%/hour. Going from <10% to 3% overshadows it if it's even active at all.
I cant really say for certian if it even effects everyone or happens every boot. I've been on the same rom for 2 months and have extremely consistant data with regards to these two bugs.
The logcat one is just as consistant for me on SD 19x roms.
You can also do it without SDK installed, you just need to download terminal emulator from market and enter:
su
logcat
And you are ready
At least when I do it, i use it as an opportunity to charge anyway. I always do it on my pc as I need the SDK for other things so I always have it installed.
On a custom SD244 not OCed with airplane mode and after running logcat previously with wifi turning off when screen is off:
getting 15hours @5% lost.
I'm gonna keep testing till tomorrow then install 407
Surprisingly: the s5 has even better battery life then the s10 (ignoring the differences in battery life).
The s10 has amazing battery life too.
Current results:
S5 : 31 hours = 24%
S7 : 54 hours = 48%
S10:61 hours = 13%
Normalizing their results to the size of the S10's batt:
S5: 5.17 hours each %
S7: 2.63 hours each %
S10: 4.7 hours each %
Roms used:
S5: SD 2.4.4 <2.3.3>
S7: Stock 506-wifi <3.2>
S10: Chimeradroid r2 <3.2>
The S5 can be explained by the RIL bugs as mentioned earlier, and by airplane mode is also turning off the radio too. All 3 devices were left to idle for the entirety, with only battery graph checks and no actual use.
Guys , i have a really vad problems with my battery life. After i go on to Power Rom EVG (before that i was with StreakDroid 2.4.4) my battery is absolutely not good. I do this logcat trick, just a few programs is running, auto-brighness and ... nothing! please, help!
Hi - newbie here hoping to get to the bottom of my battery drain problem.
Somewhat unusually I think, I am seeing problems only when I have wi-fi switched on. It took me a while to realise as I have wi-fi at work and home and I wouldn't normally have turned wi-fi off as I always understood that 3G uses more power.
I tried installing BetterBatteryStats but I am not rooted so it is only giving limited information. What it does tell me is that I am draining the battery at a rate of 9% or so an hour on wi-fi and about 1.4% on 3G. This is with very light or no actual use of the phone. The top two wakelocks by a big margin are msm_hsic_host and PowerManagementService.WakeLocks.
I have virtually nothing running according to my running processes list - mainly the Google ones like Google Play Services, Google Keyboard.
I couldn't put my finger on exactly when this started but it was towards the end of 2013. I did have the really bad drain with Google Play for a few days until the next Android update came. What I'm seeing now is not as bad as that was. I couldn't say whether I had a period after that update when things for a while were better than they are now but my feeling is that things have never been great since the 4.4 updates.
Does anyone have any suggestions please? Am I going to have to root to get better info to debug this problem?
OK, I'm too having this problem and couldn't find any concrete solution for this.
Without full use of batterystats application, the information that you provide don't help much.
Could be many things.
Unleashed by my Nexus 4
Good day to you all,
Recently after a small android update (still having version 4.4.2) I noticed the battery was draining faster than I'm used to. Before that, it was consuming roughly 1% per hour in idle. This has changed now to 3-5% per hour. Looking at the battery info I noticed the Android system was the biggest batterysucker here. Not only that, there are even TWO Android systems shown and I began to think there's something wrong here.
http://forum.xda-developers.com/attachment.php?attachmentid=2908920&stc=1&d=1408796626
Also looking at the wakelocks shows that my phone is barely able to get into sleepmode.
http://forum.xda-developers.com/attachment.php?attachmentid=2908921&stc=1&d=1408796626
Before posting this thread I have literally tried every option to see if it could lessen the battery consumption:
- Disabled Google location reporting services
- Disabled GPS
- Disabled Google sync
- Disable Wifi when in Sleep mode
- I don't use Google Now so it's disabled
- Widen the Facebook refresh intervals to 4 hours
- Wiped the cache partition
None of the above worked and I started to think that the second Android system here might be the cause.
Should there be a second Android system consuming battery? What could be the problem here??
JohnnyGui said:
Good day to you all,
Recently after a small android update (still having version 4.4.2) I noticed the battery was draining faster than I'm used to. Before that, it was consuming roughly 1% per hour in idle. This has changed now to 3-5% per hour. Looking at the battery info I noticed the Android system was the biggest batterysucker here. Not only that, there are even TWO Android systems shown and I began to think there's something wrong here.
http://forum.xda-developers.com/attachment.php?attachmentid=2908920&stc=1&d=1408796626
Also looking at the wakelocks shows that my phone is barely able to get into sleepmode.
http://forum.xda-developers.com/attachment.php?attachmentid=2908921&stc=1&d=1408796626
Before posting this thread I have literally tried every option to see if it could lessen the battery consumption:
- Disabled Google location reporting services
- Disabled GPS
- Disabled Google sync
- Disable Wifi when in Sleep mode
- I don't use Google Now so it's disabled
- Widen the Facebook refresh intervals to 4 hours
- Wiped the cache partition
None of the above worked and I started to think that the second Android system here might be the cause.
Should there be a second Android system consuming battery? What could be the problem here??
Click to expand...
Click to collapse
Hi ,
is hard to tell with what you show here...get an app like Better Battery Stats
http://forum.xda-developers.com/showthread.php?t=1179809
Let it run for 3-4 hours and check it , the app will tell tell you what is going on....is the only way to find the real culprit
MAX 404 said:
Hi ,
is hard to tell with what you show here...get an app like Better Battery Stats
http://forum.xda-developers.com/showthread.php?t=1179809
Let it run for 3-4 hours and check it , the app will tell tell you what is going on....is the only way to find the real culprit
Click to expand...
Click to collapse
Will this app also show the needed info even when my phone isn't rooted? Because I'm really not into rooting it.
JohnnyGui said:
Will this app also show the needed info even when my phone isn't rooted? Because I'm really not into rooting it.
Click to expand...
Click to collapse
Hi mate
This is from the thread :
Q:Why installing BBS as a system app as everything works with root?
A: Starting with Kikat BBS has 3 modes: without root a limited mode provides a minimal set of stats. With root the set of stats is complete but some stats (other, partial wakelocks, processes) still use a workaround. Finally with the system app BBS is fully featured without any workaround.
For this cases root is good to have as it gives you a better access to all the process running , try without root and see what kind of info you get
If it's a conciliation, my android (currently on AOSP) is also running two android systems. Not exactly the same name (Android-System and Android-Besturingssysteem), but you get the idea. You mentioned quite a few things you've already tried, but what about existing widgets and or android apps you've installed? Usually (for me anyway) battery drain is an installed app not exactly behaving nicely.
MAX 404 said:
Hi mate
This is from the thread :
Q:Why installing BBS as a system app as everything works with root?
A: Starting with Kikat BBS has 3 modes: without root a limited mode provides a minimal set of stats. With root the set of stats is complete but some stats (other, partial wakelocks, processes) still use a workaround. Finally with the system app BBS is fully featured without any workaround.
For this cases root is good to have as it gives you a better access to all the process running , try without root and see what kind of info you get
Click to expand...
Click to collapse
So does this mean I'm not able to see the exact cause of my wakelocks since my phone isn't rooted?? I have installed Gsam Battery monitor from Google Play, hopefully it will give me (and you guys) the relevant information after keeping my phone on idle for a while.
@Skyrider: The weird thing is that in my case, it DOES display the same name twice. Doesn't that seem weird? I can't see any Android OS (besturingssysteem) displayed.
Also, if I have a battery heavy app, shouldn't it be displayed in the battery info screen as well? I only have the Weather widget and a News widget (NU.nl) on my homescreens. Haven't installed many apps except for Facebook and a few games that barely use background processes.
JohnnyGui said:
So does this mean I'm not able to see the exact cause of my wakelocks since my phone isn't rooted?? I have installed Gsam Battery monitor from Google Play, hopefully it will give me (and you guys) the relevant information after keeping my phone on idle for a while.
@Skyrider: The weird thing is that in my case, it DOES display the same name twice. Doesn't that seem weird? I can't see any Android OS (besturingssysteem) displayed.
Also, if I have a battery heavy app, shouldn't it be displayed in the battery info screen as well? I only have the Weather widget and a News widget (NU.nl) on my homescreens. Haven't installed many apps except for Facebook and a few games that barely use background processes.
Click to expand...
Click to collapse
Let us know what you find ....good luck
JohnnyGui said:
The weird thing is that in my case, it DOES display the same name twice. Doesn't that seem weird? I can't see any Android OS (besturingssysteem) displayed.
Also, if I have a battery heavy app, shouldn't it be displayed in the battery info screen as well? I only have the Weather widget and a News widget (NU.nl) on my homescreens. Haven't installed many apps except for Facebook and a few games that barely use background processes.
Click to expand...
Click to collapse
In my opinion, that's the problem with the default battery information. In my years of experience, it usually never knows the information that you need what exactly is braining the battery. If your battery is still being drained, I suggest to remove most of your apps. Only for a day orso. It should be enough to gather the information to know that at least one of your apps was the cause of it.
It's a pain to do it. But It always has helped me rather than relying on apps of which usually doesn't work out for me.
Also. Might be a good idea to alter your system language from Dutch to English and check the battery info again to search for the duplicate running system on google. You'd expect "Android System" being enough, but who knows that a different language might show a different name.
Ok, I don't have the slightest idea what happened but my battery duration is amazing now. After installing Gsam Battery Monitor and charging my phone to 100% I went to sleep and after 10 hours of standby I looked at my phone and it was on 93%. My phone doesn't consume more than 0,6-1,0% per hour now in the last 3 days!!
I haven't changed anything except choosing to use Wifi and mobile network for location services but not GPS. Weird thing is that I tried that option before without success.
I'm happy now
I'm still confused about the 2 Android systems in my battery info screen though. That might be a good idea to try @Skyrider but I do remember that "Android OS" was displayed differently in Dutch a while back. I'm guessing you have your phone language in Dutch as well since you're seeing "Android Besturingssysteem" on the battery info screen?
JohnnyGui said:
Ok, I don't have the slightest idea what happened but my battery duration is amazing now. After installing Gsam Battery Monitor and charging my phone to 100% I went to sleep and after 10 hours of standby I looked at my phone and it was on 93%. My phone doesn't consume more than 0,6-1,0% per hour in the last 3 days!!
I haven't changed anything except choosing to use Wifi and mobile network for location services but not GPS. Weird thing is that I did try that option before without success.
I'm happy now
I'm still confused about the 2 Android systems in my battery info screen though. That might be a good idea to try @Skyrider but I do remember that "Android OS" was displayed differently in Dutch a while back. I guess you're having your phone language in Dutch as well since you're seeing "Android Besturingssysteem" on the battery info screen?
Click to expand...
Click to collapse
Kudos for the battery mate.
JohnnyGui said:
I'm still confused about the 2 Android systems in my battery info screen though. That might be a good idea to try @Skyrider but I do remember that "Android OS" was displayed differently in Dutch a while back. I'm guessing you have your phone language in Dutch as well since you're seeing "Android Besturingssysteem" on the battery info screen?
Click to expand...
Click to collapse
Yea, I'm using the Dutch language. But I'm not using the stock ROM of the phone, so hence I am seeing different systems running in the background. But I'm glad the battery is semi-fixed.
Ok, so I changed my phone to English and behold, one of the "Android Systems" indeed changed to "Android OS"
I could have sworn it was like that when my phone was in Dutch.
Perhaps someone with the stock ROM in Dutch could check that out?
No idea if this helps but i thought might as well contribute what it sais on my phone
Edit : i have a very high idle battery drain so any advice is welcome btw
Sent from my GT-I9505 using XDA Free mobile app
Stefan0vic said:
No idea if this helps but i thought might as well contribute what it sais on my phone
Edit : i have a very high idle battery drain so any advice is welcome btw
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot for confirming this! I guess Android OS is indeed translated to "System" for Dutch S4's.
Have you tried my suggestions in the opening post?
Overheating on my Galaxy S4.
I have a Galaxy S4 for about a year, I have this problem almost since I bought it, but it appears and reappears, so I let it go.
My Galaxy S4, using WhatsApp Music and the CPU temperature rises to just using these programs 45-50ºC
Using only the poweramp the instrument reaches 65c for no reason.
Using browser is hopeless, the device rises to 50-70 degrees and finally restarts or shuts down.
When I bought the unit in the first week I realized that he was heating a lot, but did not reach this temperature (50-70) normally.
I read in various forums that the normal temperature of the Galaxy S4 units were 35-56c
Recently, I downloaded a few albums of music and some pictures on my phone that day he shot and started this strange behavior, and following the same steps bellow, the problem still persists.
I already own a Galaxy Note and I have witnessed the bug "AndroidMediaScanner".
I did all the steps (exeto formatting the MicroSD, I recently formatted to exFAT SD) Until I checked the status of the reading process of media using the Android ADB, there was nothing abnormal ..
Even without the memory card, few files in SD (just applications) the problem still appears.
What do you think? It may be a hardware problem that requires replacement?
It may be the battery?
It may be the ROM • (when the OmegaROM use a series of modules Xposed)
Recently reinstalled the ROM and the problem still persists.
I read in a blog that the DS Battery Saver could be giving conflict with the manager's native battery used in the Galaxy S4, I uninstalled the program, yet the problem persists warming.
Connected to the USB temperature suddenly increases to 65c without any reason or use.
What recommend?
Sorry for the English. I used Google translator.
Maybe i attach prints.
My initial thought would be to get a new battery. Becaus it jumps so drastically when you start charging it. You could also check your battery connections. Make sure they are free from dust and corrosion.
Hey Girafa, missed u man. :/
KevSanches said:
Hey Girafa, missed u man. :/
Click to expand...
Click to collapse
xD
I sent him the link to the forum Galaxy s4 was not?
SocratesDemise said:
My initial thought would be to get a new battery. Becaus it jumps so drastically when you start charging it. You could also check your battery connections. Make sure they are free from dust and corrosion.
Click to expand...
Click to collapse
Ever encountered moisture near my battery (cover).
I try to buy a battery when you can.
But do you have any recommendations?
thxz for quickly reply.
GiRaFa-SAMA said:
Ever encountered moisture near my battery (cover).
I try to buy a battery when you can.
But do you have any recommendations?
thxz for quickly reply.
Click to expand...
Click to collapse
You have to find the "service" that is turning in background....
If you mind it is the AndroidMediaScanner, I can say from experience ( it was killing my battery in less than 5 hours)
I stopped this issue (flaw) by cleaning one by one my Music folders and deleting those empty or having no music file in it ( that sometime comes when you clean a directory from the music player interface) .
then my phone turning back to normal temperature state.
lolo9393 said:
You have to find the "service" that is turning in background....
If you mind it is the AndroidMediaScanner, I can say from experience ( it was killing my battery in less than 5 hours)
I stopped this issue (flaw) by cleaning one by one my Music folders and deleting those empty or having no music file in it ( that sometime comes when you clean a directory from the music player interface) .
then my phone turning back to normal temperature state.
Click to expand...
Click to collapse
I said in the text that has nothing wrong with MediaScanner Android. I used the Android Debug Bridge to verify this and it appears to be normal.
The application showed 10% CPU usage when the unit was starting.
I used OS Monitor app (it shows up the processes of the Linux kernel and user) in order to find some buggy process that was doing it.
I removed 4GB of external memory file and checked the Android Debug Bridge MediaScanner if the process had been stuck at some file storage.
There was no error in both stores.
I witnessed this primary failure of the Android system twice on my old Galaxy Note.
Thxz for reply.
whats the solution