Whenever I disconnect/reject a call on my Nexus 6 the phone screen doesn't respond!
I can lock the phone and use the screen swipe up to unlock it, but after unlocking it screen doesn't respond.
If I hold the power button and touch on power off or power on, it works, the phone powers off/restarts!
When unlocked, the nav buttons work. But the part above the nav bar buttons doesn't work. It however, works for the above mentioned cases
It's very irritating yet funny how it isn't responding.
Is the system frozen?
No, lock and unlock works, on screen nav buttons work, restart and power off menu works!
Is the touch screen not responding?
Nope! Consider the same answer as above
Can anyone help me with this issue please?
PS: Only started facing the issue after updating to Android 7.1.1 (Yes, I did manual OTA install)
Rajakodumuri said:
Whenever I disconnect/reject a call on my Nexus 6 the phone screen doesn't respond!
I can lock the phone and use the screen swipe up to unlock it, but after unlocking it screen doesn't respond.
If I hold the power button and touch on power off or power on, it works, the phone powers off/restarts!
When unlocked, the nav buttons work. But the part above the nav bar buttons doesn't work. It however, works for the above mentioned cases
It's very irritating yet funny how it isn't responding.
Is the system frozen?
No, lock and unlock works, on screen nav buttons work, restart and power off menu works!
Is the touch screen not responding?
Nope! Consider the same answer as above
Can anyone help me with this issue please?
PS: Only started facing the issue after updating to Android 7.1.1 (Yes, I did manual OTA install)
Click to expand...
Click to collapse
Without the basic logcat there is nothing that anyone will be able to help you with. Logcats are trouble shooting 101
zelendel said:
Without the basic logcat there is nothing that anyone will be able to help you with. Logcats are trouble shooting 101
Click to expand...
Click to collapse
Reinstalled the same image and rooted the phone! Issue resolved
Related
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
I just recently purchased a Nexus 6 project FI phone that was on sale and have been encountering a weird issue: whenever I lower the brightness down all the way and try to hit the power button to unlock, the lock screen flashes for a second and goes back to black and I'm not able to unlock it. What's weird is it still registers my touches because it vibrates as if I was swiping for my unlock pattern. The only solution to this is to keep hitting the power button quickly until the screen finally decides to turn on.
The build is LYV48h running 5.1.1 and rooted/unlocked
Has anyone run into this issue, and if so what can I do to fix it? My next plan is to factory reset it and see if that helps at all
Thanks for your help!
Has anyone encountered a frozen screen?
Use the touch screen to malfunction. You can only press the power button again to lock the screen and unlock it:crying:.
hackjackyer said:
Has anyone encountered a frozen screen?
Use the touch screen to malfunction. You can only press the power button again to lock the screen and unlock it:crying:.
Click to expand...
Click to collapse
None as I'm concerned. You should get it replaced. Although it maybe something cause by static. Turn it off for 3o minutes or so and only use the provided cable. Give it a try.
hackjackyer said:
Has anyone encountered a frozen screen?
Use the touch screen to malfunction. You can only press the power button again to lock the screen and unlock it:crying:.
Click to expand...
Click to collapse
I have the same issue, I think is not a frozen screen, its the touch, try pressing volume keys and you will see that works. It happens several times at day, curiously that started after a Factory Reset, before never happened
Zisco0011 said:
I have the same issue, I think is not a frozen screen, its the touch, try pressing volume keys and you will see that works. It happens several times at day, curiously that started after a Factory Reset, before never happened
Click to expand...
Click to collapse
I went to Nokia after-sales service and they replaced the screen for free. Tell me the screen problem.
hackjackyer said:
I went to Nokia after-sales service and they replaced the screen for free. Tell me the screen problem.
Click to expand...
Click to collapse
Nice to hear it, please comment if the issue occur again. Regards.
This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?
Do you have lock instantly with power key on?
funkyverb said:
This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?
Click to expand...
Click to collapse
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!
funkyverb said:
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!
Click to expand...
Click to collapse
This delay issue is so silly but it annoys the hell out of me. Where did you turn off this feature in Pie?
Update: Found it. Just use the search box in settings and type in "camera" (or whatever it is in your language). The "double tap power" setting will get listed.
Thanks alot,
Watz
I even turned off the double press for camera app but I'm still noticing a 0.5 sec lag when i press the side key
I even restarted after changing the setting
Nothing is happening
Please help
xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Thank you bro.
Hello friends,
My situation:
Out of the blue my phone stopped responding to the wake-up action. Every time I lock it, I have to restart for the screen to turn on again. The power button is working just fine, since I can go to recovery mode and use it to select options there. I even installed a somewhat wrong version of the TWRP recovery that would not boot to the main OS, but the power/lock button would work just fine in recovery, putting the phone to sleep and waking it up. I reverted the instalation after so I could boot to the main OS ( Android 10). I tried reinstalling(from an official image of the rom) the full rom, incluing everything from OS to Bootloader, and could not make the wakeup action work again. Once my phone is on, if I lock it, I have to force a restart to turn the screen on again. I even tried sending a direct command to the OS using adb shell input keyevent KEYCODE_POWER and KEYCODE_WAKEUP to no success. Even tough I made sure other common events like opening the camera (KEYCODE_CAMERA) were working when the screen was on, and I bet it was working when the screen was off too, but it would not wakeup the screen and I would not be able to see the camera view finder.
My phone is a Samsung galaxy A30, model SM-A305G, currently in Android 10.
I think I described the problem good enough, but If anyone have a problem understanding it, just let me know and I try to explain it better.
Can anyone help me out here? I tried a lot of things to not success.
Thanks!
I have the exact problem you described, did you find any solution ?
Shalesh said:
I have the exact problem you described, did you find any solution ?
Click to expand...
Click to collapse
flash official ROM with Odin or with twrp
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Shalesh said:
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Click to expand...
Click to collapse
very strange
I made furher research about the issue and here is what i've found.
Some videos mentioned same problem in similar samsung models and they stated that changing the daughterboard that connected to motherboard via screen flex resolved the issue. Other videos reflowed the connector in the motherboard side of the flex.
Also phone not responding the adb power commands while in sleep but responding fine when awake got me thinking there is a problem with a some kind of awake pin of screen. Probably there is a short or a missconnection in that pin. That's why solutions in the videos work I think.
It is definitelty not a software issue because it happens in every official or custom rom except in twrp (which does not put screen into sleep mode according "mScreenState" info)
It is not a hardware issue related to power button. Power button works perfectly fine in recovery, download mode and when awake.
Its a hardware issue that probably about the connection that sends wake up signal which maybe from motherboard side of the connection or maybe daughterboard side.
Not a real solution but I found a app called touch protector which has an option that you can disable the touch and set screen brightness to 0%, basically means normal off state for the amoled screens.
I set double click of volume down to sleep mode for touch protector. Maybe with some keymap editing someone can set powerbuttons function to not real sleep but touch protector's sleep. This will be best software solution.
In the hardware side if the problem is daughterboard it can be swapped easily but reflowing smd connecters in motherboard could be risky for me and I don't want to open the never opened device for not solving the problem.