Database Users

JT's Pure Gingerbread from Twitter

Just installed, but no gapps and no recovery or reboot option, just shutdown.
So far sensors seem to work- rotation, proximity is a little slow after pulling away from face
Call volume is much improved
GPS turns on, have not been able to get outside to test for satellite lock yet
Wireless will not turn on - no foce close, just wont enable
Data works - downloading New Market to try and bump gapps install ( no PC available for adb at the moment)
Will post details in a bit

MMS sends, have not received reply yet
Still unable to install gapps, any ideas?
Very fast and very vanilla

Ha, I'm stuck at work too! Really looking forward to seeing how it runs. I'm sure you can flash the gapps package jt has in his CM7 thread. And if your drivers are set up on your pc you should be able to adb reboot recovery.... hopefully.

Did you ask JT if you could post the link here? You think there might be a reason he is only posting on twitter and not here?

nunyazz said:
Did you ask JT if you could post the link here? You think there might be a reason he is only posting on twitter and not here?
Click to expand...
Click to collapse
Oops, did not think about that. Will remove link until I hear back...

No lock on GPS
Received MMS
Very nice so far, but restoring back to CM7 until I can get to a PC with adb to install gapps

Is there a way to get to the new recovery? Not the three finger salute one that is

AuroEdge said:
Is there a way to get to the new recovery? Not the three finger salute one that is
Click to expand...
Click to collapse
Since it is vanilla Gingerbread, the only option to recovery is three finger, although I did not try to install ROM Manager, so it may work to boot straight into recovery.
I odin'd the cw4 from Jt's CM7 post, but still got errors about not being able to mount /system, so I guess there are still file system differences between CM7, Gingerbread, and Froyo.
I had to odin back to stock, flash CM7, then restore my backup.
With the limited time I played with it, it performed spectacularly aside from the previously mentioned issues.
Once I can get gapps and a working recovery installed it could easily be a daily driver for me.

AuroEdge said:
Is there a way to get to the new recovery? Not the three finger salute one that is
Click to expand...
Click to collapse
If you have JT's .zip file for installing CM7, when you tell CWM (red) to Install Zip from SD card, and choose the CM7 zip, it will auto-reboot you into CWM blue.
from there you can easily flash any of the new CM7 roms, including MIUI, OMFGB, and of course the CM7 zip that got you into the blue recovery in the first place.
Also, put JT's gapps .zip file onto your SD card and flash with thew new CWM after you have installed the rom. shouldn't need adb to install that.

I noticed yesterday that his release has Dev Tools which includes the Terminal Emulator. So I ended up just rebooting that way

AuroEdge said:
I noticed yesterday that his release has Dev Tools which includes the Terminal Emulator. So I ended up just rebooting that way
Click to expand...
Click to collapse
reboot recovery?
Did not think about that, I am going to re-flash it later this afternoon from scratch to try some GPS fixes also...

Does anyone know if this project is still being worked on? I haven't seen any mention of it from JT since the original tweet.
I would like to use this as a daily-driver if it's stable enough.

AOSP Gingerbread isn't really a project, it's plain Gingerbread as Google released it. Not really a whole lot to work on after it's Fascinate ready.

lukusb83 said:
Does anyone know if this project is still being worked on? I haven't seen any mention of it from JT since the original tweet.
I would like to use this as a daily-driver if it's stable enough.
Click to expand...
Click to collapse
Check here:
http://forum.xda-developers.com/showthread.php?t=1195355
Everything seems to work so far...GPS, MMS, data, wifi, sensors, etc

JTs vanilla GB is very light and very fast. This is GB as Android intended it to be. Nothing more than an OS really. No FB contact integration, appears no video or does not play avi, video recorder without 720p record.

He has released a second version and added a few things.

CM9 on Nook Color is frustrating me

I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
How did you install it? To SD or internal memory. And which version of CM9 are you using? Opengl or non-opengl?
If you installed to internal memory, did you factory reset via CWM first? You need to if coming from stock. You can still do it now.
If you installed to SD, what class SD card are you using? It should be a Sandisk class 4.

Your download isn't broken. CM9 on the NC is - it isn't really *done* yet on the Nook Color. Developers are working on it, but for now your best bet is CM7.2. I expect we might hear an announcement very soon, but for now, use CM7.2.

It's obvious that the installation of this person has problems.
CM9 DOESNT have this kind of problems. It might be a bit slower in hardware acceleration matters in comparison to CM7, but it sure works fine in all other matters.
It's quite mature by now.
Produced by NookColor at ICS AOKP 4.0.4

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
What did you download?
Edit: Forget it. LeapinLar already asked all the pertinent questions.

I'm having similar issues as well. It's kind of sluggish and it has frozen a few times already. I downloaded the nightly by Eyeballer over at Techerrata: cm-9-encore-20120904-0700-unofficial.zip.
In the instructions over at Androidforums does say that it might be sluggish the first few days so I guess I will just have to wait it out. I did just install about roughly 12 hours ago.

I just installed today, over my CM7.2 install in internal memory. It seemed okay at first, though a bit sluggish. But then I re-booted it and now it is acting possessed. Apps are launching by themselves (Play Store, a notepad app I had installed, voice command window, etc.) Very odd. I've shut it down and re-booted, same thing. I am thinking of maybe doing a complete fresh install from a SD card, wiping out all my apps from 7.2 and see if that helps at all. Or, I made a backup of my 7.2 install from CWM before installing CM9, so can always go back to that.

Just to follow up on my previous post: My NC running CM9 (latest GL version) did stabilize quite a bit after a day or so. But it still is very sluggish at times, to respond to screen touches, opening apps, and even loading webpages. I ran the Quadrant benchmark tool and the results are slightly lower than I got with CM7.2, but not terribly so. I'm debating whether to go back to 7.2, or do a factory reset and try a fresh install of CM9 and see if that's any better? Is there any evidence that a fresh install will work better than updating over a installed 7.2?

It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD

RASTAVIPER said:
It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wow, that made a world of difference! Thanks. I thought I'd read somewhere else that it was okay to update from CM7 to CM9.

[FIX] Auto rotate and accelerometer bricked on JB roms

Hello! I have been observing for the past few weeks how the accelerometer on my device stopped working after i flashed a jellybean rom. The curious thing is that if i installed any other rom (sense or non-sense ICS or GB) my accelerometer started working perfectly.
So i followed a few recomendations from other users who told me to use Aahk and return to full stock then re-root flash recovery and flash jb rom.
I did that and guess what everything was fine until today when i switched from a sense 4 rom back to jb and the problem with auto rotate was back.
I am not a dev but something in the sense 4 rom is killing the accelerometer for any/all jb roms flashed afterwards ( yes i have wiped everything 3x even with ARHD superwipe script)
And now the good part, i was experimenting today to see how i could get back accelerometer functionality without going through aahk re-stock procedure and i found a way:
1. Download this stock rooted rom: http://forum.xda-developers.com/showthread.php?t=1382235
2. Put it on your sd card , reboot in recovery , wipe everything except sd card (obviously) and install it
3. Let it boot at least once, go through initial setup, reboot recovery wipe everything, and now you are ready to flash jb with working auto rotate
P.S. to reboot in recovery with stock rooted rom you have more options ( no advanced power menu)
1, From adb : adb reboot recovery
2. Download quick boot from playstore ----> https://play.google.com/store/search?q=quick+boot&c=apps
3. Pull battery out then put it back in keep volume down and power buttons pressed until you enter bootloader from here navigate to recovery and you are done.
I hope i am right. I had but only one dhd to test.

don't work for me :s
have test with this stock rom (full) and super stock rom 3.20 from inspire 4G thread;
i have a DHD.
with hboot 0.85 it work (before have hboot 2.0 from aahk)

there are 2 files with no extensions, how do I flash it ?

tripleR123 said:
there are 2 files with no extensions, how do I flash it ?
Click to expand...
Click to collapse
extract with 7zip

bondocel said:
Hello! I have been observing for the past few weeks how the accelerometer on my device stopped working after i flashed a jellybean rom. The curious thing is that if i installed any other rom (sense or non-sense ICS or GB) my accelerometer started working perfectly.
So i followed a few recomendations from other users who told me to use Aahk and return to full stock then re-root flash recovery and flash jb rom.
I did that and guess what everything was fine until today when i switched from a sense 4 rom back to jb and the problem with auto rotate was back.
I am not a dev but something in the sense 4 rom is killing the accelerometer for any/all jb roms flashed afterwards ( yes i have wiped everything 3x even with ARHD superwipe script)
And now the good part, i was experimenting today to see how i could get back accelerometer functionality without going through aahk re-stock procedure and i found a way:
1. Download this stock rooted rom: http://forum.xda-developers.com/showthread.php?t=1382235
2. Put it on your sd card , reboot in recovery , wipe everything except sd card (obviously) and install it
3. Let it boot at least once, go through initial setup, reboot recovery wipe everything, and now you are ready to flash jb with working auto rotate
P.S. to reboot in recovery with stock rooted rom you have more options ( no advanced power menu)
1, From adb : adb reboot recovery
2. Download quick boot from playstore ----> https://play.google.com/store/search?q=quick+boot&c=apps
3. Pull battery out then put it back in keep volume down and power buttons pressed until you enter bootloader from here navigate to recovery and you are done.
I hope i am right. I had but only one dhd to test.
Click to expand...
Click to collapse
Doubt it has to do with the rom you had installed before, but it has to do with the kernel etc. Have not checked the link you posted above but I am certain you have tried the JellyTime Rom and it is true that the accelerometer does not work. However, jellybean is still more than anything still new at best to our device and it will take time for it to be fully stable, taking into the account that HTC never had plans on upgrading us to JellyBean
Sent from my HTC Inspire 4G using xda app-developers app

It has nothing to do with kernel, flash a sense 4 rom and then a jb rom , any jb rom ( paranidandroid for examlpe) and the auto rotate doesn't work and you can change kernels and the auto rotate doesn't work

bondocel said:
It has nothing to do with kernel, flash a sense 4 rom and then a jb rom , any jb rom ( paranidandroid for examlpe) and the auto rotate doesn't work and you can change kernels and the auto rotate doesn't work
Click to expand...
Click to collapse
Just to clarify things... There is a cahce partition in our phones (Im not talking about Dalvik Cache)
The data in this cache partition won't be erased even with a full wipe.
When you install a JB rom, you CAN have conflicts in it ( not all users experince this ... )
So the only way , was to use the RUU, because the process it is using include wiping this cache partition ....
However , the cause of this conflict is still unkown , even if one day , if i rememeber, Synergy pointed out that the problem had to do with the upstream in custom JB roms.

Rikodu said:
Just to clarify things... There is a cahce partition in our phones (Im not talking about Dalvik Cache)
The data in this cache partition won't be erased even with a full wipe.
When you install a JB rom, you CAN have conflicts in it ( not all users experince this ... )
So the only way , was to use the RUU, because the process it is using include wiping this cache partition ....
However , the cause of this conflict is still unkown , even if one day , if i rememeber, Synergy pointed out that the problem had to do with the upstream in custom JB roms.
Click to expand...
Click to collapse
Shiiittt, i have only stock RUU sense 2.1 and arhd 6.3.3 can i do this because i try arhd it doesnt work ..
Sent from my hTC Desire HD powered CM10 by Syngergy(e)™

qazsxdcfv said:
Shiiittt, i have only stock RUU sense 2.1 and arhd 6.3.3 can i do this because i try arhd it doesnt work ..
Click to expand...
Click to collapse
Have a look here if it can help you http://forum.xda-developers.com/showthread.php?t=1970972

Worked for me! Thanks!
Sent from my Desire HD using xda app-developers app

Have had this bug, too. Now it works. Thank you

Rikodu said:
Just to clarify things... There is a cahce partition in our phones (Im not talking about Dalvik Cache)
The data in this cache partition won't be erased even with a full wipe.
When you install a JB rom, you CAN have conflicts in it ( not all users experince this ... )
So the only way , was to use the RUU, because the process it is using include wiping this cache partition ....
However , the cause of this conflict is still unkown , even if one day , if i rememeber, Synergy pointed out that the problem had to do with the upstream in custom JB roms.
Click to expand...
Click to collapse
The first time i returned to stock i used aahk and i fully returned to stock ( s-on ) and then i rerooted and flashed recovery but with the help of the aahk devs i realized that i didn't have to go full stock actualy you don't even have to use ruu you just need a stock rooted rom zip to flash in recovery and allow it to run once.
This is easy to do just flash it like any other rom in recovery let it power on and let sense start then reboot recovery and flash jb and you have working accelerometer and auto-rotate

bondocel said:
The first time i returned to stock i used aahk and i fully returned to stock ( s-on ) and then i rerooted and flashed recovery but with the help of the aahk devs i realized that i didn't have to go full stock actualy you don't even have to use ruu you just need a stock rooted rom zip to flash in recovery and allow it to run once.
This is easy to do just flash it like any other rom in recovery let it power on and let sense start then reboot recovery and flash jb and you have working accelerometer and auto-rotate
Click to expand...
Click to collapse
First point, returning to stock doesnt mean you are making your device S-on again
Second point, I did not say that your solution isnt working.. It is just that it did not work for everyone (see my thread)
Third point, Accelerometer is stil working on JB even if your auto rotation doesnt work... The proof ??? you can use manual rotation with an application form the PlayStore( unfortunatly, I forgot its name)

Bingo ! :good::good:
Thank you very much...

Rikodu said:
First point, returning to stock doesnt mean you are making your device S-on again
Second point, I did not say that your solution isnt working.. It is just that it did not work for everyone (see my thread)
Third point, Accelerometer is stil working on JB even if your auto rotation doesnt work... The proof ??? you can use manual rotation with an application form the PlayStore( unfortunatly, I forgot its name)
Click to expand...
Click to collapse
The accelerometer in my case didn't work at all on jb roms. I have tried, exactly as you suggested using andro sensor from play store, and my accelerometer was on a gray background and nothing was changing in read values as i tilted the phone. But from what i have heard it is also a radio related issue plus that pesky cache partition.
But i'm sure that the devs will figure a out an easyer way my friend.

bondocel said:
The accelerometer in my case didn't work at all on jb roms. I have tried, exactly as you suggested using andro sensor from play store, and my accelerometer was on a gray background and nothing was changing in read values as i tilted the phone. But from what i have heard it is also a radio related issue plus that pesky cache partition.
But i'm sure that the devs will figure a out an easyer way my friend.
Click to expand...
Click to collapse
Mysteries ... There are still a lot of mysteries
Anyway, the important is that we can use auto rotation again whatever the solution is....
However, I hope too that devs will figure out what is the real culprit even if I see this as not being their priority for now

Rikodu said:
Mysteries ... There are still a lot of mysteries
Anyway, the important is that we can use auto rotation again whatever the solution is....
However, I hope too that devs will figure out what is the real culprit even if I see this as not being their priority for now
Click to expand...
Click to collapse
+1 you are right my friend

Newbie Need Help..got my TF101 rooted..now what?

Hello, Im new to this and was able to root my TF101 build .27 with oneclickrecovery V0.4, which installed SUPERUSER v3.0.7
Wanted to install the EOS 4 JB because I read this is very Fast and Stable. This is what is important to me, hence the root.
Now how do I use this and install the ROM?
Is there a youtube or link that someone can direct me to?

Have a look here:
http://www.transformerforums.com/forum/showthread.php?t=33773
You will need to update to TWRP 2.3.2.3 (highly recommended) via GooManager

THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I'll alleviate some of your confusion lol, Rouge XM etc are recoveries (that are accessed via holding vol down and power) Easyflasher is a program that runs off your pc and allows you to install a recovery (like Rouge, TWRP or CWM). Easyflasher also works as an unbrick tool (if you do something wrong and mess up your tf101 easyflasher will restore it back to stock)
When using a recovery you need to place the rom on your sd card (some recoveries will only allow flashing from internal or external sd card's not both, but in the case of rouge it access both) then wipe the device (this will get rid of data etc, so if your going to make a back up this is the time) and then wipe everything except for battery stats (it isnt necessary to wipe everything but im not using the same recovery so i cant remember what the options say on rouge so just wipe everything for now) then flash the rom with "install for .zip"(and anything that goes with it i.e gapps or another kernel----- depends on the rom your using) and then just to be safe wipe the devlik cache again and reboot.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I would STRONGLY suggest switching to TWRP. Rogue will work for now, but if you flash updates to this ROM, the new file structure for 4.2 will cause your /sdcard/ to end up in the /sdcard/0/ directory, and after another flash it will be /sdcard/0/0/. You can move the files, but IMO TWRP is much better anyway (it can flash from internal and external storage).
You can install GooManager and choose to install open recoveryscript from the menu, or you can use the dd command and a terminal emulator to install TWRP:
First, download the twrp blob from here: http://techerrata.com/browse/twrp2/tf101
Rename the 2.3.2.3 blob to TWRP.blob
Method 1
Open a terminal emulator.
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
It is important to just do a reboot, if you reboot to recovery immediately it WILL NOT update the recovery. Upon reboot, you should see a progress indicator at the Eee Pad screen. Feel free to reboot to recovery after this (even before it boots).​

I strongly recommend reading the post by Fredurco in the link he provided. As a matter of fact, read the first three posts. These are the most detailed instructions for any ROM I've ever seen and believe me, I've seen more than a few. Take your time and just follow those directions to the letter and you will be fine.

frederuco said:
IMO TWRP is much better anyway (it can flash from internal and external storage).
Click to expand...
Click to collapse
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...

Thing O Doom said:
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Click to expand...
Click to collapse
Yeah, get crackin!

Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
JoinTheRealms said:
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
Click to expand...
Click to collapse
I agree! EOS 4 IMO is the most usable and stable 4.2 build. My biggest complaint with the CM10.1 build was the touchpad disable was not working. It is still a great ROM otherwise and pretty stable.
As far as 4.1 ROMs, EOS 3 is solid, and so is the CM10/PananoidAndroid hybrid.
I am definitely itching for some cornerstone love!

I use liquidsmooth currently, and it's my new favorite, since everything works. I haven't found or noticed any bugs, which is rare.
EOS4 is also good, but I just don't like the feel of it oddly. Very well built and worth a shot though.

Hi Fred! Dug my TF101 out of moth balls and put on EOS4.
Had some trouble with the drivers, So I ended up using 1 from column A, 2 from column B:silly:
end result, got my drivers, APX mode going, (cross between oneclickrecovery, easyflash, nvFlash, Universal Naked Drivers),
Finally got twrp on and flashed superuser
got twrp-goo manager to update it, Flashed EOS4- saw updated recovery did not stick, finished the flash, updated twrp again, reflashed eos4- saw twrp update did stick this time, and now get to play with the TF 101 all over again!
Everything old is new again!
Thanks Fred! Your post on the TF forum was great, and XDA supplemented what wasn't working for me!! Great teamwork:victory:

Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!

LongbowFoSho said:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
Click to expand...
Click to collapse
I guess I am not sure what is causing your WiFi stability issues. I have no problems with the EOS 4 ROM and WiFi. It never drops out on me. It is perfectly stable, and I can play 720p H264 23.94 FPS mkv files with no issues using MX player.
Before I ran EOS 4, I was running the ParanoidAndroid/CM10 Hybrid ROM and it was just as stable and fast.
If you are having WiFi issues, did you do all the wipes (Cache, Davlik, System, Factory Reset) before flashing the ROM? If not, then that is probably where the WiFi issue is (settings from your previous ICS ROM still present on the data partition).

Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!

LongbowFoSho said:
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
Click to expand...
Click to collapse
EOS4 and the CM10.1 No-Name are the only ones getting regular updates.

Thanks for the quick responses. EOS 4 is installed and process of redownloading all my apps. Now I just need to test out some video. I'm testing it without the OC kernel first, just for fun.

If you wanna see more in-depth which rom is better, I recommend a little app called Antutu benchmark, it'll give your current setup a score depending on how fast it does things like 3d renderind, sd card reading and battery performance

I might be in the minority with this opinion, but after some tinkering I'm not all that convinced that EOS is any faster than the stock ROM from a general usability standpoint (even with the latest KAT kernel), but the video is definitely improved, so I'll keep it as my "daily driver".
Thanks for the help, guys!

Most stable ROM for WiFi TF101

Title says it all guys blowing of the dust of this thing can anyone point me to the most stable ROMs out there CM10 prefer
Sent from my HTC6435LVW using Tapatalk 2

I'd like to know this too. I often have to turn wifi off then on to reconnect.

Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings

Team EOS 4, Katkernel here too, make sure you reboot a few times after installing it. follow the guide in this forum, install it like it directs you to.
FULL wipe(cache, dalvik, factory, system), install ROM, cache/dalvik wipe, install gapps, cache/dalvik wipe, install Kernel, cache/dalvik wipe, reboot.
Get Kat apk to boost volume and GPS fix.
I was having systemUI issues, reinstalled everything a few times and now it's running great. Keep it under 1400mhz, 1200mhz seems to work well for me. Nightly 109 was eating up my battery too quickly, 111 is doing better, I hope they can improve more if possible, great ROM either way, I'm very grateful.
Sent from my Transformer TF101 using xda app-developers app

I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.

Astania said:
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Click to expand...
Click to collapse
Just reply to a few other threads, XDA has thousands

+1 for EOS4/KAT kernel. No-name is pretty good as well if you like CM 10.1.

EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing

+1
talman26 said:
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
Click to expand...
Click to collapse
Aye...EOS 4.2.2 (v109) + 1400, very stable, no big issues, suitable for daily drive tab

+1
Team EOS4, Been using it for months and not a WiFi hicup.

*Detection* said:
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Click to expand...
Click to collapse
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:

danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
Can you still get into recovery? If so, can you flash from the microSD?

danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs

Team EOS 4 + Kat Kernel = FAST and STABLE :victory:
PS: If you wish to use Phablet UI i suggest you use Trebuchet from CM 10.1

*Detection* said:
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Click to expand...
Click to collapse
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!

danilimpsy said:
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
Click to expand...
Click to collapse
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Sent from my Transformer TF101

zAlbee said:
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Click to expand...
Click to collapse
As I already said...flashing ROM FAILED over 5 to 7 times...and I CAN´T get to APX...i´m stucked at NO SYSTEM...just can get to Recovery, but NO flashing!

Try a different PC, or reinstall APX drivers
99% that APX mode does work, either you are doing something wrong, or your PC is struggling with the APX drivers
APX mode is volume up & power from powered off state while already plugged into PC, the only notification for entering APX mode is USB connect sound, nothing will appear on TF screen

I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment

hulk69 said:
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
Click to expand...
Click to collapse
Have to ask, what recovery did you use and did you do a full wipe before installing?
I find EOS 4 to be MUCH more stable on WiFi than any ICS ROM (including Stock and stock based ROMs)