samsung galaxy nexus - Why is my phone slow?

19
2014-04
  • Scott Severance

    My phone has lately been really slow. When I turn on the screen, particularly if it has been off for a while, the phone is really sluggish. For example, it might take 30 seconds to respond to my input. Or if someone calls, it might not respond to my answer gesture until after the caller has already given up and hung up.

    If I leave the screen on for several minutes (up to five), the phone will eventually start to respond more normally.

    The CPU information in the developer options shows that the processor is pegged during all this slowness, and the process system_server is consuming almost all of that CPU capacity with other processes fighting for a little CPU time.

    Also, this CPU activity is killing my battery. I'm only getting half the battery life I should be getting.

    I recently lost root in an OTA upgrade; in re-rooting I had to do a wipe of the phone. Once I restored everything, the problem came back.

    My phone is a Galaxy Nexus running Jelly Bean (4.1.2). I also experienced a similar issue with my previous phone, a Nexus One running MIUI and "ICS". I attributed that phone's slowness to its age, but now I think there must be something else going on.

    What could be wrong, or how could I go about tracking down the problem?

    Answers to questions posed

    • My current phone is running 4.1.2. The problem became much worse after the update. My previous phone was the one I said was running "ICS". I put that in quotes because it was a custom ROM that claimed to be 4.0 but which I suspect was actually Gingerbread+.
    • My RAM typically runs at about 85%. But, I doubt this is too useful since Android automatically kills apps when it needs more RAM and the Linux kernel is designed to keep RAM mostly full so as not to waste it.
    • Currently, Google Maps is using the most battery, followed by Tasker. I'm quite sure that this isn't typical, however. I can't imagine why Google Maps would be so high, as I don't use it often. Anyway, I turned off the location permissions, so hopefully that'll cure Google Maps. And Tasker doesn't usually consume so much, but when the CPU is pegged it seems to have a harder time operating than most apps. (By the way, I have no location-based profiles in Tasker.)
    • Upon rebooting my phone, it's OK until the screen goes off for a period of time. Then, the problems resume. They're so severe that it's often faster to reboot than to try to use the phone without rebooting.
    • Auto-rotate seems to have no effect. I regularly toggle it in the normal course of using my phone, and haven't noticed any difference either way.
    • Apps would appear to be the culprit since I've experienced the same issue on two different phones and since doing a factory reset. However:
      • The process that's consuming the CPU isn't an app but system_server, which is a core part of Android.
      • I have a lot of apps, so disabling them one by one would be a time-consuming process.
    • I tried re-nicing system_server, but I didn't se any effect.
  • Answers
  • Lie Ryan

    This looks like it could be an issue with certain background services malfunctioning. Try observing the background services and disable some of them to see if you might hit the culprit. To do it in a way that is less hit and miss, there are several battery app in the market or you can use ICS native battery monitor to see if there are anything that are consuming more battery than it really should.

  • Martin Tapankov

    I've had a similar issue with my new mobile, Razr Maxx running ICS. It turned out to be an overzealous car HUD application that consumed CPU cycles even when not running. Uninstalling it solved the problem. What confused me initially was that Android OS was shown as the main battery drainer and not the app itself. Since you had the same issue with your previous phone, this suggests a misbehaving application that you have installed on both.

    I would try turning off GPS and mobile data/Wi-fi and observe whether the battery continues to drain at a similar alarming rate. If it's the internet connection that triggers the problem, this is likely due to an ad-supported application unsuccessfully trying to phone home.

  • amh15

    Another very common source of Galaxy Nexus slowdowns is quite a nasty hardware/firmware issue documented here: http://code.google.com/p/android/issues/detail?id=39154 .

    This will probably affect you if you have less than 3 to 4Gb storage free. There are some workarounds but they involve root and thus possible warranty invalidation. I found that clearing out some storage and rebooting does help somewhat, but have not yet tried the workarounds.

  • geffchang

    Check the running services. You will know what is running unnecessarily. I closed these, and I could immediately see a change in speed.


  • Related Question

    performance - Why does my phone peg the CPU every time I wake it up?
  • Questioner

    This is driving me nuts. I have SeePU installed so that I can see a CPU graph on my Moto Droid. When I unlock the phone after being idle for a while, the CPU is pegged by android.process.acore and the phone is unusable for 15-45 seconds, which is an eternity when you are trying to answer the phone!

    Tech details:

    • Moto Droid
    • OS 2.2 CyanogenMod v6 (also happens with 2.1 stock)
    • Launcher: LauncherPro (also happens with DXTop, and ADW Launcher)
    • No task killer

    Apps: http://www.appbrain.com/user/mark_porter/apps-on-the-phone

    UPDATE: I un-installed most of my apps, and I seem to have licked the problem for now. I'm gonna try adding one app back a day until it gets stupid again. If I can find a particular app that causes this problem, I'll post it here


  • Related Answers
  • Saiboogu

    Are you over/underclocking your CPU at all and/or using profiles?

    A lot of users will underclock their CPU when the phone is sleeping, which may save battery. However, if you underclock too much (125 MHz), the phone will lag like crazy when it wakes. It is recommended to never underclock further than 250 MHz.

    Aside from that, I'm not really sure anything would cause this to happen and would need more information to help you diagnose.

  • Manivasagam

    Instead of doing that , just try with WatchDog app , which finds which App uses more of your memory or slow downs your Android Phone ..

    Hope it helps you ..