yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Android Development] coolloser:
Is there a new method for people unable to unlock or am I just reading this wrong? (I'm unlocked on my ME301T but was considering a TF300T for my dad to upgrade his Xoom if I can ensure unlock-ability :D )

No problems here, streaming Songza via bluetooth with no dropouts. Downloading 4.6 now, will update if there are issues.
[Transformer TF300T Android Development] ne0zone75:
The fact that the bootloader of my TF300T is not currently unlockable is a very specific ASUS issue : i had to RMA it and since it returned from their RMA facility, i am unable to unlock its bootloader again :mad: BUT it's moving in a good way ATM... :D

FYI every ASUS tablet that is supported by their official unlocking APK, should be bootloader unlocked without any problem ;)

Kind regards

PS : Thank you for the bluetooth feedback :good: (are you running latest RC2 ?)
[Transformer TF300T Android Development] coolloser:
Ahh okay, so they locked it or mismatched hardware when they repaired it, causing the apk to fail or something...makes sense. Hopefully it happens quickly for you, there is only one locked device in this house (probably around 20+ unlocked) and it will be getting unlocked very soon! :D

Yes, I got the latest RC2 running. I dirty flashed over 5.4 with no immediate issues. Have been streaming over bluetooth for 30+ mins, even ran a couple benchtests at the same time to see if it would stutter but it kept going strong. I also tested the camera because I realized I hadn't touched it in the last build, I installed Google Camera and it's all good (not upside down like my laptop, also Asus! hehe).
[Transformer TF300T Android Development] coolloser:
I forgot about Greenifying Songza so I got the dreaded constant wakelock from it. This after I rebooted once, ran Antutu and quadrant, listened to Songza for 62 mins and let it stay unplugged over night. The battery was at 83% when I went to bed so I would say that losing 17% in that time is pretty good from my experience. It also stayed at 100% after unplugging unlike when I'm on Omni where it starts dropping right away.
[Transformer TF300T Android Development] ne0zone75:
Hi, very interesting ! Thanks to [MENTION=5161352]JustArchi[/MENTION] optimizations and 'Official Linaro GCC' v4.8/7 (ROM/kernel) :good:

Good night

Sent from my TF701T
[Transformer TF300T Android Development] fezza:
Another TF201 happy camper on RC2 build, working flawlessly for the light use it's getting. Slimkat has given it a new life!
[Transformer TF300T Android Development] GibonXL:
I've made a clean instal on my TF201 with F2FS and standard steroids pack :)

Kernel is Geas v7.

You guys have to believe my words, our old TF201's are rising up from the ashes like a phoenix :)

This is the fastest and most responsive KK rom for TF300/201 out there! Forget about benchmarks (e-penis), as end-user experience is all it matters. I've tried CM11 and Crombi-KK and for me the Slim base has a greater potential for development.

I was unable to get any lag while browsing: a truly internet tablet, just the way it was advertised by Asus some two years ago :silly:

The rom Is not perfect, BT is going off from on by itself, I won't be able to estimate the battery life accuratelty without the dock battery indicator.

As for yesterday tests, I can tell You the system was consuming the battery gently :good:

If You want to listen to music, You nedd to get an app, I have Apollo 1.3 from XDA working just fine.

[MENTION=5280400]ne0zone75[/MENTION]

The things are moving to a good direction, hopefully You'll get Your unlockments soon :)
[Transformer TF300T Android Development] ne0zone75:
Good morning and thank you !,

I truly hope that my tablet will get unlocked soon in order to apply CyanogenMod's 'dock battery status display' code over SlimKAT and regarding bluetooth, i think that i will replace SlimKAT bluetooth subsystem by CyanogenMod's one like i have already done for my S4 mini SlimKAT ports :good: :silly: ;)

Greetings
[Transformer TF300T Android Development] luismiguel1977:
I've noted similar BT issues, and grimlock kernal seems the most reliable kernel currently for WiFi and BT. I flash the slimkat extreme patch after flashing kernel to enable the tweaks as well with no issues.

The ROM includes music apk which isn't too shabby a music player imo:good:

Slim5.6 battery life is stellar, with greenify, I get only a percentage or two drain while tablet is not in use for a day even!:laugh:victory: this is with WiFi always on even, while docked seems slightly more drain, always been the case for me.

Thanks to neo for the ongoing great work, its appreciated!!!

Won't be buying a new 10" tab until my tf201 is broke;)
[Transformer TF300T Android Development] fezza:
My TF201 is connected to my solar system's transformer via BT during the day which uploads stats to the net every 10 mins, so no BT problems with me. I haven't installed any other kernel except the one that came with the RC2 5.4 build.

Really loving this rom on my TF201 Mk II :cool: really feels like a brand new tablet!
[Transformer TF300T Android Development] shawnbrennan55:
Bluetooth appears to be working fine for me as well.
[Transformer TF300T Android Development] GibonXL:
Could You share what exactly did You greenify:

- were these external apps (Yours)

- or did You use xposed module to greenify system ones - if so, please write which.

I didn't greenify anything this time, because I use app "system unistaler" to delete unused gooogle apps, google services and some system stuff, such as e-mail, exchange, talkback etc. No system instability has been noticed by me :good:

[MENTION=5280400]ne0zone75[/MENTION] - it's nice to read You're finding workarounds with the CM sources :highfive:
[Transformer TF300T Android Development] ne0zone75:
So it seems, from what i am reading here, that it is confirmed that bluetooth is working as it should out of the box with embedded CyanogenMod kernel on TF201; considering this, there absolutely no reason that it is different on TF300T because the kernel packaged into my ROM installer is for it; compatibility issues caused by the embedded CM kernel should only arise for the TF201 and AFAIK there are none hopefully... :good:

As bluetooth is confirmed to be working with embedded CM kernel on TF300T (probably) and TF201 (for sure...), i am not planning to replace the entire SlimKAT bluetooth subsystem by CM's one ATM...

Hello, your device is a TF300T or a TF201 ?!

Anyway, users who are experiencing bluetooth issues with a custom kernel flashed to their device should look for support from the DEV who is sharing it; maybe that you need recompiled BT and Wi-Fi kernel modules matching your custom kernel in order to have those working...

Now, i am really glad to learn that most of you are happy with my Tranformer port, [MENTION=5161352]JustArchi[/MENTION] v3 optimizations + official Linaro GCC are true benefits for custom ROMs. It seems that battery life is now very good on RC2, thanks to 'JA' for it ! :good:

Enjoy SlimKAT :D

NB : you might already have noticed my little announcement on post number 1 :

i have created today a dedicated TWRP for TF300T thread

over HERE with updated STABLE & DEV branches AND soon the TWRP subsection of post number 1 of this topic will be deleted ! The reason for this splitting is to provide support for one thing at one place...
[Transformer TF300T Android Development] shawnbrennan55:
Yes, TF300T.

~~~~~

Samsung Exhilarate (SGH-i577)

ROM: Gummy Nightly 05/31/14

Kernel: CyanogenMod

GApps: BaNkS Minimal 05/16/14

Recovery: Philz Touch 6.19.2 (CWM 6.0.4.7)

---------- Post added at 05:11 AM ---------- Previous post was at 05:07 AM ----------

Try PA GApps. They have an uninstall zip that you can flash immediately after flashing GApps that let's you select which apps you do not want to install.

http://xdaforums.com/showthread.php?t=2397942

~~~~~

Samsung Exhilarate (SGH-i577)

ROM: Gummy Nightly 05/31/14

Kernel: CyanogenMod

GApps: BaNkS Minimal 05/16/14

Recovery: Philz Touch 6.19.2 (CWM 6.0.4.7)
[Transformer TF300T Android Development] ne0zone75:
BT issues...

Oops... i forgot to give a look at your signature... :confused:

Now writing for every user..., it is confirming that bluetooth is working as it should OOTB on the Transformer series of my SlimKAT ports (TF300T/TF201/ME301T) without having replaced the SlimKAT BT subsystem by CyanogenMod one... :good:

BUT, there are issues with it which seem to occur only when running a custom kernel, like it has been already reported back ;) If those are not solved by updating kernel modules accordingly after having flashed a custom kernel, then i will maybe reconsider switching bluetooth subsystem from SlimKAT one to CyanogenMod one at compilation time...

With that said, please be sure that i keep in mind every confirmed bug in order for you to have the best user experience with SlimKAT custom ROM on your device, some of them are port wide while others are device specific as you might already know...

Kind regards
[Transformer TF300T Android Development] Quimicax:
Dont have BT problems here! :D

5.6 Running Very Smooth :good:

4.4.3 Is Out
[Transformer TF300T Android Development] ne0zone75:
4.4.3 :victory: :good: ;)

Greetings

Sent from my GT-I9195
[Transformer TF300T Android Development] coolloser:
I bet I don't have bluetooth issues on the ME301T because the kernel patch that we use probably replaces the bluetooth..,so my tests likely didn't mean much! :D
[Transformer TF300T Android Development] ne0zone75:
BT + DEX concerns...

Well... i am happy to read that you seem to have a nice SlimKAT user experience with your ME301T :good:

Now writing more widely..., i do think there is some misunderstanding somewhere about my concerns regarding bluetooth over my Transformer series SlimKAT ports :

-> first of all, i never managed to successfully build the entire SlimKAT BT subsystem across my target devices when porting SlimKAT by using CyanogenMod device / kernel source trees

-> from that point there are two options :

the basic bluetooth support in my straight SlimKAT port is sufficient as is for the target device : it seems that it is the case for TF300T/TF201/ME301T ;) Here, BT may be failing when having flashed a custom kernel without updating kernel modules...

the basic bluetooth support is not suitable for the target device : it is the case for S4 mini, as a result and in the worst case BT cannot be turned ON at all... Here, a solution i've found is to replace the original SlimKAT bluetooth subsystem by CyanogenMod's one... and after having replaced it there is still a failing possibilty for the same reason as above when using a custom kernel...

That's it ;)

Finally, i would like to say that [MENTION=5767881]Phenom2122[/MENTION] pointed out inconsistencies in my ODEXED builds (S4 mini series) and i thank him for this ;) [MENTION=4551757]Silesh.Nair[/MENTION] just told me about [MENTION=4944549]MatrixDJ96[/MENTION] ODEXING script and you can give a look at it here..., so : every upcoming weekly will be reverted back to DEODEX, letting every one of you the ability to get an ODEXED build easily by using the above mentionned tool if you want to; i do think that everybody will be satisfied that way :good:

Very nice evening :D
[Transformer TF300T Android Development] coolloser:
Ya, that's what we had before out patch and the touch was wonky.

Fine by me, I've never really noticed a difference personally with Deodex vs. Odex except perhaps the battery life. Good to give people the choice either way :D

By the way; Thanks for being such an involved Dev and keeping us up-to-date!
[Transformer TF300T Android Development] luismiguel1977:
Only thing I DONT greenify is my Taptu widgets (have them set to poll for updates every 6hrs) and my weather widgt as it want it to also refresh every 6hrs. I do run the xposed enabled version, fnd it to hibernate more reliably.

Always been using TiBu to freeze then uninstall picott, as well as "news and weather genie" as I don't use em,

---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------

Only reason I stick with GrimKern is for its F2fs kernel version, I'm hooked on internal formatted to F2FS, its as snappy as data2sd evr was for me!!
[Transformer TF300T Android Development] ne0zone75:
Hey ! My purpose here was to clarify MY concerns regarding BT... I cannot agree more with you than i am about the benefits of switching from embedded CM kernel to a F2FS custom one like GEASS / GRIMLOCK. :good: ;)

Good night :D

Sent from my GT-I9195
[Transformer TF300T Android Development] Frankyg:
Hey, rom is very good for me so far.

Just got an issue when I connect the dock and try to access the sd card, ES file explorer gives an error "Sorry current OTG USB device format is not supported, only Fat32 now". Card format is fat32 - any idea why I get this error?

Thanks

edit * my bad it was formatted as fat.
[Transformer TF300T Android Development] golokipok:
Can someone extract the boot.img from this ROM please? I'm quite unfamiliar with unpacking blobs. I'll try to edit it for x-axis inversion.
[Transformer TF300T Android Development] ne0zone75:
Next weekly will be 'APP2SD' enabled...

Good morning,

SlimKAT build 5.6 has embedded 'APP2SD' feature BUT because a part of the source code is device specific AND because i forgot to add it into my CyanogenMod device sources tree, it is not enabled in the current weekly... :confused:

It will be the case in upcoming release :victory: :good:

You'll find SlimKAT 'APP2SD' screenshots below from my S4 mini series SlimKAT ports...,

Have a very nice day
[Transformer TF300T Android Development] ne0zone75:
Do you mean 'unpack boot.img' ?! if that is the case, you will find 'BootTools' and 'BlobTools' over 'AndroidRoot' GitHub page here...

You will have to clone these two repositories by using 'git' command and then compile the tools in order to have fresh binaries...

Are you sure that x-axis inversion cannot be completely managed from inside your ROM ?!

Regards

Sent from my TF701T
[Transformer TF300T Android Development] golokipok:
Hello, I'm not familiar with git or even with compiling whatsoever :( I just wanna give it a try because it's been a while since someone made a compatible kernel.

I'm trying to do this: http://www.pc-xp.com/2013/05/29/tf201-v0-3-with-inverted-x-axis-digitizer-fix-solution-repair/ and I'm afraid it's not manageable without flashing a modified kernel. Um, if it's not difficult for you, can you make a separate kernel with the fix?
[Transformer TF300T Android Development] ne0zone75:
Well..., as your request is very specific, i will contact you over PM ASAP...

Meanwhile, i am wondering what is the issue you are currently experiencing with stock CyanogenMod kernel packed into my ROM installer that is leading you to want to do so... ?! Because there is nothing about it in the web link from your above post...

Regards

Sent from my TF701T

PS : You are using a custom ROM or ASUS stock one BTW...?!
[Transformer TF300T Android Development] golokipok:
There's nothing wrong with your included kernel. I got my digitizer replaced and because of that I got an inverted x-axis (I press the left side of the screen but the right side is the one responding). I think this is the part that is needed to be changed to get it working:

Unpack sources, find file

drivers/input/touchscreen/atmel_maxtouch.c

Find lines:

if (mxt->max_y_val < 1024)
ypos >>= 2;

stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;
fingerInfo[touch_number].y=ypos;

replace them with

if (mxt->max_y_val < 1024)
ypos >>= 2;
xpos = mxt->max_x_val – xpos;
stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;
fingerInfo[touch_number].y=ypos;
[Transformer TF300T Android Development] ne0zone75:
TF300T/TF201 inverted x axis patched kernel (USE ONLY IN CASE OF INVERTED DIGITIZER)

Allright, i am slow sometimes ;) I was not aware of this kind of specific hardware issue over the Transformer series...

Let's say that you are a lucky guy... i have extra freetime today... and your patched kernel is building right now ! :good: :silly:

Regards

EDIT : you will find the 'inverted x axis patched kernel' file below and you will be able to install it by using the 'fastboot' command :

# sudo fastboot flash staging boot.img

# sudo fastboot reboot

NB : if you need any further assistance, please contact me over PM, thank you !

WARNING : ONLY FOR AOSP based ROM's
[Transformer TF300T Android Development] ne0zone75:
Current weekly will be released soon...

Good morning,

As soon as SlimROMs team will have merged current weekly freezed source code upstream, i will start to build its TF300T release... :good:

I am currently running build 5.7 on S4 mini LTE and everything is fine so far

... :D

Upcoming current weekly will be DEODEXED and featuring :

-> Android 4.4.3

-> APP2SD functionality (available from 'Settings/Apps' menu)

... and will still be compiled with 'Official Linaro GCC' v4.8/7 (ROM/kernel) and with [MENTION=5161352]JustArchi[/MENTION] v3 optimizations applied ! ;)

Dock battery status display will not be available yet

...

Of course, after having flashed upcoming build you will be able to

ODEX

your ROM by running [MENTION=4944549]MatrixDJ96[/MENTION] script...

Stay tuned !

NB : I will test [MENTION=5123642]lj50036[/MENTION] kernel (based off CyanogenMod 11.0 one) out this week in order to try to provide OOTB F2FS support in the next weekly BUT also full F2FS support in the DEV branch of my TWRP builds for TF300T, thanks to him for his work ! :good:

PS : If you do want to add F2FS to your setup please refer to [MENTION=4972193]ebildude123[/MENTION] GEASS & [MENTION=2158597]hardslog[/MENTION] GRIMLOCK threads, thank you !
[Transformer TF300T Android Development] ne0zone75:
Awaiting merging of current weekly source code upstream...

Good evening,

Just a few words to let you know that current weekly source code is not merged upstream yet... of course, i will update this post when its building process will have started ! ;)

Best regards

EDIT : Build process is completed... starting uploading ! :D
[Transformer TF300T Android Development] zen_phones:
i love LOVE this rom. im a huge fan of slim roms. just installed this today and its running great. i have a few questions.

1) everytime i switch to ART runtime, and i go back to developer options to view it, it's radio button is on dalvik again. is this normal? how do i know its running ART?

2) i tried installing this on multirom, as a 2nd rom, it installed good, but when i flashed the extreme pack kernal, it gave me a black SOD. so i ditched my other rom and installed it as the primary rom (i think it deserved that). is this known to happen? i'll take a nandroid back up before i attempt again.

3) when i cleared cache and dalvik cache when it was the 2nd rom using multirom, i also got a black SOD. has this happened to anyone? am i not suppose to do that when i've selected ART runtime (as least i think im in ART, back to question 1).

keep up the good work!
[Transformer TF300T Android Development] ne0zone75:
Well..., Hello and thank you,

For 1), 2) and 3) :

i do not think that you have successfully switched to ART in 1) for some reason

... Did you get a popup message, asking you to reboot just after selecting it in 'developer options', and if you got one and selected to reboot, has your tablet successfully rebooted after having regenerated dalvik + cache (because it is automatically cleared when selecting ART as runtime even if you choose to reboot later in the popup message...).

For 2) : No, it should not happen at all with it and AFAIK you are the first in this case BUT ART IS CLEARLY RELATED TO SODs... maybe it has also something to do with your initial dual boot setup BUT that it is just a guess...

FYI, ART is :

-> under heavy development (it is the cause of manu issues...)

-> it is maybe not properly working because of the 'JA' optimizations i am currently using to build the ROM (even if ART is patched in order to be working with those...) : so it would be really interesting if someone could confirm ART as working... thank you !

What i would do if i were in your position :

-> flash latest ROM released today and...

-> try to switch to ART again and test it out a little bit without flashing any 'Power Pack' if you are able to switch to it (anyway in 'developer options' you should see ART if you are really running it...)

-> after this and if you successfully switched to ART or not, flash 'SlimKAT Extreme Power Pack for TF300T' again while running dalvik as runtime (not ART, even if you are able to turn it ON...) to check if you are getting a black SOD again and if not reswitch to ART with 'Extreme Power Pack' already flashed (if ART is working for you)...

Greetings
[Transformer TF300T Android Development] ne0zone75:
SlimKAT RC2 for TF300T/TF201 Build 5.8 is online !

Good afternoon,

New build is now available for download from updated download links on post number 1 (Dev-Host) :victory: :good:

xda download tabs will be updated later because i have a slow Internet connection today...

UPGRADE / INSTALL instructions : you can upgrade to latest release by doing a clean install OR a dirty flash (if you are dirty flashing, DO NOT FORGET to wipe dalvik + cache, thank you !); No special instructions for a first install, just follow AOSP guidelines on post number 1 ! ;)

Enjoy SlimKAT :D

NB : Please report back if proprietary dock hardware keys are not working anymore because i have changed something in the way 'asusdec' is built..., thank you !

EDIT : IF YOU ARE FLASHING A GAPPS PACKAGE, be sure to flash a 4.4.3 one !
[Transformer TF300T Android Development] zen_phones:
as for the ART, yeah i'm not sure if it took. it did give me a pop up asking to reboot after selecting the radio button. i've had to install several times due to multirom and what not, but the first time i selected ART i got the pop up, i rebooted and it seemed to have worked, when it started up i got the "android upgrading" and then like 3 or 4 system apps (i forget which) were not compatible. then i kept getting a google music error so i just re-flashed. thats when it was the 2nd rom. when i reflashed again (while in 2nd rom position) i picked ART again and i got the pop up, and everything went smooth. i thought it had worked, but when i go to developer options > select runtime, is says "use dalvik". not sure if thats the way its suppose to be. i do it again and reboot and same thing "use dalvik" in the select runtime. maybe this is the way it should be?

also i tried flashed extreme pack (now that slimkat is primary rom) and multirom twrp said "failed". i cleared cache+dalvik before and after flashing extreme pack. does extreme pack have a user interface? how do i know its working? also, i had to flash superSU zip because i have having problems getting root. i lost it somehow, and when i flashed superSU zip, multirom twrp said "failed" but it still took, so i was thinking maybe extreme pack took. how do i know if extreme pack is working?

i'll drity flash the new release you just posted. thanks.

---------- Post added at 08:32 AM ---------- Previous post was at 08:24 AM ----------

EDIT : IF YOU ARE FLASHING A GAPPS PACKAGE, be sure to flash a 4.4.3 one ![/QUOTE]

i used the 4.4.2 minimal gapps package from slimroms site. do you think that'll cause a problem? everything seems to be ok. i dont know if the ART issue can be blamed on gapps?

edit: oooh i see its 4.4.3 is the new update. will i be ok if i dirty flash over yesterdays 4.4.2?