[Kernel][For TF300T][F2FS+RECOVERY][4.4.x] GEASS [#7][03/28][LINARO4.8.3]

[ebildude123]

Hey guys going to have some good stuff to post soon
built twrp and kernel working with f2fs.
running F2FS on data right now

 

[boldnuts]

Hey guys going to have some good stuff to post soon
built twrp and kernel working with f2fs.
running F2FS on data right now

look forward to trying this out, your kernel runs great on my TF201 with the Crombi KK rom

Sent from my TF300T using XDA Premium HD app

 

[ebildude123]

http://forum.xda-developers.com/showpost.php?p=49909410&postcount=2

 

[Artic89]

Recovery update is not needed right?just flash over it as usual?

 

[ebildude123]

Recovery update is not needed right?just flash over it as usual?

If you don't plan on using f2fs there is no need to update, 6a is for f2fs.
Thanks :highfive:

 

[RagingHarry]

Just installed it on my TF300TG.
Needed a reinstall of Crombi-kk to get wifi to work.
But at first run feels very fast and art cache is rebuiding super fast

Beamed into tha netzz by a jfltexx @ AOSP KVT49L

 

[ebildude123]

Just installed it on my TF300TG.
Needed a reinstall of Crombi-kk to get wifi to work.
But at first run feels very fast and art cache is rebuiding super fast

Beamed into tha netzz by a jfltexx @ AOSP KVT49L

If you are coming from _that kernel on CROMBI-kk please flash the stock CM11 kernel from CROMBI-kk before installing GEASS.

If you reflashed crombi-kk after installing the kernel then the kernel is not installed anymore; also I do not have a TG so i cannot guarantee support for it. thx

 

[RagingHarry]

Well wiped the whole device. Reinstalled it with crombi cm11 kernel to start full fresh, now have wifi from start, and rebooted to activate art, everything fine sofar.
Not expecting 3G to work cause thats also the case on crombi stock

UpdateMode ....
Ok ofcourse installed Geass 6a kernel after crombi and geapps again, and the grep command showed all is working in termunal app



Beamed into tha netzz by a jfltexx @ AOSP KVT49L

 

[boldnuts]

Running f2fs file system on my tf201 with the crombi kk rom, very smooth and quick , thank you for this great kernel.
only issue seems to be Bluetooth not turning on

Sent from my TF300T using XDA Premium HD app

 

[ebildude123]

Running f2fs file system on my tf201 with the crombi kk rom, very smooth and quick , thank you for this great kernel.
only issue seems to be Bluetooth not turning on

Sent from my TF300T using XDA Premium HD app

Do you know if the tf201 has the same BT driver as the tf300?

Sent from my TF300T on CM11 using Tapatalk 4

 

[Smackeroni]

Hi,

I flashed the f2fs kernel Yesterday. It worked really well. But I installed an OpenDelta update of Omni Rom without copying the Kernel to the FlashAfterUpdate Folder. But i still have it on my ext. SD-Card. The problem is: The modded recovery doesnt work with the SD Card. How can i "unbrick" it?

Thanks in advance!

 

[tjk639]

This is so cool! Can't wait to try this on my TF300.

Sent from my SCH-I545 using Tapatalk

 

[ebildude123]

Hi,

I flashed the f2fs kernel Yesterday. It worked really well. But I installed an OpenDelta update of Omni Rom without copying the Kernel to the FlashAfterUpdate Folder. But i still have it on my ext. SD-Card. The problem is: The modded recovery doesnt work with the SD Card. How can i "unbrick" it?

Thanks in advance!

That's odd since my microsd worked.
But you can install the kernel using adb sideload in twrp. I can't post too much info now since I'm on mobile but a quick Google search should help thanks

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[ebildude123]

#7 will come Friday or Saturday. If you want me to add something before then, post it

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[gargash]

I'm using you PAC kernel on my tf201 w/ kd8bny PAC 4.4, and I'm getting screen locks on sleep, its still active as I hear Facebook chimes and gv tones. Something to look at, but thanks for the hard work. I know its not said often enough.

Sent from my TF201 using Tapatalk

 

[ebildude123]

I'm using you PAC kernel on my tf201 w/ kd8bny PAC 4.4, and I'm getting screen locks on sleep, its still active as I hear Facebook chimes and gv tones. Something to look at, but thanks for the hard work. I know its not said often enough.

Sent from my TF201 using Tapatalk

If you can get a logcat & last kmsg and tell me your settings it would help. Personally I cannot test on a 201 so thanks

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[gargash]

Here is all of them when I narrow to kernel
03-25 16:31:41.125 E/ActivityManager(639): 62% 15630/com.android.chrome:sandboxed_process3: 53% user + 8.7% kernel / faults: 12533 minor 12 major
03-25 16:31:41.125 E/ActivityManager(639): 35% 13563/com.android.chrome: 23% user + 12% kernel / faults: 37890 minor 2 major
03-25 16:31:41.125 E/ActivityManager(639): 19% 639/system_server: 16% user + 3.4% kernel / faults: 1268 minor 6 major
03-25 16:31:41.125 E/ActivityManager(639): 12% 140/surfaceflinger: 5.8% user + 6.5% kernel / faults: 50 minor 25 major
03-25 16:31:41.125 E/ActivityManager(639): 11% 1367/com.android.systemui: 8.3% user + 3% kernel / faults: 363 minor
03-25 16:31:41.125 E/ActivityManager(639): 8.9% 137/netd: 7.9% user + 0.9% kernel / faults: 110 minor
03-25 16:31:41.125 E/ActivityManager(639): 2.2% 9405/com.android.vending: 1.9% user + 0.3% kernel / faults: 501 minor
03-25 16:31:41.125 E/ActivityManager(639): 0% 139/debuggerd: 0% user + 0% kernel / faults: 2738 minor 49 major
03-25 16:31:41.125 E/ActivityManager(639): 5.8% 104/mmcqd/0: 0% user + 5.8% kernel
03-25 16:31:41.125 E/ActivityManager(639): 2% 164/dhd_dpc: 0% user + 2% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.7% 14181/kworker/0:0: 0% user + 1.7% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.2% 40/kswapd0: 0% user + 0.2% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.5% 10072/com.nolanlawson.logcat: 0.4% user + 0.1% kernel / faults: 1 minor
03-25 16:31:41.125 E/ActivityManager(639): 0.8% 15569/com.facebook.katana: 0.4% user + 0.4% kernel / faults: 265 minor
03-25 16:31:41.125 E/ActivityManager(639): 0.7% 15228/irq/214-host_sp: 0% user + 0.7% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.2% 1503/com.android.phone: 0% user + 0.1% kernel / faults: 208 minor
03-25 16:31:41.125 E/ActivityManager(639): 0.6% 15227/irq/210-host_sp: 0% user + 0.6% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 1527/org.omnirom.omniswitch: 0% user + 0% kernel / faults: 207 minor
03-25 16:31:41.125 E/ActivityManager(639): 0.4% 14902/kworker/u:2: 0% user + 0.4% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.3% 11/kworker/1:0: 0% user + 0.3% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 1516/com.tmobile.thememanager: 0% user + 0% kernel / faults: 207 minor
03-25 16:31:41.125 E/ActivityManager(639): 0% 1536/com.bel.android.dspmanager: 0% user + 0% kernel / faults: 221 minor 1 major
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 10109/daemonsu:10432: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 15079/kworker/0:1H: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 12/kworker/1:0H: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 9057/kworker/3:2: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 10209/logcat: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.2% 14769/kworker/u:0: 0% user + 0.2% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 15230/irq/218-host_sp: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 15469/android.process.media: 0% user + 0% kernel / faults: 9 minor
03-25 16:31:41.125 E/ActivityManager(639): 0% 28/kworker/2:1: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 114/irq/77-tegra_ac: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 126/flush-179:0: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 127/jbd2/mmcblk0p8-: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 163/dhd_watchdog: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 3136/kworker/2:3: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 5213/daemonsu:10434: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 10203/su: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 10852/su: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.1% 10859/logcat: 0% user + 0.1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0% 13755/su: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15672/migration/1: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15673/ksoftirqd/1: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15675/watchdog/1: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15679/migration/3: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15680/ksoftirqd/3: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): +0% 15681/watchdog/3: 0% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 41% TOTAL: 18% user + 7.9% kernel + 14% iowait + 0.1% softirq
03-25 16:31:41.125 E/ActivityManager(639): 7.4% 639/system_server: 7.4% user + 0% kernel / faults: 1 minor
03-25 16:31:41.125 E/ActivityManager(639): 5.5% 656/ActivityManager: 5.5% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.8% 660/android.ui: 1.8% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 5.5% 140/surfaceflinger: 0% user + 5.5% kernel
03-25 16:31:41.125 E/ActivityManager(639): 3.7% 140/surfaceflinger: 0% user + 3.7% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.8% 444/hwc_eventmon: 0% user + 1.8% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.8% 466/EventThread: 1.8% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 3.7% 13563/com.android.chrome: 3.7% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 3.7% 13563/.android.chrome: 3.7% user + 0% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.8% 1367/com.android.systemui: 0% user + 1.8% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1.8% 1367/ndroid.systemui: 0% user + 1.8% kernel
03-25 16:31:41.125 E/ActivityManager(639): 0.9% 9057/kworker/3:2: 0% user + 0.9% kernel
03-25 16:31:41.125 E/ActivityManager(639): 1% 14181/kworker/0:0: 0% user + 1% kernel
03-25 16:31:41.125 E/ActivityManager(639): 74% TOTAL: 2.9% user + 2.9% kernel + 68% iowait
03-25 16:33:13.715 E/ActivityManager(639): 16% 639/system_server: 11% user + 4.8% kernel / faults: 1589 minor 11 major
03-25 16:33:13.715 E/ActivityManager(639): 10% 15785/com.android.chrome: 8% user + 2.9% kernel / faults: 3027 minor 4 major
03-25 16:33:13.715 E/ActivityManager(639): 10% 104/mmcqd/0: 0% user + 10% kernel
03-25 16:33:13.715 E/ActivityManager(639): 9.2% 137/netd: 8.2% user + 1% kernel / faults: 127 minor
03-25 16:33:13.715 E/ActivityManager(639): 8.2% 15923/com.android.chrome:sandboxed_process1: 6.2% user + 1.9% kernel / faults: 2921 minor 73 major
03-25 16:33:13.715 E/ActivityManager(639): 5% 140/surfaceflinger: 2.5% user + 2.5% kernel / faults: 3 minor
03-25 16:33:13.715 E/ActivityManager(639): 0.7% 139/debuggerd: 0.3% user + 0.3% kernel / faults: 2522 minor 69 major
03-25 16:33:13.715 E/ActivityManager(639): 2.9% 15808/com.android.chrome:sandboxed_process0: 1.9% user + 0.9% kernel / faults: 315 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 2.4% 141/zygote: 0.4% user + 1.9% kernel / faults: 561 minor
03-25 16:33:13.715 E/ActivityManager(639): 2.3% 1367/com.android.systemui: 1.5% user + 0.8% kernel / faults: 190 minor
03-25 16:33:13.715 E/ActivityManager(639): 2.1% 1527/org.omnirom.omniswitch: 1.2% user + 0.9% kernel / faults: 1016 minor 27 major
03-25 16:33:13.715 E/ActivityManager(639): 1.9% 40/kswapd0: 0% user + 1.9% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.9% 10072/com.nolanlawson.logcat: 0.8% user + 0% kernel / faults: 184 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 0.3% 15893/com.google.android.partnersetup: 0.2% user + 0% kernel / faults: 673 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 0.6% 14181/kworker/0:0: 0% user + 0.6% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.6% 15227/irq/210-host_sp: 0% user + 0.6% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.4% 15987/com.svox.pico: 0.3% user + 0.1% kernel / faults: 1582 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 0.4% 164/dhd_dpc: 0% user + 0.4% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.1% 1503/com.android.phone: 0% user + 0% kernel / faults: 211 minor
03-25 16:33:13.715 E/ActivityManager(639): 0.4% 14902/kworker/u:2: 0% user + 0.4% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.3% 12936/kworker/u:3: 0% user + 0.3% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.3% 15228/irq/214-host_sp: 0% user + 0.3% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 29/kworker/1:1: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 1516/com.tmobile.thememanager: 0% user + 0% kernel / faults: 458 minor 2 major
03-25 16:33:13.715 E/ActivityManager(639): 0.2% 6912/com.google.android.gms: 0.1% user + 0% kernel / faults: 35 minor
03-25 16:33:13.715 E/ActivityManager(639): 0% 10209/logcat: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.2% 11179/com.google.process.gapps: 0% user + 0.1% kernel / faults: 12 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 0.1% 27/kworker/3:1: 0% user + 0.1% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 1536/com.bel.android.dspmanager: 0% user + 0% kernel / faults: 255 minor
03-25 16:33:13.715 E/ActivityManager(639): 0.1% 10109/daemonsu:10432: 0% user + 0.1% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 10859/logcat: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0.1% 15230/irq/218-host_sp: 0% user + 0.1% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 22/kworker/3:0H: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 109/kworker/1:1H: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 114/irq/77-tegra_ac: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 126/flush-179:0: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 127/jbd2/mmcblk0p8-: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 163/dhd_watchdog: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 200/adbd: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 1253/wpa_supplicant: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 5213/daemonsu:10434: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 10203/su: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 0% 12527/com.google.android.googlequicksearchbox:search: 0% user + 0% kernel / faults: 193 minor 3 major
03-25 16:33:13.715 E/ActivityManager(639): +0% 16000/com.android.settings: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16036/migration/1: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16037/ksoftirqd/1: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16038/watchdog/1: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16043/migration/3: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16044/ksoftirqd/3: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16045/com.android.voicedialer: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16058/kworker/u:1: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16059/watchdog/3: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16063/com.android.gallery3d: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16078/org.cyanogenmod.voiceplus: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16091/migration/2: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16092/ksoftirqd/2: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16095/watchdog/2: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): +0% 16099/eu.chainfire.supersu: 0% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 63% TOTAL: 12% user + 9.2% kernel + 41% iowait + 0.1% softirq
03-25 16:33:13.715 E/ActivityManager(639): 26% 104/mmcqd/0: 0% user + 26% kernel
03-25 16:33:13.715 E/ActivityManager(639): 17% 639/system_server: 3.5% user + 14% kernel / faults: 29 minor 1 major
03-25 16:33:13.715 E/ActivityManager(639): 10% 656/ActivityManager: 1.7% user + 8.7% kernel
03-25 16:33:13.715 E/ActivityManager(639): 1.7% 646/Compiler: 0% user + 1.7% kernel
03-25 16:33:13.715 E/ActivityManager(639): 1.7% 660/android.ui: 1.7% user + 0% kernel
03-25 16:33:13.715 E/ActivityManager(639): 1.7% 1652/Binder_B: 0% user + 1.7% kernel
03-25 17:48:50.116 I/ViPER4Android(22833): Convolver kernel =
03-25 17:48:50.116 I/ViPER4Android(22833): Clear convolver kernel
03-25 17:48:50.116 I/ViPER4Android_v2(143): Convolver: [PrepareKernelBuffer] ID = 0, Channels = 0
03-25 17:48:50.116 I/ViPER4Android_v2(143): Convolver: [PrepareKernelBuffer] Empty kernel.
03-25 17:49:05.156 I/ViPER4Android(22833): Convolver kernel =
03-25 17:49:05.156 I/ViPER4Android(22833): Clear convolver kernel
03-25 17:49:05.156 I/ViPER4Android_v2(143): Convolver: [PrepareKernelBuffer] ID = 0, Channels = 0
03-25 17:49:05.156 I/ViPER4Android_v2(143): Convolver: [PrepareKernelBuffer] Empty kernel.

My settings are all default aside from changing the governor to different settings is smartassx, or interactivex. I don't have a pro key for trickster yet so I don't believe its an issue on boot, also it only happens about once a day, which when I ran real tf201 Roms I had more issues. I would have to say though I'm very impressed as I thought it would be less stable than than designer prime roms since its not really supported hardware as I had random restarts frequently, I generally use a2sd as I have a 64gb sandisk msd. By as of right now aside from having to hard reset once a day its a huge improvement. Also since I'm just running PAC w/ your kernel it even has less stutter when installing and working with other apps. I do also have art running. That's all I can think would be pertinent to debugging ATM. Let me know if you need anything else.

Sent from my TF300T using Tapatalk

 

[ch3mn3y]

I would like to use f2fs on my tab, but I have a question(s):
- wipe /data wont wipe /data/media, so should I wipe it myself? I think yes
- after makeing backup of whole rom or only /data using yours f2fs twrp can I restore it after flashing twrp, kernel and all necessary reboots? While restoring it should format /data to f2fs again and than restore apps, right?

 

[ebildude123]

I would like to use f2fs on my tab, but I have a question(s):
- wipe /data wont wipe /data/media, so should I wipe it myself? I think yes
- after makeing backup of whole rom or only /data using yours f2fs twrp can I restore it after flashing twrp, kernel and all necessary reboots? While restoring it should format /data to f2fs again and than restore apps, right?

You have to use the Format Data button in my twrp build as instructed not wipe. Else the partition won't be formatted to f2fs.
Backups are fully functional. But remember if you backup your /data when using ext4 it will restore as ext4 and if you backup when using f2fs it will restore as f2fs file system. So if you restore an old ext4 /data it when using f2fs it will become an ext4 partition again. Just use titanium backup is what I would recommend.

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[gargash]

The BT driver for the tf201 has to be different as BT will not turn on. Also I was using ART and it appears going to Dalvik has ceased screen issues, any other constructive feedback I can help with just let me know.

Sent from my TF300T using Tapatalk