I'm having an odd problem, and wanted to see if anyone has experienced it.
My Evo was replaced by Sprint when it started randomly rebooting multiple times a day. The problem I am having never happened on the old phone, although given the nature of it, it seems odd to be a hardware defect.
Basically, whenever you engage Car Mode, either by running the car dock app manually, or by dropping the phone into the dock, the menu button stops working on the dialer screen.
By dialer screen, I mean both the dialer and the in-call screen, which I believe are part of the same apk. If you hit the Evo's Menu button, it vibrates as usual, but the menu does not appear. If I pull it from the dock or exit car mode, it reonsumes working as usual. It does not affect the menu button on any other application.
I have tried re-flashing rooted stock, flashing MikG GB Sense, Swagged out Stock. I have repeatedly wiped everything before and after flashes. I test it each time without installing anything else, so it's not caused by apps I've installed, unless the wipe process has left something laying around that will not go away.
I have googled the web, as well as searching this site. I can't find anyone else who has reported this issue.
Has anyone seen this, or have any ideas on solving it?
I'll add that I tried flashing a rooted stock, and then taking my SD card out, just to make sure there was nothing loading from the SD card. Same issue with the menu button.
I was playing NFS Underground on my Nexus 7 (Running Paul O'Briens MCR) and I have started having a weird problem with it.
I was playing away (at work) and someone came in the door, so I switched the screen off, after that it wouldn't respond to me pressing the power button to turn it back on. (I was using Gesture Control to hide the Nav Bar also)
So I held the Power Button to Hard Reset it, and it still wouldn't come back to life, so I thought I should plug it into the wall to give it a charge, then try again! When I picked it up 10 minutes later there was a weird vertical static on the screen (a bunch of white dots on black background), and again it wouldn't respond to any input.
From there I have tried to Wipe Dalvik & Cache and reboot (same happens), I tried to backup my ROM and flash a fresh one, the same thing happens in the middle of a backup.
I have managed to start it a few times (and it has now managed to process all the apps after the Dalvik wipe), but as soon as it boots, it just re-starts?
Anyone have any ideas how I can get it up and running again?
Also one thing I have noticed (this may be related to an updated Bootloader) whenever I plug my Tablet into the Wall, it turns on automatically! It definitely never used to do that!!
This is driving me mad!!!
Cheers
Stewart
EDIT - I seem to be able to put it in bootloader mode without it turning itself off!
Going to try flashing back to stock!
Quick question, can I pull a file from my SDCARD partition using my Mac while in bootloader?
Moral of the story, don't play games at work :/
But on a helpful note to you, yes you can pull a file.
If it doesn't boot, I'd get TWRP and the mount it whilst in recovery mode.
From there you can push/pull files
I seem to have the most bizarre issue that started happening last night. Ive been running XNote v3 and AEL kernel fine for a long time now.
Whenever my screen turns off (when i hit the power button or the timer runs out to turn screen off) The phone will after x minutes, either auto reboot or turn off (without shutdown animation)
It then remains off black screen and you do not know this unless you try use it again as you cannot power it back on at all, no sound and the phone is off as if you call you get voicemail.
Anyone any ideas what it might be?
I cant work out if it is software/ hardware related as nothing has changed software config wise and i have not done any updates.
I was thinking of maybe going to a stock kernel and see how that lives.
Its very easy to replicate and the only way to bring the phone back to life is to take the battery out.
If i am using the phone its perfectly fine, no reboots, freezes etc. Its only when screen is off.
OK since no one replied back but a lot of people viewed i thought i would provide an update.
Since factory resetting it
changing battery
wireless charging
removing sim
removing SD card
changing rom
changing kernel
changing back to stock
remove root
boot loader etc
all failed! a new replacement motherboard fixed the problem. i am unsure what caused the fault as it was working perfectly for over a month.
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...
I have an ASUS Nexus 7 2012 Wifi (grouper). I have installed a custom rom and recovery on this device. (This didn't cause the issue)
It was on its original firmware and I was playing a lite game on it. (King of Maths) I was playing and scrolling through game menus hen suddenly the device shut down without warning the screen just turned off. Then I rebooted it (turned on with power button) and immediately started glitzing with artefacts on the screen, and touch didn't work in some places. A few years later I tried to revive it with lineage os 14.1. It had worked and was running the software, but the glitch was still there. and when I pull down notification shade, (only on home screen) and tried to just brightness with slider. The touch stopped.
Anyway I can fix this?
Thanks, Yeebee
Yeebee said:
I have an ASUS Nexus 7 2012 Wifi (grouper). I have installed a custom rom and recovery on this device. (This didn't cause the issue)
It was on its original firmware and I was playing a lite game on it. (King of Maths) I was playing and scrolling through game menus hen suddenly the device shut down without warning the screen just turned off. Then I rebooted it (turned on with power button) and immediately started glitzing with artefacts on the screen, and touch didn't work in some places. A few years later I tried to revive it with lineage os 14.1. It had worked and was running the software, but the glitch was still there. and when I pull down notification shade, (only on home screen) and tried to just brightness with slider. The touch stopped.
Anyway I can fix this?
Thanks, Yeebee
Click to expand...
Click to collapse
Just so that I understand, are you saying that upon adjusting the brightness, the touchscreen failed to respond? It seems odd that it would do that. Does the touchscreen work at all anymore? If you could enable developer options and usb debugging then it would be very useful to post the 'adb logcat' output.