yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] rosco_pc:
Look at the SDK documentation: http://developer.android.com/reference/android/net/TrafficStats.html :)
[Eee Pad Transformer Android Development] Sun2down:
Worked for me! Many thanks.

Gesendet von meinem GT-N7100 mit Tapatalk 4
[Eee Pad Transformer Android Development] xbs:
Working fine here too.
[Eee Pad Transformer Android Development] mattgren:
Working for me too, just plugged in - no alteration to settings at all.
[Eee Pad Transformer Android Development] kokabunga:
Update : Me too! Now album art slowly pan without jumping top/bottom ; I just have to reboot

[MENTION=3951330]timduru[/MENTION]

With Katkiss 22 and gapps 4.3, dock's keyboard strokes buffering are back (no more lost off strokes, when typing directly from launcher : it launch google now with all strokes)

thanks man

and the tf101 is now a flying meerkat...

Envoyé depuis mon Transformer TF101 avec Tapatalk 4
[Eee Pad Transformer Android Development] talman26:
Working great here also. Only thing that seems to have a problem is the xda app sadly. Alot of the topics wont load. Really weird.
[Eee Pad Transformer Android Development] crisscross3:
Running #22 and I'm experiencing battery drain when docked to the keyboard. I don't believe this was happening on #20 (I skipped #21).
[Eee Pad Transformer Android Development] YeloSub7:
Ya that's how I've always done it too... Except for this ROM. Might be the port or cable... Always something
[Eee Pad Transformer Android Development] ryanmm:
With this ROM is there a way to disable the battery percentage indicator?
[Eee Pad Transformer Android Development] aparanoidandroid:
Stuck at boot loop

I wiped data/factory reset and /system

flashed latest stable Katkiss rom 4.3 build 020 for my tf101 and gapps from the 1st post and now I'm stuck in a boot loop with the 4 colors. I waited 15 minutes and it didn't boot.

I tried repeating the process again and ran into the same issue.

Has anyone found an issue for this?
[Eee Pad Transformer Android Development] dbuckham:
Which Recovery are you using?

Did you factory reset before you installed?

Have you tried re-downloading the ROM and GAPPS?

Have you tried just installing ROM?

Was the flash successful? (Recovery should state this)

Are you wiping caches after flashing?

Hoping this spurs something for you...

EDIT: I notice you said you updated to the latest build #20. The latest build is #23. Maybe try the update?
[Eee Pad Transformer Android Development] aparanoidandroid:
1. Clockworkmod Recovery 5.8.3.4

2. Not yet

3. Yes

4. Yes

5. Yes

I'll try 23. but how do i transfer the rom to my tf101 since it wont boot ? Edit: Where do I get build 23 from ? The 1st post shows 20 as being the latest stable and 22 as the dev ? TimDuru's site that is linked to on the first page also shows 20 as being the latest stable and 22 as the latest dev build.
[Eee Pad Transformer Android Development] just lou:
#1 is your problem.

Sent using the free XDA-Developers App because the new Premium Version doesn't work.
[Eee Pad Transformer Android Development] aparanoidandroid:
why?
[Eee Pad Transformer Android Development] just lou:
Because it's been stated ad nauseum in here that using CWM will more than likely soft-brick your TF if you attempt to use it to flash KK.

Some people claim CWM works though.
[Eee Pad Transformer Android Development] aparanoidandroid:
thanks for sharing that. I am new to this rom and had no clue.

I know how to flash twrp in fastboot. How do I put the TF101 into Fastboot/APX mode to flash it ?
[Eee Pad Transformer Android Development] just lou:
Go here and just flash it in CWM:

http://xdaforums.com/showthread.php?t=2434422
[Eee Pad Transformer Android Development] aparanoidandroid:
So do I flash it like any other zip in CWM ?
[Eee Pad Transformer Android Development] just lou:
Yes, but do NOT flash anything else with it when flash it.
[Eee Pad Transformer Android Development] aparanoidandroid:
I did that but when I rebooted, it went back into CWM. When I flashed it it did report that it flashed without any errors.
[Eee Pad Transformer Android Development] just lou:
You got me then. You're gonna have to try and flash a 4.1 ROM in CWM or use adb. I haven't used APX mode in so long, I forgot how. There are several threads on it around here though.
[Eee Pad Transformer Android Development] aparanoidandroid:
I got TWRP installed now. Its related to a problem I've had since I got my TF101. After I flash a ROM, it will always boot directly into recovery mode. The only fix is running this command via adb or from Terminal if Android is booted up:

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
[Eee Pad Transformer Android Development] just lou:
If you do a full wipe, install KK 22 and GAPPS, you should be good to go.
[Eee Pad Transformer Android Development] dbuckham:
I'm not sure BUT, I'd try doing a COMPLETE WIPE. Make sure you do at the least a factory reset. Something is staying so maybe something in an Internal partition? Someone else may be able to speak wisdom to this.
[Eee Pad Transformer Android Development] mgeniusm:
build

I think you'll find latest build is #22
[Eee Pad Transformer Android Development] cracks:
Updated with TWRP 2.6.0.0 from #19 to #22 yesterday without full wipe and so far so good. Why there are full wife needed in this update?

Full wipe is kinda pain in the ass because I need to restore all apps.

Btw anyone else not recieving notificiations from Hangouts app and sync for this app is broken. I have delays ~1 hour for recieving messages.

Gmail are giving notificiations to 1 email per 20. Notifications are enabled for all categories. Apps before #22 was banks, now it`s from first thread.
[Eee Pad Transformer Android Development] timduru:
The answer is kinda in your own message, seeing that you did not do it and you are now having issues.

Did you at least format /system before installing 22 and the 4.3 gapps from the OP as indicated ?

If you don't do at least that, it's going to mix gapps packages which is bad.

Certain components in the gapps package are system components that requires the same signature to work,

and will most likely not work together.

Some packages are containing apps that are now available through playstore like gmail, other packages are not.

So if you mix It's just unpredictable what will happen and will most likely cause what you're experiencing.

The only way to make sure it's going to work 100% the same for everyone is full wipe.

otherwise I cannot predict what you did before, like installing bank gapps for example...

So for your problems I'd suggest to at minimum redo the install procedure, make sure you format /system before.

Uninstall the apps like gmail and such that are having issues.

Reinstall them clean from the market.

See if that solves your issue,

if it doesn't => full wipe.
[Eee Pad Transformer Android Development] cracks:
I have sync issues since I went to your rom. Before I was on noname 4.2.2 and did full wipe before comming to yours. I will try to reinstall those apps. Thanks for advice! ;)
[Eee Pad Transformer Android Development] demod_oz:
A Partial wife and also multiple wives are always trouble!
[Eee Pad Transformer Android Development] mgeniusm:
lol

now this is why there should be a like button in xda!
[Eee Pad Transformer Android Development] TomTcom:
Plus a dirty wife always spells trouble too! Haha!
[Eee Pad Transformer Android Development] Chinaboy5216:
Hi Tim, I always do like this and have never had issues nor with no name before nor with kk. Did do a full wipe when going from no name to kk.

1 wipe system

2 install ROM and gapps

3 wipe cache and dalvik

4.reboot

Picked this sequence up from Josteink and have been using it as far as I can remember. By the way I use twrp.
[Eee Pad Transformer Android Development] jays473:
either update to CWM 6.0.2.7 or switch recovery to TWRP 6.2
[Eee Pad Transformer Android Development] PRBajista:
Depends on what you mean by "dirty"... Lol
[Eee Pad Transformer Android Development] ryanmm:
Anyone know?
[Eee Pad Transformer Android Development] PeQuEsan:
Last night I wiped my tablet and installed KatKiss 22 + 4.3 Gapps + fsync_on... All is wonderfully smooth and stable. No SODs Timduru.

Great work man! Again!

Desde el móvil, con Tapatalk...
[Eee Pad Transformer Android Development] Spookymonster:
Every time I reboot, I get prompted to select a launcher again. Trebuchet seems fine after that, until the next reboot. Is this normal?
[Eee Pad Transformer Android Development] TomTcom:
Probably not. Maybe clear defaults in the app settings, reinstall from the market, or worse case try fix permissions in recovery.
[Eee Pad Transformer Android Development] Spookymonster:
Tried clearing both launcher defaults and fixing permissions. Still no good. Couldn't find Trebuchet launcher in Play store to reinstall. Weird.
[Eee Pad Transformer Android Development] TomTcom:
How about clearing data? I know it will clear your settings but maybe it needs a full reset of the app for some reason?

You could also wipe cache in recovery which will reset apps and reoptimize them as Trebuchet is loaded as a system app.
[Eee Pad Transformer Android Development] Spookymonster:
Yep to both, still n/g.
[Eee Pad Transformer Android Development] TomTcom:
Lol...perhaps backup with titanium, uninstall, reinstall?
[Eee Pad Transformer Android Development] frederuco:
Yup, got to KatKiss 4.2.2 and you can change it. This has not been added to KatKiss 4.3 yet.
[Eee Pad Transformer Android Development] Jamesyboy:
If I understand correctly, that's an XTheme Engine Theme. For the life of me, I haven't been able to find a single good looking theme. What's the name of it? Any way you can post/PM me with a link?
[Eee Pad Transformer Android Development] dbuckham:
Yup! Typo. Thanks.

---------- Post added at 11:15 PM ---------- Previous post was at 11:10 PM ----------

Try installing a different launcher. Set it as ALWAYS. Reboot and see what happens. If all is well, clear your defaults and select the launcher you want.
[Eee Pad Transformer Android Development] scottyf79:
Not sure if anyone else has this issue or if it has been reported already but i seem to have a bit of a strange issue when charging the TF.

What im finding is that when the battery on both my dock and the TF get quite low and i stick it on to charge, the dock charges fully but it is then not allowing the TF to charge as its activating the green "full" indicator light.

I either have to charge the TF seperately or allow the dock to top the TF up then stick it back on charge.

Nothing major tbh but just thought id mention it.
[Eee Pad Transformer Android Development] pjw65:
Thanks, KatKiss-4.3 is really great. #20 and #22. :good:

The only bug I found:

- the German (Swiss) Keyboard uses the Y-Z wrong :eek:

Can I fix it myself and how?

FIXED in #24, thanx. No workaround needed.
[Eee Pad Transformer Android Development] mgeniusm:
charging

happens to me occasionally, usually when dock is about 3% and tab is over 60%. if I let the tab get below 60% rarely ever happens.
[Eee Pad Transformer Android Development] scottyf79:
:good: gotta look after our old ladies:laugh:
[Eee Pad Transformer Android Development] XellossMetallium:
How to setup

Dear developer, thanks for your work!

The volume rocker (vol DOWN button) of my TF101 is unresponsive, so going to recovery is impossible. Actually I've almost never used this key and never upgraded from the last stock rom. I have no experience with asus products so I'd like to know if there is a safe method to install your rom without the aforementioned button (I have the root access).. if not I'll have it repaired :)

thanks!
[Eee Pad Transformer Android Development] Kingzak34:
Flash a ROM without volume rocker is never safe ;)

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] xbs:
Isn't it possible to root the device using a PC tool and after that install goo manager, from goo install twrp, install an app to reboot to recovery from google play and install KK?

After root, twrp and KK are installed you'll be able to boot to recovery from power menu.
[Eee Pad Transformer Android Development] TomTcom:
Very true but if they get boot loops or or problems it could be tough. Either way you present the best method if they want to continue flashing and whatnot.
[Eee Pad Transformer Android Development] xbs:
It's very risky for sure if something goes wrong.
[Eee Pad Transformer Android Development] Spookymonster:
Figured my launcher problem out. Nothing to do with KK. I installed Launcher Switcher and looked to see what else was reporting itself as a launcher. There was an additional app (Bit Web Server) on the list. When I uninstalled it, the problem went away.

Thanks for all the suggestions!
[Eee Pad Transformer Android Development] frederuco:
That has been happening on my TF since the Megatron days. Happens on all ROMs, even stock. I think it is a hardware issue myself. I just charge it and check after 15 minutes that the tab percentage has gone up. If not, undock and dock and it will charge.

Not a good idea but it is possible. Could be a huge issue if you get in a boot loop and then your only option is to use ADB to try to boot to recovery.
[Eee Pad Transformer Android Development] pjw65:
German (Swiss) Hardware Keyboard QUERY instead of QWERTZ

FIXED in #24, thanx. No workaround needed.

WORKAROUND to help myself:

$ adb shell 'find / -iname asusec'
$ adb shell 'egrep "(21|44) " /data/data/org.autoparts.settings.device/asusec* /system/usr/keylayout/asusec*'
/data/data/org.autoparts.settings.device/asusec.kl:key 21 Z WAKE
/data/data/org.autoparts.settings.device/asusec.kl:key 44 Y WAKE
/system/usr/keylayout/asusec.kl:key 21 Y WAKE
/system/usr/keylayout/asusec.kl:key 44 Z WAKE

/data/data/org.autoparts.settings.device/asusec.kl are QUERTZ

/system/usr/keylayout/asusec.kl are QUERTY (wrong for swiss german layout).

$ adb pull /system/usr/keylayout/asusec.kl asusec.kl

So I have to change them on my computer:

To write back, I have to make /system rw

$ adb shell 'mount | grep system'
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
$ adb shell 'mount -o rw,remount /dev/block/mmcblk0p1'

$ sudo adb push asusec.kl /system/usr/keylayout/asusec.kl
68 KB/s (3354 bytes in 0.047s)

make /system again ro and show my changes:

$ adb shell 'mount -o ro,remount /dev/block/mmcblk0p1'

$ adb shell 'egrep "(21|44) " /data/data/org.autoparts.settings.device/asusec* /system/usr/keylayout/asusec*'
/data/data/org.autoparts.settings.device/asusec.kl:key 21 Z WAKE
/data/data/org.autoparts.settings.device/asusec.kl:key 44 Y WAKE
/system/usr/keylayout/asusec.kl:key 21 Z WAKE
/system/usr/keylayout/asusec.kl:key 44 Y WAKE

After reboot, everything is fine.

As long as I don't want to change to a US (or other QUERTY) layout.

FIXED in #24, thanx. No workaround needed.
[Eee Pad Transformer Android Development] XellossMetallium:
Thanks! I'll be cautious and have the button repaired before trying anything! :D
[Eee Pad Transformer Android Development] Lethe6:
22 won't work for me. It reboots in loops endlessly. If I'm lucky I get a whole minute out of it before it reboots again. Sometimes it doesn't even get to the android screen, I have to forcibly reboot it. I did a full wipe, even /sdcard/ and no change. No custom kernel or anything, just rom and gapps. Restored to 21, works fine.
[Eee Pad Transformer Android Development] dbuckham:
Odd. I'm wondering if it is connected to your overclocking?
[Eee Pad Transformer Android Development] Lethe6:
Should have probably mentioned, didn't overclock after doing a full wipe, and didn't reinstall any apps. Couldn't get that far. It's as stock as it could be.
[Eee Pad Transformer Android Development] mattgren:
Strange. I had something similar with 21 - 22 has been rock solid for me over the last 100 hours.

I eventually restored my nandroid backup of 20, then flashed 22.
[Eee Pad Transformer Android Development] HectorAguirre:
Went back to the developer and said that they are using functions like getTotalRxByte, and said that this may not be supported in KK4.3, I also tested some other applications like "My Data Manager", and also didn't worked, Do you think this can be fixed in KK?
[Eee Pad Transformer Android Development] jimpmc:
Just upgraded my TF101 from ICS to KK 4.3 #22. First off, wow! The ROM is great and really makes it feel like a whole new tablet.

I did have an issue arise and since this is my first experience with 4.3, I don't know if it's general Android behavior or specific to this ROM. My issue relates to multi-users and notifications. I set up multiple users for each family member, and installed their own email app with their accounts. What is happening is that notifications for each user (e.g., each email address) are showing up for all users. So user A sees the notifications for their own and user B's emails and vice versa. You can't read the emails by clicking on the notification that doesn't belong in your account, but you can see the subject and part of the message. Is this the way 4.3 generally works or is this specific to this ROM? It seems unexpected that they would allow other users to see other users notifications, but maybe I'm missing how this is supposed to work.
[Eee Pad Transformer Android Development] 53l3c7a:
Yeah, known issue. Not sure if its a general 4.3 bug or specific to KatKiss. I only have one user; my wife has an iPad :(

Edit: post containing the same complaint.

http://xdaforums.com/showthread.php?p=45295992
[Eee Pad Transformer Android Development] jimpmc:
Thanks...followed the post and then dug a bit deeper. It seems to be related to using the Tablet UI instead of the now standard Phablet UI. I came across a mod for the Nexus 7 2013 to let it use Tablet UI and the caveats are:

So I suspect that Katkiss may have the same limitations if they are using a similar mod to access the remnants of Tablet UI in 4.3.

I guess I'll just have to get used to the Phablet UI, since that seems to be what will be standard on tablets going forward (for now).
[Eee Pad Transformer Android Development] rosco_pc:
''

Well all the relevant code is in KK:

https://github.com/timduru/platform-frameworks-base/raw/rCS/core/jni/android_net_TrafficStats.cpp

https://github.com/timduru/platform-frameworks-base/raw/rCS/core/java/android/net/TrafficStats.java

And there is data:

u0_a33@tf101:/ $ su
root@tf101:/ # cat /proc/net/xt_qtaguid/iface_stat_all
wlan0 1 0 0 0 0 326971282 420678 35489332 250429

I don't know what is missing here, maybe Timduru has an idea??
[Eee Pad Transformer Android Development] timduru:
Yeah weirdly they didn't do it low level enough, so the notifications are reaching the UI,

and they added the test to discard other users notifications in the phone / phablet UI code.

Since TabletUI is not updated anymore by google it doesn't contain that test.

I'll see about that, it shouldn't be too difficult to add it to TabletUI into the next version.

It seems that they changed the code in 4.3 to use the iface_stat_fmt entry

That interface is present in kernel 3.4.

I'll see about porting it back into KatKernel.

That will also most likely fix the missing transmit / receive overlays on the signal cluster.
[Eee Pad Transformer Android Development] qicgun:
Hi anyone have issue with bluetooth tether on this rom.

First time flash this ROM form EOS4 to #020 & #021 (wipe everything, factory reset....) I always experience Bluethooth Share crashing when try to tether from my Nexus 4.

After update to #022 with latest gapps no more crashing, both devices show as connected but cannot browse internet on my TF101.

Transfer files via bluethooth is fine though. Any help appreciated. Thanks
[Eee Pad Transformer Android Development] wn1ytw:
I could be wrong, but I don't believe that bluetooth function has been supported on this ROM or it's predecessors (EOS4 or KK 4.2.2 flavors) ever. Devices, such as keyboards but not tether.
[Eee Pad Transformer Android Development] shonkin:
Glad to report I'm back with a quite nice (almost new) keyboard after the old one died. I was so tired of using the screen to type with! Save that for my android cell phone.

Meanwhile, KatKiss 22 is rockin' along. Rock solid. Can I come up with a complaint? Naaaah. Love the speed. Love the stability. Okay, one -- well, not a complaint but a question. Does this rom tend to unmount the mini-sd card more often than did EOS or KatKiss 4.2? It seems it may do so to me. Not a huge problem, but noticeable to me when I go to read a book and Moon Reader can't find 'em due to the card having been unmounted.

Now, back to enjoying my keyboard w/ KatKiss.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] 53l3c7a:
Do you mean the SD card slot in the dock, or the microSD slot in the tablet? I've never taken my microSD out of the tablet, and I've never found it not mounted. Regular SD in the dock seems to come and go as it pleases.
[Eee Pad Transformer Android Development] shonkin:
Micro-SD. Sorry "Mini-SD" was a misnomer, since all sd cards are pretty much "mini." Every time the tablet goes to sleep, then is awakened, it seems the micro-sd unmounts and has to be remounted.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] frederuco:
Hmm, I only have issues with the SD in the dock, never the micro.

Also, there is a mini-sd card that is between the SD and Micro. If you try to use one of those, then that's your problem! :)
[Eee Pad Transformer Android Development] baseballfanz:
Awesome ROM. I've never had GPS lock so fast onto so many sat before with any ROM. After installing the Kat app and following directions I got 15 birds in seconds indoor.

☞Sent from here☜
[Eee Pad Transformer Android Development] mak8tack:
He might be using an adapter with the mini-sd card. Such as:

https://www.google.com/search?q=min...TF-8#q=mini+sd+card+adapter&safe=off&tbm=shop

I've personally never had problems with a Micro-SD card -> SD Card adapter on either the TF101 or the Dock... both mount ok. With the dock, I just have to remember to unmount it before closing the lid.
[Eee Pad Transformer Android Development] shonkin:
My micro-sd card is in the slot in the tablet, not via adapter in the keyboard/dock. Just to be absolutely clear. ;) I've used it that way almost from the day I purchased the tablet and this unmounting issue is a newer one. Not a deal-breaker, of course, since I can mount it via Settings > Storage > Micro SD. But a little less seamless than it was under EOS 4.2.

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] frederuco:
Perhaps a logcat could shed some light on it since most others are not having the issue.

I have a FAT32 (32 GB) and an exFAT (64 GB) microSD and neither unmount on me under KatKiss 4.3 (or 4.2/EOS 4)
[Eee Pad Transformer Android Development] rosco_pc:
Aah right, I looked at the wrong repository :o
[Eee Pad Transformer Android Development] Chinaboy5216:
64gb? Do you get the full 64gb availability? tf only supports 32gb as far as I know.
[Eee Pad Transformer Android Development] frederuco:
Yup, I can use every last byte on it. Officially, Asus (and Android) does not support exFAT so they cannot advertise 64 GB compatability as 64 GB is SDXC which uses exFAT. Even if that is not supported on a specific ROM, it can be formatted for FAT32 with 3rd party tools or you can also use NTFS.

I have a 64 GB microSD and a 64 GB SD both formatted for exFAT. Both are loaded with media for my long international flights for business.
[Eee Pad Transformer Android Development] qicgun:
Thanks for the info, just look thru KK4.2.2 mention some issue with bluetooth. will wait for it to be resolved.
[Eee Pad Transformer Android Development] Chinaboy5216:
Wow, great this i did not know yet.

Need to get a new card so this info comes with a perfect timing, thanks Frederuco