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.
Related
Hi all,
I recently received a replacement Desire for my 'faulty' one. I tested all basic functions before walking away and everything checked out.
After I rooted it and installed Modaco r17 ROM, My proximity sensor sensitivity dropped dramatically. When I make or receive a call, the screen blanks as it should, but when I move the phone away from my face, it stays blank. I can't end the call or use speakerphone or keypad. The only way to bring the screen back is to hold it under a very bright indoor light, or direct sunlight...or pull the battery, of course.
I loaded a sensor test tool (SensorList) and it confirms that the sensor is reacting only to very bright light. I've checked that my cover doesn't obscure the sensor and tested that the behavior is the same with or without the screen protector.
I tried a couple of other ROMs, Modaco r19 and Shadowfrost v13. I un-rooted my phone and dropped a stock HTC ROM back onto it...and the problem is still there!
I'm waiting on a reply from HTC service about it...but in the meantime...any advice? I've seen a few posts around the web with this problem, but no definitive solutions or answers.
Question Added to Developers
I've noticed a smattering of people in various forums, with various of the newer android phones having proximity sensor problems. Perhaps these are not quite as finely calibrated as the other sensors, or not as reliable. Have any of you developers seen a way calibrating or adjusting the sensitivity? Perhaps a value in a system file we can change?
Thanks in advance.
Added question and bumped
Apols if this is pushy. I added a question to you developers, so giving this a bump.
phantomfisho said:
Apols if this is pushy. I added a question to you developers, so giving this a bump.
Click to expand...
Click to collapse
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Daelyn said:
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Click to expand...
Click to collapse
Images:
1. Holding hand over phone screen
2. Clear view of the screen in dimly lit room (it's quite cloudy )
3. While running FroYo
This does seem like Sensor List correctly detects and measures the proximity/light sensors in FroYo on an HTC Desire, or am I mistaken?
Ditto Issue
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
nayajoeun said:
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
Click to expand...
Click to collapse
Thanks John. I tried the same thing with the same result.
I ended up taking it in to HTC. Luckily I came across a good service rep. He said they'd seen some quality problems with the first batches of Desires and mine was not the first faulty proximity sensor they'd seen. My guess is the timing with the rooting was coincidental.
They would have replaced it, but they didn't have any replacement stock at the time...more evidence of early quality issues. They gave me priority and repaired it in 24 hours. It's been running fine under a number of ROMs since.
BTW I had problems de-rooting and reloading the stock ROM. Then I realised I just had to have the original goldcard in the phone and presto! One day I'll learn to RTFM properly.
Cheers mate and good luck with yours.
I have also this problem. When I make a phone call screen goes black immediately and there's nothing you can do. After the call is over I can wake up screen by pressing power button. I'm not sure when it started because there's been so many variables. I even destroyed my invisibleshield thinking it caused the problem.
Sensor list and sensor dump says that max value for proximity sensor is 1. Screenshots above there was at least 9. Also light sensor doesn't work at all.
I tried to unroot and go back stock but the problem still exist.
Have anybody found a way to control these sensors or do I have to send my phone to HTC to get it repaired?
Thanks in advance!
Hi, I have the same problem here with my proximity sensor since I have used a custom ROM (I don't remember wich one because I have tried so many Froyo ROM before the OTA).
I can't send my desire to HTC because my phone is out of waranty since I have installed all these ROMs.
Does anybody's got an idea, some help from devs ?
OK,
Maybe I'have found a solution to the proximity sensor's problem... At least my proximity sensor is working normaly now.
What I have done (you can found all in the xda posts) :
1. Going back to Hboot 0.80 => forum.xda-developers.com/showthread.php?t=741672
2. Rooting the desire and install the new recovery using unrevoked
3. Installing the OTA 2.2 without the Radio 5.09 (not a leedroid or djdroid or any other ROM, just a 2.2 rooted)
4. Configuring my phone
5. Installing the 5.09 Radio
I don't think that I have doing anything else, but now I can call someone even in the dark and my screen doesn't stay blank anymore !
Hope this could help someone.
Hi all! I had my Nexus since New Year and I'm so pleased with it. The last 2 weeks have I just noticed that my compass doesn't work anymore. I have checked several calibration apps but nothing works(twisting it around it's axis etc) . I then tried "advanced tools" application. Here could I see that my phone got zero signals from the compass and the magnetometer! I have switched from stock to m5 just to see if it was software related but the problem is the same. It is like the sensors is out... So my question to you all: Is it any way (through root for example) that I can force reset the sensors or is maybe service next?
Skickat från min Galaxy Nexus via Tapatalk 2
Did you flash any custom ROMs at any point?
I got a fresh Sprint Nexus. Compass worked fine. Flashed some custom ROMs, and compass didn't work with any of them. Next step recommended by CM9 folks is to revert to full stock to see if it works again to troubleshoot, but I won't have time for a while to do this.
As noted elsewhere in other posts, compass just doesn't work. It's not just N/S being reversed, it just goes haywire with any tilting, etc. Calibrating doesn't work from Compass or GPS Status.
That's the thing. I was on stock when I noticed the problem, that was why I switched to M5. But the compass is totally still for me. It doesn't move at all. It's totally non functional..
Skickat från min Galaxy Nexus via Tapatalk 2
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Salem24 said:
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Click to expand...
Click to collapse
Did exactly that with Compass app and GPS Status. Neither works.
Anyone have any progress with fixing this?
This is posted in the Sprint Nexus CM9 thread, might provide some information. Same compass problems happened with other CM9-based ROMs I've tried in the past.
I popped into the [CM9] IRC channel a little while ago and talked about how the compass was broken. It was suggested that I do a complete flash back to stock and report back. Trying to document as best as I can:
1. Complete flash back to stock under "[ACS] Return to stock" thread in this forum, used the first big link for FC12 Stock .tar (md5: 638d9b052b45396be345727ec0eedd64), which curiously is linked to "http://www.shabbypenguin.com/ACS/devices/Samsung/Sprint/GNexus/Stock/FC12/code_i9250xxsph-l700fd01.tar" and not *fd12.tar, like the mirror links to.
2. First reboot, downloaded Catch.com's Compass, compass works.
3. Baseband version lists as L700.05 V.FD01 / L700.FD02. I had previously flashed "toroplus_full_radios-FD02" a while ago.
4. Used Galaxy Nexus ToolKit v6.1, did option 7 for "all in one," though bootloader was already unlocked. Powered off, powered on, compass still works.
5. Copied over backed up zips, etc, flashed "toroplus_full_radios-FD02," rebooted. Compass still works. For kicks, updated to latest Google Maps, and Compass still works, GPS locks, location is correct. Baseband version lists L700.05 V.FD02 / L700.FD02.
6. Wiped system/cache/Dalvik & did factory reset. Flashed latest CM9 nightly (20120509-NIGHTLY-toroplus), GApps (20120429-signed), rebooted. AAAAND compass is broken again, as before.
Hope this gives you guys some information for a fix.
I've noticed on my new S3 that the compass is sometimes off by 90 degrees. Then, if I close the map app and open it later, the compass is accurate.
This this a known issue?
Thanks!
Not sure about this issue but I know there is a way to calibrate the phone somewhere in the settings. Not sure if it will help or is even related but might as well give it a try.
dmobbjr said:
Not sure about this issue but I know there is a way to calibrate the phone somewhere in the settings. Not sure if it will help or is even related but might as well give it a try.
Click to expand...
Click to collapse
I didn't find a compass calibration, although I recall seeing a gyroscope calibration setting hidden somewhere (I'll have to find it again). Would that help at all?
I tried a compass calibration using the GPS Status app, but it didn't seem to help. It's strange. Tried it again on my way into work and it got some of the directions right, but wrong on others. It also seems to improve over time. I almost wondered if it didn't have a magnetic compass and was just using gps signals to guess at your direction. As far as I can tell, there is a real compass in there, although I suppose I can't be sure Samsung is actually using it.
Same problem here...
I'm having the same problem here on all my devices, so i'm thinking it is more likely a bug in android than a hardware issue.
Calibrating the compass with GPS Status (on the play store, can*t post a link yet) helps but never for long... quit google maps or navigation, and on next use I have to calibrate again.
I just verified this one someone else's S5, same there.
Another interesting detail:
I used to have the same issue on my Samsung S3, but with CM on it all is well now... so it really seems to be a software thing.
Sent from my Nexus 10 using XDA Free mobile app
interesting: there's a two year old bug entry about this on google: https://code.google.com/p/android/issues/detail?id=37771
...it has been closed as "obsolete".
nice going there.
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
Since 4.3 ROM I'm having trouble with my ZL accelerometer. It gets crazy sometimes, not responding or doing it wrong, thinking the phone is upside down for example. It's a real pain in the a$$.
To fix it, I had to enter the service menu (*#*#7378423#*#*) and calibrate it. Sometimes even this didn't work, Y axis got stuck, only rebooting made it go right.
The problem persists in KitKat 4.4.2. I don't know if it's a software problem (I didn't do a hard reset or tried reinstalling the ROM yet) or it's a faulty hardware (and the warranty is already expired, damn! ).
The service menu in KitKat is different from Jelly Bean. I can test the accelerometer in the service test menu (that little ball is not behaving well in my ZL), but there's no option to calibrate it.
How do I do that? Is there a way to calibrate the accelerometer in 4.4.2?
You can also suggest something to fix it definitively.
Great question,
I seem to always be pointing in the wrond direction in Maps as well.
I think it could be the same issue.
Anyone else having these issues?
Anyu sugestions.
I am running rooted - Stock 4.4.2
Cheers :highfive:
I Have the same issue with the accelerometer and don't find any solution for this