I recently flashed the latest CM9 Nightly build for my LG E400 successfully. And just after few minutes of playing around with it, my phone freezes. The screen display is normal but my touches won't register. Pressing all the hardware controls won't work too. And the only way to fix this temporarily is by removing the battery and placing it again then long pressing the power button.
Please help me on what should I do.
jloLOLS said:
I recently flashed the latest CM9 Nightly build for my LG E400 successfully. And just after few minutes of playing around with it, my phone freezes. The screen display is normal but my touches won't register. Pressing all the hardware controls won't work too. And the only way to fix this temporarily is by removing the battery and placing it again then long pressing the power button.
Please help me on what should I do.
Click to expand...
Click to collapse
Nightlies may have many bugs.If you want bug free ROM then go for stable releases..
Related
Is this only me to has this problem?
When I do screenshot by motion, it stuck at "saving screenshot..." most of the time.
Sometimes a reboot works. But after a few moments, the problem comes again.
Any way to solve this problem?
I'm currently using Omega V37.1 - XXELC.
Probably rom problem. Omega v40 is out, you might look at upgrading
Firmware issue I think. I too have had this happen. Pain in the butt.. But you can also take a screenshot by simultaneously pressing and holding your home+power button.
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.
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...
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
Firstly I wanted to clarify one thing that my phone worked okay after the update. I didn't realise it has updated until after a boot loop.
Just FYI The camera in my phone have been crashing randomly when taking pics and the pics weren't having the full resolution. It was 1280x720. This wasn't an issue for me and I ignored it for like 3-4 months.
So my redmi note 10 have had some random reboot issues lately which i didn't give much attention to. It wasn't frequent just rare random reboots. Few days back I noticed my phone rebooting while in use and it started to loop for a few times and when it loaded into lockscreen right after unlocking, the power button started to press automatically triggering the power option screen and then the emergency calls as well. It stopped after a few taps on the power button.
A day or two later it rebooted once again while the recorder was on and and this time it boot looped a few times and showed the lockscreen and crashed booting back once again. A few tries after that it booted up and I was able to use it for another day.
The very next day, it did the same. Started to boot and loop once again. But this time when the battery is sufficient enough or the phones cool and haven't been used for a while, it boots into lockscreen but freezes and crashes. At one occasion, it stayed just a few more seconds long enough to open the passcode screen but crashes before I could type anything. Then it loops once again and before even reaching the lockscreen, boots back into MI Android Powered screen right after the three dots blinking page. And randomly it boots into lockscreen as well. But once the battery is down or the phone is heated enough, it barely goes into lockscreen.
Booting into safe mode also shows the same. It sometimes boots into lockscreen but doesn't show the 'safe mode' text in the bottom.
Right now when I had kept my phone off for a while it booted into lockscreen twice and the screen dims immediately before freezing and crashing.
The third time it just went back to the MI Android powered logo right after the three dots blinking screen.
Guys please let me know do you think this is a hardware issue or a corrupt software update?
I know software update issue can cause bootloop but does it reach till the lockscreen? My phone consistently gets into the lockscreen when the battery is sufficient or the phones cool enough.
What last update did you perform?
carlos974 said:
What last update did you perform?
Click to expand...
Click to collapse
MIUI 14 which i didn't even realise until I checked the settings app one day after a boot issue
What version do you have?
For me see screenshot, works fine!
Backup your data and clean flash with Mi Flash Tool, you can then exclude any software problem
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Dheerajvirgo said:
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Click to expand...
Click to collapse
May I know how did you fixed the issue? I'm stock with same situation as you. Did you change any hardware?
Hey, my mi 10 5g has similar symptoms - random restarts + random switch on power button without pressing it...
all this came after upgrade from miui 13 to 14..I use this phone for 1,5 yr with no problems...
Phone get hotter also...
Is it related to bug?