yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] SOTK:
I couldn't get the motley kernel to work with CM10 and I know others have reported the same. I tried the generic/any kernel one and no dice. I haven't tried the light one but don't intend to. I'm hoping motley will eventually come out with a newer version(s) which will work and be more stable with JB based Roms and JB AOSP (CM) Roms. :)
[Asus  Eee Pad Transformer Prime] KingDavid63:
havent checked in here in awhile because i found the perfect kernel for this beast so far, the lite versions are freaking epic man, killing every kernel ive flashed so far, stock and sorry to say your other kernels... thanks for what you do bro great job, im content until stock jb....

Sent from my Asus TF201 Prime Virtuous Loaded Quad Core +1 Beast!
[Asus  Eee Pad Transformer Prime] seeknom:
motley - love your kernels!!!... running them on my Prime and my N7.

Speaking of the N7, I was reading the forums, and saw you mention that you have a Linaro kernel for Prime in progress... how is it performing?

Thanks!
[Asus  Eee Pad Transformer Prime] shaolin95:
Is v3.0.5 capable of 1.8Ghz?

I am trying it using the scripts but I cannot get it to work so far.

I cannot resit testing OCing :D
[Asus  Eee Pad Transformer Prime] YoMarK:
Noticed today that Asus has released the kernel source from the JellyBean update: http://support.asus.com/Download.aspx?SLanguage=nl-nl&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16 .

It's dated 02-10-2012, and i've mirrored it here: http://www.lavrijsen.org/kernel_V10_4_2_15.zip

So Motley, do you still have some love for the Prime? :)
[Asus  Eee Pad Transformer Prime] meldrak:
and what about new F2FS file system? it could be a solution to the poor I/O performence ....

http://xdaforums.com/showthread.php?p=32525813#post32525813

http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg318439.html
[Asus  Eee Pad Transformer Prime] Bastaerd:
Random writes will still be crap ;) more a bandaid fix imo.
[Asus  Eee Pad Transformer Prime] meldrak:
if I read correctly first benchmark on a galaxy nexus are very impressive !!!

seq. read, seq. write, rand. read, rand. write

- ext4: 29.88 12.83 11.43 0.56

- f2fs: 29.70 13.34 10.79 12.82
[Asus  Eee Pad Transformer Prime] winni91:
Is it right that i can NOT use this Kernel with a AOKP Jelly Bean Rom and Jelly Bean Bootloader?
[Asus  Eee Pad Transformer Prime] Bastaerd:
Yes
[Asus  Eee Pad Transformer Prime] _motley:
alpha released for testing with 4.2.2 ROMs

Hi guys, it's been awhile, but I wanted to stop by and share the kernel I built for the 4.2.2 ROMs I see popping up. This is an alpha, so please read the OP carefully for details. Once I know it works, we can see what else we can do with it.

Let me know know how it goes and which ROMs it works with (or doesn't work with).
[Asus  Eee Pad Transformer Prime] Voyager2k:
Flashed it. No problems so far. You have no idea how long I've been waiting for this!
[Asus  Eee Pad Transformer Prime] dcrjay:
Wow. You just gave me the reason to upgrade. Very very thankful.
[Asus  Eee Pad Transformer Prime] b.huss2:
Ah yea! That's what I'm talkin about! Thank you sir for your contribution.
[Asus  Eee Pad Transformer Prime] dcrjay:
Can't get full speed with baked beans or change mod 10.1 , stuck at 1.4ghz.
[Asus  Eee Pad Transformer Prime] b.huss2:
No problem here on blackbean running 1.6 max. :good:
[Asus  Eee Pad Transformer Prime] dcrjay:
Im showing only 1.4ghz in cpu spy. 1.7ghz max not being used. How do you turn on performace mode or max speed?
[Asus  Eee Pad Transformer Prime] Voyager2k:
Re: [KERNEL][GPL]2013-02-27 b24 motley kernel for the Prime (4.2.2 alpha)

Works for me using ParanoidAndroid 3.10. What ROM are you using?
[Asus  Eee Pad Transformer Prime] dcrjay:
Installed trickstar, works perfect now. Thank you very much.
[Asus  Eee Pad Transformer Prime] _motley:
Glad to hear it is working for you guys, thanks for testing and reporting back.

Voyager2k and b.huss2, thanks for your work on the 4.2.2 ROMs. I was considering building a vanilla AOSP 4.2.2 to see how it works on the prime, but I am not sure I will have the time and was glad to see these ROMs popping up!

P.S. b.huss2, ran out of thanks for the day...I'll be back to hit you up later!
[Asus  Eee Pad Transformer Prime] b.huss2:
I'm figuring out (as you are well aware) that this stuff is very time consuming. It's exciting that you have re-surfaced with this custom kernel. I have been wanting to learn how to customize kernels for us but now the pressure is off. :)

Would it be OK to build your kernel into my ROMs? (With proper credits of course)
[Asus  Eee Pad Transformer Prime] dj-bilbo:
anyone tried it on CM10.1 rom yet?
[Asus  Eee Pad Transformer Prime] _motley:
LOL, thanks. Absolutely, you can use the kernel. All I ask is that devs link back to this thread so users can get info and updates.

Thx
[Asus  Eee Pad Transformer Prime] pappschlumpf:
AW: [KERNEL][GPL]2013-02-27 b24 motley kernel for the Prime (4.2.2 alpha)

Flashed it, my prime only shows the asus logo, no twrp, no recovery, fastboot selection screen with volume down, any hints?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Asus  Eee Pad Transformer Prime] metcag:
Same here, I just flashed and now I have just ASUS boot logo and I can't access anything. Any Ideas?
[Asus  Eee Pad Transformer Prime] b.huss2:
What ROM?

What Bootloader?

guys you can't just pop in and say "I flashed, no boot, help please" and expect any real help. Always be specific.
[Asus  Eee Pad Transformer Prime] huskerkate:
i was wondering the same thing, and then just decided, "what the hell." flashed it, and seems to be running pretty well. thus far, seems a little smoother and snappier than stock cm10.1.

thanks motley!!

the first things that pop to mind:

1. corrupt download

2. make sure you are on a rom w/ the JB bootloader

3. make sure have latest version of TWRP for JB bootloader (which you can't install from goo.im app, and have to install from website. i used the terminal emulator method (even tho it's not recommended) just cuz it was easiest - it worked fine).
[Asus  Eee Pad Transformer Prime] metcag:
I was on CM 10.1 unofficial with JB boot loader. I can enter the mode with the volume up and it keeps the screen of I don't really remember the name of it I thing it is ADF or APX or something like that. how can I recover my tablet on that mode?
[Asus  Eee Pad Transformer Prime] lortay78:
I am in the same boat. Was running Jellybeer with the Jellybean bootloader. I do have my NVflash backups, but I have never had to use them. My problem is I can't even shut the thing off to figure it out. It will only reboot to blank screen if I hold volume up, or it reboots to the Asus logo. Won't shut down.
[Asus  Eee Pad Transformer Prime] b.huss2:
Can you guys tell is your exact steps when you flashed the kernel. For example I just flashed the kernel package then wiped cache and rebooted.

I do know it runs on paranoid android which is aosp based. I'm running it on black bean, also mostly aosp but has some cm bits. It would be helpful for anyone who has this running on a cm based rom to leave a report.
[Asus  Eee Pad Transformer Prime] lortay78:
Well, I hit the download link in the post and after it downloaded it it asked me to use some kind of .zip flash process I'd never seen before. (This is where I should have stopped and done some reading. I'm used to just downloading and using recovery.)

I still don't know what that was. I assumed it was something you use to flash your kernels kind of like Aroma installer. edit: this was part of Jellybeer rom. (My ignorance resulting in paperweight)

It detected my twrp installation and asked if I wanted that to be my default. I hit flash, and when I looked at my tablet it was in recovery.

I wiped dalvik and cache, found the kernel in my downloads directory, flashed, fixed permissions, and rebooted.

I no longer see the Device unlocked language at the top left of my screen that I believe has been there since I did my NVflash. (I haven't paid much attention for awhile.)
[Asus  Eee Pad Transformer Prime] b.huss2:
Your running jelly beer, and that was the zip flasher app that they include but I've never used it.

I'm wondering, Do you have adb access?
[Asus  Eee Pad Transformer Prime] tech247:
I have it running in on CM 10.1 the 2/22 build I flashed it in recovery and use trickster to oc but CM's built in oc seetings see it too! Blazing fast on this Kernel thank YOU!
[Asus  Eee Pad Transformer Prime] lortay78:
I have no adb access. I am trying to see if I can set up wheelie on my linux install. I can't believe I had some zip flasher thing included with the rom I didn't know about. This is why I can't have a job. I need to stay current!

PS, I'd appreciate any help. DM me so I don't clog up your thread. This was my error, not this kernel. I'm sure of it. I love your work I have had a lot of scares over the years, but I think this one might be my first real brick.

EDIT: Kind of looks like I'm done. I can't get APX or ADB to work. I did upgrade to a new machine and Win8, but I think I have the universal naked drivers, and I can get adb on other devices. My Linux install doesn't want to recognize any androids plugged into it for some reason, so my only hope is to find another linux machine and follow this: http://xdaforums.com/showthread.php?t=1927818 if I can. I'd be more than happy to hear any suggestions. I don't know if it is charging, so I feel a bit of a time crunch.
[Asus  Eee Pad Transformer Prime] pappschlumpf:
AW: [KERNEL][GPL]2013-02-27 b24 motley kernel for the Prime (4.2.2 alpha)

I was running paranoid 3.10 latest build. Flashed the kernel using twrp. The prime is recognized as APX device after holding power volume up, that's all. But no adp, nothing, it seems to be dead!

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Asus  Eee Pad Transformer Prime] Bastaerd:
Re: [KERNEL][GPL]2013-02-27 b24 motley kernel for the Prime (4.2.2 alpha)

Just bit the bullet and flashed b24 on stock 10.4.2.18 on a 32GB Prime.

Booted up fine, using the tablet feels more snappy then stock. Could pair my BT headset. WiFi doesn't work, stuck on turning on.
[Asus  Eee Pad Transformer Prime] _motley:
Yeah, probably won't work on stock because of the WiFi drivers setup in the ROM and kernel doesn't match (WEXT vs wext vs nl80211) . This is like the old generic builds that I used to put out for CM and others. I could probably do a stock build as well this weekend.

Very sorry to hear you guys are having issues. Are you trying to use this on a 64GB Prime by chance? We know from past experience that the AnyKernel method won't work for some reason with a 64GB model, so that is why I put up the disclaimer in the OP. However, I don't recall it being that hard to recover from if you can still get to fastboot to flash the boot.img from your previous ROM (fastboot boot boot.img). If you have NVFlash backups, I would think you would be able to recover somehow or another. I am not a recovery expert, but there are some threads on here that are dedicated to it and some are very good at it. The USB drivers are finicky, so I would try another PC with the correct drivers (Win 7 preferably) before giving up. I've seen several times where one PC will work and another one won't due to some scrambled USB driver mess. I will check in later after work to see if there is anything else I can suggest.
[Asus  Eee Pad Transformer Prime] Bastaerd:
Re: [KERNEL][GPL]2013-02-27 b24 motley kernel for the Prime (4.2.2 alpha)

I vaguely remember reading something about it in this thread. Thank you for clarifying. Would be awesome if you did :)
[Asus  Eee Pad Transformer Prime] seeknom:
Yeah, I tried flashing it over Androwook Hairy Bean, and same thing - couldn't enable wifi.
[Asus  Eee Pad Transformer Prime] dcrjay:
Androwook is 4.2.1, this kernel is for 4.2.2 roms. Shawdowgun and nova3 run so much smoother on 4.2.2 and motleys kernel at 1.7ghz than any 4.2.1 rom with clemysys. 4.2.2 is a must if you like playing games and with motleys kernel the ui is as snappy as androwook. Quandrant benchmark about the same if not a little higher than androwook at 6300-6400 with forced 2d gpu accel. off.
[Asus  Eee Pad Transformer Prime] Namidairo:
Androwook is neither of those things.

It's 4.1 based.

That's not even the reason it does not work either.
[Asus  Eee Pad Transformer Prime] dcrjay:
Whoops my bad. Meant to say 4.1 but typed down 4.2.1 because of the firmware number. So you can make a kernel that works for all? Cool.I'm not technical like you, just trying to let him know this kernel is not for stock based Roms, he created it for 4.2.2. I don't know why it doesn't work, just a regular Joe. All I know is stock base Roms uses clemsys and now we have Motleys for 4.2.2.

Oh yeah, I would like to also thank you for your work on bringing us 4.2.2
[Asus  Eee Pad Transformer Prime] lortay78:
I do have 64gb version, and I did read the disclaimer and proceded anyway. This was my fault on many levels. But I did get everything fixed. I used the semi-automated complete recovery here: http://xdaforums.com/showthread.php?t=1927818 I tried Win7, doing the manual version, but it still wouldn't boot. The linux version gave me trouble with getting nvflash.so to do anything until I ran this: sudo apt-get install lib32stdc++6 Then it worked like a charm. Hope that helps someone else.

I wish I could try your kernel again, but maybe I'll wait until I have confirmation on someone else with success on a 64gb model first. ;) Also, Thank you Motley for developing kernels for this device. I feel this device could be so much better with a great kernel.
[Asus  Eee Pad Transformer Prime] _motley:
Awesome glad to hear you got it sorted. Thanks for posting your solution. All I need to do is create a boot.blob for CM and AOSP based ROMs and then it should work fine for 32 and 64 GB tabs. It's not the kernel that is incompatible with the 64GB model, it is the anykernel method and the boot.img unpack binaries that don't work for some reason. It is really unfortunate because it makes it a pain to support the different ROMs when they change the boot.img. Never had this issue on any other tablet:(
[Asus  Eee Pad Transformer Prime] _motley:
I have now added blob based installs for b24 for 4.2.2 ROMs. The blob based installs will allow the kernel to be used on 64GB Primes as well.
[Asus  Eee Pad Transformer Prime] ickk:
motley thank you so much dude you're a hero!

my device might be underperforming but quadrant at 1.7 high 1.0 low in performance, almost constant 70fps just by flashing bb8 and your kernel.

feel proud to own this thing again, no kernel problems at all so far.
[Asus  Eee Pad Transformer Prime] lortay78:
Donated and testing 64 on PA now. Thanks!!!
[Asus  Eee Pad Transformer Prime] kix08:
Flashed any kernel twice with TWRP latest version to my 32gb prime running latest bb8 and kernel is not sticking. Wiped catch and dalvik before flashing as well. I've searched thus thread for a bit and did not find nothing that help.(no I didn't read every post) can anyone help so I can get a prime as fast as yours :)

Edit: bad download. Re-downloaded and working
[Asus  Eee Pad Transformer Prime] b.huss2:
FWIW for blackbean:

If you want to see that 65+ fps in quadrant then go to device settings and set CPU mode to performance, otherwise it will be limited to 35.
[Asus  Eee Pad Transformer Prime] _motley:
Thanks, appreciate it! Glad to get the 64GB tabs rollin'

Thanks for stopping back, glad you have it working now.

I haven't had time to check, do you know if the Asus perf modes are calling scripts like in the stock ROM (cpu3.sh etc.), or are the sysfs and setprop calls built-in to the Java app that sets the mode?

I haven't tried BlackBean yet, got it downloaded so I can give it a try as soon as I get some time. I am wondering how all the 4.2.2 ROMs compare in performance. If the modes are going to be built into the ROM's, it would be nice to maintain them, however, if we have 5 modes in the kernel instead of 3 for example, it is a PITA since system_mode 4 and 5 still need to be done manually. What do you think? It would be cool if we could work together to get a kernel and device tree in sync to support the same number of modes for proper OC and perhaps GPU OC:D
[Asus  Eee Pad Transformer Prime] b.huss2:
I'm not real familiar with the kernel side but I can tell you what I see through the device tree. "autoparts" just sets a string for cpu mode (0, 1 or 2) and the specifics are defined in "init.cardhu.cpu.rc". I suppose the rest is kernel side.
[Asus  Eee Pad Transformer Prime] dj-bilbo:
ROM: Cm10.1 build Feb26th

Kernel: motley b24 CM blob "as is"

Few things I noticed - Install was a breeze. Wiped cache&dalik just because.

1) On 1st boot, lock screen wallpaper was "cut in half" (ie, lower half of screen was black, upper half had the wallpaper). After unlock, same thing. Swiped to the left and wallpaper was back to normal.

2) ext microSD card notification that my "card was corrupt" and needed formatting. Ejected it and put it back in. everything back to normal.

3) screened timed out (as usual after 30s) but impossible to power screen on again by pressing "power" button for 1s or 2-3seconds. I know the Prime is "on" because when plugged to the computer, i get the usb prompt and am able to explore the prime. Had to hard reboot it.

After reboot, prime seemed to function normally. able to power off/on as before.

Smoother transition b/t screens when in perf mode vs balance mode. Might just leave it on perf mode 24h/7 for a better experience!

Performance mode w/ 1400Mhz (enabled in CM settings & performance governor):

Nenamark2 score- 61.5fps

Quadrant Std- 1st run:5465 / 2nd run: 5290

Antutu v3.1.2- 1400 MHz (x4) [800x1232]

Total score: 14057

CPU: 7596 / GPU: 3079

RAM: 2588 / I/O: 794

Balance mode w/ 1700Mhz (interactive governor)

Nenamark2:

Quadrant: 1st run: 5894 / 2nd run: 6090

Antutu v3.1.2- 1700 MHz (x4) [800x1232]

Total score: 15907

CPU: 9227 / GPU: 2884

RAM: 2970 / I/O: 826

Performance mode w/1700Mhz (interactive gov)

Nenamark2: 63.1fps

Quadrant: 1st run: 6143 / 2nd run: 6231

Antutu v3.1.2- 1700 MHz (x4) [800x1232]

Total score: 16395

CPU: 9291 / GPU: 3289

RAM: 2998 / I/O: 817

At this point I'm not sure if i should O/C to 1700Mhz with balance mode & interactive gov OR Keep 1400 MHz with performance mode & interactive gov...
[Asus  Eee Pad Transformer Prime] _motley:
Thx, I'll take a closer look. I know the kernel side well, but not how the custom ROMs are handling the modes. In the the stock ROM, the ROM played role in what it changed when switching between the modes. It would run a script for each mode. For example, when you clicked performance, it would run a script somewhat like what I have pasted below. I have taken the system_mode out of the picture now, so now I need to know what else it is doing. The system mode is what keeps your CPU max at a certain speed, but the other settings still come into play. It is annoying though because your max will be seen to be at 1700, but you can't go past whatever the frequency is set by the mode. I have a love/hate relationship with this setup LOL. The 3 modes are neat, but you can only choose one freq for performance. It would be cool to have 6 modes, something like (power save, balanced 1.3, performance stock 1.4, OC slot 1 1.6, OC slot 2 1.7, OC slot 3 1.8). However, if the ROM's don't allow for this, then I would rather just build a generic kernel that works like a Nexus device and cut out the Asus mode BS. Users can then set their max frequency as they wish and play with whatever other settings they like. We might be in OK shape as we have it now though, I just need to understand what else is happening when you click those modes from the ROM's, and if all the ROMs are doing the same thing. I'll study the Java code to find out.

#!/bin/sh -x

echo 0 > /sys/module/cpu_tegra/parameters/system_mode

echo 1300 /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

Thanks for the feedback!
[Asus  Eee Pad Transformer Prime] justcookiesncream:
I feel that I've got some questions in mind in terms of the over clocking mechanics

Judging by the modes that you have is it safe to assume that the over clock makes an adjustment to each performance profile?

However if that's so what's the difference between a 1.7ghz set up on Balance mode and a 1.7ghz setup on performance mode that resulted in a difference in benchmark scores?
[Asus  Eee Pad Transformer Prime] _motley:
If you look at my last post, I would say that this is likely the answer to your question (I have listed again here below and removed the first one since it doesn't matter). When you switch between modes, the ROM should be setting all the sysfs parameters and properties for the mode, like it did for stock. These other settings are the difference and why the scores differ. In stock, I believe the scripts were in /system/etc, but I haven't had a chance to figure out how it works in the custom 4.2.2 ROMs, or if it is even working correctly for the different ROMs we have available. I know the power modes were just merged for one of the ROMs I saw.

What we can do though is set the mode in a each ROM and then go check sysfs and check the properties to see if they are being set for each ROM as we would expect. These are the settings where some may different between the modes. The first one will be very limiting since lowering the core voltage will prevent higher frequencies above a certain threshold.

echo 1300 /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
[Asus  Eee Pad Transformer Prime] rocky3:
blackbean 8

Any kernel for a 64Gb prime running blackbean 8
[Asus  Eee Pad Transformer Prime] ZebTheCalvinist:
This is probably a dumb question, but what app should I use to overclock using the 4.2.2 anykernel? SetCPU only registers the option of running it up to 1.4ghz, as does ROM Toolbox.
[Asus  Eee Pad Transformer Prime] _motley:
Does this mean it worked for you (not likely), or is this a question? You should be able to use the AOSP/PA blob based zip install.

Something doesn't sound right. If it flashed correctly, you should bet able to set to a max of 1.7 (it will boot to 1.4 though). I can see 1.7 in SetCPU. Check in System|About tablet to make sure the kernel is mine (motley build #24). If you flash a ROM after the kernel flash, the kernel will be replaced and you will need to flash it again each time you upgrade or change your ROM.
[Asus  Eee Pad Transformer Prime] ZebTheCalvinist:
Haha, well I feel silly... I thought I had flashed the kernel in TWRP after I had flashed the latest build of BlackBean, but I guess I either didn't have it in queue or it didn't take, because it was still on the stock kernel. I suppose that would explain my issues. Thanks!
[Asus  Eee Pad Transformer Prime] _motley:
No problem. When you do a blob based install, you have to allow the blob to be staged and then it is flashed on the first boot. After the first boot of the ROM, then you can come back and do the AnyKernel install. Not sure if that was it, but it can be confusing when coming from other devices that don't have the silly blobs:silly: