[ROM][Nightly][ICS] Team Eos Transformer Prime Nightlies (tf201)

Search This thread

goodintentions

Senior Member
Aug 14, 2010
2,540
729
No offense to anyone here, but posting on here I always feel like I'm praying to god. I get ignored most of the time. For instance, I asked a simple question to someone which version cornerstone do they have bluetooth working and I get completely ignored.

So, chances are I will get ignored here for the info I'm about to give.

Regarding the black screen during the auto-rotate, I know a dev that solved it. He solved it for the cornerstone over in tf101 rom. Check out the post that he made the announcement.

http://xdaforums.com/showpost.php?p=24082027&postcount=571

Why not ask him on how to solve this for us?

But again, I don't expect much from this since this post will probably get ignored.
 

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
No offense to anyone here, but posting on here I always feel like I'm praying to god. I get ignored most of the time. For instance, I asked a simple question to someone which version cornerstone do they have bluetooth working and I get completely ignored.

Lol, praying to god :p I agree that it is quite quiet in here. Its a bit of a shame because I think this is a really good rom. Quiet forums make people think there might be something dodgy...

As for your question, I don't use bluetooth so I can't help.
 

Hobbesian

Senior Member
May 9, 2012
58
32
Shepton Mallet
Just done a proper test of the v15 build (non cornerstone), 23/5

I can see only one issue that needs immediate attention, I'll check up on sleep of death by leaving the thing overnight and seeing if it stays comatose next day. So far this build is stable, handles different nationality keyboard setups just fine, all the android keys work regardless of language selection.

Wifi stability on the non CS variant is very much there by the looks of, and any performance hiccups seem to be strictly down to the cornerstone framework (and to be fair, there weren't many, though I was able to force a hard lockup by using Tunein Radio pro + Email + web browser via CS).

However, something which is a mite disconcerting - there's no indicator to tell me that the keyboard is plugged in, nor is there a charge read on said keyboard. This is however getting into the realms of "Small things that would be useful to have but not essential".

This feels a lot like a release candidate, I'm hoping the last odds and sods are patched out with the next few nightlies.
 
  • Like
Reactions: paddycr

hartej

Senior Member
Dec 10, 2004
159
54
However, something which is a mite disconcerting - there's no indicator to tell me that the keyboard is plugged in, nor is there a charge read on said keyboard. This is however getting into the realms of "Small things that would be useful to have but not essential".

Have a quick search for "Dual Battery Widget" on the Google Market (I'm refusing to use the silly name it's become!)

Here: https://play.google.com/store/apps/details?id=org.flexlabs.widgets.dualbattery&hl=en
 

fabolous02000

Senior Member
May 20, 2010
116
21
Nyc
On cornerstone v12 is anyone having a problem with MultiPicture live wallpaper app. It doesn't display any pictures when I try to set multiple backgrounds

Sent from my EPAD using xda premium
 

Hobbesian

Senior Member
May 9, 2012
58
32
Shepton Mallet
I might be mistaken but I thought that live wallpapers were disabled for cornerstone builds due to resolution/random other issues.

Sent from my AOKP OG Epic 4G

This is correct to my knowledge. Also, I'm now coloured curious. The Dual Battery Widget has a silly name, what is it? Inquiring minds demand to know! My money was on Didget but that came up blank...
 

fabolous02000

Senior Member
May 20, 2010
116
21
Nyc
I might be mistaken but I thought that live wallpapers were disabled for cornerstone builds due to resolution/random other issues.

Sent from my AOKP OG Epic 4G

Im using Wp clock app to set a background image without cropping it. Multipicture lwp has the same feature for multiple screens , but it doesn't work on cornerstone. Just seemed weird to me cause wp clock is a live wallpaper & sets a picture no problem.
Sent from my EPAD using xda premium
 

paddycr

Senior Member
Jan 25, 2012
659
156
OnePlus 8T
Just done a proper test of the v15 build (non cornerstone), 23/5

I can see only one issue that needs immediate attention, I'll check up on sleep of death by leaving the thing overnight and seeing if it stays comatose next day. So far this build is stable, handles different nationality keyboard setups just fine, all the android keys work regardless of language selection.

Wifi stability on the non CS variant is very much there by the looks of, and any performance hiccups seem to be strictly down to the cornerstone framework (and to be fair, there weren't many, though I was able to force a hard lockup by using Tunein Radio pro + Email + web browser via CS).

However, something which is a mite disconcerting - there's no indicator to tell me that the keyboard is plugged in, nor is there a charge read on said keyboard. This is however getting into the realms of "Small things that would be useful to have but not essential".

This feels a lot like a release candidate, I'm hoping the last odds and sods are patched out with the next few nightlies.

Good to see you over in this direction Hobbesian :) I see you are doing the rounds like me in terms of jumping from rom to rom. Two nice reviews btw. How do you think these roms stack up against the others?

Edit: the Dual Batter Widget has been very useful with this rom in spite of having a faintly ridiculous name...

Sent from my EPAD using xda premium
 
Last edited:

Hobbesian

Senior Member
May 9, 2012
58
32
Shepton Mallet
I 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 :)
 
Last edited:

goodintentions

Senior Member
Aug 14, 2010
2,540
729
Need help with bluetooth. It appears that I'm the only one using this rom with a problem with bluetooth. With the stock and primalicious, I can connect to my bluetooth devices instantly. With this rom (v12 cornerstone) I can't pair to anything. Keeps saying got rejected.

Did you guys do something I'm not aware of?

Edit.

SOLVED!

The bluetooth in the settings is useless. But if I use bluetooth file transfer app and use that to pair with the devices it works. The question is why?
 
Last edited:

Xelstyle

Senior Member
Dec 22, 2011
342
50
Need help with bluetooth. It appears that I'm the only one using this rom with a problem with bluetooth. With the stock and primalicious, I can connect to my bluetooth devices instantly. With this rom (v12 cornerstone) I can't pair to anything. Keeps saying got rejected.

Did you guys do something I'm not aware of?

Edit.

SOLVED!

The bluetooth in the settings is useless. But if I use bluetooth file transfer app and use that to pair with the devices it works. The question is why?

Can't really help much seeing as I'm part of the group with no blue tooth issue in any of the builds. Glad you manage to find a work around though.
Definitely a random odd ball.

Sent from my GT-I9100 using Xparent Cyan Tapatalk 2
 

goodintentions

Senior Member
Aug 14, 2010
2,540
729
I don't understand something. Why is the clock automatically set to 1.6? Am I the only one that wants battery life over speed?
 

Hobbesian

Senior Member
May 9, 2012
58
32
Shepton Mallet
There's two elements at work in the EOS rom - First is the governor and CPU limits which most of us know about, but there's a secondary layer under the EOS header "Device Settings" which give the same 3 CPU profiles ASUS does : Balanced hard caps the CPU ceiling to 1.2ghz, if you set it to performance, the limit is whatever you set the max frequency to under the CPU settings.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 40
    Team EOS​
    ICS 4.0.4 TF201​
    NIGHTLIES​

    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
    Cornerstone builds are available from http://goo.im/devs/teameos/roms/cornerstone/nightlies/tf201

    Please note that these are not supported and will have issues.

    ----------------------------------------------------------------------------------------------

    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.
    5
    Reserved for me
    4
    Big ride.. 25 posts


    Sent from my iPad using Tapatalk HD

    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.
    4
    I 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 :)