I would also love to hear anyone's experience on 1.5+ handsets. What I would really love though is a definitive answer from Google on this issue. I don't know why this can't be addressed officially, we're not asking for secret information to be revealed here - we have to know these kinds of things to make basic decisions about what to do in the market.
If I've overlooked information about this issue then I apologize, please point me in that direction as soon as possible. :) Matt On Nov 16, 5:35 pm, Dave <supp...@bumptechnologies.com> wrote: > These two Issues seem to be identical to me. We submitted our app > with copy-protection turned on (not aware of these issues, nor of the > fact that some people wouldn't be able to download our app as a > result). We'd now like to turn copy-protection off so everyone can > use our app. But before hosing all our users running Android 1.5, it > would be nice to know which release (1.5 or 1.6) actually fixed this > issue. > > Am I misreading the two Issue reports? > > Has anyone switched their app from copy-protection to no copy- > protection and had issues with force closes for users running Android > 1.5? > > Thanks, > -dave > > On Nov 12, 11:32 pm, tauntz <tau...@gmail.com> wrote: > > > > > >> When a bug is marked as "FutureRelease" it usually means it will be > > >> fixed in the next release at the time the bug is closed. > > >http://code.google.com/p/android/issues/detail?id=2263wasmarked as > > "FutureRelease" @ Mar 21, 2009 so it should be fixed in Android 1.5 - > > that was the next version after this date (first SDK released on 13 > > April 2009). > > >http://code.google.com/p/android/issues/detail?id=2047wasmarked as > > "FutureRelease" @ Apr 20, 2009 so it should be fixed in Android 1.6 - > > that was the next version after this date (released on 15 September > > 2009). > > > Tauno > > > On Thu, Nov 12, 2009 at 10:28 PM, Matt Hall <matt.h...@gmail.com> wrote: > > > So can I take that to mean that that the bug exists in all current > > > releases including 2.0? I could really use some concrete info on this > > > particular issue as it affects most of our apps and the enlarged > > > bundle size is becoming a real problem on Droid. > > > > Thanks very much, > > > Matt > > > > On Nov 12, 3:22 pm, Romain Guy <romain...@google.com> wrote: > > >> When a bug is marked as "FutureRelease" it usually means it will be > > >> fixed in the next release at the time the bug is closed. Anyhow, it > > >> means the bug has been fixed and will eventually reach users phones :) > > > >> On Thu, Nov 12, 2009 at 9:07 AM, Neiman Buffard > > >> <neimanbuff...@gmail.com> wrote: > > >> > ok for starters im pretty sure im not doin this right but i wanted to > > >> > throw > > >> > an idea at anyone who would take the time to read/listen for upgrades > > >> > to > > >> > come if it cant make the cut for the next one. I would like to see > > >> > this done > > >> > in an upgrade instead of an app only because i feel that this is > > >> > somthin > > >> > everyone would enjoy. BIG PICTURES i feel that When ur favorite > > >> > contacts/friends call and u have a customized ring tone and possibly an > > >> > assigned contact photo would it be askin to much to utilize the > > >> > 3.2-inch > > >> > TFT-LCD flat touch-sensitive screen with 320 x 480 (HVGA) > > >> > resolution for > > >> > that photo. Very simple yes i know however we are limited to that small > > >> > picture with out even being givin the option as to weather you' like > > >> > it that > > >> > small or not. > > >> > just a thought i've had for some time now that i wanted to share > > >> > thanks for > > >> > listening follow android but more specificly G1 users > > >> > On Thu, Nov 12, 2009 at 12:02 PM, Matt Hall <matt.h...@gmail.com> > > >> > wrote: > > > >> >> Can anyone from Google comment on the status of the followingcopy > > >> >>protectionrelated bugs: > > > >> >>http://code.google.com/p/android/issues/detail?id=2047 > > >> >>http://code.google.com/p/android/issues/detail?id=2263 > > > >> >> They're marked fixed in a future release, but I don't know what > > >> >> release (if any) that means. > > > >> >> I'd love to revert to nocopyprotectionon our games for a number of > > >> >> pressing reasons, but these bugs bit us pretty bad last time I tried. > > > >> >> Any info much appreciated, thanks. > > >> >> Matt > > > >> >> -- > > >> >> 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 > > > >> > -- > > >> > 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 > > > >> -- > > >> 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 -- 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
