On Jul 19, 4:14 pm, Adam Ratana <[email protected]> wrote: > Hello Nathan, I actually use raw Accelerometer + Magnetometer data as > well as the deprecated Orientation sensor in my apps (they support > 2.1+) and I have yet to receive anything stating that the orientation > sensor was not available, perhaps I have been lucky.
Well, I may have gotten lucky too, but I can't say there are no error reports. ANR DALVIK THREADS: (mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0) "main" prio=5 tid=1 NATIVE | group="main" sCount=1 dsCount=0 obj=0x4001f1b8 self=0xcee8 | sysTid=6034 nice=0 sched=0/0 cgrp=default handle=-1345006496 at android.hardware.SensorManager.sensors_enable_sensor(Native Method) at android.hardware.SensorManager.enableSensorLocked(SensorManager.java: 1048) at android.hardware.SensorManager.registerListener(SensorManager.java: 1143) at android.hardware.SensorManager.registerListener(SensorManager.java: 1039) I can't match it up exactly with reports from users that the app is frozen on startup, but I am looking at all possibilities. This article suggests I capture data from both the accelerometer and the magnetic field, neither of which I would otherwise care about, and use them to calculate orientation. It's a guy from Google, so it might be the closest thing I can find to official. http://www.damonkohler.com/2010/06/better-orientation-readings-in-android.html Nathan -- 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
