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 power issue then. My battery is 97% (immediately after PC disconnect). Will check Orienteer again later. On Nov 4, 2:29 pm, mitush <[EMAIL PROTECTED]> wrote: > 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 Orienteercompassgoes between 0 and 90 degrees only. > The same thing happens when usingcompassview with the maps/street > view, here I could only get about 90 degrees view angle as well (in > other words I cannot see other side of the street and other direction > of the street). > > The funny thing is that, in my G1 app I was listening and logging > SensorManager.SENSOR_ORIENTATION_RAW values and earlier today the > returned values had the range of 360 degrees, and I have the log file > to prove it was not a dream :) When I run the same app now, it shows > limited range values only, consistent with Orienteer . As if something > got broken between now and few hours ago. I also recall that when I > triedcompass/map/streetview few days ago, I was able to rotate my > view without any constraints. > > There is not much metal around, I tried changing my location as well. > For a second, I though it could be the car, which my wife parked > outside the house an hour ago, but Orienteer shows the same problem > even 120 ft away in the backyard. I did not drop G1 or did anything of > that sort. > > On Nov 4, 4:01 am, bryan <[EMAIL PROTECTED]> wrote: > > > I've been trying to figure out the cause of acompassrelated error > > for a while. After debugging and standing out in the rain slowly > > spinning in circles for a while, I finally found out that my device is > > reporting back yaw values inconsistently. > > > 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 > > sensor? I've gotten a number of reports from others complaining about > > inaccuracy withcompasstype results and am wondering if this is a per > > phone error or if all of the G1s have poor yaw/orientation sensors. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
