yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] TechSavvy2:
a

Confirmed working for newest CM9 build.

On a side note, I gotta say hats off to you motley!!!! I've never been a fan of flashing kernels on any devices. But for the prime, you just gave it life!! This should be baked into every single rom out there, lol. Now I don't have to flash twenty different things with every nightly. No flash nightly, flash gapps, flash mod1 flash mod2 flash cfq....etc etc. Now just flash nightly, gapps, motley...and profit!!

Thank you!
[Asus  Eee Pad Transformer Prime] umneycreep:
Motley! that worked! WIFI works on Gummy ROM now...Thanks, you are amazing.
[Asus  Eee Pad Transformer Prime] bri315317:
Two words.... Simply Amazing!

Excellent work Motley!
[Asus  Eee Pad Transformer Prime] dixxa:
Still no explanation ?
[Asus  Eee Pad Transformer Prime] newellj79:
91zram, which you have, is a script that needs to be ran. use script manager from the market to run it with su permissions. you can watch the script activate.
[Asus  Eee Pad Transformer Prime] rift999:
I am running EOS and the version with the extra file added for EOS and gummi. Whenever I try to pair my bluetooth headset settings force closes and I even managed to get a forced reboot after one attempt. Any idea what is going on?

Rift

Sent from my EPAD
[Asus  Eee Pad Transformer Prime] dixxa:
Lol xD

I know that but why I don't have a zram0 folder ??

When I launch the script with script manager or manually I just see the echo printing of the script.

" echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";

echo "[90ZRAM]: Is this a ZRAM kernel?";

echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";"

No folder, no disksize file, as if the script was stopping right after checking if zram0 was present or not.

I can't chgrp because my tab don't recognize the group "shell" maybe that's why but I doubt about it.

I'm using androwook rom kinda like stock.

Any constructives explanations are welcome.
[Asus  Eee Pad Transformer Prime] fordwolden:
NTFS support.

Is NTFS support decided by rom or kernel? I'm running this kernel with EOS

and can't mount my 64gb microsd (NTFS). EOS wouldn't mount it earlier but

I hoped the kernel would do the trick. Any tips and/or tricks?

Thanks
[Asus  Eee Pad Transformer Prime] berto1014:
Should I run the overclock script and zram script at boot, or are the settings already applied when I run them once?
[Asus  Eee Pad Transformer Prime] newellj79:
Sorry about that friend. I don't know to much about it. I'm running aokp and it was there as it should be. To be honest I don't know that it is making much of a difference for me.
[Asus  Eee Pad Transformer Prime] _motley:
Updated Info

Thanks for the continued testing and updates. I have updated post 803 with the latest info and zips for the alpha 3.0.3 version. I have now provided a blob-based CWM zip for stock primes so that 64GB primes can join the fun.

To answer other questions:

Which ROM are you on and do you have a 64GB prime? It may be that you flashed the anykernel zip and it really didn't really install or your flashed a rom afterwards and it overwrote the kernel. Stock kernel build in System|About tablet is build #142 and I think the generic kernel is build #143. If you have a kernel build different than that, then you aren't on the latest alpha kernel. After you flash the new kernel, you should have /sys/block/zram0 since it includes ZRAM. If you don't, you aren't on the right kernel.

This kernel expects the stock modules to be used for NTFS (see first post for details on the Tuxera modules), however it is the ROM that will provide auto mounting of the media and mount points. Maybe you can try using FAT32 and see if it works any better.

OC script has to be run on boot for generic roms. For stock-based roms, the performance modes are still in control

ZRAM has to to be run as su on boot to activate. I can be automated, but none of the roms (ramdisks) support this yet. I have updated post 803 with the most recent info.
[Asus  Eee Pad Transformer Prime] berto1014:
Thank you very much for answering my question! So far the kernel works excellent! Great work!
[Asus  Eee Pad Transformer Prime] rift999:
Is anyone else having issues with bluetooth? especially on EOS?

Sent from my EPAD
[Asus  Eee Pad Transformer Prime] newellj79:
BT audio is working great with the new kernel on aokp for me.
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
Flashed the 1.7 blob the day it dropped with zram configed via script manager. Way too many random reboots and the occasional fc using the stock browser and trying to respond to a post in another forum...used another browser and the same result....funny thing is the kernel runs like a champ doing 10 other things simultaneously and rides the net like a smooth wave, but crashes when doing a simple task like responding in a forum.

I have since down clocked to1.6 and it seems to be running fine. Any ideas? Also can somebody kindly confirm if copying the 1.6oc script in motley's post, pasting it to the oc script in etc/init.d file in place of the original and running via script manager with root and boot perms is the correct way to be running this script.
[Asus  Eee Pad Transformer Prime] 760hacker:
i am running the latest AOKP and i get SOD with this everytime close my tablet while in the dock. Anyone else or any fixes. Other than that it runs like a champ while its awake.
[Asus  Eee Pad Transformer Prime] Charsher47:
I can open and close my lid just fine with this and AOKP.
[Asus  Eee Pad Transformer Prime] jiffy1080:
I have had SOD 3-4 different times running the 3.0.0 kernel on AndroWook Prime. Also sometimes if I leave my screen on for a few minutes on the same screen it will kinda shake but I swipe to another screen or page it goes away. I've tested it on the stock kernel and on the version of your kernel bundled with AndroWook and those problems don't seem to occur. I guess it could be a combination of the kernel and AndroWook/My init.d/prop tweaks.

Montley - If you want I can send you logs if it happens again.
[Asus  Eee Pad Transformer Prime] _motley:
I don't have any headphones to test with, but I paired my Galaxy Nexus on EOS and could surf through the phone using bluetooth tether.

The SOD issues are a PITA to track down. I have had SOD on my custom kernel and on the stock kernel while troubleshooting. I can't say 100%, but it seems like I am always plugged in or docked when they occur.

For example, here is a thread where stock users are having the SOD problem. Since this kernel source is based on stock, it is not suprising that it would have some of the same gremlins. I'll do more research into what changed in .21 to see if anything sticks out.

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

If 1.6 is working OK, then it could be a voltage problem. On stock-based ROMs, make sure you alter the stock OC script for performance mode (system/etc/cpu3.sh) so you have the proper core_cap_level for the frequency/system mode you run. For custom ROMs, make sure you modify the OC script with the same (init.d script typically).

This is the biggest mistake people make when playing around with the kernel. They forget about the core_cap_level in the script. If you cap it too low, the kernel will lag and perform badly and sometime freeze up completely. The other thing to remember is that all of these chips are not created equally at the factory. One person may be able to OC all day with no problems at one core cap level/frequency, while another may find their limit somewhere else.

For 1.7 or 1.8, use 1350 (system_mode = 4 or system_mode = 5)

For 1.6, use core_cap_level = 1300 like stock (system_mode = 3)

Here is cpu3.sh with 1.7GHz

#!/bin/sh -x
#This is 1.7 Performance mode - motley kernel Cayenne
echo 4 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0

[/QUOTE]
[Asus  Eee Pad Transformer Prime] jiffy1080:
[/QUOTE]

Thanks for the tips! Yeah, I had the dock connected as well. I forget about it being connected since it is 99% of the time.
[Asus  Eee Pad Transformer Prime] boynamedstacy:
I am running the new 3.0.3 kernel OC'd to 1.7 with the Zram mod and have been fortunate to not experience these SOD's I am reading about. I love the way she runs now! Thank you very much Motley, I am so happy you are back! :D

AOKP B38
[Asus  Eee Pad Transformer Prime] silverdart:
Hope this helps someone!

0. prime 64GB

1. virtuous prime s 9.4.2.21 v1

2. motley stock full kernel and ramdisk 3.0.3

3. 90-zram (search for it) in system/etc/init.d - no script manager!

4. 91-zram did not work-doesn't mention busybox being in system/xbin so I replaced it with 90-zram, that I use with my sensation, which does mention busybox in system/xbin and it loaded zram with 120mb on each and every reboot.

5. Hope this helps someone!
[Asus  Eee Pad Transformer Prime] fordwolden:
I'm on EOS nightly 17 and use my Jabra bluetooth headset without issues!
[Asus  Eee Pad Transformer Prime] rift999:
I am running the official stable EOS and whenever I try to pair my headphones settings forcecloses or reboots the tablets. I did try a dirty reflash with no results I didn't use bluetooth headphones on the last version because they are new but I do pair them with my nexus s without problem. If no one else is having issues on any other versions I will try flashing an nightly.

Sent from my EPAD
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
[/QUOTE]

Thanks for the fast reply and help...tried the above 1.7 script (I'm assuming this new script includes the proper voltage you mentioned above...***if it does not please let me know, so I can try again with the moded voltage.....***after restoring to AOKP with the original blob file flashed and the problem persisted. Perhaps my chip is one of the few that can't handle 1.7. Few things to note: I was able to OC to 1.8 with your initial kernel release. Despite currently running with the 1.6 script and zram I am sporadically thrown off of both dolphin and stock browser from time to time. Finally, the best experience I've had with your kernel thus far has been with the oringinal 1.7 blob, with exception to the random reboots and crashes when trying to respond in forums. --- might run the original 1.7 and just leave forum posting for my PC...this would be a sucky limitation though.
[Asus  Eee Pad Transformer Prime] Tempie007:
running the 3.0.3 alpha for some days now with zram enabled ,cfq scheduler, on androwook 1.1.

played games , browsing (stock), flash video, tapatalk googlereader.

Got 1 reboot while in the youtube app .

prety stable to me
[Asus  Eee Pad Transformer Prime] CharliesTheMan:
I actually came to the thread to post almost identical information. I'm running AndroWook 1.2 now and 3.0.3 alpha with zram enabled, CFQ sceduler (although I've been testing with deadline flipping back and fourth) and the dangerous but fast sqlite patched libs, and my prime has been rock solid. I think I've had one weird freeze or reboot, last night just before I fell asleep, but it may very well have been an app I was using.

AndroWook and this Prime with Motley's 3.0.3 kernel is a BEAST. This prime is unbelievably fast, I've even converted a couple of guys that were running other roms just because of the tweaks, and once they saw the performance of this combo they completely abandoned colorful tweaks built into the rom settings being a requirement.

Thank you motley for a job well done and for the way that you offer your knowledge up to other rom developers. You are a great asset to the community my friend.
[Asus  Eee Pad Transformer Prime] fordwolden:
Lost something!

Hi.

Fantastic kernel. I just encountered an issue though. I'm on EOS and I use the hide statusbar option regularly as I use my prime alot for videos. After I flashed your kernel, whenever I try to hide statusbar I only lose the effect of the soft keys, the statusbar is still there. I then did a factory reset, wiped cache/dalvik and reflashed the rom without reflashing your kernel but issue still remain.

Any help would be much appreciated. By the way I don't have access to my data cable so I can't do a full wipe.

Thanks
[Asus  Eee Pad Transformer Prime] Tempie007:
im wondering , is this kernel flashable on androwook 1.3 and/or wil it revert some of the changes asus made on the .28 build?

whats the kernel version on .28?
[Asus  Eee Pad Transformer Prime] bedoig:
Don't know if there are major changes, but .28 source is out.

Go Motley, go!
[Asus  Eee Pad Transformer Prime] notoriouspk:
+1 alpha for .28 motley :)

Waiting alpha 3.0 for .28
[Asus  Eee Pad Transformer Prime] LNJ:
2.6.11 works fine with 1.31 rom.
[Asus  Eee Pad Transformer Prime] craigacgomez:
Till then you can use the generic anykernel version... it retains the ramdisk...
[Asus  Eee Pad Transformer Prime] rift999:
I just switched from EOS 2.00 to AOKP 38 and I have been getting occasional freezes leading to a reboot on both roms.
[Asus  Eee Pad Transformer Prime] 760hacker:
I can confirm anykernel version works fine so far on the new .28 release base specifically androwook 1.3.
[Asus  Eee Pad Transformer Prime] _motley:
Update for testers: post 803 has been updated to v3.0.4. 9.4.2.28 kernel changes have been merged;)

http://xdaforums.com/showpost.php?p=27014792&postcount=803
[Asus  Eee Pad Transformer Prime] RubenRybnik:
You da man Motley ... You're killing it lately, awesome work!
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
+ 1...def working hard...

Any chance we can get a quick blurb on the changes made?...Downloading as we speak.

Okay dirty flashed it...do I have to wipe davlik before flashing for it to take hold? The reason I ask is kernel version says "2.6.39.4-cardhu-motley-v3+" and my previous 1.6 script using init.d is still active...just want to be sure I'm actually running it, before I do "testing"
[Asus  Eee Pad Transformer Prime] _motley:
Thanks guys. As far as the changes between 3.0.3 and 3.0.4, it is just the .28 merges. You can see the merge here. There is quite a few bug fixes inlcuding the addition of the new GPS stuff.

https://github.com/motley-git/TF201-Kernel/commit/9d4e3cc4dd326660c0476513a5f3bd94796fa408
[Asus  Eee Pad Transformer Prime] _motley:
Not sure of the build #, but I will look later today...for 3.0.4, it be higher than 142 & 143 which were the build numbers for stock and generic builds respectively in 3.0.3. So if you are 144 or higher, you are on 3.0.4.
[Asus  Eee Pad Transformer Prime] CekMTL:
Testing now, with new AndroWook 1.32

Till this morning I was running with aging WSG 0.0.6

THX again Mr.LEGEND! ... wuups I mean Mr. _Motley! :)))))
[Asus  Eee Pad Transformer Prime] it2swbrown:
Build number I have after flashing is 146 to save you some time
[Asus  Eee Pad Transformer Prime] Philosoma:
Motley you are a star! From my early tests, wifi has improved dramatically, getting the same speed test as my SGS2 and also doesn't seem to be draining the battery as much. Only drama I do have is the wifi icon disappears after Tasker turns the wifi off and on. Had that on 3.0.3 but is very minor.
[Asus  Eee Pad Transformer Prime] master1988:
Hey motley,

Have some problems with newest alpha 3.0.4.

If i choose 3rd cpu mode (normal mode) i get reboot. Then i looked in skrip and voltage for cpu3 was on 1350 what i think should be enough. After that i looked for voltages in setcpu and it says on 1.7 ghz i have set only 1300mv. But there i only can undervolt?!

So which of the showed voltages are the right ones and how can i solve my problem?

Thanks in advance

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Asus  Eee Pad Transformer Prime] CekMTL:
Maybe cpu5.sh is the file being activated instead of cpu3.sh ?
[Asus  Eee Pad Transformer Prime] MrSimmonsSr:
So to run this 3.0.4 kernel with the latest AOKP (b38) I should just wipe and flash AOKP, flash gapps and then flash your above linked Motley AOKP anykernel zip after that?

Do I have the order correct? Sorry for the newbie questions... Wanted to give this a try as I would like to test the wifi fixes and also I enjoyed running AOKP. I'm on AndroWookie at the moment but miss a few of the AOKP features..

Thanks for any input. Would hate to screw myself up here..
[Asus  Eee Pad Transformer Prime] master1988:
cpu5.sh is also 1.7 mode with 1350mv for me.

Only script in system/etc with 1300mv is cpu4.sh

Can someone post a Screenshot from SetCPU with voltages.

I think something went wrong for me...

Here is mine:

https://www.dropbox.com/s/wnlyeeu34bee98n/Screenshot_2012-06-15-15-19-32.jpg

https://www.dropbox.com/s/g8w9hplrg2nx07w/Screenshot_2012-06-15-15-19-40.jpg
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
Yes, being that you're coming from another rom, you have to do a full wipe...davlik, cache and system...if you're on twrp install b38...some are having minor issues with b39 and I'm personally not sure if b39 can run with motley...any way install b38 and the latest gapps from goo and boot up...let it settle and go for the motley install. Some might suggest to install all while in recovery, but I personally like to see that my device will boot with a new rom and them with a new kernel....enjoy - Thing is so smooth with motley's kernel.
[Asus  Eee Pad Transformer Prime] berto1014:
Any chance Deep Sleep will be added into the kernel?
[Asus  Eee Pad Transformer Prime] Charsher47:
I'm deep sleeping just fine on 3.0.4 and aokp...
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
+1... Me too...Like REM type deep sleep...LOL

What ROM are you running?
[Asus  Eee Pad Transformer Prime] rift999:
I am on B38 with no deep sleep
[Asus  Eee Pad Transformer Prime] ThunderRootedDragon:
Weird...I'd suggest you guys reflash 38 and gapps...boot to see if you get deep sleep. If you do, flash motely and see if you get deep sleep...if you don't, I'd suggest a full wipe and flash of b38 and then of motley to check all ends.
[Asus  Eee Pad Transformer Prime] cragains:
I flashed the alpha 3.0.3, or whatever the newest kernel is, and suddenly my 23' monitor will not see my prime.

I had an HDMI to DVI to connect my PC to it, I would reach around the back, pull out the HDMI, then insert the HDMI connected to the prime.....no problems

When I brought the monitor home, now it wont see the prime at all. Tried switching inputs on the monitor.

I flashed back to CM9 with latest nightly, shouldn't something pop up when it is connected to external monitor, cause it doesn't.

Any ideas
[Asus  Eee Pad Transformer Prime] Charsher47:
kernel's working pretty well for me, used it all day.
[Asus  Eee Pad Transformer Prime] _motley:
Hi guys, is anyone having issues with connecting to your PC via USB cable (direct or via dock)? Just curious since the AndroWook ROM creator thinks we may have an issue. I can't duplicate the issue on rooted .28 stock with kernel 3.0.4 (build 146). I can connect to my wifes Windows 7 64-bit as a media device and browse files (only tried without dock so far) and I can do my ADB work using my Linux dev box.

The kernel supports deep sleep just like stock kernel does, with a few tweaks here and there that are different. If you are on a non-stock rom, make sure you init.d script contains the script values from post 83 (in my example, the script filename is 51overclock, on AOKP it is called cpu_overclock)

http://xdaforums.com/showpost.php?p=27014792&postcount=803

I have found that if you don't use the last line on some generic builds, it will not deep sleep. no_lp means "no low power" mode I believe. I found that it gets set to N in the stock ROM so I set it on generic ROMs to make sure they sleep. I verified this change by turning the screen on and off on my generic AOSP 4.0.4 ROM.

echo N > /sys/module/cpu_tegra3/parameters/no_lp

Those voltages sound like the stock values, so that should be fine. I am not sure what the problem is. Which ROM are you on? Maybe try 1.6GHz and a 1300 core_cap_level to see if it is stable, or whether something strage is happening when you try to execute cpu3.sh from the performance icon. The core cap voltage is different than the voltage for the 1.7 frequency. One is in the dvfs table and the other is a cap voltage level. I am not even 100% sure if it is operational when core_cap_state is 0.

Edit these two lines to clock down to 1.6GHz to give it a try.

echo 3 > /sys/module/cpu_tegra/parameters/system_mode
echo 1300 > /sys/kernel/tegra_cap/core_cap_level

I have a HDMI cable on the way so I can test HDMI-out...I just ordered it from Amazon :) I am not sure which ROMs support HDMI-out properly besides stock. Try switching the input mode on your monitor to HDMI if you haven't tried that. Also make sure you only plug in one digital video cable (DVI or HDMI) at a time, i.e. don't leave the DVI adapter for the PC in too while you connect the prime.
[Asus  Eee Pad Transformer Prime] berto1014:
Ok thanks for the headsup on the deep sleep. I was using 3.0.3 and it definitely wasn't activating (checked with cpu spy). I will flash the latest version and be sure to activate the scripts.
[Asus  Eee Pad Transformer Prime] master1988:
Hey tried it since yesterday now.

I went back on 1.6Ghz and still can't finish Antutu without getting a reboot.

Then i tried motley_stock_full_kernel_and_ramdisk_3.0.4.zip instead the one which comes with AndroWooks v.1.33 (should be z_motley_anykernel_stock_and_AOKP_3.0.4.zip).

Also no go on 1.7 but on 1.6 the Antutu Benchmark run until Testing CPU float performance and then it rebooted or close the App.

So i can't run 1.6 , 1.7 and 1.8...

Will test now downward until i find a stable one.

But can't understand why i can't run faster because before i flashed Wookies Rom and your Kernel i ran 1.6 on stock rom with ezoverclock app without any problems.

Is there a way to controll the actual voltages (not the cap_limit)?!

Thanks in advance
[Asus  Eee Pad Transformer Prime] cragains:
As you said, I tried all your recommendations to no avail. I even hooked up my laptop with a VGA, powered it up, working. Then pluged in the hdmi, switched input sources, still nothing.

I just don't understand how something just stops working suddenly.

Side note, can I flash Motleys latest kernel with AOKP milestone, and the may 29th nightly?
[Asus  Eee Pad Transformer Prime] cragains:
Well, turns out one of the pins in the cable was bent inwards, far right bottom....

Now I feel small for wasting posting space. Gonna order new cable
[Asus  Eee Pad Transformer Prime] MrSimmonsSr:
Running this with AOKP and have had two reboots in the last 24 hours.. Just wanted everyone to know.

Thanks for all you do, Motley! Will try the next build and see if it is more stable. The wifi signal on this kernel does seem to be stronger so I'll stick with it for a while and see if I can tell what is triggering the reboot.
[Asus  Eee Pad Transformer Prime] notoriouspk:
wifi killing battery

i am on .28 is this normal for wifi to eat all my battery in 24 hours ?
[Asus  Eee Pad Transformer Prime] demandarin:
check pm asap, Motley
[Asus  Eee Pad Transformer Prime] cyiam40:
Just wanted to post this in case it helps someone. I installed the Motley 3.04b kernel from the Androwook thread and it's running great. I am running the latest Virtuous Prime rom. I ran all of the benchmarks with good improvement at 1.7ghz. I am checking my games now and will report back when completed.
[Asus  Eee Pad Transformer Prime] cyiam40:
Nova 3, Max Payne are running great at 1.7ghz.