Related
[Solved] [Q] Battery drain due to "am2server" and "aes1750" on CM7
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.
masmddr said:
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.
Click to expand...
Click to collapse
I had the same problems. I think it's because I went from a previous non-FP enabled build without wiping then all the subsequent FP builds had this issue. Data wipe fixes it is all I know, I'm afraid.
Thank you for replaying.
I moved from Ba2tF without a full wipe and anything related to the FP didn't work, trying to set a lock screen returned a couple of errors.
But afterwards I did a full wipe and reapplied the zip of weekly #4.
This fixed the FP sensor for about 20 minutes, I eventually gave up and decided to wait for CM9; hoping it will work better then.
I am much more interested in the battery drain.
I don't want to go back to Ba2tF because I like scrolling with the sensor and I find it very useful.
Edit : seems that the problem was "fast reboot " application.
Stopped using it and so far am2server and aes1750 are acting normally, plus the FP scanner works fine.
Sent from my MB860 using XDA App
This is garbage, my 6P will not sleep anymore on 6.0.1. I am stock, rooted, ElementalX, and Xposed.
Not running anything to crazy but this wakelock is destroying my battery. Anything I can do short of a factory reset?
It's related to your location services. Do you have high accuracy for all apps? Maybe have location history enabled on Google Maps
I have both enabled. Prior to 6.0.1 this was a non issue. I have the same settings on my Nexus 9 on 6.0.1 and the device will not be held awake :/
This has been driving me nuts lately too. 6.0.1 stock rooted. The only solution I've found so far is Amplify to limit the wakelock but I'd like to keep Android Pay working... At least until they change root detection methods.
Probably a little late to this thread but I have a possible reason for this issue... I am not a developer so this is only based on my practical experiments..
I used to face this problem till very recently on my Nexus 6p.. no matter which kernel or ROM I use... some nights the phone doesn't sleep at all and then I see the culprit is nlpcollector wakelock. If I restart, the problem goes away for a day or two but then comes back again...
Then I noticed that every post I have seen with this issue on the internet has related to people with rooted phones (else you wouldn't be able to use BBS ) and most had made modifications to the doze parameters (using whichever app).. So I reset my doze parameters to default.. Since the last 2 weeks I haven't seen this issue anymore..
My guess is that one of my customized doze parameters is breaking the functionality but I can't figure out which one.. Tried resetting only the location based parameters but the wakelock returns.. My only solution is to reset all the doze settings..
Obviously the other solution is to set up xposed and download amplify or other such apps to block the wakelock.. I haven't tried it but should work..
PS - I still have location history on and location set to high accuracy. So that is not the culprit.
hi MI A1 owners.
for those brave enough to use the latest vanilla, official OTA rom, what change did you notice?
does the battery still suffer huge drain that appeared in 2018 roms?
it's a big "NOPE" for me to update, i'm still on official DEC rom because of this drain issue.
Battery life is good on 8.1 no issue for me getting 5-6 hours SOT on gaming.
Never had battery drain problems. Only "issue" is notification led not blinking.
Just noticed that led light is no longer blinking when notifications arrive. Light stays on only when screen is off. Also Bluetooth is constantly disconnecting.
Ambient display isn't working for me.
Led notifier is also not blinking anymore!
Led not blinking, proximity sensor doesn't work properly all the time, some scrolling lag. That's what I've got so far
dudes thanks for your answers.
i'm just more convinced to not doing the update.
maybe the drain i had was magisk-related. (?)
Nothing for me, even got ten hours of screen after some cycles. Led doesn't bother me and it's the only thing i noticed.
Yes, the LED is always on, which is annoying, but the bigger issue is there is no change in the battery drain. I charged to 100%, set the phone down and did not move it or use it overnight. 8 hours later almost 14% of battery was drained. I have tried everything I can think of to try, including turning off high accuracy location, not allowing any location things like safe area, etc. and still I get this drain even when the phone is not in use. Android kernel and system consumed 85% of that usage, and System UI, Play Store and Phone Services accounted for 7%! SO basically, basic Android paired with the A1 hardware seems to be the issue and I don't know that there is any fix for that.
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
KB_Thailand said:
8 hours later almost 14% of battery was drained.
Click to expand...
Click to collapse
Dunno what to say man. Mine is below.
2-3% at most over night.
And now it would appear that there is an issue with airplane mode.
I put the phone into Airplane mode at 2300 last night with 90% battery and did not pay attention to it. This morning I turned to phone on to find there was only 69% battery left, and WiFi was working. (see screen shot) WTF???? I have started using airplane mode to keep the battery drain to a minimum when the phone is not in use, and now it would appear that this doesn't work either.
I am REALLY getting frustrated with Android and Xiaomi as it seems that every time they do an update, something else goes bump! I have gone from totally happy with the AI when I first got it to being ready to write off Xiaomi as a company I would consider for purchase.
IjazCI said:
Is your WiFi scanning is on. ( Under location / scanning)
Play services also cause these type of sudden battery losses.
Try downloading latest play services apk from apkmirror . Latest one is
"com.google.android.gms_12.8.74_(090408-204998136)-12874034_minAPI26(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk"
Uninstall your current one. Install this .
Power off your phone for a few seconds and reboot.
Click to expand...
Click to collapse
Thanks for the thoughts, but unless I totally misunderstand what airplane mode is, WiFi should not be active when airplane mode is invoked. You can see by the screen cap that airplane mode is on AND WiFi is active. This seems to be a one off as it has not happened again for the last two days. I turn airplane mode on to stop the overnight battery drain while the phone is doing nothing. I have location set to GPS Only. IIRC play services was just updated 3 days or so ago, so it should have the latest version. I will check it and see though. Again, thanks for the thoughts.
KB_Thailand said:
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
Click to expand...
Click to collapse
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
ludditefornow said:
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
Click to expand...
Click to collapse
Actually, I think it is a combination of hardware/software, but that is just a WAG. Others have noted the exact same issue without running the same software. My bet would be on the RCS services stuff.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
Click to expand...
Click to collapse
Those icons are my Email client and GSAM Battery Monitor (presently 0.1% and 0.8%) and are the only two constantly running programs other than the stock apps and Sophos (0.3%). Neither use much battery compared to the Android stuff. Presently Kernel is 41.6%, RCS/Phone is 30.3%. SystemUI is 3.3%, Play Services is 2.0% and Phone Services is 1.8%
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
Click to expand...
Click to collapse
Good advice. I will do this when I have a few days to play with it. In the interim, it's airplane mode every night. Thanks for the reply. If it turns out to be one of these apps, let me know where to send the Singhas.
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
For me, night light auto schedule not working properly.
I can't tether via wifi/bluetoth/usb
Made another post with the problem.
ludditefornow said:
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
Click to expand...
Click to collapse
Just for grins and giggles, I uninstalled my email client, GSAM, and Sophos, the only programs that run constantly other than system and Line. I then turned my phone off and back on, forced stopped Line, charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed, but still not close to what I would consider normal. When I first got the phone, it easily lasted 2-3 days between charges, with 6-7 hours SoT. Overnight would use MAYBE 2% of the battery. Now if I want it to last 2 days I need to turn on airplane mode overnight and then I can make it through a day.
So I guess the next step is to do as you recommended and load up the fresh rom when I have time to mess with it. At least I am now pretty sure that those apps aren't the culprits causing the biggest part of the battery drain. I hate to do it, but I am seriously thinking of a factory reset and seeing if that clears the issue. Would that put me back to Nougat?
IjazCI said:
I always disable carrier services apk. As rcs is not here in India.
Click to expand...
Click to collapse
How do you disable this apk? I seriously think this is the major culprit in the battery drain.
KB_Thailand said:
charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed,
Click to expand...
Click to collapse
So those apps were causing 40% of of the 20% of the battery drain. That is a good start. I am confident there are software issues with your phone. I see you have some GPS app on your home screen, if that was running askew, it might be constantly pinging. That is just a guess.
In things like this, work methodically through it. But of cause a hard reset would be the best way to go. I see no reason why you wouldn't stay on your current version after a hard reset.
If you want to go make to version 7 you would need to use the MiFlash program and a downloaded standard fastboot rom. You may need to do something else to the phone to go back to 7, but I would not think so.
Has anyone experienced any issues on the 9.0.6 update?
I've noticed slowness on the accuracy of face unlock and fingerprint compared to 9.0.5
I've also noticed some lag in speed and apps just randomly closing, not crashing, just closing.
Anyone else experienced these or other issues? Post and these will be shared with OnePlus for review.
Nova Launcher crashes randomly like 1-3 times a day.
Higher idle drain in comparison to 9.0.5.
Rest everything seems normal to me on 9.0.6.
I have had some apps just close. Also get freezing with Nova launcher at times. I cleaned the cache for all apps in TB and that seems to have fixed the problem for now.
Sent from my ONEPLUS A6013 using Tapatalk
Absolutely no problems here.
No Issues with Nova and battery runtime
No issues with performance or anything compared to 9.0.5
SOT for me is lower and idle drain is definitely worse for me and a number of others, with regards to performance it's around the same
Has been behaving like 9.0.5 here.
Troubles with Bluetooth headset / car. I think it's when i have switched from one to another (Car - Headset and vise versa), then you are able ho hear the calling part, but the opposite part are not able to hear you. If you reboot the phone, the bluetooth will work again until next time you change bluetooth device.
The use of Dual-Sim on Android Auto are still impossible. You can't even, if you make a call from Android Auto, make the choice on the phone, like you were able to in previous versions (OnePlus 2)
Absolutely no issues here.
Don't know if it's 9.0.6 related, but fingerprint reader unlock appears to be a bit quicker from the actual lock screen rather than the ambient display... Also oddly at times my ambient display will be missing the fingerprint icon (which actually I kind of like, lol) ... no also nothing is covering proximity sensor, I just place my finger where the icon should be and it lights up green still and unlocks like normal. Another issue related to unlocking seems that going from ambient to home screen [via fingerprint] is glitchy while going from lock screen to home screen is much smoother [via fingerprint]... Other problems I've noticed are relative to the force closes you guys have mentioned and I can't recall having similar issues 9.0.5...I was even wondering about a the possibility of downgrading just for the sake of running comparisons.
-I get "ghost notifications" sometimes. Mostly from Download Manager, something I downloaded days ago. Can still show up from time to time on Ambient Display but it's always gone when I turn on the screen again. Yesterday it was the same from Play Store though.
-I get too much stuttering in animations for my liking. Phone needs optimization. I'm not even a heavy user. Not close to it. Still it stutters from time to time and sometimes heavily like 10-20fps.
-Tap to wake is a little bit unreliable at times and wont work the first try.
Lately I have this problem with my gps. When screen is off and the device is not plugged in, the accuracy is bad. it seems as though it switched back to "cell towers" only. When recording my position using any app (like Strava or Locus) the position is far out of range until I switch on the screen: I can see the pin being restored to the correct location and follows me correctly until I switch off the screen again.
I did a lot of research but I only can find suggestions like "switch on high accuracy" which I obviously have switched on.
Anyone notice this same behaviour?
Any solutions?
I'm on the latest stock ROM: OxygenOS 9.0.5 (non-root)
thanks!
auricgoldfinger said:
Lately I have this problem with my gps. When screen is off and the device is not plugged in, the accuracy is bad. it seems as though it switched back to "cell towers" only. When recording my position using any app (like Strava or Locus) the position is far out of range until I switch on the screen: I can see the pin being restored to the correct location and follows me correctly until I switch off the screen again.
I did a lot of research but I only can find suggestions like "switch on high accuracy" which I obviously have switched on.
Anyone notice this same behaviour?
Any solutions?
I'm on the latest stock ROM: OxygenOS 9.0.5 (non-root)
thanks!
Click to expand...
Click to collapse
Maybe you did not exclude your apps from battery optimization? I have no issues using orux maps (OB33).
Thank you for your response. I should've mentioned the battery settings I already activated:
battery optimisation for the apps are off.
apps are locked in the recent apps so that they're not being killed and removed from memory
Deep optimisation and Sleep Standby Optimisation are off
Is it possible that I missed an optimisation?
Btw, it seems to be app unrelated: when I lock the GPS in Locus (recording position) and activate Strava as well, both apps record the same inaccurate position.
auricgoldfinger said:
Thank you for your response. I should've mentioned the battery settings I already activated:
battery optimisation for the apps are off.
apps are locked in the recent apps so that they're not being killed and removed from memory
Deep optimisation and Sleep Standby Optimisation are off
Is it possible that I missed an optimisation?
Btw, it seems to be app unrelated: when I lock the GPS in Locus (recording position) and activate Strava as well, both apps record the same inaccurate position.
Click to expand...
Click to collapse
The GPS on the OP5 is known to have glitches where it suddenly shoots off to another location. I've found this yusing my Canon Connect app to record the location of my pictures.
Alan
alan sh said:
The GPS on the OP5 is known to have glitches where it suddenly shoots off to another location. I've found this yusing my Canon Connect app to record the location of my pictures.
Alan
Click to expand...
Click to collapse
I never had issues with GPS and there's no general problem with GPS.