On Jul 24, 4:31 am, dan raaka <danra...@gmail.com> wrote: > The issue is even if you indeed fix it say in donut and it gets propagated > to cupcake and master, users will have to wait till donut OTA or some form > of intermitent OTA like CRC1 that happened recently to get an update see > that bug they reported has been fixed. This is just a normal life cycle !! > > Meanwhile you will have more and more people reporting the same bug .. I am > guessing that is what happened with the original poster. >
I think the bigger problem here is that issue is not even marked as fixed. Which means it is probably still not fixed in donut or even the generation after that. Actually, if you look at comment 2 on that issue, JBQ did "respond" by changing the name on the very same day but nothing happened since. Eric > -Dan > > On Thu, Jul 23, 2009 at 11:04 AM, Romain Guy <romain...@google.com> wrote: > > > The Android team is responding and resolving basic usability issues, > > and even non-basic ones, etc. Unfortunately, and believe me when I say > > we're sorry about it, we *cannot* fix *every single* bug. Some bugs > > are fixed right away, some take more time. > > > On Thu, Jul 23, 2009 at 10:58 AM, dotclick<dotcl...@gmail.com> wrote: > > > > Good point... and I probably deserve the criticism. > > > > However, your comments only strengthen my original point of GOOGLE is > > > not responding and resolving basic usability issues. This is one of > > > the key reasons why a company I work with made the decision today to > > > dump 100+ Android G1 phones that are only 9 months old and order non- > > > Android phones. > > > > -D > > > > On Jul 15, 5:30 pm, Mark Murphy <mmur...@commonsware.com> wrote: > > >> dotclickwrote: > > >> > So the only response I am going to get from Google is from someone who > > >> > didn't read the message or take the time to research it. > > > >> No, the only responses you will get is from people other than Google > > >> employees. As Romain Guy pointed out, if you read the response you were > > >> lambasting, you would notice that it is from a T-Mobile employee. > > > >> It seems curious that you seem to have made the same error that you are > > >> complaining about -- not completely reading the email. It's almost as if > > >> making mistakes were, like, human or something. > > > >> Of course, it is also curious that you appear to think this is an > > >> end-user tech support forum (which it is not) and that it is Google's > > >> primary responsibility to respond to you here (which it is not). > > > >> But I digress. > > > >> > No status updates or responses on the bug report from 7+ months ago. > > > >> Please point out the official public bug trackers for Windows Mobile, > > >> Blackberry, iPhone, and Palm WebOS. I'm not even sure there's one up for > > >> Symbian, and they're at least on the road to open source. > > > >> Please point out where you get detailed, bug-level information months in > > >> advance of product releases for Windows Mobile, Blackberry, iPhone, Palm > > >> WebOS, and Symbian. > > > >> Please point out how you -- whether via your own engineering efforts, or > > >> by hiring somebody, or by collecting interested people to raise money to > > >> hire somebody -- have a chance to fix bugs in Windows Mobile, > > >> Blackberry, iPhone, or Palm WebOS, as you can with Android. I'll give > > >> Symbian a mulligan here, since they're in progress on this issue. > > > >> Had this same bug, or an equivalent one, affected you on one of these > > >> other platforms, the best-case scenario is that, after sitting in > > >> indefinite tech support queues, you would be told it is a bug and it may > > >> get fixed someday. Here, not only were you able to file the bug report > > >> without much effort (albeit with no better of a response), but you have > > >> options for spearheading a fix, which you lack with any other > > >> commercial-grade smartphone platform. > > > >> Now, you may not elect to use any of those options to accelerate a fix, > > >> but that's your decision, not Google's. Regardless, you are no worse off > > >> than you would have been with any other platform with the same sort of > > bug. > > > >> If you want to whine about how Android has bugs, be my guest, just don't > > >> whine about the lack of response, since that's all you'll get from > > anyone. > > > >> Note: once Symbian gets a-rollin' in earnest on the open source front, > > >> the bar for Google and Android may get raised a fair bit, but we're not > > >> there yet. > > > >> -- > > >> Mark Murphy (a Commons Guy)http://commonsware.com| > >http://twitter.com/commonsguy > > > >> Android App Developer Training:http://commonsware.com/training.html > > > -- > > Romain Guy > > Android framework engineer > > romain...@android.com > > > 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 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 -~----------~----~----~----~------~----~------~--~---
