Hi, I'm new to the forum.
I installed
[ROM][LOS][OFFICIAL][7.1.1]Resurrection Remix-N OnePlus 3[26/01] by sud.vastav
and it works very well at the first look. But sometimes when i try to unlock my phone (Oneplus3) with the fingerprint nothing happens. Then i have to tap it for 3 or 4 times and then it will unlock. There is no wrong finger or something, it just does nothing.
At the next time it works fine and without problems. I have wiped the phone completely and flashed it again, but its the same.
Does anybody know a solution?
Thanks
Its a ghost bug. I was looking for days for answers, maybe someday it will be fixed. What about the FW+Modem?
Can it depend on what kernel do you use?
I can not post a link to a pic
Baseband: MPSS.TH.2.0.c1.9-00078-M8996FAAAANAZM-1.81324.1
If that's all I can live wth that, because I realy like this rom :laugh:
Greets
I have flashed now the ElementalX Kernel, but still the same, sometimes it will not unlock. Specially when i get a notification and i wanna unlock the phone. So It has nothing to do with the Kernel.
If someone has a solution i would be happy about it.
And by the way,
what camera apps are you using?
I opened the camera and sometimes it dont works, when i press the home button i see the camera on my homescreen. Now I installed "Open Camera" --> no problems any more
Greets
Related
every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z
Do you have set CPU set to 245MHz @ screen off?
no i dont, why?
Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!
I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.
Problem solved, An update did the trick, thanks for helping out my friends,
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
Hello guyz.. My htc 816 touch screen not working properly, have to press several times each button.. This suddenly happened.. I turn on in settings "show touches" and began to see in the left down corner on the back button that the touch is moving there and pressing back very fast.. Now this issue often appear .. But now the soft keys are not pressing from the first time I touch them.. The notification bar is to hard to open either.. And tapping a message is a massacre hehe..
P.s : I'm rooted.. And I try to install cm12 but nothing happened.
Plz friends help.. And thanks
Flash a RUU, or restore a stock backup and see if the problem persists.
I have the same issue. 816x single SIM. Any Rom I flash I get this same issue after a few minutes into the Rom. Only on stock it works normally. I have used most recent released of twrp and cwm. I have also tried garak kernal and stock trying to narrow it down. Any ideas on this?
FoxyDrew said:
Flash a RUU, or restore a stock backup and see if the problem persists.
Click to expand...
Click to collapse
OK I'll try... And I will tell u what happens..
uushh2u said:
I have the same issue. 816x single SIM. Any Rom I flash I get this same issue after a few minutes into the Rom. Only on stock it works normally. I have used most recent released of twrp and cwm. I have also tried garak kernal and stock trying to narrow it down. Any ideas on this?
Click to expand...
Click to collapse
R u sure is the same issue?? Cuz I'm worry it's a hardware issue..
Sounds the same to me. Have to hit home keys few times to get it to work, trying to text is hectic. During swiping it'll select things instead of swipe. Put on pointer location youll see it on and off while moving around the screen (even though you're doing a circle with your finger). Something around those lines?
Did anyone find a fix on this at all? Seen a few posts on this but no answers yet.
I have the same issue . plz help
same here. on virgin mobile, is there any fix?
i have 2 phone with this issue
plz help to fix
Sepid Gsm said:
i have 2 phone with this issue
plz help to fix
Click to expand...
Click to collapse
I also have this problem. Just started two days ago. The most problematic is the going back button and the home button. Text is a nightmare as swipe works intermittently and it's all so slow. I've had to turn it off and on to get out of the camera or off another page due to the back button not working. It has also started bringing up random pages that I haven't touched, as someone else said somewhere.
I've taken the sim card out but that doesn't seem to be the problem.
So, if I restore to factory settings as has been suggested, what happens to my apps? I'm only concerned about my one paid app as it was $28! Can I just download via pc as I did initially?
What if this doesn't work? This is a new phone from January ... I love it :crying:
Anelei32 said:
I also have this problem. Just started two days ago. The most problematic is the going back button and the home button. Text is a nightmare as swipe works intermittently and it's all so slow. I've had to turn it off and on to get out of the camera or off another page due to the back button not working. It has also started bringing up random pages that I haven't touched, as someone else said somewhere.
I've taken the sim card out but that doesn't seem to be the problem.
So, if I restore to factory settings as has been suggested, what happens to my apps? I'm only concerned about my one paid app as it was $28! Can I just download via pc as I did initially?
What if this doesn't work? This is a new phone from January ... I love it :crying:
Click to expand...
Click to collapse
take it to hTC if it's under warranty.
paid apps will remain in your Google account if you have purchased them in google playstore.
seekfind said:
take it to hTC if it's under warranty.
paid apps will remain in your Google account if you have purchased them in google playstore.
Click to expand...
Click to collapse
Thanks. I have hard reset to no avail. Now to tussle with Kogan...
Any firmware solution so far?
ctnerdem said:
Any firmware solution so far?
Click to expand...
Click to collapse
Have sent back to Kogan and am still waiting. Been gone for over a week now
zheo77 said:
Hello guyz.. My htc 816 touch screen not working properly, have to press several times each button.. This suddenly happened.. I turn on in settings "show touches" and began to see in the left down corner on the back button that the touch is moving there and pressing back very fast.. Now this issue often appear .. But now the soft keys are not pressing from the first time I touch them.. The notification bar is to hard to open either.. And tapping a message is a massacre hehe..
P.s : I'm rooted.. And I try to install cm12 but nothing happened.
Plz friends help.. And thanks
Click to expand...
Click to collapse
Your device software is not up to date speaking bootloader wise. This happens and causes your device touch functions to act up. This was an early issue when device was just released.
Sent from my 710C using XDA Free mobile app
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Hi there,
did anyone notice this? Compared to Stock (OOS), the fingerprint scanner on any Custom Rom I've tested so far is quite slower. Maybe not the detection of the fingerprint, but the unlock itself, maybe it has like a 1000ms delay that can be set to 0 ? It bugged me for a while now but I couldn't find any settings on this.
Currently on ResurrectionRemix-N 5.8.0-2016-12-18.
I doubt an update to the very newest version will help though, as I already had this problem since my first custom rom on this device (which wasn't even RR).
Seems like custom roms sometimes take a second to activate the fingerprint scanner, there's been times I went to use it and it clicked like I pressed home. Have to swipe up to get to the pin input screen then usually that works. Guess we'll see if it's the same on lineage when I get around to flashing that after work
Sent from my ONEPLUS A3000 using Tapatalk
Im also facing the same issue .i have fpc fp i dont find any solution yet
Hi guys, I'm currently on AEX 4.6, everything is running smoothly but all of the sudden my fingerprints sensor is not working as well as the slide options. The actual button works. It clicks so I'm managing to use the phone normally but no u-touch function. I've already tried different roms and nothing seems to work. Has anyone experienced a similar problem? I'm afraid it's a hardware problem.
I'm glad to say that I found the solution for this problem on another thread. The sensor driver might have had an issue, so installing it again will solve the malfunction. After all it wasn't a real hardware problem. Just download the file I'm sending and restart your phone so it'll come back to life again :laugh:
Here's the link:
dropbox. com/s/0gqvvfzae4exi12/sensor.zip?dl=0
PS: it didn't work at first with me. So I sort of gave up then I tried another time and it worked.