So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
DroidApprentice said:
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
Click to expand...
Click to collapse
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
machx0r said:
So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Click to expand...
Click to collapse
machx0r said:
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
Click to expand...
Click to collapse
offtohavasu said:
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Click to expand...
Click to collapse
Yeah, I used to use /system/bin/sensorcalibutil_yamaha as well, and it worked very well for increasing the speed/sensitivity of rotation, but seems to be gone in CM7 (Which is built upon AOSP GB 2.3.5). I brought it up in another topic & one of the devs (I forget who) said that there is no known fix right now.
I'll try offtohavasu's tip, but I'm not gonna hold my breath! I've used it before with no success, but I haven't tried it with CM7 yet. Cross your fingers that this is the fix we need!
EDIT: no luck. I tried both the "Compass calibration" (which I didn't expect would do anything for rotation speed/sensitivity, but I tried anyway) and "Calibrate Pitch and Roll," and neither one had any impact.
not working for me either.
My rotation lag is terrible as well, and the upside down / display calibration option has not fixed it. I thought it was just me as this popped up on the last two GB leaks for me. I would love to be able to rotate my phone properly again.
Hate to tease but if I had a computer I could probably whip up a possible fix if I had my computer:/
Sent from my Samsung Legen-wait for it-dary! 4g
This certainly seems to be somewhat hardware related (as in, variations in production quality). I had issues back on Eclair or one of the first froyo leaks, including the bacwards compass that initially lead me to the upside-down calibration discovery, but my rotation speed has been fine since sometime around the release of EC05.
But how long of a delay do we each define as lag? When I had issues, I actually had to shake the phone to get the rotation to register... now, it still hesitates for about a second, but I see that at as a check to make sure it was an actual rotation instead of an incidental, momentary tilt of the phone - I would be annoyed if my screen rotated every time the motion sensor detected the slightest movement
Edit: a full second is an exaggeration, I'm seeing more like half a second of hesitation... Just trying to remain accurate
2nd edit - damn swypos, lol
Sent from my SPH-D700 using XDA App
Related
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
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!
I just wanted to share this with fellow Epic 4G sufferers, er, owners. Zynga's Scrabble clone, Words with Friends has a "shake to shuffle your tiles" option. Well, not an option, really. You can't disable it. For some reason, if my phone isn't lying flat on the table, my tiles shuffle constantly. They have some bug reading the g-sensor. Here's the response I got from them:
This issue may be related to the version of the Operating System that is on installed on your device being out-of-date. Operating Systems are constantly being updated to improve stability and performance, while eliminating bugs. It is highly recommended that you update your Operating System so that your version is up-to-date. By updating your OS, you can increase the likelihood that this issue you are having with the application will be resolved.
Click to expand...
Click to collapse
They go on to explain to me how to update my OS from the Settings menu.
Well, F#$% YOU, Zynga.
I had this issue when I first got the phone. I tried doing the calibration in Settings -> Display -> Horizontal Calibration but it wasn't enough. It wasn't until I rooted and used the command line calibration that it got fixed (and my screen rotation became much more accurate). I'll see if I can find the link to the other calibration tool.
Edit: Found it...
From a terminal or adb shell run /system/bin/sensorcalibutil_yamaha to perform a better calibration. I believe you need to have root to run this. I was amazed how much better this made my screen rotation and questioned why it wasn't calibrated correctly from the factory...
machx0r said:
I had this issue when I first got the phone. I tried doing the calibration in Settings -> Display -> Horizontal Calibration but it wasn't enough. It wasn't until I rooted and used the command line calibration that it got fixed (and my screen rotation became much more accurate). I'll see if I can find the link to the other calibration tool.
Edit: Found it...
From a terminal or adb shell run /system/bin/sensorcalibutil_yamaha to perform a better calibration. I believe you need to have root to run this. I was amazed how much better this made my screen rotation and questioned why it wasn't calibrated correctly from the factory...
Click to expand...
Click to collapse
Thanks. I haven't tried that. I think I forgot to run that since I last reflashed my rom. I'll give it a try and see if it fixes the issue. Since Zynga isn't going to be any help.
Edit: No dice. Hmm, I was sure that would fix it. Darn.
machx0r said:
I had this issue when I first got the phone. I tried doing the calibration in Settings -> Display -> Horizontal Calibration but it wasn't enough. It wasn't until I rooted and used the command line calibration that it got fixed (and my screen rotation became much more accurate). I'll see if I can find the link to the other calibration tool.
Edit: Found it...
From a terminal or adb shell run /system/bin/sensorcalibutil_yamaha to perform a better calibration. I believe you need to have root to run this. I was amazed how much better this made my screen rotation and questioned why it wasn't calibrated correctly from the factory...
Click to expand...
Click to collapse
Because the Epic was a last minute patch-work job, that's why. From the software (it was originally supposed to run Bada, not Android) to the GPS (they were going to use another chip or something, but Google put the kibosh on that so they had to replace it at the last minute). It was all patched up just before it was shipped out.
Our devs here don't get enough credit considering the sorry state this thing was in from the get-go.
I play the game and don't have sensor issues, what ROM are you on? I'm assuming you've already calibrated your sensor?
Yeah, I ran the calibration today. Had forgotten to do it since the last flash. I'm on rooted EC05 stock.
I'm going to play around with CM7. Maybe when I flash back I'll reinstall from scratch instead of a nandroid restore. Possible I've screwed something up.
Glad to hear that it should be working and isn't a bug in Words.
Jason
I stopped using WWF when it stopped displaying properly with AdFree enabled.
jasonsf said:
Yeah, I ran the calibration today. Had forgotten to do it since the last flash. I'm on rooted EC05 stock.
I'm going to play around with CM7. Maybe when I flash back I'll reinstall from scratch instead of a nandroid restore. Possible I've screwed something up.
Glad to hear that it should be working and isn't a bug in Words.
Jason
Click to expand...
Click to collapse
Yeah, my backups were borked, best stable thing for me was stock ec05 rooted, odexed. I just remove bloatware, etc, but I still calibrate my sensor on a flat surface even though my sensor is calibrated fine.
That is funny, I have the exact opposite problem. I find that the WWF shake to shuffle feature doesn't work very will on my Epic. I have to practically hit it against the wall to get it to shuffle. lol
I have words with friends adfree and i don't have the shuffle issue and i'm on bonsai 4.0.1
I do hate zynga developing team on android ugh..... there ipod touch one is so much better...
Also they have come a long way with words with friends, the only issue/bug i have with it is the damn notifications suck monkey balls!!!
There hanging for friends is a disaster even adfree it always reloads old games i deleted and won or lost and makes me clear its data every 3 days
It needs a lot of work!!
Zynga needs to get their sh*t together on android!!! or hire some better developers. I consider the android version of both games like a direct port somehow running on android.. feels like garbage SMH i may get rid of them
In the top left corner of my KF there seems to be a sensor. Anyone know what it is for? It doesn't seem to do anything when I cover it.
It is a light sensor that could be used to automatically adjust the screen backlight for example.
Yea but it doesn't seem to do that. I cover it and the screen brightness doesn't change. Is there a setting I am missing?
interesting - i think to remember there was a setting in settings->display called "auto brightness" in stock 6.2 and it was not activated by default - not shure but i think so
this setting seems to be gone in 6.2.1
found that:
http://forum.xda-developers.com/showthread.php?t=1351077
and
http://forum.xda-developers.com/showthread.php?t=1366894
and
http://www.amazon.com/forum/kindle?_encoding=UTF8&cdForum=Fx1D7SY3BVSESG&cdThread=Tx1A25EP3Z5BWB9
maybe i got mine with 6.0 ...
and here a picture of old times:
http://attachments.xda-developers.com/attachment.php?attachmentid=791845&d=1321998472
It should be a light sensor, but on my cm7 fire...it seems not functioning.
-Zeta- said:
It should be a light sensor, but on my cm7 fire...it seems not functioning.
Click to expand...
Click to collapse
It does not work currently on CM7, see post from whistlestop...
http://forum.xda-developers.com/showpost.php?p=21300591&postcount=820
I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful
nateware said:
I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful
Click to expand...
Click to collapse
See same post I listed above. It says that they haven't got the light sensor working in ICS either.
It worked originally in the Kindle Fire 6.0 release but was removed in the 6.1 update and has not been re-enabled in any version ROM that I know of.
Those that had the KF with 6.0 said it didn't work well which is why the most likely disabled it.
The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...
Thanks everyone, that explains it!
fallingcowdude said:
The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...
Click to expand...
Click to collapse
Doubtful. One the KF doesn't come with a case and many cases have the hole for it. Mine does. More likely, there is a hardware issue.
I also note that many phones which have the same thing work better by turning the auto off. Using auto uses more battery on my Dinc, so I just turn it off.
They removed it because it was like watching a bad monitor with a low flicking refresh rate.... it was sampling like 3-5 times a second and adjusting. I thought I was going to have a seizure until it updated
Sent from my Kindle Fire using xda premium
I am relatively new to this device, coming from Samsung. So different hardware, newer Android. Trying to work through everything. The phone is rooted and I have been making some mods including Xposed.
My latest problem is that the compass seems to be stuck pointing North (at least on some apps). This affects GPS Status and HereWeGo, both of which I have used for years now without problems. Interestingly, this does not seem to affect GPS Test app which I have also used for years.
I have seen a few posting elsewhere mentioning this same problem. Those were for Verizon models, if I recall. But even those posting said it happened before rooting, etc.
Anyone have any suggestions? Thanks!
Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.
pistacios said:
Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.
Click to expand...
Click to collapse
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers
whitedavidp said:
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers
Click to expand...
Click to collapse
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.
KUSOsan said:
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.
Click to expand...
Click to collapse
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!
whitedavidp said:
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!
Click to expand...
Click to collapse
When it happens test to see if you can rotate your phone into landscape mode. Mine rarely happens for me and it only happens upon rebooting. It won't just happen while the phone is on