I'm sure this has been posted already, but I wanted to centralize this information after having seen and helped a few people with battery screen shots that indicate high Media Server and Google Maps battery drain/CPU usage.
Google Maps and Media Server should not be your two highest battery drain apps Unless you are using Google maps all day long. Even then, Screen should be eating more battery than Google Maps.
Go into Settings, Application Manager, All, then find Google Maps and Clear Cache / Clear Data. Exit all that and select the Google Maps app icon. I bet it says "updating to latest version" and all your problems are fixed with Google Maps. Google Maps does not show up in my battery information (it is hardly using any battery), even though my GPS is turned on all day and set to update location automatically. Google Maps does not even show up on my Battery status page unless I use the Navigation.
Media Server scans your SD card and phone for new media files. I found that I needed to reformat my SD Card and then copy my big library of pictures back to it to fix the high amount of battery drain and cpu usage from this app. Before the reformat, Media Server was my higest drain application and the Gallery would slug around. After the reformat, Media Server doesnt even show up on my battery information and gallery flies as it should.
Grant H said:
I'm sure this has been posted already, but I wanted to centralize this information after having seen and helped a few people with battery screen shots that indicate high Media Server and Google Maps battery drain/CPU usage.
Google Maps and Media Server should not be your two highest battery drain apps Unless you are using Google maps all day long. Even then, Screen should be eating more battery than Google Maps.
Go into Settings, Application Manager, All, then find Google Maps and Clear Cache / Clear Data. Exit all that and select the Google Maps app icon. I bet it says "updating to latest version" and all your problems are fixed with Google Maps. Google Maps does not show up in my battery information (it is hardly using any battery), even though my GPS is turned on all day and set to update location automatically. Google Maps does not even show up on my Battery status page unless I use the Navigation.
Media Server scans your SD card and phone for new media files. I found that I needed to reformat my SD Card and then copy my big library of pictures back to it to fix the high amount of battery drain and cpu usage from this app. Before the reformat, Media Server was my higest drain application and the Gallery would slug around. After the reformat, Media Server doesnt even show up on my battery information and gallery flies as it should.
Click to expand...
Click to collapse
Google now uses maps to know your location and give you relevant content. If you disable it after enabling google now, you will be affecting the usefulness of google now. That being said, I have google now off anyway.
Giving up
I've been struggling with runaway Media Storage for the last few days and am giving up!
Two different SD cards (32gb and 64gb). About 10gb of Music and Pictures copied to music and pictures folders. Fresh formats using exFAT and FAT32. No matter what I do, it gets hung up for hour after hour after hour and runs the battery down with less than 2 hours of screen time.
My last experiment confirmed that it's an S4 bug:
Took the 2 cards, formatted them FAT32, copied over my media. Stuck one in the S4, the other in my old Moto Defy running cm10. After boot, the Defy was done indexing (Media Storage dropped off task status list in System Tuner) within 15 minutes. The S4 was still spinning after 3 hours.
So I powered off the devices, and switched the cards between the two. Booted them up, and the same thing happened. The Defy was done within 15 minutes while the S4 was still bogging after several hours.
Keep in mind that the Defy is merely a single core overclocked to 1.2ghz. Everything else is painfully slow on it, but it still manages to spank the S4 in indexing my media. And as a result, the battery also outlasts.
Arg! Was really hoping this S4 was going to work out for me, but it looks like it won't be of any use until the custom roms start rolling out...
I've essentially been unable to get rid of the mediaserver wakelock, well, since jellybean has been released. It is persisant whether there is a memory card or not. Even if I delete every picture and music file on the phone it persists. It seems it cannot be stopped!
Also, I have been able to rid the maps wakelocks by disabling google now, but I'll give your method a shot.
Related
I'd like to share tips and get help on how to reduce memory usage in Android. Maybe we can start a wiki page somewhere for this.
I've found that getting more free memory on my Android phone (G1) makes the phone much faster, especially when switching between apps.
I'd tried CompCache, but found it made little difference. I tried a swap partition, but found it made my phone unstable.
So here's my process for identifying memory hogs under CyanogenMod: connect the phone via USB, run 'adb shell', and then 'top -m 15 -s rss -d 10'. I then use the phone for a while, switching between some large apps like the browser and Google Maps, and observe which processes are staying in memory. Note that the USB debugger itself uses some memory.
I was able to get rid of some apps that were staying in memory for no apparent reason: Callbook.
I was able to get rid of some apps that were staying in memory and I didn't really need: 3G Watchdog, NetCounter
I was able to change settings in some apps so that they wouldn't stay in memory all the time: disable notifications in CyanogenMod Updater; disable 'start service on power on' in Quick Calendar
I was able to find some alternative apps that don't stay in memory all the time: now using Mode Scheduler and Timeriffic instead of Sound Manager
I'm still experimenting with different calendar widgets to see which one uses the least memory.
I noticed that the Calendar app was staying in memory. I'm not sure, but I think that disabling gmail/contacts/calendar sync fixed that. Disabling sync makes the phone faster anyway, though I then want some alternative mechanism to make sure that the phone syncs at least once a day. I've been using WiSyncPlus, set to turn on WiFi on charging, and force sync on WiFi connection. That works, though WiSyncPlus uses 15 MB or so itself. If Timeriffic or some other timer-based program that doesn't stay in memory had the ability to do a force sync, I'd prefer that.
After all that, things were greatly improved: I could keep a couple of large apps like eBuddy and the Browser in memory at the same time.
Since then I've wiped my phone and upgraded from CyanogenMod 4.2.13 to 4.2.15.1, and replicated my apps and settings as best I could remember.
I still have some large apps that seem to stay in memory:
* system_server
* android.process.acore
* com.android.phone
* com.android.inputmethod.latin
* zygote
* com.google.process.gapps
I don't recall if all of these apps were staying in memory under 4.2.13. No doubt at least some of these are necessary. (acore)
Are there any settings I can change or apps I can uninstall to stop these processes from staying in memory all the time? I don't use my phone as a phone very much; I'd be happy to get the phone app out of memory. What does gapps do? I don't need my gmail, contacts, and calendar to sync constantly. I've tried disabled the wireless network location service, but that doesn't seem to have made any difference.
Under which process does the memory usage for a widget go? I'm not seeing a separate process for some of my widgets.
balazer said:
I'd like to share tips and get help on how to reduce memory usage in Android. Maybe we can start a wiki page somewhere for this.
I've found that getting more free memory on my Android phone (G1) makes the phone much faster, especially when switching between apps.
I'd tried CompCache, but found it made little difference. I tried a swap partition, but found it made my phone unstable.
So here's my process for identifying memory hogs under CyanogenMod: connect the phone via USB, run 'adb shell', and then 'top -m 15 -s rss -d 10'. I then use the phone for a while, switching between some large apps like the browser and Google Maps, and observe which processes are staying in memory. Note that the USB debugger itself uses some memory.
I was able to get rid of some apps that were staying in memory for no apparent reason: Callbook.
I was able to get rid of some apps that were staying in memory and I didn't really need: 3G Watchdog, NetCounter
I was able to change settings in some apps so that they wouldn't stay in memory all the time: disable notifications in CyanogenMod Updater; disable 'start service on power on' in Quick Calendar
I was able to find some alternative apps that don't stay in memory all the time: now using Mode Scheduler and Timeriffic instead of Sound Manager
I'm still experimenting with different calendar widgets to see which one uses the least memory.
I noticed that the Calendar app was staying in memory. I'm not sure, but I think that disabling gmail/contacts/calendar sync fixed that. Disabling sync makes the phone faster anyway, though I then want some alternative mechanism to make sure that the phone syncs at least once a day. I've been using WiSyncPlus, set to turn on WiFi on charging, and force sync on WiFi connection. That works, though WiSyncPlus uses 15 MB or so itself. If Timeriffic or some other timer-based program that doesn't stay in memory had the ability to do a force sync, I'd prefer that.
After all that, things were greatly improved: I could keep a couple of large apps like eBuddy and the Browser in memory at the same time.
Since then I've wiped my phone and upgraded from CyanogenMod 4.2.13 to 4.2.15.1, and replicated my apps and settings as best I could remember.
I still have some large apps that seem to stay in memory:
* system_server
* android.process.acore
* com.android.phone
* com.android.inputmethod.latin
* zygote
* com.google.process.gapps
I don't recall if all of these apps were staying in memory under 4.2.13. No doubt at least some of these are necessary. (acore)
Are there any settings I can change or apps I can uninstall to stop these processes from staying in memory all the time? I don't use my phone as a phone very much; I'd be happy to get the phone app out of memory. What does gapps do? I don't need my gmail, contacts, and calendar to sync constantly. I've tried disabled the wireless network location service, but that doesn't seem to have made any difference.
Under which process does the memory usage for a widget go? I'm not seeing a separate process for some of my widgets.
Click to expand...
Click to collapse
I realize this is a little late to the party, but thank you for using and suggesting Timeriffic. We work hard on it and it's nice to know that people use it and love it.
Has anyone encountered this problem before? Many games are sluggish and run in frames, and it sometimes runs in frames on the homescreen. I have Android 4.0.4 from AOKP (aokp-crespo-milestone-5) and Matr1x (#11) kernel installed. Also, I had the same problem when running Android 2.3.6 and also Stock ICS both rooted and unrooted.
I discovered this problem when trying to play Asphalt 6. On a Samsung Galaxy S worked fine, but on the Nexus S it was going in frames. Since, I have seen many more games that have the same issue, any ideas?
Hi, maybe you should try Matr1x v22 BFS (Better than CFS for running games) should be good with 4.0.4
I played Asphalt 6 on my Nexus S and it was fine, as much as the Nexus S gets.
Do you have some services syncing with the network in the background? Sometimes, when the SD card is not responding properly, the device itself can get a little sluggish, so if a service is saving some data on the SD card in the background it could cause this.
Check the running applications menu to see what's there, try removing everything that is not necessary (syncing applications, social network apps, ad networks, etc.), and then try playing again.
A few times, I noticed that TweetDeck was causing this on my device. I had to manually close it so that games would be smooth, but it was a long time ago and I think this problem was resolved (am using TweakDeck now).
lightpriest said:
I played Asphalt 6 on my Nexus S and it was fine, as much as the Nexus S gets.
Do you have some services syncing with the network in the background? Sometimes, when the SD card is not responding properly, the device itself can get a little sluggish, so if a service is saving some data on the SD card in the background it could cause this.
Check the running applications menu to see what's there, try removing everything that is not necessary (syncing applications, social network apps, ad networks, etc.), and then try playing again.
A few times, I noticed that TweetDeck was causing this on my device. I had to manually close it so that games would be smooth, but it was a long time ago and I think this problem was resolved (am using TweakDeck now).
Click to expand...
Click to collapse
closed all apps in the background, no effect.
try this:
Save essential data from the SD card.
Format data, system, cache and boot. And then format sd card.
Reinstall everything back and see if it works better.
Anytime my Nexus S has been sluggish, I've used Android System Info (available on Google Play) to diagnose. Granted, it, like all other task manager style apps, will eat resources while running. However, under the Tasks tab, it will give you a list of each process and its MEM (RAM) and CPU usage. See if there are any processes that seem to be pulling too much CPU, or possibly too much MEM. It may be a constant issue that only shows when another resource-hungry process (i.e. Asphalt 6) competes for these valuable resources.
If you don't trust apps or don't wish to install any, it's possible to look at your battery usage. Although this is not a sure-fire nor exact method, it's possible that if you have a run-away process that's eating CPU, it could also be eating your battery as well. Have you noticed any major battery drain lately?
Fellas,
I'd installed the HERE maps during last month for a couple of Coastal line drives in South-India to make the best use of its offline navigation.
To my surprise, the HERE maps kept crashing after every 10-15 kms of drive.
Nothing much I could do about it, ergo switched over to the good old Google Navigation.
This is how I tried to install + use it:
Install the HERE maps app from the Play Store.
Set memory as SD-Card in settings.
Download Karnataka+Goa map data so that it resides on the SD-Card selected in Step-2.
Start driving by setting a destination being online/offline, the app crashes.
Uninstall the app and reinstall again.
Leave the memory to Phone's internal memory.
Repeat step 3, and the app crashes again.
Mine is a non-rooted HTC One E8 Dual Sim.
Did any of you observe this on your device yet?
Would appreciate if your could please share a fix if available.
PS: I've also tried setting the traffic to off, but it wasn't of any use.
Thanks,
Vinay
I started my Galaxy S6 920I battery issues a long time ago and couldn't find any help without rooting or tripping knox, so here's how I went back to a normal state. I want to share my experience with you guys and maybe help someone who's desperate like me.
UPDATE: 5.1.1 India OTA came 2 days ago and my problem is solved now. No more deep sleep isues.
device: 920I on Stock 5.1.1 India (G920IDVU2COF8), Brazil on VIVO network.
problem: "Android OS" process show up eating almost 50% of my battery, even on idle. I couldn't even get through the day. If I went to sleep and just left my phone alone with wifi, data, gps off and all apps closed, I would wake up with a dead phone.
conditions: I didn't want to void Knox since I think I can still use my warranty for something, even though Samsung offers a pretty lame service here in Brazil.
background: I've read basically everything regarding this subject and nothing seemed to work for me. Wiping cache, factory resetting, nothing.
method:
STEP 1: ERASING IT ALL
My phone came with stock 5.0.2 and I updated to 5.1.1 (Trinidad and Tobago) via Odin hoping it would solve my problems. It didn't, at all.
I decided to do a full wipe and flash 5.1.1 India just to see if the problem was relying on the ROM itself
When my phone started, I added my google account, normal setup, and then started disabling the useless Samsung features like motion gestures and Wifi always scanning
I DID NOT download any app from the play store, I decided to get them back gradually in order to try to find the problem.
I started disabling every app I though it was safe to to so. Here's the list: ANTT Radio Service, ANT + Plugins Service, Brefing, Dictionary, Drive, Dropbox, Facebook, Galaxy Apps, Galaxy Apps Widget, Google Play Books, Google Play Games, Google Play Movies & TV, Google Play Newsstand, Google +, Hancom Office Viewer, Instagram, Live Weather, Memo, Messages, Messenger, OneDrive, OneNote, Peel Smart Remote, S Beam, S Health, S Planner, S Voice, Samsung Galaxy, Samsung Push Service, Skype, Hangouts
I Kept basically Whatsapp, Hangouts, Play Music, Gmail and updated them through Play Store
Downloaded Google Keyboard since I hate the samsung one
Then I went to sleep with 15% battery. Woke up with 15% battery. Good job.
STEP 2: PUTTING INTO TEST
I woke up and charged the phone until 100%. Got our of home, wifi and data off.
I commuted for 60 minutes while listening to cached Play Music songs. Made some calls. Turned data on, used some whatsapp. Battery still on 94% at the end. Seemed ok.
When I arrived at work, I decided to enable instagram and Hangouts back and check on it again. My battery was on 92%.
1 hour later, my battery was 80% and "Android OS" was at the top of draining list again. Nightmare.
Uninstalled instagram. 1 hour later I had a drop of 3% without touching the phone. Android OS still on the top.
Uninstalled Hangouts and enabled default samsung Messages app. Answered some whatsapp chats and left the phone sleeping, didn't touch it. 1 hour later, battery dropped by 2% with Android OS on top.
Restarted and wiped cache. Things went back to normal.
NEXT STEPS
It seems like there's some serious bug with the apps, but somehow there's s System bug that needs to be sweeped with a cache wiping. That's the continuous process I need to be doing on regular basis.
I wonder, would it be that simple? A simple app making continuous requests to Android System and putting it on top of the draining list, hogging all of my battery on idle for nothing?
Anyone had the same problem?
Most likely a defective battery. Return your S6 back to Samsung telling them of your extensive tests as supporting evidence and request for a warranty repair/replacement.
Hi! I just bought the note 5 and everything's been great. I just started having a leaky battery though. It started after I restored my apps with an app from the Play store. Additionally, I downloaded previous problem apps like Skype. I wanted to confirm that restoring apps instead of downloading them still causes battery problems with the battery and if Skype is still a problem. Additionally, I had modified the sync settings of my social media apps, news feed, etc but I saw no significant change.
I just uninstalled all of my apps, drained the battery all the way, and charged it up fully. I do still notice a rapid decline though. I wanted to upload a pic but it said it was an invalid file Any comments are greatly appreciated and if you need more info, just ask, thanks!