We were hoping that it would get resolved very soon after the release of the ADP1, and it's been taking much much much much longer than anyone had anticipated (even myself, albeit a permanent pessimist when it comes to schedules, didn't see that one coming at all).
Like I said above, this isn't an oversight. Making official flashable images available has always been part of the ADP1 plan. Sometimes however some scheduling disasters happen and a tiny grain of sand can block an otherwise well-oiled machine for very long times. This is one of those times. The ADP1 1.1 situation has made February a very painful month for everyone involved. I totally understand your frustration, and, knowing myself, I would be vending on the list exactly the way you currently are if I happened to be in your situation. Even if you don't want to trust Google at this point, I'm asking that you trust me when I say that I'm doing everything that I can to get this issue resolved. JBQ On Fri, Feb 27, 2009 at 11:25 AM, Java Developer <supp...@cyntacks.com> wrote: > > Can I return my ADP1? I was completely mislead, and so was everyone > else. Now that I think about it, I believe American Express would > agree with me. I suggest we all start charge back procedures on these > bricks as they don't deliver anything near what was expected and > "promised". > > JBP, how can you state "and we've known about it since before the > first ADP1 shipped, since right from day 1" and not realize holding > this information back from developers at the time of rollout is at > best an EXTREME OVERSIGHT? I am pleased that organizations such as > CNET are now publicly taking Google to task on this, I can only hope > the NYTs follows suit this Sunday. > > > > On Feb 27, 1:33 pm, Disconnect <dc.disconn...@gmail.com> wrote: >> Except you are allowed (and even, kinda, encouraged) to make your app >> available in many places. >> >> So how do you distinguish between "I got it from andappstore" or "I got it >> for free from the developer" (both legit but not market) from "Joe copied it >> off his phone for me"? >> >> >> >> On Fri, Feb 27, 2009 at 12:34 PM, Steve Barr <barr8...@gmail.com> wrote: >> >> > On 2/27/09, Jean-Baptiste Queru <j...@android.com> wrote: >> > > DRM in this discussion is a mechanism that allows developers to say "I >> > > don't want my application to be available on devices from which it can >> > > be copied". >> >> > Given rooted devices, would it make more sense to look for DRM which >> > locked an app to a particular device ID (or user ID), no matter what >> > kind of device it was? It seems like the Market has to keep track of >> > which device (or perhaps person) downloaded/purchased which apps >> > already, so the user can download them again if needed. >> >> > I'm no expert on DRM, but it seems to me there are some pieces >> > available for a different solution to the problem. >> >> > Steve > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. Please don't contact me directly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
