Is the "logd" process eating up battery for anyone else here?
I'm having the same issue.
I solved it by rooting my phone, installing termux (terminal app from playstore) and typing the following commands on it:
su
stop logd
However, this process has to be repeated everytime the device is restarted.
Its possibly pernamenty off this proces?
Yes but it is a very lengthy process and involves a lot of risk as well so lets not consider it
Related
I am using a Defy + 2.2.1 stock.
At some point, my CPU is always at 100%.
I first tried moving more stuff to SD and deleting preinstalled junk with Titanium Backup, in order to free space.
Then I started looking into the processes (using OS Monitor 2.0.5) and found out that the system_server process is always over 70%.(no file-system is full)
I have USB debug set, and I already tried chmod on time_in_state using Phone Prioritizer, but that didn´t do either.
I was preparing to upgrade my android, but I am afraid of doing so over an unstable system. Should I update anyway ?
Is there a better app to monitor processes other than OS Monitor ? (sorting by cpu use doesn´t work)
I searched all topics with similar problems but didnt find anything else to try.
Any suggestions ?
Tks
Leo
Not sure if it goes deep enough but "betterbatterystats" give process usage, other usage & partial wakelocks so it may pin point something that OS Monitor doesn't (although I haven't used that so not really sure what it gives you).
I've been using it this week & it really gives some good information http://forum.xda-developers.com/showthread.php?t=1179809
Hope it helps
sp8y said:
Not sure if it goes deep enough but "betterbatterystats" give process usage, other usage & partial wakelocks so it may pin point something that OS Monitor doesn't (although I haven't used that so not really sure what it gives you).
I've been using it this week & it really gives some good information http://forum.xda-developers.com/showthread.php?t=1179809
Hope it helps
Click to expand...
Click to collapse
Unfortunately not. Nice UI but little info, and just user processes.
Now I´m trying the app System Tuner, but it is too heavy for my already overloaded system.
I am planning to do a factory reset then install app by app to try to figure out where it went wrong ... a hard way ...
Problem fixed :
I found out in tread All-in-one Defy Beginners -
Stock Froyo sometimes lags and/or freezes the phone: Its caused by the VM consuming all memory, all you need to do is adjust the amount of MB the VM should leave free.
There are a few ways to do it:
Use a terminal emulator, or use GScript Lite to run this:
Code:
su;
vm.min_free_kbytes=8192;
(Not permanent, need to be ran every time you reboot)
I placed the comands in the startup script of Phone Prioritizer.
It is still unstable, even with a higher value, but now I think I should go to a newer version of Android.
Leo Bernstein said:
I am using a Defy + 2.2.1 stock.
At some point, my CPU is always at 100%.
I first tried moving more stuff to SD and deleting preinstalled junk with Titanium Backup, in order to free space.
Then I started looking into the processes (using OS Monitor 2.0.5) and found out that the system_server process is always over 70%.(no file-system is full)
I have USB debug set, and I already tried chmod on time_in_state using Phone Prioritizer, but that didn´t do either.
I was preparing to upgrade my android, but I am afraid of doing so over an unstable system. Should I update anyway ?
Is there a better app to monitor processes other than OS Monitor ? (sorting by cpu use doesn´t work)
I searched all topics with similar problems but didnt find anything else to try.
Any suggestions ?
Tks
Leo
Click to expand...
Click to collapse
100% cpu usage
I am using a Defy + 2.2.1 stock.
At some point, my CPU is always at 100%.
Even i am facing the same problem with my defy 2.2.2 stock. The Motorola service center changed my motherboard but i am still facing the problem and it is really getting frustrating now. Can you help me out?
My phone (rooted, but stock running 4.1.1) keeps restarting by itself. I have seen other folks with the same problem on the S3 and other devices. And it seems the only thing that fixed it was changing the SD Card (tried it) or resetting the phone. It takes me ages to set up my phone and I'd like to avoid doing the latter if possible. Is there some kind of a panic log file that gets written that I could look at? I believe that the logcat file gets cleared at every reboot which, if true, explains why I can't spot anything in there. Since this happens erratically, I can't connect from my PC and redirect the logcat to a file on my PC. I believe Linux stores crash logs. Is there something similar on Android?
Oh, and it's not rebooting because it's getting hot or anything. And I haven't done any overclocking or any messing around with the phone.
Found a couple of options after googling. I had tried earlier, but "logcat across reboots" was a better search phrase.
Anyway, I can hook up my phone to the PC and run
adb -d logcat > mylogfile.txt
which should save a log file to my PC and when I'm not near a PC, I can use something like alogrec which saves logcat files to an SD card
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Another option is to use adb bugreport
http://developer.sonymobile.com/2012/01/25/new-bugreport-analysis-tool-released-as-open-source/
Hopefully it will provide a useful clue.
If not....you can always make a Nandroid, reset your phone, and then restore.
Sent from my PG06100
You can use terminal emulator from your phone and dump a logcat to sd as a .txt if you search around you'll find the proper command which I can't remember at the moment but its something like
Su > enter
Logcat -d /sdcard/filename.txt
Filename being whatever you choose
I like to break stuff!
[ROOT]SGH-I467 4.4.2 ATT with 360-super-root & fix mediaserver battery drain
I bought this piece of crap from ebay and though it would be just like N5100 and I was wrong. This tablet is lack of support and could not even be rooted with those one-click root software, nor with a stock image to create an odin rooted system image. And since there was someones said they could root this **** with KingsRoot, I tried every version of it and failed every time.
---------------Enough Complaining---------------------------------------------------------------------------------------------------------------------------------------------
Here is a magic software from China saved me, it is called 360 super root, if you heard that company "360 safe guard" or "qi hoo" you should know they are reliable.
worth to point out is, this software uses it's own superuser and will have issue with some of the app does not recognize it, but if you really want to fix that, you could try gain root with this software and total uninstall it and install your own superuser. (360 will block other superuser app while installed)
and yes it is fully Chinese, please find someone can read Chinese if you face any problem.
drive.google.com/file/d/0B8FqTHNeorKlVFY4aXNOWEk3WTA/view?usp=sharing
(I couldn't find upload attachment button so I uploaded it on drive with public access, please help me to upload this if I am breaking any forum rules).
---------------Fix MediaServer Draining Battery-------------------------------------------------------------------------------------------------------------------------------
Oh yeah after rooted your device, if you had the same issue with me that the "mediaserver" process keeps running and draining your battery life, I found a simple way to solve it WITH ROOT ACCESS, from this link : geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain
This method requires you have an adb shell running on your computer, device usb debugging on, and connect device with your computer, then run adb shell, follow these commands to disable media server process.
QUOTE :
adb shell
su
adb shell
su
pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
Please reply me if you have any questions.
What does this mean? Looks the same as kin root. Doesn't work.
Hi,
I know the issue is already documented, but what i ask is the debug process to know what caused the phone to reboot and to burn 55% of battery in 6 hours, even in airplane mode and no wifi connection.
Is there a way to read battery logs and system bug errors ?
p.s. : I already have the android SDK since i develop android apps, if it could help
Been trying to dig around but don't see a solution for this.
On older devices you can apparently see this the last successful dexopt job via this command.
adb shell dumpsys jobscheduler
But I don't see it here nor have I any older phone to confirm success in finding it.
Any ideas?
Manually running "cmd package bg-dexopt-job" and it finishes in like 2 minutes and you know it does not have a lot of unfinished optimizing but it's a less fun way to know it
swejuggalo said:
Been trying to dig around but don't see a solution for this.
On older devices you can apparently see this the last successful dexopt job via this command.
adb shell dumpsys jobscheduler
But I don't see it here nor have I any older phone to confirm success in finding it.
Any ideas?
Manually running "cmd package bg-dexopt-job" and it finishes in like 2 minutes and you know it does not have a lot of unfinished optimizing but it's a less fun way to know it
Click to expand...
Click to collapse
Hey friend! Followed your guide over on the OP Community for optimizing apps and such for the 9Pro, and ran the adb command as well after setting up my 9pro as a clean flash, not restored from other phone.
Just put it on the charger, I was at something around 6 hours and 14 minutes of SoT, 30 hours off of charge with 3% battery left. I am still on 11.2.3.3 as well.
Not that any of this really relates to your question, but wanted to let you know!