yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] Diamondback:
And now @OP

I guess the kernel itself is based on the outdated ASUS source?

And for the next build, maybe make a verion where you overclock the 1.6GHz mode instead of the Performance mode?

Most (if not all) who would use such a kernel, use some kind of tool/app/rom which can access the 1.6 Ghz mode anyway, so you are better of tweaking the 1.6Ghz mode :)
[Asus  Eee Pad Transformer Prime] the2rrell:
looks promising. will wait till for the updated version before i start playing with the kernel.

but always appreciate the work bruh thanks.
[Asus  Eee Pad Transformer Prime] jermaine151:
Correct me if I'm wrong, but the kernel versions are identical and the only things that changed were the host that the new kernel was compiled on and the appended string on the end. It sounds to me like they just built the same source with a different config.

Am I missing something???
[Asus  Eee Pad Transformer Prime] Diamondback:
First: I have no idea about kernels or building them from source :p

I only see that we got several kernel upgrades without getting new kernel source from ASUS.

So I guessed that they have newer source, correct me if I am wrong here :)
[Asus  Eee Pad Transformer Prime] jermaine151:
I think we'll only get a new release if they use a different source version. The kernel version hasn't changed on their ICS kernels yet, so I "believe" that the source they have posted is the latest and is what they built the mercury kernel from.
[Asus  Eee Pad Transformer Prime] Diamondback:
Oh okay, good to know :)
[Asus  Eee Pad Transformer Prime] tassadar898:
I tried my best for the past 10 hours and couldnt get the boot.img repacked. Is there a way someone can help me do it?
[Asus  Eee Pad Transformer Prime] jermaine151:
I attached a pretty much stock kernel blob (Dr Wowe's kernel) to this post:

http://xdaforums.com/showpost.php?p=23182705&postcount=13

You need to grab it out of the zip file. Maybe that will help you get up and running again.
[Asus  Eee Pad Transformer Prime] cfaberlle:
This is great! Can't wait till this kernel is included in one of the stock roms ;) ;)
[Asus  Eee Pad Transformer Prime] Atlas7:
If was this kernel make it like app can i get overclock without unlockbootloader???
[Asus  Eee Pad Transformer Prime] jermaine151:
EDIT: Thanks to demandarin for testing this. It looks like this will NOT be able to be flashed on a Prime with a locked bootloader. It was worth a shot. I'll leave the attachment in case anyone needs this kernel in a signed blob format.
[Asus  Eee Pad Transformer Prime] SOTK:
Prime gets pretty hot running benchmarks at 1700. First time I've noticed any heat at all since owning this. Gets a little warm playing games but not too bad. Running CF Bench made it hot..hot to the touch. Its stable though. Haven't had any reboots or force closes.
[Asus  Eee Pad Transformer Prime] di11igaf:
hey motley, just wondering did your kernel boot first try after you applied the 9.4.2.17 patches?

i just diffed and made a patch with the .17 updates, patched them into my source recompiled, all went fine, prime wont boot though.

hangs at asus screen.

just asking if yours booted right up or not with the source from new release.

doesnt boot far enough for me to logcat neither.
[Asus  Eee Pad Transformer Prime] _motley:
Yep, it booted right up the first time after I merged in the diffs from .17. It shouldn't be the new Asus changes keeping it from booting if they were merged successfully. If it were me, I would roll back and try my last build that worked. If it works, then at least you know your existing build and flashing process is sound.
[Asus  Eee Pad Transformer Prime] _motley:
I have some insight on these issues from another user running the virtuous rom and I think it may help us narrow down what is going on here. I added init.d support in this last version and perhaps it is different than what the Virtuous ROM expects. Before this latest version of the kernel, when you would flash my older kernels with Virtuous, it would remove init.d support from the ROM since the kernel install contained the stock initramfs and replaced the initramfs that Diamondback had in the ROM. All the scripts that he had running on boot would no longer run after the kernel install. Now with this latest kernel version, all the scripts in /system/etc/init.d are now running on boot with my latest kernel. I haven't studied his initramfs and init.d setup yet, but I will take a look when I get a chance. Most likely a kernel install using his initramfs will need to be created for the Virtuous ROM for it to work properly.

Here is what the user reported to me in a PM: "i read that someone was having probs with - android.process.acore force closing . i also encountered this with virtuous rom v2 after flashing your update from #14 to your newer #15 kernal . now after much time and nandroid backups ;) I've narrowed it down to this... its not your kernal. i did a fresh reinstall..had issues with script manager not getting Super User even after giving it permission, it would give me some errors about no root .. i updated busybox to 1.19.4 with serticson's busybox installer, thinking it was that.. anyway after that, i ran the KickAss Kernalizer. after my reboot i started getting those FCs. if i tired to use my home screen google search bar widget that would trigger it..BAM...FC.. now the odd thing is that before on your older #14 kernal i had both KAK and V6 supercharger and everything functioned fine."

I also would like to study if any ROMs having issues are disabling journaling on the file systems during the init process (within initramfs where they are mounted). While giving better speed, this sacrifices recover-ability of the file system and I have seen this cause problems in other ROMs before where users need to reload periodically because of this.

Let me know if anyone else has additional input or ideas. Hopefully Diamondback can also lend a hand and give his input.
[Asus  Eee Pad Transformer Prime] di11igaf:
Thanks for the info about the .19 patches, I'm just gonna have to

to recompile without my last few patches like you said.

Also, Asus has already disabled the file system journaling by default. /data /cache and /system (system may be ordered can't remember, doesn't really get written to much anyway) are data=writeback(no journal)
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Thanks for the explanation. After a little research I figured out the fcs were due to the contacts and contact providers (or something like that). Since I never use those on my tab I just deleted em and the FCs disappeared. I did notice a bunch of scripts from virtuous in the init.d folder from virtuous and figured I'd let em be since they might help optimize stuff. Hopefully you guys can find a solution!

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] _motley:
Good deal, glad you have it sorted. I see some others in the rom thread having similar issues, so I am going to sit tight for now until the dust settles a bit. It doesn't appear to have anything to do with the kernel, but we'll have to keep an eye on it. Thanks for reporting back.
[Asus  Eee Pad Transformer Prime] Turge:
Agreed. I resolved the FC by deleting the /data/data/com.android.providers.contacts folder after seeing these errors:

W/dalvikvm( 1153): threadid=11: thread exiting with uncaught exception (group=0x40a4f1f8)
E/AndroidRuntime( 1153): FATAL EXCEPTION: ContactsProviderWorker
E/AndroidRuntime( 1153): java.lang.RuntimeException: Unable to create photo storage directory /data/data/com.android.pro
viders.contacts/files/profile/photos
E/AndroidRuntime( 1153): at com.android.providers.contacts.PhotoStore.<init>(PhotoStore.java:72)
E/AndroidRuntime( 1153): at com.android.providers.contacts.ContactsProvider2.initForDefaultLocale(ContactsProvide
r2.java:1483)
E/AndroidRuntime( 1153): at com.android.providers.contacts.ContactsProvider2.performBackgroundTask(ContactsProvid
er2.java:1543)
E/AndroidRuntime( 1153): at com.android.providers.contacts.ContactsProvider2$1.handleMessage(ContactsProvider2.ja
va:1430)
E/AndroidRuntime( 1153): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1153): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1153): at android.os.HandlerThread.run(HandlerThread.java:60)

Motley, what are the chances of implementing unsecured boot to your kernel so that we can adb shell/logcat during boot?

---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------

I had to delete /system/etc/init.d/91-fix-contact-pics as well.
[Asus  Eee Pad Transformer Prime] _motley:
The included initramfs default.prop has ro.secure=0. Just make sure USB Debugging is turned on in "Developer options". I can pull up logcat during boot with "adb logcat" (it will attach as soon as adb is available during boot) or shell with "adb shell".

Thanks for the additional info on the contacts provider. I don't think it has anything to do with the kernel, but my ears are still open. I have never seen this issue on the stock rom (9.4.2.15), but if someone else has it would be interesting to hear about it.
[Asus  Eee Pad Transformer Prime] Turge:
You're right.. it is enabled, however, if I type "adb reboot" then "adb logcat" while rebooting, it doesn't start outputting logcat until the lockscreen comes up and just says "waiting for device"

I'm pretty sure this issue will only occur on Virtuous since it appears to be self-inflicted. Here are the contents of /system/etc/init.d/91-fix-contact-pics:

#!/system/bin/sh

# ===========================================================================
# Virtuous ROM Tools (chrisch, Evil D)
#
# $LastChangedDate: 2011-07-18 10:39:15 +0200 (lun. 18 juil. 2011) $
# ===========================================================================
#
# Fixes permissions
# Solves contact pics disappearing in msg app/other apps
#
# ===========================================================================

. /system/virtuous/scripts/virtuous-functions.sh

# ===========================================================================
# Run this section on every boot.
# ===========================================================================

CONTACT_DATA_DIR="/data/data/com.android.providers.contacts"
CONTACT_PIC_DIR="$CONTACT_DATA_DIR/files"
CONTACT_DB="$CONTACT_DATA_DIR/databases/contacts2.db"

if $TEST -d $CONTACT_PIC_DIR ; then
$LOG -p i "Fixing contacts permissions"
$CHMOD 666 $CONTACT_PIC_DIR/*
fi

if $TEST -f $SQLITE ; then
RESTCONT=`$SQLITE $CONTACT_DB 'SELECT count(*) FROM raw_contacts WHERE is_restricted=1';`
if [ "$RESTCONT" != 0 ] ; then
$LOG -p i "Fixing contacts restrictions"
$SQLITE $CONTACT_DB 'UPDATE raw_contacts SET is_restricted=0 WHERE is_restricted=1';
fi
fi
[Asus  Eee Pad Transformer Prime] RamAir02:
As of now, is this kernel safe to flash with Virtuous v2 or no?
[Asus  Eee Pad Transformer Prime] _motley:
Interesting, I can attach using the stock ROM and it starts logging fairly soon after "start adbd" in the init process. Could it be all those init.d scripts firing up on boot? I only have one script in mine...an inert test script to prove that it works.

- waiting for device -
--------- beginning of /dev/log/main
I/DEBUG ( 107): debuggerd: Feb 21 2012 18:34:45
I/Sensor Daemon( 118): Service started
--------- beginning of /dev/log/system
I/Vold ( 105): Vold 2.1 (the revenge) firing up

Great info on the following. Thanks for helping out. This explains why the init.d enabling in kernel 2.1 coincided with this issue for those previously running my 2.0 kernel that didn't provide init.d support.

So, for users wanting to install Virtuous, I recommend you remove the file /system/etc/init.d/91-fix-contact-pics so it doesn't run on init before installing kernel v2.1.
[Asus  Eee Pad Transformer Prime] _motley:
See my notes in the last post and I think you will be good doing it this way. Hopefully Diamondback can provide a flash-able zip with his ramdisk like some of the other ROM devs are doing. I would provide one, but I don't to step on any toes nor do I want folks to expect me to provide a zip to flash for all the ROMs that come out. I will try to work on the Anykernel method I mentioned a few posts back when I get a chance. That would be a better option for all of us.
[Asus  Eee Pad Transformer Prime] demandarin:
any chance this 1.7Ghz can be implemented into an apk form, like Dr.Wowee. EzOcerclock, for rooted, stock rom users? I'd love to try this 1.7Ghz out. I'm sure tons of others on the fence about unlocking would love to also.

I remember Dr. Wowee said he he was looking into it when 1.7Ghz came out at first but his thread hasn't had any updates lately.

just asking since you seem to be the resident kernel master here ;)
[Asus  Eee Pad Transformer Prime] _motley:
Sorry man, I don't see how that is possible since SYSTEM_OVERCLOCK_1P6G_MODE_MAX_FREQ is hard coded at 1.6 in the stock kernel. See https://github.com/motley-git/TF201...6eb1eb38a0619/arch/arm/mach-tegra/cpu-tegra.c
[Asus  Eee Pad Transformer Prime] w1000i:
************* delete *********** sorry
[Asus  Eee Pad Transformer Prime] artro:
Android FTDI Support

Would it be possible for you to incorporate the kernel changes mentioned at http://www.ftdichip.com/Android.htm under the document TN_132_Adding_FTDI_Devices_VCP_Driver_Support_to_Android.pdf? If you could, I would be so very grateful!
[Asus  Eee Pad Transformer Prime] :
2 second look at the document, its stated that for it to function you need access to operating system code/source code level, most likely roms will neee modified (aosp)
[Asus  Eee Pad Transformer Prime] _motley:
Hi, configuring this in the kernel, building a kernel module, and granting permission in ueventd.rc should be be trivial. This theoretically gets you up to step 5. After that, you would be on your own to figure the rest out. I am guessing that you might have some application in mind that already works in Android to drive a device or perhaps you will be building something on your own?

If you are really interested, I can make this happen in the next release. Just let me know.

Step 5

5 Accessing The COM Port Via Java APIs
Despite native applications now having access to the serial port device, applications developed using the
Android SDK will not be able to access the serial port since the Android platform does not include an API
to access serial ports from Java applications. This is a serious limitation for Android application
developers wishing to access FTxxxx devices via the VCP driver.
An open source project has been created to provide the missing serial port Java APIs for Android
(http://code.google.com/p/android-serialport-api/). This project allows access to serial ports, USB or
otherwise, from a Java application on the Android platform. It has been tested on FTDI’s BeagleBoardxM Rev C development platform and has been shown to work after being recompiled from source to
remove the O_DIRECT flag from line 96 of the SerialPort.c source file; the resulting library
(libserial_port.so) should then be copied to /rootfs/system/lib and the application should be copied to
/rootfs/system/app. After copying these files, the SerialPort application will appear on the main Android
application screen and will communicate with the USB serial port.
Please note however, that this is an open-source community project and is not maintained or supported
by FTDI.
[Asus  Eee Pad Transformer Prime] _motley:
Hey guys, sorry I haven't replied on these higher OC inquiries. I still haven't tried to push higher than 1.7GHz. I think most are pleased at 1.7GHz. If I were to try, mV are going to need to go up to about 1550-1600mV to start testing @1.8 I'm afraid. This makes me a bit nervous as I still haven't found any documentation for tegra3 with detailed power specification and limits etc. Even if there was, we already know we are above rec'd limits LOL. Even if we did achieve it, it would be more for show than for real world usability as heat will be a problem and battery life would be poor. I likely would not even provide it as a general release since I feel that I have to have some level of responsibility when doing these things.

Hope this makes sense. If I do try it, I will post my results and findings at least. Who knows, maybe 2 months from now benefit14snake will be running a liquid nitrogen cooled CPU at 3.0 GHZ:) (sarc.)
[Asus  Eee Pad Transformer Prime] newellj79:
Ha! Made me chuckle. Please let us know how things go if you decide to try. I think your right though. At this point is 100mhz going to make that much of a real world difference. That said, the tinkerer in me is still itching to try :)
[Asus  Eee Pad Transformer Prime] benefit14snake:
Haha one can dream Motley =)

Maybe dry ice though, couldnt get my hands on liquid nitrogen when I tried.

I will rip this thing apart when I get bored again. I will make my cooling mod work! BUT.....I just got a dock and am "entertained" for the moment, but as soon as I run out of stuff to flash or play with I get the urge to break things haha.

Edit: I really need to buy a memo or whatever it will be called when it comes out, my wife will KILL me if I break this thing.
[Asus  Eee Pad Transformer Prime] _motley:
New version released with .21 merges

New version released with .21 merges, see first post for more details.
[Asus  Eee Pad Transformer Prime] FunkyMcBain:
Seems to be running with the Virtuous Rom .21
[Asus  Eee Pad Transformer Prime] benefit14snake:
WOOT! new motley kernels always make me happy! Flashed and running great!

Thanks again.
[Asus  Eee Pad Transformer Prime] Striatum_bdr:
Great job motley, thanks
[Asus  Eee Pad Transformer Prime] :
Hey motley could i contact you on any are irc? Or gtalk?
[Asus  Eee Pad Transformer Prime] schack:
VPN

Hi

Does this kernel contain VPN (PPTP & L2TP) modules ?

/Henrik Schack
[Asus  Eee Pad Transformer Prime] jaycustom:
Awesome! So if I'm running WSG with your 2.1, I just flash this over it, correct?

Zen hard bricked his Prime right before releasing an update Saturday, so development is at a stand still. Between this kernel and the Serenity theme, you guys are keeping my ROM fresh.:D
[Asus  Eee Pad Transformer Prime] benefit14snake:
MasterZen should be getting a new prime soon, we raised $475 in just a couple days. There are some truly amazing people on this forum. We really do have a great community!
[Asus  Eee Pad Transformer Prime] _motley:
Hi shaky156, I may be able to be on gtalk later tonight after 9pm Eastern. Please PM me and let me know what you need.

Just added for you! Thx for the reminder. It's built-in, so no modules needed.

Sad to hear!

Great to hear!

New build posted with 1.8GHz experimental mode. Please see the first post for details.
[Asus  Eee Pad Transformer Prime] Spartan301:
I've been reading alot about your kernel and I would love to flash it. However, I'm a novice when it comes to editing system files and whatnot. Would it be possible to have this written in a script format so that when I flash it it's done?

For example. Have 3 different downloadable zips. One for each different clock speed?

Or have the aroma installer in your zip so the user can choose voltage and clock speed etc?
[Asus  Eee Pad Transformer Prime] Turge:
Motley,

Back to being able to access ADB shell/logcat during boot which I still can't do on Virtuous Prime, shouldn't persist.service.adb.enable=1 be enabled in default.prop as well?

Just wondering
[Asus  Eee Pad Transformer Prime] tylermaciaszek:
did all the steps and i only get to 1.3 on virtuous rom
[Asus  Eee Pad Transformer Prime] newellj79:
I'm still maxing out at 1.7 for some reason. About to try again.

Edit... 1.8 working fine. Once again I was over anxious and did fully read the OP. For those where it doesn't seem to be working correctly don't forget to change to cpu scripts. Thanks Motley!!!
[Asus  Eee Pad Transformer Prime] tylermaciaszek:
your doing better then me atleast!
[Asus  Eee Pad Transformer Prime] newellj79:
Just edited my post above yours. All is well now.
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Mines still not getting to 1.8. I just have to change the 0 to a 5 in cpu3.sh then run the script right?

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] _motley:
Definitely good ideas for novice users. I will consider this. I may just have you flash two zips. One for the kernel and one for the setting the mode. Once the mode is in place, you don't have to flash that again unless you change your mind. The kernel zip changes all the time and I don't want to have to make several zips each time I release....more testing required and thus more room for error. I just wish I had more time to work on this stuff!

Read on and see if this helps you for now.

Awesome :)

Yes, like newellj79, make sure you edit the cpu scripts as per the OP instructions. You can use a root file explorer and text editor if you like, just make sure you set the permissions on the file cpu3.sh to allow write access by "Others" than just the owner before you try to edit and save the changes. File Manager HD lets you see permissions as does Root Explorer.

Asus has us using these scripts since they mesh with the UI toggle performance modes. It is kinda neat, but also limiting or at least non-standard for non-stock roms that don't have these toggles. These other roms just have to set a preferred mode during init via a script, or build in something similar. At some point, I may make a custom rom version that just does it the standard way without the system modes.

We may need to try persist.sys.usb.config=mtp,adb for ICS, not sure. So it works fine using my initramfs used with my kernel.

Here is the virtuous default.prop:

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp

Here is my default.prop:

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp

I also just compared my initramfs with Virtuous .21 v1. What is weird is he has a lot of init.d scripts in place in /system/etc/init.d, but I don't see that init.d is implemented in the initramfs. Perhaps he is doing this in the rom in some other way? My worry is that when folks installed the first version of my kernel that had init.d support, it started causing issues because these scripts started running all of the sudden, not sure, but it seems like it. Or, maybe the scripts are now running twice or something...

Unless I made a mistake, a full file level compare on my initramfs versus Virtuous .21 v1 initramfs yields only two differences:

The difference above in default.prop (ro.debuggable=0 for me and ro.debuggable=1 for him)

init.rc - I have an implementation of init.d that uses busybox, so I have this extra service definition

service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root
[Asus  Eee Pad Transformer Prime] _motley:
Yes, that's it. You can just hit the performance mode button (toggle off to balanced mode first and then toggle back on to the fire icon for performance mode).
[Asus  Eee Pad Transformer Prime] tylermaciaszek:
i reflashed kernel and all went well! now at 1.8GHz
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
I'll try that now too and see if I get better luck.

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
Still no dice. Kernel info should say 2.6.39.4+ right?

Sent from my ROOTED Transformer Prime
[Asus  Eee Pad Transformer Prime] newellj79:
Yes thats right. Are you editing the cpu scripts as described in the op?
[Asus  Eee Pad Transformer Prime] YodaDaCoda:
I was wondering if someone can tell me whether or not this kernel includes NFS/CIFS? I'm trying to mount a shared drive but the error messages lead me to conclude that these modules aren't included (but I don't know how to test for sure).

If they aren't included, could adding them be included on a to-do list?
[Asus  Eee Pad Transformer Prime] PapaSmurf6768:
From what I can tell the OP just says to change 0 to a 5 in cpu3.sh, so that's what I've been doing. When that didn't work I followed all the instructions to the T and it still won't get past 1.7ghz

Sent from my ROOTED Transformer Prime