Database Info

App to calibrate the orientation sensors?

Mine seems to be really sensitive so that the screen rotates even if I tilt the phone a small amount. Is there any way to fine-tune it?
--
Sent from my HTC EVO 4G using Tapatalk Pro.

Wondering this also since I noticed there is no calibration for it in CM6.

Don't know about on CM6 but on other roms, go to Settings > Display > G-Sensor calibration.

Anyway to do this on non-rooted phones? Ever since I upgraded to Froyo it seems to rotate if I tilt it even just slightly off it's axis

Those directions were for rooted and non rooted phones...

Greenfieldan said:
Anyway to do this on non-rooted phones? Ever since I upgraded to Froyo it seems to rotate if I tilt it even just slightly off it's axis
Click to expand...
Click to collapse
Turn off garbage rotation with Switchpro

Anyone gotten a reply from Cyanogen? I messaged him on Twitter, but he never responded.

If you download, GPS Status from the market and in settings under " Help and release notes " it says this...........
My compass points to the wrong direction or I'm asked to calibrate my compass. What should I do?
Your phone contains a digital compass which measures the magnetic field's strength in three direction with three separate sensors. The orientation of your phone is calculated from these values. Unfortunately the sensitivity of the sensors are a little different. To correctly calculate your orientation your phone must measure first these differences. This is done during the calibration process. To calibrate your phone, simply find a space where no external magnetic field is present (preferable outside of buildings) and rotate your phone 1-2 times on EACH of its three axes (Swinging your phone in big 8s in all direction will also do, but it' less scientifically correct ). If you feel that your compass has become inaccurate you can repeat this procedure.
But i dunno if it works or not..

BAleR said:
If you download, GPS Status from the market and in settings under " Help and release notes " it says this...........
My compass points to the wrong direction or I'm asked to calibrate my compass. What should I do?
Your phone contains a digital compass which measures the magnetic field's strength in three direction with three separate sensors. The orientation of your phone is calculated from these values. Unfortunately the sensitivity of the sensors are a little different. To correctly calculate your orientation your phone must measure first these differences. This is done during the calibration process. To calibrate your phone, simply find a space where no external magnetic field is present (preferable outside of buildings) and rotate your phone 1-2 times on EACH of its three axes (Swinging your phone in big 8s in all direction will also do, but it' less scientifically correct ). If you feel that your compass has become inaccurate you can repeat this procedure.
But i dunno if it works or not..
Click to expand...
Click to collapse
That just calibrates the compass.

Gallery3d bug, sensor always on draining the battery

A fellow on the i9000 forum posted this and it seems like it probably affects all galaxy s phone http://forum.xda-developers.com/showthread.php?t=838949
To check if the sensor is always on do this
Type *#*#4636#*#* in the dialer
Click Battery history
Pick Sensor usage
Click on gallery and you'll see for how long the sensor has been on, seems like the sensor never shuts off after you exit the gallery.
To fix this glitch delete Gallery3d.apk from /system/app using root explorer or a terminal, restart the phone and download Gallery3d from the market.
There's also a new gallery3d app from the desire, it doesn't seem to have this glitch either plus it has a cool pinch peek feature http://forum.xda-developers.com/showthread.php?t=847656

Thanks alot. The new gallery also gets rid of the low res bug. Zooming in keeps the detail. Nice.
From a phone

I looked but my gallery sensor seems to turn off so may not be an issue with everyone, but thanks for post

ERRR
only i'm suffering from this problem ?
when i installed that zip file (from recovery) gallery 3D (deleted the 1 from RE like u'v said)
now when i load a picture it's loading first in LOW res than only after 2 sec it gives u the full nice RES
why is that !?? u can't enjoy seeing your pictures like that
how do i go back to the first ORIGINAL gallery APK ?
10x
ps in the original gallery it was loading HIGH RES instantly and extremly FAST
using I9000 2.2 VOODOO LAGFIX

interesting...I noticed my gallery was keeping the sensor on as well. new version from the market has fixed the problem.
does anyone know how much battery drain this is actually causing? I have noticed that the app "Bedside" is also using the sensor all the time- even when it has seemingly been killed- which seems very strange.
also- does this "sensor usage" stat apply only to the light sensor? or does the phone orientation sensor count toward it as well?

One thing i don't see mentioned here (it is in the original i9000 thread) is that this battery drain bug came with the official Froyo release on the i9000 and didn't seem to exist in 2.1.

How are you all getting the new version from the market? When I search for "Gallery", nothing resembling the official app comes up anywhere in the first hundred or so results...The rom I'm running has the AT&T version of the market, maybe thats the issue?

OP - Thank you for the instructions. I tested mine and it seems that Homerun Battle 3D was using the sensors even though it had not been launched in a couple days. It was maxed as the most Sensor usage since unplugged this morning.
I uninstalled it and will update if this helps my battery.
Thank you again

I just deleted my gallery app using Titanium backup and searched for "gallery 3d" in the market. I'm running cognition which I believe has a fixed build.prop so that might be why I can see it in the market.
looking back in the history, the app "bedside" has used significantly more sensor than even the Android system. I am a bit concerned that the app may be draining my battery. since the app is paid, I would like to raise the issue with the developer but I don't really know how much battery drain it is causing or if it is light sensor, orientation sensor, or something else. I'd appreciate any help.

thanks for this info.
I dont have this particular issue but I do see "camera" as using the sensor for the past 3 hours. I opened the camera this morning but I have closed it since. Does this mean the sensor has been using the battery all this time?...just curious...

Just wanted to update.
After finding out that Homerun Battle 3D had the sensors running when the game itself had not even been launched, I uninstalled it..
Today so far after being unplugged for 7hr 47m I am at 93% battery. Which isnt bad IMO

A interesting GPS Test with surprising results...

TL;DR version:
1)Start Google Navigation, pick destination, start driving. Result: Sporatic or no lock and definitely no turn by turn working.
2)Start Google Navigation, pick destination, start GPSTest, start driving. Result: Almost constant lock and turn by turn works astonishingly well.
What gives?
Alright, please read this whole post, try it out, then comment on whether there is something to this or maybe I'm just crazy (a very definitely possibility). I was playing around with the GPS today and tried the Vibrant GPS hardware fix (pulling up the contact so that the GPS antenna is making better contact with the metal back). There wasn't much of a difference, so I decided to take the back off and run the GPS without the metal backing. I found that interestingly enough I was getting a better SNR with the back off than with the back on it was 8/8 at about 25-30 with the back on (using GPSTest) while with the back off it was 8/8 with 30-35.
Now comes the really interesting bit. On my drive home today I decided to see how well I could hold a moving lock. I turned on Google Navigation, pointed to my house, and started driving. Needless to say I was not able to hold a lock for very long. However, if I left the navigation app running and started GPSTest, all of a sudden I was getting the turn by turn voice pretty accurately. I then exited GPSTest and probably 10 seconds later lost my lock again. Open GPSTest, BOOM lock back on and turn by turn working again. Am I just hitting a really lucky coincidence or is GPSTest doing something we're not aware of? Please post here if you can either a) replicate what I'm seeing or b)think I'm blowing smoke cuz you aren't seeing a lick of difference.

smoking blow/10
anyways I'll try it out

comdei said:
smoking blow/10
anyways I'll try it out
Click to expand...
Click to collapse
BTW... this is GPS Test by Chartcross Limited, NOT the one by Mike Lockwood. You're welcome to try both however.

Previous GPS threads have repeatedly documented the positive effect of moving your nav app to the background. Theories on it center around backlight, temperature, or CPU/GPU. My own myTracks tests seem to point towards CPU/GPU. Or, at least, they seemed to rule out temperature or backlight as a factor.

So did you have GPS Test in the foreground during this test? This will pretty consistently give you improved performance over having Navigation up. If you turn the screen OFF altogether, it almost works as well as a real GPS! Check out the difference by recording a few drives in MyTracks -- it's night and day, on my phone at least.
My personal, uninformed theory (guess) is that the CPU/GPU and screen during Navigation are starving the GPS subsystem of power, causing either reception issues or causing the clock to desync and lose the position of the satellites it's tracking.
Ah well, such is life.
Perception 10.2 | SpeedMod K13D | I9000XXJQ1

I noticed this as well with my old setup (phone bought in August 2010 running Cognition & JK4 radio firmware). I got one of the refurbs from the random power off fiasco and GPS seemed to be just as unreliable. I've recently flashed the JL2 radio firmware, and GPS locks on within seconds and stays locked around town - as it should. I think a lot of people's issue would be completely resolved if they played around with radio firmwares...

Ikonomi said:
So did you have GPS Test in the foreground during this test? This will pretty consistently give you improved performance over having Navigation up. If you turn the screen OFF altogether, it almost works as well as a real GPS! Check out the difference by recording a few drives in MyTracks -- it's night and day, on my phone at least.
Click to expand...
Click to collapse
Yeah, GPS Test was in the foreground, navigation in the background. I get the feeling however its more to do with the application than the hardware. I say this because having other apps in the foreground doesn't quite have the same effect for me. Is that the case for everyone else as well?

knyghtryda said:
TL;DR version:
1)Start Google Navigation, pick destination, start driving. Result: Sporatic or no lock and definitely no turn by turn working.
2)Start Google Navigation, pick destination, start GPSTest, start driving. Result: Almost constant lock and turn by turn works astonishingly well.
What gives?
Alright, please read this whole post, try it out, then comment on whether there is something to this or maybe I'm just crazy (a very definitely possibility). I was playing around with the GPS today and tried the Vibrant GPS hardware fix (pulling up the contact so that the GPS antenna is making better contact with the metal back). There wasn't much of a difference, so I decided to take the back off and run the GPS without the metal backing. I found that interestingly enough I was getting a better SNR with the back off than with the back on it was 8/8 at about 25-30 with the back on (using GPSTest) while with the back off it was 8/8 with 30-35.
Now comes the really interesting bit. On my drive home today I decided to see how well I could hold a moving lock. I turned on Google Navigation, pointed to my house, and started driving. Needless to say I was not able to hold a lock for very long. However, if I left the navigation app running and started GPSTest, all of a sudden I was getting the turn by turn voice pretty accurately. I then exited GPSTest and probably 10 seconds later lost my lock again. Open GPSTest, BOOM lock back on and turn by turn working again. Am I just hitting a really lucky coincidence or is GPSTest doing something we're not aware of? Please post here if you can either a) replicate what I'm seeing or b)think I'm blowing smoke cuz you aren't seeing a lick of difference.
Click to expand...
Click to collapse
this worked really well for me. am on andromeda 3. but was getting on locks without staying on continuously. with the approach. gps was spot on.!! a BIG Thanks

I've noticed this for some time when running the GPS Application Test in lbstestmode. Run the GPS test first and then move it to the background and launch your normal GPS program and you'll usually be better off. Needless to say, I'm doing another warranty exchange in hopes of getting one with better GPS hardware soon.

Try this:
Get a mobile hotspot (or someone who has wifi tethering enabled on their phone). Put your phone into flight mode, then turn WIFI on and connect to that mobile hotspot. Fire up navigation, and go for a drive. You'll be amazed at how accurate your GPS is.
That leads me to believe that there is an interference issue in the GSM/GPS antennas. Part of the reason why putting navigation in the background helps improve the GPS performance is because it stops refreshing the map, which means it's not trying to use the GSM radio. But if you fire up Pandora, even with Navigation in the background, the GPS will start going nuts again.
I'm pretty sure AT&T is aware of this, and I even think they have a... well, not a fix, but a way to mitigate the problem.
A friend of mine did a warranty exchange on his Captivate last Monday for a problem with his USB port. The Captivate he got in exchange has been getting much better performance with it's GPS. And since his worked just fine all week, I exchanged mine yesterday. Now, quite often after flashing a new ROM, the GPS will work fine for a day or three. So I'm not going to be convinced mine is working as well just yet. But there are some notable differences from what I've seen before... When I'm tracking my position on Google Maps, my actual position now stays within what the GPS reports as it's error, even when I'm driving around. Previously, my phone might report a 10m error, but my actual position might be 200m or more from where it thought I was. In addition to that, I'm seeing that my phone is locking into more satellites, and holding that lock even as the SNRs drop due to obstructions. And finally, my GPS works just as good while it's in the car dock, whereas before it would only intermittently get enough signal to fix a position. Overall, while my GPS still isn't as good as other phones I've had in the past, it is now actually good enough to use and trust.
I think that AT&T isn't advertising this because it's not something that they can push out over the air or through a Kies update. I'm guessing that either they modified the antennas slightly, or that they installed a new firmware to the GPS chip (at a lower level than the driver)... or maybe both.
Either way, my friend's GPS has been working great all week long, and mine appears to be doing so as well. I'll not say that it's permanently fixed yet, but I'm cautiously optimistic. We'll see how it's doing after another few days go by.
UPDATE 3/28:
Two more days of testing have passed. So far, the GPS is holding up nicely. The only issues are with the car dock. When the phone is in the car dock, the GPS will occasionally drift 5~10 meters off of my position. This doesn't really surprise me, as the electronics in the car dock are right up against the GPS antenna, and simply putting the phone in the dock will drop the reported SNRs by more than 25% - usually a lot more.
Still, even with the car dock, the GPS is perfectly usable. And without the car dock, the GPS is now exactly what it should have been from the get-go.

I've also found that if I run either gps status or gps test to get the fix, then start whatever app I need to use, the performance is much better. Recently I just use lbs test to get the fix, then proceed with whatever app i need to use. Seems to work better, as lbs test continues to work in the background

i have seen this in the past but trying to prove that it is not random has been a problem as i cant repeat the results.
also i dont thing i have ever observed the phenomenon while using control plane mode.
maybe another coincidence, i cant tell but i have been using the control plane version of da_g's fix for a couple months now in combination with the jl3 modem and have gps that many smart phones would envy. i find jl3 to have the most stable positioning and tracking, less blue circles ect. i also find agps settings to hinder tracking. i only set agps mode to standalone. not sure how supl works or if controlplane supl setting is actually doing anything because i was under the impression that supl was part of agps but it is a combination that started working for me and i am sticking to it.

GPS and Ingress

Has anyone else had any issues with GPS and/or Ingress?
Here's the problem. While playing Ingress and being tethered to my phone, the GPS usually cannot get a lock on ANY satelites. I mean absolutely 0. Occasionally I'll end up moving but we're talking hundreds of meter jumps, usually taking anywhere from 20 seconds to sometimes up to 5 minutes for 1 to occur (in the 5 minutes one, I was nearly 2 miles away from where it last jumped.....).
Now, you'd think there was something wrong with my GPS, right?
Well, how come I can go and open my Google Maps application, and within 15 seconds have a lock on 5 to 8 satelites and have correct placement as well?
I've tried this a number of times, where Ingress essentially has me no where near where I should be. I exit out of Ingress and go to Google Maps and nearly immediately it shows my current location exactly without issues.
I've tried nearly everything I can think of to get this fixed. Overclocking/underclocking and such make no real difference here (hoping that maybe there wasn't enough processor speed or the graphics were too intense), has little to no effect as one would hope. Even using a few GPS tools (such as GPSFix, GPS Status and Toolbox, etc...) provide little insight into the problem, as they just confirm my fears, that inside Ingress I get 0 satelites, inside any other GPS application I'll get a lock on 5 to 8 satelites in no time.
Does anyone know of a way that I can truely monitor the GPS while using another application? I'd like some kind of log or something to help figure this out.

darkhawkff said:
Has anyone else had any issues with GPS and/or Ingress?
Here's the problem. While playing Ingress and being tethered to my phone, the GPS usually cannot get a lock on ANY satelites. I mean absolutely 0. Occasionally I'll end up moving but we're talking hundreds of meter jumps, usually taking anywhere from 20 seconds to sometimes up to 5 minutes for 1 to occur (in the 5 minutes one, I was nearly 2 miles away from where it last jumped.....).
Now, you'd think there was something wrong with my GPS, right?
Well, how come I can go and open my Google Maps application, and within 15 seconds have a lock on 5 to 8 satelites and have correct placement as well?
I've tried this a number of times, where Ingress essentially has me no where near where I should be. I exit out of Ingress and go to Google Maps and nearly immediately it shows my current location exactly without issues.
I've tried nearly everything I can think of to get this fixed. Overclocking/underclocking and such make no real difference here (hoping that maybe there wasn't enough processor speed or the graphics were too intense), has little to no effect as one would hope. Even using a few GPS tools (such as GPSFix, GPS Status and Toolbox, etc...) provide little insight into the problem, as they just confirm my fears, that inside Ingress I get 0 satelites, inside any other GPS application I'll get a lock on 5 to 8 satelites in no time.
Does anyone know of a way that I can truely monitor the GPS while using another application? I'd like some kind of log or something to help figure this out.
Click to expand...
Click to collapse
Hello friend. It has been almost a year since you have posted, but I've gone through the same hardships, on different device though.
See my post here, if you still need some solution and see if it helps.

Compass resetting

Does anyone ever have the issue of the compass always pointing in the wrong direction?
I've done manual sensor calibration by going into the service menu (*#0*#, Sensor) quite a few times but the compass always resets.

levitron said:
Does anyone ever have the issue of the compass always pointing in the wrong direction?
I've done manual sensor calibration by going into the service menu (*#0*#, Sensor) quite a few times but the compass always resets.
Click to expand...
Click to collapse
Probably would have been best to not start a new thread for this since you already commented in another one.
My compass is still fine and working properly from my one calibration from the other thread. Are you getting the blue compass line with a "3" next to it?

I had the "3" and blue line. It was pointing to the true North after calibration. Then it lost the calibration. I've since recalibrated it.
I'm keeping an eye out on this. Will monitor it.

So after a few weeks of testing, I've concluded that the compass resets every time I reboot my phone. This happens consistently without fail.
The fix for me is to do a calibration every time I reboot the phone - this means "twirling" my phone in a circular motion (it's faster than doing the separate axis calibration). Usually this will recalibrate my phone in under 10 "twirls".
I guess it's something to do with the compass not being able to store the calibration permanently. Perhaps it's a R/W permissions issue. I'm on stock Three UK firmware, not rooted.