[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
I posted a while ago about the GPS failing to find even a single satellite. I got no responses, just a redirect to this forum. Since then I have searched and searched but no one has a solution to this common problem. I watched a video about cleaning the antenna contacts and performed this cleaning - no help. I have tried numerous apps that are supposed to help - no help. I took the tablet out of its case - no help. I even set the tablet out in the backyard for 45 minutes with a GPS app running as was suggested by someone - no help. I can't find anything at all about updating or re-installing GPS drivers or firmware so i don't know if that is even an option, but if there is a way to do this I would sure like help trying that. I have Titanium backups from before the GPS outage but I don't know which ones control the GPS.
It is as though this is a taboo subject and no one wants to even talk about it, but I did see that LOTS of people are having the same problem. Doesn't anyone have a solid solution short of just buying a new tablet? The GPS worked on a flight from TX to TN last March but never worked again after that. Could something on that flight have jammed or disabled my GPS?
If anyone has a solid solution based on actual resolution of this same problem, a lot of people would appreciate knowing about it.
Thank you.
Oooh i luv a good conspiracy! xD
Although i don't think taboo has any thing to do with it, now, if we were talking about dwarf elephants,sodomy and juggling then that would be troubling! But i think the empire is too busy tripping over the trump disaster to jam your gps. xD
okay, start by cycling through your back ups and find the one that worked, though i don't know much about titanium backup. It would have been smarter to use an actual recovery to make you backups.
The reason most common for not finding an answer or even a lead to one is insufficient data.
I have a tab4 and gps doesn't work, is literally nothing to go on.
What OS and/or firmware were/are you running? Did you install a custom kernel? Did you modify your OS with questionable applications or modifications that came at a cost or broke something?
What tab 4 is your tab 4? there are about 11-16 of them. Specifying the 8.0 is still not good enough.
It is interesting that you got some function on a flight. That's definitely worth a ? . I don't think a "jamming device" would fry your gps though.
I would say that you should first restore your tab back to cherry, meaning the original state you purchased/recieved it in and walk your mod process forward. Take notes and get logs.
m
Moonbutt74, thanks for responding.
My Tab 4 8.0 is model SM-T330NU
It's rooted & has several of the nice apps that can be used on rooted devices. Nothing was added between the time the GPS worked and when I noticed it not working. I am ALMOST certain of that. If there were a way to check logs for changes maybe I could get a clue - hadn't thought of that 'till now. Do you know how to do that? I suppose restoration to original state may end up being necessary, but I would sure like to avoid that. Everything else works just as I like it except for the fact that Google is still spying on me. There's no stable custom ROM yet as far as I can tell.
Yes, GPS worked fine on several commercial flights. It's fun seeing things on the ground and seeing what they are on the map + knowing speed and ETA.
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
moonbutt74 said:
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
Click to expand...
Click to collapse
I have posted this in a new thread, but I'll tell you the short version: My Allow Mock Locations was disabled in Settings/General/Developer options/Allow mock locations...). When I enabled this my GPS started working. Such a simple thing but a total odyssey to find out about it. OB
Phone:
SM-G900R7 (rooted) | SDK 21/Lollipop 5.0 stock
History:
Unintentionally nuked OS via TWRP's "Fix Permissions" (big no-no), then used "Advanced Wipe" when I shouldn't have (was desperate to get Xposed working). Eventually got everything back up with this ROM[1] (same build identifier as on the other GS5s purchased at the same time as mine/under the same plan as me). I had no such audio problems before with this phone, but ever since flashing back to stock, my audio experience is doomed to have its immersion broken by way of little split-second hitches, driving me bonkers with wanting to just know why, why, why. In a recent attempt to fix this problem, I did a backup through Titanium, then TWRP, then Advanced Wiped Dalvik/ART, System, Data, and Cache, but was too chicken to wipe "internal." Perhaps I should have wiped internal too? Dunno.
Behavior:
My audio will hitch for a split second randomly (sometimes five minutes apart, often a moment after turn my screen off, or in shorter 20/30-second intervals here and there, but nothing 100% reliable). Happens with any app. Stitcher. Recorder (playback). Text-to-Speech reader. Audible. Spotify. OGYouTube. VLC. Any audio will behave as described.
Questions:
I've been trying to correlate what the problem might be with OS Monitor (root enabled), looking at the system messages. I'll often see E LightSensor: Light old sensor_state 0, new sensor_state : 512 en : 1 and E/Zygote (26507) MountEmulatedStorage() appear in red (along with some others), but can't find useful reference to what these might mean (are there E/Blastocyst errors as well?). I'm just looking for aaany kind pointer or direction on what to look for, what to disregard, or how one should go about troubleshooting this surprisingly frustrating problem. Is OS Monitor what I should use? I don't even know if the error'd items in Red are even what's causing the problem. Could just be meaningless correlation, since correlation is all I've got right now.
Thanks for any suggestions...
[1] shipped-roms (dot) com/download.php?model=Galaxy%20S5&file=ACG-G900R7WWU3BOH1-20150921182030.zip (can't post external links, apparently, so this mess will have to suffice until I reach 10 posts)
I have what I needed, thanks!
Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell df -P > df-P.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:
Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:
Run "adb shell"
Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"
Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
secXces_debaki said:
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
Click to expand...
Click to collapse
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
dr4stic said:
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
Click to expand...
Click to collapse
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
secXces_debaki said:
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
Click to expand...
Click to collapse
Well, don't get yourself into any trouble. I'm not in the business of ending relationships None of the commands modify anything, they just read information and dump it into a file. Other than rebooting, your device won't need to go offline. Also, if you HAVE modified your device in terms of ROM or whatever, please include a list of your mods or whatever in the message you send me with the text files zip.
PS> I've visited your area, or at least the one listed with your profile on XDA. It's a beautiful place. If I could get a visa worked out, it's on my list of places in europe I'd love to move to, possibly in retirement
U are planing to get one x720/7?
There are some way beautiful places around in Germany.
Can u maybe help me with my meta-inf?
secXces_debaki said:
U are planing to get one x720/7?
Click to expand...
Click to collapse
I'm giving it some very serious thought. I'm in the US and the x727 will be on sale on wednesday at US$300, which is very compelling for a device with an msm8996pro, even if the camera is average at best, the screen is less than impressive, and it's missing a headphone jack. My G2 is starting to act up and I need something cheap for the short term.
In any case, I'm doing my research now. I've downloaded the ROMs for 17s (both the stock CN version and the modified IT version). The kernel sources are released for x727, and I imagine the x720 kernel can likely be built from the same sources, in fact I wouldn't be surprised if everything about the kernel was the same. So I wanna see if I can get a kernel and rom building. I may attempt a TWRP build first, since I'd want that anyway, and it's simple enough to boot from fastboot and see if things work. But, I need help understanding the system. And that's where the information gathering in this post comes in.
secXces_debaki said:
Can u maybe help me with my meta-inf?
Click to expand...
Click to collapse
I have no idea what you're referring to with the meta-inf.
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
secXces_debaki said:
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
Click to expand...
Click to collapse
I would really like the logcat and logcat-radio to be running from the moment just after the hardware logos on the screen start showing up, once EUI starts to boot. The logcat is circular and has a limited buffer. Once it reaches the end of it's buffer, it starts overwriting itself, therefore it only keeps a certain amount of the logs in memory before they're gone. Your logcats were therefore incomplete. In more basic terms, I don't see where the system started booting up, that part of the log had already been overwritten when you took the log.
I also sent you a response requesting additional information, and for you to re-run one of the other commands that also errored out.
I do appreciate the help, I really do, thank you
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
secXces_debaki said:
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
Click to expand...
Click to collapse
Yeah, that doesn't help at all. Meta-inf to me is a file included in a flashable zip. It isn't even a main file, and it isn't even particularly important. It certainly wouldn't damage the baseband. The baseband, otherwise known as the modem or radio, controls your phone. It's like the brain stem, it controls the most basic automatic responses. Generally if your radio was broken, your phone would be hard bricked, there would almost certainly be no recovering from that.
Did you flash a modified radio/firmware to your device?
secXces_debaki said:
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
Click to expand...
Click to collapse
Heh, thanks
That actually lines up similarly to other things I've head about the device. Your assessment of the screen seems more positive than some, but then that sorta thing is a bit of personal preference. Frankly I don't game (much) to the point where I want a QHD or 4K display, and I don't intend to do VR. The reason I wanted a msm8996 is for the other advanced capabilities. The thing I'm looking forward to most is getting WiFi Calling working for T-Mobile, my reception isn't always great and that would be fantastic for me
As for the sound, I learned a long time ago to accept disappointment there. And I'm OK with that. I really wanted a headphone jack. Adapters tend to be bulky and/or break, and I don't like to be restricted to a single pair of headphones just because they have the right connector. You also can't easily share headphones with a CDLA connection. I have heard that the speaker output is nice, and I'm looking forward to that.
Mostly I'm excited that the kernel is not much modified from the CAF sources. Once I've verified that whatever it is I'm working on will actually boot, I will be able to upgrade to a newer revision of the kernel (with security fixes) and possibly even jump to the UM branch for the kernel, which is unifying for the Nougat release. I'm using the op3 as a template for my cm device and at the moment just gathering information. I don't even know if I'll buy the device yet or even make a rom. But it's what I'm looking into. This is a side project for me, and I desperately need to find a job, that takes priority.
secXces_debaki said:
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
Click to expand...
Click to collapse
I don't know how fast the phone boots, but usually I have the command already typed into the window, then I reboot and as soon as the first logo appears on the screen I hit enter. The command may not see the device immediately, and it'll say "awaiting device" and that's fine, it'll start logging as soon as the device appears. Then do CTRL+C 30 seconds after all the final connections to the cellular network are done
Managed to fix my standby drain..
U got a pm with the last logs. Hope it's good
Last month I bought a cheap Chinese 4k android TV and for the last weeks it has been great.
However I recently bought a PS5 and it is basicly stuck at 1080p forever unless I restart the TV every time I want to game.
The only way I get the PS5 to output 4k to the TV is on the first time after a cold boot of the TV. At this state everything is working really well (4k HDR everything).
Now if I turn the PS5 off and power it on again, it reports it can only do 1080p and the option for 4k is greyed out and the only way to fix it is to reboot the whole TV.
As you could imagine this is totally driving me crazy. (By the way the same Symptoms apply to other 4k capable devices such as a Fire TV Stick I had laying around)
The TV settings are also completely useless and there are no options regarding "UHD Color" or resolution.
If someone has any ideas on how to fix this I would be really happy.
Thank you in advance.
So I fiddled with the settings a bit and stumbled across a greyed out setting called "HDMI-EDID Version" which was set to "AUTO-EDID" but since this is a greyed out setting I could not change it in any way.
Then after countless hours of searching in the Internet and tempted to buy an HDMI EDID emulator, I found someone who had similar issues with a shield TV and a projector. He used adb and "bugreport" to find out about the EDID capabilities of his TV and so did I.
So now after generating the bug report using adb and searching for EDID, I found this line:
"settings/global/tv_input_hdmi_edid_version" which was set to "2" by default.
So fair enough I executed the command:
adb shell settings put global tv_input_hdmi_edid_version 1
And the greyed out setting now shows "EDID-2.0" and everything is working as it should and no more restarting of the TV is required to get 4K HDR from the PS5.
So it seems like it was indeed a firmware issue or more or less a broken auto EDID feature.