Hello, I have a OnePlus Two running the latest CM 14.1 nightly. My fingerprint sensor will not work. It stopped working a week ago, at which point I was still running Oxygen OS, whatever the latest update for it had been. my sensor became buggy, not responding, then quit altogether. I have to use onscreen buttons. I still had fingerprint options at that point in my system settings, but I couldn't do anything with them because they were grayed out. I ended up switching to CM 14.1 hoping a new ROM would help it to work, but now my fingerprint sensor is still non-functional.
At this point, I do not even have fingerprint settings in my settings. I can not locate the com.fingerprint.... process that is supposed to be running, so at this point i feel like the sensor might work, but the process is gone or does not exist. When I dial *#808# it does not recognize that dial code and gives me no feedback, which reinforces my thought that the fingerprint service just does not exist.
user: johnthepig, at the end of this forum (http://forum.xda-developers.com/oneplus-2/help/home-button-tried-fixes-t3366992/page2) said back in may that after Oxygen 3.0.1, the fingerprint sensor would not work in anything else. that he tried going to CM and it wouldn't work and then he went back to Oxygen and it worked, and back to CM again and it wouldn't work. My experience was that it just stopped working in Oxygen. Is there a way to manually give my phone the proper com.fingerprint service/process to run?
jcgordon10 said:
Hello, I have a OnePlus Two running the latest CM 14.1 nightly. My fingerprint sensor will not work. It stopped working a week ago, at which point I was still running Oxygen OS, whatever the latest update for it had been. my sensor became buggy, not responding, then quit altogether. I have to use onscreen buttons. I still had fingerprint options at that point in my system settings, but I couldn't do anything with them because they were grayed out. I ended up switching to CM 14.1 hoping a new ROM would help it to work, but now my fingerprint sensor is still non-functional.
At this point, I do not even have fingerprint settings in my settings. I can not locate the com.fingerprint.... process that is supposed to be running, so at this point i feel like the sensor might work, but the process is gone or does not exist. When I dial *#808# it does not recognize that dial code and gives me no feedback, which reinforces my thought that the fingerprint service just does not exist.
user: johnthepig, at the end of this forum (http://forum.xda-developers.com/oneplus-2/help/home-button-tried-fixes-t3366992/page2) said back in may that after Oxygen 3.0.1, the fingerprint sensor would not work in anything else. that he tried going to CM and it wouldn't work and then he went back to Oxygen and it worked, and back to CM again and it wouldn't work. My experience was that it just stopped working in Oxygen. Is there a way to manually give my phone the proper com.fingerprint service/process to run?
Click to expand...
Click to collapse
This is BY FAR the best description and observation of the issue. Did you find any information on that service missing from the apps menu?
Roadsalt said:
This is BY FAR the best description and observation of the issue. Did you find any information on that service missing from the apps menu?
Click to expand...
Click to collapse
No, unfortunately I never found a resolution to the issue. I'm still using my OnePlus Two and just operating it with the on screen buttons. At this point I'm just used to it and don't think about it anymore. It was very annoying originally. I'm still not sure if it's just the missing process, or whether it's a hardware issue and because the hardware isn't there, it doesn't obtain the process or what. Idk honestly. I resigned myself to on screen buttons till I upgrade in another year or so.
Related
Hello all,
It appears my NFC sensor has quit working on my T-Mobile Galaxy S5. To provide some back story in hopes of finding a solution, here's what's going on:
A few days back, everything was running fine. I flashed an unofficial CM12 ROM (Albinoman887's) to my phone, which at the time had broken hotspot and no Netflix support. NFC worked for me at that point, as I used it to 'Tap n Go' when setting up my account to transfer everything to my S5 from my N7.
The next build that was released fixed Netflix for me, but since then I haven't been able to get any functionality out of NFC. According to the ROM developer, NFC works on his device, as it also does for several other T-Mobile S5 owners. I definitely believe that it works for them, but it's super frustrating to me that it won't for me -- even though I rarely use NFC. I'm just irritated at the thought that my sensor may have died and I have no idea why/how. The phone has never been dropped, so it shouldn't be shock damage.
It's also worth noting that I Odin'd back to my stock firmware, just to test NFC, and I couldn't get any NFC functions to work once I started fresh.
I'm not sure what my options are at this point, but I was hoping someone might have some input to help steer me in the right direction.
Quick update: I flashed a CM 11 ROM (Bliss Stalk, to be exact), and my NFC sensors now work like normal. I'm glad to see it's not dead, but I'm completely baffled as to why it doesn't work on CM 12, when the ROM developer is running the same device and it works for him.
Ahh, the perils of Android development. I'm still glad Lollipop is coming along so smoothly, and I apologize to @albinoman887 for being such a pain in his butt!
Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.
I don´t know if it´s a coincidence or not, but I a few days after the update to Oxigen OS 3.6.1 I noticed that the proximity sensor and light sensor of my ONEPLUS 2 stopped working.
I used AndroSenor and Sensor box from the PlayStore, and both os them say thar the proximity and light sensors are missing.
I had a remote session with a ONEPLUS L2 specialist and they wiped my phone and reflashed the latest ROM (ver. 3.6.1), but the problem wasn´t solved..
I guess that, if the sensors don´t appear in the apps I mentioned maybe it´a a hardware problem, but I would like to hear more opinions.
If anyone has any suggestion to try to solve this problem before sending it to repair (out of warranty)??
flash persist.img from fastboot
backup all your info
in some cases it will help
hi there!
I seem to be having quite a similar problem, though, my sensors work, but stop responding after an unspecified period of time (can be anywhere between minutes and hours).
I tried flashing several roms (oreo, nougat) and yesterday i flashed Oreo Pixel Experience (just pure ROM+OP5 camera, no root no custom kernel just to rule out a few things) but the issue remains. Important to mention, i always clean flash.
The best way to describe the issue is: "sometimes the proximity and light sensor just stop working and i dont really know why" which is obviously causing a whole bunch of issues with auto brightness, making calls, picking up when someone calls etc.
The thing is, everything works after a reboot...but only for some time...then the sensors go "offline".
sometimes they work for a couple of hours, even a day...sometimes they die after half an hour or something. I have a feeling that i see them die faster when i have my phone in the pocket and leave it idle for a while, and when i use my phone often and dont really give the phone time to rest they live longer. It almost feels as if the phone goes to some deep sleep when idle for some time, disconnects the sensors, but doesnt turn them on again when woken up.
tried flashing the persist.img as advised just above, but it doesnt seem to have an effect.
anyone has any good idea?
thanks!
allright, being desperate from not being able to use my phone in a normal way i flashed OOS 3.6.1 from official zip files that can be downloaded from oneplus.net support section, using OP recovery and surprise surprise - sensors are working flawlessly! so im ruling out the HW problem. I think im going to stick to OOS for a while to monitor the sensors and eventually im going to try flashing oreo again.
ok, last update from my side: after two days on OOS where everything worked fine i flashed Pixel Oreo build and sensors continue working just fine! so, whoever is experiencing strange behavior of his sensors, i recommend the same approach.
Jackill said:
ok, last update from my side: after two days on OOS where everything worked fine i flashed Pixel Oreo build and sensors continue working just fine! so, whoever is experiencing strange behavior of his sensors, i recommend the same approach.
Click to expand...
Click to collapse
You still have working sensors?
I have exactly the same behavior as you mentioned in your first post. FRUSTRATING!
I've tried flash lineageos 15.1 ROM, no luck. New persist.img from official fastboot oos ROM but no luck either.
flaektrem said:
You still have working sensors?
I have exactly the same behavior as you mentioned in your first post. FRUSTRATING!
I've tried flash lineageos 15.1 ROM, no luck. New persist.img from official fastboot oos ROM but no luck either.
Click to expand...
Click to collapse
Hi! Yes, my sensors are still working just nicely.
Jackill said:
Hi! Yes, my sensors are still working just nicely.
Click to expand...
Click to collapse
So good for you ?
Before when your sensors struggled, did they also disappear from any sensor test app. Or did they just not work?
My prox sensor did not disappear but just hangs at 0 or 5cm if I check the value in any sensor app. And light turns 0 Lux also.
I've similar problem. Went completely stock as suggested but the problem persisted.
flaektrem said:
So good for you
Before when your sensors struggled, did they also disappear from any sensor test app. Or did they just not work?
My prox sensor did not disappear but just hangs at 0 or 5cm if I check the value in any sensor app. And light turns 0 Lux also.
Click to expand...
Click to collapse
Well mine didnt really "dissappear" either. They "froze" too. Lux froze at whatever value it measured the last however i am almost certain it was never exactly 0. Prox behaved the same as you describe: 0 or 5.
lazyfarmer said:
I've similar problem. Went completely stock as suggested but the problem persisted.
Click to expand...
Click to collapse
Interesting. I'm going to flash OOS recovery and latest OOS ROM later today and give it a try.
Jackill said:
Well mine didnt really "dissappear" either. They "froze" too. Lux froze at whatever value it measured the last however i am almost certain it was never exactly 0. Prox behaved the same as you describe: 0 or 5.
Click to expand...
Click to collapse
My lightsensor always freezes at 0 Lux. And when the prox freeze at 0 its impossible to quit a call. So f*cking frustrating so I have to fix this problem ASAP
I have the same problem with my LUX device, sometimes the sensors work randomly. When I reboot my phone the sensors stop working. The screen does not rotate, the most interesting thing is that it did flash the Moto camera mod and the rotation works perfectly with the camera, with the stock camera there is no rotation.
UPDATE:
I scheduled a remote session with Oneplus L2 Team and they performed a full factory reset of all partitions. No luck, problems still persist.
It must be a hardware problem.
In my case I sent the smartphone to them and they said it was a problem with the motherboard.
Hey guys!
Just to be clear it is not a hardware issue I don't have any kind of a problem with the stock ROM. Everything fingerprint related works as it should.
The problem. I am able to set several apps to use fingerprint login (couple of banking apps and ebay app for example). Everything works fine until the first reboot or the first day. Then the apps suddenly stop to use (or see or detect) the fingerprint sensor. They either start with an error or give the error when I try to login with my finger. When I log in the app with a PIN code I can see the fingerprint login is disabled and when I try to re-enable it the most of the apps crash, some of them just repeat again the error. It's not that they don't recognize the fingerprint itself. They simply don't get that far - they can't use the sensor.
The problem for me is present in every custom ROM I've tried, no matter 8.1 or 9.0. I've tested Liquid Remix (9.0), Havoc (9.0) and Bootleggers (8.1)
On the other hand unlocking the device with fingerprint works always fast and perfectly fine no matter the ROM - stock or custom.
Just a little update here. I found another ROM that (so far) has no problems in regards of the fingerprint. The unofficial Pixel Experience.
I've been looking around to solve this issue, but haven't have much luck. It looks like it's an issue with a good number of ROMs on this phone, but my issue is that after some time, the touchscreen in some games and apps stops working normally.
Phone is running Lineage 16, rooted w/ magisk
To have it work, I need to hold one finger on the screen and the other finger will register properly.
The issue can temporarily be fixed by rebooting the phone.
I notice the issue occurring when an app/game accesses the camera. At that moment, issue occurs.
I came across this in my searches: https://review.lineageos.org/c/Linea...ative/+/198809
Not sure exactly how to work with that, but I figured I would provide as much info as I can before asking for help. Thanks ahead for the help