yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] dgcruzing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

B152 v K-92 all good here..

Tried a dirty flash but got what I say was a Google apps bug.. Location service pop up..

Reflash of apps fixed it..

Will run it in and report back if any strange behavior..
[Eee Pad Transformer Android Development] rjvdhoek:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I flashed 4.2.2 last night, with same apps as with 4.2.1. Full wipe/factory reset. But: unfortunately no more deep sleep :( I'll try a new fresh flash this evening.
[Eee Pad Transformer Android Development] Jamesyboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

The search function has failed me. Can someone explain why everything is so retartedly big? Ive changed the font size in settings, but that didn't flux it, so I assume its a DPI setting. What's the default dpi for the transformer?
[Eee Pad Transformer Android Development] didier74:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Right, but he seems to have the same problem as I have on my tablet, and got bored to push the button 10 times a day, this is why i finally decided not to install Kat kernel any more, it is his choice now to do what he wants.

Have a nice day .

Envoyé depuis mon GT-N7000 avec Tapatalk
[Eee Pad Transformer Android Development] Jamesyboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Edit: there is some talk of a theme flash to fix the DPI, but I don't know if that's a package released by EOS, or I'm supposed to apply any ol theme in theme chooser. Just as well, it isn't clear if they were talking about the same issue I'm having

---------- Post added at 02:00 AM ---------- Previous post was at 01:52 AM ----------

And where is the Internal Storage mounted at? Did this seriously just wipe my internal SD card?

Wow....found it. Sort of. This is a REALLY , really, really, obscure mounting layout.

Now. To fix the DPI, and figure out why its running slow.
[Eee Pad Transformer Android Development] timduru:
Ah nice, thanks for letting me know and thanks to whoever did that :)

That sure should come in handy if I can put useful info in the 2nd post, and update it as time goes.

Will see about that later today. :)

I don't think I've seen anyone else with that issue.

Things are not big for me.

Maybe you didn't wipe correctly when coming to the rom and it picked up some previous mod / setting or something ?

Did you read the procedure to install and other infos in my SIG ?

Otherwise post a capture and explain "what is big"

Also indicates which rom version / kernel you're using and if you have other things and customisations installed.

And how you came to the rom / which rom you had installed previously.
[Eee Pad Transformer Android Development] Jamesyboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I came from LS, and the DPI was the same as it was for every other ROM I've used. I'm using the 94 nightly...and I wiped every relevant partition using twrp: cache, dalvik, factory reset, and system. For good measure, I wipe them manually as well.

Also....when I finally found where my old Internal files were, I copied and pasted them using root explorer into the "New" Internal folder. The screen started flickering like crazy, and something crashed....the navbar and status bar disappeared.
[Eee Pad Transformer Android Development] cimbike:
Dirty flashed B152 + Kat kernel 92 and runs very, very smooth.

Once again thx so much timduru for such an awesome job, and for keeping our TF up to date.

A friend of mine bought yesterday a Samsung Note 10.1 and still running ICS. :confused::confused::confused:
[Eee Pad Transformer Android Development] Jamesyboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

For some reason, this ROM calls a folder named 0 in the emmc home...any way to change that?
[Eee Pad Transformer Android Development] billouetaudrey:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

It's 4.2 multiuser folder

Don't touch...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

learning something new everyday. so another user might be /data/media/1 ?

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] Jamesyboy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Thanks. I see. All my internal data was moved though. I had to access it thru /mnt/*

The only issues I see to be having now is with the keyboard, with flickering, and general sluggishness. The keyboard seems to pop out, then pop back up with alarming speed and randomness.

Parts of it are faster than 4.1, but other parts aren't. Most of it isn't.

I wish there was a way to have the recent apps list start on the left. This is pretty unintuitive.

Otherwise, I'll give this a day or two. If I can get used to it, or find a way to smooth out a couple of the bugs, this has a lot of potential.
[Eee Pad Transformer Android Development] inigoml:
Dirty upgrade to B152. Everything working great with Kat 92.

By the way, EOS Control Center look has change to phone look. I think previous look was better for a tablet...

English UK keyboard for asusec not still present. EOS CC workaroud works, but It should be great to have it...

Tim, great job as usual. My TF101 runs faster with each new release!

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

Tim following your tips I managed to boot with Guevor Kernel V1.1 your EOS4 build. All appear to be working. However, when opening an app lockscreen is activated automatically. If I unlock screen, launch app appear for a moment and again I come back to lockscreen...

Do you have an idea about what could be happening?

init.d scripts are quite different between Guevor and Kat/default EOS but I only changed kernel and leave ramdisk without modifying. I'm not sure if it could be a lidpatch issue but since I've tested using both EOS and Kat packages as base I've discarded as cause of faulting...

I'm trying to use Guevor V1.1 kernel because although don't have many of the optimizations of modern kernels it's really stable and fixed my old SOD problem when I was with ICS ROMs.

Thanks in advance.
[Eee Pad Transformer Android Development] jpmccarthy:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Not sure an ICS kernel will work on JB. That's probably your issue there.
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

in linux(not android) isn't the kernel independant of the system or are there compatibility issues like it appears there are here with android between kernel and system?

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] timduru:
It's the way android 4.2 works.

You don't even need to know how it maps the folders.

All you need to know is that:

Your usual internal data folder is accessible through /sdcard/ and also /storage/sdcard0

Your MicroSD is at /storage/sdcard1

Your SD is at /storage/sdcard2

usbdisk are in /storage/ too.

Please read general info about Android 4.2 first before posting here.

For the rest of your questions it's either answered here or in the links in my SIG

In particular please read the Known issues & workarounds.

If you still have questions ask in the Q&A.

We really need to get this thread to a cleaner state, as it'll help to progress better and will be less time consuming. ;)

Remember it is a dev thread that is here to get the rom to progress.

Thanks.

Good to hear :)

Yeah EOS CC is being changed quite a bit, the version you have in B152 is not fully finished, there will be a better tablet layout soon.

Yes, EOS4 is made to work with lidpatch kernels.

Looking back, we really should have avoided that as it has only generated issues, and everything was fine before.

In addition it complexifies the kernel compilation as it basically requires 2 different versions for roms.... but well a bit too late now.

So if you want to get guevor's kernel to work with EOS4 you'd need to patch it with the lidpatch and recompile it / repackage it.
[Eee Pad Transformer Android Development] DevourDarkness:
I have more than one user. What will happen if I dirty flash?
[Eee Pad Transformer Android Development] catfishbilly:
I am on B152 + Kat kernel 92 and KAT app and everything works flawlessly, thanks timduru.

Just that i was testing out skype echo service and the mic wasnt working or rather it worked at the first try, was lower on the 2nd try then wasnt working at all on the 3rd try i tried rebooting and still wont come back. i have no apps that make use of mics installed. i know i have to grab a logcat and dsmeg and some other things, can anyone walk me through how to get them? BTW, the rom flies.

i just uninstalled KAT app and tried it again, voice recording works.
[Eee Pad Transformer Android Development] dgcruzing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I have flashed this mode over top and I can feel a difference..
[Eee Pad Transformer Android Development] wn1ytw:
Quite a few logcat tips on XDA, start here maybe: http://www.xda-developers.com/android/dont-know-how-to-logcat-try-logcat-tool/

:)

scott
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Just open the Terminal Emulator and run through Tim's steps on logging the issue.

Then open a file explorer like ES File Explorer and zip the dmesg, lc and top files.

Attach to this post

Profit
[Eee Pad Transformer Android Development] leomeloxp:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Okay, I know this is not dirctly related to the rom, but the rom seemed to have temporarily fixed it for me so I'll ask anyway XD

I think most all of you here are aware of that bug on the Youtube app that you can't fullscreen the videos while docked (no FS button). I just flashed b152 with a factory reset, system and caches wipe and the button was there after I booted oO I found that out a while ago when I did a Factory reset to install another preview. The bad point is, after I reboot, the FS button disappears while docked =/

Am I missing anything here? I mean, I really like watching videos in FS and undocking it all the time for that is a pain... What I thought was that maybe the tablet would fail to recognise the dock properly upon first boot, but I managed to type things just fine so I really don't know.

So, if anyone has any clue on this, I'll be very happy with some enlightment =D And if need be I'll create a thread just for that later on o/
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

It doesn't happen like that for me. For me, its only about 1 out 10 times coming out of sleep. It hasn't even happened in about a week.
[Eee Pad Transformer Android Development] frederuco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

You need to find an older version of the YouTube app. Depending on which GAPPs you are using, it may be included with the GAPPs and a working verison. Then as soon as you boot it automatically updates to the latest one.

You can try going to Settings - Apps - YouTube - Uninstall updates (the GAPPs in the first post do not have YT included so it just has an UNINSTALL button).

If you can uninstall updates, you should be golden. If not, search for an older version.
[Eee Pad Transformer Android Development] grgmre:
Agreed, and now you have access to that second post hopefully people will look at your FAQ and install (etc) page a little more often. :)

---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------

A Youtube app issue should be directed to the QandA forum, or the apps forum first. If someone directs you to the ROM itself (this forum) then I suppose it's something worth asking. I bet if this thread was cleaned we should pull over 30 pages out of this.
[Eee Pad Transformer Android Development] PeQuEsan:
Yes... I'm the boy hunting my SoDs. :) Installed B150, nothing else (no GAPPs), if you remember. Well, 86h after, no SoDs... I've tested deep sleep with/without dock, charging/not charging... So stable config at this point. Now I've rebooted to test again for 48 hours, to be sure I've got this stability across reboots after first clean flash. Then I'll install default TeamEOS gapps and see... Last time, if you remember, I got my first SoD after flashing GAPPs MIX on top of clean B148 preview (after 50h with

no SoDs).

Sorry... this is gonna be terribly slow... :) I'll try to quote myself every time so we all can keep track of what I'm doing.

bye!
[Eee Pad Transformer Android Development] timduru:
Perfect, thanks for the logs :)

Seeeee, that's a good example of how to report, all reports should be like that ;P

Well now that I have proper logs, I think I've spotted something :)

It seems that with certain apps the routing and/or mic routine is not applied correctly as they open or reopen the mic.

So when mic routing is ok and mic record routine is off you most likely get the lower mic effect.

If the routing is not reapplied and that some other app is changing the routing in between the first time and the nth time the app opens the mic (like if you apply a profile in the K.A.T app <= V1.2.4) you get no mic sound until an app properly reopen the mic.

To try to address that I've changed 2 things:

+ Mic routing code to try to force the mic routing after the >= 2nd times

if it works it should fix both issues most likely.

Flash this on B152 to test: B152_Mic2ndOpeningFix.zip

+ Just to be safe, I've also updated the K.A.T app: K.A.T_V1.2.5.apk

In this version I've removed the default route reinit from the profiles.

So that it only applies the sound quality + levels when you click on apply for the profiles.

That should help for apps that don't reopen the microphone / switch the route properly everytime they record, and that you apply a profile in between their mic opening.

I'll readd a dedicated/separate route selection feature later on in the app, not linked to the profiles.

Try one or the other or both, and report how it goes and what you tested.

see above :)
[Eee Pad Transformer Android Development] NoUseToRush:
Well, I'm also hunting SOD but I'm not as patient as you are! I clean installed the latest EOS4.2.2-tf101-20130208_previewB152 + gapps-mix with the stock kernel and...pouf! SOD in less tha 3 hours.

That was last night, so I went back to the latest kernel used by Raymanfx in his 0.8.0 Xmas rom: no more SOD

My device has definitely a problem with katkernel:confused:
[Eee Pad Transformer Android Development] timduru:
If you get SOD with the stock kernel it's not KatKernel ;)

PeQuEsan method might be slower, but at least he's progressing on targetting what is causing the issues.

Since he doesn't have the issue with the rom only without gapps and such. that should mostly eliminate the rom as the source of the SOD.

Or it's only once that you had something in particular on top that it's causing SOD.

It'll be definitely interesting and a good progress if he finds out exactly at which point he starts to have SOD.
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

my speaker isnt cutting out when i plug it in after that mic fix? Amazing.

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] timduru:
What did you test exactly ?

And is your phrase a question or an affirmation ?
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

just plugging the speaker in and out seems to work. its not cutting out as before.

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] simo.scorpion:
R: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

where i can found the themes for this ROM?

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] billouetaudrey:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

http://xdaforums.com/showthread.php?p=36237311

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Android Development] timduru:
I mean did you test B152_Mic2ndOpeningFix.zip or K.A.T_V1.2.5.apk or both ?

But that's interesting, in the Mic modifications I also isolated the in flags from the out flags,

so that could be what is fixing your issue too.
[Eee Pad Transformer Android Development] catfishbilly:
i installed the new kat app and everything works good now, will continue testing. Thanks for your prompt response.
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

ya its fixed. I did the mic fix but not the kat app yet.:cool:

works flawlessly. no reboot needed anymore.

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] Woody:
And then you can go here to the Mega CM10/10.1 Theme Chooser thread

****

@Tim,if you ever want a thread cleaning, just hit the report button and there is a dropdown for Thread Maintenance. I'm not on the Mod team for this section, so I can't do it.
[Eee Pad Transformer Android Development] billouetaudrey:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Or CM10 theme chooser in Play Store ;)

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Android Development] MessyMarv:
Thanks Tim for checking this :)

did a quick test and flashed the zip over B152 and second, third recording volumes remained at full

will do a full wipe later this evening nad test the new kat app on clean system to see if that fixes the issue with out the need for the patch zip

once again thanks for your time and smarticules on improving our transformers :good: :good: :good:
[Eee Pad Transformer Android Development] timduru:
Bluetooth HID devices support for Keyboards + Mice + Touchpads

And here is the long awaited support for Bluetooth keyboards & mice ;)

Much easier to test when having a bluetooth keyboard.

Got a nice Advance KeyMote (keyboard on one side and touch pad on the other side)

pretty handy and it works great now :)

You need that for it to work for the moment: Tim_KatKernel_94_JB4.2_Lidpatch.zip

Test & report.

You might have to unpair / repair your device to get it to work the first time if you had it paired previously.

Once it's confirmed to work I'll try to backport that to the default EOS4 kernel too.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Just flashed it, and it worked fine with my Logitech BT keyboard.
[Eee Pad Transformer Android Development] gladi8r:
Logitech laser travel mouse working!

Re-paired, cursor popped up and we're good to go.

I can even use the LMT pie launcher with it.

Thank you :laugh:
[Eee Pad Transformer Android Development] catfishbilly:
It works!!!! i have a bluetooth headset i have given up on, but it works with the new kernel. Thanks for everything!
[Eee Pad Transformer Android Development] didier74:
Good for You then....:fingers-crossed:
[Eee Pad Transformer Android Development] Puzzlegirl:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Could someone explain why you're running Android 4.2.2 when it's only rumoured to be released in mid February? The last minor update was 4.2.1 still :confused:
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Haha. I asked the same thing and didn't get an answer. In another forum I was told this is really 4.2.1 with a modified build prop. ;)
[Eee Pad Transformer Android Development] rjvdhoek:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

B152 + KK94 + Micfix brought deep sleep back. Thanks Tim.
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I think we would all like to know.

sent from TF101 with Android 4.2.2

---------- Post added at 03:34 PM ---------- Previous post was at 03:20 PM ----------

maybe if he told us he would have to kill us so its better not knowing.:eek:

sent from TF101 with Android 4.2.2
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

:thumbup:
[Eee Pad Transformer Android Development] monsignori:
Thank you, Tim ... my Bluetooth mouse is working too now ...
[Eee Pad Transformer Android Development] timduru:
indeed, it should be 4.2.1 mr1.2 not 4.2.2
[Eee Pad Transformer Android Development] Hidden Username:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Would someone direct me to the latest kernel for 94 please?
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Check Tim's signature and posts.
[Eee Pad Transformer Android Development] archcantor:
Hey Tim! Thanks for fixing the bluetooth mouse. I was going to report it today with a logcat but I see you already fixed it. I flashed B152 and Kernel #94 and the Mouse works. It is a Microsoft 5000 mouse. It's a little fussy but it does connect. The last time I tried EOS4 I thought the GPS performance was less than Revolver ICS (which was my daily driver). On to test that now. The B145 dock battery patch does not seem to work on B152. Thanks to you and the others who have been working on this ROM. It's really fine. I think I am staying. -Rick

Update: GPS performance is poor. Can't get a lock. Two sats received, often not even both at the same time. Any tricks here? I tried GPS Doctor. No change. As I mentioned Revolver ICS on the same tablet is consistently pretty good with GPS lock, often within 10 secs.
[Eee Pad Transformer Android Development] DevourDarkness:
Can you add an option for the nav bar to automatically hide when the dock is connected?

Can you remove the 'removed SD card' notification when I remove the dock?

Can you add the dock battery to the battery widget in quick settings?
[Eee Pad Transformer Android Development] hyperxguy:
After Megatron (ICS404), GPS has been weak in JB. I've used "agps.patch.asus.tf101.build.v1.0" to patch thru recovery. It really help with more satellites locked, but the signal is still not as strong as then. I didn't need this patch in early nightlies, but lately ...
[Eee Pad Transformer Android Development] sidneyk:
RR watching Netflix

I just experienced 3 reboots within 2-3 hours while trying to watch Netflix, docked with headphones plugged in, off of charger. I'm on the latest preview (B152) and v94 of KAT kernel. I flashed everything the normal way - wipe caches, wipe system, flash ROM, flash gapps, flash kernel, wipe caches again and reboot. Here are the links to the requested logs from the 3rd time it rebooted.

http://db.tt/WoFgIPyX - dmesg

http://db.tt/GvwHNHad - logcat

http://db.tt/fTQIdz5g - top -n1

Although the top output appears to be Japanese or something. Thanks. Going to try the stock kernel now.

[EDIT] I just realized that I left it OC'd to 1640 and performance setting and forgot to put it back to interactive and 1540, so that might be part of it.

[EDIT] After turning down the OC now Netflix is running just fine for the past 2 hours. Everything is nice and smooth with this latest ROM / kernel combo.
[Eee Pad Transformer Android Development] timduru:
Well yes, it's not surprising that it reboots under high load if you're overclocked and using an cpu/gpu intensive app like netflix.

Heck you're even lucky that you can run at 1640 or 1540 ;)

My TF reboot instantly if I overclock to 1640, at 1540 I can run it for a bit, but as soon as something uses the cpu to the max for more than a few seconds it'll reboot ;)

Did you capture the logs after the reboot or did you have them run until the reboot ?