Tell me more ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.
up vote 0 down vote favorite

I have kept my Google Nexus S up to date with the latest Android O/S since I've owned it and its always had performance problems to varying degrees. I'm currently running:

Android version: 4.1.2
Baseband version: I9023XXKI1
Kernel version: 3.0.31-g5894150
Build number: JZO54K
Uptime: 145:35:00

Currently the performance is particularly bad. The UI is generally very sluggish, apps can take a long time to open or switch, occasionally the home screen appears empty after switching away from a "big" app (e.g. Bad Piggies or Chrome) almost as if the shell had crashed and restarted. The performance seems to deteriorate the longer the phone has been without a reboot. There is a bug where the phone think its still charging after being unplugged. I am not sure if this is associated with the performance issue.

I tried various performance monitoring apps but none of them told me anything useful. I finally installed a terminal emulator and ran the trusty top. Here are the results:

top

These two threads: com.google.android.inputmethod.latin and UEventObserver, appear to consistently be using high CPU. I have seem UEventObserver using as much as 40-50%. Regarding the inputmethod.latin I am assuming this is keyboard related but I am only using the standard Android keyboard so the high CPU usage is inexplicable.

Any theories about what is going on?

How can I fix these two threads that are hogging the CPU?

share|improve this question
Have you checked around on XDA? – t0mm13b Jan 2 at 20:14
as matter of interest, you're using Android Terminal Emulator right? Possibly that even? – t0mm13b Jan 2 at 20:15
I've done a fair bit of googling, but nothing seems to come up with the specific searches for the thread names. Yes I think its Android Terminal Emulator – Schneider Jan 2 at 20:16
What is the uptime on that nexus s? Quite possibly you could have stumbled on a kernel glitch? In short, you cannot "fix these two threads that are hogging the CPU", the binder_X I see in there, some service must have died and ended up in repeat restart die loop... – t0mm13b Jan 2 at 20:18
Might help to include a logcat of what's going on... :) – t0mm13b Jan 2 at 20:20
show 1 more comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.