Related
I have upgraded my HTC Desire to Android 2.2. Unfortunately I have realized that after that update, an embedded compass started acting up. I mean it's not showing the North anymore. It seems to me that it's not an issue with some particular application as I have tried with several ones available on the Market and it needs to be some bug with new OS. Anyway here is what I have figured out and what I have already done in order to get this sorted out. At this point of time, it even looks like I have just some kinda workaround:
Once I pick out 'Calibrate' menu item in Compass v1.1 (developed by Snaptic, Inc.) and then according to the instruction, start off waving my phone in a figure 8 pattern to reset the magnetometer on my device, it's not gonna fix the issue but when I start rolling my phone in a hand (side to side then top to bottom) and then it seems to me that the issue is sorted out as finally compass points out the North, but after I close the application and open it again (or open any other compass based app) the magnetometer is broken again So all what I can do is to reset the magnetometer as per above-mentioned instruction again. It just looks like the device is not able to save some compass calibration setting anymore.
Anyway I was just wondering if some of you already faced this same issue and know how to fix it permanently. I would appreciate it, if you could share any thoughts with me. Thanks in advance.
Hey folks, I don't believe that nobody experiences that issue too. Maybe you just haven't noticed that yet? Anyway could you please just check if your compass works as intended after the upgrade to Android 2.2? Personally, I really believe it's a bug with Froyo.
I think mine is also acting weird.
Wenn starting Google Maps and using streetview in compass mode it only looks up and down and I cannot look from left to right.
When i roll the phone a few times in my hand it starts working.
But after closing Google Maps and starting it again I have to do the rolling again
I was wondering that compass problem too. With ver.2.1 everything worked like a dream as I use compass mostly geocaching. After updating in every app I've tried the compass stucks pointing to approx. to the lower left corner of the screen. Sometimes calibration helps but it stuck again after a while even the app is running all the time.
"Compass" app kinda could wake up after waiting a while but usually it doesn't. In any other software won't work at all as I've tried, 5secs after calibration but nothing more.
JLillia said:
With ver.2.1 everything worked like a dream as I use compass mostly geocaching..
Click to expand...
Click to collapse
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...
I can't say if it worked properly with 2.1, didn't use the compass a lot before.
With 2.1 I needed to calibrate it a few times, but probably not as much as I need to do now. I'm using the "compass" app and it directly tells me it detected an abnormal magnetic field. After calibrating it again, it points north. Haven't checked the correct north with a real compass, so it may have a slight difference.
I put my phone down at the table at 0 degrees N. I turn off my screen, and turn it back on. It is now pointing 90 degrees E. But the interesting thing is.. the east is actually located west, compared with the previous north :?
When I rotate my phone it displays only E or SE, always between 90 degrees E and 130 degrees SE. I can't even find north.
I can rotate my phone 180 degrees (Pointing south), it displays 130 degrees. When I calibrate the phone and I rotate my phone 180 degrees (Still south) it displays 160 degrees S. Which is kinda strange. And when I try to find the 180 degrees point, and rotate my phone again, it displays 35 degrees NE.
After another calibration the values seems to be okay...
My conclusion? Don't trust the compass at all unless you have a real compass to compare.
That person with the exact opposite experience is me
I complained on 2.1 here with many others about the compass going haywire every time you took it off-screen and its lack of stability and consistency. HTC 2.2 totally fixed this issue for me. I've calibrated it once about a week back and it's still accurate every time I'm opening it and in Google Earth.
Beware, the compass draws a lot of power in use so it'll drain the battery very fast. About as fast as playing a 8Mbps 720p VC-1 vid.
-----------------------------------
- Sent via my HTC Desire -
My problem is kinda dame that with Nakebod.
As I said compass stucks pointing to the lower left corner, it infact tells I'm holding the phone towards 120-130 decrees east, where ever I turn the phone to. Calibration helps for a while as after that the compass points approxamtely to north which is enough direction to me, but after a while or at least after swithing apps or taking compass background and back on, it stucks again to the 130 decrees.
Of course I am not using this kind of device as "for real" but I'd like to have it at least somewhat accurate. As geocacher I use compass as a tool with my hobby and I was quite happy with Desire because of the quite accurate GPS but after the update the compass is practically useless.
Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.
Try calibrating your magnetometer by waving your phone in 8-shaped moves.
I emailed HTC customer care also about the issue and the answer was to factory reset the phone. Of course that was the first thing I had already done at the minute I noticed the problem in first place so I wasn't quite fond of the idea. In fact I have reseted phone three times after the update and allways the result was the same; compass stucks.
Well, I thought that maybe I have some weird app that messes up the compass so I tried one more time...
At first after the reset I downloaded only EStrong file manager, compass and c:eo. Compass worked most of the time! I kept resuming backups and compass did stuck occasionally but not very often (+ abnormal magnetic field). I am not sure what I did leave out of the phone but now the comapss works quite fine. It is a lot more sensitive for magnetic fields than in 2.1 but usually calibration works to it.
So, the conclusion is, that even for some reason first times the reset didn't work, it did help after all. Just backup your data and give it a try. Doesn't cost more than some time. The compass DOES stuck still but is most of the time usable.
At least I left out MoreLocale2, Metal detector and some games. And I DIDN'T calibrate G-sensors after reset.
So, there is still some issues with update and compass but it COULD also be somewhat application related...
G-Sensor calibration might be the answer! Following the first factory reset yesterday which cleared the compass problem initially I reinstalled all apps and calibrated G-sensor to find the problem came back. Then I factory-reset once more last night and reinstalled all apps but didn't do the re-calibration, left the phone on for the night - no problem in the morning. Feel tempted to re-calibrate to proof the point now.
Please inform here how did it do if you re-calibrate. I have an ongoing geocaching challenge, so I won't try that until I'm sure that I don't need the compass for couple of days. After that I'm going to test if calibration is the problem as soon as possible.
I have the same problem. Have tried everything but hard reset. Still, compass worked a lot better on 2.1 :-(
Sent from my HTC Desire using XDA App
nitemarc said:
@JLillia: Also in my case the compass worked as intended on android 2.1.
Anyway thanks for your answers guys! I really appreciate it! So it looks like at least 3 folks here are experiencing some issues with digital compass after the upgrade to the Froyo on HTC Desire
Wonder if there is anyone here who could disagree with us and say that the upgrade didn't cause any compass degradation on his/her device at all...
Click to expand...
Click to collapse
My compass works fine on HTC Desire on Android 2.2.
Try 3d compass, and use its calibration option. Always works for me.
Sent from my HTC Desire using XDA App
nitemarc said:
Just a quick update, I made a quick phone call to HTC support this morning and raised that issue. The support analyst recommended the factory data reset to see if it helps. I guess it's just a standard answer so at this point of time I'm not gonna proceed with that and erase all data on my phone. (Btw, I wonder if it's possible to backup all current data from my unrooted, unbranded Desire?)
Furthermore he promised to get back to me in next few days with some official resolution of that issue so I will keep you updated.
Click to expand...
Click to collapse
Wonder how does HTC support team's SLA look like in terms of resolving client's tickets as my one hasn't been resolved yet... Anyway it seems to me that HTC is not going to confirm that OTA update to Froyo could caused that compass issue.
That's why I decided on factory data reset and it looks like that helped with getting this issue sorted out. After the hard reset, my first step was an initial compass calibration and that's really all what I did. The digital compass is not maybe so precise and accurate as it used to be on Android 2.1 but finally roughly (I would say with 15° margin) points out the north so there is a progress
Just to add my 2c, I can confirm that the compass has become useless since I upgraded to 2.2 on my device. Doing the figure 8 in Compass app has short lived benefits.
Sent from my HTC Desire using XDA App
Neither does my compass react in any application (tried Compass, Places directory, Google Navigation) after update to Froyo.
Calibrating with the 8 movement or G-sensor calibration does not help at all.
However, it always starts working normally when I tilt the phone to the side (so that I look on the slim side of the phone) and then start a short forward and backward rotation with the rotational axis going thru the display.
I need to repeat this every time I unlock the phone and the compass keeps on working until i lock the phone again or until I switch the application.
Weired.
I have the same problem, and it is a bit annoying. The compass works correctly if I wave the phone like in the video posted, but I have to do this every time I start an app that uses the magnetometer. My phone was not like this on 2.1.
Hey folks, I've got SyndicateROM Frozen running, and have the following problem:
When I use Google SkyMap, it won't let me see above the horizon. If I use GPS Test, which shows pitch/roll, it'll detect up to 90 degrees up, but doesn't seem to register anything higher than that. I mean: when I hold the phone flat on a table, no problem. Pick it up, and face it in front of me so the screen faces me, no problem. Tilt it upward so the camera is looking at the sky, and it doesn't seem to register.
I've tried calibrating compass, accelerometers (with the GPS Test tool, and with sensorcalibutil_yamaha), but to no avail. Tried the calibration tool in system settings, too.
This happens with any Froyo build/ROM I've tried. Did battery pull, etc., no go.
Anyone have any suggestions?
Finally someone else has asked about this. There is an app called "Surveyor" that is used to measure distances with the camera but ever since I started using custom ROMs it isn't able to find horizon. Any help with a possible fix would be appreciated.
Sent from my SPH-D700 using XDA Premium App
I had a problem similar to this (the compass was pointing way off and very erractic). I used an app called Sensor Debug and found that my pitch axis was reading -178 lying flat on a table. I went into the phones display settings and chose the Horizontal Calibration, put the phone upside down flat on a table, but hanging over it so I could reach under and push the Calibrate button. This worked for me like a champ! (Calibrate upside down). I noticed this after the OTA Froyo.
I have the same issue as the OP. I tried installing that sensor debug and it showed 0 for pitch and 0 for roll when laying flat... note... I put it flat but with the camera hanging over the edge of the table.
Anyways, Google Skymap fails for me too...
bump... any word... hopefully from a dev on what is happening?
Not flat with the camera hanging off... upside down flat.. screen side down.. with enough of the screen hanging off to hit the calibrate button..
Sent from my SPH-D700 using XDA App
Hmph.
Welp, looks like I've got to post here, as I'm a new enough member and don't have the necessary # of posts to post to the Developer forum!
In case anyone from the ACS/SyndicateROM team is reading this: AWESOME JOB. Flashed EC05 and Takiya (1.1.0) without a hitch. Amazing that it just keeps all data/settings. I can't thank you guys enough!
Back to the point of this thread: Accelerometers are still not working correctly, even with EC05. I've re-tried:
- Android horizontal calibrate (under settings) both screen up and screen down
- system/bin/sensorcalibutil_yamaha, both screen up and screen down
- Battery out/battery in
- Recalibrate from within GPS test.
Good news is compass works, GPS works. Within GPS test there's a pitch/roll sensor. Doesn't seem to want to register above 90 degrees.
If someone is running EC05/SyndicateRom 1.1.0, would you try running Google SkyMap and see if you can see above the horizon? Basically, I can tilt down and look at the Nadir, but when I tilt up, no matter how far I tilt up, in landscape or portrait mode, it won't show anything above the horizon.
Thanks!
EDIT: Er, the app I use is called "GPS Status," it has the pitch/roll/calibrate stuff.
It seems to work for me (running SRF 1.1.0).
Unless I'm just interpreting what I see incorrectly, but if I start out pointing down, and gradually shift to pointing up, it crosses what I assume is the horizon (because it has directions like north/south written on it) and keeps going.
I'm pretty sure it worked for me on previous versions of SRF though.
my samsung wave's accelerometer is off by a few degrees, any fix for that? thank you
There should be a way to reset the device, but I have yet to discover it, it should be under "adminastrating menu" or "admin menu", not sure.
.......................................................
What the hell do you mean by all dots in various topics??
please explain otherwise it will be considered as spam
Where i found this "admin menu"?
try this by typing in "call keypad" while phone lies on flat ground
*#66225*# Motion Calibration
te_chnix said:
try this by typing in "call keypad" while phone lies on flat ground
*#66225*# Motion Calibration
Click to expand...
Click to collapse
WTH!!! After doing this now I can't even turn left! I have tot turn the pjone 360 degrees to turn the orientation to the left. Is there any way to reset the earlier settings! Or else I will sue you!
I have the same issue hope theres an answer
Tried that on 2 phones. S8500 and S8530.
Everything works fine for me.
Try different positions for calibrating and test it with sWaterLevel.
Should be "free".
SuperDeform said:
I have the same issue hope theres an answer
Click to expand...
Click to collapse
Yep, same here.
*#66225*# works for me
Finally I solved it. I had to calibrate the phone with it kept at 30 degrees to the floor.
Depending upon the accuracy of the workers and place of build, the sensors might be placed wrongly. So keeping the phone flat and calibrating the phone is not a good idea for all phones.
I solved my problem by keeping the phone flat and opening asphalt 5. After the initial calibration, in asphalt 5, when the phone is kept flat, my car kept going to the right. So I calibrated the phone with the bottom part of the phone in the air and the whole phone making an angle of 30 degrees with the ground.
On the other hand if for others, their car goes to the right when kept flat, calibrate the phone with the top of the phone in the air making a suitable angle. Keep increasing and decreasing angles until you find that the car goes completely straight.
Hi i have a question how you put the phone to calibrate it for me any position I choose nothing changes when the phone horizontally my screen is rotated to the right it is for all applications except "Asphalt" where nothing changes (even still turns slightly right).
te_chnix said:
try this by typing in "call keypad" while phone lies on flat ground
*#66225*# Motion Calibration
Click to expand...
Click to collapse
Nice code... Thanks...
I think I've buggered mine as I had it flat on a desk and now the system sensor test (*#0*# then # for sensors) is showing wacky figures... I'll have to hold my phone in strange positions to correct it
I have mistakenly caliberated it incorrect and i also upgraded to bada 2.0. Now, there is no way to recaliberate as 66225 doesn't work.
I've searched around and so far I haven't found anyone else who has this issue, so I thought I'd throw it out here:
I noticed that the compass was never working, in google maps, gps tools, or Ingress, so I downloaded "Phone Tester", and it shows the compass as almost completely static when I rotate the tablet on a flat surface. The pitch and roll change just fine. The other odd thing is that when I tilt my device up or down, which should only change the pitch, the compass shows different angles, as if the reading for the compass was coming from the pitch instead of the magnetic pull.... odd.
Here are some things I've tried:
1. Complete wipe of rom, system, data, etc.
2. Stock roms and CM11
3. The built in kernels for the stock rom and CM11, as well as blackhawk's kernel (v1 & v1.3)
4. Calibrating the compass via "GPS Status" app (multiple times)
5. In an act of semi-desperation I tried a suggestion to take a weak magnet and run it around the top corners of the tablet to "unstick" the magnetic sensor. Interestingly enough, that changed the sensor reading, which confused things even more for why it would be connected with the pitch instead of magnet compass pull.
6. Removing it from it's case. Using a different case. Tapping it gently, again to "unstick" the sensor?
I would be grateful for any ideas and/or collaboration if anyone has had the same issue.
EDIT: It seems that the sensor was simply stuck. I took it out of the case again and ran a kitchen magnet along the edge. This time it released it to work properly, though the magnets in both of my tablet cases seem to be pulling it in wrong directions.
When using Google Maps, I'll press the circle to center in on my location, and the arrow is supposed to show the direction I'm facing. About half the time, it shows me facing about 30 to 90* in the wrong direction. The arrow will move left or right as I do, but still faces the wrong direction. There have been occasions when it will show the dot and arrow moving and facing backwards while I'm driving. This hasn't affected Navigation, as it still accurately shows my location. Has anyone else noticed this, or have a solution?
What I've tried so far: Sensor Calibration under the *#0*# menu.
Also, I had this issue on my Note 4 as well.
Welcome to Samsung crap GPS. Crap radios as well, the radio on the edge drops more signal then on the Note 4.
DigitalChris602 said:
When using Google Maps, I'll press the circle to center in on my location, and the arrow is supposed to show the direction I'm facing. About half the time, it shows me facing about 30 to 90* in the wrong direction. The arrow will move left or right as I do, but still faces the wrong direction. There have been occasions when it will show the dot and arrow moving and facing backwards while I'm driving. This hasn't affected Navigation, as it still accurately shows my location. Has anyone else noticed this, or have a solution?
What I've tried so far: Sensor Calibration under the *#0*# menu.
Also, I had this issue on my Note 4 as well.
Click to expand...
Click to collapse
Unless you're military... I wouldn't so much worry about where my "GPS arrow" is facing... and just hope that it is an accurate location. Apps like Skymaps, etc will have that "un-usability" but for the most part... if your pretty close to the street, and the location of your device is mostly on point.. I would just get use to it.
Wouldn't say it's a Samsung defect either.. it's more of a "expecting your phone to perform as well as a satellite GPS tracker" issue...
Like I said, would just try to get use to it. Most often, when I cross an intersection, my phone shows me crossing ab ok about the same time. That's all that should matter. The directional point is something that will never work like it does in COD, etc. Lol
Sent from my SM-G928T using XDA Free mobile app
The part that bugs me is that for years I've never had this problem on any android phone, now all of a sudden it's an issue on two samsung phones in a row. :^(
Sent from my SM-G928T
I have a temporary fix that must be done while an app is using the compass. Rotate the phone two full circles on all three axis, one after the other. Like turn the phone full round as if taking a panorama, then a full circle like capturing a panorama of the floor then sky, and lastly a full spin like the phone is on a turntable in front of you. The compass should be stellar right after this and at least prove to you that it CAN work.
I asked some hardware buddies of mine at Qualcomm and they told me some reasons why it sucks on phones. The magnetometer that scans relative magnetic field strength does not self calibrate whenever it is subjected to new fields. This happens very often as you pass through varying fields all the time. If the phone was kept away from all of these, the phone still would need calibration as its own operation creates magnetic fields that may tamper with its magnetometer depending on placement and shielding.
hate to say it.
DigitalChris602 said:
When using Google Maps, I'll press the circle to center in on my location, and the arrow is supposed to show the direction I'm facing. About half the time, it shows me facing about 30 to 90* in the wrong direction. The arrow will move left or right as I do, but still faces the wrong direction. There have been occasions when it will show the dot and arrow moving and facing backwards while I'm driving. This hasn't affected Navigation, as it still accurately shows my location. Has anyone else noticed this, or have a solution?
What I've tried so far: Sensor Calibration under the *#0*# menu.
Also, I had this issue on my Note 4 as well.
Click to expand...
Click to collapse
I do not experience this problem at all and keep my phone in the hub between the front seats in my car and use Android auto in my car. However the poster above is correct about resetting your magnetometer. May be your magnetometer is faulty or fried. Also what position do you keep your phone in the car? That could make a difference, I would rotate phone until it shows you the right direction.