Sure, that's what I meant with "still buggy". In my case, NewsRob, I can say though that I don't use any private API.
I have to add though that I never verified the bug myself, so it might be totally unrelated to the Magic or not a bug at all. But for the twidroid problem he also posted a screenshot though: http://twitter.com/techtravel/statuses/1238274270 Anyway, I'd mark it up as suspicious behavior for the time being. The user is willing to show the problem to me in person. As he lives 300 kms apart from me I would need to have something else in the area to go there, but when I do I'll take my logcat with me and feedback here then. On Sat, Mar 7, 2009 at 9:27 AM, Mariano Kamp <mariano.k...@gmail.com> wrote: > And as it is not releases it might still be buggy. > > I also got an error report regarding the Magic and he also mentioned > problems with Twitroid. > http://twitter.com/techtravel/statuses/1237848578 > http://twitter.com/techtravel/statuses/1237863847 > > Both complaints are not about "Forced Close", but about GUI problems. Very > strange. > > > > On Sat, Mar 7, 2009 at 2:12 AM, Justin Allen Jaynes <jus...@ragblue.com>wrote: > >> >> 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 -~----------~----~----~----~------~----~------~--~---
