Develop Bugs

[Q] Gyroscope, Accelerometer & Compass Won't Work

So at some random point my Gyroscope, Accelerometer AND compass all stopped working. I first realized web pages weren't changing orientation so I tried turning Smart Rotation on and off. No luck. Auto rotate is turned on. I also tried recalibrating my Gyroscope in the settings and still no luck. Everything from games to the browser and even apps to show info on all 3 of these things will not work and the compass reads North/NW all the time. I can't find a decent app that just says yes/no the gyroscope/accelerometer are/are not working, but I can flip my phone around and move it fast, etc etc and the readings don't change on the apps I have found. I wouldn't think it's a hardware issue unless all 3 of these are on the same part? I'm no too keen on the hardware end so I'm kind of blind, but I wouldn't be posting for help if I didn't try everything I could think of. Any help or suggestions would be incredible!
Oh, and also good to know: I even tried full wipe and changing to the AT&T CleanROM coming from v6? of the Jedi ROM thinking it could just be some random thing I missed... Although I did use Titanium Backup to restore everything... Anyways, I'll try any and all ideas. Thanks in advance!

Bliznade said:
So at some random point my Gyroscope, Accelerometer AND compass all stopped working. I first realized web pages weren't changing orientation so I tried turning Smart Rotation on and off. No luck. Auto rotate is turned on. I also tried recalibrating my Gyroscope in the settings and still no luck. Everything from games to the browser and even apps to show info on all 3 of these things will not work and the compass reads North/NW all the time. I can't find a decent app that just says yes/no the gyroscope/accelerometer are/are not working, but I can flip my phone around and move it fast, etc etc and the readings don't change on the apps I have found. I wouldn't think it's a hardware issue unless all 3 of these are on the same part? I'm no too keen on the hardware end so I'm kind of blind, but I wouldn't be posting for help if I didn't try everything I could think of. Any help or suggestions would be incredible!
Oh, and also good to know: I even tried full wipe and changing to the AT&T CleanROM coming from v6? of the Jedi ROM thinking it could just be some random thing I missed... Although I did use Titanium Backup to restore everything... Anyways, I'll try any and all ideas. Thanks in advance!
Click to expand...
Click to collapse
Download https://play.google.com/store/apps/details?id=zausan.zdevicetest&hl=en and see what is and isn't working. :good:
hope this helps
Edit: btw if you use APEX Launcher, did you enable "lock desktop" option by any chance? Don't know if that keeps your screen from rotating or anything... just a thought!

*#0*#
Then select Sensor and see if they display readings.
Sent from my GT-N7100 using xda premium

Get into the diagnostic screen by typing *#0*# into the dialer screen and check the sensors if they are gathering the right data.
Sent from the Rabbit Hole

Okay, I did the number thing and a bunch of different things came up...
"UPC-A
EAN-13
EAN-8
Code 39
Code 128
Interleaved 2 of 5
Codabar
GS1 Databar"
Do I need to do something here? Thanks for the responses!
*UPDATE*
So it must be a software thing. I used the app retrorom posted about and it seems like the compass doesn't work. But the accelerometer and gyroscope work on both the green and red axis but the blue seems to stay in position.. Not sure which is which (x/y/z). Still unsure if this is a software or hardware issue... I'm running Nova Launcher, by the way.

Bliznade said:
Okay, I did the number thing and a bunch of different things came up...
"UPC-A
EAN-13
EAN-8
Code 39
Code 128
Interleaved 2 of 5
Codabar
GS1 Databar"
Do I need to do something here? Thanks for the responses!
*UPDATE*
So it must be a software thing. I used the app retrorom posted about and it seems like the compass doesn't work. But the accelerometer and gyroscope work on both the green and red axis but the blue seems to stay in position.. Not sure which is which (x/y/z). Still unsure if this is a software or hardware issue... I'm running Nova Launcher, by the way.
Click to expand...
Click to collapse
Hmm ok. I just tried the compass feature with ZdeviceTest and when I move the NoteII left to right and up and down I can see all three lines moving. So that seems not normal that your "blue line" on the compass feature doesn't move. Maybe it really is a hardware issue then, I hope not...

Proximity sensor seems to not work anymore

I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?

Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.

My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .

I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.

I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.

amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).

iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app

Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !

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.

Disabling Proximity Sensor for cracked screen S4?

I've pulled up several threads on this issue but I dont think many fit my situation.
The proximity sensor is not broken or dirty. I just have a cracked screen interfering with the sensor.
I do not see any options in latest dialer to disable this functionality
The guides I have found to edit the build.prop file have not worked. 'gsm.proximity.enable=false'. Is this device specific? I havent gotten it to work, but it could be user error.
Is there any way to just disable the damn proximity sensor? I cant stand not being able to hang up on calls, especially when the operator on the other end wont hang up or I'm leaving a voicemail. I usually have to yank the battery.
I'm dying for options here and havent pulled up anything.

jaredmac11 said:
I've pulled up several threads on this issue but I dont think many fit my situation.
The proximity sensor is not broken or dirty. I just have a cracked screen interfering with the sensor.
I do not see any options in latest dialer to disable this functionality
The guides I have found to edit the build.prop file have not worked. 'gsm.proximity.enable=false'. Is this device specific? I havent gotten it to work, but it could be user error.
Is there any way to just disable the damn proximity sensor? I cant stand not being able to hang up on calls, especially when the operator on the other end wont hang up or I'm leaving a voicemail. I usually have to yank the battery.
I'm dying for options here and havent pulled up anything.
Click to expand...
Click to collapse
If you are rooted and have xposed installed there are a few xposed modules that have the option for that, I don't recall what they are though sorry
Sent from my SGH-M919 using XDA Free mobile app

How to disable proximity sensor in rooted phone?

So it appears that my proximity sensor is faulty because of which it always thinks there is something close to it. Due to this issue, whenever I make a phone call the screen is always off as the proximity sensor thinks my ear is close to the phone, even when I remove the phone from my face.
This is quite annoying obviously and I was wondering if I can somehow disable the sensor. I rooted the phone with the hope of doing so. I am guessing I can delete/rename an appropriate file in the "sys" folder or add something to the build.prop to disable the proximity sensor. Can someone tell me what needs to be changed?

Use an app for disabling/mocking sensor reading, e.g. this one. I'm using it on Nexus 5, which after some time stops reading data from proximity and light sensors. Unfortunately, for this one you have to install Xposed too.
Maybe somebody will come up with an app, which will work without Xposed.

przemcio510 said:
Use an app for disabling/mocking sensor reading, e.g. this one. I'm using it on Nexus 5, which after some time stops reading data from proximity and light sensors. Unfortunately, for this one you have to install Xposed too.
Maybe somebody will come up with an app, which will work without Xposed.
Click to expand...
Click to collapse
I know I could do it with Xposed but Xposed does not work for Nougat. I need a solution for Android 7.1.1.