I've been experiencing for some time now some random freezes when trying to face-unlock the phone. When pushing the power button to wake the phone, it displays the unlock screen but the box in the screen where your face (or whatever the front camera catches) blacks out, while the rest of the screen is normal (I can see the clock, the notification bar and the emergency call), also the leds for back and menu light up. And the phone justs stays like that, all the leds lighted up and the screen on. The home button doesn't work and the power button only works if I hold it down (it powers down / restarts the phone).
This has happened to my phone from some time ago, its purely random and it always happens when I try to unlock the phone. I haven't had any issues while using the phone nor strange bootloops or sudden reboots. I'm currently on stock XXEMB5 with Speedmod Kernel k2-13 and some apps removed, mainly yahoo widgets and some Samsung apps (I think I just removed all the hubs: game hub, social hub, etc...).
I red the bad eMMs symptoms, but it doesn't seem to be the same. If I had to guess, I would say its something with the camera, but right now I don't know for sure... Anyone has any idea where could be the problem?
Favourite culprit would be a non-standard kernel, wipe the phone and return to fully stock to test.
Your collection of mods and custom changes to rom are probably unique, if it doesn't freeze when stock then add changes one at a time until it happens again.
Related
I can't remember which rom I'm on (probably the one in my signature, can't remember if I updated it since then lol), but I've been having this issue for a little while now, but sometimes (can't quite figure out what triggers it) I lock my phone and my screen won't turn back on when I hit the lock/power button to turn it back on. Also sometimes I go to lock my phone and the screen will turn off then immediately back on, showing the lock screen. I love everything about the rom except this bug. I don't want to have to pull the battery constantly and it's getting very annoying. I do know I'm on 3.6, but can't remember which rom I'm on. Please help!
Flash different rom? If it sticks on another rom, it's a hardware issue, and you should get it replaced by Verizon
I had this same exact problem I posted about a while back. I linked it to my use of turboprop. Everytime i hit the on button the backlight would turn on but the ui would never come up. Reflash your rom and not turbo after a good wipe. my problem got fixed.
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
What app are you using that is supposed to wake your phone? Just my opinion but it sounds like an issue with the app.
PS. Crt off animation was introduced well before ics.
ThomasBags said:
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
Click to expand...
Click to collapse
Try turning off CRT in system setting / ROM Control / General UI / uncheck CRT off animation. I have it off and never have a problem in AOKP
This guy probably didn't wipe everything before posting. Yes this includes your data.
Sent from my MB860 using Tapatalk 2
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
(I posted on the wrong location first time, sorry)
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
For a week or two now,* I have been having some funny things happen with my Redmi Note 4 (Qualcomm, Global) phone.
Before that it had gotten water in it and basically shut down entirely, but they fixed it and got it up and running. When I picked it up they showed me watermarks on the screen, saying that the screen had frozen only once but that it may just be lagging.
Since then I have had a few symptoms of an issues, perhaps hardware issues, but potentially something that I can fix without paying more for parts.
Here are the things that happen:
- Music stops suddenly (screen on or off) and the music app has to be reopened (DoubleTwist, Miuiu's Music app, etc); Somes while in Doubletwist, if I click to visit home screen (square button) than the music stops. (this is the first issue that I noticed).
- 1-2 seconds of white screen before already-open apps appear after selected; Sometimes problems with apps loading or screen goes black when loading
- When closing apps or returning to home screen, it looks like the desktop(?) background comes up and then a second after is is re-populated with icons as if system is refreshing the home screen
- Once any of these issues begins, it usually worsens and the cell phone gets slower, behaving more and more strangely until not even useful to me; Reboot clears it right up for an hour or two or whenever this wierd stuff starts to happen again
-It seems like if I make a point of using the phone modestly, slowly, I can avoid these issues from starting up
- Sometimes reboot rometimes hangs on initial black loading screen
- Sometimes if I hit the power button to turn off the display, I can not turn it back on with that button (neither does the battery-dead orange light flash), so I have to reboot.
-When I turn the phone screen off while it has been working fine, I come back later, turn on the screen to find that it is now on the boot logo screen and it stays until I hard-reset the phone.
So, these are potential issues I have guessed at:
* Screen damaged? So far, other than watermarking at the top and some backlight bleed, sensistivity is perfect on the phone, and symptoms involving screen always seem to be triggered more by apps or pressing buttons.
* Apps or Android corrupted/internal memory damaged? I backed up via Settings and did a Hard/Factory Reset, then restored from backup. I still have the problems.
* RAM partially damaged? I test RAM with two apps and none of them showed issues. Namely my available RAM and used RAM reported always add up to the 4GB my phone has.
*Other Hardware Components failing? I used 3 apps to check all of the hardware devices and sensors that I could think of. Vibration is the only thing that does not work, and honestly, I don't care much about vibration.
Today I have suspected that settings may being at fault, and/or battery savers turning off my audio. Battery savers often identify my music apps as using "excessive amounts of power," perhaps because the speakers at involved, but it does make me think... I removed any battery-related and security apps, then turned off all battery saver options in settings earlier today. In 2 hours of music listening after that, I have not had any shutdowns, but I am not convinced I have solved the problems. In the weeks after this, the issue is back and the audio issue is always followed by the phone operating very sluggishly.
I have done a factory reset and restore, and the issue persists. Do you think there's any point in trying to do a clean reflashing of MIUI? Could it be a software issue or definitely hardware?
What advice can you give me?
Thank you for reading.
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Lazy_Pickachu said:
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Click to expand...
Click to collapse
Miui 9 does not have safe mode to boot in.