Hi. I'm on a rooted Nexus 5, stock ROM & Kernel, and I'm experiencing two little issues:
1) Proximity sensor problems
When I answer a phone call the screen just doesn't go off. The same if I make a phone call. This is pretty annoying because during phone calls I often touch buttons with my face and I mess up with settings.
2) Notification LED stuck
Sometimes, let's say about once every two weeks, the notification LED keeps flashing even after I wake my phone and read the notification. The only way to reset it is to do a hard reboot.
Do you have these problems too? How could I resolve?
Related
Hi,
I have a problem with proximity sensor.
I looked through many threads here, but they didn't solve it to the end.
Problem:
When I am making/received call, my screen goes blank (near ear or far).
Tried using various apps (ProximityOFF, Sanity, ScreenBl), also tried adding "gsm.proximity.enable=false" to a build.prop file in system, didnt help.
At the moment I am using ScreenBl (it is always on), but it works kinda weird - it helps me keep screen awake during every SECOND call, i.e. call happens - screen off, call happens - screen on, call happens - screen off, call happens - screen on and so on.
Also, during that every second call with screen on, if i press speaker button twice, screen goes off (until call is ended).
So i wanted to ask, maybe someone found a solution of how to PERMANENTLY disable proximity sensor?
Thanks
P.S. I also cant figure out why it happens every SECOND call... maybe if you could help with that, we could find a solution?..
P.P.S. It's a Galaxy S, Darky's ROM, 2.3.3 - worked fine for many months, until couple weeks ago (dont know what changed....)
Edit: Same thing is happening without ScreenBl - still screen is on/off every second call...
hey,
similar issue with my SE xperia x10, the touchscreen broke in that corner where the sensor is so every time i make a call the screen gets locked and i have to remove the battery to end it.
the solution i found was intalling this app: Screen On from the market.
it keeps the screen on when some apps or process are running. i choose "active call".
please excuse my spelling, english is not my native language!
i hope you can solve the issue!!
rgrds,
Manuel
I've a problem with my Note Edge SM-N915S (Exynos device).
/i've never seen this issue before, just first time happened today:
First, I'm running few apps like FB, Messenger, Chrome... and I turn my screen off for taking a little rest before an important call of my boss.
It's about 15 minutes later, I got an incoming call of boss: the phone's ringing loud, but the screen still stays dark except there's an ELECTRIC-HORIZONTAL-LINE ... yeah I mean it's looks like a thin line of the CRT SCREEN OFF ANIMATION - but I'm currently at stock ROM, with no custom screen off effect.
it looks like the picture here (can't post image because of new user restriction please paste this link into your web browser manually to view them and help me )
_http ://i.imgur.com/oSBkc6N.jpg
_http ://i.imgur.com/CgB81W1.png
_http ://i.imgur.com/1fSOPML.jpg
I cannot turn it on with touching on screen or anything except press the Power button twice. Accidental wake up is Off. I've no problem when using this phone before and after this time, phone still work normally... there's no any problem with the screen, the touch, and even the proximity sensor...
But i'm afraid if is there any hardware problem with my phone or my screen which is making phone unusable. Appreciate help, please. Thanks.
Hello!
My oneplus one is having this issue for a while now, When I plug it in and lock the device, there is a 60~70% chance that the display stays on but its just blank, I have to unlock it and lock it again to fix it.
Recently this also started happening when it was not charging and the screen would often stay on causing massive battery drain :/
This happens on every single rom all the way from CM11S up to CM13 and also oxygen os,...
Does anyone know what the problem is?
Thanks,
Noahvt
I have the same problem since I can remember, also looking for an answer.
I have a similar issue. Sometimes the screen stays on, but is dimmed. A simple double press of the power button resolves it (turn on full, turn off screen) but its mildly irritating. I have only noticed it since being on sultanxdas cm12 ROM. I had an issue with a notification LED app not working since a recent ROM update so uninstalled it. Maybe the issue was related to that app as I cant remember the issue occurring since I uninstalled it a few days ago.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...