The emulator doesn't simulate any specific phone. Just a generic one. Your application *should* run the same on an HTC magic as on a TMobile G1 because the hardware is very similar. The whole intention of Android is to separate the application layer sufficiently from the hardware so that your app will run equally well on any android device. So, although there are possible reasons it might not work well on a Magic, it's far more likely misbehaving because of either 1) the users particular phone setup (too many other running apps, etc), or 2) it's misbehaving on most actual physical phones. If it's reason 1, you just got bad luck that they left a poor review. If it's reason 2, you should investigate and fix it.
If at all possible, you should get an actual G1 (or Magic when it becomes publicly available in your area) and install and test the app. And although a DEV phone would be better than the emulator, the DEV phone ships with a different configuration than what end users have on their phones. So an actual phone from a phone company would be the absolute best way to test. The Android Platform which gets installed onto these phones by cellular phone companies is customized as they choose (which is one reason Android is open source). For this reason, the emulator will never be exactly the same as the real world. Justin Mattaku Betsujin wrote: > I am getting user feedback for my app "closes a lot on HTC magic, one > star" > > Are there any HTC magics out there? Will it be able to get an > SDK/emulator for it? > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
