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!
EpicMTD-TWKernel-v1.0
Since there aren't a lot of different kernels available yet for running TouchWiz(TW) roms on MTD, and I've been rather bored while on winter break from college, I decided to put together a basic kernel that is as close to stock as possible while still supporting MTD. This will make a great base for other developers to start off of (I've been doing some work of my own based off of this, but its not ready to be released yet).
This is forked from Rodderik's github, and most of the changes for MTD where cherry-picked from Tortel's github. I got init.d working, modified the kernel build script, and wrote scripts to build the boot.img from the zImage (kernel and first stage initramfs), second stage initramfs, and recovery. I also disabled as many debugging options as possible in the kernel to decrease its memory use and increase its performance. A few other unused kernel features were disabled, and all tweaks and unnecessary parts have been removed from the init.rc file. The tweaks were removed since they can all be done from init.d scripts, and had the potential to interfere with tweaks done in init.d scripts.
This probably isn't the best [fastest] for a day to day kernel, but it does perform surprisingly well, and I have been getting some great data speeds. Been using it for a few days with no crashes.
Features:
MTD Boot
TW Support
Kernel debugging disabled
Kexec (untested)
Schedule autogroup patches
No CIQ
Size of initramfs reduced
Initramfs and Recovery use modules compiled in tree with the kernel (might help stability)
Clockwork recovery 5
DO NOT FLASH THIS IF YOU ARE NOT ALREADY ON AN MTD ROM!
DO NOT FLASH THIS IF YOU ARE ON CYANOGEN MOD!
Download:
EpicMTD-TWKernel-v1.0.zip - 5.7 MB
Source:
GitHub
Info for developers:
If you want to build this kernel from source, I recommend using arm-eabi-4.4.3 or arm-eabi-4.4.0 from the android source repo. (Thanks earthbound for the info!) Both of them seem to work fine with the current source. The code sourcery toolchain works, but it prevents the soft key light from turning off while the screen is on.
Thanks:
Tortel
Rodderik
Earthbound
Everyone in the CM7 team
And the following people who are listed as authors of many of the commits I used:
Mike Kasick
noobnl
DRockstar
Felix Radensky
nullghost
nubecoder
Did I forget anyone? PM me if I did...
FIRST!
Awesome, the more MTD kernels the better! Btw, I'm tracking MTD ROMs and kernels here: http://forum.xda-developers.com/showthread.php?t=1405547
And away we go....
Sent from my PG86100 using xda premium
Say thanks if you agree the a dual boot kernel for cyanogen mod 7 and touch wiz based roms would be a good idea. Especially for those of us who miss their 4g connection.
Sent from my SPH-D700 using xda premium
jamice4u said:
Say thanks if you agree the a dual boot kernel for cyanogen mod 7 and touch wiz based roms would be a good idea. Especially for those of us who miss their 4g connection.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I agree that it is a good idea although I NEVER use my 4G lol, it would definitely increase options and more availability to mtd roms, CyanogenMod and MIUI are the only roms I know of that aren't TW so by allowing us to have mtd with TW it would be loads better. and it would also still allow us to switch back and forth I say, bring on the dualboot mtd/tw kernel!
Most of the touch wiz based roms are converting to mtd.
Sent from my SPH-D700 using xda premium
hey zman, I think the permissions you set on gpsd in your init.rc breaks gps.
Code:
chmod 0777 /system/vendor/bin/gpsd
Using your initramfs in my kernel, GPS was broken and logcat showed permission denied errors in relation to GPS. After switching the permissions to 0755 in my kernel, gps started to work again.
jamice4u said:
Say thanks if you agree the a dual boot kernel for cyanogen mod 7 and touch wiz based roms would be a good idea. Especially for those of us who miss their 4g connection.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Earthbound kernel and this kernel have kexec (or however you spell it) support... = dual boot compatible...
Sent from my SPH-D700 using Tapatalk
Today I saw they launched linux 3.4 with merged android code into it, which made me happy. And also I read that they fixed the powersaving problem since 3.1 to 3.3, so my question is the one above. Will chefs be able to "port" 3.4 kernel to ICS anytime sooner or later? I know I should wait and see, as it is a kernel that was just released, but I just want to know wether this is possible.
It will most likely be merged and release for our Sensation. That is usually what Faux and showp do.
Sent from my HTC Sensation 4G with Beats Audio using XDA App
Thanks for the info, I remembered in my old desire that for example there were no 2.6.35 kernels for gb, so I thought it would not be possible. Hope to see it sooner than later
Hi everyone
Voodoo kernels
I've finally been able to add support for Voodoo Sound into 2.6.39.x kernels, starting with Roach EOS3 #56 & guevor JB kernels.
With a kernel that has Voodoo Sound support added you can simply use the latest free version of the VoodooSound Market app, and it should work fine. (that shouldn't stop you from buying the voodoo sound pro licence to show your support to supercurio )
The 2 kernels zip are tailored specifically for the TeamEos3 JB rom, for other roms someone will most likely have to edit the ramdisk / scripts or simply use the patch posted into post #2 to add support into the kernels.
Please report if the kernels works for you too
This had been bugging me for a while, as the status of voodoo sound for our TF101 has kinda been on hold for a while.
Sure there is the beta app but it doesn't have most of the features from the original app.
And with the recent craving from the voodoo market app to want to overwrite the beta app, it's quite annoying
So now we can simply use the regular Voodoo app.
How to flash the kernels:
Just like any other kernels, use CWM or another recovery tool to flash the zip, then wipe /cache and reboot.
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to your ears.
Makes sure to test it carefully with the headphones not on your ears, before using it.
KatAudio KatAudio has now been moved into the android app See dedicated thread: http://forum.xda-developers.com/showthread.php?t=1841851
Since our current kernels can access the WM8903 registers directly through alsa and don't even require a voodoo kernel module for that, I've added a few "KatAudio" zips to get better sound at boot time directly without the need of voodoo sound.
If you're not only after max power, I'd suggest to flash the default script "Tim_KatAudio01_Enhancer.zip"
I find it to be the best compromise between quality and power myself.
The KatAudio zip will install the command line alsa mixer "tinymix" for you and activate more or less boot scripts automatically depending on which zip you choose, so that you don't have to play with command line
(About alsa see more info in this post: http://forum.xda-developers.com/showthread.php?p=29908141)
When I get more time I'll make an android app that can make it even more powerfull, flexible, and easier for you
I'll also create a new thread at that time, since these scripts are not using anything "Voodoo".
KatAudio Zips
just flash using CWM or another recovery
Tim_KatAudioXX_Enhancer.zip
Speakers: left speaker fix (induce volume boost too)
Headphones: volume boost
Other registers forcing, to make sure they are at their correct values.
Tim_KatAudioXX_Higher.zip
Same as _Enhancer
+ increase the headphones higher to 0dB
+ increase the speakers higher to +3dB
Tim_KatAudioXX_Max1.zip
Same as _Enhancer
+ increase the headphones to max analog +6dB
+ increase the speakers to max analog +6dB
Note that some of the scripts are maxing the volume, which might introduce clipping
If at max digital android volume you ear saturation, just decrease the android volume slightly for those cases.
All scripts above include the "Left Speaker fix", what it does is that it re-routes both LR channels through both Speakers,
that is not considered "hifi" anymore, but I don't think it matters much with that kind of speakers, compared to the benefits:
Lower Left speaker fixing + increase of volume.
From msg #2:
Tim_KatAudioXX_RemoveSpeakerFix.zip
If you prefer not to have the speakerFix activated by default, flash this script after flashing one of the above.
Tim_KatAudioXX_Removal.zip
If you want to remove KatAudio and go back to like it was before.
You can also flash any new rom on top and it'll get rid of it.
Credits:
- Supercurio for the original Voodoo Sound GPL patches I based this one onto.
- Roach and teameos for TeamEOS3 JellyBean Kernel
- Guevor for his awesome kernels
Sources:
For Guevor JB Kernel #696 branch: https://github.com/timduru/tf101-kernel-test
For TeamEOS3 Roach kernel: https://review.teameos.org/#/c/904/
Compatibility report from users:
Tim_VoodooV3_JBKernel_EOS3_Roach56.zip: JB - TeamEOS3
Tim_VoodooV3_JBKernel_EOS3_Guevor696.zip: JB - TeamEOS3
For other roms you should try to flash the "Generic enabler" zip, it seems to work fine with most 2.6.39.x kernel flavors so far, ICS or JellyBean.
For the generic enabler I've moved the kernel side code into a module and it will try to add the module for you at boot time.
(Pending that the rom has init.d support, but most custom roms should have it)
It might be a hit or miss but that shall add support for most kernels in a more generic way
EDIT: Generic enabler zip removed as to respect Supercurio's wish and preferences.
You can check our discussions in his thread if you want to see our views on that subject: http://forum.xda-developers.com/showthread.php?p=29940776
You can still use the specific kernels that have the modules inside, since for him it's not the same and is ok...
Tim_VoodooV3_2.6.39_Kernels_GenericEnabler_2.zip:
ICS - ARHD 3.5.1 - Stock Kernel
ICS - Revolver 4.1.1 - Guevor Kernel V22.6
ICS - ARHD 3.5.1 - test kernel #689
ICS - Megatron 116 - guevor kernel #657
ICS - CM9 Nightlies - Rayman Harmony kernel
JB - TeamEOS3 - GuevorKernel#696
JB - TeamEOS3 - RoachKernel#56
JB - JELLYBRO-cm-10-20120804.1329 - Default rom kernel
JB - RaymanFX-AOSP #3- Default rom kernel
(Working - Works with manual insert - Not Working)
For roms that require a manual insert of the module (rom doesn't support init.d)
do the following:
- launch a terminal
type the following commands:
su
insmod /system/lib/modules/voodoo-sound.ko
kill / relaunch voodoo app.
Please make it compatible with the rayman 33 asop jellybean build!!
excellent work ! working like a charm with the latest Voodoo app from the market and EOS3-N56.
Thank's!!!!!!
what change with this voodoo sound respect to normal sound?
is more hight?
Finally, thanks.
Inviato dal mio Transformer TF101 usando XDA Premium HD app
Can it be OC'ed ???
alizafar said:
Please make it compatible with the rayman 33 asop jellybean build!!
Click to expand...
Click to collapse
Never tried his rom, but I might have a look after I'm done with adding Voodoo to Guevor's kernel..
It should be about the same if rayman has kernel source posted.
cbrox said:
excellent work ! working like a charm with the latest Voodoo app from the market and EOS3-N56.
Thank's!!!!!!
Click to expand...
Click to collapse
perfect, thanks for the report
acquariusoft said:
what change with this voodoo sound respect to normal sound?
is more hight?
Click to expand...
Click to collapse
Supercurio's thread will explain it better than me. check there:
http://forum.xda-developers.com/showthread.php?t=1132875
sagar_tiru2006 said:
Can it be OC'ed ???
Click to expand...
Click to collapse
Yes, for the 1st kernel I posted, the base is EOS3 #56 Roach's kernel.
I see that you are using Guevor V23 kernel, I'm currently trying to get his #696 to compile with Voodoo sound, I'll post it too when I'm done if you prefer to wait for that one
it works very well!!
Good work!
Can you try to solve the problem with audio problem with hdmi output with your kernel?
Inviato dal mio Transformer TF101 con Tapatalk 2
acquariusoft said:
Can you try to solve the problem with audio problem with hdmi output with your kernel?
Inviato dal mio Transformer TF101 con Tapatalk 2
Click to expand...
Click to collapse
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
K900 said:
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
Click to expand...
Click to collapse
The voodoo beta or pre-alpha (or whatever it is called) for ICS works just fine on JB aokp, aosp or cm10 based ROMs that I've tried, as long as you own the paid Voodoo Plus license. No kernel support needed by design.
K900 said:
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
Click to expand...
Click to collapse
good, i hope you can work together for solve this big problem ;D
Inviato dal mio Transformer TF101 con Tapatalk 2
sidneyk said:
The voodoo beta or pre-alpha (or whatever it is called) for ICS works just fine on JB aokp, aosp or cm10 based ROMs that I've tried, as long as you own the paid Voodoo Plus license. No kernel support needed by design.
Click to expand...
Click to collapse
The beta app just turns voodoo sound on but it doesn't have any features though, and it doesn't seem to go anywhere unfortunately.
I've paid for the licence myself, but in EOS3 the beta app is not even able to map the analog gain with the volume slider anymore in the latest versions.
If you get a compatible kernel you can simply use the regular Voodoo app that works fine and has all the features.
You will also benefit from the voodoo market app updates as it seems Supercurio is still updating that one at least.
timduru said:
Yes, for the 1st kernel I posted, the base is EOS3 #56 Roach's kernel.
I see that you are using Guevor V23 kernel, I'm currently trying to get his #696 to compile with Voodoo sound, I'll post it too when I'm done if you prefer to wait for that one
Click to expand...
Click to collapse
Looking foward to it I flashed this kernel either wayz
timduru said:
The beta app just turns voodoo sound on but it doesn't have any features though, and it doesn't seem to go anywhere unfortunately.
I've paid for the licence myself, but in EOS3 the beta app is not even able to map the analog gain with the volume slider anymore in the latest versions.
If you get a compatible kernel you can simply use the regular Voodoo app that works fine and has all the features.
You will also benefit from the voodoo market app updates as it seems Supercurio is still updating that one at least.
Click to expand...
Click to collapse
I'm not knocking your work or anything, good to see things progress, as long as you have supercurio's blessing. He got mad at me for posting a link to the app on my dropbox trying to help someone out. I was just saying that the ICS app w/license works on JB seemingly the same as it does on ICS, lacking the same features it lacked there. Still, it does improve the sound if you already own the license. I see that supercurio posted that he is going to update the market app (bug) and also update the beta app soon.
sidneyk said:
I'm not knocking your work or anything, good to see things progress, as long as you have supercurio's blessing. He got mad at me for posting a link to the app on my dropbox trying to help someone out. I was just saying that the ICS app w/license works on JB seemingly the same as it does on ICS, lacking the same features it lacked there. Still, it does improve the sound if you already own the license. I see that supercurio posted that he is going to update the market app (bug) and also update the beta app soon.
Click to expand...
Click to collapse
No offense taken
I just wanted to add precisions for those who've not tried the beta app yet, that way they know what to expect.
As for the kernel well, I just did it the way supercurio wanted it to work and how it was working previously, so I don't see why there would be a problem:
supercurio said:
Free version requires a kernel implementing Voodoo sound GPL patches as you'll find plenty on XDA.
Click to expand...
Click to collapse
And well you can still buy the licence even if you have a kernel supporting voodoo, voodoo is definitely a great sound enhancement for the TF101, so it's a good move to thanks supercurio for bringing it originally too
First post updated with Guevor's JB #696 kernel voodoo support.
I've also added a Generic 2.6.39.x kernel enabler.
Depending on your rom and kernel it *might* work.
It might actually work for ICS roms too if they use 2.6.39 kernels...
Please report the rom - kernels combinations that are working with it.
See 1st post for updated instructions.
alizafar said:
Please make it compatible with the rayman 33 asop jellybean build!!
Click to expand...
Click to collapse
Try the generic enabler and report
It *should* work, unless Rayman has made major changes to the tegra sound files.
Generic enabler report: running ARHD 3.5.1 with stock kernel..... voodoo-sound module does not load with provided script. Changing the init script commandline to "insmod /system/lib/modules/voodoo-sound.ko" the module loads at boot and the old app works fine. Thanks for this.
Sent from my Transformer TF101 using xda premium
OK, so I flashed the voodoo enabled guevor JB #696 kernel on eos3. It didn't really change anything with the beta app and license setup, other than loading the additional module, sound and control were the same. But, it did let me update to the latest market app and now I don't have to keep dismissing the notification about an update. A few more control settings than the ICS app. Looks pretty good. Thanks. I also reflashed DSP Manager from the Revolver thread which gives pretty good control and results for shaping the resultant sound further.
bkmo said:
Generic enabler report: running ARHD 3.5.1 with stock kernel..... voodoo-sound module does not load with provided script. Changing the init script commandline to "insmod /system/lib/modules/voodoo-sound.ko" the module loads at boot and the old app works fine. Thanks for this.
Click to expand...
Click to collapse
Ah good news then, thanks for the info
That means that it's working with ICS roms too, which is good
I've updated the Generic enabler zip in the first post.
Do you mind retesting it to make sure it works with ARHD too now ?
Using insmod is definitely better, and should be more compatible with the different roms.
The default android one lacks the -f option though, but it shouldn't be too much of a problem unless the kernel is of too different version and uses the module magic version.
sidneyk said:
OK, so I flashed the voodoo enabled guevor JB #696 kernel on eos3. It didn't really change anything with the beta app and license setup, other than loading the additional module, sound and control were the same. But, it did let me update to the latest market app and now I don't have to keep dismissing the notification about an update. A few more control settings than the ICS app. Looks pretty good. Thanks. I also reflashed DSP Manager from the Revolver thread which gives pretty good control and results for shaping the resultant sound further.
Click to expand...
Click to collapse
Okie, sound good
First off, here is the github
https://github.com/pio-masaki/at100-kernel.git
Everything I do for this kernel is done there.
Now that's out of the way, here are some highlights:
Beginning of OC code (yes, an OC ICS kernel)
Added a slew of governors for your choosing
Added a couple i/o schedulers
Slight CFLAG tweaking
This is a work in progress!
If you have issues feel free to report, but this is my first ever kernel project, and it may take some time for me to address them!
Dos and Dont's in this thread:
No flaming, please. If someone asks a question thats been asked before, simply remind them and if you would, link the post or thread containing the answer. Replies like "Use search" don't help at all. Saying "Next time, use the search, the information is here" is of course what I would like to see. XDA will be better for this.
No ETAs! I can not, and will not, make any promises on when I can fix, build, or otherwise even think about this kernel, or any rom, period. Asking for ETAs, even politely, will either go unanswered, or reminded of this note.
Issue reporting: I always welcome issue reports, of course, however keep in mind, the point made above is also covering this, I may not have time to address an issue immediatly, though I will try to post back and acknowledge that I have seen the issue, or to ask further questions. Please include as much information as possible, settings for speed, governor, IO, profiles in use for screen off (which I advise against), cpu control app in use, etc. Dmesg would be nice as well, use pastebin, we don't want to see an 8K line post of a log
Changelog:
Experimental V0.1 10-02-12
First "release" for testing. This is internal build 8, and from this point on, will be labeled and numbered as releases, IE if this does ok, next will be Alpha 1, or experimental V0.2, etc.
Added OC code
Experimental V0.2 10-05.12
Second release for testing. Does now include the CODE for voltage control, but is not enabled yet. I didn't enable it to help prevent issues with instabilities from UV being confused with kernel issues. GPU OC is active, 320/400 MHz 2D/3D. Does not play well with ICS, CM10 use only.
Experimental V0.3 10-06-12
Rewrote alot of the upper end speed/voltage/timing code from 1.508 to 1.472, VT, haptic feedback fix? Proved unstable to the point of being unusable. Pulled.
Stable V0.4 10-06-12 "Caspar"
Reverted to V0.1 OC code after the disaster of V0.3. Left out voltage control code, implemented GPU OC as previous in V0.2, VT is enabled, possible haptic fix (not likely). Governors and IO schedulers should remain as before, min/max settings should remain as before. 1.5 is likely still broken.
Experimental V0.5e "Melchoir" 10-18-12 ICS only
All new CPU Speed tables, overall max is lowered from 1.5 which froze to 1.478, and more speeds in between. Those who used the Shiva Kernel will be familiar with the speed range. GPU OC is bumped up 20mhz in 2D/3D. SmartassV2 code added. The kernel has branched since V0.4 and is now a JB and an ICS specific design, one doesn't work for the other anymore, sorry to say. "Melchoir" is the ICS branch kernel, "Balthesaur" is the JB branch kernel which is included in the CM10/Kuroikaze builds.
"Melchoir" V2.4 ICS
Experimental support of CIFS and slight config changes to maybe improve kernel performance. Branch from "Caspar" and includes speeds, governors, IO schedulers and any previous bugs. 1.5Ghz is likely still broken.
"Balthesaur" V2.75 Linaro JB NON OC
Experimental fixes for ExFat corruption issues.
No CPU or GPU OC
Built with Linaro 4.7 toolchain with some optimizing tags turned on
Retains Governors and IO Schedulers from the OC version
Instructions
Download the zip from the link given below
Boot into CWM
Wipe cache
Wipe dalvik cache
Install from zip
Install the kernel zip
Reboot
First boot will take longer as the caches are being rebuilt
Let kernel settle for 10 minutes
Reboot
Let kernel settle for 5 minutes
Begin normal usage and setting up
System Tuner has been reported to work with great success.
Downloads
Experimental OC 1 | Mirror
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.2
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing. Only for CM10.
Experimental V0.3
*note* completely unstable, pulled.
Stable V0.4 "Caspar" ICS
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.5e "Melchoir" ICS
*note* does not boot. See change log for information. ICS only kernel. Please have V0.4 zip handy in case this kernel goes ballistic or doesn't boot, etc.
Experimental V2.4 "Melchoir" ICS
*note* likely retains the 1.5GHz lockup issue.
Balthesaur V2.75 Linaro No OC JB ONLY
Non OC kernel by request. Built with Linaro and current 2.75 source. For use with Jellybean ROMs only. Retains IO Schedulers and Governors, just no CPU or GPU overclock at all. Possibly includes fixes for exfat corruption (planned for U6, but may as well)
Revert kernel
Favum ICS kernel | Mirror
Use this in CWM, same as before, to restore the boot.img and modules for Favum ICS, it may work for other Official based ICS, may not, untested.
Notes and Updates
Mirrors added, V0.1 initial release
V0.2: GPU OC 320/400 MHz 2D/3D. Does not play well with ICS, use only with CM10.
Kernel naming and what they mean:
As the kernel development for Jellybean gained momentum, changes to the kernel source and drivers made the kernel no longer compatible with BOTH ICS and JB, so a new branch needed to be built, one for each android version.
Caspar = The trunk kernel, the first base which all other kernels are built from, contains the original OC settings, governors and schedulers, but not much else, pretty stock.
Melchoir = The First branch, this is for ICS only, and is slightly more updated then the JB kernel, but not by far, is pretty stale development wise while I work on the JB kernel.
Balthesaur = The second branch, this is for JB only, and is the more updated and recent and heavily developed kernel by far.
Each kernel release is still compatible with ANY ROM, however it MUST be of the proper android version, Meclchoir should be flashed only to ICS and Balthesaur should only be flashed to JB. Caspar, should you choose to use it, is ICS only as well.
Do not flash these to other android versions, including Honey Comb, they may boot but they will certainly not function correctly.
FAQ
Q: How does this work with any ROM?
A: Installs by taking apart the current boot image, replacing the kernel binary, repacking then reflashing the boot image, and copies the matching modules into your system/lib folder. It keeps the existing ramdisk, which is why it works in between both ICS and JB.
Q: Where did you get your source changes from?
A: Source changes are coming from ezTerry and Godmachine, with guidance from Godmachine. Changes by ezTerry may come from other places, however I can not verify that, and its from his github.
Q: Is this included in any ROM?
A: Yes, this kernel is included with my CM10 builds, including Kuroikaze-Thrive
Thanks go out to:
First off, godmachine / linux society! We've had our spats (rather, I've had mine) however his guidance made this possible.
ezTerry: for giving us the first modded Acer Iconia kernels, also basing some of this work on his work on ezT20 kernel.
Da-pharoah for as always encouraging my work and to try new things.
tybar over at thriveforums.org (he may also be here?) for his work on CM10 and supplying the initial source this began with.
The rest of the guys pitching in over there!
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
wigginst said:
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
That depends on the ROM being used so no, I hadn't planned on it. I probably could but its per ROM which is quite a few lol
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Was just thinking of a backup in case. Flashed it to favum and letting it settle right now.
Sent from my PG86100 using Tapatalk 2
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Could you make a revert for his darkside ROM? Sorry for being a pain
Sent from my AT100 using xda app-developers app
stevie13.xo said:
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Sent from my AT100 using xda app-developers app
Click to expand...
Click to collapse
Yeah unless something is different with the kernel binary as well, which I doubt, it shouldnt cause a problem.
As far as I know its the first kernel from source for ics so I don't think any issues will come up.
Edit: I'll try to get a revert zip up for dark side as well, the favum won't work, different ramdisk I think.
Sent from my Galaxy Nexus using Tapatalk 2
Are u saying I can use this kernel on my phone or some specific phone only?
ramoneC said:
Are u saying I can use this kernel on my phone or some specific phone only?
Click to expand...
Click to collapse
For the device this forum is for? In other words its for the Toshiba thrive 10" tablet. Flashing this on anything else can lead to no boots or even bricks. Its for any ROM, not device.
Sent from my Galaxy Nexus using Tapatalk 2
I nearly was going to brick my phone /: maybe not cos your updater-script might have been aborted but the main thing was I could not download it because of some sqlite error
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
ramoneC said:
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
Click to expand...
Click to collapse
Generally speaking, no. What device are you talking about?
Sent from my Galaxy Nexus using Tapatalk 2
old galaxy s5830 < wont matter if it bricked
ramoneC said:
old galaxy s5830 < wont matter if it bricked
Click to expand...
Click to collapse
This kernel won't flash let alone boot on that lol
Sent from my Galaxy Nexus using Tapatalk 2
I have decided to buy googles phone henceforth so I wont have to worry about updating
stevie13.xo said:
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Click to expand...
Click to collapse
Mirrors are up.