Database Info

Plants vs zombies - Not playable on ics

Playing on ics on my phone is doable, but the tab won't play at all. Worked barely under hc as it was, but hw acceleration or software both freeze up. Stock or arhd. Anyone else play this and having the same problem?
Sent from my Transformer TF101 using xda premium

I have the same problem, got for free from Amazon. It worked flawlessly on HC for me but not even booting up on ICS.

Worked until I reset the device
It worked okay for me upon first start-up after upgrading to ICS on my Transformer. Since I had to do a reset to factory so I would stop getting the FC's on my google media, no go. It will get to the yard screen of level one then freeze. That happened once. The rest of the time it stops around the hour glass.

having the same problem ...

I played though the first 3 levels w/o problems.
I guess PopCap needs to repackage the game for ICS.

I have some problem

Am running stock rooted 9.2.1.17 ICS. Played 5 hours today without problem with my daughter. File I have is named "plants_vs_zombies_hd_android.apk" I used CWM to install pre-rooted 9.2.1.11 and then used CWM again to flash 9.2.1.17 update. Don't know why others are having so much trouble.

Amazon vs HD
I think this is exactly the problem. The Amazon (as they say in "the Scene") "crap non-working fake" version has finally fallen over completely with ICS. OTOH, the HD version (there is one, and it's completely different) works great on ICS (9.2.1.17). I'm running it now.
theremix said:
I have the same problem, got for free from Amazon. It worked flawlessly on HC for me but not even booting up on ICS.
Click to expand...
Click to collapse
33colburn said:
Am running stock rooted 9.2.1.17 ICS. Played 5 hours today without problem with my daughter. File I have is named "plants_vs_zombies_hd_android.apk" I used CWM to install pre-rooted 9.2.1.11 and then used CWM again to flash 9.2.1.17 update. Don't know why others are having so much trouble.
Click to expand...
Click to collapse

[Q] (Help) Which ICS ROM to choose??

So I've been using Revolver for a few months...
And I saw these new ROMs and I was wondering if they are worthy to switch from Revolver...
(IF anybody tried these ROMs PLEASE post your opinion)
These are the ROMs:
[ROM] CM9 with Cornerstone
[ROM][Nightly][ICS] Team Eos Transformer Nightlies (tf101)
[ROM][ICS] Codename Android v1.5.0
Plus.. I want "Cornerstone" and Revolver doesn't have it!
Thanks in advance...

If you haven't updated to the new revolver 4 then you are still on honeycomb.
And cornerstone is a gimmick right now, it breaks a lot of features and apps don't always run correctly in the cornerstone windows..I will be surprised at this point if cornerstone survives onto android 5.0, google and Onskreen seem to be at odds over it's usefulness and how to implement it into ROMs without breaking market access to keep users from leaving negative feedback for 'broken apps' that don't work simply because they have cornerstone installed. I have a feeling cornerstone is either about to die, or be neutered beyond usability, they have already removed features and hinting at removing more to make it compliant to Google's standards. In other words, enjoy cornerstone, but I wouldn't get dependent on it, it may not be around (at least in the same form it is now) for very long.

luna_c666 said:
If you haven't updated to the new revolver 4 then you are still on honeycomb.
And cornerstone is a gimmick right now, it breaks a lot of features and apps don't always run correctly in the cornerstone windows..I will be surprised at this point if cornerstone survives onto android 5.0, google and Onskreen seem to be at odds over it's usefulness and how to implement it into ROMs without breaking market access to keep users from leaving negative feedback for 'broken apps' that don't work simply because they have cornerstone installed. I have a feeling cornerstone is either about to die, or be neutered beyond usability, they have already removed features and hinting at removing more to make it compliant to Google's standards. In other words, enjoy cornerstone, but I wouldn't get dependent on it, it may not be around (at least in the same form it is now) for very long.
Click to expand...
Click to collapse
No, I'm using Revolver 4
Good to know about that!
I wanted to try those ROMs for myself but it's really troublesome wiping everything then restoring again! which I did twice to get ICS to work! and I still have random shutdowns!
So I wanted to ask if anyone tried them... and how are they compared to the Revolver!

Do a backup of your apps and data, then do a nandroid backup through recovery. If you are currently on HC and then you upgrade to ICS, you will need to make sure that you can go back to your previous HC rom if need be by having a nandroid backup and a way to flash the corresponding HC kernel. The safest way to do this is to perform the nandroid restore through recovery, do not reboot, after restore, then reflash your HC rom's zip file. If you do not have a TF that has sbk1 and can use the nvflash utility, then you run a risk of hard bricking your tf when u try to go back to HC. So the safest bet is to stick with ICS once u upgrade.
Do a full wipe and download and try every rom you are interested in and try them out yourself. Perform the above recovery steps if you want to go back.

cavsoldier19d said:
Do a backup of your apps and data, then do a nandroid backup through recovery. If you are currently on HC and then you upgrade to ICS, you will need to make sure that you can go back to your previous HC rom if need be by having a nandroid backup and a way to flash the corresponding HC kernel. The safest way to do this is to perform the nandroid restore through recovery, do not reboot, after restore, then reflash your HC rom's zip file. If you do not have a TF that has sbk1 and can use the nvflash utility, then you run a risk of hard bricking your tf when u try to go back to HC. So the safest bet is to stick with ICS once u upgrade.
Do a full wipe and download and try every rom you are interested in and try them out yourself. Perform the above recovery steps if you want to go back.
Click to expand...
Click to collapse
I'm on ICS!
I've already backed up everything from TB but It does take a very long time to restore! (250+ Apps)
And to test the ROM properly I have to restore my data and use the ROM for couple of days!
BUT If somebody already tried one of those ROMs then I don't have to do all of that...

Hi,
I am also have a problem with Asus Base ROM as well.
So I change from Revolution HD to EOS nighlies with Cornerstone version 4.
Overall is great, it's very fast. However, I still have some problem of random not-wake up and battery drain after restart.
It may be my individual problems but just for your consideration.

ROM to use
There is always going to be some sort of wok when you are trying out different ROMs.... Somewhat nature of the beast.
I have run revolution HD and codename 1.5 so far and prefer codename at this point. Codename is still being upgraded quite often... So maybe more work than revolution.
According to other threads, these random reboots will probably be in every tf101 ICS rom as they are due to old nvidia drivers delivered by asus.

I know what you mean i have a 12kb/s internet connection and downloading roms to try is a pain. I was on revolver 3 and very happy stable fast and reliable. Upgraded to revolver 4 and had to many small problems and it all seemed a little tired and slow. Tried cornerstone and thought nah! Whats the big deal, cant change window position and half the apps dont work. I am now on codename 1.5 and although their are a few little problems it hasn't reebooted got stuck in a loop or slowed to a crawl. Loads of extra settings and the inbuilt launcher is great. So far impressed and will be sticking with it.

Ok thanks to everyone!
I guess I'm gonna be testing out "Codname" later...
Although I'm still waiting for the Official CM9 to come out!

+1 for codename android
there is the best 3d power for me.
Sent from my Xperia X8

[Q] Does rooting & custom rom help speed up the TF??

I got my tablet a week ago, it started off decent, but after a few days with several apps installed and nothing removed it started to slow down, crash apps constantly, and frozen screen till I hold power button to force power down. So I wanna know if it will help speed it up and not cause all these issues. Overall its a wonderful tablet just those issues are a major inconvenience for my school app University of Phoenix.
Also with this being new fresh out of the box. Would the hardware inside cause any issues with Rooting. I had that issue once before on the HTC Evo Shift back in August where I just got it on the new update that would brick if i tried to root.

Yes custom roms generally improve speed and no there is no brick update Vipermod works for the latest firmware without issue

ok thank you very much! Im just concerned about rooting this one. I like it as is except those frequent crashes and the horrible slow speed.

rooting, not so much, but custom ROMs really have a huge impact, and custom kernels allow overclocking, which REALLY speeds your device up. More than anything, simply replacing your kernel with one that can be overclocked will increase your speed..compared to the speed increase gained from this the custom ROM speed increase is fairly small.

luna_c666 said:
rooting, not so much, but custom ROMs really have a huge impact, and custom kernels allow overclocking, which REALLY speeds your device up. More than anything, simply replacing your kernel with one that can be overclocked will increase your speed..compared to the speed increase gained from this the custom ROM speed increase is fairly small.
Click to expand...
Click to collapse
ok well thank you. Which is the most stable OC kernal and best rom to go with it. I need something highly stable for school, but at the same time enough to at least open some games... i cant even play angry birds at the momment.... kinda pathetic. it opens be crashes after every lvl.

kyhassen said:
ok well thank you. Which is the most stable OC kernal and best rom to go with it. I need something highly stable for school, but at the same time enough to at least open some games... i cant even play angry birds at the momment.... kinda pathetic. it opens be crashes after every lvl.
Click to expand...
Click to collapse
Thats not normal... Most stable in my opinion is revolution hd with blades kernel

The new o/c kernel made from roaches sources has been the best for me so far and when frozn is released it will be good with regular updates but revolver has always been pretty good to
Things are changing quickly at the moment so now is not the best time to find a rock solid custom set up or say a certain set up is best
Sent from my Transformer TF101 using XDA Premium HD app

I think most OC kernels are in testing phase right now?
But they should be pretty much stable unless you are overclocking to maximum frequency.
You don't really need to OC for normal usage, including playing games like Angry Birds. If it's not working, it's for reasons other than the CPU's speed.
I would recommend CM9 for ROM. http://forum.xda-developers.com/showthread.php?t=1525148
It benchmarked really high compared to other ROMs and is really stable.

mrevankyle said:
Thats not normal... Most stable in my opinion is revolution hd with blades kernel
Click to expand...
Click to collapse
no its not. so i thought i would root it to see if i can FIX this issue. usually works that way some times. i do know that it worked fine when i got my tablet. i avoided the stupid update but it annoyed me enough so i did it. thats when this started happening.

did you factory reset before updating?

Angry birds has been crashing for me too, I think it's a problem with the app or Asus' ICS ROM, I just installed it clean so no factory reset needed. Also, agree with Danzano, not the best time to upgrade considering a new update just dropped and introduced tons of new issues and things to do..unfortunately Honeycomb was in a much later phase of 'stable', but ICS is just so sweet lol. I think it's stable ENOUGH for me..a reboot every now and then doesn't keep me from using it.

horndroid said:
did you factory reset before updating?
Click to expand...
Click to collapse
no i didnt.

kyhassen said:
I got my tablet a week ago, it started off decent, but after a few days with several apps installed and nothing removed it started to slow down, crash apps constantly, and frozen screen till I hold power button to force power down. So I wanna know if it will help speed it up and not cause all these issues. Overall its a wonderful tablet just those issues are a major inconvenience for my school app University of Phoenix.
Also with this being new fresh out of the box. Would the hardware inside cause any issues with Rooting. I had that issue once before on the HTC Evo Shift back in August where I just got it on the new update that would brick if i tried to root.
Click to expand...
Click to collapse
Rooting is just elevated privileges and won't necessarily speed or slow anything. A custom ROM, on the other hand, can speed things up with various tweaks and customizations. Most custom ROMs require root, for privileges.

kyhassen said:
no i didnt.
Click to expand...
Click to collapse
You probably should have.
If you want to fix things right now, flash a good custom AOSP rom like CM9. Make sure to do all the needed data wipes in CWM before flashing.
Only thing you will be missing from stock Asus rom is a few apps and widgets made by Asus. What you will gain is MUCH MUCH more.

Ok well thanks for the info. But which rooting method should i use on the newest update???

kyhassen said:
Ok well thanks for the info. But which rooting method should i use on the newest update???
Click to expand...
Click to collapse
1. You root with this. http://forum.xda-developers.com/showthread.php?t=1427125
2. Once you have root, you install CWM with this app http://forum.xda-developers.com/showthread.php?t=1346180 It will install a fairly recent version of CWM that still works.
3. Optional: If you want to update your CWM to the latest version, you flash this: http://forum.xda-developers.com/showthread.php?t=1213723
4. Use CWM to flash whatever ROM you want.

horndroid said:
1. You root with this. http://forum.xda-developers.com/showthread.php?t=1427125
2. Once you have root, you install CWM with this app http://forum.xda-developers.com/showthread.php?t=1346180 It will install a fairly recent version of CWM that still works.
3. Optional: If you want to update your CWM to the latest version, you flash this: http://forum.xda-developers.com/showthread.php?t=1213723
4. Use CWM to flash whatever ROM you want.
Click to expand...
Click to collapse
Sweet, thank you very much!!

Very unreliable TF101 and confused

Hi,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.

1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)

15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.

As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.

Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.

rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.

Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.

NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?

Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.

Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!

Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !

It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.

So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.

Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.

Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/

It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.

Megatron is really stable, I've found. I like aosp better too.

Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app

Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?

You'll want to RMA to ASUS if nothing works :/

Q. EOS4 shuts down on sleep

So I installed Team Eos4 nightly build 94 with kat kernel 80b and it is great so far with only a couple odd things. Has anyone trying this had their device turn off when it it should just be sleeping? Mine will shut off if the screen goes dark for more than just a few minutes. Thanks.
Edit: i messed up. I was on the stock kernel, not kk 80b. I must have flashed the kernel first before the rom. Idiot i am. Anywho, other than that i followed all protocol set up by the developers. Am using rogue recovery. Just flashed Kat kernel 80b now, so I'll see what happens. Thanks for the replies.

What recovery are you using?
Did you wipe the caches, system and do a factory reset in recovery before flashing?

OK, it is still happening. I'm running rogue xm recovery 1.5.0 which claims to be a cwm 5 based recovery.
Same issue. If the pad sleeps for more than minute or so-- haven't done an official time-it will basicly turn itself off. Need to long press the power button to turn back on and it goes through the regular boot process. I don't think this is some sort of deep sleep mode, but not really sure.
Sent from my Transformer TF101 using Tapatalk HD

I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.

frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
Thank you for your help. I guess afterward it would be necessary to go through the whole process of wiping and flashing again?
Sent from my Transformer TF101 using Tapatalk HD

I would highly recommend it.

Update: interesting experiences yesterday with the rom. Was doing fine with me at work when there was no WiFi access, but once back home it would sometimes do its little sleeping trick. I decided to wipe and re flash the room and then the kernel, but it is still happening. Will try a full factory reset and flash again.
Sent from my Transformer TF101 using Tapatalk HD

I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???

Shesakillatwo said:
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Click to expand...
Click to collapse
Been messing around with things.. This issue only happens when unplugged from charger. I installed wake lock to see if that would do anything. It seems to eliminate the problem but then you have battery drain. This reminds me of an issue that occured to some people after the ICS update.
Sent from my Transformer TF101 using Tapatalk HD

frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium

just lou said:
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD

wekurtz74 said:
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
I upgraded from B143 to 93 last night just before going to bed, left the tablet on all night, and again this morning had to do the long power button hold to get the tablet booted. A minor inconvenience when stacked up against the gains the ROM gives me. Guess we'll wait for the next version and see how that goes...............
---------- Post added at 09:31 AM ---------- Previous post was at 09:21 AM ----------
One other thing I noticed in the Dev Threads. If I understood correctly, some builds are appear to be done with "Linaro toolchain", and some not. I do not even know what "Linaro toolchain" is, but if some use this and some do not, could this possibly be a reason I have issues with some builds and not others. Sorry in advance if this is a stupid question???

Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.

wekurtz74 said:
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
Click to expand...
Click to collapse
As an FYI, I have downloaded and installed B145 and will let you know how it goes. To add to my input here, everytime I upgrade/flash:
1. I do a Cache wipe
2. I do a Dalvik Wipe
3. I flash the ROM
4. Flash the 80B Kernel
5. I flash the GAPPS
6. I again do both a Cache and a Dalvik Wipe
7. I reboot.........
I also have the TWRP Flash script/app installed.

So, I attached my dock last night for the first time since I rooted and moved to the 4.2 ROM to check out the Battery changes for the Dock. They worked well and the ROM continues to be awesome. On going to bed, I left the dock attached and all started up fine this morning. Since having the dock attached is adding another variable, I will disconnect it before going to bed tonight and provide an update tomrrow.

Short update. Left my unit on all night and responded perfectly this morning when I tried to wake it up. B145 with the v3 Battery patch seems to be working Great!!!!!

After Several days I can report that B145 with the v3 Battery patch seems to be working perfectly for me.

Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...

landous said:
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
Click to expand...
Click to collapse
try the 92 kernel also and preview 150.
scott

wn1ytw said:
try the 92 kernel also and preview 150.
scott
Click to expand...
Click to collapse
I am heading this way.. will let you know how it goes.. as I have had most of the problems described in this thread over the last few days..