Google sky maps and compass
I recently posted this question in an older thread but didn't really get any answers. Is it just my phone or doesn't the sky map and compass apps work very well? The first day or so after installing google sky maps, it worked great as the compass app did as well. Well then they both would start stalling and not updating with phone movement, I un-stalled both and re-installed with no luck. The compass app will work but I have to re-calibrate it everytime I use it or it will just either sit there or be real slow. So is this the normal performance to expect out of the magnetic sensors on the EVO? Thanks for any help or tips to make this work, it was one of the many reasons I wanted an EVO to begin with.
- 09-08-2010, 10:57 AM #2
- 09-08-2010, 11:49 AM #3
- 09-08-2010, 11:57 AM #4
- 1,195 Posts
Are you trying to use it indoors or near buildings?
If so, the magnetic sensor is very sensitive to the magnetic field generated by the electrical service for a building.
I find it works OK out on the road or in a field, but in something like a backyard or indoors it gets thrown off easily.
Sucks when you're trying to spot stars for a telescope in your backyard. :/
- 09-08-2010, 12:08 PM #5
- 09-08-2010, 11:27 PM #7
Try running the Sensor calibration tool. I have a feeling the compass, GPS and the actual G sensor orientation may be part of the entire thing.
Settings > Display > G calibration.HTC Evo 4G running OTA 3.70.651.5 (Rooted) with Netarchy SBC Kernel 4.2.2
- 10-04-2010, 12:20 AM #10
- 17 Posts
I know this thread is a bit stale, but I thought I'd chime in with my recent findings on this topic.
Ironically, the problem with the compass is actually caused by running the G-sensor calibration. For any phone that has never had the calibration performed, the compass will more than likely work flawlessly. 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). 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). 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. Yes, this is a pain and certainly not desirable... I'm pretty sure it's a software/firmware bug, since a hard reset does fix the problem.
I've confirmed this behavior on 2 of 2 EVOs, so I'd bet it affects all EVOs. 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 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. Customer Service and Sprint's phone tech support certainly are not the right people. 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.
- 10-04-2010, 09:03 AM #11
- 10-04-2010, 10:33 AM #12
To make any compass to work right you have to be outside, well away from away from electical lines.
For the EVO you also have to start by doing the figure 8 motions once you open any app that uses the compass to get it to work right.
Then Google Sky works well outside for helping you to find constellations.
- 10-04-2010, 12:05 PM #13
That makes perfect sense bacause when I first got the EVO, the compass and skymap worked perfectly inside or out. Now after doing the G-sensor calibration, I noticed things went down hill. Probably nothing we can do to fix this other than a factory re-set I'm guessing, not that desperate to use skymaps so I will wait for a work around. Thanks for the heads up on this, now we know what is going on.
- 10-05-2010, 08:42 AM #15
- 213 Posts
firstname.lastname@example.org and that got me to someone who could actually solve the problem.
Regarding Skymap, I am sure you have done this but make sure that GPS is turned on.
- 10-05-2010, 11:59 AM #16
- 10-05-2010, 08:11 PM #17
- 17 Posts
FWIW, I reported the problem to HTC's customer support (866-449-8358). They claimed to be aware of the problem and that "hopefully" it will be fixed in an upcoming release. With something like this, though, it's hard to tell if they really understand the specific problem being reported... I guess all I can do is hope!
If any of you have time, please call HTC and report the problem as well. I think the more complaints they get the more likely the problem will actually get fixed!