Hi,
I apologise if this has been asked before but I did a search and have found no solution that works.
From yesterday my Nokia has had an issue with the display dim and timeout. When the phone is first switched on it works fine and dims and locks within the set time (30 seconds) once I start using the phone say I send a text, put the phone down it just stays unlocked and does not dim. Also, if I press the power button to lock the screen it does not go black it locks the screen but stays lit (like when pressing power to see the time when locked) I have updated the software, this did not fix the issue. I restored back to before the update. I've also gone to settings>about> reset phone (I've actually done this several times) but the issue is still there!! Do I assume there is a fault on the phone now or am I missing some simple solution?!? It is driving me mad as it was fine. I'm in Cyprus so I'm not sure how easy it is to take to a service centre. Any ideas please?
Thanks in advance
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 got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
geiswiz said:
I got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
Click to expand...
Click to collapse
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
kirbo20 said:
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
Click to expand...
Click to collapse
Hmm, I did turn off the wifi power save mode using *#0011* because of wifi disconnect issues. I went in and turned it back on and rebooted the phone. I'll see if I still get the screen lock issue.
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
Hi all,
I have a Samsung Galaxy S3 GT-I9305T rooted and running Android 4.3 with Touchwizz.
The problem I am having is that the screen will not turn off and pressing the power button will not lock the phone. Holding the power button will bring up the device options menu (power off, restart etc) indicating that the button itself is still functioning.
Restarting the device will boot to the lock screen, however the screen still wont turn off and after unlocking the phone once, you can no longer lock the phone.
In the phones settings, under battery it shows that it doesn't even register the screen as being on or the phone being awake (see image) however the phone is still completely functional aside from the issues stated above.
This problem occurred after accidentally dialling emergency services from the lock screen while watching a video on my computer and absent mindedly spinning my phone in my fingers. As soon as I saw it was dialling I cancelled the call and took the battery out. When I started the phone I noticed the screen wouldn't turn off and the phone wouldn't lock.
Hoping I wont have to do a factory reset, if anyone has any ideas or suggestions, they'd be greatly appreciated.
Thanks
Have same problem with my Alcatel Onetouch Fierce 2. Fairly certain it's from this Kingroot in my case. However I don't know enough to prove this. I started using apps to lock the screen for me but they started not working as well.
Dear friends, see this, see in the youtube:
watch?v=ixWozCI8sek
I activated the phone in their own settings of android to show screen touches and strokes that you can see in the video above, and installed YAMTT app to better show the problem.
The Problem on mobile touch in the middle of the screen there is a track that is not recognized touch, but if I press the screen sinking, she returns to work temporarily, and now recognizes the touch - but after a few minutes the problem back and touch is not recognized again.
The screen is perhaps dished up, and when I press down her back to be in contact with the part of the cell that recognizes the touch, but with time the screen should be getting back dished up (this is my guess, not i'm sure).
Detail, not always when I press is running, sometimes I press the screen to the center of the touch again be recognized, but it seems that the phone is registering touches alone.
What would be a solution, and change the screen (it does not mean that changing the screen the problem solved), want to try other alternatives before changing the screen.
Perhaps heating up the screen with hot air, in theory it will expand and become more pliable, and then if I press down the center panel of the phone with something for a while until it cools, in theory the screen would remain indefinitely, and if that is the problem could solve -
Anyone have any thoughts, has been there?
Thanks in advanced!