For some roms like Havoc OS and Resurrection Remix, I'm occasionally getting deep freeze issues. Blank screen and no reeponse until I hard reboot through power button. Anybody face this issue?
+
aowe94 said:
+
Click to expand...
Click to collapse
I noticed that it's a fingerprint mismatch issue. Device when given fp, sometimes can't decide whether to open or not, it simply hangs...
Try to register fingerprint perfectly once again, might solve the issue.
I (curtana) have the exact issue with multiple AOSP roms and I still can't find any solutions.
Related
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
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.
Greetings,
Does anyone have this issue? Phone wakes up when fingerprint reader is touched (with any finger) even when it's not set up? Is there any workaround?
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
katoda_ltd said:
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
Click to expand...
Click to collapse
That happens to me as well if I have a fingerprint set up.
But if there is absolutely no fingerprint is set up, the phone still wakes up whenever the scanner is touched.
To see if you have this issue, delete all your fingerprints from your f1, turn off the display and touch the fingerprint sensor and see what happens.
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
katoda_ltd said:
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
Click to expand...
Click to collapse
It's not a big issue. I was just wondering if it's only a problem with my specific unit.
If its a software issue probably get fixed with updates or maybe a different rom.
You never know if it's a bug or a feature
katoda_ltd said:
You never know if it's a bug or a feature
Click to expand...
Click to collapse
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Rowdyy Ronnie said:
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Click to expand...
Click to collapse
Do you also have this bug?
Windoors said:
Do you also have this bug?
Click to expand...
Click to collapse
Nope I don't have any such issue on miui beta 9.4.26
I would suggest you to do a factory reset if you continue to have this issue.
My phone came with oreo, it had this issue.
Now using 10.3.4 stable (prerooted) the issue persists.
Haven't tried lineageos.
This is a software feature from miui, my mi max used to also light up when no fingerprint is registered. It can be turned off somewhere in settings iirc.
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
srahman53171618 said:
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
Click to expand...
Click to collapse
Well, if you accidentally touch it phone will wake up without you knowing. It can happen while its in your pocket.
Anyone using non-MIUI rom, do you also have this problem?
Hi all,
I keep running into the same issue on different roms.
When i wake up the device, double tap to wake or the power button, sometimes the screen comes on black with no further. I lock and unlock the device and it doesn't move onto the lock-screen. All i see is the notification bar on LOS17.1, the rest of the screen is black.
I have to hard reset it, and then the device comes back on normally until the issue re-occurs.
Anyone have any idea what kind of hardware issue this is?
Thanks
w1ll1m said:
Hi all,
I keep running into the same issue on different roms.
When i wake up the device, double tap to wake or the power button, sometimes the screen comes on black with no further. I lock and unlock the device and it doesn't move onto the lock-screen. All i see is the notification bar on LOS17.1, the rest of the screen is black.
I have to hard reset it, and then the device comes back on normally until the issue re-occurs.
Anyone have any idea what kind of hardware issue this is?
Thanks
Click to expand...
Click to collapse
Disable Double tap to sleep on lockscreen and check if it happens.
Yes, this bug is in several or probably all Android 10 based ROMs.
Try turning of pocket detection and see if that solves this issue for you.
I am using Havoc OS 3.4, i have kept turn off pocket detection and it does happens to me once or twice in a day or two and that to if i use device heavily with multiple apps.
This bug could be solved but the problem is that bug/crash report is not getting created when black screen occurs and hence it became difficult to resolve.
Black_Stark said:
Disable Double tap to sleep on lockscreen and check if it happens.
Click to expand...
Click to collapse
metelhammer said:
Yes, this bug is in several or probably all Android 10 based ROMs.
Try turning of pocket detection and see if that solves this issue for you.
I am using Havoc OS 3.4, i have kept turn off pocket detection and it does happens to me once or twice in a day or two and that to if i use device heavily with multiple apps.
This bug could be solved but the problem is that bug/crash report is not getting created when black screen occurs and hence it became difficult to resolve.
Click to expand...
Click to collapse
Hey guys,
Just to let you know, i disabled double tap to sleep and pocket detection and i haven't ran into the issue once.
This solved it.
Cheers
i have been experiencing touch failure on bottom screen just above navigation buttons like a straight row in my moto g5 plus. which makes me like unable to give a space between when i'm texting. But sometimes it works for a couple of seconds and goes off. And sometimes the whole screen become unresponsive too and then i have to lock the phone and open again one to three times to make i work. currently it is running on pixel experience+ A10 rom. Is this issue occur because of i installed a custom rom. somewhere i saw that pixel experience have some touch failure issues like the users have to lock the phone and open it again just as i do. if it is a software prob maybe i can solve it by flashing the stock rom again . i'm a complete noob i need some serious help!
yamin mathew said:
i have been experiencing touch failure on bottom screen just above navigation buttons like a straight row in my moto g5 plus. which makes me like unable to give a space between when i'm texting. But sometimes it works for a couple of seconds and goes off. And sometimes the whole screen become unresponsive too and then i have to lock the phone and open again one to three times to make i work. currently it is running on pixel experience+ A10 rom. Is this issue occur because of i installed a custom rom. somewhere i saw that pixel experience have some touch failure issues like the users have to lock the phone and open it again just as i do. if it is a software prob maybe i can solve it by flashing the stock rom again . i'm a complete noob i need some serious help!
Click to expand...
Click to collapse
This one?
https://forum.xda-developers.com/g5-plus/development/rom-pixel-experience-t3995717
In the g5 plus forum
https://forum.xda-developers.com/g5-plus
Sent from my ocean using XDA Labs