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.
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?
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Hi, so sorry for the vague thread title, but really, there's no other way to describe it. So here's what happened.
For the past few weeks (or month), my Xperia Ray has had a problem of switching on after it was put into standby mode, i.e. after i pressed the lock button. The screen would light up, however would remain blank. So all I would get is a bright black screen.
I could have lived with this for a few more months (until Xperia Z gets released in my country D: ) however this problem started getting worse. At first, after pressing the home button, the volume rockers and/or the lock button for about 20 times, the screen would turn on (finally). Despite it giving me that bright black screen, i could still operate the screen. I could still try to unlock it because of the haptic feedback on my lockscreen. I could still change music tracks on my music widget on my lockscreen. In short, the screen worked perfectly, only that it kinda wouldn't show. However, for the past week, the only way to turn it back on would be to do a battery pull and switch on the phone again. And it recently developed a problem of giving me that bright black screen again when I switch it on, causing me to do about 5 battery pulls before being able to actually use my phone again.
I did get fed up with this problem, being a heavy user of my phone. Therefore, today I decided to try to do a factory reset of my phone, intending to wipe the dalvik cache + clear all user data, thinking it might help my bright black screen problem. However, I found that I couldn't boot into recovery because all my phone would do was to give me that bright black screen again! So after many battery pulls, I managed to boot up my phone normally and do a factory reset under the backup & restore tab in settings. Of course, the phone tried to reboot itself, but of course, just gave me the bright black screen.
I kinda gave up at this point, and did many battery pulls and boots, however, all I got was either
1. the terrible bright black screen
or less frequently
2. the free xperia project logo then the terrible bright black screen.
I did get very fed up, so I plugged it into a wall socket to charge it. However, since about an hour or two ago, I realised it may be on bootloop. When I plug it into a wall socket, the free xperia project logo shows up and then an even brighter black screen shows up for about 3-5 minutes, then those two repeat endlessly. The notification light doesn't show that it's charging at all.
Okay here's background info on my phone.
- Is rooted
- Bootloader is unlocked
- CM 9.1 is installed
- Was running GO Launcher (if that helps)
- had a custom boot animation
- I think i deleted an apk for the google start up configuration thing...the one that asks if you have any google accounts you want to connect when you switch on your phone for the first time. I'll search up the correct apk name if you need it.
- Is about a year old (got it last early April)
- is a Sony Ericsson Xperia Ray (in case you didn't notice haha)
- battery level was about 20%+ when I did a factory reset (terrible of me I know)
- I have tried to caliberate the battery a few months ago
That's all the background info I can think you need. Please do let me know if you need any other info. If you need the logcat text of what happens when I hit the lock button at the top of my phone and the phone gives me the bright black screen (the early stages of this problem), let me know and I'll dig it up. I think I've bricked it, but I can't boot it into recovery so I can't do anything. And I did all I could google for the bright black screen problem which I won't tire you by specifying here. Please do help me. It seems as if the worst of evils has befallen my phone. Now I'm stuck here with my phone crazily on bootloop beside me. Please please do help.
Flash stock rom
Just try flashing a stock rom with Flashtool. If the problem persists, then it could be a hardware problem. Flashing a stock ftf takes care of all software issues. Get the stock ics FTF file and place it in firmwares folder of flashtool. Start flashtool and select flash mode. Then choose your ftf and press ok. Then wait until it prompts you to connect your phone. Then, just turn off your phone, while holding the power button down attach the USB cable. The LED notification should turn green and wait until it finishes flashing.
flash extended stock kernel and then the stock ftf firmware file...
hit thanks if i helped u
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Benlux1 said:
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Click to expand...
Click to collapse
Hi, if your phone can still be switched on and hasn't progressed so far in being destroyed, you could try downloading the Disable Auto Brightness app for Xperia phones from the Play Store. I've read somewhere that the screen might not turn on because of the auto brightness. I'm not sure if it actually helps, but perhaps my phone would have died faster without it. I've read of people changing their battery, doing battery calibrations or changing their screen to fix the problem. But before you change the hardware, I suggest that you check the hardware first. If the Disable Auto Brightness doesn't work, do a Nandroid backup and store the backup somewhere safe. Then flash the stock firmware to your phone and try to get it to switch on. Do flash the firmware before your phone runs out of battery because you never know, your phone may decide to refuse to charge your battery anytime. Then try to switch it on. If your phone goes into a bootloop (like mine now) really consider getting a new phone or sending it for repair or try all day to fix it if you use your phone alot. I'm still trying to fix mine.
I flashed the original firmware for my phone, tried to turn it on, was very happy when I saw the original Xperia logo, but then I realised it was on bootloop. When I tried to charge it, it immediately turns on and goes into bootloop again. Logcat doesn't detect my phone, so I can't obtain the logcat of what's happening. I haven't tried to replace the battery of my phone because I couldn't find a supplier. But I'll go on trying to fix my phone until the day that it really breaks down. Good luck with yours and keep us posted.
Sent from my MT25i using xda app-developers app
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.
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.