Related
AnyKernel zips will only replace the kernel in your boot.img.
To define a boot.img:
Kernel(zImage) + ramdisk(root file system + init scripts) = boot.img
Where AnyKernel came from:
While searching for different kernels for my Motorola Droid I stumbled on a great idea implemented by Koush. Basically it will split the boot.img from recovery while your phone is running then replace the kernel and make a new boot.img and flash it along with the correct modules for the kernel.
I figured I would implement it on the CDMA Hero and it worked out.
This will work on any rooted rom with a custom recovery running Sense UI including the stock rom.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are the undervolted and overclocked kernels for Sense ROMS
These kernels are built from the HTC heroc-2.6.29-bc0d2ccf source with toasts overclock patch modified by darchstar/Decad3nce to include undervolt.
The git repo for this is @ http://github.com/zenulator/htc-heroc-2.6.29-bc0d2cff
The GPL license can be read @ http://www.gnu.org/licenses/gpl.html
ZenKernel-HTC-08122010 no perf lock
It has perf lock disabled to allow full overclocking with out the need use setcpu to disable perf lock. The clock speeds will stay at what ever the target rom uses unless you running a rom with no overclock built in. If so it will scale from 19mhz to 768mhz.
Download
ZenKernel-HTC-08122010 perf lock
Same as above but with perf lock enabled. It will run at stock values on any sense Rom until you use setcpu. To overclock it you will need to set setcpu to autodetect and then disable perf lock inside setcpu.
Download
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
StockVoltage Overclocked Kernel:
This kernel is built from the same source as the rest except the voltages were changed to stock values. It will max out at 691 and the governor is set to performance.
Download
Setcpu is free for xda memebers and can be found here:
http://forum.xda-developers.com/showpost.php?p=3638937&postcount=1
Instructions:
Download the update and copy it to the root of your sdcard.
Reboot into recovery.
Nandroid (just in case you want to go back)
Flash the update
Reboot
Check Settings > About phone > Software information > Kernel version
_____________________________________________________________________________
If you wish to modify this with another kernel just extract the update and replace the zImage in the kernel directory with the one you want and replace the corresponding modules. Then rezip and resign and flash. It will work on any 2.1 sense rom regardless of boot.img.
Damn good work zenulator I am downloading it now and will test thoroughly tomorrow and see how it go's.
Thanks for the hard work.
Works great, using it with your beta ROM. Lock screen lag is gone
I got used to it so I barely noticed it... but now it seems a lot faster
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
thatguythatdid said:
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
Click to expand...
Click to collapse
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
zenulator said:
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
Click to expand...
Click to collapse
Thanks for the reply I'm gonna give the new kernel a chance to see how it does
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Thanks for this zen works great
this is undervolted correct? does this really help the battery life?
c00ller said:
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Click to expand...
Click to collapse
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Decad3nce said:
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Click to expand...
Click to collapse
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Now with the HTC Synaptics driver included, the swipe action once the screen is on is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Well just an update but it has been very smooth so far, 8 hours as still smooth . Great job. Screen rotation and scroll seem quicker also .
Sent from my HERO200 using XDA App
Papa Smurf151 said:
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Click to expand...
Click to collapse
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
zer0vette said:
Now with the HTC Synaptics driver included, the swipe action once the screen is one is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Click to expand...
Click to collapse
I've always wondered about this delay with the OC kernels as well.
Sent from my HERO200 using XDA App
zenulator said:
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Papa Smurf151 said:
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Click to expand...
Click to collapse
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
zenulator said:
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Now this is what I'm talking about
I was looking for something like this. Darchstar is one helluva dev, but it seems like the only kernels in use these days are Toasts (base) then modded toast kerenels by Darchstar (which are great as well). But I'd like to see a couple of tweaks fixed in the most recent Kernel #6 such as the typo that Uroshiol mentioned that is located in the actual zImage in the DArchstar uv2 kernel 710 with freememkiller
Nice nice work ya'llz and great stuff Zen... makes the addition of new kernels a breeeeze
Wait...so there is an under volted, oc kernel available for nfinite's .6 stock rom that eliminates the menu button wake lag?? i dont like the lag but deal with it. although if there is a way to eliminate the lag, please share!!
Zen, you're definitely an unsung hero (no pun intended I swear) around these parts and I for one definitely appreciate your work. Cheers!
I think the Gtab devs should team up too.
http://tabletroms.com/index.php/2011/07/08/adamcomb-v0-1-vegacomb-beta-1-7-released-today-782011/
Wonder is this AdamComb v0.1 can be flashed on gtab ?
Anybody knows ?
Dave,
I haven't tried it, but it probably can, so long as you also flash Clem's HC kernel. Some of the drivers might not be there though, like wifi.
I'm really hoping zhyong makes that his next bl1.1 project.
MC
Should be able to.
Ok, I nvflashed back to 1.2, installed adamcomb. wifi works. I'll start testing other things.
I didn't install clem or pershoot kernel. I'm wondering if the vega/adam teams are using anything from Eduardo's .36 kernel port?
MC
Thanks for the heads up. I'll take a look at it.
MicroChip said:
Ok, I nvflashed back to 1.2, installed adamcomb. wifi works. I'll start testing other things.
I didn't install clem or pershoot kernel. I'm wondering if the vega/adam teams are using anything from Eduardo's .36 kernel port?
MC
Click to expand...
Click to collapse
Great work ! I assume that you are using standard recovery to flash, not CWM1.2 bl friendly ?
Keep us posted with your evaluation, please.
Dave
I used bl 1.2 with cwm. I'm doing testing now. I'm probably going to want to add pershoot kernel but want to test all the other stuff first like flash, youtube, etc...
MC
Adamcomb does work on the gtab, I just installed with cwm, Bootloader 1.2 required, will report later after testing.
.
Thanks
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Can't help but +1 for the effort. I hope you get this going
MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Uh... I hope you know how to sign a zip file so it will install in an android device. If not, tell me and I'll add instructions on my website so that everyone can become a dev.
MicroChip said:
As I suspected, adding pershoot kernel killed wifi. I know which files to move and from where, but will test that later or in the morning.
Once I have that, I don't mind packaging as a rom but could use a little advice (or a wiki somewhere) on how to take the rom, copy pershoot's kernel to it, sort out the meta-inf's or whatever I have to do to get it to install kernel, and rezip it.
If anybody can help me there, I'm willing to start maintaining this rom...
MC
Click to expand...
Click to collapse
Best luck to you and wish that you will gain the knowledge somehow to do so. Your initiative to take on this subject is to be complimented.
Meanwhile, our friendly developer tlbardelljr just ported some features from this rom to the Flashback rev 5.3 http://forum.xda-developers.com/showthread.php?t=1138100. However, I hope (perhaps many would agree) that you would continue your path. It is fun and educational anyway.
Dave
goodintentions said:
Uh... I hope you know how to sign a zip file so it will install in an android device. If not, tell me and I'll add instructions on my website so that everyone can become a dev.
Click to expand...
Click to collapse
Great idea. Your works are much appreciated by a great many.
Dave
As I hoped, Zhyong got it done. He's way ahead of me in terms of knowledge and putting roms together.
I found that using Adamcomb by itself didn't cause sleep of death, but when I added pershoot kernel, I got sleep of death and couldn't sort that out. Going to play with Zhyong's bl1.1 and 1.2 versions and try to see how he did it.
His roms based on Adamcomb are in the Rom dev forum here and it's his 3.0.
MC
MicroChip said:
I found that using Adamcomb by itself didn't cause sleep of death, but when I added pershoot kernel, I got sleep of death and couldn't sort that out.
Click to expand...
Click to collapse
Sleep of death is usually due to undervolting. Pershoot's kernel does that. Some tegra-2 cpus can undervolt lower than others. If yours can't, the "sleep of death" is the result.
schettj said:
Sleep of death is usually due to undervolting. Pershoot's kernel does that. Some tegra-2 cpus can undervolt lower than others. If yours can't, the "sleep of death" is the result.
Click to expand...
Click to collapse
Possibly, but it only happens with bl1.2 roms, and not bl1.1 roms. I'm pretty sure zhyong used the same adamcomb base, and pershoot kernel, and made one for bl1.1 and one for bl1.2 and I installed and got no sleep of death on 1.1. I'll try his 1.2 and see if the result is the same.
It would possibly make sense as I think originally roebeet built his 1.2 honeycomb roms with clemsyn kernel and switched to pershoot around his version 4 or 5 and before that I didn't have sod, but even now, if I take adamcomb and put clemsyn kernel on 1.2, I get sod. It definitely seems bl 1.2 related, though I know some people have the problem and some don't.
MC
GtabComb is basically a direct port of AdamComb, but with some very useful gTab optimizations. In my (limited) testing it is fully compatible with other Pershoot kernels as well.
This is a new Custom Kernel I started a few days ago. Using Samsung's source as base, I'll go adding features one by one. I'll try not to add a lot of things, but just enough to have a good battery life and performance.
Features:
Overclock up to 1083Mhz.
Kernel HZ: 750.
Voodoo sound driver v10.
1% Battery Mod.
Lagfree governor.
5 touchpoints.
Has Simple I/O Scheduler, optimized for flash devices and set as default.
Bootup progress bar enabled.
Compiled with arch-specific flags.
Root ADB.
Busybox.
Filesystems support (same as other kernels) and convertion.
G3Mod's ClockWorkMod Recovery & RZRecovery versions.
Toggleable Compcache.
Support for early init scripts (aka init.d).
Credits:
marcellusbe, for all he's done for G3.
Dharamg3, for teaching me almost all I know of Kernel developing, for creating G3Mod and all he's done.
Hillbeast, for working with me in G3Mod and teaching me some stuff from time to time.
Source code:
https://github.com/moikop/Astrum-Kernel
Changelog
Andromedae (v1.0):
Hillbeast's Data2SD support added.
Added one more CPU step: 1083Mhz (Only recommended when high performance is needed).
Alpha Centauri (A1):
"Pre-initial" release.
Downloads
Downloads: http://code.google.com/p/astrum-kernel-apollo/downloads/list
Nice :-D
Sent from my GT-I5800 using Tapatalk
Good luck Moikop!
BTW. 750 Hz?
will it be able to run cm7?
Sent from my GT-I5800 using Tapatalk
KSLevel11 said:
Good luck Moikop!
BTW. 750 Hz?
Click to expand...
Click to collapse
Yes. Seems to have a good performance, and yet not too much to overload the cpu or have significant effect on battery. Still testing though..
EternalFame said:
will it be able to run cm7?
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
Maybe not in the first releases, since I want to get other things working first (like overclocking). But yes, it will.
Don't know about Hillbeast's Data2SD system yet, but either way it's not a priority (since you can use an init.d script to do the same thing).
Great idea man.I think it is more usefull to make more kernels than "custom ROM's" which are copies from one or two
How about cwm5? (or some other recovery - there are many)
cdesai said:
How about cwm5? (or some other recovery - there are many)
Click to expand...
Click to collapse
Yes, RZ Recovery is nice.
Very nice. Good luck.
I think its not so good to spiit the g3mod team, that was probably hillbeasts fail. I think its better to merge astrum with kyorakernel or with other words to rewrite g3mod with hillbeast.
cdesai said:
How about cwm5? (or some other recovery - there are many)
Click to expand...
Click to collapse
Mohanshbhr said:
Yes, RZ Recovery is nice.
Click to expand...
Click to collapse
G3Mod Recovery is only temporarily (so I don't have to use Stock recovery :S). Maybe I'll port RZ. Which one would you guys prefer? CWM5 or RZ?
TearsDontFalls said:
I think its not so good to spiit the g3mod team, that was probably hillbeasts fail. I think its better to merge astrum with kyorakernel or with other words to rewrite g3mod with hillbeast.
Click to expand...
Click to collapse
G3Mod is still on foot. Hillbeast and I will still bring support for it. Eventually there will be G3Mod updates (as long as the changes are significant). So users who still want to use G3Mod Kernel, they don't have to change. A little diversity won't hurt anyone, will it?
Please add CWM, most of users learned to use this recovery so changing now could be a little confusing. And CWM is used in CM too... having a unique recovery is better than 2 or more different...
andreapier said:
Please add CWM, most of users learned to use this recovery so changing now could be a little confusing. And CWM is used in CM too... having a unique recovery is better than 2 or more different...
Click to expand...
Click to collapse
RZ recover is a very nice recovery, nice colour profile, nice menu options, take a look at RZ recovery its really very nice recovery. We already have cwm 5, may be hillbeast is going to port cwm5 in his kernel, so there is no benefit of having same recovery in both kernel, and about confusion in recovery, recovery is not quantum mechanics, spending some minutes on recovery made it easy. A have a personal request please port RZ recovery. I think RZ recovery is ported to galaxy w and some more galaxy devices.
@ moikop
hi mate
is there any chance of adding compatibility to ecliar
thanks in advance
austin266 said:
@ moikop
hi mate
is there any chance of adding compatibility to ecliar
thanks in advance
Click to expand...
Click to collapse
No. Froyo now, GB & ICS later. But no Eclair..
moikop said:
No. Froyo now, GB & ICS later. But no Eclair..
Click to expand...
Click to collapse
but is it possible?.
Edit: maybe Amon Ra recovery, its also used alot.
RafayelG said:
but is it possible?.
Edit: maybe Amon Ra recovery, its also used alot.
Click to expand...
Click to collapse
Yes, it's possible.
I've already started working on RZ Recovery. It boots, but I'm getting a weird problem :S
This kernel aims to improve performance, while still maximizing stability (and getting rid of reboots and SODs). It's working on all ROMs so far, so here it is for your approval. It can overclock to 1704Mhz, but doesn't override your user limit. I've added SIO and Init.d support and some various tweaks, and rebased to the newest source. Next is more cpu governors and general tweaks. Thanks to Roach for his commits from github, and guevor for new suspend code to imitate.
Some ROMs use a different build config, so Use The Right Version Below! Please Wipe Cache in CWM before flashing.
Update 4/11/12: Added test version of Veno, read about it at: http://www.ie.cuhk.edu.hk/fileadmin/staff_upload/soung/Journal/J3.pdf1.0 is up for All testers. Voodoo should be supported, please report. Wifi has been tested on Stock/ARHD/Revolver/Megatron/CNA/AOKP, but please test with other ROMs. I'm trying to compile one kernel for all ROMs, but EOS is still separate. Mega props to Guevor for the new suspend code. I'm trying to implement it without directly copying him though, so I need testers again. I will compile for other ROMs if necessary.
Update 4/7/12-2: 0.8 Added OC up to 1704mhz, Under/Overvolt support, made some changes to error handling for wifi stack, tweaked default voltages, and some stuff I can't remember right now. For testing, 0.8 downloads are in green. CIFS, TUN, and NTFS are cooked in, you should not need to load modules. There is a download link provided below for people who want the modules anyways.Personally tested on all ROMs listed, haven't had time to try Frozn.
Install with CWM or Rogue
Download 1.0(All ROMs, except EOS):http://db.tt/nNEbqufy
Download 1.0 With TCP_VENO(All ROMs, except EOS):http://db.tt/CqEqLMDQ
Download 1.0(EOS):http://db.tt/nnn4x9mN
Download 0.8(Stock/ARHD/Revolver/Megatron):http://db.tt/XyxW8WTK
Download 0.8(CNA/CM9Mar29/AOKP):http://db.tt/fiOXe16e
Download 0.8(EOS)http://db.tt/rcUAfPjz
Download 0.6 (Stock/ARHD/Revolver):http://db.tt/YDIInoKn
Download 0.6 (CNA, CM9, AOKP):http://db.tt/wdwPhWVt
Download 0.6 (EOS):http://db.tt/1yAOB7tq
Download 0.7 (Stock/ARHD/Revolver):http://db.tt/YsOdC3Tk
Download 0.7 (CNA, CM9, AOKP):http://db.tt/91iLDpKq
Download 0.7 (EOS):http://db.tt/HVY81MUQ
CIFS/NTFS Modules: http://dl.dropbox.com/u/21284412/modules.zip
You shouldn't need these, but I'll leave the link for old time's sake.
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
I had a couple requests for a donation link, so I'm posting one below. Feel free to buy me a beer if you want, but most of the work was done by the source code and people before me.
Click Here To Donate To My Delinquency
Github is at: https://github.com/msticninja/asus_kernel_tf101
Changelog:
Code:
1.0-Veno Add TCP_VENO as default ipv4 Congestion Control Method
1.0 Change suspend code to be closer to guevor's. Hopefully fix reboots again. Add post_boot exec for ARHD.
0.9 Change clk_disable_locked code to be closer to Nvidia source. Hopefully fix reboots.
0.8 Add BFQ, Over/Undervolt support, wifi patches, OC to 1704, etc.
0.7 Rebased off Asus March 29th Kernel Source. SIO/Init.d is now included in all kernels.
0.6 Fixed Wifi on CNA SIO Version(still getting the hang of using git branches, sorry)
0.5 Add Init.d support to ramdisk
0.4 Add SIO IO Scheduler
0.3 Add EOS Version
0.2 Add CNA/CM9/AOKP Version
0.1 Add OC and compile tweaks
Compatible with cyanogenmod?
psyk974 said:
Compatible with cyanogenmod?
Click to expand...
Click to collapse
Depends. Try it. The worst thing will be that the wifi doesn't work. I'm working on the bcmdhd version for people with AOSP roms, that may use the same driver.
Thx. I will try it !
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
psyk974 said:
Thx. I will try it !
Click to expand...
Click to collapse
Let me know what happens. If anything isn't right, give me as much detail as you can.
i9apps said:
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
Click to expand...
Click to collapse
Just checked with a couple of flash drives, works perfectly.
msticninja said:
Let me know what happens. If anything isn't right, give me as much detail as you can.
Click to expand...
Click to collapse
Okay ! I inform you
msticninja said:
I just compiled this from my github, which is forked from Roach's(He's working on EOS, so I'm filling in the void for now, with his permission). It's working beautifully for me on stock ROM and ARHD so far, so here it is for testing. It can overclock to 1600Mhz, but doesn't override your user limit. Blades' test kernel "meh" overrides the user limit once the screen is off, which makes my TF reboot constantly. That's really the only reason I compiled my own kernel, but I know other people have this issue, and Roach said he doesn't have time to compile and post it for us. Thanks to Roach of course, and Blades, because I used his "meh" updater-script (because I forgot which partition the kernel was supposed to be dd'ed to.)
Install with CWM, (or Rogue(untested though))
Download:http://db.tt/wKQ6ho2h
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
Going to bed now. Will respond to responding responders in morning. Seriously. Me So Tired.
P.S. @guevor Didn't mean to post this right after you merged Roach's fix, we must've been compiling at the same time, little did we know.
Click to expand...
Click to collapse
Dont forget the source or patches main rule !!!
Could you list the Core mV per frequency too please?
Jhinta said:
Dont forget the source or patches main rule !!!
Click to expand...
Click to collapse
Grrr...lack of sleep. I thought I did. Appended.
cspiby said:
Could you list the Core mV per frequency too please?
Click to expand...
Click to collapse
https://github.com/msticninja/asus_kernel_tf101/blob/d1da185880877e22c7881fe69d4cb650e7a84ba5/arch/arm/mach-tegra/tegra2_dvfs.c
Too sleepy to make a table out of it. I'll do it tomorrow if you can't figure it out from the source.
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
i9apps said:
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
Click to expand...
Click to collapse
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
initd support?
drakal said:
initd support?
Click to expand...
Click to collapse
Haven't had time yet, just made it for my own purposes originally. I'll put a new ramdisk together and repack tomorrow if someone else hasn't done it by then.
msticninja said:
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
Click to expand...
Click to collapse
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
i9apps said:
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
Click to expand...
Click to collapse
I haven't tested on Revolver. I didn't add init.d support yet, so it could be that. Can you run at lower frequencies without rebooting? Mine can't handle 1600 on any kernel, so I can't really troubleshoot that, but if it still reboots at 1000 or 1200, then it's probably a ROM incompatibility. We'll see if anyone else can test it on Revolver in the mean time.
Hi,
tested your kernel with CNA 1.5.5.3 sadly no wifi.
Now I'm back on stock
Greetings
Nice to see more kernels popping up
I would help you test it, but frankly Im not in the mood to troubleshoot (if needed) today
Been screaming at a PC all day that refused to work properly hehe
Hi, does anyone have a link to the bodivas repack kernel for the 6810? The link is missing from UTIA's second post in the thread for his kernel. I want to give his kernel a whirl. Thanks, Matt
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
mattbuffey said:
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
Click to expand...
Click to collapse
I'll upload it later today. Forgot all about it sorry.
Firstly, did you flash the SkyHigh kernel after first boot of any ROM? Don't flash directly after ROM flash. Otherwise boot loop. Only after ROM full boot.
Secondly, make sure that you have no tweaks or tweaking apps etc installed.
For the ROM, you need to follow the installation instructions EXACTLY, using correct recovery version and full wipe install.
Other than that, unfortunately, your hardware may not like some of the kernel tweaking or UV etc.
BTW, I'm working on a SkyHigh kernel update. Maybe try that in future "IF" I ever get to release stage.....
Sent from my GT-I9500 using XDA Premium 4 mobile app
It's weird, I had the same problem with your ROM on ICS. I was hoping JB would be different, but I got exactly the same stability problem. As you say, it must be something to do with the tweaks that upsets my tab. I can report that CIFS works fine with your kernel though!