yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] fear_factory84:
Found the problem, opened a bug http://code.google.com/p/teameos/issues/detail?id=207&thanks=207&ts=1353667805

It seems that is microsd card that drains battery.

Anyone could remember me if micro sd is unmounted on poweroff by stock asus roms?

Is there a way to have a rapid shortcut to unmount sdcard without going to settings -> memory?
[Eee Pad Transformer Android Development] AstroTrain:
Has Team Eos released any clues they are working on 4.2?
[Eee Pad Transformer Android Development] Globespy:
Codename secret squirrel.....but hoping for a Christmas gift from Team EOS
[Eee Pad Transformer Android Development] timduru:
https://review.teameos.org/#/q/status:merged,n,z

Should be enough clues ;)
[Eee Pad Transformer Android Development] morphuex:
Schmexy news...
[Eee Pad Transformer Android Development] Nonek:
Hey Tim,

Maybe they were waiting to surprise us for Christmas! Way to ruin Christmas. You were probably that kid who was barely two who snuck down on Christmas eve who somehow got ahold of a pair of Scissors and was gingerly trying to cut the bow off when your mom catches you and takes a picture.... Wait.. that was me.

Heaven forbid she would immediately take the scissors away before I stabbed myself.

Thanks for pointing out the build work...

Looking forward like the rest of us for a new release to patch..
[Eee Pad Transformer Android Development] AstroTrain:
Gotcha, :laugh:
[Eee Pad Transformer Android Development] grgmre:
Sounds like it's getting close to 4.2 time. Exciting.
[Eee Pad Transformer Android Development] chatch15117:
:cowboy::cowboy::o:(:silly::fingers-crossed::laugh:
[Eee Pad Transformer Android Development] skaburn:
sorry guys,

I'm on #81 and kat 55d,

I know that there are milion post like this, but I can't stop my tablet go to sleep of dead, and anyone of them was helpful for me.

the only time I'm safe it's when I use adownloader, in that case I can be sure that the tablet will not stop working.

P.S.: I love your work, you are the only reason why I use my tab until today

thanks
[Eee Pad Transformer Android Development] asder00:
Hey guys how good is your audio in this jelly bean roms?

I think is too low compared to old ics roms, someone could tell me why????

How to fix that? I've tried volume+ etc. apps but the sound get crap like speakers are about to explode -.-

Thx
[Eee Pad Transformer Android Development] skaburn:
tried kat app?

http://xdaforums.com/showthread.php?t=1841851
[Eee Pad Transformer Android Development] akyboy:
got notification that new gaaps are available. i downloaded them and flash them, tried to clean dalvik and cashe 2 times but still getting

Unfortunately, Android keyboard (AOSP) has stopped.

any ideas?

thanks
[Eee Pad Transformer Android Development] xox:
I have your problem. I reinstall the ROM band install the old gaps

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] akyboy:
uh,. no, i cant do that for at least cpl of days,.. have to work with tablet ,....

wonder if i can install some other keyboard?
[Eee Pad Transformer Android Development] *Detection*:
Just flash an older version of Gapps back over the top
[Eee Pad Transformer Android Development] akyboy:
Still doing same :(
[Eee Pad Transformer Android Development] *Detection*:
Flashing ROM #81 over the top will not wipe your tablet and should fix the problem, then flash the last Gapps that was working again
[Eee Pad Transformer Android Development] akyboy:
I will do it now,.. thanks!!!!

---------- Post added at 05:41 PM ---------- Previous post was at 05:37 PM ----------

Fixed!!

Thanks!!
[Eee Pad Transformer Android Development] *Detection*:
:) Good news :)
[Eee Pad Transformer Android Development] nheem:
i don't know why my device is automatic reboot in lastest EOS#81. i try to change kernel and all app and game is lost, it comeback look like i start the rom. :crying:
[Eee Pad Transformer Android Development] skaburn:
Anyone con help me?
[Eee Pad Transformer Android Development] nergrum:
I am having the same issue as you, also running #81 and kat 55d. This has been the best my tablet has every performed, and super smooth.

Everything works as expected, no WiFi issues, etc.

I to, however, cannot wake from deep sleep. So i am getting Sleep of Death as well.
[Eee Pad Transformer Android Development] fear_factory84:
are you using dock? if yes, are you using the lock button on keyboard?

My tablet dies every time only when docked and when I use the lock keyboard.
[Eee Pad Transformer Android Development] NMCBR600:
I'm running 81 with 55b. I have not had any sod and I have the dock attached to the tablet and use the lock key on the keyboard to 'sleep' the tablet.

Do you have an app running in the background that may be causing the problem?
[Eee Pad Transformer Android Development] fear_factory84:
Only god knows who causes sod and rr on tf101!

Asus probably is very pleased to have stopped development on this device....
[Eee Pad Transformer Android Development] nergrum:
I dont have the dock, and outside of when I had the tablet running stock asus, I cant remember the last ROM I ran where SOD wasnt an issue.

I wouldnt know how to diagnose an app causing SOD.
[Eee Pad Transformer Android Development] NMCBR600:
Go to settings -- Apps -- running

See if there are any unneeded programs running -- you can select the program and stop it

Then in the upper right select cached process

and see if there are any unneeded programs cached that can be stoped
[Eee Pad Transformer Android Development] nergrum:
Thanks NMCBR600

I will give this a try.

I also saw an option to lock background processes to a certain number, ill try that as well to keep the number of processes low so its easier to track which one might be doing it.

Like I said though, I have always experienced SOD when not running stock Asus kernels.

I should also add, for a time I thought it was due to overclocking, so I stopped. However, SOD kept happening.
[Eee Pad Transformer Android Development] smithchipz:
Just installed the latest build 81 plus KAT kernel and it is flying! Can definitely notice a performance boost over Revolver and have had 0 problems so far, touch wood. Great work devs and looking forward to RaymanFX maintaining our device in the future :thumbup:

Also, what's with the small space under the list of recent apps and above the recents button?
[Eee Pad Transformer Android Development] Globespy:
Maps using most of battery

Im on build 81 and KAT kernel 55d.

Noticed recently that battery life in deep sleep has been poor.

I fully charged my device and unplugged it last night, never used it until this morning.

Battery was depleted 10% but maps had used 88% of the battery usage.

Wonder if its something to do with the new KAT kernel?

Ideas?
[Eee Pad Transformer Android Development] timduru:
No nothing to do with the kernel,

you have most likely left the gps turned on, and maps/location has been using it and preventing it to sleep.

=> try to turn gps off before going to sleep.
[Eee Pad Transformer Android Development] fear_factory84:
I have gps disabled, and the tablet actually is in deep sleep in airplane mode, no alarms and no wakelocks can be seen in betterbatterystats.

Drain is circa 0.5% per hour without microsd and 1% with microsd inserted.

Kat kernel vs stock eos kernel doesn't differ.

There is definitely something that remains powered on.

See my older posts in this thread fo my bug report and some screenshots.
[Eee Pad Transformer Android Development] andyman_187:
Just wanted to say thanks for this ROM! I am currently using it on a hand-me-down SL101 (Slider) and I m:silly:ust say apart from the few annoyances, it works great! If there are any slider owners out there who are thinking about flashing this, here are my findings after a week of using it. (Note: I use either the latest RaymanFX kernel or KAT kernel only)

Screen turns off when closing the keyboard

Soft keyboard will not work whencoming froma reboot (you have to turn off the physical keyboard in Language and Input settings to get the soft keyboard working, but the hardwarae keyboard will still continue to function anyway)

Rear camera works but the live and captured images will be upside down

The device is identified as a TF101 Transformer in apps and the play store

So far that's about it! Againi, pretty solid performancehere and no SODs or RRs experienced yet. Thank you once again for the awesome ROM!

PS: If any dev would like to work on solving the bugs i mentioned, I would be more than willing to test any patches/fixes on my SL101!
[Eee Pad Transformer Android Development] pcurator:
The new kat kernel 69 seems to be much better.

---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------

Would be great if they upgraded 4.2
[Eee Pad Transformer Android Development] grgmre:
I think you'll be happy with this link. Seems it's almost here. I'm of two minds having raymanFX on the EOS team. The guy is a brilliant programmer but I moved to EOS when his roms began to fork in several different directions at once and started being maintained/edited by a bunch of different people who never seemed to speak to each other. It's pretty messy in those threads.

timduru was my gateway drug to EOS with his kernel, and EOS has proven to be a stable, dependable place to make sure my tablet works great. I hope that doesn't change any time soon.
[Eee Pad Transformer Android Development] pcurator:
I've stuck with eos ROM and I love their work. I'm glad to hear eos is coming out with 4.2 soon.
[Eee Pad Transformer Android Development] chazzdjr:
I can't wait!!!
[Eee Pad Transformer Android Development] timduru:
Things were already almost there *BEFORE* RaymanFX commits.

RaymanFX: have you even bothered trying it before you overwrite everything ??

I had already compiled TeamEOS 4.2.1 rom with only a few minor changes and it booted fine before that.

SystemUI was crashing because of a few EOS Settings, I was going to have a look into that this weekend, but I see Randall might have fixed it already now, thanks :) https://review.teameos.org/#/c/1331/

So yeah pending a few adjustments and paths fix, the rom boots fine !

That is if I remove RaymanFX bulldozer commits I guess now though...

Because if I understand well what he just did, he overwrote the entire tf101 tree with his own 4.2 tree,

replaced Roach's kernel with his own and so on... (it has been a few months that the kernel is supposed to be built as part of team EOS rom build process btw)

So yeah now, the TF101 side of TeamEOS3 has not much to do with TeamEOS anymore I'm afraid.

Time to fork and cherrypick I guess, sad.

Now I guess it's partially my fault, as Randall came to me a few months ago asking if I could be the TF101 maintainer,

but I declined his nice offer, because I found that I wouldn't have enough time to dedicate for that.

And you don't need to be a maintainer to contribute to the rom anyway, so.

But if had known it would end up like that, I might have accepted ;)

I'm afraid it just did change...

But that's exactly my thoughts, I've tested most roms out there, and always coming back to TeamEOS, as I find it's the most stable and polished / finished, and well maintained.

And I find the Team to be quite dedicated and they know what they do.

They don't just "play" with things

There's a good review system with gerrit when you submit and so on.

Things are tested before commitingand so on.

Maybe something to keep in mind RaymanFX, you don't just commit crap and hope it works, you *test* locally and compile against the latest tree *before* submitting to guerrit.

RaymanFX: don't get me wrong, we all appreciate your hard work on all fronts of the TF101, roms & kernels & misc.

But what you just did is not "maintaining" a rom.

There's a difference between :

- maintaining and trying to improve a rom, trying to see what to change by modifying the

previous work

in place,

and

- simply coming in and overwriting past work and replacing it with your own previous rom work.

I think you would me much better focusing on one rom and one kernel and making them good, keep maintaining and improving them,

instead of adding a new rom or new kernel to your toy box every few weeks, or trying to be an official maintainer for x or y rom.

If your main reason to accept the TeamEOS3 TF101 maintainer position is because EOS has its own build server, well.. even if it's definitely a plus, I'd say it's a wrong reason.

There's a difference between maintaining and "playing with", maintaining is more of a long term commitment, and as a maintainer you're supposed to integrate with what is already in place, not trash it.
[Eee Pad Transformer Android Development] RaymanFX:
If you think that way, than fine.

Ask Randall to become the device maintainer, just revert my commits and start off again clean.

I didn't see any TF101 related commits for jellybean-4.2 branch.. so yes, I trashed it all and merged my device tree.

As I said, just revert that to your liking.

I just wanted to pump off TeamEOS, cause the truth is, Randall is nearly the only peace that's left of EOS.

Solarnz, Roach, etc have left.

I wanted to keep the EOS support for our device and use my own device tree for that, because the old one seemed like a mess.

But again, if you want to, just revert all that and publish EOS on your own.

I will concentrate on CM then.

And no, I did not accept the position at EOS because of the build server ... look, the last build was done over a month ago, so I'm still wondering if Randall has access to it. The most important, however, is bringing some straight facts to the community now. You say you are working on EOS - fine. I didn't notice that, I'm sorry. Then take it over, do the work and open a new thread for EOS-Android 4.2 please.

All the best for your ROM and work in the future :)

EDIT:

On a further note, timduru, how do you know I commited crap? Of course I tested it locally, first. And my changes were merged by Randall; he could also have declined. It's easy criticising someone else's work when not having done much on your own. I never saw a rom release from you before, and I might be wrong. But I think approaching an argumentation like that, or, in other words, bashing me for what I do, was one step taken too far.
[Eee Pad Transformer Android Development] grgmre:
Well, the kernel work is pointless unless your katkernel #69 is folded in as I'd just have to flash that anyway, but you need to boot from something right? The raymanFX (as everyone notes) has a much poorer wi-fi connection, and with the #69 update yours is just as fast in my testing. It also handles multi-tasking better and doesn't bog down when apps are running in the background. In short, it's a better kernel and should be the one the EOS rom comes with out of the box.

I've used raymanFX's AOSP rom before he started on his cyanogenmod rom. The CM rom ran faster so I upgraded from v1 through v6, before switching over to EOS. I'm not a fan-boy - I'll go where the speed and stability is. Hell, my first flashed rom was Revolver and moved on when Jellybean showed up - so that's four different major roms and three different recoverys.

I'm just looking for a 4.2 update to my tablet from EOS, not another raymanFX variant that will have a point update or two before the new coolness sends him off somewhere else. That's why I'm using EOS. ;)

If you wants this users opinion, roll everything back. If I want a raymanFX rom I know where the thread is. I'd much rather see several different competing roms than just variations on a theme. Oh, and while you're asking for feedback, how about upgrading the EOS boot logo to something that's not pixelated as hell on a 10 inch tablet. :)
[Eee Pad Transformer Android Development] Gatak:
Hey all!

I hope you devs can settle the "dispute" between you. As a TF101 user I greatly and deeply appreciate the EOS roms, and I have not questioned the approach taken by the team. In fact, if I felt it would be wrong, I'd gone to another ROM to seek my luck.

AFAIK the concept or EOS is a plain, but stable and fast ROM with a few EOS settings contrary to all the millions of features added on other ROMs.

Reading the last few posts it seems I could agree with both positions. I hope you wont fight =(. Both have good points, so lets be more sympathetic and gentle. :)

I am also sad to hear that solarnz and roach has left? Why did they, is it true?
[Eee Pad Transformer Android Development] grgmre:
.... but you really probably should. Just saying. ;)
[Eee Pad Transformer Android Development] timduru:
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.
[Eee Pad Transformer Android Development] cholywell:
I prefer the TeamEOS rom and kernel over others. I have tried everything out there and I keep coming back to Eos because it is simple, stable and updated often. It works better then anything else out there. No sods no RR. If eos is now going to be essentially a renamed Raymanfx ROM then I guess I will have to move on to a new device. I fear eos will get abandoned like so many of Raymanfxs projects.
[Eee Pad Transformer Android Development] RaymanFX:
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.
[Eee Pad Transformer Android Development] timduru:
Glad to hear, I definitely think there'll be more benefits with that approach :)

And sure I can try to help as I can. :)

How would you like to proceed ?

I think we'd kinda need to synchronize so that we don't do the work twice.

I've pulled the changes from teameos without your commits, and working on that currently.

I think one of the the first thing would be to revert your tree commits, that way I can resynchronize with the repo.

To make it work with 4.2 since you have most likely done that once for your 4.2 rom, if you prefer to merge the first bunch of modifications into EOS tree, feel free to do so. :)

From there see how you prefer that we work together.

Here are my findings so far with the current TeamEOS version:

1) Storage:

It's mostly a matter of changing the paths in init.ventana.rc, and the sdcard service.

better not overwrite the *.rc files with your versions as TeamEOS has a few specifics in there.

On the EOS specifics side, we'd have to decide if we keep the /Removable/XXXX mounting points or not, as it has always been TeamEOS "philosophy" until now.

Maybe hear what users prefer on that aspect too before changing.

=>But I guess for that you might be better to modify it as you've done it once before for your ROM.

So let me know when you did the reverting and added the storage and init booting modifications part.

And I'll sync.

location fix

it's posted for other devices, we just need to do the same for the tf101 device.

we can push that after the tf101 tree is reverted.

https://review.teameos.org/1318

2) com.android.phone

It's loop crashing once the boot is finished,

not sure what would be the best to do, either deactivate it completely but that would render the rom incompatible with any attempts to make it 3G for the moment.

And see later on what to do with it.

Did you encounter that in your rom and what did you change to prevent it if you had that issue ?

3) Audio:

Audio HAL needs mostly its version bumped to 2 I think, I've not tested it yet, but I think the current Audio HAL of TeamEOS should be good for the rest.

No need to change it, as I also have uncommited stuff for most of the audio loss fix, so I would prefer not to see it completely changed :)

I can commit that once the tree is back and we get the current tree in a booting state :)

4) Other hardware stuff:

Then we'll have the few other hardware changes to make like wifi & co.

Since you've solved these on your rom already, I guess you know what to do. :)

be careful with the bcm hcd and such, they have different paths and locations in EOS,

to keep the current good wifi and since we're keeping the existing kernel, I'd say it's better not to change any of that nor the nvram & hcd.

Shane Francis from CM10 has also announced that he got most of the hardware working too, I didn't have time to have a look yet,

but I guess we can have a peek there too once he has commited ;)

https://plus.google.com/u/0/112837272535265201743/posts/5bAsg67tHi9

Does that sound ok for you ?

We might be better communicating by email too if you prefer. :)
[Eee Pad Transformer Android Development] RaymanFX:
Sure, let's talk via email!

Hit me up at raymanfx@gmail.com, mate :)

Glad we are able to resolve the conflicts and now hopefully can deliver soemthing beautiful together.

Looking forward to the teamwork!

BTW, the audio HAL is fine indeed, but mic does not work. I am working on porting the grouper Audio HAL and implementing our fm34 needings.

Waiting for your contact mail ..
[Eee Pad Transformer Android Development] timduru:
okie, email sent :)
[Eee Pad Transformer Android Development] pcurator:
I'm so glad that the two of you were able to overcome your differences and work together. 2 smart people = amazing ROM :)
[Eee Pad Transformer Android Development] crisscross3:
Glad things didn't blow up so that the community suffered. Now I'm really looking forward to seeing what this collaboration will produce. :)
[Eee Pad Transformer Android Development] zachf714:
So what happened exactly

Sent from my ADR6300 using Xparent Red Tapatalk 2
[Eee Pad Transformer Android Development] kalkrishnan:
At this point, let's just say "all is well that ends well!" When people are doing free work for the community, it is not uncommon for there to be some friction from time to time. As a non-profit volunteer, I have seen happen many times before. Sometimes, it can even get pretty bad. I am so glad the parties worked it out, and all of us will benefit!

Now, I can't wait for a solid 4.2!
[Eee Pad Transformer Android Development] zachf714:
Oh OK yeah I know what you mean

Sent from my ADR6300 using Xparent Red Tapatalk 2
[Eee Pad Transformer Android Development] CalvinH:
Wow! What two last pages.

Thanks to Rayman for his work, timduru for voicing his ideas and bringing some methodology, and to grmgre for putting into words the same thing I am thinking of.
[Eee Pad Transformer Android Development] lazydesi:
Hi guys, firstly I want to thank Team EOS for their contribution to TF101.

I am currently using the latest build no=81 and I found the audio is very low.

so I installed KAT audio app and found the audio is crackling time to time, .yes it did boost the volume, but not clear. did I miss anything?

using kat kernel 69 also.

Thanks
[Eee Pad Transformer Android Development] timduru:
If by crackling you mean that it sounds like saturated from time to time depending on what music you play,

well it's an expected behaviour if you push the levels to the max and that your input media already has a high recorded level.

If you don't want crackling you should keep the analog level below 57, which is 0dB for the amp.

I personnally find that up to 60 (+3dB) is usually ok.

Using 63 will for sure generate clipping with a "good input media level".

If you use front boost in addition to that, it'll crack even more ;)

Front boost is more made to give you the extra boost needed for quieter medias. :)

So basically if your media has already a good level, simply decrease the volume until you find the best compromise between saturating and power. :)
[Eee Pad Transformer Android Development] lazydesi:
thanks timduru,

the media I use mostly Youtube.