Credit to: abrognlie for pointing this out here: http://forum.xda-developers.com/showpost.php?p=11552644&postcount=163
Figured this would be easier to find in searchs.
Problem: Your compass is backwards and overly erractic and inaccurate.
Solution: Upside down horizontal calibration
How: Plant the phone on a flat surface upside down. A low ceiling, top of a door frame etc. Make sure it's flat and facing upside down. Go to: Settings, Display, Horizontal calibration and calibrate it upside down.
Bingo bango, your broken compass should be fixed. This also cures slow auto rotation
Just tried that. Still as erratic and jumpy as ever.
DiGi760 said:
Just tried that. Still as erratic and jumpy as ever.
Click to expand...
Click to collapse
Hardware problem?
The first time I used Google Maps with EB13 it told me that the compass needed to be calibrated and to move the phone several times in a figure 8 manner. I did it, and the compass has been fine. I'd never seen that before. I hadn't used the compass at all before this, so I don't know if it "fixed" a problem or if I just didn't have a problem, but I thought I'd throw it out there for people who are having problems.
edonnelly said:
The first time I used Google Maps with EB13 it told me that the compass needed to be calibrated and to move the phone several times in a figure 8 manner. I did it, and the compass has been fine. I'd never seen that before. I hadn't used the compass at all before this, so I don't know if it "fixed" a problem or if I just didn't have a problem, but I thought I'd throw it out there for people who are having problems.
Click to expand...
Click to collapse
Same for me but it was still broken. X-Plane was unplayable, auto rotation was slow and sometimes unresponsive because the compass was backwards and jumping direction erratically. (download a compass app and check yours) North was south, etc.
The upside down trick 100% cured the issue. Not the figure 8 or the right side up calibration.
*shrug*
Wow! Best find ever! The upsides down calibration worked for my slow gsensor lanscape bug! All this time, rooted was needed for the
"system/bin/sensorcalibutil_yamaha" code to work! Very nice!
I wish I could claim credit for this (the member who deserves all the credit is styles420), and I wish it worked for everyone, but someone found this back when DK28 first leaked. It seems to help with a group of us with sensor data that gets mapped backwards during the flash. It shows up in the compass or google sky maps, but it seems to be a problem with the g-sensors that affects how the compass works.
Sent from my SPH-D700 using XDA App
DiGi760 said:
Just tried that. Still as erratic and jumpy as ever.
Click to expand...
Click to collapse
try downloading GPS Status from the market. Open it and do the calibration tools. Should fix this. Also may improve your GPS (if it isn't doing well)
Possible, but it was the same on my previous epic. I haven't put too much effort into it since I don't really need a compass very often, but it would be nice to have it work for once.
djbacon06 said:
try downloading GPS Status from the market. Open it and do the calibration tools. Should fix this. Also may improve your GPS (if it isn't doing well)
Click to expand...
Click to collapse
I already have GPS Status. I did that calibration from that again, and it is still messed up. It jumps a little less, but I can turn the phone 90 degrees and the compass rotates 180. Then I turn the compass 90 degrees the same direction, and the compass jumps backwards 90 degrees. I'm having a really hard time figuring out a reason for the pattern. I might have to sit down and draw some compass diagrams.
Worked for me. Fixed slow auto rotate as well
Sent from my SPH-D700 using XDA App
it fixes mine! thanks you for finding a fix!
Fixes mine. Thanks for posting this!
Sent from my SPH-D700 using Tapatalk
SON OF A- I was just about out the door to get a replacement. I tried everything a month ago and gave up.
This fixed it.
Sky maps works perfect again.
Thank you and those who figured this out.
Home run battle 3d just became a hell of alot easier now. Thank you
Sent from my SPH-D700 using Tapatalk
tried all solutions here. no joy
Another issue, maybe?
I wonder if there might be an underlying issue here...
Was doing some research on why my battery life is garbage after EB13.
I hit on this thread because it looks like the compass sensor is consuming a ridiculous amount of CPU... I mean, foregrounded using 7% CPU when nothing else is going on.. like, no compass app or maps being used.
With my Epic pretty much quiescent, top consistently reports it (/system/bin/sensorserver_yamaha) as the highest user. Under DI18, it never even cracked the top ten.
Samsung Epic (EB13 Official) + Clockwork
wow thanks for the tip! i almost returned my epic because of this.
Amazing... how you found this out is beyond me, but it works!
Related
Google Sky Maps. I just installed this again and am getting weird behavior. As I rotate up above the horizon everything shifts towards the west, and I can't see the sky. I used the new time shift feature to watch a sunrise..... Sun went below the horizon at sunrise?
Using Bonsia ROM, not sure if this is a 2.2 Froyo problem or what. Searches bring up mag calibration, but this seems more profoundly wrong.
It's not a Froyo problem, the compass in the Epic seems all wonky and I've never gotten it to work quite right.
Orbiting234 said:
It's not a Froyo problem, the compass in the Epic seems all wonky and I've never gotten it to work quite right.
Click to expand...
Click to collapse
I never had that problem in Eclair; sky map would function almost perfectly. I upgraded to stock Froyo and I have the same problem (and yes, I did the terminal emulator fix).
You must be in the great minority. I have yet to see an Epic that consistently gets its compass headings reliably correct nor have I ever seen Google Sky Map move nearly as smooth as any other android phone (very jerky).
My google sky also worked perfectly under stock eclair, but once I started futzing around with custom roms this and froyo that, **** got weird..
I DID however find a fix.. you need to calibrate your compass.. There's a couple ways, one long and complicated involving terminal emulators (which btw: didnt fix the problem for me) and the other, seemingly silly, "hold your phone and wave it around in a figure eight motion" which did the trick..
so.. go outside, preferably where lots of people can see you, hold your with your arms fully extended and wave it around in a figure eight..
The sillier you look, and the more people that can see you, the more likely it is to work
The figure 8 trick solved mine as well. Insanity is the answer.
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic! http://mobilehighway.blogspot.com/
Figure 8 trick didn't work for me, which is weird cuz I have a compass app on my phone and it almost perfectly points north, same goes for google maps. Any suggestions as to why sky maps isn't functioning correctly?
I wish google would fix the night mode on this app. It doesn't do a lot of good to have everything on the screen a dim red, but then have a blazing white menu pop up whenever you want to find something specific in the sky. How, exactly, is that supposed to help you keep your night vision while star gazing?
Just saw a guy with a stock Epic and his G Sky works fine. Must be a froyo thing. Don't think it has anything to do with the compass calibration...mine seems to be fine in compass apps. This problem is more related to the accelerometers... the app inverts axis or something when you rotate the phone above the horizon.
Does anyone have it working right on a 2.2 ROM?
Did some more testing using the app GPS status. It gives pitch and roll readout. In my case as I increase pitch or roll above 90deg, the readings stop at about 86 degrees and then don't change.
For some reason we're capped to less than 90 deg. Any ideas? Can someone with 2.1 try GPS status and see what kind of pitch indication you get if you go above vertical?
.... and Paper Airplane game doesn't work. Great free game that uses pitch and roll of the phone to control the plane flying through obstacle course.
With 2.2..... can't pitch up, and the plane won't climb! So I really don't think it's a G maps problem. Something is wrong with our 2.2 inclination settings.
Edit: Can a MOD change the name of this thread to include "Froyo inclination error"?
Edit: Huge thread in another area of xda. http://forum.xda-developers.com/showthread.php?t=803242 regarding sensor calibration. Kind of deep for me.
Does this work in stock 2.2? Anyone?
Alright... I'm back on a stock DI18, full data wipe. Only thing installed is Sky maps and Sensor Debug.
Sensor Debug values are now (on a flat surface):
Pitch -179/179 (pitching up, it goes up to -150 and stops. or down to 150)
Roll 1 (will go from +/- 30)
Z Force 9.69
The same values I had with a clean install of Bonsai 1.4.
With my original install on Bonsai 1.3 (I had hit the calibrate option from Display settings, and run the su command for system/bin/sensorcalibutil_yamaha) and the z axis was -9.69, pitch values where +/- 86.
If anyone has a working g sky maps, on any build... please get Sensor Debug and post your sensor values (laying flat, and how they change as you pitch/roll the phone).
Thanks.
Hey come on... where's the community support here!
This isn't just G sky prob. Using the app sensor debug, my pitch and roll values are all over the place. When I pitch past vertical, the roll axis starts to change? Somehow the axis values are getting mixed up....
Tried the same test on a Hero and another Galaxy S. There pitch smoothly goes 0 to -90 when vertical to -180 when upside down....with no change to roll axis.
Sent from my SPH-D700 using XDA App
Update: Just odin'd back from DK28 to DI18, and I'm still having the same sky map problem,even though before I never had it.
Finally! Glad you are having problems too. Hope we can get this figured out ASAP.... driving me batty.
I'm going to start a new thread... this source of the Google Sky Maps problem is larger. We're either dealing with a calibration error in the accelerometers or dare I saw hardware. Please join in the new thread.
For now, download Sensor Debug from the market. Also, get the values from /data/system/ms3c_yamaha.cfg.
Let's nail this!
Yesterday I installed a demo of the game 'Winds of Steel' on my Epic. It uses the accelerometer to control the motion of a fighter plane, but I immediately noticed that the motion sensing was way off. It jumps from extreme up to extreme down with no mid-range. Left and right movements are fine, but the up/down issue makes the game unplayable. I checked the forums and even chatted with the developer, and no one seems to have had a similar issue. I've reset the horizontal calibration, rebooted the the phone and even re-installed the game and I still get the same thing. A friend who has a stock Epic says it runs great on his phone, so I'm wondering if it has something to do with Froyo.
I'm running the Quantum ROM with the DK28 modem and EXT4 on my Epic. If anyone else has a similar problem, please let me know. Everything else runs flawlessly on this phone, so this one has me stumped.
Thanks!
I have the same problem from running dk28 (even though I'm back on 2.1 now). Have you tried rooting and then running sensorcalibutil_yamaha ?
Sent from my SPH-D700 using XDA App
You may have one of the Epics like mine that had their accelerometer borked when you went to DK28. The way I corrected it was:
1. Go to settings -> display
2. Choose Horizontal Calibration
3. Turn the phone over so it is face down, and place it so the bottom edge is hanging off of a table, so you can just access the "calibrate" button.
4. Hit "calibrate" (while phone is upside down)
5. Enjoy your properly calibrated accelerometer.
Those of us that had the problem think it is possible due to the sensor data getting written incorrectly on certain phones with DK28.
I wish I could take credit for the process I laid out, but I don't remember who told me about it a month or 2 ago.
Hope this helps!
Calibrating it upside down did the trick. Thanks! I never would have thought to try that.
I'll have to mention it to the developer in the event that other people contact him.
I don't think it's an issue with the game - I think the problem lies in the DK28 update, because I know there are lots of other programs that were affected by it, not just that game.
I'm just glad the solution worked out for you.
Yeah, this issue isn't game-specific. I can't play X-Plane or use Google Sky Map (to look up) because of it.
I've tried multiple times to fix it in 2.1, to no avail. I'm considering flashing to dk28 again to fix it and then hoping the fix will remain if I then flash back to 2.1
Update: I flashed to dk28, calibrated upside down, flashed back to 2.1, and then ran sensorcalibutil_yamaha to fix the rotation issue. It fixed my issue so now the pitch is registering correctly!
Sent from my SPH-D700 using XDA App
i'm finding it's crazy again. 2.3.3 seemed to tack it down, but it seems worse than 2.3.2, and the gps seems a lot slower too.
i haven't been out yet and properly tested it, but has anyone tested it yet?
2.3.4 actually seemed to fix the compass for me, it seems a lot more accurate now.
GPS works well too but I didnt have a problem with GPS on 2.3.3.
if i lie the phone flat the compass will say one direction, if i pick it up, so it's perp to the horizon, it says a different direction. the compass in 2.3.2 went crazy in one particular angle, gittering back and forth, same now
GPS fixed for me as well. I get a fix in five seconds
Compass is less jumpy
2.3.4 no fix gps for my i9023
any 1 got solution?
i am from malaysia
and i hope no need root to fix it
MarkusPO said:
if i lie the phone flat the compass will say one direction, if i pick it up, so it's perp to the horizon, it says a different direction. the compass in 2.3.2 went crazy in one particular angle, gittering back and forth, same now
Click to expand...
Click to collapse
Isn't a compass supposed to be held horizontal to the ground?
Anyways, it's best to wave your phone in a figure 8 pattern from time to time if your compass is spazzing out. This will get rid of any abnormal magnetic fields in the phone.
zero383 said:
Isn't a compass supposed to be held horizontal to the ground
Click to expand...
Click to collapse
try using the look around on google earth
Removed Miss read comment
amir80 said:
GPS fixed for me as well. I get a fix in five seconds
Compass is less jumpy
Click to expand...
Click to collapse
Same here i9023 model
For me the compass keeps his direction, but it is wrong by about 30 degree.
I've just downloaded the Compass app from the market, but it doesn't seem to working correctly. I've tired both 'sensor types' but the direction it shows flickers and is incorrect.
Have any of you encountered the same issue?
you should try another app. I think gps status will work fine.
Sent from my Nexus One using XDA App
sogo87 said:
you should try another app. I think gps status will work fine.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I've just tried that GPS Status app and it does work better then compass, but it seems to be about 40 degrees out when the phone is moves and even seems to wobble abit when it's stationary. I've made sure there's no interference before testing it out
Have you calibrated it?
Intratech said:
Have you calibrated it?
Click to expand...
Click to collapse
Yep, I've done the figure '8' waving
I have this problem too. Definitely a sensor issue -- the apps work perfectly on other phones (and indeed I *think* the compass used to work).
This is really damn annoying -- part of the reason I got the phone was so I can make a gyroscope-assisted compass app.
Hmph.
Just installed it from the market and it worked without any settings adjustment on the SGS II.
Timmmmmm said:
I have this problem too. Definitely a sensor issue -- the apps work perfectly on other phones (and indeed I *think* the compass used to work).
This is really damn annoying -- part of the reason I got the phone was so I can make a gyroscope-assisted compass app.
Hmph.
Click to expand...
Click to collapse
I'm on the phone to O2 getting an exchange.
I'm hoping it's an uncommon problem
Let me know how that goes, I may have to do the same. My compass has since settled down but it is consistently off by about 25-30 degrees...
Maybe this is your problem too
Read this, maybe you have the same problem...
http://forum.xda-developers.com/showthread.php?t=1047894&highlight=compass
Good day XDA. I just noticed that my N7 is having problems with its accelerometer. I was playing temple run and mutant road kill and the characters always veer to the right.
Question is: is this a software or a hardware issue?
also, is there a fix/app if this is indeed a software issue?
thanks
well, i know that there is apps for calibrate the accelerometer, i can´t remember now the name, sorry, but i´m sure that you can find it on the market o google.
Anyways, did you try in diferents places? i mean, maybe the surface where you try wasn´t flat...
thanks for the reply man.. anyway, i already found a way to fix it and it's been holding up.
juanito05 said:
thanks for the reply man.. anyway, i already found a way to fix it and it's been holding up.
Click to expand...
Click to collapse
What's the fix?
What did you do to fix the issue?
Sent from my Paranoid Nexus 7
well first you have to confirm that you indeed have the gyro/accelerometer problem. you guys could download an app for that (i used Android Sensor Box). once that is confirmed, download the app "GPS Status". Run it and go to tools, then calibrate pitch and roll and just follow the instructions. I suggest you guys do this while your device is lying flat on a surface.
after trying this fix, i uninstalled GPS Status, rebooted my device and it held up. played temple run and the character started right smack in the middle lol. also tried checking the sensors using Android Sensor Box and it was calibrated. i just reinstalled GPS Sensor just in case i might need it down the road but im hoping this fix will be permanent. if it isnt, im pretty sure that this is a software problem and an update could give a permanent solution.
let me know if you guys get the same result i had with this.
Thanks
juanito05 said:
well first you have to confirm that you indeed have the gyro/accelerometer problem. you guys could download an app for that (i used Android Sensor Box). once that is confirmed, download the app "GPS Status". Run it and go to tools, then calibrate pitch and roll and just follow the instructions. I suggest you guys do this while your device is lying flat on a surface.
after trying this fix, i uninstalled GPS Status, rebooted my device and it held up. played temple run and the character started right smack in the middle lol. also tried checking the sensors using Android Sensor Box and it was calibrated. i just reinstalled GPS Sensor just in case i might need it down the road but im hoping this fix will be permanent. if it isnt, im pretty sure that this is a software problem and an update could give a permanent solution.
let me know if you guys get the same result i had with this.
Thanks
Click to expand...
Click to collapse
That was amazing man. I have been swearing over this accelerometer issue ever since I got the device, and now it's perfect. :beer:
Sent from my SGH-I747M using xda app-developers app
Had exactly same issues on all three units I have purchased. GPS Status app does fix the problem. Thanks for the solution.
GPS status did nothing for me.
Same problem veering to the right
Held n7 landscape
Reboot
After reboot accelerometer is working fine
Sent from my Nexus 7
bagofcrap24 said:
GPS status did nothing for me.
Same problem veering to the right
Held n7 landscape
Reboot
After reboot accelerometer is working fine
Sent from my Nexus 7
Click to expand...
Click to collapse
This didn't do the thIng for me neither
But I did the job like this.
Open an app that uses the compass. You can use GPS Status, Android Sensor Box or whatever app you like that uses a compass.
twist/turn your device 3 times around each of all the three axes
FINISH
Even after a reboot it works great.
But if you flash a new rom this fix will be broken