Thanks Romain, I really appreciate you fixing this without even a bug report being filed. We were using the same GIF for multiple densities as the auto-scaling worked quite well for us, so that must have been the problem. Can you clarify if this was fixed in the 4.1.1 that is now being released or if we should expect it in a future update? We have some plans for other games and features to existing that may benefit from GIF again so it would help to know when/if we should consider using them again. Thanks again!
On Wednesday, July 11, 2012 10:10:44 AM UTC-7, Romain Guy (Google) wrote: > > I found and fixed the bug by the way. It occurs only when the bitmap > loaded from the GIF has the wrong density and gets auto-scaled by the > framework. > > > On Tue, Jul 10, 2012 at 6:19 PM, Bradley Hekman wrote: > >> Josh, I encountered the same problem in my app while running on hardware. >> I'm just going to switch over to png.. >> >> On Saturday, July 7, 2012 2:39:27 AM UTC-4, Zsolt Vasvari wrote: >>> >>> If this happens on hardware but not on the emulator, my guess is that >>> this is not really a PNG/GIF issue. I couldn't get Google I/O tickets >>> either, so I cannot help. >>> >>> On Friday, July 6, 2012 11:50:43 PM UTC+8, Josh F. wrote: >>>> >>>> I will create the bug report as soon as I can get a development device >>>> with this actual build on it as it does not happen in the emulator. As it >>>> stands right now you had to be at Google I/O to get one and tickets sold >>>> so >>>> fast I was not able to get one. To test this issue and the fix I have had >>>> to rely on my users who were there and have a Galaxy 7, which is not going >>>> to work to create a sample project example of the issue required to post >>>> an >>>> official bug report. Hopefully in a few weeks I'll get my Galaxy 7 and do >>>> just that. >>>> >>>> If someone in the community has a device that they would be willing to >>>> test with me on, I can send sample files/etc. to create the bug report >>>> sooner. >>>> >>>> On Friday, July 6, 2012 8:27:14 AM UTC-7, Mark Murphy (a Commons Guy) >>>> wrote: >>>>> >>>>> > This is a bug in >>>>> > Android 4.1 Jelly Bean as released on current devices and I hope >>>>> that they >>>>> > fix it before full retail devices ship or this thread will get very >>>>> busy. >>>>> >>>>> Please feel free to file a bug report on http://b.android.com, with a >>>>> sample project demonstrating the issue. >>>>> >>>>> -- >>>>> Mark Murphy (a Commons Guy) >>>>> http://commonsware.com | http://github.com/commonsguy >>>>> http://commonsware.com/blog | http://twitter.com/commonsguy >>>>> >>>>> _The Busy Coder's Guide to Android Development_ Version 3.7 Available! >>>>> >>>> -- >> 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 > > -- 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
