If you have a G1, you should probably be contacting TMobile for support. Obviously you can also give your suggestions/feedback to Android forums so the Android platform can be improved on th e longer run. But I don't think we can control the priority of Android developers, since they have their own roadmap to focus on. Hope your problem gets solved.
take care, Muthu Ramadoss. http://linkedin.com/in/tellibitz +91-9840348914 http://androidrocks.in - Android Consulting. On Thu, Jan 29, 2009 at 3:55 AM, [email protected] <[email protected]>wrote: > > On Jan 24, 6:39 pm, Mark Murphy <[email protected]> wrote: > > Perhaps nobody in the community has stepped up to write an > implementation. > > > > Perhaps somebody in the community has written one, but it's a patch > > somewhere inside Gerrit and hasn't been approved yet. > > > > Perhaps somebody in the community has written one, but it's a patch > > somewhere inside Gerrit which, while approved, has not been reflected on > > any public status page. > > Okay? That's...um...great? I don't exactly care, you see, I'm just one > of those stupid end-users who wants an operating system that came pre- > installed on my G1 to work. Yes, it's "free and open source" and > developed by a community of people as opposed to a corporation with a > tech support department, but if it's trying to cater to more than just > people who coded it, then please don't ask end users to learn advanced > C++ and code their own patches. Or at least tell them where they > should be asking for things like this instead, because there doesn't > seem to be any other place to get the Android team's attention. > > Just because I'm technically minded enough to press Control-Alt-Delete > and know what I'm doing doesn't make me a developer. Speaking of > which... > > Mike Hearn wrote: > >The problem is that if you go the route of a button to work around > >bugs in apps, then pretty soon you'll have 50 buttons, all of which > >require a PhD in Androidology to understand, and the apps will still > >be buggy. > > Open task manager. Select application. Force quit. Three buttons, all > of which require a Ph.D. in Having Fingers to push. It's also a fairly > basic function in any operating system that allows two applications to > run at the same time, which can cause all sorts of problems depending > on incredibly predictable factors, such as the weather, and the > precise temperature to 14 decimal points at which Richard Stallman's > blood will be the next time somebody doesn't precede "Linux" with "Guh- > noo slash". In other words, it would be quite useful when it's > necessary, and not very difficult to use if implemented correctly. > > In a perfect world, all apps would have zero bugs and play nice with > one another, but when the choice is between rebooting my phone or > waiting for the battery to die under the load of 48 instances of "while > (true) useCPU(a lot);", I'd much rather there be a third choice of not > losing the lengthy email I was just typing, thank you very much. > > Apologies if my tone seems bitter, but I'm kind of annoyed by the > level of customer support for this OS. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
