Hi all,
I apoligise in advance if this has been posted before but it's 4:30am and I don't have anymore time to search for this problem.
I've noticed ever since I've updated my phone to Darky's ROM (starting in dec 2010 with v8) my proximity sensor hasn't been turning my screen off during calls. I'm not sure if this is rom related or not but I ran some tests tonight (using SGS tools and sensor test/z-devicetest) and in all those apps my sensor doesn't seem to respond.
Does this mean it's broken?? Or am i missing some drivers or something??
I'm currently running DarkyROM v10.1.
TIA
Edit: found out that it is indeed working, however only when a bright light shines onto the sensors. Is this normal??
I just fixed the magnetometer on my Vibrant, using advice found on another site. It took me a long time to find it, so I thought I should post it here to help other Vibrant users find it more easily. There is similar advice in forums for other Galaxy S variants, but nothing here.
About a week ago, I noticed that my phone was no longer sensing its position. The screen would not rotate, and the compass was not working. I ran the sensor test using the *#0*# code, and both the accelerometer and magnetic sensor were stuck on one reading regardless of phone position. Rebooting had no effect.
I found the following procedure on a different site. I would post the link to give proper credit, but I don't have sufficient forum privileges because this is my first post. It was on the dp.nonoo.hu blog.
Your Samsung Galaxy S phone’s compass is not working? Auto rotation is faulty? Check your hardware by dialing *#0*# – this is a factory test app for the phone.
If the compass is broken there too, here’s how you can fix it: delete /data/system/ms3c_yamaha.cfg, and if there’s a backup file, delete it too, then reboot.
If it won’t help, make sure the files are deleted and then run /system/bin/sensorcalibutil_yamaha from a root shell, follow the instructions and then reboot your phone.
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.
Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.
Cheers Blue,
This fixed it for me.
I cannot find neither the .cfg fila and or the configuration app.
+1
These files do not exist in ICS AOKP on my Vibrant and my magnetometer still points in the wrong direction lol.
Trying everything I can find on the Internet.
Edit: Removing the battery does not work even after 15 minutes. However, flipping the phone end over end worked immediately. Seems strange that this is not mentioned by any of the Compass apps yet they tell you to draw figure 8's in the air which does nothing on my Vibrant. lol
Thanks to the individual who shared that tip.
same here, a few vertical and horizontal flips did the trick for me. (on ics passion)
Didn't find the "/data/system/ms3c_yamaha.cfg" on my GalaxyS running Slim ICS 3.2. Seems like ICS doesn't have this file. And some vertical/horizontal flips almost did the trick. Now the compass is moving, before it wasn't moving at all. It not showing very good direction like it used to when I first purchased the device almost 15 months ago.
And one more question, does anyone know, what is the testing code for ICS? Because *#0*# isn't working on ICS. I used this code while on gingerbread and it worked before. I thought this code is universal, but now it seems like, its not.
blueguitarbob said:
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.
Click to expand...
Click to collapse
1. Doest it still work when the phone is:
- touched with a little magnet like in a standard vertical flip-case (with little magnet) or
- travelling by car/bus/train or
- plugged in headphones
In the one I had (I don't have it any more) while plugging in headphones, or travelling by car/bus/train, or putting it in an flip-case with a little magnet the arrow In Google Maps pointing the direction which a device is currently facing simply freezes. Compass app also freezes at the same time. The app called Android Sensor Box in the scale for magnetometer reaches its maximum level. While moving the little magnet, from mentioned before filp-case, around a phone the arrow travels with it. Move it away and it freezes. It simply won't move. While sticking S4 to the metal part of laptop table the arrow immediately points opposite direction. Only making 8s in the air helps but only for a bit. Neither S3 9305 nor S5 have this problem. Even when stuck with a magnet their arrows in GM works just fine.
2. Does deleting the file fixes the GM's arrow issue also?
Danstek said:
Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.
Click to expand...
Click to collapse
**** this worked
Hi guys, so I'm one of lucky guys who's HD2 sensors don't work (black screen after calls)
Is there any way to disable light/proximity sensors on phone (android builds ofc)
I'm also having this problem with my Samsung Captivate/Fascinate(Telus). Its really annoying. I tried everything from http://forum.xda-developers.com/showthread.php?t=764368&page=2 but nothing worked.
Anything new? Its quite an old thread.
EDIT:
found this and it works! Covering it actually helps!
http://forum.xda-developers.com/showpost.php?p=16477794&postcount=15
Hi all,
I've recently installed the ICS ColdFusionX ROM tillals 15/05 build, on my Orange Sanfrancisco (ZTE Blade) (gen1 - TPT'd to gen2).
After some initial problems I now only have one problem blocking me from using this ROM as my daily...
When I go to make a call (and possibly also when someone calls me) the call is established but the phones screen goes black. The UI and buttons then effectively become disabled meaning I can't hangup the call, or exit without removing the battery :-(
This is a real shame as it otherwise seems to be an excellent ROM... I really can't believe how fast and smooth it is!
I've looked around, and can't see anyone else mention this issue (when establishing calls from the device itself). The few posts I've seen suggest recalibrating the proximity sensor and rebooting, but I've tried that and no luck :-( any ideas???
Thanks greatly.
Update
After re-installing and experiencing the same problem, I managed to resolve it simply by recalibrating the proximity sensor (and not reseting/rebooting).
this problem has been fixed try fixed try flashing the rom again
Hi guys!
I'm having problems with the proximity sensor of my Nexus 4, exactly is not switching off the screen during a call.
I got it recently and quickly flash all kind of kernels, apps, etc... but at this moment it's stock + Franco Kernel. Other apps which I'm using and I guess can cause: LightFlow, Greenify.
Some checks I have done...
- No screen protector is used (I saw can cause this problem...).
- Checking with a 3rd party app like AndroSensor, CPU-Z, ... which can provide sensor values, looks that h/w is working. Actually I can see the values are changing when I put my finger on the sensor (0-2, 0-5cm depending of the app).
My guessing is that maybe those 3rd party apps are taking the raw sensor values (thus working) and maybe android itself is using some kind of calibration which maybe is messed.
What do you think? Anybody with the same problem? Any solution?
Thanks,
Antonio
Am having the same problem. Am running cm 10.2. Anyone know whats causing this?
Yes it surely the rough app.. Try uninstalling the newly/latest installed app.. Or try wakelclock detector to see which app is cuasing the wakeup and try uninstalling it. Hope this might help..