Hi everyone,
So my issue is one that I don't see anywhere else, hence this thread. I'm not entirely sure if it's a hardware or software issue, and I'd like your help/suggestions (pls)
If I boot the phone via "normal startup" or whatever it is from fastboot mode, it boots. However, after I get into the OS, if I press the power key to take the screen off, and I press it again to turn it back on, it doesn't turn back on. The phone still operates - it receives calls, I hear all sounds, I can even tap by memory to get to different settings, but the screen won't turn on at all until I boot into fastboot and reselect the normal startup option.
I tried enabling tap to wake via custom kernel, reassigning the volume keys to turn it on, but it simply doesn't work. I get the same issue if I double tap to sleep (the top bar) and then double tap to wake. I don't know what else to try - any suggestions?
I'm wholly ready to just call it a loss (I already have a new Moto G) but it would be cool if I could somehow revive this one. The reason I decided not to use the warranty is because I was pretty sure it had already been voided since my mother dropped it in water. As I said, this may be a hardware issue, but I'm not entirely sure and I'd like your opinions/suggestions?
For reference, it had this issue while on stock as well. It ran the latest update Motorola had sent out. It's the XT1063.
Thanks in advance!
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.
If your phone's power button is in a 'pressed' state, like mine, (turns on automatically when battery is inserted), it is a hardware issue.
Here is a hassle free alternative to turn on the phone when it is in sleep mode, without relying on the power key!! Takes a minute or two only!!
1. Get 'Go launcher' from the app market (play)
2. Get 'Go Locker'
3. Now Enable Go Locker on your device. And you are done!!
When the screen goes black again, Just press the volume button, The screen wakes up!!
Using this method you don't lose the normal functionality of the volume rocker!!
I recalled that I used to have Go Locker on my phone, and that when I pressed the Volume key the screen turned on!!
At that time I found it a little annoying, But now it has turned out to be such a gift!!
* For this method to work, your phone has to be rooted.
The power button is not going to work until the hardware is repaired, I prefer to use this method, because it is a safe and quick method!!
Believe me I looked around the internet and this forum for a fix, The usual method: editing the system files on the phone, and after which the volume button cannot be used to control the volume.
For those looking for a quick fix, just follow my method!
Cheers!
There are also several roms out there that have the volume rocker wake built into the rom without making it completely useless for it intended purpose. As well as several that offer a go to sleep toggle in the notification window so you can lock your phone again.
so this is a hardware issue ? i had been using the go locker i been using but the power button is annoying cus it keep showing the power button options . and killing my battery.
only fix is samsung?
Pretty much every version of cm for cappy has volume rocker wake as an option, because of this common problem. I use app called turn off screen as well.
Natureboyhcg said:
so this is a hardware issue? only fix is samsung?
Click to expand...
Click to collapse
I had the exact same problem with my Epic Touch 4G. Thought it was the ROM, the overclock, etc. I flashed back to (almost) stock, went back to original clock speeds. I couldn't figure out what it the world was causing the issue, until it got worse. Then, I noticed that even brushing past the power button would wake the screen, and about 10 seconds later the phone would reboot.
Long story short, I bought a replacement power switch, soldered it in place, and have had zero problems since!
Several eBay sellers offer the proper replacement switch you'll need.
(They don't include the required skills to properly desolder/solder it, however. It's a tiny switch - about 4mm x 2mm x 1.5mm, and you'll need a good quality fine-tipped soldering iron.)
Hi,
My KnockON functionality is acting up. It used to work fine, until 2 things I did to my phone. Is there a way to somehow reset/refresh the phone, without doing a factory reset? I don't want to lose the free wifi tether, because I'm on ZVC.
Details: I installed some Ingress timer app, and it somehow messed with the phone to where my phone sometimes ignores the wake-up when I tap twice on the screen. The phone is fine when I double-tap to sleep the screen. And sometimes it wakes up fine. Other times, I need to hold my finger down on the black/sleeping screen, and then it wakes (so that's just one tap and hold, instead of the usual double-tap, to wake the sleeping phone). Other times it could be that I tap several times, hold my hand on the screen, etc., and it might work. Then other times no tapping or holding will work, and I have to press the physical button to wake the phone. But I never have any trouble when I double-tap to sleep the phone, because I think the phone is fully awake at that point and able to detect each press correctly. So something is making my phone sleep so hardcore that it may ignore some screen taps. I have already tried using quickshortcut maker to launch the hidden KnockON menu, and toggled that on/off with resetting the phone in between, and also tried installing and uninstalling the Ingress timer app that led to this.
Just want to confirm that my situation is hopeless and I have no choice but to perform a factory reset, and then figure out how to get wireless tether later. But I'm worried that there is no mention whether people on ZVC have any options when it comes to free wifi tether after doing a factory reset on ZVC?
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.