I have the weirdest thing on my new Tab 10.1 Wifi. All goes well with the tab, until I put it into the Samsung Keyboard dock. It locks up, at unpredictable intervals (from a few minutes to a few hours), and I need to press the on/off button for 10 seconds to turn it on again. I thought it was the keyboard, but the same behaviour on the new one.
Anybody out there with a similar experience / solution?
Related
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.
Hello, I come from a Nokia 5800 and this behavior was common in CFWs, but I can't find anything similar on android yet.
What I mean is, android's behavior is something like this:
- 30 seconds go by and the screen dims.
- 5 seconds more and screen turns off.
- 2 seconds more and lockscreen kicks in.
- If you want to use the phone now, you must press power or home button.
In Nokia 5800, it was something like this, and what I'm looking on android:
- 30 seconds go by and screen dims.
- 5 seconds more and screen turns off.
- xx seconds more and lockscreen kicks in. Also (this is the important part!) if you tap the screen at this point while the screen is off, it turns on back again! Kinda like when its dim and you touch it and it lights up again. Same behavior but with screen off!
My question is, Is there some way to replicate this behavior on android?
Thanks.
Anyone else having slow wakeup response times? For instance when my alarm goes off in the morning i have to slide it off twice because the first time isn't recognized.
I find this sometimes happens when pressing the power button to bring up the lock screen, that's slow sometimes too...
Is there a remedy for this?
Sent from my Samsung Galaxy Note™
ZPaul2Fresh8 said:
Anyone else having slow wakeup response times? For instance when my alarm goes off in the morning i have to slide it off twice because the first time isn't recognized.
I find this sometimes happens when pressing the power button to bring up the lock screen, that's slow sometimes too...
Is there a remedy for this?
Sent from my Samsung Galaxy Note™
Click to expand...
Click to collapse
I have the same thing. It's happening on every rom I have tried so far (5 or 6? different ones). Seems to be something with the deeper sleep mode maybe? If I rapidly turn the screen on and off again it's fast. If it sits with the screen off for more than five or so seconds it then takes the longer wake up time.
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.
Hello people,
I've noticed a weird problem with my Samsung S2 running Gingerbread 2.3.5 (yes, I know, it's old... but the last time I've upgraded to anything more recent, the battery lasted less than one day. I'll happily receive any advices on newer versions tho).
let me tell the story:
the phone is "quiet", with the screen black.
...a message arrives! (doesn't really matter if it's an SMS, Telegram, WhatsApp or anything else. Even notes will be affected, everything needing a keyboard input)
I press the power button, the phone "wakes up" and shows me the lock screen - I've set a static image with the time in the upper area.
so the phone starts running and I go to the desired application (sms/telegram/notes/etc...)
the keyboard (swype keyboard, but is the same also with my other 2 keyboards) shows up.
I try to input letters, words, but nothing gets written. If I press longer to get to the special character selection, I can't select any of them, all I can do is touching the Back button and return to the keyboard.
I usually press a key from time to time to see when the keyboard starts working.
After a delay of ~15 seconds it starts working, but I have to be careful not to let the phone going back to sleep or I will have to endure the delay again (this usually happens during a chat and it's quite annoying).
so, I suspect there is some application that gets stuck after waking up from the lock screen, but does anyone have experienced this? Any ideas on what it could be?
Thanks!
Best Regards
Max