Anyone else experiencing their 10.1 retail Tab having the screen come on randomly and stay on? Every so the screen comes on, but it's black. I can tell because of the backlighting being on. I have to reboot to make it stop.
spokenjeremy said:
Anyone else experiencing their 10.1 retail Tab having the screen come on randomly and stay on? Every so the screen comes on, but it's black. I can tell because of the backlighting being on. I have to reboot to make it stop.
Click to expand...
Click to collapse
That has something to do with background apps making it "wake" up
I think a more important problem is the Tab either turning off on its own or having the "sleep of death" even on Android 3.1. I just experienced both of these but the one that scares me more is the "sleep of death" because in order for you to turn it back on, you have to plug it into a power source, hit the power button once until the battery gauge appears then hit it again, and this time hold it down until the Galaxy Tab 10.1 logo appears. Then it boots into Android like it should. this is the first time its done it for me, and its only been two weeks since i got it.
Hopefully Samsung's upcoming TouchWiz UX update will include fixes for this and maybe a dash of Android 3.2
Yes. I have exactly the same symptoms. Every few days, my Galaxy Tab 10.1 (v3.1) will turn on the backlight (but with a black screen). Sometimes it is on battery, and other times it is being charged. Either way, I cannot wake the tablet and have to hold down the power button until it resets. Then, the first time it tries to reboot, it displays a DOS-like error message and I have to reset it again. Then typically it boots up fine. I really don't like these symptoms. Any help in fixing it would be very appreciated.
Related
For some reason my screen quickly turns itself off when I awake it from stand by. It's like 3 or 4 seconds and then the screen will turn off, I can normally get around it by quickly pressing a button and this will keep the screen on.
It's also not a constant problem, after a soft reset the problem seems to go away for a random period of time and then return.
Any one else experience similar?
aLlamaWithARifle said:
For some reason my screen quickly turns itself off when I awake it from stand by. It's like 3 or 4 seconds and then the screen will turn off, I can normally get around it by quickly pressing a button and this will keep the screen on.
It's also not a constant problem, after a soft reset the problem seems to go away for a random period of time and then return.
Any one else experience similar?
Click to expand...
Click to collapse
Just go to Sound and Display --> Backlight --> Set it for longer.
gaarry said:
Just go to Sound and Display --> Backlight --> Set it for longer.
Click to expand...
Click to collapse
That doesn't work mainly cause there isn't an option to turn the backlight off after 3 seconds
sorry, wrong tab selected
pls delete.
When I leave my galaxy player 5 (international) plugged during the night the screen wakes up at some point which forces me to leave it with the screen down (when I remember), I would guess that happens when the battery full notification comes up.
That anoys me specially because sometimes the screen doesn't seem to follow the screen timeout settings and stays always on. It used to happen in stock froyo and still happens in eryigit gingerbread rom.
Does that happen to anyone else? Any tips?
I have the US version and when it finishes charging the screen stays on for about 3 minutes before turning off (I actually waited to see what would happen). I think it's a bug because my default settings is a minute. Try using different timeouts to see if that solves anything.
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.
Hi, so, I have my SGS3 for almost a week now. Using Omega v27 and enjoying every second of it.
One thing bothers me (besides the dialer ) - it takes the phone a good 2 seconds to turn on when i press the power button. I'm not talking about restarting itself. I'm talking when the phone is on, there is no app running, and i lock it. Clicking the power button should bring up the unlock screen, but it takes a whooping 2 seconds for it to turn on.
On my previous Galaxy Mini, it was instant.
Is there any way to fix it?
Egozy said:
Hi, so, I have my SGS3 for almost a week now. Using Omega v27 and enjoying every second of it.
One thing bothers me (besides the dialer ) - it takes the phone a good 2 seconds to turn on when i press the power button. I'm not talking about restarting itself. I'm talking when the phone is on, there is no app running, and i lock it. Clicking the power button should bring up the unlock screen, but it takes a whooping 2 seconds for it to turn on.
On my previous Galaxy Mini, it was instant.
Is there any way to fix it?
Click to expand...
Click to collapse
I have the same problem on every S3 i have ever used in my hands.
Its called "wake up lag"... 1.5-2s - its normal and I hate this so much!!!
It´s the time samsung need to wake up modem and so on after going to deep sleep (5s after switching off). You can download some software tools to prevent deep sleep, but its not battery friendly...
Its not a software problem - its a hardware problem - No... its a Samsung problem.
xbpv060 said:
I have the same problem on every S3 i have ever used in my hands.
Its called "wake up lag"... 1.5-2s - its normal and I hate this so much!!!
It´s the time samsung need to wake up modem and so on after going to deep sleep (5s after switching off). You can download some software tools to prevent deep sleep, but its not battery friendly...
Its not a software problem - its a hardware problem - No... its a Samsung problem.
Click to expand...
Click to collapse
I have never had that problem. I really have no solution apart from a wipe but it definitely seems a issue as I have never faced it.
Sent from my GT-I9300
This is not a problem.
It was there in my S2 after ICS update.
It is present in S3 also and it takes a second before lock screen appears after pressing power or home key.
you have to live with this.
It's Samsung's 'wakeup lag' that seems to appear in every one of their Android phones.
No way to get rid of it other than to flash AOSP/AOKP roms I believe.
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