It's probably something different, but I had problems like this myself
and found it connected to an application aquiring a lot of wakelocks
(75.000). You might want to try this out, just to rule the wakelocks
out:

Connect to your phone with adb -d shell

ls -l /data/system/batterystats.bin

On my phone this currently is 42k big. When I had the error it had
become a 1.5m monster.

If you should have the same problem, pull the batterystats.bin from
the device and analyze which user-id has allocated the wakelocks. Then
find out which app has this userid and uninstall. In my case it was
ITweet.

You can find my bugreport here:

http://code.google.com/p/android/issues/detail?id=4043

Ralf

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to