Help me
I am Japanese and I am not good at English.
Because it translates and writes, it may not be correct English.
I can not unlock after sleep.
The screen lights up with the power button.
But swiping the screen does not react.
In this case it is OK.
case 1
In Recovery Mode (TWRP), I can swipe the screen to unlock even after sleep.
Case 2
I can use it without problems until you sleep or lock after powering on from power off.
However, after locking with sleep or power button, the screen lights, but you can not swipe.
Initialization already done
Reinstalled ROM (Officiak MIUI, CM12 etc)
But it does not fix it
Well, this can be one of two issues:
1. Hardware issue, and a very weird one. Almost one-of-a-kind.
2. What MIUI version have you tried? 8.5.10 MIUI 8? You can also try MIUI 7 or the MIUI 9 beta. Try all of them and see if any of them works.
I tried these ROMs
I have not tried MIUI 7, but have any good signs to try?
miui official HMNote2Global_V8.5.1.0.LHMMIED
xiaomi.eu_multi_HMNote2_7.9.21_v9-5.0.zip
Thank you.
I tried these ROMs
I have not tried MIUI 7, but have any good signs to try?
miui official HMNote2Global_V8.5.1.0.LHMMIED
xiaomi.eu_multi_HMNote2_7.9.21_v9-5.0.zip
Thank you.
My Redmi Note 2 has the MIUI 8 8.5.1.0 and no problems here. For MIUI 7 you can try 7.3.3.0 and for MIUI 9 have you tried 7.9.15? If not try these ROM versions and report back.
I tried, but the result was Ng.
7.3.3.0 and 7.9.15
Since it is not a software problem (apparently), since when has this issue started appearing? I am suspecting this is a hardware issue. Say everything you know, I will try and understand.
Since returning from sleep in TWRP mode is no problem, I think that it is not a hardware problem.
Since returning from sleep in TWRP mode is no problem, I think that it is not a hardware problem.
The problem is that the screen stops responding after sleeping normally after starting normally.
You can use it without problems until the screen goes to sleep.
give up.
(´；ω；`)ｳｩｩ
same case like me
I have flashing rr 6.0 and cm 13.0 and so on based Android 6.0. But except dinolek lineage worked, other's lock screen touch not work sometimes. It's wired. I don't think it's hardware's issue
Exact same problemfor me too. It's not Touch panel problem. I ordered new Touch panel + LCD + frame replacement. After replace still same issue.
If the device goes to sleep -wake up, touch panel stop working.
After reboot phone works perfectly until it sleeps again.
Related
Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
chrriiiss said:
Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
Click to expand...
Click to collapse
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Addicted2xda said:
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Click to expand...
Click to collapse
Well I first experienced the issue running CM 10.1.
Since then I've relocked it and loaded the stock RUU where things got REALLY weird. The navigation keys still didn't work and soon nothing was really responsive. I can't even get past the unlock screen. The ring bounces when I touch it but it won't drag and unlock. So it's still detecting something, but it's not really responding at all. I can't even turn the thing off now as holding the power button down restarts the phone. what is this i don't even....
bump!
I need help with this and after extensive searching, I haven't found anyone else with this sort of problem.
I'm trying to install a ROM via TWRP but my capacitive and on screen navigation buttons don't do anything, so I'm stuck without a ROM at the moment.
Hello I have a 9100 international version, and this is not your usual 1-2 seconds lag on wake. My phone (well, my friend's) takes around 10 seconds to wake. Not exactly wake but for the display to show, because when I press the home key or power key, the soft keys light up and the phone vibrates to the touch, the screen is also responsive to touch while the screen is off.
All this started after I flashed paranoid android into it, but after trying multiple roms, the issue is exactly the same. I also flashed a pit file to repartition the phone to have more storage for apps and it worked. I mean the phone works flawlessly except for this particular issue of the screen not turning on fast enough, even though the touchscreen seems to be responsive.
Ill flash stock back to it and give it a try. In the meanwhile, any one else have had this issue?
Try Neatrom 6.4 is a stock based with more feautures and battery friendly. Yeah i faced this issue one time, in neatrom 6.4 i never have this issue.
Hey, i have a problem with my phone not being able to be waked up with pressing the hard key or dubbletapping on the screen. When i press the power button to wake it up, the soft-keys lights up, but not the screen. It stays completely dark. The only way for me to access my phone, is to force shutdown by holding down the powerbutton. It started like 2 days ago, but i thought; that won't be a problem. I'll just force a shutdown when it happens. But today i revived a phone call, but i wasn't able to pick up the phone, because my screen turned dark. Again softkeys turned on but not the screen.
Using a Oneplus One, with the latest CM12.1 nightlies (That might be the problem), rooted, twrp, and a bunch of xposed modules.
asge1210 said:
Hey, i have a problem with my phone not being able to be waked up with pressing the hard key or dubbletapping on the screen. When i press the power button to wake it up, the soft-keys lights up, but not the screen. It stays completely dark. The only way for me to access my phone, is to force shutdown by holding down the powerbutton. It started like 2 days ago, but i thought; that won't be a problem. I'll just force a shutdown when it happens. But today i revived a phone call, but i wasn't able to pick up the phone, because my screen turned dark. Again softkeys turned on but not the screen.
Using a Oneplus One, with the latest CM12.1 nightlies (That might be the problem), rooted, twrp, and a bunch of xposed modules.
Click to expand...
Click to collapse
Or maybe it is Xposed that causing the issue. Are you using the latest Xposed version (v75)? If yes, try to uninstall Xposed through recovery and check whether the issue still persists. Otherwise update to the latest Xposed version and check again.
If Xposed isn't the culprit, revert back to an older nightly version of CM12.1 which is known to work without issues and wait for a new nightly or - even better - a stable release.
Thread moved to proper forum
Problem solved
It seems like it was the xposed module "YouTube background play" that caused the problem. Simply disabling it, made my phone work as normal. Still don't see how a module for YouTube can cause so much damage..
Thanks for the help
-Asge1210
hi,
I have a Redmi Note 3 SE (kate) running lineageos 14.1 official. a while ago, the screen broke, so I ordered a new screen assembly and replaced the broken one with the new one. the screen works perfectly, but the digitiser doesn't... it _always_ works in TWRP, and seems to work when fresh flashing lineageos. after a reboot or update however, it stops working. when booting to recovery, it works perfectly, but not in lineageos.
has anybody got any idea what to try ? the assembly clearly is not broken, but I'm stumped. clean flashed multiple times, always with the same problems.
check that the flex of the screen is well connected
My screen is replaced too, try agni kernel it have option to fix replaced screen issue. But double tap to wake is gone, and sometimes after screen off, touchscreen doesnt work you must turn on/off the screen and it will work again
strawjerry said:
My screen is replaced too, try agni kernel it have option to fix replaced screen issue. But double tap to wake is gone, and sometimes after screen off, touchscreen doesnt work you must turn on/off the screen and it will work again
Click to expand...
Click to collapse
agni pure los n kernel fixed it for me, thanks !
I've bought this phone around february/march 2018. I've been using an LOS 15.1 unofficial rom last updated april/june which has been working perfectly, no problem besides no VoLTE but i don't mind this.
I booted the phone into recovery (longpressing power button, then selecting with touchscreen the "reset option". It turned and then couldn't select any button via touchscreen. The phone reseted itself by the first time and got into this! Now touchscreen don't work (so i can't turn it off -it just restart when I longpress for 5 secs the power button), can't unlock it because I set it to ask me the pin on every reboot..
As a sidenote, the phone fell of my desk like 2 months ago, and changed it's entire screen tile (the LED and the glass) for another one because the original one got shattered and made the device unusable. I'm thinking it's a malfunction of this module (or maybe something disconnected? Is this possible)
Anyway, tomorrow i'm going to ask the guy who changed it for help. BUT, is there any other possible fix guys? Or a hard keys combination to completely turn it off so I don't get more messages and save battery?
Thanks a lot!
Just flash stock MIUI via adb n it will work ?