I figure I’ll ask because I have always wanted to know, and this is one of the things that keeps me switching back to stock from LOS.
On stock the approach seems much more sensitive and will trigger in instances where the proximity sensor is not even in play.
When on LOS it seems the only trigger is the proximity sensor.
Just wondering.
Related
Hi all,
troubleshooting for a girl with a Bionic; replaced cracked glass/digitizer for her and updated to JB via the OTA update, but her proximity sensor is flaking out.
I've installed a few Prox. Sensor reporting apps to see what values it's putting out: it reads 3cm most of the time, and 100cm when swiping down the notification bar. (100cm is max range, which I assume is a placeholder for a no-report state in the phone, not sure what it has to do with the notification bar.)
Problematic behaviour is that the screen turns off almost instantly after placing a call, and won't come back on except by swiping down (on the blank screen) to pull down the notifications, which temporarily disables the sensor. (it lasts long enough to get ~1 keypress on the keypad, which is *not* a usable workaround even for checking voicemail.)
I'll take the phone apart again and make sure there's nothing in the way of the prox. sensor, as that seems the most likely cause... but any guesses or similar reports from anyone about possible bugs in the firmware update? Any proximity sensor calibration apps for this hardware I'm not seeing in the marketplace, or ROMs that expose that functionality? (I wasn't planning to root the phone, but she won't know the difference if I need to. Was hoping to avoid safestrap to simplify the boot procedure and not interfere with future OTA updates, but warranty is gone already so it's not a big deal if I need to install something new.)
Girlfriend's phone is rooted, but ROM is stock gingerbread. Her proximity sensor has been flaky since she first got the phone, often turning off the screen when the phone is away from her ear, but not always. On forums for other phones I have seen that similar proximity sensor issues were cured when the carrier pushed out a ROM update. So I'm wondering have others had proximity sensor issues with the stock ROM or the jocala rooted stock gingerbread ROM, and if so, were proximity sensor issues cured with flashing a new, custom ROM?
I have never had proximity sensor issues with my phone, when bone stock or when using all the various ROMs I have flashed. I sure am happy with AOIP. I will flash that on her phone if people think that might cure her proximity sensor issue. I just don't like to risk messing with somebody else's phone and potentially bricking it if there is not a pretty good chance of curing a problem by flashing a ROM. Please advise. Thanks, everybody.
proximity sensor fixed with ROM update?
motorapido said:
Girlfriend's phone is rooted, but ROM is stock gingerbread. Her proximity sensor has been flaky since she first got the phone, often turning off the screen when the phone is away from her ear, but not always. On forums for other phones I have seen that similar proximity sensor issues were cured when the carrier pushed out a ROM update. So I'm wondering have others had proximity sensor issues with the stock ROM or the jocala rooted stock gingerbread ROM, and if so, were proximity sensor issues cured with flashing a new, custom ROM?
I have never had proximity sensor issues with my phone, when bone stock or when using all the various ROMs I have flashed. I sure am happy with AOIP. I will flash that on her phone if people think that might cure her proximity sensor issue. I just don't like to risk messing with somebody else's phone and potentially bricking it if there is not a pretty good chance of curing a problem by flashing a ROM. Please advise. Thanks, everybody.
Click to expand...
Click to collapse
WOW. This forum is really slowing down. Everybody must be migrating over to the Nexus 4. Any ideas on the proximity sensor and whether it is buggy because of the gb stock ROM? I guess I'll find out when I flash AOIP.
I have had no problem with the proximity sensor on aoip
If you like my post feel free to hit the thanks button.
This is my first Lollipop device after a long time with Kitkat, so I may be missing something obvious, but I just can't wrap my head around Adaptive Brightness.
So when it's set to on it adjusts the brightness based on the light sensor, but I can also use the slider to tweak it, correct? But then sometimes the slider just stops working, moving it doesn't change the brightness at all. Only way to make it work again is to change the lighting significantly (for example I point the phone at a lamp). After the auto-adjustment kicks in I can tweak it with the slider again. Is this a bug, or yet another misguided "feature"? Do I have a hardware problem? I've tried a few sensor apps and everything seems to work fine. On top of the auto adjustment not being as good as Kitkat's, the inconsistency is really bothering me.
EDIT: I am on stock rom. I'm sure that CM12 would solve this problem if it's a Lollipop bug, but I can't be arsed with a custom rom a this time. Looking for a stock based solution, or at least an explanation for this strange behaviour.
I had been on FreedomOS or stock OxygenOS for most of my time with the OP3T (though I used RR briefly) but I recently decided to give Paranoid Android a try. I'm having some Bluetooth issues there so I was planning to go back to FreedomOS, but I've noticed that the proximity sensor during a call works much better on PA than on any OOS ROMs. On OOS the screen will intermittently turn back on causing me to hang up or mute the call while on PA the screen stays dark while it is against my face.
Is there any way, I assume with root, to tweak this behavior in an OOS-based ROM?
raptir said:
On OOS the screen will intermittently turn back on causing me to hang up or mute the call while on PA the screen stays dark while it is against my face.
Is there any way, I assume with root, to tweak this behavior in an OOS-based ROM?
Click to expand...
Click to collapse
this happened to me all the time on OOS too, even when I turned off double tap to wake (which I thought was the issue).
Any reason you want to go back to OOS? I'm on NOS right now and couldn't be happier!
rykanator said:
this happened to me all the time on OOS too, even when I turned off double tap to wake (which I thought was the issue).
Any reason you want to go back to OOS? I'm on NOS right now and couldn't be happier!
Click to expand...
Click to collapse
Yeah, my wife has the issue with her OP5 as well. I thought it was just an issue with the proximity sensors OnePlus uses but apparently it's their software.
I've had trouble with Bluetooth on every AOSP-based ROM I've tried (RR, LOS, PA). Bluetooth works fine once connected, but it will often fail to autoconnect. On OOS, my phone will automatically connect to my car when I start it up while on AOSP-based ROMs I often (~60% of the time) need to go to the settings menu and manually connect.
Double post, sorry.
raptir said:
Yeah, my wife has the issue with her OP5 as well. I thought it was just an issue with the proximity sensors OnePlus uses but apparently it's their software.
Click to expand...
Click to collapse
Gotcha, I know on nougat ROMs there was a port of the Google dialer and the dialer framework. I wonder if you could find a port for that at all. I'm not sure if the proximity sensor code is in the dialer framework or if it's deeper in the system.
rykanator said:
Gotcha, I know on nougat ROMs there was a port of the Google dialer and the dialer framework. I wonder if you could find a port for that at all. I'm not sure if the proximity sensor code is in the dialer framework or if it's deeper in the system.
Click to expand...
Click to collapse
I'm using Google Dialer on OOS and I'm experiencing screen flashing as well, I think this is OOS fault itself.
Hello,
although the developers are very active and we are getting there, my question is whether there's a ROM that is "complete" at the moment.
With that, I mainly mean the 100% working fingerprint sensor. With that, I mean a ROM that doesn't 100% brightness while using fingerprint reader and that has a functional fingerprint reader when screen is turned off (ie. wakes the phone)?
I am excited about the recent developments, however, I am just looking for a smooth experience for the time being
Thanks again to all the hard working developers.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
You can try all of these and chose the best one for you
(Lineage(18.1/19), OmniRom, StatixOS, ArrowOS (no longer supported, the unit of the maintainer ramdump-ed.))
I haven't tried Statix yet. Good time to try.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
Click to expand...
Click to collapse
Does this mean that fingerprint doesn't wake the phone either?
I currently have Los19, wasn't able to get 18.1 working. Haven't tried OmniRom, but I've tried ArrowOS and it wasn't bad.
Thanks for the pointers! Does anyone know what's the reason everyone is having problems with the scanner?