Hi JBQ, Take a look at [1] and [2].
[1] http://www.google.com/support/forum/p/Android+Market/thread?tid=40dc07e3a35208c1&hl=en [2] http://www.google.com/support/androidmarket/bin/search.py?hl=en&forum=1&query=download+issue+more:forum So it appears there *are* men at Google! Thanks On Tue, Mar 10, 2009 at 3:56 PM, Jean-Baptiste Queru <[email protected]> wrote: > > In cases of hanging "downloads", do you know whether the users are > seeing an actual download icon in the notification bar (it looks like > an arrow pointing down)? > > Longer explanation: There are two phases in a "download", one where > the Market uses its own protocols to retrieve the download URI, and > one where the Market instructs my code, the Android Download Manager, > to get the actual bits using the Android HTTP stack. My code displays > the download icon, and whether that icon is present or not is a good > hint to know whether the problem is with Market retrieving the > download URI or whether it's in my code failing to download the data > (which could also technically be an issue with the underlying network > stack, though that should be rare). > > JBQ > > On Tue, Mar 10, 2009 at 6:45 AM, Stoyan Damov <[email protected]> wrote: >> >> Hi Android engineers, >> >> It's been weeks since we, developers, and many users, started ranting >> about the bugs in the Android Market application, namely: >> >> 1. Hanging downloads >> 2. Hanging installs >> 3. The DREADED "Force Close" after an application update. >> >> Many of us have received low ratings (especially 1 star ratings) >> because of the aforementioned issues. >> I took the time to review more than 100 applications, all in different >> categories, and most of them sacrificed some of the RIDICULOUS 325 >> characters[1] description in explaining to users that 1, 2, and 3 are >> actually not their fault but yours (Google's), and setting up websites >> for alternative downloads. >> >> All of the problems above are intermittent and are thus hard to >> reproduce and we understand that. >> What we don't understand is how much more will we have to listen to >> the sound of silence. >> Is there an Android engineer, man enough (or woman enough) to stand up >> and say *anything* about these issues, whether they are acknowledged, >> or being reviewed, or someone is working on them, or whether and when >> there's a planned deadline on fixing any of them? Also, is Google >> going to stand up and say "we fucked up, it wasn't the devs fault, but >> now everything's back to normal, sorry for the inconvenience" >> >> So far, it appears that you are HIDING, and I can't stress enough how >> much I hope that's not true, and that the reason for the silence is >> that you're actually extremely busy busting your @$$3$ working on >> fixes. >> >> Thanks >> >> > >> > > > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
