I noticed the same thing but my download kept giving me an MD5 mismatch. I tried going to the Goo site and #6 isn't there.
First the Cornerstone this morning, now this. :/
[ROM][Nightly][ICS] Team Eos Transformer Prime Nightlies (tf201)
- Thread starter teameos
- Start date
-
- Tags
- development
I noticed the same thing but my download kept giving me an MD5 mismatch. I tried going to the Goo site and #6 isn't there.
First the Cornerstone this morning, now this. :/
We have a new build bot so please bear with us.
OMG, we are so so sorry. However can we make it up to you!
We have a new build bot so please bear with us.
OMG, we are so so sorry. However can we make it up to you!
It's okay! I forgive you! LOL. J/K, of course. In case others here really think I'm bashing you, I'm all cool with it.
Regarding the test kernels, I've only gotten to testing #3, #4 and the one built-in with nightly #6.
I took the average of 10 tests for each. The results for the speed tests:
test kernel #4 - 14ms / 6.847 Mbps down / 10.143 Mbps up
kernel in nightly #6 - 15.4ms / 6.966 Mbps down / 8.034 Mbps up
test kernel #3 - 12.6ms / 6.214 Mbps down / 9.378 Mbps up
According to Roach`, the difference is the latest drivers are on #4 and that if it doesn't make a difference in the tests, then it's not the drivers.
There are many other factors contributing to one's WiFi connection speeds, but for me I guess it's safe to say it isn't the drivers. I'd suggest to give this a try before settling for the kernel. For Roach`, test kernel #4 works best, for me I'll be sticking with the one he put in nightly #6.
EDIT: Apologies! I just realized that when I tested #4, it was connected to a server slightly further from my location. I redid the test and the results reflect above. I guess test kernel #4 is better. The reason why the download speeds are a little lower than nightly #6 is because I did more tests on #4 (I couldn't believe how much higher it was than the previous test since the locations are only a few miles apart) and that brought down the average. Take my results with a grain of salt, but for me, I can honestly say that I prefer test kernel #4.
I took the average of 10 tests for each. The results for the speed tests:
test kernel #4 - 14ms / 6.847 Mbps down / 10.143 Mbps up
kernel in nightly #6 - 15.4ms / 6.966 Mbps down / 8.034 Mbps up
test kernel #3 - 12.6ms / 6.214 Mbps down / 9.378 Mbps up
According to Roach`, the difference is the latest drivers are on #4 and that if it doesn't make a difference in the tests, then it's not the drivers.
There are many other factors contributing to one's WiFi connection speeds, but for me I guess it's safe to say it isn't the drivers. I'd suggest to give this a try before settling for the kernel. For Roach`, test kernel #4 works best, for me I'll be sticking with the one he put in nightly #6.
EDIT: Apologies! I just realized that when I tested #4, it was connected to a server slightly further from my location. I redid the test and the results reflect above. I guess test kernel #4 is better. The reason why the download speeds are a little lower than nightly #6 is because I did more tests on #4 (I couldn't believe how much higher it was than the previous test since the locations are only a few miles apart) and that brought down the average. Take my results with a grain of salt, but for me, I can honestly say that I prefer test kernel #4.
Last edited:
I tested all 4 (test kernels) and (for me) number 4 is the best. The reception and speed is a big improvement over stock and the 3 other test kernels. With #4 @ 60' I was getting around 10/5 Mbps, that almost double from yesterday ( #1 & #2). Awesome work Roach'.
I installed the tf201-4 version. Everything installed and it booted up fine but then it gave a error saying a file quit working followed by what looked like japanese. Then it would do a quick boot and then it would do the same thing again. I wish it would work as it looked like a cool rom. I had to do a restore from backup with cwm touch.
Just to muddy the waters a bit I am going to say that kernel #3 seems to give me the best performance. My wifi is basically the same as I saw with stock in terms of speed and ability to connect to my network both close to and a distance away from my router.
This really is a sh*t hot rom Roach and I don't think that it has been getting the attention that it deserves on this forum given that it is so far along in terms of development. I must admit that I was put off at first by the fact that it is a nightly and was expecting a buggy mess. I am on Cornerstone v5 and aside from being extremely stable the only thing that I see isn't working is the dock key to disable the touchpad. Am I missing something?! Really cool work - please keep it up!
Sent from my EPAD using xda premium
This really is a sh*t hot rom Roach and I don't think that it has been getting the attention that it deserves on this forum given that it is so far along in terms of development. I must admit that I was put off at first by the fact that it is a nightly and was expecting a buggy mess. I am on Cornerstone v5 and aside from being extremely stable the only thing that I see isn't working is the dock key to disable the touchpad. Am I missing something?! Really cool work - please keep it up!
Sent from my EPAD using xda premium
I'm on cornerstone v5. All of the keyboard is working apart from the button that toggles the touchpad.
Sent from my EPAD using xda premium
Are you using Roach's modified version of CWM? If not, that is probably what has caused this. There is a link in OP that describe it and explains how to get out of the loop. Hope that helps.
Sent from my EPAD using xda premium
And I've now written the framework code for the button so I just need to write a native function to actually switch off the touchpad. Jni is not my strongest point so this should be fun.
The good news is that the setting is stored so once disabled, the touchpad will not turn back on after every reboot.
That's good news mate - I will look forward to it. Thanks again for all of your work on this.
Sent from my EPAD using xda premium
Sent from my EPAD using xda premium
Last edited:
I just got to testing the WiFi speeds with a stock Asus Transformer Prime (only rooted) against my Eos #7 with its built-in kernel (not #3 or #4) and the speeds are identical. I'm not sure about the range, but this is a good sign for me. After unlocking and trying Eos, my speeds were slightly slower until yesterday. Today, I can confirm my Prime is back in good shape, even better than the stock with Eos but WiFi-wise, I'm happy.
Go this post from Roach:
http://xdaforums.com/showthread.php?p=25152304
Sent from my GT-I9100 using Tapatalk 2
And I've now written the framework code for the button so I just need to write a native function to actually switch off the touchpad. Jni is not my strongest point so this should be fun.
The good news is that the setting is stored so once disabled, the touchpad will not turn back on after every reboot.
Is there a way that you could incorporate the multi bowser button hack in a future build? I noticed that the keyboard.apk is not included in the system/app folder which leads me to believe that the keyboard function lies somewhere else in the from, correct me if I'm wrong though
Hi. I am on the cornerstone nightly 6 rom with kerna fix 4 posted earlier. WIFI is great an everything is working, well, essentailly flawlessy; its awesome. My only problem is that my prime doesn't seem to be able to operate at a core level above 1.3ghz. I wanted to see if anyone else has had this problem and if they would know how to fix it. I tried looking in system/ect/inid for the overclock script but am unsure of what to edit to change the frequency
Wow I'm running the cornerstone #6 build and it is sweet. Thank you so much for this. Team EOS rocks.
Sent from my EPAD using Tapatalk 2 Beta-5
Sent from my EPAD using Tapatalk 2 Beta-5
+1 on that. I was using the AOKP Cornerstone rom before this and I think that this is more stable and less buggy. One of the main problems that I had with AOKP Cornerstone was on most boots my widgets wouldn't load and I would have to reboot. This only occasionally happens with this rom.
Also, is anyone else having a problem with TiBu recognizing their purchased license for this app on Eos? I get some weird error message that the license is not recognized and that I need to purchase a new one. No biggie - I just have to delete the app from system>apps then redownload and it works fine.
Thanks again for this Roach - its a fantastic piece of work
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
