Am 07.09.2011 02:42, schrieb gjs:
This is a known bug on some devices, eg Nexus One& Motorola Xoom see http://code.google.com/p/android/issues/detail?id=15500
That sounds like a vendor specific implementation bug, but the emulator has it, too.
I get around it by using external bluetooth GPS devices.
How do you do that? I have another bluetooth device at hand but how can I force the phone device or the emulator using that one?
In 'GPS Test' they might be reverse engineering the 'Location& related classes' details back into NMEA strings, but you would have to ask them...
It's a commercial company (http://www.chartcross.co.uk), I doubt they'll tell me their secrets. Maybe I shoud go reverse engeneer their software myself :)
Thanks, Hans -- 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