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

As I noted, I'm also good w/ this version. Would add that like you I don't use the default desktop manager; I use Apex.

Asus Transformer TF101 16g / 1.4ghz overclocked

EOS 4.2.2 Jellybean / Preview version #168

Kat Kernel 94 / Kat App

--

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

Apex is good too. I used it for a long time before Nova. I would be using Nova or Apex as my launcher even if the stock launcher was perfectly smooth. They are just so much more configurable and fast.
[Eee Pad Transformer Android Development] JoinTheRealms:
Nova and apex are very smooth as lauchers but that navbar input lag is just too noticable from me, try Go Launcher ex (not the pad version) and be amazed with your tf101.
[Eee Pad Transformer Android Development] st0nedpenguin:
I stopped worrying about the launcher, it's not like I sit staring at it for longer than the 2s it takes to launch an app.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I do not like Go Launcher. ...I have zero lag on my TF using Nova even with the navigation bar enabled. I'm on my Nexus 7 at the moment, and my TF is just as smooth.
[Eee Pad Transformer Android Development] JoinTheRealms:
With nova if a pull one of the tabs up and down fast my finger will reach back to the top as the tab is reaching the bottem (maybe just under half a second behind-----so still very little lag im just picky lol) with go launcher its the most reponsive part of my tablet. Its even less lag than using the status bar while in browser. This is just my experience.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Interesting. I just don't seem to have this issue. At least I'm not noticing it which I guess is the important thing. ;)
[Eee Pad Transformer Android Development] Isham.padron:
Running 156 and kat kernel. Sometimes i get a lag or stutter when im scrolling slowly. Ive gotten this before in pevious builds.

168 is a lot better. I'm getting smoother scrolling.
[Eee Pad Transformer Android Development] jesuita:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Also on B156 and Kat94.

Whats the trick to keep sound on, from time to time it just turns off and I have to enable it again on Kat, not a big drama but still annoying.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Kat is the easiest option. It did it to me on on 168 yesterday too.
[Eee Pad Transformer Android Development] MassStash:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Ah haaaahh! Its in /data/media/! Moved everything to sdcard aka emulated/0... Prolly borks me for easy drop back to 4.1.2, but this is so good so far I've committed! Haha. And is it the Rom version, or recovery that needs things unusual with the "emulated/0" oddness? Point me where to read if I'm behind the curve here please, just jumped up to 4.2.x recently...

Nova works fantastic for me btw. B168, Kat Kern 94

~S-Off LTEvo; Viper4G_3.x.x; Elementalx

cpu0/1: 1.7ghz ¦ 192mhz ¦ sleep: 486mhz max

Intellidemand

row

mpdecision: off
[Eee Pad Transformer Android Development] mgeniusm:
no problems

168 and nova launcher working great for me!
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

The new /storage/emulated/0/ is for the multi-user in 4.2.

Additional users are at:

/emulated/10/

/emulated/11/

/emulated/12/

Etc.

When each user logs in their emulated folder is mounted at /sdcard/ and also /storage/sdcard0/

Be sure to use TWRP 2.3.2.3 or newer to allow recovery to work best!
[Eee Pad Transformer Android Development] MassStash:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Ahhhhhhh, that make a day sense now! Thanks bro

~d2spr runnin' CarbonRom

cpu0/1: 1.7ghz | 192mhz | sleep 486mhz with latest ktoonsez kernel

Intellidemand

row

mpdecision: off
[Eee Pad Transformer Android Development] kukky:
R: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

i'm on b168 and i have to say this is very reactive rom...i don't know why, but firstly when i flashed i was a little bit confused because everything was very very slow...menu, application, connection, etc...i putted my tf in standby all night long and this mornig it's faster like a bullet!!!!.....

good job!!!

Inviato dal mio Transformer TF101 con Tapatalk 2
[Eee Pad Transformer Android Development] timduru:
Good to hear,

on the first boot / right after flashing it's normal it's lagging more as it'll restore / rescan all the medias & stuff.

It'll do that even more if you're doing a full wipe.

So yeah, you need to let it settle for a bit after flashing a new rom :)

You can help some of the lag after the install by using the mediascanner filters from the K.A.T app to restrict the mediascanner at scanning only where your media are.

That's the first thing you can do basically after installing the rom:

wipe/ install rom,

then:

1) install K.A.T directly , install mediascanner filters, reboot,

2) launch the app to configure the filters, reboot.

Then mediascanner will be muzzled ;)

Once the filters are configured and that you don't do a full wipe the configuration of the filters will survive a regular flash

so you can skip 2)
[Eee Pad Transformer Android Development] mariox26:
Tim this rom is so great,but i have a little problem,i have installed real racing 3 on tablet and on my phone S2,the difference is image on mirror,on our rom i see no image,put attachment to see,thanks a lot
[Eee Pad Transformer Android Development] mgeniusm:
This rom rocks BUT!!

The rom is amazing, But for me the best thing about this rom is the guy responsible for it! Your interaction with the forum is very commendable.

I think I can talk for everyone when I say thanks for all the time you take not only for developing the rom but also answering questions and helping all!

Thanks Tim
[Eee Pad Transformer Android Development] kukky:
.....ok...i'll follow your tip next flash.....even if...for now this is so little "problem" in front this BIG rom!!!....
[Eee Pad Transformer Android Development] *Detection*:
haha finally :D
[Eee Pad Transformer Android Development] YayYouFixedIt:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

oMg!:beer:

Sent from my Transformer TF101

---------- Post added at 11:16 AM ---------- Previous post was at 10:42 AM ----------

Yeah! The google playstore movies work. This is excellent. Thanks TimDuru.:D

Sent from my Transformer TF101

---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------

One small issue though is for some movies the previews say not available in your country(Canada), but i can watch previews and the movies through the cable providers digital box. i wonder if thats just a google play issue.

Sent from my Transformer TF101

---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------

ok it must be google play cause it does the same thing on nexus 7

edit:

Movies on Google Play are currently available in the US, UK, Canada, Japan, Spain, and France. TV shows and movies are also available for purchase in the US only at this time.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] nachopr:
Hello. I am a happy user of your rom, although I find one thing missing. The menu of "control data consumption." In this menu (inside in) there is an option to declare a wifi as mobile, so that android does not use this connection for large volumes of data. It is an option that comes by default in all stock roms google but for some reason you've deleted.
[Eee Pad Transformer Android Development] ceecee10:
RS2012

Is anybody getting a fc on RS2012? I am running the newest preview with Kat 94.
[Eee Pad Transformer Android Development] sbliner:
I was very happy with the prior combo of EOS 4.2.1 B148 | KatKernel 80b_lidpatch . The only issue really was with the skype mic.

Just upgraded to EOS 4.2.2 previewB168 | Katkernel 94_jb4.2 with KatApp 1.2.7....and I'm glad to report the other side could actually hear me today.

great work !
[Eee Pad Transformer Android Development] i9apps:
WOW Tim! i cant believe this ROM just becoming better and better!

The tf101 never worked better (im on 168b+kat kernel)...Thank you for all the awesome and hard work!
[Eee Pad Transformer Android Development] Taomyn:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Is anyone else able to get text-to-speech to work? I've tried both UK and US and nothing is spoken in the settings example, and all I see in the logs is:

03-02 13:02:43.805 I/TextToSpeech(30253): Sucessfully bound to com.google.android.tts

03-02 13:02:43.805 I/patts (32085): Loading project file (apk mode is true) ...

03-02 13:02:43.805 I/patts (32085): [android_project_file.cc:32] Loading "eng-gbr/phonology_en-GB.cfg" ...

03-02 13:02:43.805 E/patts (32085): [android_file_resource.cc:79] jni: Failed to obtain asset "eng-gbr/phonology_en-GB.cfg"

03-02 13:02:43.805 E/patts (32085): [text_normalizer-inl.h:32] Failed to load DataParamsFile "eng-gbr/phonology_en-GB.cfg" from project file

03-02 13:02:43.805 E/patts (32085): [jni_text_analysis_api.cc:226] jni: Failed to load and initialize text normalizer

03-02 13:02:43.805 E/patts (32085): Failed to load and initialize text normalizer

03-02 13:02:43.805 E/PattsSynthesizer(32085): Failed to load synth data.

03-02 13:02:43.805 E/PattsSynthesizer(32085): onLoadLanguage : Synthesizer failed to initialize

03-02 13:02:43.805 W/ContextImpl(30253): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1424 android.content.ContextWrapper.bindService:473 android.speech.tts.TextToSpeech.connectToEngine:627 android.speech.tts.TextToSpeech.initTts:597 android.speech.tts.TextToSpeech.<init>:553

03-02 13:02:43.815 I/ActivityManager( 714): START u0 {act=android.speech.tts.engine.CHECK_TTS_DATA pkg=com.google.android.tts cmp=com.google.android.tts/.CheckVoiceData} from pid 30253

03-02 13:02:43.875 D/dalvikvm(30253): GC_CONCURRENT freed 756K, 19% free 4569K/5580K, paused 1ms+2ms, total 25ms

03-02 13:02:43.885 I/TextToSpeech(30253): Connected to ComponentInfo{com.google.android.tts/com.google.android.tts.GoogleTTSService}

03-02 13:02:45.815 E/TextToSpeechSettings(30253): Failed to get sample text, no activity found for Intent { act=android.speech.tts.engine.GET_SAMPLE_TEXT pkg=com.google.android.tts })

03-02 13:02:45.815 I/ActivityManager( 714): START u0 {act=android.speech.tts.engine.GET_SAMPLE_TEXT pkg=com.google.android.tts} from pid 30253

03-02 13:02:45.825 E/TextToSpeechSettings(30253): Did not have a sample string for the requested language

03-02 13:02:45.825 D/BluetoothAdapter(30253): 1106391528: getState() : mService = null. Returning STATE_OFF

03-02 13:02:47.515 E/TextToSpeechSettings(30253): Failed to get sample text, no activity found for Intent { act=android.speech.tts.engine.GET_SAMPLE_TEXT pkg=com.google.android.tts })

03-02 13:02:47.515 I/ActivityManager( 714): START u0 {act=android.speech.tts.engine.GET_SAMPLE_TEXT pkg=com.google.android.tts} from pid 30253

03-02 13:02:47.525 E/TextToSpeechSettings(30253): Did not have a sample string for the requested language

03-02 13:02:47.525 D/BluetoothAdapter(30253): 1106391528: getState() : mService = null. Returning STATE_OFF

03-02 13:02:48.295 V/ ( 714): void cb_onMotion(uint16_t)

03-02 13:02:48.575 V/ ( 714): void cb_onMotion(uint16_t)
[Eee Pad Transformer Android Development] inigoml:
Two alternatives:

- Use RaymanFX kernel for CM10.1 (repackaged for EOS4 and linked somewhere in this thread)

- Use KatKernel and wakelock app from Play Store in order to avoid entering into Deep Sleep state.

RaymanFX kernel avoids deep sleep SODs but performance is worst and there are some issues with wifi (less coverage and sometimes wifi do not wake up properly from deep sleep)

Katkerner is by far the best option for perfomance but due to wakelock app battery last for only 48 hours in standby.

I use Katkernel + wakelock.
[Eee Pad Transformer Android Development] wilkster:
I don't usually use TTS but I tried it andI get the same error as you. There is a discussion here http://code.google.com/p/jellytime/issues/detail?id=285, it may be related.
[Eee Pad Transformer Android Development] PMcHargue:
Voice input issue with 168

I flashed:

EOS4.2.2-tf101-20130227_previewB168.zip

B168_DRM_PlaystoreMovieFix.zip

gapps-jb-20130105-EOS-TF101-ONLY.zip

Tim_KatKernel_94_JB4.2_Lidpatch.zip

K.A.T_V1.2.7.apk

Everything sems to work quite well, thank you Tim. However, one app I am using, 'Assistant' by SPEAKTOIT won't allow speech input any longer.

<https://play.google.com/store/apps/details?id=com.speaktoit.assistant>

I figured it might have be something related to 'Hotword detection', but under the TF101 Tablet's 'Settings | Language & Input' I don't see any area there labeled as 'Voice Search'. Am I looking in the right place?

Anyone else have a similar issue that they managed to resolve? I didn't have this problem under 156. The error logs are attached.

Patrick

P.S. Could not get the the upload to work; either the direct, or from a URL. I posted the log on my google drive,

https://docs.google.com/file/d/0B258H385xkQqR2VlTGNMNEVETk0/edit?usp=sharing
[Eee Pad Transformer Android Development] d3l1:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I'm back to nightly 97 because preview 156 had an extremely laggy chrome. Besides that the system and apps were overall not as smooth as the 97 build.

Sent from here using Tapatalk
[Eee Pad Transformer Android Development] Tuborg68:
Sv: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Well, seems as my gps is totally borked. Did a full wipe and installed preview b168, KAT kernel #94 and KAT 1.2.7. Installed the gps fix and rebooted (tried a couple of times) but still not seeing a single sat.

So you think it's hardware fault or can there be something else I could try?

Skickat från min Transformer TF101 via Tapatalk 2
[Eee Pad Transformer Android Development] jab0321:
My speech isn't working either. I have a workout timer app, Impetus https://play.google.com/store/apps/...t#?t=W251bGwsMSwyLDEsImZpLm9ocmEuaW1wZXR1cyJd ,and it normally speaks the workout interval that I am on, but it is not working anymore.
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

97 and 156 are almost identical. Did you try the latest 168?
[Eee Pad Transformer Android Development] newsguy99:
I tried 168b yesterday.. The install went without a hitch.. However, after installing some of the apps I use, I was disappointed that 2 of the favs I use, were no longer supported... Or at least thats what the play store was complaining about..

Gas Buddy was one. I use it all the time, and its a app I really like. So, when I couldn't install this one. I reverted back to 156b...

The other app, I no longer use, but, wanted to still see if it would install was Officemax. Nope.. still can't get that to install.. It'll sideload, but not directly off the play store.
[Eee Pad Transformer Android Development] archcantor:
Well, I personally would try a full wipe / factory reset and load a stock ICS ROM or Revolver. If the GPS works there then you can rule out hardware. I came from Revolver and I thought the GPS there was as good as the TF101 ever got. Now on EOS4 I believe I am back to that standard. (Thanks again Tim!)

Do you have internet connectivity while searching for sats? I think the software looks for an NTP server to get a time lock over the internet to speed up the sat detection. Good luck.
[Eee Pad Transformer Android Development] d3l1:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Oh my, my bad I meant 168. Wasn't running well for me so I went back from 168 to 97.

Gesendet von meinem Transformer TF101 mit Tapatalk 2
[Eee Pad Transformer Android Development] just lou:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I may go back to 97 too. I didn't have any issues until I just saw my sleeping TF reboot itself. I haven't seen that since the first release of stock ICS.
[Eee Pad Transformer Android Development] MassStash:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

On 168 and I've had no reboots and battery life is insanely better than I was getting with k900's last build of aokp

~S-Off LTEvo; Viper4G_3.x.x; Elementalx

cpu0/1: 1.7ghz ¦ 192mhz ¦ sleep: 486mhz max

Intellidemand

fiops

mpdecision: off
[Eee Pad Transformer Android Development] Woody:
I have to agree here. I think that a full clean flash might work for you. Meaning nvflash stock and reset and rewrite the partitions. And then clean install up to #168 and I would bet you'd get some birds pretty quickly.

While I would be comfortable letting my TF stay on this build, I would have to say that I am pretty excited about Cornerstone.
[Eee Pad Transformer Android Development] bunilla:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I cant seem to take a screenshot? Any fix?
[Eee Pad Transformer Android Development] dgcruzing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Anyone else got problems plunging a NTFS drive into dock?

Using KAT app to try to load.. But it's giving me an error. But I can plug it in to the laptop no problems.. Just did a disk scan to fix any errors and no dramas..

Do I have to format it as fat32/exfat to get it working?

I have used it before on ICS so it's definitely JB related..

I am out on the road on a business trip but have a ATV1200 set top box waiting for me in Suzhou so will get to try it in that.. If it works off the bat then it's this machine Rom related.. Will test and report back..

But can others report back using external drives work or not..

The dock is handling small usb drives.. So maybe it's just not liking my portable hard drive anymore..

Preview 168 with JB94 kernel

Sent from my GT-I9300
[Eee Pad Transformer Android Development] zap-o-post:
After a new install of B168, kat 94 and an uptime from 36 hours, I had the WiFi problem again. I can't reproduce the issue, so I have no logs. But I find a workaround. In the terminal (as root) I kill wpa_supplicant. After some seconds WiFi comes back.

@timduru: Can this info help to solve the issue?
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

VOL DOWN and POWER for 3 sec.

Or program a soft key for long press in EOS Control Center - Navigation section
[Eee Pad Transformer Android Development] dgcruzing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

ok, now its the same for the SDcard in the dock..

64g Scandisk extreme class 10..

Bloody thing is not going to mount it..

Giving me the same error as the external HD..

"Damaged card, try reformating it"

Problem i have with that is the camera it came out of see's it..

The two laptops I have had it in over the last few hours see it.

And i have just spent time transfering movies to it as the external HD drive is not working..

and have run the checks on it..

So at this stage its pointing to Kernel problems..

Kat is giving me the error of "drive is busy error=1"

Is there anyway I can get this going in the next day or two so i can watch movies as I take these long fast train trips across China?

If I remember correctly, same SDcard was working for me on EOS#3 as I took it on the month trip through philippines loaded full of movies..

Anyone else got these problems or is it only me?
[Eee Pad Transformer Android Development] timduru:
which button are you using in the K.A.T app to mount it ?

if it's busy it usually means that it's mounted, so try to unmount it first, then hit the mount auto button or try the other one if it doesn't work.
[Eee Pad Transformer Android Development] dgcruzing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

k.. give me a tic and will try it..

as its fustrating the next out of me..

it is formated as a exfat.. is this a problem?

Edit: unmounted microsd card..

tried to mount Dock sdcard within settings.. no joy..

Tried to mount dock sdcard in KAT - Exec error 11 and 12..

unmount just gives me the Exec error 1

Put micro sdcard back in.. no problems.. registered..

Still same on trying to mount Dock SDcard..

Let me format it as Fat32 tomorrow and give it a try and see if that works..

It might be because its formated as extfat at the moment.. and jellybean just doesnt like it it..

As to external hard drive.. still would like others to chime in wiether they are able to use one with thier docks.

So I can trouble shoot this.. As said, Wednesday night will have the ATV1200 to play with so will be able to plug and play with that at nights,

so can compare whats going on..

thats it for me tonight..

othewise 168 had been rock solid for me all day..
[Eee Pad Transformer Android Development] timduru:
Yeah exfat is not supported,

You're better to format fat32, that will work for sure.

NTFS might vary depending on the format, but you should still be able to mount it with limited write support with the K.A.T app.(mount auto)

I can mount my stick fine with full write support too, but I know a few reported issues sometime with automount / full write support.

So you have to fall back to mount with limited write support in that case and use the K.A.T app.
[Eee Pad Transformer Android Development] AstroTrain:
Same issue with rom version and kernal, Wifi randomly fails to connect to network after sleep, toggling the wifi shortcut does nothing, opening settings to get to Wifi option causes a blank settings page, requiring a reboot to solve issue.

I am also getting random Sods on Kat 94. I forget how to make the logs as well.
[Eee Pad Transformer Android Development] frederuco:
[ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

See any of Tim's posts as they are in his signature, or see post 2.

It isn't that hard to find...
[Eee Pad Transformer Android Development] demdh:
AW: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Push
[Eee Pad Transformer Android Development] zap-o-post:
You can solve the problem by killing the wpa_supplicant process.

It's faster then a reboot.
[Eee Pad Transformer Android Development] SmokenAce:
Kat App did the same to me never had the problem before.
[Eee Pad Transformer Android Development] aspros21:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

I always had this issue with eos 4.

Now I use USB otg helper to mount my disks. You can try it.
[Eee Pad Transformer Android Development] aburgthing:
Re: [ROM][4.2 JB MR1] Team EOS 4 *JELLYBEAN MR1* Nightlies -- TF101

Just a note of thanks to the developers for a great ROM. I finally got the time to flash this after running stock for months and I couldn't be happier. I use my pad every day as a productivity tool as well as a consumption device. After hearing that Asus wasn't going to upgrade this any further, I decided to just suck it up and buy another tablet soon. Well after running this for the past 24 hours new life has been breathed into this device. It is faster, smoother with the KAT audio app it is louder and every single app works as designed. Battery life is improved despite over clocking to 1.4. I can't give enough praise for this work of art; to me its perfect. Once again thank you to the developers for providing this. Payday is Friday and for the money you've saved me I have got to make a donation! Thank you.
[Eee Pad Transformer Android Development] CodeKid:
Hi guys,

was your pc able to detect your tf101 when it is connected? this is my problem since eos3. do you have any fix for this?

thanks and more power :)