Develop Bugs

HTC desire, magnetic field sensor problem on rooted rom

Recently I rooted my HTC desire and installed the froyo stock rooted rom, the person who published it says that he did not change anything in the Rom however I'm having problems with my magnetic field sensor. The compass app just goes crazy, doesn't point in the right direction plus Google sky maps also does not work. Please correct me if I'm wrong but my theory is that is the magnetic field sensor at fault. Does anyone know how to fix this?
Sent from my HTC Desire using XDA App

you can calibrate by going to compass and waving it in figure 8 direction 3-10 times. this might help the sensor.

compass / gps only works once. root problem?
I am having the exact same problem with my rooted samaung r720 vitality. I am not sure if this problem existed prior to rooting but as I can't get a stock rom or back this one up I can't test it. I can't see why a root would cause this problem but who knows. I also have a problem withe gps it only works once maybe you can try this too. Download gps test put it in airplane mode go outside let it run for 2 mins after getting a fix shut off gps fix/ gps for 2 mins and then start it up again repeat this one more time (3rd time) then report your results.
With regards to the compass if you calibrate it it will work for a shortime but this is soon lost. I only have the problem with horizontal movement not vertical. It seem the calibration/ ofset settings are not being remembered.
Pedro
fixed. used another persons nandroid backup of a stock rom. probably firmware was faulty not from rooting process.

Qualcomm Vision GPS drivers

I dont know how many of you guys know about this, but this driver is a life saver for the Evo. For a lot of Evo's, GPS lock can take FOREVER. However, with these drivers, GPS lock on Evo is INSTANT (within 5 seconds)!
I thought that since our phones have qualcomm hardware, these drivers might work. My E4GT (stock with Rogue's EK02 kernel and recovery) takes for-e-ver to get a lock if at all (indoor locks are a bona-fide no-go). However, after flashing this, I now get a quick lock outdoors, and get a lock indoors within 30 seconds. Perhaps it's just a fluke/placebo effect, I dont know. Been rebooting and testing these GPS drivers for the last couple hours and everything seems kosher now. YMMV.
Original Thread:
http://forum.xda-developers.com/showthread.php?p=15760767
Download Link:
http://forum.xda-developers.com/attachment.php?attachmentid=658352&d=1311002339

Are you using Flash, Flash2, or Flash3?
The filename for the upload link doesn't seem to match the obvious ones from the thread.

my bad, stupid me, the download link was actually taken from another thread that wasn't as thorough as the thread i linked to. lemee find the REAL original thread...

How's the stability / speed of GPS lock after you leave the screen off 10 or so minutes?
So far I've been using the following gps.conf + SetCPU profile with good results:
http://forum.xda-developers.com/showthread.php?t=1356865
I already own SetCPU, but it would be nice to offer a solution to friends with the Epic 4G Touch without having to set up SetCPU for them.

i updated my op witht he correct links. sorry for the confusion!
edit:
TalynOne said:
How's the stability / speed of GPS lock after you leave the screen off 10 or so minutes?
So far I've been using the following gps.conf + SetCPU profile with good results:
http://forum.xda-developers.com/showthread.php?t=1356865
I already own SetCPU, but it would be nice to offer a solution to friends with the Epic 4G Touch without having to set up SetCPU for them.
Click to expand...
Click to collapse
can't tell you right now, i'm at work. i will tell you though, i did leave the screen off (with gps status running) for about 20 minutes while i was getting ready for work. when the screen came back on (after i got in my car), only took about 5 seconds to lock on after i opened google maps.

thanks a lot this fix worked for me

i see mention of battery issues on some of the earlier driver revisions... can the people that flash this report on any additional battery drain?
is there a way to revert from these drivers? i guess just nandroid first and revert back if needed?

Thanks GPS fixed
Sent from my SPH-D710 using xda premium

autoprime said:
i see mention of battery issues on some of the earlier driver revisions... can the people that flash this report on any additional battery drain?
is there a way to revert from these drivers? i guess just nandroid first and revert back if needed?
Click to expand...
Click to collapse
Yes, I believe a nandroid backup will suffice. It's like that on the Evo anyways.

Can a MOD please sticky this...I think its very essential... this fix is flawless bro!
Drunk Browsing

Also I sometimes have issues when changing roms with GPS but I have found that the app GPS status works great by just clearing out cache. You go to Tools - Options - choice at the bottom.. let it do its thing and then check your GPS again.
Just an alternative but the GPS fix posted here has worked wonders for the OG Evo

cnstarz said:
I dont know how many of you guys know about this, but this driver is a life saver for the Evo. For a lot of Evo's, GPS lock can take FOREVER. However, with these drivers, GPS lock on Evo is INSTANT (within 5 seconds)!
I thought that since our phones have qualcomm hardware, these drivers might work. My E4GT (stock with Rogue's EK02 kernel and recovery) takes for-e-ver to get a lock if at all (indoor locks are a bona-fide no-go). However, after flashing this, I now get a quick lock outdoors, and get a lock indoors within 30 seconds. Perhaps it's just a fluke/placebo effect, I dont know. Been rebooting and testing these GPS drivers for the last couple hours and everything seems kosher now. YMMV.
Original Thread:
http://forum.xda-developers.com/showthread.php?p=15760767
Download Link:
http://forum.xda-developers.com/attachment.php?attachmentid=658352&d=1311002339
Click to expand...
Click to collapse
Our device does not use the qualcomm gps, it uses a discrete sirfstar gps chip.
Sent from my SPH-D710 using xda premium

I don't see how this will help as the filename included doesn't match what our devices use to load it, the zip one is gps.supersonic.so & ours is gps.s5pc210.so

The whole idea of it being for a differnt phone and manufacturer raises questions but it seems to work.
Sent from my SPH-D700 using xda premium

Your right..but it does work..well for me at least...
Drunk Browsing

Yea it does work
Sent from my SPH-D700 using xda premium

Yup, it works
I have an OG Epic and had to flash a fix (the GPS started sucking pretty bad after the recent 2.3 update), so when I noticed my roommates ET4G was having GPS issues too I convinced her to let me root it (couldn't help myself), and more importantly flash CWM and this fix. I can say, their effects were nearly identical on both devices (albeit I used a different fix for my OG Epic: http://forum.xda-developers.com/showthread.php?t=1321049). After that fix on my device, and this fix on her ET4G we both went from 0-1 Sat locks in GPS Status, and unusable Google Nav to 4-7 locks and completely usable Google Nav. Neither device has had any other GPS issues since the fix (no freezes, etc).

GPS fixed!
Hi,
This is my first time posting on the xda forums as I only read others comments and try out things. Followed the cdma hero when I had it and now this.
Well I had gps issues. when I got this phone I tried every type of fix in this these forums. I tried the trick about configuring the gps.conf in the other forum post, additionally tried putting the set cpu to the screen off 500-500 100priority trick. The gps would work at times but would take around a minute to do so or sometimes when I had the phone on idle for a few hours it would never connect until a reboot.
At this I would have tried anything to fix the gps and I found this thread. I was like might as well try it if anything I can just nandroid back. Man it worked flawlessly. I tested every scenario in which I restarted the phone and it locked in 5seconds and then idled the phone for over 4 hours and then turned on gps status and it connected within 10-15seconds. This is all without clearing the cache too. But when I did clear it, it would lock faster.
My phone is set up with all the previous configurations from the other thread and this gps fix. There is definitely a performance difference, so its not the placebo effect. I haven't isolated if this fix was the the fix that corrected my gps or if it was the combination of both. But this sure works. Sorry for the long post lol hope this helps whoever had the same problem as me.
Ps. The whole phone is perfect. No los. Good battery. It was just the gps issue.
Running eg30 baseband with the 1.5a calkulin Rom and rogue .eg30 stock kernel .

misticd said:
Hi,
This is my first time posting on the xda forums as I only read others comments and try out things. Followed the cdma hero when I had it and now this.
Well I had gps issues. when I got this phone I tried every type of fix in this these forums. I tried the trick about configuring the gps.conf in the other forum post, additionally tried putting the set cpu to the screen off 500-500 100priority trick. The gps would work at times but would take around a minute to do so or sometimes when I had the phone on idle for a few hours it would never connect until a reboot.
At this I would have tried anything to fix the gps and I found this thread. I was like might as well try it if anything I can just nandroid back. Man it worked flawlessly. I tested every scenario in which I restarted the phone and it locked in 5seconds and then idled the phone for over 4 hours and then turned on gps status and it connected within 10-15seconds. This is all without clearing the cache too. But when I did clear it, it would lock faster.
My phone is set up with all the previous configurations from the other thread and this gps fix. There is definitely a performance difference, so its not the placebo effect. I haven't isolated if this fix was the the fix that corrected my gps or if it was the combination of both. But this sure works. Sorry for the long post lol hope this helps whoever had the same problem as me.
Ps. The whole phone is perfect. No los. Good battery. It was just the gps issue.
Running eg30 baseband with the 1.5a calkulin Rom and rogue .eg30 stock kernel .
Click to expand...
Click to collapse
So then, you recommend doing a nandroid backup, then Flash the Drivers, if nothing ends up working, one can always reflash the previous backup and you're set as before?... also is there any wipes needed to be done before flashing the backup?

Calkulin said:
I don't see how this will help as the filename included doesn't match what our devices use to load it, the zip one is gps.supersonic.so & ours is gps.s5pc210.so
Click to expand...
Click to collapse
Placebos are powerful things

Here's a *possible* solution to bad compass...

If your Nitro is like mine, then its' compass couldn't find North to save its' life. Or worse yet it might be in the vicinity, but is very sporadic...Makes it just about impossible to use apps like Google Star Maps or get a proper bearing on direction in Nav when you're at a stop.
If you're also like me, you've tried doing the compass calibrations with the whacky waving your phone in a figure 8 to calibrate. But this hasn't fixed my issue.
But then I tried the rotate-all-axis calibration method and now my compass is much better! Here's what to try:
1. Install GPS Status from the Play Store:
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
2. Open the app, then bring up the Menu and choose: Tools > Compass calibration
3. Rotate the phone along the 3 axises a couple of times, like in this video:
http://www.youtube.com/watch?v=oNJJPeoG8lQ
4. Press okay and your compass *should* be better
NOTE: I just noticed that when I went to test on another phone to compare (I also have a Nexus One), that my Nitro went out-of-whack again and only after a short while from previous calibration! Another calibration and it's working again, but that sucks that it lost its' bearings so quickly like that.
Give it a try and good luck!

Didn't really work for me. I really think this is a hardware issue. Do you think we should demand some kind of rebate for this or something? I know (its somewhere on the threads) that LG officially acknowledged the problem and have yet to come out for a fix. They are knowingly selling a defected phone.

anybody test the phone with any of the new official software?

After calibration compass works correctly.

Wlld1 said:
After calibration compass works correctly.
Click to expand...
Click to collapse
For how long? Work after a reboot?
After flashing a new ROM?

Yes, it works after reboot. But calibration will be lost after flashing new ROM. I dont know where its data is stored.

Wlld1 said:
Yes, it works after reboot. But calibration will be lost after flashing new ROM. I dont know where its data is stored.
Click to expand...
Click to collapse
still sucks. all jumpy and not accurate.
I calibrated mine acouple of times yesterday. The compass worked, but it was very sluggish or spun too fast, and unless I put it on a table, wouldn't stop spinning.
I tried today, and it worked but was very slow to catch up to my movements.
Tried some sky map apps, and it just sucks. Same with the augmented reality apps.
wish there was a fix - or we at least new the problem.
thinking I may go back to stock and send it in to telus and see if there is a fix. Anybody have a working compass after a hardware swap? or repair?

The calibration did fix (even after reboot) the compass but I've noticed it takes sometime to settle after starting an application that use the compass.
At first it looks like the infernal spinning madness is about to start over again but after a few spins it stops at the correct position and stay there.
Weird...
Sent from my Nexus 7 using xda app-developers app

Proximity Sensor Mmuzzy JB 4.2

On this particular Rom, has anyone had any issues with proximity sensor not recognizing the phone to your ear, therefore pressing buttons with your face instead of shutting off? I don't use phone for calls often, but seems every call I've taken I've run across that issue. Thanks!

I am on the latest MMuzzy Toro plus 4.2 and haven't noticed anything like this so far. I don't do a lot of calling but when I take a call it seems to work normally.

I'm running the 11/21 build and have no issue. I have made a few calls and no problems.

OP may try a fresh flash

Thanks I'll try fresh flash see what happens. Just wanted to see if anyone else had similar issues.
Sent from my Galaxy Nexus using xda app-developers app

I've problems with the Proximity sensor too.
Ok.. I am noob. But here is what I've.
I got the new 4.2 takju image from google and followed a very good thread here about how to install it and it worked perfectly. The only thing that is not working is Proximity sensor during Skype calls and Google Talk calls. I really can't understand this but this is the problem I've.
I flashed it twice with takju and it didn't work and installed yajku too and still not working. I am noticing minimal amount of reports about this but over the internet. But no solutions yet.
Hope someone would help us

I have been on his ROM from the day 4.2 dropped and it has been great. Few problems (googles not mmuzy's)but they have been fixed berry quickly
Sent from my Galaxy Nexus using Tapatalk 2

Yes, please check out my thread: http://forum.xda-developers.com/showthread.php?t=2006783
Fresh install, factory resets, the works. Still have the problem. Proximity sensor turns the screen off but the dial pad or even the end call button are active and are pressed by my cheek. It pretty much kills 4.2 for me and I am just about to go back to 4.1.2.
EDIT: Just to clarify, I am running completely stock 4.2 tajku

Just an FYI, appears to be a PGM issue in relation to 4.2. Even checked the PGM app thread and author released an update for the paid version, with the free version being updated soon.

Screen does not rotate!

Hi,
My nexus 7 screen doesn't rotate back from landscape mode. This happens when I watch the BBC iPlayer. Then I have to uninstall the iPlayer and reboot the device each time. This was fine before going to Lollipop.
Any ideas what might be happening?
Sent from my Nexus 5 using XDA Free mobile app

crywolf_68 said:
Hi,
My nexus 7 screen doesn't rotate back from landscape mode. This happens when I watch the BBC iPlayer. Then I have to uninstall the iPlayer and reboot the device each time. This was fine before going to Lollipop.
Any ideas what might be happening?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Check the settings in Display > Auto Rotate Screen. It might be disabling auto rotation but not toggling back.
If that's the case, you could use Tasker to turn auto rotation back on when you exit iPlayer.

I don't use the BBC iPlayer, but like the OP, I have been having this problem as well. Auto-rotate would work again after a reboot, but then just fail at any given time. I've also had this problem ever since Lollipop was installed to my device, and never when I had KitKat or even Jellybean on it. My Nexus 7 2013 is a 16 GB model, and it's on Lollipop 5.1.1 build number LMY47V.

I have this problem on CleanROM 6 with both Elemental and Glitch Kernel. It only happens after a couple of hours of use and a reboot fixes it. I have not been motivated enough to flash the stock kernel to see of that fixes it. I haven't seen it mentioned by anyone else in the Clean ROM thread.

Me too, came here to look for answers.
I hope it's not hardware related.

try clean restore to "stock"
I had this issue with grogg's rom (mostly stock) and went back the the cleanrom (closer to stock) with a full wipe, and it's back to working as it should. So, maybe just some sort of side effect or bad data somewhere.
Try a really "clean" reset of the OS/environment and see if that helps

Same here. Have to use certain apps to force the orientation to change
Sent from my Nexus 7 using XDA Free mobile app

I've been having this problem on 4.4, 5.0.1, 5.1, stock rom, oakp, pa. And I found the following (in hope it would help fixing it):
1. Rebooting doesn't always fix it. Sometimes I have to clear cache + dalvik.
2. The issue happens less often when not using Nova Launcher and sticking to the Google Launcher.
3. The issue happens less often when switching off the magnetics sensor (that turns off the device when closing a 'smart' lid) using ElementalX kernel.
Could anyone confirm that?

Turn off your tablet. Try to press back cover hardly on N & S at nexus logo for a few second. Then turn on your tablet again. It should work.

I don't know why, but I also had this issue. I flashed stock 5.1.1 and rotation works normally.
If I had to guess, and I do..., I'd say it was an app causing the problem. Don't know what one or how though.

Flashing the stock kernel solved it for me. It's been a week and I have not seen the issue since.

I believe the problem is because the sensor board is either failing or just faulty and works on and off.
I hate the same problem and if you open CPU-Z and go to the sensor section when the screen doesn't rotate you can see most/ all of the sensors are not being picked up/detected
My fix is to shut down the hit my knuckle out of anger on the bottom of the tablet (On the screen and the back) Its as if the board is loose or has something that isn't making contact