[ROM][JB] Team EOS 3 *JELLYBEAN* Nightlies - TF101

Search This thread

michaeljc70

Senior Member
Nov 8, 2010
100
3
I've been using this ROM for a while and the only issue I have is losing audio/low audio. I installed the KAT Audio app and that fixed the low volume. I was wondering if any of the updates since I installed (Build 81/Kernel 2.6.39.4-kay 11/11) fix the losing audio issue.

If I do install a newer nightly, do I have to wipe anything?
 

frederuco

Senior Member
Feb 27, 2012
1,578
690
Build 81 is the last TeamEOS 3 ROM. Build 82 moved to TeamEOS 4 and Android 4.2.

If moving from TeamEOS 3 to 4, you need to wipe caches, system and factory reset.

Install ROM, GAPPS, boot and then restore your apps and data.
 

aspros21

Senior Member
Apr 22, 2009
104
17
Athens
Does that version fix the audio issue?

no.
you can use kat app to maximize the audio volume. check cascade and when you press volume up, keep pressing and you will notice that it will become louder. even when you are on the end of the bar keep pressing. you will notice the difference.
when you lose audio press reint fm34 and the audio is back.
 

unixdood

Senior Member
Apr 26, 2007
57
5
New hampshire
So I went from ICS to this EOS JB rom. The rom is fantastic except for one app that i use that is way too slow to play it. In ICS, the game NFL 2013 runs perfectly, when i upgraded to EOS the game slows down to less than HALF the speed and is unplayable. Everything else seems great. I messed with the EOS system performance settings but everytime i OC up to 1.4Ghz or 1.6GHz the system freezes for 10 sec and then reboots. It doesnt seem to OC properly. I tried a different kernel (KAT) and that causes reboots constantly. Any thoughts?
 

aspros21

Senior Member
Apr 22, 2009
104
17
Athens
So I went from ICS to this EOS JB rom. The rom is fantastic except for one app that i use that is way too slow to play it. In ICS, the game NFL 2013 runs perfectly, when i upgraded to EOS the game slows down to less than HALF the speed and is unplayable. Everything else seems great. I messed with the EOS system performance settings but everytime i OC up to 1.4Ghz or 1.6GHz the system freezes for 10 sec and then reboots. It doesnt seem to OC properly. I tried a different kernel (KAT) and that causes reboots constantly. Any thoughts?

what kat kernel? I think with this ROM you need 69b, but I am not so sure. check the thread of kat kernel the 2nd or 3rd post for compatibility.

Sent from my Transformer TF101
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
For 4.1-based ROMs, Kat kernel 70 lidpatch should be OK.

RaymanFX is very busy with his Sony Experia for which he has started numerous projects. He haven't done anything for the TF101 since December. I say he has found a new love :p

You are better off either using Timduru's kernel or moving to a 4.2-based ROM (where Timduru also has good kernels :) ).
 

thunderman98

Senior Member
Jul 26, 2011
79
8
EOS 3 ROM

Hi..I am going to flash my tf101 for the first time.I want to start with eos3 then work my way up.Could someonelet Mr know if this os the right configuration for this Rom,have been reading thru this thread and from what I have read is this the best and most stable?
EOS3 BUILD #81
GAPPS 121212
KAT KERNAL 69B
KAT APP V1.2.2

THANKS...want to feel out JB before advancing and is this the way to start?
 

aspros21

Senior Member
Apr 22, 2009
104
17
Athens
Hi..I am going to flash my tf101 for the first time.I want to start with eos3 then work my way up.Could someonelet Mr know if this os the right configuration for this Rom,have been reading thru this thread and from what I have read is this the best and most stable?
EOS3 BUILD #81
GAPPS 121212
KAT KERNAL 69B
KAT APP V1.2.2

THANKS...want to feel out JB before advancing and is this the way to start?

it is pretty stable and fast but is not updated any more.

i use eos 4 rom (jb 4.2.2 - nightly 168) with latest kat kernel & kat app.
it is the same stable, more fast and smooth than eos 3. beside that it is updated often for fixes and new features.

i suggest to try first eos 4. you will not regret it and you will never flash other rom ;)

Sent from my Nexus 7 using xda app-developers app
 
  • Like
Reactions: thunderman98

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
The CM10.1 ROM is pretty good too. :p

But yeah, I agree this ROM is not really updated any more and I would suggest getting something more recent.
 
  • Like
Reactions: thunderman98

thunderman98

Senior Member
Jul 26, 2011
79
8
new rom

Thanks for the info...in goo manager it only goes to eos4 build 97...is this a good place to start or what build # and on the nightly what is a stable update...thought i read somewhere if it had a b after it it was the one.also what governor do most use? Smartass v2.?again thanks for all the help ...also what gapps? And when do you flash the kernal after gapps?
 
Last edited:

frederuco

Senior Member
Feb 27, 2012
1,578
690
Thanks for the info...in goo manager it only goes to eos4 build 97...is this a good place to start or what build # and on the nightly what is a stable update...thought i read somewhere if it had a b after it it was the one.also what governor do most use? Smartass v2.?again thanks for all the help ...also what gapps? And when do you flash the kernal after gapps?

There is a B168 preview on TimDuru's site that has added a way to change the physical keyboard without rebooting. Check the EOS 4 thread for Tim's preview download links.

I use the KatKernel OC'd to 1.4 and Interactive governor. Using smartassv2 seems to keep my CPU at 1.4 all the time. Not sure why, but it never slows down until I turn the tablet off.
 

aspros21

Senior Member
Apr 22, 2009
104
17
Athens
Thanks for the info...in goo manager it only goes to eos4 build 97...is this a good place to start or what build # and on the nightly what is a stable update...thought i read somewhere if it had a b after it it was the one.also what governor do most use? Smartass v2.?again thanks for all the help ...also what gapps? And when do you flash the kernal after gapps?

see timduru s signature. he has links for everything you will probably need.

the order I am making to work is
wipe cache
wipe dalvik
wipe system / factory reset
flash ROM
flash kernel
flash gapps
wipe cache
wipe dalvik

all these from TWRP 2.3.2.3 because is fully compatible with jb 4,2,2 file structure.

Sent from my Transformer TF101

---------- Post added at 11:23 PM ---------- Previous post was at 11:12 PM ----------

The CM10.1 ROM is pretty good too. :p

But yeah, I agree this ROM is not really updated any more and I would suggest getting something more recent.


he preferred eos ROM so I suggested to go to newer version of eos. :rolleyes:
I have flashed some of your builds . it was very good work :thumbup:. I think that we all have to be grateful to CM team and every dev / XDA member tries to make things better.
thank you for your effort. and keep up.




Sent from my Transformer TF101
 

Top Liked Posts

  • There are no posts matching your filters.
  • 156
    Team EOS​
    JB 4.1.1 TF101​
    NIGHTLIES​

    Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!

    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. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.

    --
    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 every now and then, 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 Nightly builds: http://goo-inside.me/devs/teameos/roms/eos3/nightlies/tf101/

    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:

    Temporary Gapps package gapps
    --
    Features:
    Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
    For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org

    Kernel:
    Kernel Note: This rom is currently using the stock kernel, so you can find the sources from aosp.

    --

    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 ICS or JB based rom.

    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.


    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.

    ---

    Enabling voice search in google now

    1. Go into Settings
    2. Go to "Language & input"
    3. Scroll down to "Speech" and click on "Voice Search"
    4. Click on "Download offline speech recognition"
    5. Swipe Across to the "ALL" tab if needed
    6. Download your speech pack for your language
    40
    Here is what I am aware of that has still to be fixed. I'll add to it once I've went through the bugtracker.

    GPS
    Face unlock
    Audio is a bit too quiet.
    HDMI Audio
    Touchscreen sometimes stops accepting input. (temp workaround - go into standby and resume and it should come back to life).

    Changelog:
    Hopefully as of Build #58 the unscheduled reboot issue has been resolved. Freedback appreciated
    Wifi regualatory domain changed added.
    Full dock support including keyboard layout selector.
    Google Search no longer crashes.
    Screen now turns off when the lid is closed on the dock.
    Smart covers now switch off the screen.
    Location is reported correctly via wifi.
    Screen no longer rotates when docked.


    Credits:
    The rest of Team EOS.
    AndroidRoot esp. RaYmAn and Bumble-Bee for helping with the device tree in particular with sound. (Also for all the other great work AndroidRoot have done with this device).
    aremcee (Ricardo Cerqueira) of Cyanogenmod for fixing the OMX issues. (Camera/YouTube)
    Everyone else who provided feedback.
    26
    Thanks ;)
    Well if I had the time I would, but really time is lacking.
    That's why I think having RaymanFX on our side is good, he has a lot of free time. :)

    But since I lack time, I prefer to do a few things right, instead of too many things wrongly ;)
    The K.A.T app is already way behind schedule currently, so yeah. That was supposed to be my next main update,
    but not sure anymore now.

    I'd just personally prefer that the TeamEOS rom doesn't take a turn I won't like.

    Tim, it took me some time to rethink my new strategy.
    Right now, i think I made a decision. I will revert all my commits regarding the tf101 vendor and tf101 device tree and just improve the old one with the needed fixes for 4.2. Would you like to help me with EOS? I mean, working on gerrit. Like a clean, working teamwork.
    25
    Timduru and me are making great progress :)
    Seems like my code and logcat digging-weekend were successful, cause we got both cams to work now !
    Left will be bluetooth ...
    24
    And Bluetooth is now working in 4.2.1 :D

    There's mostly HDMI & surfaceflinger eating the cpu left to fix & a few non critical features to add back.
    But besides that I think everything should be fixed now :)

    It's pretty usable I'd say now if you don't need hdmi that is ;)
    with a tiny bit power lost because of surfaceflinger atm :)