Well, this issue bugged me for months now and it looks like there is a workaround.
Problem:
Proximity sensor not functioning during calls - Screen will go black and won't restore until the call ends and with a few power button clicks.
If you tried - Blowing at the sensor, Fixing apps, Opening the device and cleaning the sensor, Creating a bolder separation between the two receptors of the sensor, sending it for repair, Running ADB shell Auto + Manual Calibration - and it all failed, I hope the next workaround solution will help you.
Unless you have a defective hardware/software, doing a manual calibration of the proximity sensor should solve any problem with it. Follow this tutorial - How to Perform Proximity Sensor Calibration on any Samsung Phone .
For me though, it never worked.
When I did the commands:
Code:
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
cat /sys/devices/virtual/sensors/proximity_sensor/state
They both returned a value of '0' (Zero). Which mean I couldn't do any calibration.
I tried so many times but always got '0'.
I saw a few comments from users on threads and tutorials who had this problem and no one seemed to have an answer.
Now, i'm not a debugger savvy but here is what I did which seem to have solved this:
Make sure you run the ADB shell from a pc and not directly on your mobile., You'll want to use copy&paste with your mouse for this.
Run the auto calibration first from the tutorial above.
Now make a call on your phone - this will force the sensor to go into a live mode.
While your phone is calling - run the manual calibration codes.
You should now have different number/s other than 0. Write them down.
You can hang up now
Keep following the tutorial with the number/s you have.
.
I hope this helps. :highfive:
I have a Galaxy S3, i9300 - CM11.
Xolusia said:
Well, this issue bugged me for months now and it looks like there is a workaround.
Problem:
Proximity sensor not functioning during calls - Screen will go black and won't restore until the call ends and with a few power button clicks.
If you tried - Blowing at the sensor, Fixing apps, Opening the device and cleaning the sensor, Creating a bolder separation between the two receptors of the sensor, sending it for repair, Running ADB shell Auto + Manual Calibration - and it all failed, I hope the next workaround solution will help you.
Unless you have a defective hardware/software, doing a manual calibration of the proximity sensor should solve any problem with it. Follow this tutorial - How to Perform Proximity Sensor Calibration on any Samsung Phone .
For me though, it never worked.
When I did the commands:
Code:
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
cat /sys/devices/virtual/sensors/proximity_sensor/state
They both returned a value of '0' (Zero). Which mean I couldn't do any calibration.
I tried so many times but always got '0'.
I saw a few comments from users on threads and tutorials who had this problem and no one seemed to have an answer.
Now, i'm not a debugger savvy but here is what I did which seem to have solved this:
Make sure you run the ADB shell from a pc and not directly on your mobile., You'll want to use copy&paste with your mouse for this.
Run the auto calibration first from the tutorial above.
Now make a call on your phone - this will force the sensor to go into a live mode.
While your phone is calling - run the manual calibration codes.
You should now have different number/s other than 0. Write them down.
You can hang up now
Keep following the tutorial with the number/s you have.
.
I hope this helps. :highfive:
I have a Galaxy S3, i9300 - CM11.
Click to expand...
Click to collapse
Hi, I saw your thread and have similar problem. offset and normal state returns 0. After doing your steps I recieved 0 in offset but 67 in normal state when in call. Followed the tutorial as you describe adding the numbers converting to hex etc but my sensor do still not work.
After calibration according to your guide:
Out of call: It reports 36 in offset and 0 in normal state.
In call: It reports 36 in offset and 31 in normal state
Any ideas ?
Turwaithion said:
Hi, I saw your thread and have similar problem. offset and normal state returns 0. After doing your steps I recieved 0 in offset but 67 in normal state when in call. Followed the tutorial as you describe adding the numbers converting to hex etc but my sensor do still not work.
After calibration according to your guide:
Out of call: It reports 36 in offset and 0 in normal state.
In call: It reports 36 in offset and 31 in normal state
Any ideas ?
Click to expand...
Click to collapse
Have you flashed a stock firmware via odin?.
Beamed in by telepathy.
Related
Over the past week or so I have noticed the backlight on my Atrix acting strange during calls. Sometimes it will not shut off when placed next to my head(I can see the screen out of the corner of my eye) or it will not light up when taken away from my head(to key in a selection on a menu). Sometimes it also shuts the backlight off as soon as the call is placed and I have to press the power button to "wake it up" so that I can make a selection.
The only other thing that I noticed just a little bit ago is - while in a call the LED next to the earpiece appears to be glowing red(dim - like the Terminator's eye right before it got crushed ).
I haven't added any apps in the last two weeks and there haven't been any major updates to speak of.
The phone is basically stock. I did root it so I could use titanium backup and barnacle.
Build: OLYFRU4 1.8.3
Kernel: 2.6.32.9-00007
baseband: n_01.77.15p
android version: 2.2.2
sys ver: 4.1.83.nb860.att.en.us
Has anyone else had a similar problem? More importantly, has anyone else resolved a similar problem?
Thank you in advance for any assistance provided.
Interesting.. I have similar problems, and I've heard this is a known problem with the Gingerbread update (which you haven't done it seems). I've personally noticed that this happens after I use bluetooth and making calls and stuff with BT devices. Do you do anything like that?
I do use a bluetooth headset but haven't noticed any problems when using it.
Shortly after making this thread I checked for any OTA updates and there was the gingerbread update available. I went ahead and performed the update and the problem still exists.
I also believe that my terminology was different and that is why I didn't have success when searching. I have found several threads describing the problem as dealing with the proximity sensor instead of the light sensor. I have not found a definite solution though yet - I'm contemplating a factory reset.
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
71chevellejohn said:
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
Click to expand...
Click to collapse
Unfortunately, it sounds like your proximity sensor (or logic board in general) may be going haywire - meaning a hardware problem not a software problem (I'm guessing that since, as you said, it's happening both ways)...
In my sig there is a app called Build.prop editor. You can use this to change the proximity timing and distance. the little red light you see is the infrared sensor that tells the screen to shut off.
In the build.prop edit mot.proximity.delay=200
and edit mot.proximity.distance=30
should fix screen not turning off issue.
Once again link in my sig for build.prop app( must be rooted)
You can try other values that fit you, doesnt have to be 200 and 30
Anyone else have issues with their accelerometer being off. I was trying to play temple run and noticed I had to hold it at an angle for the player to stay in the middle of the screen. Then I loaded up bubble level and it shows it being 5 degrees off. I tried to calibrate it from the screen menu and a factory reset neither of which helped. Should I send to Samsung for repairs?
Hmm, no clue. Have you tried Googling "how to calibrate android accelerometer" or similar?
Sent using Tapatalk
Me too
Man, that's so weird. I had almost the same problem on the same day. Suddenly, my player's accelerometer freaked out. The x axis keeps showing -9 at horizontal position. I have tried calibrating it many times and also tried lots of wipes and even 2 flashes using odin and nothing seems to solve the problem.
My player was bought 2 months ago in Brazil and I have never let it fall or suffer any kind of physical shock. Now I don't know even how to send for repair cause I only have rooted roms to flash on it and support may discover custom roms through CWM recovery on boot.
I'm still pretty sure it's not hardware malfunction. Something has happened and I can't find out how to reset sensors the hard way.
Strange that happened to us on the same day (at least, with me was on 21st).
I'll keep searching for a solution. It's horrible to use the player with this issue. (Not to say, almost impossible.)
Best regards.
I have found this and it seems to work for many ppl. I'll try it later, when I get back home (I'm at work).
First, navigate to /data/system folder and then rename or delete ms3c_yamaha.cfg
Later (you need to have your phone rooted), try this at the terminal:
adb shell
su
/system/bin/sensorcalibutil_yamaha
then place your phone horizontally and still and press enter.
Finally, run the Horizontal Calibration from the Display settings and then reboot.
Really hope it helps and work.
I tried everything I could
So, I got back home and started trying many things I saw on the web.
I reflashed again, using odin, different roms (now I'm keeping Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) with rotation off).
I also tried what I have posted before and it didn't work, actually I found 2 files similar to the ones posted before: One is caled sensorlib_yamaha_test.so and the other is sensorlibconfig.so (not pretty sure about the name of the second file).
What happened during my attempts was that: before, the X sensor had the problem (value -9 with the cellphone laid on a desk, at horizontal position) and now, surprisingly, the X sensor is OK and now the Y sensor has the failure.
Using the HORIZONTAL CALIBRATION in SAMSUNG 2.3.6 (or 2.3.5, whatever), the ball only stays in the middle of the screen if I keep my phone in vertical position - upside (cause of the Y axis). Even if I rotate the tab in every direction possible, the ball never goes UP, so it only keeps with negative values and never positive ones.
BUT If I shake the phone, not so hard and not so soft, I see the ball of the calibration software moving on all directions. But when I manage to do it softly (as we do with normal use), the ball never goes up.
I have downloaded many sensor programs to test the calibration and after trying about 20 programs, ONLY ONE have showed the exact values as if the accelerometer was normal, but the calibration of the program did not affect the accelerometer on the system and other programs.
So, this is it, of course I won´t give up and try as many things as I can. Here in Brazil we have a saying that is: I'm Brazilian and I never give up.
P.S. I hope someone reads this and give me ideas. hehe
Thanks in advance.
Have a nice day u all.
Great news - a solution
GREAT NEWS - I HAVE SOLVED IT
Ok, after lots of attempts here is what I did.
I have downloaded android Froyo firmware from a Korean website (its on a thread of android development from galaxy player). Then I flashed it with ODIN and when it turned on, at first it was discalibrated the same way (Y axis only showing from 0 to -9).
I turned the player OFF and then turned it ON holding vol + button to enter in stock recovery mode. In recovery mode I wiped cache and data. Then I tried to calibrate again, with my device upside down and then voila.
Of course it was sort of a luck, but I had to try everything my mind could guess.
After all, I think that maybe It wasn't necessary to flash other roms (but it would be impossible to solve it using ICS due to a lack of calibrator - without having to use terminal / for curious noobies like me).
Then, I always tried to calibrate my tab laying it in horizontal position and that is the why I never got any satisfactory results. When I tried the calibration with the tab in 'incorrect' positions, the problem was solved. I guess, the calibration program tried to compensate the wrong results cause of the vertical position and then it calibrated itself.
Hope this helps someone someday. (But I really hope you won't have this kind of problem. It's frustrating.
Any device you have, if you have accelerometer problems, you should try this idea: wipe data and cache, and the first calibration you do, do it with your device turned to the side that has the wrong value or to the oposite side. This worked for me.
Best Regards,
Very happy Zilian28.
go to settings>display>horizontal calibration lay it on a flat surface and calibrate it
Sent from my GT-I9000 using XDA
Hello Everybody!
I've been using my Lumia 920 for a month now, and few days ago, I picked my phone and touchscreen was not responding.
I used device very carefully - so there was nothing like drops or something.
I tried Soft Reset, Hard Reset nothing helped.
I connected device to Nokia Care Suite, and runned the Self Test.
All tests were OK, but these two Failed
ST_TOUCH_TEST and ST_TOUCH_IF_TEST
What does this mean? Should I replace touchscreen digitizer or it's something else?
ST_TOUCH_IF_TEST Details:
Code:
Test name:
Touch interface self test
Test description:
The test verifies data and control lines between MCM and touch controller.
Result:
MINOR
Result (detailed view):
Failed loading the driver
Data description:
Detailed result contains HwFails bitmask. Zero means all was ok, and fail codes are:
- SELF_TEST_HW_FAIL_CONTROL 0x0001 (No communication with a device at all)
- SELF_TEST_HW_FAIL_BIST 0x0004 (Component internal self test)
- SELF_TEST_HW_FAIL_INTERRUPT 0x0010 (Interrupt line fails)
Method description:
Touch driver identifies controller by reading of the test register via control interface. Interrupt is generated for INT line verification by setting the threshold low enough.
ST_TOUCH_TEST Details:
Code:
Test name:
Touch internal self test
Test description:
The test verifies internal functionality of touch module.
Result:
MINOR
Result (detailed view):
Failed loading the driver
Data description:
Detailed result contains HwFails bitmask. Zero means all was ok, and fail codes are:
- SELF_TEST_HW_FAIL_CONTROL 0x0001 (no communication with a device at all)
- SELF_TEST_HW_FAIL_INTERRUPT 0x0010.
Method description:
Build-in selftest for touch sensor network verification is run where RAW values of the sensor network are read and they are verified to be within the specified limits. The touch screen should not be pressed during the selftest.
Was that with or without a screen protector? Sometimes a screen protector can get dirty or get dirt around or under the edge and trigger false touches which will make it appear to be locked or not function.
If it was just the straight touchscreen then sounds like it needs service.
Solarenemy68 said:
Was that with or without a screen protector? Sometimes a screen protector can get dirty or get dirt around or under the edge and trigger false touches which will make it appear to be locked or not function.
If it was just the straight touchscreen then sounds like it needs service.
Click to expand...
Click to collapse
I used device without screen protector.
I can't take it to Care Center, because I bought device from USA, and I guess warranty isn't valid here.
I called them, and they said that they probably should replace screen assembly, which will cost me almost the same price I paid for phone.
Meanwhile, I can buy screen assembly(or just digitizer) online and replace myself, but I need to be sure it'll solve problem.
I bought my S3 just three weeks back and everything up-till yesterday was fine. Suddenly starting from yesterday the motion sensors and evrything related to it stopped working e.g auto rotation, motion related games, motion detection etc...When I tried calibrating my gyro it gives the following error "Offset file missing. Try Gain". That error dnt seem to exist on Google when i tried looking it up.
Before you ask..I verified and took the following steps:
- Screen auto rotation is turned on
- Motion is turned on
- I performed a factory reset
- I tried using the command *#0*#
- turned off developer settings entirely fearing it might be messing things up.
- rebooted several times including taking out sim and battery.
- performed hard reset.
im really desperate ...any help would be greatly appreatiated...
Sounds like a hardware failure if you are on unrooted stock. Warranty repair required.
As no firmware details posted suggest factory reset then service centre is all you can do .
Its not a problem that's been posted before .
jje
I have a rooted/unlocked Photon Q with a partially functional display. The initial warning "Your phone has been unlocked" comes up fine. When I put it in bootloader mode, the fast boot messages appear fine. On regular boot the screen is either black or on one occasion showed some randomly scattered pixels. Booting into recovery (TWRP) results in a black screen. In all cases adb/fastboot are able to properly communicate with the phone. I was able to test if the screen was on or off using adb commands, as well as turn it on/off. The commands did register and showed the screen correctly or or off though this was not reflected in the visual screen output. When toggling on/off state I saw some activity - it almost looked like the brightness was set to 0, but I verified that with adb as well and even set it to 100 to be sure with no change in the display behavior.
So my suspect is the graphics card, but it must be just some video modes given that fastboot diagnostic and initial warning can be displayed. I am about to replace the motherboard, but I am just curious about what exactly is wrong (and if by chance it can be fixed without replacing the motherboard). I also looked around for documentation on the video modes of the Photon Q graphics adapter, but could not find anything relevant - if somebody could point me to the right source this would be appreciated.
I would not mind writing some C code to poke around on the low level, but it would be nice to start from some sample code rather than from scratch.