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.
Related
does anyones compass work right?
I have recently purchased Evo and am running latest fresh. My compass is very jittery, inaccurate and requires constant calibration. I have found several people complain about this around the web. I want to know if anyone has compass that just works. On my hero it worked great. On my Evo, skymap is almost unusable. I have to shake (figure eight) phone every time I move it and then it is only close. Should I exchange this evo for another one?
my skymap is always off too!
What's this fig 8 you mention?
I'll google it... I figured mine was just broken. I think I'm HW 002 and 651.6 maybe?
my compass always needs to be calibrated every time it's opened....using the figure 8 motion like you mentioned.
in terms of google skymap:
My skymap also sucks. The app shows the correct image of the sky that I'm pointing to, but everything seems to be off-center a little bit. I've experimented by messing with different G-sensor calibration scenarios(menu->settings->Display->G-Sensor Calibration). My hypothesis on the situation is:
When you put the phone on a flat surface and use the g-sensor calibration tool, the device does calibrate properly...BUT...my belief is that the protruding camera on the back of the device puts the phone just a bit off-center on one of the axis'. I'm guessing if you elevate the bottom of the phone slightly with a very small object(like maybe 4-6 sheets of stacked copy paper) and then run the g-sensor calibration tool it might inadvertently correct your skymap problem.
I did it the described process above very unscientifically (with my finger holding up the bottom of the phone while resting the top of the phone on a surface that's questionably level) and noticed the skymap image was off-set still, but in the complete other direction. This would indicate that you may be able to correct the problem this way if you're precise enough with an off-set calibration.
I just don't care enough about skymap to do it.
What's everyone else's thoughts?
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.
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.
I recently bought a Zenfone 2 (ZE551ML) which works exceptionally well however today I've noticed something odd (probably would have noticed it before but the phone was actually a gift so not at all times with me).
During a call the proximity sensor will only turn off the screen when the phone is close but it will not turn the phone on when I move it away. I've gone through many online articles and in the majority of cases it was a problem with the screen protection. However, I do not use any kind of screen protection.
Additionally I've noticed something really odd. Zenfone 2 has an inbuilt testing suite (SMMI Test) which allows testing various parts of the hardware. The proximity sensor test consists of three steps (NEAR, AWAY, NEAR). They should be self-explanatory (NEAR triggers when an object is close, AWAY when its far). In my case the first step (NEAR) always triggers after the test starts but the other two (AWAY, NEAR) simply won't. That's until I use the app switch button (next to the home button) to re-enter the test application again. The other two steps then complete successfully.
Considering the behavior can I rule out a hardware problem and pin the issues to the software?
The proximity sensor issue was successfully resolved by reverting back to the 2.20.40.90 firmware. The 2.40.40.97 version (at least WW) obviously has issues with it.
You can find detailed instructions on how to perform stock recovery in this topic (http://forum.xda-developers.com/zenfone2/help/reverting-to-stock-firmware-t3225632).
Once again props to kanagawaben and all the people which contributed to this topic.