Last week, I took my phone off the charger and noticed that the home button was not working. Did multiple reboots, clean wipes and also reinstalled the stock ROM, nothing worked. Did the *#808# fingerprint test and found that the figerprint sensor was not responding which led me to believe this could be a hardware issue. I did not have the time to go to the service center so I turned on the on-screen navigation bar and used it like this for a few days.
Today, I thought I'd try to sort this out one more time before I take it to the service center. The *#808# fingerprint test still showed the sensor not available. Rebooted the phone and turned the on-screen nav bar off. Lo and behold the home key started working. I do not know how this happened, I'm just glad that it did.
Just thought I'll post here so that if anyone has issues they could try this out and it might help someone.
Cheers.:good:
I got the same problem. My OP5 Home button(with fingerprint scanner) stopped working suddenly. It got stock android since purchase. I never tried to root it. It suddenly became unresponsive. Will try to use nav bar for few days. Im getting ghost touches as well. Any Help appreciated.
Hi. I have the same issue on my op3t, looking for idfeas.
finalmoksha said:
Last week, I took my phone off the charger and noticed that the home button was not working. Did multiple reboots, clean wipes and also reinstalled the stock ROM, nothing worked. Did the *#808# fingerprint test and found that the figerprint sensor was not responding which led me to believe this could be a hardware issue. I did not have the time to go to the service center so I turned on the on-screen navigation bar and used it like this for a few days.
Today, I thought I'd try to sort this out one more time before I take it to the service center. The *#808# fingerprint test still showed the sensor not available. Rebooted the phone and turned the on-screen nav bar off. Lo and behold the home key started working. I do not know how this happened, I'm just glad that it did.
Just thought I'll post here so that if anyone has issues they could try this out and it might help someone.
Cheers.:good:
Click to expand...
Click to collapse
Hi. I have the same issue on my op3t, Oxygeos Version 9.05. My home and recents buttons do not work but fingerprint works fine. I turned on the on-screen nav bar and the home and recents buttons don't work there as well. Turning it off didn't solve anything. Any idea? Thanks
Facing exactly the same issue after upgrade to 9.0.5. home and recent buttons are not working, but fingerprint is working fine. Did you resolve this issue by any chance? if yes, please let me know as well how it was resolved. thanks. -ramesh
Try doing a factory reset, but take a backup before doing that.
Sent from my OnePlus 3T using XDA Labs
I am also facing this issue. It started off with a boot loop into the recovery every time i try to start the phone. It stopped after i cleared cache from recovery, but the default launcher doesnt work properly, no notifications in my drawer, and many other issues. the hardware buttons are responding (it lights up when i tap on it) but the OS doesn't do anything with it. I have tried with switching to the soft keys and it behaves the same way as well. the fingerprint scanner and back button works so far.
i'm having this problem too Got a OP3T, i found out a bit of info, it has to do with the screen, i'm still facing this problem so im gonna buy a replacement screen and see how it goes, ive already replaced the earphone jack board that houses most the flex cable connections and i also replaced the speaker, home button, and the usb c flex cable to no avail. what i haven't tried was to replace the battery and the main/sub flex cable inside. i'd really like a fix for this.
go to Settings -> Apps -> All Apps (ie including System apps)
look for com.android.fingerprint... or com.oneplus.fingerprint...
"Force Stop" it. and go to its storage and "Clear Cache" , "Delete Data" .
Now restart the Phone.
Worked for me on OnePlus3T running OxygenOS 9.0.5.
Phone was also on charging through out the procedure .. I doubt if it would have any significance though.
Good Luck.
I could not force stop this app.
MY SOLUTION
this is what it worked for me with OP5
I deactivated fingerprint, reboot to recovery, wipe cache+dalvik, restart (without fingerprint anymore) and it seems to be working just fine again.
I have observed this issue too in my oneplus 3 with oxygen os 9.0.6 and also in previous releases. The only thing that works for me is just to reboot the phone.
cincauhangus said:
I am also facing this issue. It started off with a boot loop into the recovery every time i try to start the phone. It stopped after i cleared cache from recovery, but the default launcher doesnt work properly, no notifications in my drawer, and many other issues. the hardware buttons are responding (it lights up when i tap on it) but the OS doesn't do anything with it. I have tried with switching to the soft keys and it behaves the same way as well. the fingerprint scanner and back button works so far.
Click to expand...
Click to collapse
I am facing the exact same problem. Have tried all the other fixes/solutions mentioned in this thread except the 'Factory Reset'.
Please let me know what did you finally do to resolve it.
Thanks
Something new? I Have flash Havoc ROM, but problem still exist :/
back button and recent button does not work on mine.
I have to turn on screen navbar..
The home button was not working.. but it started working after i enabled onscreen navbar...
The phone went to frantic vibrate the first time it boot after flashing new rom..
the light can be seen on these 2 non functional h/w key during boot , but then it turn off, then the h/w back and recent key would not function..
I don't even know what happened to this phone...
Guess i'll keep using the onscreen navbar...
Related
I got my A7 and flashed the 4/17 rom right away, used it stock for a couple of days then installed dexters mod1.42 and for a day or two it worked fine. Then the menu key stopped working. sometimes it would work for an hour and then stop working again. I deleted the dexter mod, wiped cache and did factory reset when the key worked and everything was fine.
Then I did the bestialbub a7-gapps zipmod and everything worked great for 4-5 days then the same problem, no menu key. are there any known apps that may cause this problem? I am waiting for the menu key to work again so I can try again, are there any settings or other mods that will get me the market but leave me close to stock.
steamtv support just had me do a reset and flash latest firmware and that doesnt help much.
Please, I love the A7 when it's working and need some help.
Thanks,
Billy
Does this happen when the back of the device is hotter than warmer? I've had this happen often when the days are warmer and hotter. That's the reason why because the heat affects parts of the wiring. The other solution is to use Button Savior (an app on the market).
Ytain
The menu smart key comes and goes no matter the temp. It's not working now, sometimes it will work for a little while and then stop again. I can't wipe/reset without the memu key. I want to get it back to stock to see if it's a hardware problem then take it from there. Any suggestions anyone?
billy
same here (I thought, I'm the only one encounter this kind of problem). My Aunt gave me A7 as present. after 2 days, all the smart keys malfunctioned. it works fine for 10 min after that it wont work anymore. I've installed button savior for remedy. I think ytain is right, A7 has problem when the back of the device becomes hot.
Hello,
I had the same issues with some of the keys of the keyboard. but at first it started only happening when the battery was low but recently it was happening all the time.
This was making my life difficult as i write some sms to my friends and it's quite annoying.
I left my phone untouched and went to repair center of my provider to show what was happening. Put my phone there for repair and in the same day went there to pick up the phone good as new.
The issue is that the stripes connecting from the keyboard to the cellphone were a bit fragile and probably broke or it wasn't making any contact whatsoever. Now i have the phone working 100%. no problem.
Hope this helps
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
kitkat disaster
metar0n said:
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
Click to expand...
Click to collapse
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
kombochekenyere said:
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
Click to expand...
Click to collapse
Bringing this old post up as I just now encountered this on my AT&T LG G2. It occurred when I was using Google Maps which then crashed and caused everything to freeze. Upon reboot, I get the exact same issues as stated above. What was the outcome for you guys? Did you end up doing a hard reset?
Everything appears to be functioning with the exception of above. I'm suspecting a software issue with the home launcher as the soft keys are responsive but the Home one. The Notification Bar lags when trying to drag it down, but none of the notifications are functioning. I also noticed a significant amount of lag. Prior to the "crash" my phone was flawless with no lag for the past 10 months. I absolutely have no clue what just happened...
Anyone else experiencing this issue? Multiple threads on the OP2 official forums. My home button has become completely unresponsive and fails the diagnostic test (run by *#808# in the dialer, then going to "fingerprint test" or "keypad test")
Reports of the issue on the other board seem to be focused on the non-US model. Anyone else in the US experiencing this issue?
Going to go through the RMA process with the phone but doesn't seem like that will be a fast process.
Yes same issue... Not sure how to fix
One of my friend got his OP2 in India, and Service Centers are asking for AT LEAST 3 weeks for fixing this issue.
Same issue here. Tried flashing all the OTAs with any combination available in the book (since in other threads, said this fixed it), no luck.
Had this happen to my OP2. Initially had sold it but had it returned to me because of the issue. When I got it back I was able to get it working.
Shortly after that it stopped working again. Manually flashed 2.1, cleared data and cache and powered it ought door awhile as I was going to return the.
Decided to power it back on and need with it and it was working fine. Been working fine for the past three days even after unlocking the bootloader, rooting and flashing 2.1.1.
Not sure what the issue was with mine but it's working fine now.
OP support wanted to do a remote session to flash 2.0.2 with a special partition file but since I've been on vacation I haven't gone through that with them. Might not now that it is working good.
Sent from my ONE A2005 using Tapatalk
same issue here. have a open ticket with One plus awaiting a resolution.
I had faced the same issue in my OPT as well...A small trick resolved the issue.. In diagnostic test mode ( *#808#) I have tried finger print test -> finger print quality test -> some menu in Chinese with button (in Chinese) -> pressed button and placed finger on scanner -> the screen shows some numeric values... Done few times... After that my phone home button and fingerprint started working.... Registered finger again and all fine...What a magic...
Precondition oxygen 2.2.1
Previous fingerprint registration deleted..
Not sure whether this method may work for all... But can make a try.... Bibin
Try hard reset. Press power button for 8 seconds and let it restart the phone. Scanner comes back to life. Usually it happens due to some app updating conflicting with sensor setting.
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
VikramK123 said:
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
Update: So today at work it decided to behave seemingly out of the blue.
Heya,
So I have a problem with my Note 4 that I just cannot figure out this time around. I found that the lock screen was turning itself on even when left alone on a table and on top of that the home button is not working. After I installed a security update I had put off installing the home button worked again for about 10 minutes or so. I figured it was a software problem so opted to factory reset the device. No problem getting into the recovery menu by holding power and volume up.
Once that was done though the problem persisted. I'm inclined to think it's hardware but I figured before I throw down money on parts I'd get a second opinion just in case I'm missing something.
It's a N910-P running 6.0.1 and April's security update. Any ideas/suggestions would be appreciated.
Thanks!
My device is doing exactly the same thing all of a sudden... Seeing a few other threads with similar issues... I'm guessing a Google Play Services update, as the play store icon changed just about when it happened...