![]() If anyone has any ideas or knowledgeable tech contacts (HTC is probably ultimately the right place), I'd love to bring this to their attention. Customer Service and Sprint's phone tech support certainly are not the right people. ![]() I haven't tried to convince anyone at Sprint, HTC, or Google of the issue, since I'm not sure how to get ahold of anyone even remotely close to the "right" person. I'm currently running Android 2.2 with the latest 3.29.651.5 build, although I think this problem affects earlier builds, too. I've confirmed this behavior on 2 of 2 EVOs, so I'd bet it affects all EVOs. I'm pretty sure it's a software/firmware bug, since a hard reset does fix the problem. Yes, this is a pain and certainly not desirable. Once you close the app though, next time you run it or any other compass-enabled app, you'll have to redo that shaking/figure-8 routine. The compass will actually still work with any of these apps, but only after you first shake/move the phone around significantly (the "figure 8" trick). If you run the calibration even just once, you'll essentially hose your phone's compass performance and any app that uses it (including Google Sky Map). Tap on i to select your region of interest to download. For any phone that has never had the calibration performed, the compass will more than likely work flawlessly. THIS FAQ IS NO LONGER MAINTAINED First, a quick summary: Double tap on map to bring up plates. Ironically, the problem with the compass is actually caused by running the G-sensor calibration. (Most lens calibration software options will include either a hard target or a downloadable target for you to use.) Step 2 Put your camera on a tripod at a distance from the target that’s 50x the focal length of the lens. I know this thread is a bit stale, but I thought I'd chime in with my recent findings on this topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |