Power Drain: android.process.media in J1 []

asked 2017-05-22 22:29:12 +0200

Robomike gravatar image

I noticed a significantly higher battery drain since upgrade to It's not critical, but I'm at 30% and less after a day with normal use. In each previous version I mostly had 60% or more.

Crest shows a process named "android.process.media" with 1.3% permanent load, in my other device with this process is always shown with 0.0%. Another big battery drainer is (android) telegram now, so I wonder if this behaviour is related to the whatsapp media access problem as in https://together.jolla.com/question/158262/media-missing-on-android-side-gallery-sfos2109/ and https://together.jolla.com/question/161035/21011-android-apps-cannot-show-gallery-s-photos-even-rebuild-index-by-sailfish-utilites-tool/ which I can workaround with a recursively permission change.

Is something on android side repeatedly trying to access some dirs or files without success, generating the high load? Anyone found other solutions for this topic? Any suggestions what to try?

edit retag flag offensive close delete



I just installed Crest (nice app, thanks), and "android.process.media" shows 0.0% load. Did you try restarting Android runtime?

magullo ( 2017-05-23 10:48:37 +0200 )edit

I am having the exact same feeling. It seems to me that the consumption of this new version is bigger than the previous one. I just charged the phone 2 hours ago and 10% of the battery have been spent. On my way to investigate this ...

yonux ( 2017-06-29 15:28:38 +0200 )edit

I found out that the size of the effect is related to the amount of pictures / media data. When I remove most of the pictures from home/nemo/Pictures and subdirectories, the questionable process remains on 0,2 %. I deleted the android media database and let it rebuild, but without final success. I also execute automated a "chmod -R a+rwX /home/nemo/Pictures" every 5 minutes, which makes the new pictures visible for whatsapp after a short time, but that's also not able to lower the load of android.process.media.

Robomike ( 2017-06-29 20:46:36 +0200 )edit

Ok, it seems that the drain is done when the phone is idle. I cannot see any process using lot of cpu when I am logged in, but the battery is almost empty this morning (20% left when it was 80% 10 hours ago). Of course, no wlan, no Bluetooth, no apps is running.

yonux ( 2017-06-30 09:08:51 +0200 )edit

Seems fixed for me. What I did : - bought a SD card in order to backup the phone before reset to factory default - power off, insert SD, power on - backup : removed some older stuff, backup the data

Checked the battery : 99% 6 hours later : 96%

I don't know what happened, but it is ok now.

I hope it helped.

yonux ( 2017-06-30 19:08:56 +0200 )edit