[ROM][JB 4.2.2] [Team EOS 4] [Nightlies -- TF101]

Status
Not open for further replies.
Search This thread

doppelhelix

Senior Member
Jan 29, 2012
1,095
755
Hamburg
OnePlus 3
OnePlus 6T
I think that both sides have to share the blame. RTFM is always a good idea. On the other hand, this thread is over 6000 posts long. And releasing a somewhat crappy nightly#121 after announcing the end of EOS development was really a stupid idea. Now everone new to this ROM won't see how well crafted it actually is. Just my two cents.
 
Last edited:
  • Like
Reactions: wilkster

JimTDI

Senior Member
Jul 30, 2011
187
63
Saint Paul, MN
121 have boot problem and this thread is closed , why not try to install Timduru KatKiss ROM

Inviato dal mio Transformer TF101 con Tapatalk 2

That's the problem, this thread is NOT closed.

It was a slap in the face to all of us EOS4 users to announce Team EOS4 was dissolving/breaking up (while Timduru was on vacation), and then releasing Build 121 a few days later.

Build 121 seems to have major problems, for a majority of those who tried it, and not ONCE did I see anyone from the now defunct TeamEOS come back to this thread to provide support for this borked release. Almost like the members of TeamEOS who decided to bail played a very bad joke on us users.

Thankfully 1 member of TeamEOS (Timduru) carried on the TeamEOS code, and continued development with the new KatKiss ROM.

I suggest 2 things:

1.) Close this thread!

2.) Refer users to the new thread/Rom for KatKiss here on XDA:

http://forum.xda-developers.com/showthread.php?t=2362764

Come join us there!

Thanks to Timduru for keeping the legacy of TeamEOS alive in KatKiss, and improving our TF101s even more. Tim is a gentleman, and truly a class act from every indication I have seen.



Sent from my Transformer TF101 using Tapatalk HD
 

just lou

Senior Member
Dec 8, 2010
2,085
732
New York
That's the problem, this thread is NOT closed.

It was a slap in the face to all of us EOS4 users to announce Team EOS4 was dissolving/breaking up (while Timduru was on vacation), and then releasing Build 121 a few days later.

Build 121 seems to have major problems, for a majority of those who tried it, and not ONCE did I see anyone from the now defunct TeamEOS come back to this thread to provide support for this borked release. Almost like the members of TeamEOS who decided to bail played a very bad joke on us users.

Something is definitely going on and not right. After the apparent breakup of TeamEOS, "they" release a new version that is by far the most problematic version or EOS ever, and for most won't even boot. And since it's release, not a peep out of anyone responsible for its release. It almost seems like it was released for spite or to kill EOS. What a fiasco ending for the ROM that kept people's TF's alive past its prime.
 
  • Like
Reactions: philseven

mgeniusm

Senior Member
May 24, 2012
520
201
69
Hanita
www.hanita.co.il
bigrushdog

I honestly thought bigrushdog was a good guy! he kept things moving while tim was away. I don't understand why he doesn't remove 121! I for one appreciated his input and whit during that period and if he reads this then please do something about the fiasco that has become EOS. close this thread with a note stating that team EOS is no more and point people in the direction of katkiss.
Than you!
 

csb5731

Senior Member
Jan 6, 2012
156
33
Now everone new to this ROM won't see how well crafted it actually is.

I agree. So many posts/threads proclaiming/opining EOS4 to be the ultimate TF ROM in the general and QandA sections, and for good reason. It is concerning that people new to flashing might be walking away from the experience wondering if they have a bad tablet, that ROM-flashing is voodoo, or that those EOS4 fans were crazy/trolls/goof-balls with low standards. A soft-brick is NBD to most of us (and expected when on the cutting edge), but to someone new to this and with the expectation that the ROM is solid/DD-worthy, I imagine it can be an off-putting experience. I can't imagine why the 121 ROM is still up.

EOS3, then EOS4, and now Tim's Kat Kiss offshoot have literally turned my tablet from an OK budget device into one that I am extremely happy with. I hope that other people will be able to experience the satisfaction of having a better-performing and more contemporary device.
 

shonkin

Senior Member
Oct 15, 2012
1,453
584
Can we just ask -- bluntly -- that the EOS 121 be removed? Totally agree w/ previous posters that previous versions were golden and made pretty much all of us end users smile large. Timduru's new KatKiss carries on the best of the EOS and leaves 121 alone. Again, PLEASE someone remove 121.

Asus Transformer TF101 16g [BCOKAS] / 1.2ghz overclocked
EOS 4.2.2 Jellybean / KatKiss-4.2.2_220 /
Kat Kernel #105 / Kat App / Apex Launcher
--
Don't blame Jesus for the Republican Party. Blame Ayn Rand.
 

scottyf79

Senior Member
May 1, 2011
1,639
578
United Kingdom *****ez.
Team EOS owe nobody a thing. Personally find it astonishing that folks have the notion to slam them for 1 slightly off version of the build - which simply needs Kat kernel flashed on top of it to get it to boot. (trial and error fixed it for me......yeah you have to think for yourself sometimes btw - shock horror, what you mean i have to wipe my own arse???)

A bad build can happen anytime - and if your gonna sit and cry like a baby when summit doesnt work then you a) never rooted the TF yourself or b) shouldnt have. Its a development forum - its not stock Asus firmware, its a "if this rom chews your cat then thats just tuff titty - but youve been warned" situation. You take the chance and pray you dont screw it yourself or have it screwed by even the smallest error by the dev.

LEARN how to fix things yourself - best thing you will ever ever do if your gonna do **** to your mobile devices that your not really meant to do in the first place! Aaaaaand the penny drops.

So they disbanded - and then? aaaand then? and then and then and thennnnn?

Get over it. People have lives away from making **** for us for FREE out of their OWN TIME.

Timduru is doing a fantastic job but at some point he will move on......we gonna have to sit through this mince again? Go back to stock firmware with even less support if your that unhappy - or like EOS - MOVE ON.:good:
 
Last edited:

just lou

Senior Member
Dec 8, 2010
2,085
732
New York
Team EOS owe nobody a thing. Personally find it astonishing that folks have the notion to slam them for 1 slightly off version of the build - which simply needs Kat kernel flashed on top of it to get it to boot. (trial and error fixed it for me......yeah you have to think for yourself sometimes btw - shock horror, what you mean i have to wipe my own arse???)

No. For most, flashing Kat Kernel is not the solution to getting 121 to boot. I've never even attempted to flash it without Kat Kernel, and it still wouldn't boot.


Sent from my Nexus 7 using xda premium
 

scottyf79

Senior Member
May 1, 2011
1,639
578
United Kingdom *****ez.
No. For most, flashing Kat Kernel is not the solution to getting 121 to boot. I've never even attempted to flash it without Kat Kernel, and it still wouldn't boot.


Sent from my Nexus 7 using xda premium

Well the simple advice would be - flash something that works instead of sitting like a little sulky kid. (not you personally as you seem to have a bit of common sense from your posts lol)

The point is that its pretty grim that folks are whinging about EOS considering all the work they done up until now.
 

JimTDI

Senior Member
Jul 30, 2011
187
63
Saint Paul, MN
Team EOS owe nobody a thing. Personally find it astonishing that folks have the notion to slam them for 1 slightly off version of the build - which simply needs Kat kernel flashed on top of it to get it to boot. (

Yeah.. that's it. We all forgot to flash the Kat kernel.

Not slamming Team EOS - I truly do appreciate all of their work, but why would they announce they're broken up, then release another version a few days later, and not take it down or respond to the multitude of people who all seem to have a problem with it.

It felt a little amateur, maybe even premeditated as someone here pointed out, like they wanted to destroy EOS.

You're entitled to you opinion, and myself to mine, but it's CERTAINLY more that "we forgot to flash the kernel".



Sent from my Transformer TF101 using Tapatalk HD
 
Last edited:

scottyf79

Senior Member
May 1, 2011
1,639
578
United Kingdom *****ez.
Yeah.. that's it. We all forgot to flash the Kat kernel.

Not slamming Team EOS - I truly do appreciate all of their work, but why would they announce they're broken up, then release another version a few days later, and not take it down or respond to the multitude of people who all seem to have a problem with it.

It felt a little amateur, maybe even premeditated as someone here pointed out, like they wanted to destroy EOS.

You're entitled to you opinion, and myself to mine, but it's CERTAINLY more that "we forgot to flash the kernel".



Sent from my Transformer TF101 using Tapatalk HD

Didn't say anyone "forgot" as you wrongly put it just to clear that up.
Flashing the kernel was a solution that fixed 121 for me.

Anyway.....a borked build is hardly tantamount to sabotage. Drama.

Moving on - Eos is dead - end of.
 

JimTDI

Senior Member
Jul 30, 2011
187
63
Saint Paul, MN
Didn't say anyone "forgot" as you wrongly put it just to clear that up.
Flashing the kernel was a solution that fixed 121 for me.

Anyway.....a borked build is hardly tantamount to sabotage. Drama.

Moving on - Eos is dead - end of.

Well you implied that we were inexperienced, and that all we had to do to fix it was flash Kat Kernel, and that we should know how to recover. I knew how to recover, but other users did not. Glad you were able to get it to work - many others were not so lucky.

As you point out EOS is dead. We just want to try to help others from borking their TF101s by getting the word out about Build 121, and getting that build pulled from Goo.

Have a good day!


Sent from my Transformer TF101 using Tapatalk HD
 

shonkin

Senior Member
Oct 15, 2012
1,453
584
I don't think anyone is dissing Team EOS. Agree totally that us end users who've benefited from their hard work should be respectful and even thankful!

But that said, it would be very nice if the last iteration of the ROM was removed from all servers (at least those Team EOS posted it on).

This pony, however, is probably dead. If folks love EOS and are content, install a later but not last version of it. If folks want to keep up with an actively developing Rom, Timduru's KatKiss is there for them (us).

I have no bad words for Team EOS. "And that's all I have to say about that!"

Asus Transformer TF101 16g [BCOKAS] / 1.2ghz overclocked
EOS 4.2.2 Jellybean / KatKiss-4.2.2_221 /
Kat Kernel #105 / Kat App / Apex Launcher
--
Don't blame Jesus for the Republican Party. Blame Ayn Rand.
 

csb5731

Senior Member
Jan 6, 2012
156
33
I don't think anyone is dissing Team EOS. Agree totally that us end users who've benefited from their hard work should be respectful and even thankful!

But that said, it would be very nice if the last iteration of the ROM was removed from all servers (at least those Team EOS posted it on).

This pony, however, is probably dead. If folks love EOS and are content, install a later but not last version of it. If folks want to keep up with an actively developing Rom, Timduru's KatKiss is there for them (us).

I have no bad words for Team EOS. "And that's all I have to say about that!"

Asus Transformer TF101 16g [BCOKAS] / 1.2ghz overclocked
EOS 4.2.2 Jellybean / KatKiss-4.2.2_221 /
Kat Kernel #105 / Kat App / Apex Launcher
--
Don't blame Jesus for the Republican Party. Blame Ayn Rand.

Agree. Not dissing, certainly don't think they owe me anything. I am ever-so-grateful to the past EOS teams, these ROMs transformed my TF from an OK device into a great one.

I don't suspect sabotage, though I have to admit to some confusion.

I don't expect the device to be supported forever, by Tim or anyone else.

I think most people are just pointing out that a lot of problems could be prevented with a relatively little trouble. We want to spread the word as to how great these ROMS are, and have others realize what these ROMs can provide to their device. I don't want people leaving thinking the EOS ROMs in general were sketchy, when I feel so much that they were entirely the opposite.

I don't care if I soft-brick my tablet, to be perfectly honest.
 

scottyf79

Senior Member
May 1, 2011
1,639
578
United Kingdom *****ez.
Well you implied that we were inexperienced, and that all we had to do to fix it was flash Kat Kernel, and that we should know how to recover. I knew how to recover, but other users did not. Glad you were able to get it to work - many others were not so lucky.

As you point out EOS is dead. We just want to try to help others from borking their TF101s by getting the word out about Build 121, and getting that build pulled from Goo.

Have a good day!


Sent from my Transformer TF101 using Tapatalk HD

There was no implication about experience either but never mind.

***DO NOT FLASH EOS BUILD 121***

IF YOU HAVE FLASHED IT AND ARE STUCK IN A LOOP - FLASH ANOTHER ROM or PREVIOUS VERSION.

IF YOU DONT HAVE ANOTHER ROM DOWNLOADED TO FLASH - GET A MICRO SD AND ADAPTOR FOR YOUR PC/LAPTOP AND DOWNLOAD ONE FROM THERE ONTO THE MICRO SD THEN INSERT INTO YOUR TF

Assuming you know how to use the version of recovery you have then you should be able to locate the micro sd and the downloaded file to now flash a working rom

If you dont then get reading.

*** NOTE - remember to download a suitable gapps package and suitable kernel also if required

This message is not intended to question your experience - just your common sense

Thanks​


Bit better than folks moaning :p
 
  • Like
Reactions: dgcruzing

dgcruzing

Senior Member
Nov 21, 2010
1,173
322
Mermaid Beach QLD
The youngster of X team EOS is a kid..
And has left a number of unfinished projects on this hardware..

Cant beat maturity. .as it brings a sense of responsibility.

You have been warned about the last update..flash at your own risk..

+100 that it should be removed and or 1st thread should be updated to show that it is unsupported..



Sent from my GT-I9300 using Tapatalk 2
 
  • Like
Reactions: philseven

bigrushdog

Inactive Recognized Developer
Apr 23, 2007
3,547
7,244
I'd like to invite you guys to an open discussion about our new project

http://forum.xda-developers.com/showthread.php?t=2372197

It's in the Xoom board but so what lol. I know there's been some confusion lately and for that I apologize. I try to answer some questions I've seen and provide guidance on what to expect going forward. I'm glad to see Timduru carrying the Eos torch. He will be helping me with the new project too. He may not know it yet though :p:p:p

I have a personal interest in making sure tf101 users are well served with the new project. Not only because tegra2 is becoming more difficult, but because tf101 users, in large part, massively contributed to the success of the Eos project.

Please stop by the thread and at least read my opening statement. It should shed some light on the current state of affairs.

Thanks guys and gals!
 

tamthanh

Senior Member
Nov 10, 2010
89
17
after installing version 120 and 121, my TF101 does not see micro SD card, it is always notified blank or corrupted memory cards. while the previous version or Paranoid rom seem to be normal :confused:
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 276
    attachment.php
    Asus Transformer TF101 Nightlies​
    JellyBean 4.2.2​

    Continuing on from the success of the EOS ICS&JB roms, we present to you EOS4, based on the latest JELLYBEAN version!
    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.

    EOS 4 is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.

    For the latest news on Team EOS Asus Transformer releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom or #teameos.

    bigrushdog said:
    Ok guys, final post. But the adventure continues!

    The last solid Eos 4 build is #120

    http://goo.im/devs/teameos/roms/eos4/nightlies/tf101/EOS-tf101-20130617-120.zip

    Timduru continues working from the Eos 4 base with his KatKiss project here...

    http://forum.xda-developers.com/showthread.php?t=2362764


    The CodeFireX project is still in general for now

    http://forum.xda-developers.com/showthread.php?t=2375257


    We're (bigrushdog and CodeFireX guys) going balls to the wall getting 4.3 running. So likely next build will be 4.3. So it may be a bit of time still. Watch the general thread for updates and info.

    Eos lives on in KatKiss and CodeFireX!


    brd



    DOWNLOADS:
    • ROM: Team EOS Transformer Nightly builds on goo.im
    • Latest Gapps Package: 4.2.2 Gapps for TF101
    • Older 4.2.1 Eos Gapps for TF101
      If you prefer to have the Swipe feature in the default Keyboard you can use this version, but the Keyboard will crash on auto-correction
      If you use this version, make sure you go the keyboard settings and change these settings:
      + Auto-correction off
      + Show correction suggestions:always hide


      Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps you'll need to flash one of these package after installing the base rom.



    Features & ChangeLogs:
    Because these are nightly builds the included features are constantly evolving.
    The main changes are posted in the wiki: http://code.google.com/p/teameos/wiki/ChangeLog, and are also available from the EOSControlCenter menu => ChangeLog.
    For a comprehensive listing of the changes please visit http://review.teameos.org

    Please not that this version is for the TF101 model only.
    It should work on the TF101G version too but you won't get native 3G support (you can however use PPP Widget to connect to 3G)

    --
    Main Eos Features:
    Eos Control Center, one easy location to control all the customizations.
    Performance Settings & Overclockable kernel
    Battery Indicator Mods & Dock Battery support
    Full Dock keyboard Support with special keys
    Wifi with AD-HOC network connection & creation support
    Advanced power menu with reboot options.
    NX Gesture Navigation Bar
    Custom Quick Toggles Tiles with Brightness & Volume Seekbars
    Softkeys Long-Press Actions
    Custom Navigation Bar Ring Quick Launch Targets
    Status Bar Toggles
    Separate or combined EOS Status Bar & Navigation bar hiding for full screen.
    Status Bar & Navigation Bar Color w/ Project Glass (Auto-Transparency, not the Google Project Glass :p)
    Clock Mods
    T-Mobile Theme Engine
    Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
    Default Volume Control Stream (Ring or Media)
    And more...



    Installation Notes:
    These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL THE LATEST COMPATIBLE ANDROID 4.2 RECOVERY!

    Going to EOS4.2.x from a rom < 4.2.x:
    • Backup everything !
    • Go to recovery
    • Make a full wipe / factory reset
    • format /system
    • Flash the rom
    • Flash optional kernel
    • Flash gapps
    • Wipe cache/dalvik
    • Reboot
    Updating from EOS 4.2.x #XX to #YY:
    You can usually skip the full wipe step.
    If ever you encounter an issue make sure you make a full wipe first before reporting though.


    Bug reports & Contribution:
    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. See post #2 for a detailled how-to report.
    Without 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.


    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.

    --
    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!
    --

    Welcome to Team EOS 4 for Asus Transformer
    98
    Additional info & links

    Nightlies Downloads
    Previews Downloads - Main Info & differences between Nightlies and Previews
    ChangeLog - Changes on teameos gerrit


    How to install
    Tips
    How to report
    What to include in the report


    GPS:
    if it is taking a long time to get a lock or no lock, follow this:
    http://forum.xda-developers.com/showpost.php?p=38368206&postcount=2452

    Google search:
    If the version you're using is crashing when you open Google Now,
    go to Settings => Language & Input => Voice Search
    then uncheck Hotword Detection.


    Other Tips
    .
    75
    Well I'm just on vacation guys... ;)
    I will still be around, no worries, I'm still my user #1, I like to have my TF101 working well ;)
    I now have less than a couple of weeks of vacation left,
    then I'll need to get my DSL back working at home, then I'll see what I do ;)
    So a bit of patience.

    I just still don't understand very well the switch to CodeFire, I didn't really get any convincing explanation.
    Sure it's BigRushDog & RaymanFX's choice to decide which team they want to break or join,
    but I don't really see that move beneficial to the TF101, maybe it can help the phone based devices, I don't know.
    CodeFire rom seems to be mostly for phones.
    But what is of interest here is our device the TF101
    I for one would also have waited that the new rom is fully functionnal before doing the switch so that we could at least try it.
    For the moment it's more destructive and demotivating than anything of benefits.

    I think one important thing has been forgotten in the EOS breaking process: you, the users.
    I for one always try to think about that as my #1 priority.



    As for the close future, as I said before it just seems a waste of time to me at this point to switch while we have a mostly stable EOS4 rom for the TF101.
    I'm not even sure what there is to gain in that rom at all, I for one would like a detailled description of the pro and cons
    and what we have to gain.


    Until then the wisest for me for the moment seems to keep building on TeamEOS 4 imho.
    I will most likely just do like good old time with the previews, and improve from there and publish my own versions.
    Just that it wouldn't be previews of what is coming next this time since EOS is dead. ;)
    I might also revert most of the latest modifications and reboot from Preview 202 with a few added things most likely.
    As noted here by a few others, things seems a bit unstable in the latest nightlies and I prefer to stay as stable as possible, even more when I'm on vacation with the TF101 being my only device ;)


    Not having to work with TeamEOS and having to take in consideration other devices might actually be beneficial for the TF101 actually.
    Whereas TeamEOS4 needs to maintain compatibility for other devices, and as we've seen in the past break things for the TF101 while adding stuff for other devices too, generating delays, or sometime making compromises that are not optimal for the TF101.

    With only the TF101 as a target I can focus on making it better, faster, and with a much lesser painful process than with EOS.

    I can also make things work tighter and more tailored for the TF101 in the rom, integrate more things from K.A.T for example
    like the GPS , finer volume control and so on.
    Things like that that really matter for our device and not bloating the rom with less important things and making it less efficient for our old device.
    There are not really much missing though, for the moment I'm quite happy with the latest EOS4 preview myself

    It just works well and does what I want. :)


    So yeah, no worries it's not the end, we'll still have roms for the TF101. :)
    There are currently more roms than we ever had before, so it might be even time to try them and/or contribute to them.
    I kinda like the way PA is doing things myself, as I've said early in the EOS development and the PhabletUI lag issues, the window manager is really sh*t, and I kinda like that PA has rewritten part of it. I might havve a look at integrating part of that work, as it might be of benefits for the TF101.
    I'm unsure yet which strategy could be the most efficient and best for the device.
    It might also depends how quickly Android 5.0 comes out.
    4.3 seems to be mostly very minor changes..
    So we won't really need to bother with that imho.
    41
    New preview version B145

    Rom Download: EOS4.2.1-tf101-20130126_previewB145.zip
    DockBattery update: B145_DockBatteryV3.zip
    (flash after the B145 rom)

    Most had been merged into #93 before,
    so that version should be up to version #93 (see ChangeLog link in my Sig for details of the latests changes)
    And in addition you get:
    - Fix boot issue with stock kernel
    - Dock battery icon/text in statusbar
    - the usual Linaro compilation.
    http://goo.im/devs/teameos/roms/eos3/nightlies/tf101

    Note also that the stock kernel was making the ntfs ro mounting mask differently than with KatKernel,
    so I've also updated the K.A.T app to 1.2.4 to address that.


    Glad to the bluetooth hid problem is line to be fixed now. My log is attached. Happens when I try to sixaxis controller. Used to be working in the cm10 rom i was running.
    Keeps saying it could not set hci raw mode.
    Thanks for the logs. :)

    Actually do you think you could generate logs on CM10 when it is working ?
    As I never had a working BT pad, that'd help to see what might be different and making sure I'm not doing something wrong when trying to make it work here. ;)

    Basically the best way for me to spot what is going on is you to do that on a rom where your device is working:
    - disable bluetooth
    - reboot

    grab a logcat + kmsg (see link in my sig for exact procedure)

    - turn on bluetooth
    - connect your device

    grab another logcat + kmsg (see link in my sig for exact procedure)

    Redo the exact same thing on EOS4.


    i don't know why but when i flash b14* the tablet reeboots and it stops on starting apps window!!!
    damn....i'm on 136 and no issues...but i like follow your job tim!!!
    Try B145, it should be fixed.


    Running 143b and katkernel 80b and just discovered an issue with usb on my tf.
    When I connect my Sony Nex camera to the dock usb port, I can browse pics in ES explorer under storage/usbdisk0/etc..
    But if the tf goes to sleep or if I turn camera off and then on the tf doesnt see the camera any more.
    If I reboot the tf I can connect to the camera again.

    Turning camera on and off doesnt help.

    seems as if something regardin USB fails to resume connection after sleep.

    Sorry, Im not familiar with attaching logs.

    It's the way it works with KatKernel.
    It's normally helping Random Reboots.
    I might have a look again at that later on, but for the moment I prefer to leave it as that as it helps stability.
    So basically if you want your drive back after it goes to sleep,
    - umount it
    - remount it
    Ideally you should unmount then disconnect it before you put the tablet to sleep.

    If you prefer it to remount automatically and that it's a critical feature for you,
    then you are better to stay on the stock kernel I think last time I checked it was ok with it.


    Just a quick shout-out to you tinduru as I notice some of your posts show a bit of frustration from people not reading previous posts and not supplying logcats etc. Those of us sitting pretty with a perfectly running tablet with no issues at all tend to be pretty quiet. The official rom at version 92 shows over 3600 downloads (and I'm sure 93 will break that record pretty quickly) and that doesn't include us preview users which I'm sure is close to a comparable number.
    Can you imagine if over 4000 people had issues with your rom and posted in thread? Right now it appears there's less than a dozen or so people (and I have read every post in this thread too) that either have very specific needs, busted hardware, constantly re-post their grievance, or flat out don't read well.

    The rest of us might chime in once in a while when something major pops up, but please take our general silence as a nod to a job well done. I'm sure many will agree that when it comes to our tablets, you're a frickin' rockstar.

    Thanks :)
    Yeah I hope to think that the majority likes it.
    I know how it works and that there's always a majority of users with issues that are posting in the thread.
    It's normal.
    But yeah it can get frustrating sometime ;)

    So don't hesitate to hit the thanks button either on posts that you find useful
    or at least on the messages where I post a new version like this one.
    That way I know if it's heading in the right direction based on the number of thanks / preview ;)

    The number of downloads is actually quite interesting too. I had not looked there yet, but yeah.
    Especially when compared to EOS3 downloads: http://goo.im/devs/teameos/roms/eos3/nightlies/tf101
    That should definitely mean EOS4 is on the right way :)
    41
    New version KatKiss #215

    Uploaded a new "preview" version #215 :)
    Well technically it's not a preview of anything anymore, hence the new name, and I shall create a new thread at some point too I guess ;)

    Download: KatKiss-4.2.2_215.zip
    md5sum: 477782483338f948a2d22ca6d4c09e91
    More information: http://public.timduru.org/Android/tf101/KatKiss/
    KatKernel is not yet included in that first version, so you still need to flash it after the rom.

    This version is an hybrid between EOS4 PreviewB202 / 120 and new stuff and shouldn't have the EOS4 #121 microsd bug. :)
    We shall see where it leads to in the future, but most likely will stay close to EOS4 as it's mostly good and stable,
    so we can build on that until the next major Android 5 version. :)

    The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keep it Simple Stupid too ;)
    Which means that just like the other K.A.T stuff, the rom's main goal will be speed/responsiveness, keeping things efficient
    while cutting out some of the bloat in the future too.


    Test & Report to confirm that we're back on track and then we can build up on top of that version :)


    ChangeLog:
    =7/11/13 - V215=
    - Critical Security fix for Bug 8219321 (Android apk MasterKey exploit)
    - Browser: Reorg of the pie control + add Pie Feature to go to Bottom/Top of page
    - Include MediaScanner Filters by default (so you do not need to install them from the K.A.T app again after installing the rom)
    - Rom versions change
    - Deactivate GooManager versions to avoid notifications of flashing older EOS4 121
    - Default Kernel interactive threshold decrease for quicker speed boost/responsiveness.