I have been running EOS4 on my TF101 for a while, and I decided to try the Kat kernal to see if it can improve performance. I flashed it through CWM right after I did a Nandroid backup. Now all of a sudden my battery won't charge. If the device is plugged in, the upper right indicator shows charging, but the lock screen and battery section of the settings page show not charging. And if I have the unit plugged in and running, it will lose charge. If I plug it in and shut it down, it will pick up maybe 30% overnight. I also tried a recovery through Nandroid backup, but it left the kernel and my problem stayed. I assume Nandroid backup doesn't effect the kernel. For the record, the kernel I used was Tim_KatKernel_103_JB4.2_Lidpatch. I have the most recent EOS4. I believe it's 114. Any help would be appreciated.
I can't believe there is not a single response to this issue. That does lead me to believe that this is not a common problem with the Kat kernel, and just maybe it's a coincidence that this occurred when I updated the kernel. Maybe I'm just having issues with the 5/15v charger. I have one on order and we'll see if that fixes it. I'm also curious if Nandroid backup is supposed to back up the kernel.
Sent from my Transformer TF101 using xda app-developers app
hambcastle said:
I can't believe there is not a single response to this issue. That does lead me to believe that this is not a common problem with the Kat kernel, and just maybe it's a coincidence that this occurred when I updated the kernel. Maybe I'm just having issues with the 5/15v charger. I have one on order and we'll see if that fixes it. I'm also curious if Nandroid backup is supposed to back up the kernel.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I believe the newer versions of cwm backup the custom kernel in the nandroid.
Sent from my SGH-T999 using Tapatalk 2
Related
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
burgerearmuffs said:
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
Click to expand...
Click to collapse
I did have this, about once or twice per day with 1.4.4. After I updated to Tiamat ROM 1.0, I have had no spontaneous reboots.
Sent from my Xoom using XDA Premium App
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
burgerearmuffs said:
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
Click to expand...
Click to collapse
Sorry, I have no idea.
Sent from my Xoom using XDA Premium App
Hello everybody. I've done absolutely everything I can think of to fix this issue and I'm not having any luck.
My wifi just won't turn on anymore. It constantly says "turning on", but won't actually turn on. Please help.
Sent from my DROIDX using Tapatalk
I did a factory reset and there still is no wifi showing up. Its almost like the wifi hardware just completely died.
I'm trying to do the eraseData truck outlined in this thread. Haven't quite figured it out yet tho.
http://forum.xda-developers.com/archive/index.php/t-1093818.html
Sent from my DROIDX using Tapatalk
I had the same problem when i tried to restore a backup. I saw that thread too...but I think in my case...the backup was not complete (cwm f'd up?). Anyway...I just did a fresh install of the ROM that i use, cause that was faster than trying to search for a fix.
Swyped from my Nexus One
I've been trying a fresh revolver install as well, but it keeps putting me in a bootloop. The only thing that even boots is my backup. I'm downloading the revolution super wiper and revolution and see if I have better luck with that.
Sent from my DROIDX using Tapatalk
Hey, just so everyone knows, the problem I had was that the Clockwork Recovery wipe was not complete. Make sure to use Revolution wiper prior to flashing a new ROM. I did that and everything is working fine now.
Sent from my Transformer TF101 using Tapatalk
Is it possible that you may have changed kernels and then restored a nandroid backup from earlier? Cause it sounds like you have a mismatch between you kernel and the installed wifi module.
I would try re-flashing your kernel. This willreplace the wifi module and should fix the problem.
I have flashed Revolver 4 by Gnufabio 4.0.0 Beta 1.3.1 recently and I've had no problems with it for the last 4 days. However, I locked the screen today and somehow my transformer turned off. When I try to turn it back on it shows a low battery logo for a second and shuts off. (it's fully charged) I can't access recovery and since my tranformer is a SBK2 model, I can't flash it again with Nvflash. Should I wait till the battery drain and attempt to get in recovery? What should I do? Am I screwed? Does anyone have this similar problem?
one
one
two
rticphreeze said:
one
Click to expand...
Click to collapse
two
I don't think you can flash a stock ROM through cwm.... Go back to stock(unroot) using nvflash/easy flash method and once you have a untooted tf101 go back to rooting if you like to....
Sent from my Transformer TF101 using xda app-developers app
To start I'm not sure if this is the right place to post considering I can't post on the development thread yet.
So I was running the quickwiz 1.0.3 rom and i flashed the dag kernel and accidentally did a data wipe, so I then restored it to a previous backup. Now there are random times where my phone will lock the screen and it won't turn back on. I've tried doing fix permissions in rom manager and cwm. I tried reflashing the same rom via cwm, and the issue still sticks. I have yet to try Odin and don't really want to. Any ideas?
Sent from my SAMSUNG-SGH-I727 using XDA
To add on, the only fix I have for now is to remove the battery and manually reboot. Everytime I do this the battery will drop from anywhere to 5% - 20% sometimes the battery will slowly rise up again.
Sent from my SAMSUNG-SGH-I727 using XDA
If you are running da_g kernel, it has sleep of death issues
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
alright, so im going to flash to faux kernel and then report back. thanks!
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
stanleyopar2000 said:
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
Click to expand...
Click to collapse
What build was your Synergy ROM? I've had difficulties with any ROM after about 3/23 due to some problems with the whole 3.4 thing. I'm not familiar with the Synergy ROM (obviously I've heard of it, but I don't like the stock "feel") and the problems that I've encountered have been on AOKP and CM based ROMS. But you may want to try flashing an earlier build. I went back to a build of the ROM I use from 3/13 and the problems I had that were similar to the ones you described stopped.
I've been running synergy for months now, and with almost all of their different releases. I have never had random reboots like that though. If you are using r420, or pretty much any of the newer releases, make sure you are doing a full wipe and not restoring any app data. That's the only way to make sure it isn't the ROM causing it. If it's still a problem, use that manufacturer warranty
Sent from my SCH-I535 using xda app-developers app
SynergyROM is awesome agreed. I had similar problems at one point due to my voltage settings. Not all phones are created equal. Increased voltage and changed governor to 'on demand' because 'interactive x' had problems at the moment.
Some have just flashed a different kernel but imo ziggy is a genius and I will rock his kernel as long as he makes one.
The issue is one one of the builds ziggy and I think phones with rev4 couldn't handle the low volt
The blue light blinks or stays on for a bit like when booting.?
Clearly..... It your phone does it on a stock kernel,
I highly doubt the software is causing it.
It sounds like somewhere across the line you have a hardware issue.
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
I'm having the exact same problem with the latest AOKP and CM10.1. I reverted back to an older version to see if this fixes the problem.
stanleyopar2000 said:
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
reslor1 said:
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
Click to expand...
Click to collapse
+1. Also, Odin will not up your flash counter unless your flashing something that isn't stock......Odin as the last step will leave you at out of box stock.
Sent back the phone. Hope for the best
Sent from my SCH-I535 using xda premium
Amazon apologized and she got overnight a 32gb s3 for the same price as the 16. This new one has no sleep issues
Sent from my SCH-I535 using xda app-developers app