Very true Guy. Thanks for pointing that out. I've jumped to some semi-conclusions based on speculation at the memory constraints on the G1. (Which either way I'm happy) My interest is over the posted issue. You'll have to excuse my excitement over the cause of the issue having been tracked down. I love my Android phone, but every day I yell when I find it's bogged down again (which until today required a restart 1 - 2 times a day).
On Aug 18, 10:30 am, Romain Guy <[email protected]> wrote: > We never said Donut would not be delivered to G1s. > > > > On Tue, Aug 18, 2009 at 8:27 AM, Disconnect<[email protected]> wrote: > > > On Tue, Aug 18, 2009 at 11:14 AM, bryan<[email protected]> wrote: > > >> After months of confusion, it appears that the system_server process > >> issue which eats up 90% of the CPU, has been fixed. > > >>http://code.google.com/p/android/issues/detail?id=3453 > > >> The bug is absent in Donut due to an overhaul of the related code, > >> which is great. My question is about the G1s. I suspect from the > >> memory limitation, G1s are not going to be seeing a Donut build. This > >> issue needs to be addressed on the G1s. It's heavily crippling the > >> user experience on a day to day basis, including the detriment to > >> battery life. > > > I suspect everyone is going to send me a dollar, and Donut will > > finally come with the pony that hackbod promised us in cupcake. > > >> Each application I open yields a "Force Close or Wait" dialog. > >> Everything is choppy and slow. Everyone using a location polling > >> application and Network location is having this problem. Fortunately > >> the commenters on the issue noted that toggling Network location will > >> reset the problem (which is a lot better than rebooting). Allowing for > >> a half day or so before the G1 becomes buried again by 90% CPU > >> utilization. > > >> Since this G1s are likely not able to get a Donut build, when will we > >> get an OTA fix for this devastating bug? > > > "Since we'll never get a fix, when will we get a fix?" Also, for OTA > > bugs you need to ask your OTA provider (sounds like t-mobile since it > > is a g1.) > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
