yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] mgeniusm:
problem

The only problem with this rom is that there are no problems! I'm getting withdrawal symptoms from not flashing a rom for weeks! It's the same story with my phone can't find any reason to flash!
[Eee Pad Transformer Android Development] Badbullet:
Try to clear data in settings /application or reinstall gmail from play store.
[Eee Pad Transformer Android Development] Badbullet:
Just find and try new update for gallery and camera apk which is installed on HTC one and galaxy 4 google edition, works fine, photosphere too.

Just for case backup your old gallery apk with titanium backup

Install Newcameraapp. apk

Reboot your device

Download

http://db.tt/imvGE555
[Eee Pad Transformer Android Development] garyngkt:
I am testing out this LagFix app, when I click Run there are no messages/status, not sure if it was running anyone having this issue also?.

Thanks.
[Eee Pad Transformer Android Development] wilkster:
Lag fix just hung on my tf101. I don't recommend risking it.

Sent from my EOS JB TF101
[Eee Pad Transformer Android Development] edd080:
I used lagfix a couple of times, it does take quite some time as stated in the description of the app, but it completes successfully. Never had any problems..
[Eee Pad Transformer Android Development] easypanic:
Had that too.

I needed a replacement cable.. :-\
[Eee Pad Transformer Android Development] csb5731:
I gave it over an hour, and nothing happened beyond the start/run button greying out and the fstrim or whatever msg, no notice of completion or anything. From what I gather, there should be some sort of msg.
[Eee Pad Transformer Android Development] *Detection*:
Lag fix says nothing until it is finished with a partition, then it moves onto the next one and gives a small message saying it has finished the previous one

Takes a long time to run
[Eee Pad Transformer Android Development] jonse01:
New camera app work great here as well, now i have working pohotosphere happy days.

Had to get apk from here though... One above wouldn't install...

https://docs.google.com/file/d/0B_fGBfBq-dl2M21QVk5Eb0JDQ0E/preview
[Eee Pad Transformer Android Development] mgeniusm:
new camera

Installed OK here
[Eee Pad Transformer Android Development] csb5731:
This one worked for me, the first one gave me issues too.

It's been a long time since I tried photosphere, it's not perfect of course but it works 10X better than it did when in the early 4.2 builds on my TF. Pretty cool.
[Eee Pad Transformer Android Development] *Detection*:
Boot animation from Google Play Edition Galaxy S4 and HTC One

EDIT - I've edited the images and removed the word Google from the animation, but even with no compression (Store method) and correct permissions, I just get a black screen on boot, maybe someone else can fix it

http://hostr.co/KEvG7ckql2nr
[Eee Pad Transformer Android Development] cecilyen:
I have lost my WiFi connection constantly in recent update, maybe after build 100 or so. It was quite stable before. I either have to reboot my system or kill wpa_spplicant to fix this issue. Anyone got the similar issue as me? By the way, I was always using the latest kk kernel.
[Eee Pad Transformer Android Development] a.mcdear:
I don't have any of those problems... Maybe try a full wipe with the latest build?
[Eee Pad Transformer Android Development] mgeniusm:
wifi

no problems with latest build but then again never had wifi problems so maybe a full wipe will help.
[Eee Pad Transformer Android Development] RaymanFX:
Hi all!

Today, I have to make a somewhat sad announcement..

This is the end of Team EOS and thus the end of EOS ROMs.

Since there were only three active EOS 'core developers' left, rlasalle15, bigrushdog and me, RaymanFX, decided to move on and become part of Team Codefire, merging parts of our code into the CodefireX rom. We are currently merging all EOS devices into codefire, and so the TF101 will get a CodefireX build soon. I set my early-deadline for this weekend.

I myself am very sad letting EOS die, but just three active developers were too few to support the huge device- and codebase we have right now.

CodefireX will be a good new home to us and you, the community. It makes use of the newest toolchains avalable and comes with TONS of under-the-hood-optimizations.

You will also be able to find tons of UI-customization, even more than in EOS. What is especially awesome about CFX, is that you can decide whether you want the pure vanilla android experience or the customized CFX experience with just one 'tap' in CFXSettings. Your needs should be fulfilled either way :) .

Special note regarding TF101: Since I don't know where timduru is hiding atm and failed to contact him, I will prepare the first CFX build for the TF101, still having my device right here. We moved him over (or let's say we invited him to join us in CFX), hoping he will continue his efforts for the TF101, we'll see what is gonna happen after I can reach out to him. But for now it seems like I have to re-activate my TF101 capabilities and start the tablet work more actively again. The EOS kernel will be left untouched though, as long as I don't see any urgent needs to update it (maybe a few SOD/RR fixes will be released in form of a seperate kernel I plan to compile), but the default CFX kernel will stay EOS.

EDIT: further information will be provided by [MENTION=470268]bigrushdog[/MENTION]

Want to hang out with us? Join us on IRC (freenode): ##codefirex

Want to see the interactive changelog/homepage? http://codefirex.com/

Want to contribute? Our GitHub is right here! https://github.com/codefireXperiment
[Eee Pad Transformer Android Development] frederuco:
Thanks for the update [MENTION=3463426]RaymanFX[/MENTION].

We will be looking out for the new CodeFireX ROM.
[Eee Pad Transformer Android Development] st0nedpenguin:
Hopefully CodefireX will be in a better state on the TF101 than it is on the DHD right now. :(
[Eee Pad Transformer Android Development] brgroover:
I got scared before reading that development would continue
[Eee Pad Transformer Android Development] renmo:
will move over to codefirex and follow you and the team there , thanks for all your hard work in the past and future :highfive:

i asume there will be a new thread for codefirex tf101 ?
[Eee Pad Transformer Android Development] fredme:
I have exactly the same wifi problem. I am about to return to an earlier build.
[Eee Pad Transformer Android Development] *Detection*:
Looking forward to it, sounds pretty exciting, TeamEOS have given us a load of great builds, can't wait to see what CFX brings us too
[Eee Pad Transformer Android Development] bigrushdog:
Lol. That's cold! But funny! I assure you it will be. It's probably fair to consider cfx a new project from here. I'll tell Synergy to get DHD together.
[Eee Pad Transformer Android Development] zboq:
That's very good news. But if you guys are going to use aroma, then I guess you will have to update recovery for tf101 first :)

Wysłane z mojego HTC One
[Eee Pad Transformer Android Development] mgeniusm:
thanks

i would like to take this oppertunity to thank all those that were involved in making the EOS rom for the tf101 so good. I really hope you manage to get Tim to join you in the new team!

I am looking forward to seeing a new rom and to see what you will be doing to improve on what was a truly awesome rom!

Thanks guys

p.s one thing I really hope is that the forum for the new rom will be just like this one! friendly, helpful and generally a pleasure to logon to each day!
[Eee Pad Transformer Android Development] timduru:
Uh ?

As it has been answered a few times, I'm still on vacation for a few weeks in US, and my DSL is out at home, so yeah.

As for failing to contact me , I have not seen you even try, so yes if you don't try it'll fail of course ;)

You have my email, and can PM here that's usually what works.

Anyway, I'm tired of all the crap, and seeing that I'm considered 'inactive'

and that my opinion doesn't count before deciding to drop EOS or whatever has been decided

I'll just keep doing my things and leave EOS and not join CFX.

My 2 cents is that considering that the current 4.2.2 version of EOS on the TF101 is quite stable,

maybe it was not the best time to move to another rom.

Going through all the process of debugging the new base and all with TF101, no thanks.

Waiting for the next android version jump could have been wiser imho.

As there are always work required with such jumps anyway.

But anyway good luck !

Nah, you forced subscribed and spammed me with a bunch of git subscriptions, that's not 'inviting' to join

Inviting also goes through talks and opinion exchange *before* moving usually too.

Good luck, and maybe you'll stay focused on the TF101 for more than a few days this time.
[Eee Pad Transformer Android Development] RaymanFX:
To be fair from the beginning, I sent you an eMail.

If you don't read of course, I will fail.

Next, I hope you know I have worked on the TF101 at least as long as you have, if not longer.

I just didn't see any need to be more active here, because I consider EOS4 as stable as possible - just as you do.

Oh and in case of 'real' development, I have asked you more than one time for help, or rather speak a joint kernel work to *finally* bring the 3.1.10 kernel to the TF101, but you obviously didn't want to. You rather had your work on katkernel and such, which I respect, but the 3.X kernel (with cardhu drivers) would be the gate to a better future for the TF101. You refused, not me. And I don't have enough time to do all the work on my own.

Seeing all you ironic statements and the wave of hate here I think it really might be better for us not to work in the same team anymore.

Well, 'team' - as you said, needs a lot of communication. Where have you been? It was like the last 8-9 weeks I heard literally nothing from you. It was randall, ryan and me keeping EOS up and pushing code.

Anyways, I want to end this discussion at this point. You don't have to join us, nobody forces you.

We kindly invited you to the GitHub group, thus leaving the decision up to you - one click and you wouldn't have received all these notifications at all.

EOS roms are still on the server - nobody will ever force anyone to use CFX. I just thought EOS was a really nice team, with capable people and it would be worth to re-unite them under a new flag. Turns out not everyone thought this way..

Well, as I said, no further discussion on this here.

I honestly do wish you all the best for the future and your android projects (no irony this time).

You'll be able to make a real difference with the skills you acquired. Goodbye, Tim :)
[Eee Pad Transformer Android Development] wilkster:
External SD Card Remount

I am running latest EOS + KAT Kernel. I recently bought one of the ASUS external SD card adapters to view camera photos on an SD Card. When I plug in the adapter with an SD card it automounts correctly as /storage/usbdisk0 and I can see files just fine. When I remove either the SD Card or SD+Adapter I get the SD Card removed notification "Removed SD Card" and if I plug it back end the notification goes away, as expected. However after reinsert the SD card I can no longer see any files on the SD Card either through a file manager or from a terminal (ls). I have to reboot to get back to the SD Card.

Am I doing something wrong here? Has anyone seen this?
[Eee Pad Transformer Android Development] bigbubbamcgee:
What a disappointment to see EOS work coming to an end and especially with the jabs being poked back and forth now. How sad that this has happened, just as I've witnessed with so many other ROM collaborations over the years. I know that I don't want to see flaming comments on this thread and I hope that something amicable is accomplished in seeing development continue at some strong level for the TF101.

I personally don't think I will be flashing a ROM with another base and that doesn't have the strength of Timduru's handiwork. It will be like starting all over again with all the bugs and lack of stability. The EOS ROM is so rock solid and has made my Transformer so awesome. Thanks for the work... and the memories!
[Eee Pad Transformer Android Development] timduru:
didn't get anything.

You could have tried another way like IM or PM here.

You can also check my message history here and see that I still read and post, so no I had not disappeared.

And anyway why is it you who would contact me about that, you're not in charge of the rom...

Just a slight reminder: it's stable because it was brought to that point. It was not the case back in december and a lot of work was needed.

You supposedely commited to help me on the TF101 part back then.

I'm sure all the old timers here will remember that,

and that I had only accepted to take on the task under the condition that we work together on the TF101 part, but you simply vanished after a few days.

So yes excuse me when I had to deny your request to work on your 3.1 kernel, I for one prefered to keep my word and work on EOS4 even though the original condition was not fullfiled.

Anyway I hope most users are not blind here and will make their own opinion of what happened here based on facts and not on BS.

Anyway to all those who appreciated my contributions to EOS,

I'm sorry but when working on a rom becomes such a pain, it's time to say goodbye.

I might or might not come back on the rom side.

Most likely not before the next major android version.

In the meantime I'll most likely resume work on Kat* when I'm back from vacation with DSL working ;)
[Eee Pad Transformer Android Development] just lou:
Wow. Didn't expect EOS to die in a civil war. :(
[Eee Pad Transformer Android Development] bigbubbamcgee:
I know that I stand behind you 100%. I have been an avid follower of TeamEOS and your work in making the Transformer rock solid since day 1. My user profile doesn't show it since I was a lurker for many years to this site. But, I have read through this development thread every single day with anticipation like a little kid in a candy store for what was going to happen next.

Sadly, I still just don't see the need for EOS to die off or be transferred to another base. And, I just don't see the sense in all the banter of the what someone did or didn't do. It's sad to see you saying goodbye Tim! Thank you for your hard work and I really look forward to seeing what you come up with next in development when you get back from vacation.
[Eee Pad Transformer Android Development] csb5731:
EOS4 + KK has made the oldest of my three android devices into my favorite device, hate to see it go. My TF works like the device it should have been, it's several times better than new, I wouldn't trade it for my sister's Prime and I often wonder why I bought the Nexus 7. I enjoy occasionally flashing other ROMS, just to check things out, but in terms of stability and fully-baked features I haven't experienced a ROM that comes close. At this point in time I can't imagine daily-driving anything else, it's by far my favorite ROM (on all devices).

I appreciate all the work put into EOS4, and certainly remember the tremendous amount of improvement made to the performance of the ROM back in it's early days. It went from kind of usable (I was skeptical that the TF could run 4.2 properly) to great in short order, and I certainly remember the feverish pace of Tim's updates and his saint-like responsiveness to everybody's issues/findings. The TF101 for a lot of us would be a drastically different device were it not for Tim's work on both the ROM and kernal side.

I'd also be remiss not thanking BigRushDog or whoever was responsible for some of the recent changes in the EOS Control Center. It's just so polished.

Really sad to see it go.
[Eee Pad Transformer Android Development] bigrushdog:
RaymanFX appears to have jumped the gun a little regarding announcing any changes. There is no "civil war". Nobody is mad at anybody. I don't tolerate that kind of behavior regardless of team flag. Everything that made the Eos build great will be in the new project, including Timduru 's fantastic device tree and kernel.

Besides, Timduru and RaymanFX have always fought like little girls. Nothing new!

So don't start freaking out people! Have a beer. Eat some medibles. Relax. Complain about SOD. It's business as usually. I've spent the last 2 years building a user base of about 50,000 people. Do you guys really think I'm gonna hang you out to dry? Common!
[Eee Pad Transformer Android Development] jazzruby:
[MENTION=3951330]timduru[/MENTION], I just want to say a big THANK YOU for your professionalism as a ROM dev on Team EOS, in this thread and on Android in general and hope you (re)consider the TF101 when Android OS is updated :fingers-crossed:

[MENTION=470268]bigrushdog[/MENTION], What can I say? I anticipate each and every one of your posts; your talent and wit is much appreciated. Thank you for your work with TF101.

[MENTION=3463426]RaymanFX[/MENTION], While you have been sparse in this thread, I have seen your contributions behind the scenes and for Android in general, and for that I thank you much.

I will follow all of you and your future projects, good luck and thanks.

-JR-
[Eee Pad Transformer Android Development] JimTDI:
I'd like to encourage Team EOS to reconsider this decision. The pace has been frantic, and that tires people out.

It's summer, and maybe a vacation is in order for the "team". Take a rest, talk amongst yourselves, email, IM, etc., maybe you can all reach an agreement, and Team EOS can continue together.

All I can say is thank you all, my Nexus 7 sits on the shelf, and my TF101 gets used daily.
[Eee Pad Transformer Android Development] Gatak:
What's the new XDA thread for the TF101@CFX? :D
[Eee Pad Transformer Android Development] walkerx:
I'm trying to finally download the rom for my TF101 - can anyone advise if there is a problem at the moment as says it will take 12 hours to download
[Eee Pad Transformer Android Development] csb5731:
When Goo is REALLY slow I find a post by the user "Detection" and look for the mirror-link in his footer.

http://xdaforums.com/showpost.php?p=43047599&postcount=5762

It's usually pretty fast.
[Eee Pad Transformer Android Development] walkerx:
Cheers that's saying 16 hours
[Eee Pad Transformer Android Development] sidneyk:
@timduru - I noticed that with #89 and gapps 010513 with your 70b kernel that sometimes the dual battery widget I use seems to be having issues with second (dock) battery. After a period of deep sleep I know there is the issue of having to undock and redock to get the second battery status back, but since #89 with your kernel it isn't always working even with multiple attempts. Also, the tab doesn't seem to be deep sleeping as much as it should be. I know that it could be some of my apps causing it, but I haven't really changed my apps much since the previous builds. For now, I have reverted back to the stock kernel, with the same OC settings I was using with yours and the dock battery seems to be getting detected better between sleep cycles and docking, undocking. I'll watch it for awhile and let you know if I'm for sure seeing a definite difference. Thanks.
[Eee Pad Transformer Android Development] timduru:
What we list is basically what doesn't work.

From there what actually works is everything besides what is known to not work. ;)

How is that complicated ?

Maintaining an up to date list of everything that works would be quite dumb and unmaintainable.

So to know what doesn't works you have 2 choices:

- use the summary I post all the time and that can be found in my SIG

- use teameos bug tracker

or both as not everything is in the bug tracker, and you don't have the workarounds ;)

So besides the recent additionnal headache with the gapps and the different combinations that are possible depending on what you prefer to use.

The rest is already listed, precise and concise.

I tried also to list in a precise way which gapps gives you what in my previous post:

http://xdaforums.com/showpost.php?p=36436139&postcount=530

Also keep in mind that as this is still in heavy developpement it is changing and evolving all the time, creating headaches like you see with gapps where you need to simply read 4 lines to choose what you prefer until we find a solution.

If you prefer not to bother then just flash the latest gapps which bring you up in coherence with the Know issues listed in the list I maintain.

(ie you need to deactivate autocorrection for the soft keyboard)

Sounds quite easy to me :)

Basically:

flash latest rom version + latest gapps and read the known issues.
[Eee Pad Transformer Android Development] i9apps:
Hi timduru,

I have a great idea for you, you can add an option to remove only the on-screen buttons

With this added to build.prop "qemu.hw.mainkeys=1" (thanks to xuser)

The only problem i find its somehow make the menu button to

disappeared in some apps (like on the browser)

The best thing is that once you hide the on-screen-buttons the system just flew and the launcher work perfect! And you still enjoy the status bar

If u can fix just the menu bug this feature would be perfect and i think a lot of members will enjoy this..
[Eee Pad Transformer Android Development] timduru:
Ah I see, well it's easy then, if you want the most stable and usable and most compatible components,

that's simply what is listed in the 1st post now. :)

This is what is "compatible" and officially supported.

And what the known issues & workaround list tries to be coherent/updated with.

The rest of the thread is here to try to progress more quickly and proposes a few alternatives in case the package of the compatible components listed in the 1st thread doesn't fit you fully.

You then have additional choices:

- gapps: the latest version should have photosphere and everything fixed, besides the autocorrection,

so if the autocorrection feature is more priority than the others that are fixed in the latest official gapps linked from the 1st message, you can fallback to an older one that supports it.

- Kernel: just like before with other roms out there, you can choose to flash an alternative compatible kernel.

These other alternatives are not official and not officially supported.
[Eee Pad Transformer Android Development] i9apps:
Timduru,

Can u please refer to my idea :( ^^^

i think all of us would love to see our device work like this (Stutus Bar is on and the launcher working perfect)
[Eee Pad Transformer Android Development] asdfzz:
You can use full screen apk it will disable nav bar and save your settings... Just few kb

Status bar will stay
[Eee Pad Transformer Android Development] i9apps:
I know but its for some reason "brake" the menu key on some apps...like on the stock browser..

If u have a solution i would love to hear.
[Eee Pad Transformer Android Development] timduru:
NTFS

For the few who have the NTFS usb sticks / HDs that don't mount.

Could you install the KatKernel 4.2_70b

Insert the drive, wait that the rom says that it can't mount it.

Then install the attached version of the K.A.T app

Launch the app

make sure you give the root access.

Go to Storage menu

Click on mount(auto)

If it doesn't work Try to click on mount NTFS with full write

post the results + grab logcat if it doesn't work.

Then try again after a reboot, see if it's different.

@i9apps: yes, ideally that should be an option in the settings to hide only the navbar.
[Eee Pad Transformer Android Development] MAO2200:
Timduru Sorry, but I have a big problem with the wifi. He consumed 20% battery in 6 hours of operation without using the tablet. Use your latest Kernel and EOS 89. I turned off auto-rotation for some time, ever since I put on the 4.2.

Thank you, for me this is a big problem, the battery should last me at least a day with heavy use.