Hi again, to anyone interested, here is the solution:
I found out that BatteryStatsImpl persists its state to /data/system. The batterystats.bin-file there also was 1.5M big. Gladly I got information from one of the developers that this is far from normal. The command dumpsys batteryinfo helped great deal to find the culprit. In this case an application on my device that had reserved wake-locks with a random string as a name for each one. After 75k wake locks things began to go wrong. Deleting the application from my device resolved the issue. At the next periodical persist of the batterystats.bin-file, it's size went back to normal 28k. rflexor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
