The failure may very well be non specific to a Hero. In addition, there are some things that may break on Hero that won't break on others.
If you run it in a 1.5 emulator, you will already find out if you are using APIs that weren't available in 1.5. Also try to run it hundreds of times consecutively in the emulator to see if you can trigger OutOfMemory. The HERO handles memory poorly and has less RAM allowed per app than other devices. 1.5 does not allow certain flags on BitmapFactory that would help the memory situation a lot. The combination of these two things is what I believe is causing a crash that a user reported ( still without many details). Except for the fact that I've already had 1.5 enabled for some time, I would consider not supporting 1.5 in the manifest. Nathan -- 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
