yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Globespy:
Sound drop on latest preview 142 with KAT kernel

Is there any way to flash the latest stock kernel as I never had sound vanishing issues with stock, unfortunately only with KAT.

Thanks.

I'm looking ideally for a flashable stock kernel so I don't have to reflash the entire ROM and full setup again.
[Eee Pad Transformer Android Development] prog19:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

for me a custom gmd gesrure worked fine for menu, in all apps
[Eee Pad Transformer Android Development] Hammerfest:
your missing the key fact here, is that WITH the navbar hidden running the app freshly, or with the navbar showing...

key information to the discussion at hand
[Eee Pad Transformer Android Development] rickgillyon:
If you flash the ROM and only wipe cache, dalvik and system, you'll retain your data.
[Eee Pad Transformer Android Development] prog19:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Until 136 a custom gesture for menu worked fine for me. No complains about. I'll just flash 142 to see what happens. I use navbars hiden almost all the time. NOw the lag is gone, but i get used to control everything with the gestures.

Im not trying to disrupt the discussion in anyways. Just add a confirmation that the function worked untill some point

EDIT:

guys, no issues here. I'm on 142 (wich has, indeed, a nice boost on fps with navbar hidden) and in GMD Gestures (the pro version) my custom gesture for menu calls the menu for all apps that has menus.

WInamp, dolphin, kingsoft office, settings control, facebook....

142 seems to be the best release until now in terms of responsiveness and I trully recommend the GMD app. It has VERY nice funcionalities like change apps swyping across the screen, alt tabbing between apps, recent apps dock, back, home, hide unhide system bars (both of them)... it's an amazing app and a must have for those whom want ultimate smothness on this rom, so far
[Eee Pad Transformer Android Development] poetter747:
Hi,

did a dirty flash from b134 to b142 and got stuck on starting apps on first boot an got bootllop after hard power off. restored my nandroid and made a second try. same result.

before i try a full wipe. I have multiuser enabled. Is there a proper way to backup restore the profiles? I saw some notice that only the main profile has full superuser rights. That would meen that a TB restore of the 2nd profile apps would'nt do the trick.

Has anyone done full wipeing with multiuser and how did you do backup restore of the profile apps and app settings?
[Eee Pad Transformer Android Development] frederuco:
I would try MyBackup or Super Backup. It works for unrooted devices.
[Eee Pad Transformer Android Development] evoer:
Same happened to me, two different dls same result. I do not have multi user enabled so cant help there. Both times dirty flashed just like I have been doing yet cant seem to get b142 to go, no biggy though b134 is working great
[Eee Pad Transformer Android Development] chrisanthropic:
Can't help with the multi-user backup (although I'm interested as well since I use it) but I'm having the same problem - tried flashing b142 after a dalvik/cache/system wipe and get stuck at "loading apps". I tried reflashing gapps as well but still had the same issue.
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I just wanted to check in with my latest report re upgrading to 142 after the 136 (or whatever the previous one was) caused my machine to become unstable (spontaneous rebooting multiple times in just a few hours).

The news is good. No spontaneous reboots so far. And that includes when I run it at 1.4ghz -- which 136 did not like (though all previous builds of EOS I tried were fine with).

I also did try something a little different for my install of the latest. It may have been needless and neurotic, but alone with wiping system before the install I also wiped the davek cache before (and after) installing 142, Katkernel 80B (don't forget the 'B'!), and the TF101-specific gapps.

I followed this process with both my TF101 and my pet hamster Fredina. The tablet is, as noted, running fine. But after being wiped, installed upon, and rebooted, Fredina seems frayed. Jittery, even.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #136

Kat Kernel 80b / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] Globespy:
Won't I also have to reflash gapps too? I thought gapps needed to be flashed EVERY time a ROM was flashed?

Would have thought someone would have the stock kernel as a zip?
[Eee Pad Transformer Android Development] sttovo:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Yes, you have to flash gapps every every every time you flash.

Stock kernel is part of the ROM, so no, doesn't come separate.
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Sorry, the only "new" thing I did in my description was to wipe the davek cache before as well as after the install. Everything else was pretty much as Timduru's directions describe it should be done. I have no idea whether wiping the davek cache before a ROM / katkernel / gapps install is helpful. Just thought I'd try it.

Didn't mean to confuse or bewilder.

;)

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #142

Kat Kernel 80b / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] Krimbeleco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Rebot recovery

Wipe chace dalpik

Install kat 80b kernel

Enjoy
[Eee Pad Transformer Android Development] crisscross3:
So far, upgrading to EOS4 has been a positive experience. (I love the multi-user feature.) A couple of things I hope get addressed soon. I hestitate to even mention these because so much is just "right" and well done about this ROM. The keyboard drain on b98 seems to be especially bad--worse than the other preview versions. Also, in gmail, the drafts label doesn't display the email count. Finally, having to disable the nav bar to get a higher frame rate is certainly a workable solution but it will be nice when that bug is squashed. I'm also getting a fair number of random reboots running KAT kernel (overclocked to 1.5, ondemand, bfq). Should I be using different settings? Again, I hope my nitpicking isn't misconstrued. I'm extremely grateful for all the hard work being done to keep my TF101 on the bleeding edge. Thank you!
[Eee Pad Transformer Android Development] courghan:
Hi, here is the output of those commands:

18|u0_a37@android:/ # ntfs-3g.probe --readwrite /dev/block/vold/8\:1

Error reading $MFT: Invalid argument

Failed to load $MFT: Invalid argument

12|u0_a37@android:/ # ntfs-3g /dev/block/vold/8\:1 /storage/usbdisk0

Error reading $MFT: Invalid argument

Failed to load $MFT: Invalid argument

Failed to mount '/dev/block/vold/8:1': Invalid argument

The device '/dev/block/vold/8:1' doesn't seem to have a valid NTFS.

Maybe the wrong device is used? Or the whole disk instead of a

partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

12|u0_a37@android:/ # ls -l /storage/usbdisk0

u0_a37@android:/ #

The drive was formatted by WD, I can't recall formatting it after I got it. As I mentioned, Windows can't find any errors in it.

Thanks for your time dude.
[Eee Pad Transformer Android Development] grgmre:
Try smartassV2 / noop. I've never had a reboot at 1.5 GHz using those settings. 1.6 can get a little squirrelly though. SmartassV2 is brutally fast so it's worth checking out at any clock speed.
[Eee Pad Transformer Android Development] JoinTheRealms:
Yeah I just have to wait for my tf101 to go flat:( its frozen and my power button doesn't work lol
[Eee Pad Transformer Android Development] Sziehr:
I installed a couple of weeks ago, it says build is JOP40D Nightly. Which build should I try?
[Eee Pad Transformer Android Development] sidneyk:
The current preview build is here:

http://public.timduru.org/Android/tf101/eos4/#main

I don't know if it changes the displayed build info, but I'm guessing not, since mine, on B98, says the same.
[Eee Pad Transformer Android Development] JoinTheRealms:
Heres the link (http://dl.dropbox.com/u/39805348/Boot Animations/EOS4/bootanimation.zip) just make sure you give it the correct permissions, im not on eos4 atm but if its the same as eos3 it goes in /system/media

Enjoy:)
[Eee Pad Transformer Android Development] edd080:
I made the plunge and installed preview B98 :D all looks nice and smooth so far, I seem to only have one issue, I usually use Auto Airplane by don, in order to turn off wi-fi when I lock the Tablet, however it seems that wi-fi remains on even when auto airplane is running... any ideas what I can do please? maybe iam missing a couple of settings?

Thanks...
[Eee Pad Transformer Android Development] asdfzz:
I'm using B98 and stock kernel (not KAT) since more than 3 days and no reboot.

For navbar problem try different launcher, I'm using apex.. So you can use navbar
[Eee Pad Transformer Android Development] edd080:
I seem to be encountering another issue :( iam getting a damaged sd card error similar to recent posts, however this is not an external disk, it is the microsd card I normally use to transfer my games and data, it is a sandisk 32GB ntfs microsd card which I used without problems on the eos3 builds, can anyone help me out please, as I need to recover my titanium backups..

Thanks..
[Eee Pad Transformer Android Development] alberteske:
Skype

After 3 days with B98 and B70 kernel: smooth and ready for everyday ROM.

Some minor issues already reported. I just have a problem with Skype: when phoning the microphone is not working.

With other app, the microphone as no issue.

Any idea?
[Eee Pad Transformer Android Development] timduru:
EOS3 doesn't natively support NTFS automount,

what were you using in EOS3 to mount it ?

Reboot and reproduce the issue

then send me that:

What to include in the report
[Eee Pad Transformer Android Development] i9apps:
Hi Tim :) , I got "Damaged SD card" massage too on EOS 4 (when i connect a USB hard drive)
[Eee Pad Transformer Android Development] timduru:
*g*

Then as usual, how about giving me more usable information ? ;)
[Eee Pad Transformer Android Development] i9apps:
Sorry, I do not have much experience with these things ... what I need to do to provide you more information? :)
[Eee Pad Transformer Android Development] waterpolo:
I copied your bootanimation with root explorer to \\system\media

It's running fine but only once. I have a black screen for a few minutes before homescreen is coming.
[Eee Pad Transformer Android Development] alberteske:
Skype

Excuse me to be so lazy

ROM B98 with B70 Kernel

I made a nandroid from B96, full wipe, flashed B98 + Kernel + Restore Data.

when opening Skype everything is fine but when trying to phone the built in microphone is not working, the other side does not listen.

I uninstall Skype + re-install + reboot but same problem.

Herewith the files you require.

Thanks a lot!
[Eee Pad Transformer Android Development] pippoparecchio:
Inviato dal mio GT-I9100 con Tapatalk 2
[Eee Pad Transformer Android Development] timduru:
just follow that:

What to include in the report

You even quoted it in your previous message ;)

Ok, so if I understand correctly:

you can get it to work in EOS4 the same way than before in EOS3, but just that the automount in the rom indicates that it's damaged right before you can mount it successfully with paragon ?

Maybe I'll bring back the NTFS feature in the K.A.T app too for testing,

if the K.A.T app can mount it too, it should mostly be a matter of upgrading ntfs-3g in EOS4 then.

Hmm, interesting. Skype is trying to create an input stream at 48000 for the mic but we don't have that supported currently it seems.

Will see how to add that even if it's quite ridiculous to use such a high sampling rate with the mic...

W/AudioPolicyManagerBase( 137): getInput() could not find profile for device 80000004, samplingRate 48000, format 1,channelMask 0010

E/AudioRecord( 1889): Could not get audio input for record source 1

E/AudioRecord-JNI( 1889): Error creating AudioRecord instance: initialization check failed.

E/AudioRecord-Java( 1889): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.

W/AudioPolicyManagerBase( 137): getInput() could not find profile for device 80000004, samplingRate 48000, format 1,channelMask 0010

E/AudioRecord( 1889): Could not get audio input for record source 1

E/AudioRecord-JNI( 1889): Error creating AudioRecord instance: initialization check failed.

E/AudioRecord-Java( 1889): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.

In the meantime does skype have options to specify the input sampling rate ?

If so, could you try by decreasing it to 44000 or even less than that and retest ?
[Eee Pad Transformer Android Development] farsight73:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I think the latest 142 released would work great when docking with the keyboard, as timburu has added the short cut on the keyboard to show recent apps. If you're only to use the tablet alone all day, then a 3rd party app is required for bringing up the menu via gesture. Beside bringing up the menu/navi is just pressing the power button and select the systembar mode, unless if you feel the two steps is a burden..

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Well... confession time. My issues were likey in part to my own ignorance of how to properly use SetCPU (a program for overclocking among related things). I have not -- until tonight -- realized that I had SetCPU wrestling with the EOS Setup's own overclocking settings.

I unchecked the "set clock settings at boot" box, set up SetCPU, and I'm humming at 1500ghz at the moment. Probably won't leave it this high, but I want to see if it is stable now. I strongly suspect it will be.

So... nOOb moment number 25048.

Heh.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #142

Kat Kernel 80b / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] zap-o-post:
I had the same problem, get stuck at "loading apps".

Then I installed the KAT 80B kernel and my TF101 boot correctly.
[Eee Pad Transformer Android Development] Krimbeleco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

He3
[Eee Pad Transformer Android Development] st0nedpenguin:
I've been using alt tab on the dock to switch apps for a while now anyway.
[Eee Pad Transformer Android Development] JoinTheRealms:
wow didnt know that was a thing.... thanks lol very handy
[Eee Pad Transformer Android Development] frederuco:
That has been around since Android 3.1!

I swapped the search and alt keys to do easier ALT TAB switching.
[Eee Pad Transformer Android Development] JoinTheRealms:
does anyone know how to get the hide navbar button on the power menu when opened via softkey? my power button doesnt work and it would be good to get the option to hide the navbars properly as gmd gestures hides the navbar and wallpaper but the wallpaper returns sortly after bring about half the lag the navbars had when enabled
[Eee Pad Transformer Android Development] Globespy:
Interesting to see this has happened with other folks too.

I had exactly the same issue, even my nandroids (including both JB and ICS) would get stuck on the boot screen.

I managed to get an old revolver ICS ROM to boot, but my TF was running really choppy and just not well. After trying full wipes and trying to re-install 142 I just gave up and NVFlashed back to stock Asus ICS (build 27 - the last one) and my TF is running nicely again.

I've rooted and installed TWRP but am very hesitant to run build#142 again as this is where the problems all started, and since others have had the same issue, it's just not me.

I will hang out on ICS until the next nightly (#93) is up, although if it's essentially preview#142 I think I'll hold off until nightly#94.

Can you think of anything that could have caused this Timduru?

Thanks.
[Eee Pad Transformer Android Development] rickgillyon:
Of course, but the point still stands. You don't have to set everything up again.
[Eee Pad Transformer Android Development] cimbike:
Hi all,

After flashing B142 on top of B136 I've got stuck on starting apps on first boot an got bootllop after hard power off.

What I did was just get into TWR do the wipes and install B142 + gapps-jb-20121229-TF101_ONLY + Tim_KatKernel_80_JB4.2_Lidpatch and when finished wipe davilk cache and it powered up fine.

Thx a lot.
[Eee Pad Transformer Android Development] timduru:
I think it could be caused either by a messup of the recovery if it's not wiping things correctly

or a binary mixup when you flash on top of a previous version.

Do you do the format /system step each time ?

Another thing you could try is to not flash everything at once,

or flash again and wipe /cache + dalvik after a reboot.
[Eee Pad Transformer Android Development] cimbike:
Hi timduru,

I did flash with all wipes and format / system separately and was when it got stuck, and then reflashed again with all wipes and format /system once again but this time all at once and it booted fine to me.
[Eee Pad Transformer Android Development] Ultimategeppie:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Recently I installed TWRP and b136 and then setup multi-user; having three accounts setup.

Before installing b136 i first installed TWRP.

This morning i decided to upgrade to b142; All went fine, except some apps missing on another account.

I downloaded b142 (i also download kernel 80BBBB, while i was still using 80).

Rebooted to TWRP: wiped cache, wiped dalvik and system.

Installed b142 and without reboot installed kernel 80B.

Since I didn't have gapps-tf101 present, I didn't install that one.

Reboot.

All three accounts are still there!

On the second account I'm missing two apps. I'll simply install them again.

I don't know about the data of those apps, because I haven't setup those apps (so there isn't any data of those apps).

Some other point I just notice for the first time (while typing this post):

I have music playing trough BubbleUPnP (licensed) and kat app has sound setup with KAT Enhancer (no DAC L+R).

I got an alarm for a meeting. The music volume decreased during the notification sound.

But when the notification finished, the music volume didn't rstore to previous level.

I did not yet search the forum (It could be a known issue), but since I'm already posting I just writing it down.

Thank you Timduru. I'm relly happy with my tf101!!
[Eee Pad Transformer Android Development] brk:
I've already asked in Timduru's kat thread, is it possible to add ad-hoc wifi suport to this rom? or is it done at kernel level?

Thanks.
[Eee Pad Transformer Android Development] rickgillyon:
Why ask twice when you can see he reads both threads? :rolleyes:
[Eee Pad Transformer Android Development] timduru:
That was the goal of that: http://xdaforums.com/showthread.php?t=1806937&highlight=adhoc

But I didn't succeed fully.

Even it it sees the networks with that, it times-out when connecting.
[Eee Pad Transformer Android Development] ganirg:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Great ROM!

Is it possible to change the phisical keyboard layout option, in tablet settings menu, so i could choose two different layouts?
[Eee Pad Transformer Android Development] timduru:
Yes, I fixed that some time ago,

just add the different layouts languages for the keyboard in the regular keyboard options.

Then you can switch the layouts "live" with ctrl+space.
[Eee Pad Transformer Android Development] farsight73:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

So do I really need to perform factory reset in recovery before flashing B142 on top of B136? Or just wipe cache and dalvik?

I see the pain of re-installing all user apps if the wiping factory reset is a compulsory.

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] timduru:
New 4.2.1 preview version B143

Download: EOS4.2.1-tf101-20130124_previewB143.zip

That version should fix the disappearing menu key if you hide the navbar.

Test & confirm ;)

No you don't need to, but if ever you have issues, yes you should do a full clean install before reporting the issue.

I don't do a factory reset between versions, but once in a while it's good to do though.

It's a pain to reinstall everything, and the tablet will lag more for a few minutes / hours as it restores / rescan after the full wipe.

But once it's done it can really help the speed and crashes to have a clean install in case you had some old stuff creating issues.
[Eee Pad Transformer Android Development] farsight73:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Gee.. Now it B143.. I just finished downloaded B142..

Thank for quick update and lucky I haven't flash the B142 so now I will jump in to the latest B143 instead..

P/s. Where's the B143 download link by the way?

Edit.. Got it! Thanks..

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] frederuco:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Confirmed menu key is fixed in B143.

thanks for the quick turn around on this!
[Eee Pad Transformer Android Development] kaspertje100:
I came from Preview B136 (worked fine except weird red dots in my screen but thats something else I guess..)

Now I installed B143 I waited for 30 minutes now and my tablet still didnt boot it is stuck at the boot animation... I tried to reinstall at again same problem... (yes I did wipe dalvik/cache/system, I even did factory reset...) Now I went to B136 and this wors:S what can be the problem?
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Could someone direct me to the latest gapps-TF101-only file(s)? I'm downloading the 143 EOS but would like to run the latest gapps w/ it.

Thank you Timduru and all contributors.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #142

Kat Kernel 80b / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] timduru:
Try flashing KatKernel 80B then wipe cache + dalvik

It's still the gapps that are in the #1st post.
[Eee Pad Transformer Android Development] Quintasan:
@timduru

Is it possible to add Japanese to the dock keyboard layout or is it already there and I'm just blind?
[Eee Pad Transformer Android Development] shonkin:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Thanks, Timduru, re the gapps version. And yes, the menu button works fine in 143... I've finally gone ahead and turned off the Nav bar as a result.

Again... thanks so much for a great rom!

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4 Jellybean / Preview version #142

Kat Kernel 80b / Kat App

--

Don't blame Jesus for the Republican Party. Blame Ayn Rand.
[Eee Pad Transformer Android Development] frederuco:
I don't have my tablet handy, but check out the app External Keyboard Helper.

It should allow you to get Japanese layouts on the keyboard. Check out the DEMO version first, it will not let you type a space properly, but you can still test the rest of the keys.

If it works, buy a copy of it.
[Eee Pad Transformer Android Development] poetter747:
Just a confirmation,

now i flashed 143 with gapps 20130105 and Kat 80BBBBBBB Kernel, and everything is fine.

Don't know why it did'nt boot with 142 kernel.