One of the problem is the HTC magic has been doing the rounds since
early Feb when Cupcake was still way off being finished, so it's easily
possible that the device they're using is running flakey firmware.
The first hits AndAppStore saw from Magics' was on the 5th of Feb, and
since the 18th o
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 screens
However is using this device might simply be running Cupcake, which is
far from being complete and ready.
Note that apps that rely on private APIs/resources may/will run into
problems with Cupcake.
On Sat, Mar 7, 2009 at 12:27 AM, Mariano Kamp wrote:
> And as it is not releases it might still b
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 abo
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 yo
5 matches
Mail list logo
