Besides figure eights, this forum thread
http://forums.t-mobile.com/tmbl/board/message?board.id=Android3thread.id=7341view=by_date_ascendingpage=10
suggests turning G1 screen down and tapping the phone on the back.
This heimlich maneuver worked for me today, my compass is working
again, not
The compass auto-calibrates itself as it is used, but coming near a
magnet can uncalibrate it so it won't give good data until getting
calibrated again. To help it along, you can hold the phone and move
it around in figure eights.
That is not a joke. :)
On Nov 6, 11:23 am, [EMAIL PROTECTED]
bryan wrote:
[...]
For example, the range of offset from magnetic north is +/- 46
degrees. The average offset is just under 20 degrees. Depending on how
I orient my G1, the error can go to 46 degrees off of magnetic north.
Has anyone here experienced similar results when reading yaw from the
In the process of writing an app for my G1 I think I got stuck with
similar problem. Running Orienteer application (from the Market)
confirms that; turning my G1 by 360 degrees while holding it flat, the
reading on the Orienteer compass goes between 0 and 90 degrees only.
The same thing happens
I have connected G1 to my PC and Compass (Orienteer) and my app
started to get good and consistent readings from the sensor again.
After I disconnected, Orienteer sort of works (has 360 range), but the
north is off by 0-50 degrees depending on orientation and a little
jumpy.
Might be a battery
On Nov 4, 10:01 am, bryan [EMAIL PROTECTED] wrote:
Has anyone here experienced similar results when reading yaw from the
sensor? I've gotten a number of reports from others complaining about
inaccuracy with compass type results and am wondering if this is a per
phone error or if all of the
6 matches
Mail list logo
