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 following copy > >> protection related 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 no copy protection on 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
