> Web bulletin boards are rife with identical stories of people's phones > running slower and slower until all you can do is reboot (after 2-3 > days' use).
Can you provide links to some of these discussion threads? Thanks, Justin Android Team @ Google On Jan 9, 6:03 am, luke <[email protected]> wrote: > I have had the same problem, and removing Locale finally solved the > problem. > > Web bulletin boards are rife with identical stories of people's phones > running slower and slower until all you can do is reboot (after 2-3 > days' use). I got in the habit of rebooting daily. > > With Locale installed, even when the phone is mostly responsive, > system_server performs a garbage collection every 3-3.5 seconds, and > takes 260ms, so the UI blocks over 7% of the time. > > Do the Locale guys know about this problem?? Is it worth it for > Android Market put a temporary block on this app until they fix it? > For the longest time I was just thinking that Dalvik had shoddy > resource management and eventually picked up cruft... most end users > with Locale installed will just think, "this G1 phone is junk" -- it > shouldn't take 10-30 seconds to bring up the dialer or the contacts > book, but it does when the phone has slowed to a crawl... > > On Dec 29 2008, 3:18 pm, gregz <[email protected]> wrote: > > > My phone started to get slow today and when I removed Locale, it was > > immediately back to normal (fast!). FYI. > > > On Dec 22, 5:07 pm, "Justin (Google Employee)" <[email protected]> > > wrote: > > > > If other users on this thread have Locale installed, could you remove > > > it and report back on your results? > > > > Thanks, > > > Justin > > > Android Team @ Google > > > > On Dec 19, 11:21 am, fadden <[email protected]> wrote: > > > > > On Dec 19, 8:36 am, Ed <[email protected]> wrote: > > > > > > Thanks for your message. I think that the outdated scoreboard app was > > > > > one culprit, but as this thread shows, the problem existed before > > > > > scoreboard was even released. I suspect that whatever bug had to be > > > > > fixed in scoreboard exists in some other apps as well. > > > > > For future reference (and for the benefit of anybody who lands here by > > > > searching)... > > > > > "adb shell top" will tell you what's using up CPU. In most cases this > > > > will identify the (over-)active app. > > > > > "adb logcat -v time" will show the debug log, with timestamps. In > > > > many cases it will identify *why* things are active, e.g. scoreboard > > > > getting swatted constantly. > > > > > "adb bugreport" dumps about a megabyte of stuff, with logs from > > > > various components. If you are seeing a lot of activity in > > > > system_server but don't see anything telling in the logs, and only a > > > > little activity in "top", then something may be quietly driving system > > > > server to distraction. If you skip down to "BINDER TRANSACTION LOG" > > > > you can see the most recent chatter, identified by process ID. If > > > > something is appearing very frequently, it may be the culprit. > > > > > You can map the processes to apps with "ps" or by looking in the > > > > PROCESSES section. > > > > > I used the above to identify edu.mit.locale as a source of difficulty > > > > on somebody's device yesterday. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
