Proximity sensor calibration or fix? - AT&T Samsung Galaxy Note II

OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.

absinthesummer said:
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.
Click to expand...
Click to collapse
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy

absinthesummer said:
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy
Click to expand...
Click to collapse
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure about changing the range, I'll look into that but yeah depending on the screen protector it could interfere with the sensor, especially if it's particularly thick or dirty. I don't use screen protectors anymore for that very reason. They can muck up the sensor and make the front camera take fuzzy pics.

Related

[Q] Proximity sensor

So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
My understanding is that proximity sensor in note 2 is set for 8 cm and values are either 0 or 1 above or below 8cm
Sent from my SGH-T889 using xda app-developers app
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I have this exact problem here was my thread a few months ago:
http://forum.xda-developers.com/showthread.php?t=2099898
and the only response was to factory reset (which I haven't done yet and from what you're saying that won't fix the problem either...)
Quick question, I only see 1 light coming out of the two holes at the top of the phone, are there supposed to be 2 lights? (you can check using another camera since it uses infrared)
-- edit --
just found this thread on sprint forums:
http://community.sprint.com/baw/message/544084
apparently the person had a tech open it up and air out the sensor
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
same issue
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I had the exact same problem with the proximity sensor and other weird sensor issues. I had never rooted or anything. T-mobile exchanged my phone for a new one.
vaghotstuff said:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
Click to expand...
Click to collapse
This fixed for me too. But the sensors start acting up like every couple weeks and I'd have to blow air into the ear piece.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
TRY THIS
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
Thanks for advise! I'll try it and revert!
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
It didn't help! After the fix is installed the sensor works at the same manner... Is it possible to try something else?

Disable proximity sensor

Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can disabled it in TouchWiz. I'm not sure you can in an AOSP rom, which your 4.4 rom is.
It could also just be a ROM bug that hasn't been worked out yet. I'd check the development thread for this rom and see if it's a known issue.
If it is, help the developers by posting a logcat of the problem in the develoment threads. (Because odds are no one else has)
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You didn't get a response in a development thread because development threads are not for tech support. They are for discussing development. Tech support questions (which this is) do not belong in development threads.
The rest of XDA isn't even for tech support. We are just happy to try and assist if you get stumped. And don't get me wrong, we are legitimately happy to try and assist you. But complaining that it's "usual that no one responds to you" is pretty rude. No one promised you tech support here. If you get help, it's because someone was trying to be nice, not because you are owed an answer.
If you are using an alpha release ROM it's YOU who should be providing tech support to the developers by giving them logcats of your error so they can review them and find out what is causing the conflict. That's how you can help add to XDA and assist the developers who are building cutting edge software for you and giving it away free as a gift.
If you aren't willing to put up with the proximity sensor errors, or to help the developers fix it by providing them with the logs of the error, then your best bet is to move back to a stable build of a 4.3 or 4.2 ROM for another month or two until the major issues with 4.4 are hammered out.
As for asking for help here, what else have you tried? Have you verified that the bug doesn't exist if you revert to a different ROM?
Have you done a full wipe and clean install of the 4.4 rom and tested for the bug immediately, before installing any other apps or user data? Since you are the only one having the issue this could easily be a conflict with some other app that you have installed. The full wipe and test is the best way to confirm that or rule it out.
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same scrap happening with me. The problem is the proximity sensor is always detecting something is in its proximity (most likely dust that got in through the ear piece grill). As a result, the screen turns off immediately when a call is answered, and in Android 4.4 the power or home button can not override this. Interestingly, in 4.3 the power or home button does in fact override the proximity sensor. Why the difference between 4.4 and 4.3 I'm not sure. As Skip Jack alluded to, in Touchwiz roms under settings>my device>call> "turn off screen during calls" can be toggled off to shut down the proximity sensor. If I could find a setting like this in stock 4.4, that would solve this issue.
I need to reflash a 4.4 rom and look for this setting, although I do not think it exists.
I've tried the "pressurized air into the ear piece grill" fix, but it didn't work for me.
Any other suggestions?
https://www.youtube.com/watch?v=zm4f2XjQLAM&feature=youtube_gdata_player
QUOTE=fateownzyou3;47870242]Well iv went thru the threads of the developme, section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent I rom my SGH-M919 using xda app-developers app[/QUOTE]
Canned air didn't work. So I took my phone apart as demonstrated on YouTube , and when I peeled back the proximity sensor and gesture sensor assembly (they're one piece, attached to the earpiece) i found little bits of sand and dust. A lot. I enjoy the beach in the summer. I cleaned the sensors and the screen area that they are housed in (the part of the screen they "look" out of) with a dry q tip. after putting it all back together its as good as new. *#0*# confirms all sensors now working. The vid above is what I used. You only have to remove sim, sd card, little screws, back speaker, side housing, and a small bracket (in that order) before disconnecting and peeling back the proximity/gesture sensors in order to clean.
You don't have to remove all that other stuff.
I am having the same issue since puttin on CM 11. In 4.1 there was a setting to turn the proximity sensor off but in 4.4 there isn't. I keep looking for an app or something else to trigger it but it is also driving me crazy.
It only happens when my protective case is on my phone, but I am the type of person that NEEDs a case on their phone otherwise itll crack or drown within a couple of days. Any help would be appreciative.
I am having the same issue. Just installed CM 10.2.0-jfltetmo
How do I get a logcat to post? Also, what other information would be helpful for development?
I don't think my issue is sand in the sensor... but I will post back after I open it up and check it out.
If anyone knows of a fix or way to access settings for the proxy sensor, that would be awesome! Also, isn't there a way to use the terminal session to read data from the sensor?
Thanks for any help provided!
Another idea for those who are stuck. I didn't find a way to disable the proximity sensor, but there is another way to hang up a call. If you go into Accessibility options, there is an option to hang up call with Power button. This way you at least have a way to hang up the phone call without having to pull the battery, etc. But it doesn't help if you need to enter additional numbers on the keypad unfortunately. But at least we can hang up now!
I've been having this issue as well which seems to be an aosp bug, but for the mean time, has anyone come up with a solution? Ive tried tasker actions to turn screen on during calls but it seems to be blocked due to the proximity sensor. I know that downgrading to 4.3 is an option but a workaround must be possible. If you find it, Post it.:good:
Edit: Came across this post. Haven't tested yet but it seems promising
Edit2: Wasnt able to get the app to solve the issue as others stated
Hardware fix for proximity sensor
The apps mentioned in this forum and others did not worked for me. My phone is not rooted; perhaps this is required. Apps that I tried are:
Proximity Screen Off Lite
Caffene
I did find the Phone Tester app very useful during the surgery.
I was able to desensitize the proximity sensor as follows. The sensor is made of an IR emitter and an IR detector. It is very sensitive. Small reflections from one side to the other will cause the sensors to show "near" instead of "far."
0. When you look at the Nexus 4 straight on (front camera on top right), of the two elements on the top left, the one more to the right is the IR emitter.
1. Open the phone and gently peel back the proximity sensor/headphone jack (2 + 9 screws; pry plastic and one flex).
2. On the hole corresponding to the IR emitter, apply two small squares of masking tape cut to 1.5 mm x 1.5 mm. Only cover that hole; you do not want to cover the ambient light sensor. The masking tape blocks enough IR to desensitize the system, but won't deactivate it.
3. Gently pry up the digitizer from the phone near the corner when the sensor is. Using a toothpick, apply a drop of superglue just inside the top left corner. Apply pressure and ensure that the digitizer sits firmly on the frame. This is necessary because a slightly separated digitizer will reflect the output of the IR emitter back to the sensor (think about standing behind a window about a foot versus having your nose up to it; you don't see your reflection when you are close).
All this assumes that you know your way around opening the phone and have the correct tools. Sharp objects, execessive force along any step can break your screen or the phone in a split second. If you are not comfortable with it, don't do this.
-PD
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
You only need to post your question once. You have it in a more appropriate thread already. Please don't dig up 5 month old threads to multi post your questions.

Proximity sensor

Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
mrgwap said:
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Same Issue, would love some tips.
bobolinko said:
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Click to expand...
Click to collapse
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Martsmac said:
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Click to expand...
Click to collapse
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
thanks
I appreciate the response , however I'm sure its not dirt on the sensor and that its actually an issue with the software (in this case Cyanogenmod 11 nightly build) not detecting it/initializing it correctly. My reasoning for this is that as soon as I revert back to the stock ROM my issue is gone.
Really hope someone figures this out but for the time being I'm going to have to use a different ROM/stock. Love CyanogenMod though so hopefully it can be resolved soon.
Skipjacks said:
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
Click to expand...
Click to collapse

[Q] Accelerometer Calibration?

So it seems the y axis is off a few degrees. Which is noticeable when play games like Bike Race where you tilt the bike. While holding in landscape the phone shows level if you tilt to the right a tad. Anyway, is there a way i can calibrate the accelerometer. I see some apps that have calibration tools but that only fixes it within that app. I just got the phone and i am within my 14 days to return, if returning would be a simpler option.
Try *#0*# in dialer and hit sensor hub test that and sensor, sensor lists everything individually
Ok that's what I did to find the issue. I think you hit sensor button. Sensor hub test just runs some test and comes back with passed, but no options. Under sensor you can see the accelerometer data and that it's off but no way to calibrate.
So I took my phone back to at&t to get an exchange because of the accelerometer. While waiting i tested the display model and guess what. Same issue. So I asked if i could get a replacement he said yes. When i explained the problem he said he hasnt heard of that before. Then tried the same thing i did with the display model. So if anyone would perform this test on theirs for me i would be appreciative. Just go to Test menu (*#0*# in dialer) and hit sensor and see if your Y axis is correct. Mine shows -3 when on the level surface.
X=0,y=0, 90 degree angel, with and without case on
Didn't there used to be a calibration setting in device settings to get the accelerometer back on its appropriate axis?
arjun90 said:
Didn't there used to be a calibration setting in device settings to get the accelerometer back on its appropriate axis?
Click to expand...
Click to collapse
Way back on the note 2
Yep I wonder why they removed such a basic function. Anyone else with their stats before I exchange tomorrow? It's the 14th day.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
thejanitor86 said:
Yep I wonder why they removed such a basic function. Anyone else with their stats before I exchange tomorrow? It's the 14th day.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
X=0, Y=0, 90 angle laying on the table
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
So I had it swapped out today. Same results. So the only thing i can think off is its something wrong with the batch there. So i will have to see if i can get a different one from somewhere else. I will call At&t Monday. Hopefully they wont be too difficult to deal with on this issue. On the plus side the new one isnt quite as off.
Mine

Rotation

Hi. Im currently running the diamond rom 8.0 and have been for quite some time. Havent had any issues but out of the blue today my phone has decided not to rotate. Compass doesnt work and I have cpu-z installed and it doesnt show anything on the gyroscope part under sensor tab. Can someone please help me. Diamond rom 8.0 android 4.4.2
try to restart phone or flash different rom, then you will know what is going on
Ive done that...restarted many times sometimes it aorks and then it goes...ive installed another rom fresh and still same issue
MishXT said:
Ive done that...restarted many times sometimes it aorks and then it goes...ive installed another rom fresh and still same issue
Click to expand...
Click to collapse
try to call *#0*# there you'll have possibility to test all your hardware - sensors, gyroscope.
Do you use screen protection i.e. foil?
You can recalibrate gyroscope.
yaro666 said:
try to call *#0*# there you'll have possibility to test all your hardware - sensors, gyroscope.
Do you use screen protection i.e. foil?
You can recalibrate gyroscope.
Click to expand...
Click to collapse
I don't use any screen protection, I have done the *#0*# and tested all the components on there, the accelerometer sensor shows static numbers rather than numbers moving about. The Gyroscope Sensor doesn't show anything. I have tried with CPU-Z on my phone, the only thing that shows is the Light sensor and Barometer Sensor, the rest of the other fields are blank. This doesn't always happen but it happens enough to really get on my nerves when trying to use my phone the way I want to.
I am not able to recalibrate the gyroscope from settings as stock firmware and custom roms from 4.3x and upwards, it has been removed
MishXT said:
I don't use any screen protection, I have done the *#0*# and tested all the components on there, the accelerometer sensor shows static numbers rather than numbers moving about. The Gyroscope Sensor doesn't show anything. I have tried with CPU-Z on my phone, the only thing that shows is the Light sensor and Barometer Sensor, the rest of the other fields are blank. This doesn't always happen but it happens enough to really get on my nerves when trying to use my phone the way I want to.
I am not able to recalibrate the gyroscope from settings as stock firmware and custom roms from 4.3x and upwards, it has been removed
Click to expand...
Click to collapse
you can try to rotate phone while you put a little force to the back. If your hardware is faulty there is a chance that some connection is damaged or loosen
for me gyroscope is moving in every axis, image test is rotating, graph test draw 3 colored plots.
magnetic sensor also moving and selftest shows PASS.
Gyroscope also moving, graph generate 3 plots and selftest shows PASS. Here you can find auto calibration function.
yaro666 said:
for me gyroscope is moving in every axis, image test is rotating, graph test draw 3 colored plots.
magnetic sensor also moving and selftest shows PASS.
Gyroscope also moving, graph generate 3 plots and selftest shows PASS. Here you can find auto calibration function.
Click to expand...
Click to collapse
I can't seem to find auto calibration function there
You can see here what I mean,
I am continuously moving my device around and I don't get anything
MishXT said:
You can see here what I mean,
I am continuously moving my device around and I don't get anything
Click to expand...
Click to collapse
do a gyro selftest. When it's finished you'll have info about calibration
another solution:
You need to be rooted. Install root explorer
1. Install any Terminal Emulator.
2. Run this :
su
cd sys/devices/virtual/sensors/accelerometer_sensor/
echo 0 > calibration (this will reset your sensor )
echo 1 > calibration (this will calibrate your sensor )
Hit "Enter" after each command line.
(!!!!! before runing the last command, tablet must be with face up, on a leveled surface )
Now reboot. You have succesfully calibrated your accelerometer sensor. Calibration will survive even when install another room (tested).
yaro666 said:
do a gyro selftest. When it's finished you'll have info about calibration
Click to expand...
Click to collapse
this is what I get
MishXT said:
this is what I get
Click to expand...
Click to collapse
you have to keep phone still.
another solution:
You need to be rooted. Install root explorer
1. Install any Terminal Emulator.
2. Run this :
su
cd sys/devices/virtual/sensors/accelerometer_sensor/
echo 0 > calibration (this will reset your sensor )
echo 1 > calibration (this will calibrate your sensor )
Hit "Enter" after each command line.
(!!!!! before runing the last command, tablet must be with face up, on a leveled surface )
Now reboot. You have succesfully calibrated your accelerometer sensor. Calibration will survive even when install another room (tested).
yaro666 said:
you have to keep phone still.
another solution:
You need to be rooted. Install root explorer
1. Install any Terminal Emulator.
2. Run this :
su
cd sys/devices/virtual/sensors/accelerometer_sensor/
echo 0 > calibration (this will reset your sensor )
echo 1 > calibration (this will calibrate your sensor )
Hit "Enter" after each command line.
(!!!!! before runing the last command, tablet must be with face up, on a leveled surface )
Now reboot. You have succesfully calibrated your accelerometer sensor. Calibration will survive even when install another room (tested).
Click to expand...
Click to collapse
Thank you for that, I have tried it and rebooted, so far it seems to have worked, I will give it some time to see if it sticks
Thank you
MishXT said:
Thank you for that, I have tried it and rebooted, so far it seems to have worked, I will give it some time to see if it sticks
Thank you
Click to expand...
Click to collapse
I'm glad that it changed for better
Not working again. I took it to my closest samsung store and they said they would need to replace the motherboard. Its better to get a new phone...I shall wait for the Note 5

Categories

Resources