So I'm a bit unsure how this could have worked before, at least properly. That there are some issue with having resource for 1.5 and for 1.6+. There was a talk at IO that talked about this: http://code.google.com/events/io/2010/sessions/casting-wide-net-android-devices.html I encourage you to watch the video when it's posted (no idea when this is going to happen).
The short of it: 1.5 does not know about -mdpi -hpdi, so it'll take the first one it finds which could be the wrong one (which means it'll get scaled). Now, it should have found one at least, so this is something new. Since the 1.5 system image didn't change, it looks like packaging by the new aapt from 2.2 might do something different. I'll look into it later this week. In the meantime, just move your resources from drawable-mdpi/ to drawable/ Xav On Mon, May 24, 2010 at 12:41 PM, Michael A. <[email protected]> wrote: > Hi Xav, > > I had / have just had the same problem. > > The solution that worked for me is precisely the process you describe. > > Regards, > > Michael A. > > > On May 24, 9:13 pm, Xavier Ducrohet <[email protected]> wrote: >> Hi sebastian, >> >> Let see if I get this straight, you had the following resources: >> >> drawable-hdpi/ >> foo.png >> drawable-mdpi/ >> foo.png >> >> you used to build against API 7, but now you are building against API >> 8, and it started failing to work on 1.5? >> >> You moved drawable-mdpi/foo.png into drawable/foo.png and now it works on >> 1.5? >> >> Xav >> >> On Sun, May 23, 2010 at 3:27 AM, sebastian >> >> >> >> <[email protected]> wrote: >> > Have had the same problems after updating SDK to 2.2 and Android >> > Eclipse Plugin to newest version, >> > but haven't changed anything on my project, min SDK version is 3 and >> > target SDK version 4. >> >> > The problem was caused by drawables in drawable-hdpi and drawable-mdpi >> > folders that weren't in the drawable folder. >> > In my case, copying all drawables from drawable-mdpi to drawable >> > folder, clean and rebuild project solved the problem! >> >> > Looks like a bug in Android SDK/Eclipse Plugin, hope Google fixes that. >> >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Android Developers" 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-developers?hl=en >> >> -- >> Xavier Ducrohet >> Android SDK Tech Lead >> Google Inc. >> >> Please do not send me questions directly. Thanks! >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" 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 >> athttp://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 [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-developers?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
