How and when this issue will be solved. It seems that we are stuck and can not use Sensor API under emulator, I am sure it will be working fine under the real phone. Well! If anyone of you know the workaround for this problem please share it with me also.
On Thu, Apr 30, 2009 at 6:30 PM, JP <[email protected]> wrote: > > > Thanks snctl - I see something different (stuck call), but I suppose > it goes back to the same root cause. I guess I'll wait and see how it > comes out on the device (I am running with the crowd: G1/carrier OTA's > and stay on the regular-user experience side of the fence). > > As far as the Zilog Z80 note goes... that seems to be a joke for the > guys that live on the islands that likened to compare Android to the > Sinclair ZX80 on these lists (:->). Oh yeah thegoodoledays. > > > > On Apr 29, 9:56 pm, snctln <[email protected]> wrote: > > not sure if there is a work around but I believe this is a known issue > > according to the latest sdk release noteshttp:// > developer.android.com/sdk/RELEASENOTES.html > > > > (copy and pasted below for convenience) > > Known Issues > > > > Sensor problems in Emulator > > > > * If your application uses the Sensor API and you are running it > > in the emulator on the Android 1.5 system image, you may experience > > problems. Your application may generate ANR messages or crash when > > using the sensors. The problem is being investigated. > > > > Other > > > > * We regret to inform developers that Android 1.5 will not include > > support for the Zilog Z80 processor architecture. > > > > I have a few apps that make use of the Sensor API and they are all > > working great on my ADP1 with the 1.5 image installed, so it looks to > > be just an emulator issues > > > > ---snctlnwww.snctln.com > > > > On Apr 29, 11:33 pm, JP <[email protected]> wrote: > > > > > One more find in the 1.5 emulator. > > > A call to getSystemService(SENSOR_SERVICE) just hangs. Works just fine > > > in 1.0 and goes through both on a device (G1 with latest OTA update > > > from T-Mobile) and the 1.0 emulator. > > > Accelerator is a "yes" AVD option by default, so that should go > > > through? Can anybody confirm this issue... is there a known workaround/ > > > solution? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
