My Tab is running stock HC 3.2, only rooted with CWM v5.x.
Couple days ago I'm experiencing that the device is rebooting randomly while it's in deep sleep.
Does any fix or patch for this, and can I check a log or something to find why does it do that?
Thanks in advance.
Maybe it's the famous "Sleep of Death" issue?
Check this out:
http://forum.xda-developers.com/showthread.php?t=1386785
I experienced this issue in stock HC. However, after flashing CM9 it stopped. Must be some bug in Samsung's firmware...
Try reflashing stock ROM and see if it helps!
Hope I've helped!
Leave flashing as a second option
air001 said:
My Tab is running stock HC 3.2, only rooted with CWM v5.x.
Couple days ago I'm experiencing that the device is rebooting randomly while it's in deep sleep.
Does any fix or patch for this, and can I check a log or something to find why does it do that?
Thanks in advance.
Click to expand...
Click to collapse
Try to Wipe/Clean data in recovery mode first, I used to have the same problem but with stock HC (plus some batteries issue), leave flashing as a second option. Just FYI, it seems that ICS rom doesn't have this bug so far, so you can try it if you want.
Related
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old
Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...
I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.
I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???
hi guys. i had upgraded to xxkpe from froyo about a month ago and the phone worked flawlessly. now i upgraded to xxkph and then xxkpm. on both i face kernel panic or the phone automatically shuts down and enters in a bootloop. usually occurs while i am not actively using the phone. and this happens less on the day of the flashing and more on the next day.. and i have to usually reflash on the third day. i am sorry to create a new discussion portal here as i posted for help everywhere but no one really helped. so this is for those who are facing problems like me as i read on several fora that people are facing these problems.
PLEASE help us guys. it's really impossible to use the phone trying to restart it every 10 minutes. please help.
also, i am usually on xxkpe or xxkph (rooted using cf root).. what is the procedure to rollback to the 19003ddxxxx version of froyo. i have downloaded it but i am not sure.
please reply to this post someone as many of us need your help.
thank you.
Please keep questions in the general/Q&A section. This isn't development related.
Sent from the MIUI powered 3d
hi, did you find any solution to this? facing the same issue
ss03101991 said:
hi guys. i had upgraded to xxkpe from froyo about a month ago and the phone worked flawlessly. now i upgraded to xxkph and then xxkpm. on both i face kernel panic or the phone automatically shuts down and enters in a bootloop. usually occurs while i am not actively using the phone. and this happens less on the day of the flashing and more on the next day.. and i have to usually reflash on the third day. i am sorry to create a new discussion portal here as i posted for help everywhere but no one really helped. so this is for those who are facing problems like me as i read on several fora that people are facing these problems.
PLEASE help us guys. it's really impossible to use the phone trying to restart it every 10 minutes. please help.
also, i am usually on xxkpe or xxkph (rooted using cf root).. what is the procedure to rollback to the 19003ddxxxx version of froyo. i have downloaded it but i am not sure.
please reply to this post someone as many of us need your help.
thank you.
Click to expand...
Click to collapse
which cf root are you using?if you're overclocked, that's the problem. try going back to the original specs kernel first before downgrading to froyo...
Hi, thanks for the reply
1) what is 'original specs kernel"?
2) I had earlier gone from stock froyo->XXKPE->DXKP9 rooted/deodexed. Then i faced random bootloops (with factory reset). So yesterday i flashed XXKPE again (twice) and did factory reset/cache wipe. Things worked fine till today afternoon - gotten 3 kernel panics recently - not used anything apart from normal phone.
Any ideas on this ? How to go back to stock froyo (im from india) from XXKPE in case i need to go to samsung customer care ?
spm123123 said:
Hi, thanks for the reply
1) what is 'original specs kernel"?
2) I had earlier gone from stock froyo->XXKPE->DXKP9 rooted/deodexed. Then i faced random bootloops (with factory reset). So yesterday i flashed XXKPE again (twice) and did factory reset/cache wipe. Things worked fine till today afternoon - gotten 3 kernel panics recently - not used anything apart from normal phone.
Any ideas on this ? How to go back to stock froyo (im from india) from XXKPE in case i need to go to samsung customer care ?
Click to expand...
Click to collapse
Download XKB3, flash using pit and then files. Afterwards flash DDKB2
any idea what could cause the random bootloops/restarts ?
a lot of people are facing this issue, as ive read on this forum and elsewhere; however, i cannot believe that firmware flashing could cause hardware failure.
after flashing to xxkpe, no bootloops - got 3 kernel panics - one of which was preceded by "USB storage removed unexpectedly". I formatted USB and SD card storage and no bootloops/kernel panics so far.
Hoping to get 2/3 days w/o bootloops/kernel panics. Running out of options though. Any ideas?
EDIT: other option would be to exchange for a new nexus s/galaxy s (shopkeeper won't know of the issues )
ss03101991 said:
hi guys. i had upgraded to xxkpe from froyo about a month ago and the phone worked flawlessly. now i upgraded to xxkph and then xxkpm. on both i face kernel panic or the phone automatically shuts down and enters in a bootloop. usually occurs while i am not actively using the phone. and this happens less on the day of the flashing and more on the next day.. and i have to usually reflash on the third day. i am sorry to create a new discussion portal here as i posted for help everywhere but no one really helped. so this is for those who are facing problems like me as i read on several fora that people are facing these problems.
PLEASE help us guys. it's really impossible to use the phone trying to restart it every 10 minutes. please help.
also, i am usually on xxkpe or xxkph (rooted using cf root).. what is the procedure to rollback to the 19003ddxxxx version of froyo. i have downloaded it but i am not sure.
please reply to this post someone as many of us need your help.
thank you.
Click to expand...
Click to collapse
do not waste time go to sumsung and get the phone replaced or the main board changed see this thread
http://forum.xda-developers.com/showthread.php?t=1324452
Urgent help requested
supergaijin said:
which cf root are you using?if you're overclocked, that's the problem. try going back to the original specs kernel first before downgrading to froyo...
Click to expand...
Click to collapse
I had earlier applied CF-ROOT (using ganeshbiyer's thread) on DXKP9 but faced issues so did a FULL reflash to XXKPE but have since been facing issues.
Once a full reflash (using 4 files) is done, the earlier CF-root/deodex related changes are wiped out, right? im currently on xxkpe but facing numerous kernel panics (preceded by USB storage unexpectedly removed) and plan to go back to stock froyo.
please advise? Also, what is 'original specs kernel' ?
spm123123 said:
I had earlier applied CF-ROOT (using ganeshbiyer's thread) on DXKP9 but faced issues so did a FULL reflash to XXKPE but have since been facing issues.
Once a full reflash (using 4 files) is done, the earlier CF-root/deodex related changes are wiped out, right? im currently on xxkpe but facing numerous kernel panics (preceded by USB storage unexpectedly removed) and plan to go back to stock froyo.
please advise? Also, what is 'original specs kernel' ?
Click to expand...
Click to collapse
original specs is stock, overclocked is not stock. since you're not saying you used an overclocked kernel, then the other things that have been suggested would be best to try to fix your issue
guys it was a manufacturing defect. got it repaired on warranty! the motherboard and the LCD were replaced.
flashed to XXKPE the day i got my phone back. no such issue. it's been 3 months!
ss03101991 said:
hi guys. i had upgraded to xxkpe from froyo about a month ago and the phone worked flawlessly. now i upgraded to xxkph and then xxkpm. on both i face kernel panic or the phone automatically shuts down and enters in a bootloop. usually occurs while i am not actively using the phone. and this happens less on the day of the flashing and more on the next day.. and i have to usually reflash on the third day. i am sorry to create a new discussion portal here as i posted for help everywhere but no one really helped. so this is for those who are facing problems like me as i read on several fora that people are facing these problems.
PLEASE help us guys. it's really impossible to use the phone trying to restart it every 10 minutes. please help.
also, i am usually on xxkpe or xxkph (rooted using cf root).. what is the procedure to rollback to the 19003ddxxxx version of froyo. i have downloaded it but i am not sure.
please reply to this post someone as many of us need your help.
thank you.
Click to expand...
Click to collapse
im facing same problem pls let me know if u get solution for this problem
Hello,
Is anyone used the latest firmware from ASUS (9.2.1.21) and did it resolve the random reboot and screen flickering issue with TF101 ?
I'm asking above question because of following reason...
I have rooted TF101 running on ICS (revolver ROM), after i updated from Honeycomb i have an issue of random restart as my tablet randomly shuts down and gets stuck on ASUS start screen and i have to cold boot it at least once a day.
Since i had this problem i guessed problem is due to stock ICS so i installed custom ICS on my tablet but the problem never went away (before anyone can say anything, i have tried all ROMs available on XDA).
ASUS just few days back released a new firmware update (9.2.1.21), so i was wondering whether issue is still there or not as now i'm thinking of reverting back to stock ROM and hoping this random reboot issue might get resolved..
If anyone has any idea i will be greatful to you as i'm fed up with these bugs of late...
udupa82 said:
Hello,
Is anyone used the latest firmware from ASUS (9.2.1.21) and did it resolve the random reboot and screen flickering issue with TF101 ?
I'm asking above question because of following reason...
I have rooted TF101 running on ICS (revolver ROM), after i updated from Honeycomb i have an issue of random restart as my tablet randomly shuts down and gets stuck on ASUS start screen and i have to cold boot it at least once a day.
Since i had this problem i guessed problem is due to stock ICS so i installed custom ICS on my tablet but the problem never went away (before anyone can say anything, i have tried all ROMs available on XDA).
ASUS just few days back released a new firmware update (9.2.1.21), so i was wondering whether issue is still there or not as now i'm thinking of reverting back to stock ROM and hoping this random reboot issue might get resolved..
If anyone has any idea i will be greatful to you as i'm fed up with these bugs of late...
Click to expand...
Click to collapse
No, the latest update did not fix the RR's or the SOD. (I never had screen flickers?) .. anyhow, you can still use wakelock, but your battery drain will suck. Asus = #FailingAgain
jprattnu said:
No, the latest update did not fix the RR's or the SOD. (I never had screen flickers?) .. anyhow, you can still use wakelock, but your battery drain will suck. Asus = #FailingAgain
Click to expand...
Click to collapse
thanks for the info.... Asus has two important products to take care of and they cannot.... stupidest part is its a stock ICS with no skin.... Says a lot about Asus support...
G'day everyone,
I have searched the forums all around for someone with a similar issue but am coming up with no relevant information.
Basically my issue is that my phone will randomly restart at really random intervals and sometimes continually restart and also other times will just restart once in the day. I have tried re flashing ViperXL without any apps and the stock kernal installed to try and trouble shoot the issue but it still seems to want to restart every now and then. I have had this crazy thought the other day that my phone only seems to restart when I am at home and also trying to connect to my WiFi network??
I have also tried other roms and for the most part the Paranoid Android rom and CM10 stock seem to run fairly well albeit with the occasional restart.
Can anyone shed some light on some things I should try to work through the problem and to solve it, I understand the basic principles of rooting and using adb but have not delved that far into the rabbit hole. :silly:
Anyway if anyone could help that would be greatly appreciated!
Cheers Skete
P.S Sorry if I have made a major error posting in here, just this was my first post and felt like I was running out of options
Try this:
Goto Settings->WiFi(Click the word, not the toggle)->Menu->Advanced
Change option "Keep Wi-Fi on during sleep" to "Always"
That worked for me. I've seen this problem before on other phones I've had. This was a real problem for MIUI back in version 1.
Theoretically, your battery life would suffer, but I have not experienced a battery life change. ViperXL battery is pretty great.
I had these reboots with the kernel that comes with ViperXL. This setting fixed the problem. I have since changed kernels to BeastMode. I left the setting on "Always" and I do not get reboots. Not sure if its an issue in BeastMode, but why change it if it works.
- Joel
phattychops said:
Try this:
Goto Settings->WiFi(Click the word, not the toggle)->Menu->Advanced
Change option "Keep Wi-Fi on during sleep" to "Always"
That worked for me. I've seen this problem before on other phones I've had. This was a real problem for MIUI back in version 1.
Theoretically, your battery life would suffer, but I have not experienced a battery life change. ViperXL battery is pretty great.
I had these reboots with the kernel that comes with ViperXL. This setting fixed the problem. I have since changed kernels to BeastMode. I left the setting on "Always" and I do not get reboots. Not sure if its an issue in BeastMode, but why change it if it works.
- Joel
Click to expand...
Click to collapse
All he has to do is flash a new kernel. Beastmode v4.2 or elemental. Never used the WiFi always setting.
Just go flash a kernel for sense ROMs and you'll be fixed. Don't have to kill your battery.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
I'm a newbie that recently rooted the At&t One X on 2.20 firmware. I have twrp recovery 2.3.1 flashed and installed ViperXL 2.1.2 rom. After a few days I noticed that when I turn off wifi and attempt to turn it back on, it will not turn on and display an error. When I reboot, the phone would hang on a white screen until I force a shut down with the power and volume button. Once I turn the phone back on, it boots back into viper and the wifi works as normal.
When I just keep the wifi turned on and move to different locations where I have a wifi hotspot saved, the phone will occasionally reboot.
Is this a kernel issue? If so, is there one preferred with ViperXL 2.1.2?
Still rebooting
Hello!
I have those random reboots on ViperXL 3.1.0 when phone is locked, I don't touch it. What must I do to not rebooting?
R1peR said:
Hello!
I have those random reboots on ViperXL 3.1.0 when phone is locked, I don't touch it. What must I do to not rebooting?
Click to expand...
Click to collapse
From what I remember there is a wifi firmware update zip that fixed the random reboots for the sense jellybean ROMs. It should be posted in the ViperXL thread.
Sent from my HTC One XL using xda premium
PatriotXT92 said:
From what I remember there is a wifi firmware update zip that fixed the random reboots for the sense jellybean ROMs. It should be posted in the ViperXL thread.
Click to expand...
Click to collapse
While installation goes, it wrote that Wi-Fi fix installing with ROM. Thanks, I will flash it one more time independenlty. Mb It will help
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Switch to the teameos ROM. It's much more stable.
Sent from my Galaxy Nexus using Tapatalk 2
AnthraX- said:
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Click to expand...
Click to collapse
I have noticed this on my tab too. usually when i turn it back on the battery is at 49-50% each time. Maybe it's a setting? Or maybe it's just some weird malfunction.
AnthraX- said:
Hello everyone, I am having a problem with my tf101 running cyanogen mod 10 (4.1.2). When I leave it inactive for about 30min it will just randomly shutdown. I have had cyanogen 10 on the tablet for about 2 days before this started happening and it was running perfect then. If anyone has an answer for this problem it would be appreciated.
Click to expand...
Click to collapse
Try going to the development page and download the newest nightly. Make sure there is not another zip inside the zip you download. You will get SN error if you do. Put it on the root of an sdcard (microsd), place it into the transformer, and boot up clockwork mod and select "install update.zip" or whatever it is. Hope this helps! It worked for me. You should not have to a factory restore. Only do that if it will not boot up. BEFORE YPU DO ANYTHING MAKE A BACKUP IN CWM! Restore if needed. Also clear cache and dalvik cache.
Good luck,
Jake
I've found that most roms since ICS have this problem. I think its the SoD (sleep of death issue).
I'm currently running Rayman's CM10 V6 which I haven't updated for a while and that still has the issue.
You can fix it by using "wakelock" from the store, but you will loose some battery life overall as it keeps the CPU active.
I need to spend some time updating my stuff, but apart from SoD the rom I'm using works great..