When RC30 was installed on my phone (OTA update some months ago), my home and dial buttons totally stopped working. And the screen was not locking anymore.
I did a factory reset in Settings -> SD card & phone storage -> Factory reset, and it solved the issue (backup all your data before, you can even backup apks with astro). You should try this. On Feb 12, 8:12 am, Stoyan Damov <[email protected]> wrote: > On Thu, Feb 12, 2009 at 2:32 AM, Dianne Hackborn <[email protected]> wrote: > > On Wed, Feb 11, 2009 at 3:22 PM, Stoyan Damov <[email protected]> > > wrote: > > >> Who shall I rant to? T-Mobile? They could care less - they don't > >> manufacture the device and they don't develop the OS. HTC? They don't > >> develop the OS. > > > Actually the G1 is T-Mobile's phone, and they do very much care about broken > > updates, and I am sure would like to hear about this. > > The thing is that I'm not a T-Mobile customer, I just own a T-Mobile > G1 device, so I'm pretty sure T-Mobile could care less for me. > > > > > I am very sorry you are having this problem, but you seem to be assuming > > that your experience matches that of everyone else who has gotten the > > update, which as far as I know is not the case at all. For example, I was > > running the OTAed 1.1 on my phone for quite a while, with no trouble. > > The update has been released recently, we'll see. > > > > > It would certainly be interesting to know what is going on with your phone, > > however your posts so far indicate that you aren't really interested in that > > but just want to yell. Which is fine, but it isn't going to help anyone > > much. > > I really don't want to know what's going on with my phone. It's not > interesting to me - if I was an Android developer, or if I had time to > play and find bugs perhaps it would be. The fact that the update sets > me back at least 1 day is very frustrating - I either have to upgrade > the dev tools to 1.1 and be frustrated as a developer (and hope > everybody will update their phones, which, I think is inevitable given > the awfully nagging dialog) or downgrade to 1.0 and loose all my data > on the device and be frustrated as a user. > > In other words, yes, I wanted to yell! I very much doubt that begging > for help (elsewhere) would actually help me, because you see, while > you seem to want to help, you also assumed I'm the only one > experiencing this. Just like when I was the "only one" experiencing > the lost unlinked files bug... > > It's not that I want to yell to you or any other particular Android > developer on the list, but yes, I want to yell at Google's Android > development *team* for the broken update. > > Cheers, > Stoyan > > > > > -- > > Dianne Hackborn > > 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 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 -~----------~----~----~----~------~----~------~--~---
