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
Related
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device.
In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang.
If the lock screen is hanging, pressing power will:
(a) sometimes make the phone sleep again
(b) make the phone screen kind of glitch/blip and then it takes input again
(c) does nothing and the screen remains on and hung/frozen
Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu).
Now - I think this could be an app, but not sure.
When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo.
I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly.
I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app.
Other apps I have installed/running:
Swiftkey X
3G watchdog
Dolphin Browser HD
ES File Explorer
Winamp (locks without this running or running at all in lock screen mode, so that is not the issue)
Real Calc
Google Drive
Facebook
Alarm Clock Xtreme
It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period.
Thoughts?
So others may try to help or identify the possible cause / fix .......
What is your firmware version?
Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9.
But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us.
Facebook
3G watchdog
Dolphin Browser HD --i never use
Google Drive
a fix that worked for me
Steps to the solution that worked for me (so far) were to uninstall:
1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway)
2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3.
I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though.
I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings.
While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems.
Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer".
It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy.
LOOOL
Actually...
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around....
It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking.
Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said:
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
Click to expand...
Click to collapse
Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good..
This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said:
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
Click to expand...
Click to collapse
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
It worked!!
douglasurbano said:
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
Click to expand...
Click to collapse
This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
Click to expand...
Click to collapse
Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings.
Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?
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...
Currently, my phone is coming across as useless other than as a torch. I am trying to turn on the screen of my phone, although nothing at all happens. Sometimes, if I'm lucky, it turns on and shows me my home screen background, however it takes so long to load that the screen goes back off again. I think this problem is due to an XPosed module in Sense Toolbox 6 that I enabled, that allows you to turn on the torch by long-pressing on the power button, however I am really not sure. Another likely possibility is a lag issue from the high amount of apps I'm running. At the moment I am considering restoring one of my backups because the problem is so bad (If I can get it to turn off, that is). Please help me!
falseascension said:
Currently, my phone is coming across as useless other than as a torch. I am trying to turn on the screen of my phone, although nothing at all happens. Sometimes, if I'm lucky, it turns on and shows me my home screen background, however it takes so long to load that the screen goes back off again. I think this problem is due to an XPosed module in Sense Toolbox 6 that I enabled, that allows you to turn on the torch by long-pressing on the power button, however I am really not sure. Another likely possibility is a lag issue from the high amount of apps I'm running. At the moment I am considering restoring one of my backups because the problem is so bad (If I can get it to turn off, that is). Please help me!
Click to expand...
Click to collapse
As long as you have ADB enabled you should be able to connect it to you pc via ADB and type "adb reboot recovery" this will reboot you straight to recovery where you can restore your backup or disable Xposed framework see link here https://seo-michael.co.uk/how-to-disable-xposed-installer/ for howto . I think you can even disable certain modules via ADB then "adb reboot" but I can't remember the detail you would have to google it.
MiniBlu
i can feel the vibration and hear it turn on but i cant see whats on my screen
I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.
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?