[ROM][Nightly][ICS] Team Eos Transformer Prime Nightlies (tf201)
- Thread starter teameos
- Start date
-
- Tags
- development
Has anyone used HDMI with this ROM, preferably the Cornerstone version? I tried is yesterday and nothing happened, and I don't see any settings for it.
Check this post out where I replied to you. This may help you guys get it going.
http://xdaforums.com/showpost.php?p=24960442&postcount=9
Perhaps I can get some help... I installed Cornerstone 1/Gapps last night, and it was working pretty well. I just tried flashing Cornerstone 2/Gapps, and it keep looping back into CWM. Any ideas as to what I can do to fix it? Do I need to do a factory reset every time I flash a nightly? I'm a bit new to nightlies, to be honest.
hey hey
type this in CWM
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
and use one of those recovery I had this problem too
http://xdaforums.com/showthread.php?t=1601942
good luck and have fun
Thanks Dixxa, but would it be possible to get a step-by-step instruction for this process? I'm not sure where to enter that code.
Edit:
Never mind, I just clicked the link, so I see the instructions there.
Edit:
Never mind, I just clicked the link, so I see the instructions there.
Last edited:
Actually, as it turns out, I'm still pretty stuck. Every time I try to enter that line of code in Command Prompt, I get the following message:
'adb' is not recognized as an internal or external command, operable program of batch file.
Any help? It would be very much appreciated.
Edit: Update - I'm working just fine now. Thanks for the help, everyone.
'adb' is not recognized as an internal or external command, operable program of batch file.
Any help? It would be very much appreciated.
Edit: Update - I'm working just fine now. Thanks for the help, everyone.
Last edited:
I had exactly the same soft-brick yesterday, but was able to get out of it.
What you will need to do is the following:
Pre-req for this to work is you have to have ADB installed. If you do not already have this installed on your PC, use your phone and you should be fine. The other thing you need to get is the Universal Naked Driver for TFP which is available here on XDA.
1. Boot the TFP into CWM (you should already be there)
2. Open a Command Prompt window, and go to where you have ADB set up
3. Connect your tablet to the PC via the cable.
4. Check to see if your ADB setup is seeing your Tablet, you can do this by typing "ADB Devices" after the prompt. If it sees your tablet it should show your Device Serial number as connected.
5. If your tablet is not showing up, go to Device Manager (you can get there via Control Panel) and check to see if it shows up there as a device. Add the necessary driver (the UND one) here so it sees your tablet.
6. If you have installed ADB correctly, and it sees your device, then go to this thread: http://xdaforums.com/showthread.php?t=1514088 and follow the directions for a Option 1a recovery
Honestly, it took me about 4 tries to get everything setup properly, and took about an hour because I tend to go slow and careful, but I am up and running and fully recovered now.
Good luck
What you will need to do is the following:
Pre-req for this to work is you have to have ADB installed. If you do not already have this installed on your PC, use your phone and you should be fine. The other thing you need to get is the Universal Naked Driver for TFP which is available here on XDA.
1. Boot the TFP into CWM (you should already be there)
2. Open a Command Prompt window, and go to where you have ADB set up
3. Connect your tablet to the PC via the cable.
4. Check to see if your ADB setup is seeing your Tablet, you can do this by typing "ADB Devices" after the prompt. If it sees your tablet it should show your Device Serial number as connected.
5. If your tablet is not showing up, go to Device Manager (you can get there via Control Panel) and check to see if it shows up there as a device. Add the necessary driver (the UND one) here so it sees your tablet.
6. If you have installed ADB correctly, and it sees your device, then go to this thread: http://xdaforums.com/showthread.php?t=1514088 and follow the directions for a Option 1a recovery
Honestly, it took me about 4 tries to get everything setup properly, and took about an hour because I tend to go slow and careful, but I am up and running and fully recovered now.
Good luck
No matter, you will be able to change it soon in settings pages.
I'm not around much for the next few days but I am working on the ROM and specifically the dock keys as much as I can in the spare time I can grab.
Anyone trying the Cornerstone version run into issues with wi-fi?
Edit:
NVM... Reboot got it going.
Sent from my SGH-I897 using xda premium
Edit:
NVM... Reboot got it going.
Sent from my SGH-I897 using xda premium
Last edited:
I went back to the non-Cornerstone version, but my wi-fi worked for the short time I was on it
Sent from my SGH-I897 using xda premium
I haven't seen this referenced anywhere but I am curious if anyone else has this problem. Everytime I flash a CM9 nightly or TeamEOS nightly build the wifi is horrendous, to the point where it won't even show my SSID when sometimes. But when I flash a rom based off of the ASUS base rom like my wifi is perfectly fine. It shows up super quick and connects instantly. I am currently on the latest AOKP right now because it's the closest to CM9 at the moment that I can actually use.
Curious if anyone has the same issue or has a fix that I am unaware of. (And yes I realize wifi is horrible on some prime units)
Sent from my EPAD using Tapatalk 2
Curious if anyone has the same issue or has a fix that I am unaware of. (And yes I realize wifi is horrible on some prime units)
Sent from my EPAD using Tapatalk 2
My Prime's WiFi has always been great. Wherever I take my son's Xoom (also has Eos nightly) in the house, my Prime would only have a bar less than the Xoom. Ever since I flashed Eos nightly on my Prime, the WiFi has suffered more than ever. So you're definitely not alone in this. Right now I can't complain though because it's still usable for me no matter which hotspot I'm nearest. It sounds to me like for you it (the WiFi) is sometimes completely unusable?
Can't wait until you get those dock keys working! I use my prime as my main computer and without them, I feel powerless haha Thanks again for all the hard work; the rom is awesome. Also, not sure if you saw, but Jermaine got a modified AOKP b31 with cornerstone working which has working keyboard short cuts if you think that it will help with EOS in any way.
***Also, is there a way that you could add the dual battery in the status bar like in the stock asus rom when the keyboard dock is connected? I think the latest cm9 nightly has it as well.
I've tried all the other ROMs and this and CM9 are the only one that give me either 1/3 of my speed or nothing at all. Exact same situation as you, with no solution yet,
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
40Team EOSICS 4.0.4 TF201NIGHTLIES
Welcome to the evolution of TiamatXOOM.
With the AOSP release of Android 4.0 begins the next dawn of the Android operating system. And with this release comes Team EOS, the natural evolution of the TiamatXOOM development team.
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. The launching point for this development effort is the Motorola XOOM.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated once every 24 hours and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS TF201 Nightly builds: http://goo-inside.me/devs/teameos/roms/nightlies/tf201/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Use the latest available gapps package available from http://goo.im/gapps
*Note - You will need to re-flash G-Apps after you flash an updated nightly build. You can do this before you reboot after the installation of a new nightly.
Also note that if you are coming from an earlier G-Apps package you will need to wipe prior to installation of this package in order to avoid FC issues.
--
Features:
Because these are nightly builds the included features are constantly evolving. Change logs are generally generated on a daily basis.
Change logs can be viewed at http://nightlies.teameos.org/changelogs/
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
--
Installation Notes:
These builds are designed to be installed from your favorite recovery
Perform a full wipe (read Factory Reset) prior to installing this over ANY Honeycomb based rom (this includes all Tiamat roms)
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
FEATURE REQUESTS!
We need YOU, yes YOU to help us build the best AOSP rom out there. Have an idea for a feature you want to see implemented then let us know!
Team EOS Feature Request
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
Source Code
Rom: http://git.teameos.org
Kernel: https://github.com/Roach2010/asus_kernel_tf201
Welcome to the TF201 evolved. Welcome to Team EOS.
I also would like to welcome Roach2010 to the team, and is your TF201 developer for this rom.19
----------------------------------------------------------------------------------------------
Please be aware that using reboot to recovery may leave you stuck in a recovery loop with the current versions of clockworkmod recovery.
I have repacked recoveries available that have a workaround in place here.
These should suffice until CWM is updated to prevent this loop from happening.
----------------------------------------------------------------------------------------------
I'm currently conducting trials to address the poor WiFi performance that some users are experiencing. Please see this post for further details.54
I'm sorry! Is that supposed to be a put down? I find it rather offensive that after I try to share some information and then give some words of encouragement, that you come along and try to put down my information as though it's totally worthless.
Remind me to remind myself that actually some people here on xda are still very silly and need to learn some simple behavioural techniques that most of us learnt when we were children.
Of course, the fact that you assumed that the thread was "the ride" only goes to further indicate your obvious misjudgement of my previous post.
/rant
EDIT: Sorry to team EOS for putting a bit a negativity into the thread. I just needed to say it.4I was so hoping it was Didget or DuBaWidget or something equally as nutty...
As for where EOS stands compared to others? Tough to say, right now it seems like it's not so much like for like comparison but instead having different plusses and minusses to each build. Virtuous is hands down the best stock-like (not that there's much to pick from now, but nontheneless) and acts as an effective yardstick to measure everyhing else. Since it has all the asus tweaks but none of the asus junk bloat, it's a solid benchmarking point.
AOKP is clearly going for the kitchen sink approach, as evidenced by the fact they now have an APP specifically for backing up ROM settings, yes, there are that many tweaks and bends in the ROM to play with. It's very well put together, but if I was a newbug, I fear the mass of settings might cause me to have a nervous breakdown.
Gummy is going for what something between Cyanogen and EOS, there's a lot of nice cyanogen like features implemented, and their own homebrew widgets and tools are genuinely top class. However, for non US setups, it's not yet ready for showtime, if I can kill half the Dock android keys simply by changing keyboard languages, there's still some definite funkiness to get worked out.
Cyanogen was dominant during the 2.x android cycle, and whilst I hate to be seen as a naysayer to all the work done by other teams, longer term Cyanogen is going to be the one to beat. Right now though Cyanogen is having to cover so many devices that more specialised teams have got the jump on them in terms of stability and feature cycle. I wouldn't expect Cyanogen to catch AOKP, Gummy or EOS for a while yet. Cyanogen might be better in some areas, but each of the three I've poked have been stronger than CM in -some- way, just different ways per ROM.
EOS seem to have got the tablet side of ICS down to a fine art, honestly, were it not for the fact I know this is an AOSP rom I'd have assumed it came with my prime, it's that stable and brisk. I've had it sleeping, waking up, I've done some curveballs with wifi, about to run VLC into it to see what happens, but judging by the fact this build has the GCC revert, that should be dandy. Hunch says they're probably only 1 or 2 builds off of a stable release from here, though that's ignorant user me talking, I could be wrong.
At this point the only real wildcards are if ASUS provide NVFlash for unlocked devices (since that would allow devs to crack open the inner workings of the device and the teg 3 chipset) and the impending .25 stock release which I've on good authority seriously puts some speed into the stock ROM, meaning things like Virtuous might leapfrog ahead in terms of desirability. Unsure.
I've not fiddled with any of the other releases here (WSG? I think?) so I lack any opinion on those.
Just my thoughts at this point
