PROBLEM
After flashing to AOSP 6 I have problems with waking the screen up.
1. After or during the call
2. After longer sleep
It can take up to a minute to wake up. Usualy around 10-20 seconds after multiple presses (single press can sometimes doesn't wake the phone).
NO PROBLEMS WHEN:
1. I manualy sleep the screen, and press power again after a moment - I can bring it to a wake up state without any problems.
2. If the phone is connected through USB - there is also no problem to instantly bring the wakeup screen.
3. There is also no problem to bring the wakeup screen with adb
Code:
adb shell input keyevent 26
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
I've tried this: http://forum.xda-developers.com/opt...mpting-to-fix-broken-sensors-mm-e975-t3297566 without any results. I've also tried restoring factory settings.
Any ideas?
ZPZG said:
PROBLEM
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
Click to expand...
Click to collapse
What does CPU-Z think of your sensor data? it's being represented correctly?
blackbird5308 said:
What does CPU-Z think of your sensor data? it's being represented correctly?
Click to expand...
Click to collapse
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
ZPZG said:
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
Click to expand...
Click to collapse
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
blackbird5308 said:
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
Click to expand...
Click to collapse
Honestly I don't know what is the problem, but in every thread concerning wakup issues and E975 the sensors are blamed. The physical sensor is working properly as I am not having any problems running stock 4.4.2.
Related
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 !
Hello everyone. I've just installed few CM11-based roms (MIUI and AOKP) and noticed a strange thing. When I am just locking my phone and trying to unlock it after a while, screen doen's wake up. It just stays black and there is no reaction for power button. I have to reboot my phone by removing battery so that is really annoying. Stock was working fine, i hadn't notice anything like that. Anyone know the solution?
Mardrom said:
Hello everyone. I've just installed few CM11-based roms (MIUI and AOKP) and noticed a strange thing. When I am just locking my phone and trying to unlock it after a while, screen doen's wake up. It just stays black and there is no reaction for power button. I have to reboot my phone by removing battery so that is really annoying. Stock was working fine, i hadn't notice anything like that. Anyone know the solution?
Click to expand...
Click to collapse
Violently press the button over and over. It worked for me.
Sent from my awfully named device.
RedLedLight said:
Violently press the button over and over. It worked for me.
Sent from my awfully named device.
Click to expand...
Click to collapse
I found another solution i think. I just set up minimal CPU freq. over 400mhz and it's working fine. At least under the charger. You have to press it every single time or once and it's working fine then?
E: Without charger the same issue. Not solved.
I have the same problem and I think it has something to do with the proximity sensor.
Sounds interesting. Why do you think so?
Btw. I don't know why but I am happy that I am not alone with this problem.
Because:
Proximity Wake-Up support – prevent accidental wake-up of device by checking to see if proximity sensor is blocked (eg. Device is in a bag or pocket).
Click to expand...
Click to collapse
I think, here is some XPM bug. Just my thought
lookynator said:
Because:
I think, here is some XPM bug. Just my thought
Click to expand...
Click to collapse
What do you think about checking older version of miui then? I mean v4 or something...
Mardrom said:
What do you think about checking older version of miui then? I mean v4 or something...
Click to expand...
Click to collapse
I've never tried.
lookynator said:
I have the same problem and I think it has something to do with the proximity sensor.
Click to expand...
Click to collapse
Hello, I have the same issue on SGS3 with CM11 M11 (M10 too). Have U found some solution for that ?
Dik
solved
seijidinzuala said:
Hello,
I bought a Redmi 1s online and from the very first day, the proximity sensor doesn't work well, whenever I made a call, after putting the phone near my face, the screen goes dark as normal but it sometimes just won't turn back on. I tried calibrating it through *#*#64663#*#*, I was able to calibrate fine 2 times, but after putting a screen guard on, the sensor became buggy again.
*I've tried flashing different ROM's which doesn't help
*I've removed the screen guard and still buggy
*I cannot calibrate the sensor anymore and just fails
*I've tested the sensor with a 3rd party app from play store and it seems to work fine in that app.
I'm currently out of ideas, can anyone help me?
PS: Sometimes, the screen goes off right after hitting the call button and wont turn back on until the call ends.
Click to expand...
Click to collapse
Yes problem with proximity sensor was their and because it was on base rom so it reflected in other roms too. Currently i am not experiencing it in miui 6. So either try miui v50 (Latest official stable update) or try miui 6.
Again its a software problem and will be solved.
I have updated OxygenOS to 4.0.1 and now I have problem with proximity sensor during call (on 4.0 I haven't noticed that).
Firstly, there was a problem with changing volume during call. There is also problem that screen doesn't turn off when I keep it right next to my face and I'm during call. Also there is a problem that screen turned off while in call and when I took it away from my face, it turned on after few seconds.
Anyone on 4.0.1 having the same problem? I thought OP fixed this problem on that version but I'm having it. Maybe I should do something to fix that (dirty flashed from 4.0, maybe I should clean something or try wiping system and flashing 4.0.1 on top of that?
I'm having the same problem on 3.2.8, and had it ever before. Maybe you just didn't notice it till now?
Proximity sensor is bugged on this thing from MM times. Sometimes it works and other time, it doesn't
abhibnl said:
Proximity sensor is bugged on this thing from MM times. Sometimes it works and other time, it doesn't
Click to expand...
Click to collapse
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Renosh said:
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Click to expand...
Click to collapse
I didn't have that on 3.2.8 also and on 4.0 this also didn't happen but on 4.0.1 I have that problem on every call.
trawel said:
I didn't have that on 3.2.8 also and on 4.0 this also didn't happen but on 4.0.1 I have that problem on every call.
Click to expand...
Click to collapse
I'm on 4.0.1 don't have a single issue so not sure what you want me to tell you. Best solution is backup and reset device
Renosh said:
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Click to expand...
Click to collapse
Like I said mate, sometimes it worked but it never bugged me to the point of frustration so ignored it.
I am facing the proximity sensor issue too. when on call the screen is switched on and many keys are pressed. sometimes by accident even the airplane mode is switched on.
this is constantly a problem with OP3 even in 4.1.3. very poor software support. I think now that are focused only on op5.
No it's not a proximity sensor problem, it's a OnePlus dialer app bug.
There are several bug reports in OnePlus forums about this issue and in one of them they say it will be patched in next version of OOS (I assume stable not tried with new open beta which installs new dialer) so if you don't want to wait, for me the solution that works it's to install Google dialer app from this post https://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-install-google-dialer-phone-t3443006
I recommend to follow all steps in the first post to install it without problems and you won't have this issue anymore.
Hope it helps you.
Un saludo
Has anyone any idea when this will be fixed by oneplus? It is driving me mad, nearly every call gets interrupted by my ear pressing a button turning on the light etc.
I want to keep my phone stock so cannot use the google dialler tip posted above. Thanks
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
jack lamters said:
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
Click to expand...
Click to collapse
by resetting, you mean restarting my device? i tried... but still giving me issue,,,
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
Since you are running a custom ROM, the best person to ask is the creator of that ROM. See if maybe other people running the ROM have the same issue. Since you are not running Stock and haven't even mentioned which ROM you use, it's hard to help you here in any way.
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
I am not running custom rom but that fingerprint reader problem is on mine too and its sporadic. The reader would work fine after a reset/flash, days later it would bug out. I have to tap once or lift the phone to activate the screen for the reader to work. Rebooting the phone a few times would get it to work again but its random.
I've noticed on AOD the fingerprint reader doesn't respond while in a smartlock area and i have to press power to get to lockscreen then fpr works (or it shows me unlocked by smartlock depending if it's been 4 hours) . Can others confirm/rebut that theirs only does this in smartlock zones and not in the wild (or if you bt smartlock whether or not being connected causes this)
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
godlyitem said:
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
Click to expand...
Click to collapse
Yeah, its a crapshoot if it will remain working the next time you restart.