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.
Related
***Explaination***:
I, as many of us have, been using Toasts #89 Overclocked kernel since it's inception. I have been thrilled with it's performance, and that our community has produced kernel source code before one was avaliable to us from HTC. Thats quite impressive
The only cons with this kernel that I have found are:
1: Would occasionally (20% of the time?) get a Force Close when a phone call is coming in, resulting in the phone being borked, and me having to reboot the phone.
As many of you have noticed, toast incorporated a script into the kernel that makes it more likely to do this on reception of a call from your lover. Yes, this is a proven fact and can easily cause problems![/sarcasm]
2: The Application "WiFi Tether for Root Users" would start properly, and would share the internet connection over wifi as intended, but would hardlock the phone when you tried to stop the tether, requiring a battery pull to get the phone going again.
So in comes DarchDroid. I tried out darchdroid 2.6.4, and even tough it was an overclocked rom, I experienced NO force closes on phone calls, and a flawlessly working WiFi Tether.
I felt that both the problems above must be caused by the kernels, because I had never experienced them when using stock HTC kernel. So I thought it might be possible to use Darch's Kernel from 2.6.4(2.6.5 broke WiFi Tether), in a Sense rom. At the time I was using IceHoneyBun(from androincentral), after trying to make a update.zip myself using parts from darchs rom and getting nothing but boot loops, PMs back and forth with Darchstar, and Beezy(cooker of HoneyBun roms), Beezy posted a flashable zip to successfully use Darch's Kernel on HoneyBun. It worked! No phone FC, and working Wifi tether. Many people who use Toasts #89 experience the FC on incoming call, and everyone using it experiences hardlock on wifi tether end. So we thought we should share the fix, and make zips for Fresh and Damage based roms as well.
Enough jibber jabber, on the the good stuff!!!!
IMPORTANT READ THIS
Due to the folder structure for the .ko modules being different between the stock, the v4, vUV, and vUV2, you MUST run this remover to erase /system/lib/modules/* . Some of the zips below create a folder inside /modules to put the ramzswap.ko. If you flash the newest vUV 2 it puts it directly in /modules, and will not override the /modules/*/ramzswaps.ko, leaving you with 2 ramzswaps.ko. To avoid any conflicts or bugs, I am going to suggest running the remover zip before flashing ANY of the zips below. Simply put the zip on your SDcard, flash it, then flash the kernel of your choice.
http://www.4shared.com/file/mvUNHgqJ/ModuleRemover.html
DO NOT FLASH WITHOUT READING INSTRUCTIONS
Code:
INSTRUCTIONS:
1. Place zip kernel zip file and module remover zip file on root of SDcard
2. Boot into recovery
3. Perform Nandroid+EXT backup
[size=3][B]4. Flash ModuleRemover.zip[/B][/size]
5. Flash your kernel of choice
AS ALWAYS NANDROID FIRST, AND POST IF YOU HAVE PROBLEMS!
Code:
[B][size=4]vUV2 Kernel[/b][/size] 1.2v
HTC Synaptics driver! (thank you Darchstar!)
CPU is undervolted.
All versions overclockable using an app to 768.
Uses 2.6.29-cyanogenmod - [email protected] #6 kernel
With custom ramdisk for each rom/mod
[B][COLOR="blue"]Standard
Uses stock 2.27.651.6 RUU Ramdisk with apps2sd support added
Compatible with: Nfinitefx45's 2.27.651.6, ZenHeroFX, Fresh Rom 2.1.1/2.1.2/2.3.3[/COLOR][/B]
[URL="http://www.4shared.com/file/PgbKNp_0/Standard_vUV2_691.html"]Darchkernel vUV2 691mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/Ojlxi-lD/Standard_vUV2_710.html"]Darchkernel vUV2 710mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/rlOXyLcr/Standard_vUV2_768.html"]Darchkernel vUV2 768mhz for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/tcpFg_TS/Standard_vUV2_691_M.html"]Darchkernel vUV2 691mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/t5-qeBkS/Standard_vUV2_710_M.html"]Darchkernel vUV2 710mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/6mfmPmzf/Standard_vUV2_768_M.html"]Darchkernel vUV2 768mhz with freememkiller tweak for roms using 2.1 RUU ramdisk[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[B][COLOR="blue"]HoneyBun[/COLOR][/B]
[URL="http://www.4shared.com/file/31GuJx7Z/Honeybun_vUV2_691.html"]Darchkernel vUV2 691mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/YbYt2lR4/Honeybun_vUV2_710.html"]Darchkernel vUV2 710mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/CeIa3x24/Honeybun_vUV2_768.html"]Darchkernel vUV2 768mhz for Honeybun[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[B][COLOR="blue"]Damage Control[/COLOR][/B](has ramdisk from 2.09,will work in 2.08 and 2.09)
[URL="http://www.4shared.com/file/pW0_QiMf/Damage_vUV2_691.html"]Darchkernel vUV2 691mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/UkiGynor/Damage_vUV2_710.html"]Darchkernel vUV2 710mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
[URL="http://www.4shared.com/file/Y4EceZgS/Damage_vUV2_768.html"]Darchkernel vUV2 768mhz for damagecontrol based roms[/URL][color=orange]***BUGS IN zIMAGE FREEMEMKILLER***[/color]
KNOW ISSUES WITH UV v2 KERNEL
*FREEMEMKILLER BUG IN ZIMAGE, MAY EXPERIENCE MEMORY LEAK, INTERMITTEN LAG, AND LOCKUPS.
*Audio pop can be head through headphones when music/sound first starts
*You can select 787mhz using an OC app, but this frequency setting is broken,
768 is the highest frequency that works.
Code:
[B][size=4]v4 Kernel[/b][/size] 1.325v
HTC Synaptics Driver, Standard CPU Voltage.
All versions overclockable using an app to 768.
Uses Darchstar 2.6.34-GoDmOdE-Darchshizz-OC
[email protected]#4 kernel
With custom ramdisk for each rom/mod
**BUGS FOUND IN FREE MEMORY TWEAK VERSION OF V4, RECOMMEND YOU USE vUV KERNEL INSTEAD**
[B][COLOR="blue"]Fresh 2.0d[/COLOR][/B]
[URL="http://www.4shared.com/file/OSUauZsW/Fresh20b_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Fresh 2.0d[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/0QiLL5Ru/Fresh20b_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Fresh 2.0d[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]Infinitefx45's 2.27.651.6[/COLOR][/B]
[URL="http://www.4shared.com/file/tTFeHUJJ/Infinitefx_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/Pman261O/Infinitefx_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/snpFERGY/Nfinitefx45_v4_691.html"]DarchKernelv4 691mhz For Nfinitefx45[/URL][COLOR="SeaGreen"][B]**WORKING**[/COLOR][/b]
[URL="http://www.4shared.com/file/P3TciJjT/Nfinitefx45_v4_691_M.html"]DarchKernelv4 691mhz with Free Memory Tweak For Nfinitefx45[/URL][COLOR="seagreen"][B]**WORKING FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]HoneyBun[/COLOR][/B]
[URL="http://www.4shared.com/file/4N0ggqZ8/HoneyBun_v4_768.html"]DarchKernelv4 768mhz for Honeybun[/URL][COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[URL="http://www.4shared.com/file/2vcrF2fJ/HoneyBun_v4_710.html"]DarchKernelv4 710mhz for Honeybun[/URL][COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[B][COLOR="blue"]Fresh 2.1.1/2.1.2/2.3.3[/COLOR][/B]
[URL="http://www.4shared.com/file/yOuAlojE/Fresh21_v4_768_M.html"]DarchKernelv4 768mhz with Free Memory Tweak For Fresh 2.1.1/2.1.2/2.3.3[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[URL="http://www.4shared.com/file/z5TRFGnd/Fresh21_v4_710_M.html"]DarchKernelv4 710mhz with Free Memory Tweak For Fresh 2.1.1/2.1.2/2.3.3[/URL] [COLOR="orange"][B]**POSSIBLE BUGS WITH FREEMEMKILLER TWEAK**[/COLOR][/B]
[B][COLOR="blue"]Damage Control[/COLOR][/B](has ramdisk from 2.09,will work in 2.08 and 2.09)
[URL="http://www.4shared.com/file/AzNynVNU/Damage_v4_768.html"]DarchKernelv4 768mhz for DamageControl[/URL] [COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
[URL="http://www.4shared.com/file/hiYH5bQz/Damage_v4_710.html"]DarchKernelv4 710mhz for DamageControl[/URL] [COLOR="SeaGreen"][B]**TESTED**[/COLOR][/B]
KNOW ISSUES WITH UV v2 KERNEL
*Audio pop can be head through headphones when music/sound first starts
*Freememkiller versions may be buggy due to a typo that was copy/pasted into all v4 kernels,need to redo when I get an hour or so. I should note that I haven't actually seen this problem manifest in the real world, though I think it could.
Camera Fix(thanks infinitefx45!)
Camera/Media Fix**Should work on most De-Odexed roms that DO NOT use friendstream, PM me if this boot loops your phone, and I'll edit the zip for your rom. NANDROID FIRST**, **This will revert your htcdialer to an unthemed version if you are running a theme or a themed rom, you have been warned!**
Code:
[B][size=4]CHANGE LOG[/size][/b]
[b]vUV 2[/b]
*Build from newer kernel source.
*Added HTC synaptics driver (Thank you Darchstar)
*Consolidated Nfinitefx45's 2.27.651.6 stock, ZenheroFX, and Fresh into one category. Not 100% sure if it will work on fresh, if not I'll add in the fresh rom category again.
[b]vUV[/b]
*Undervolted CPU
*Fixed my incorrect settings in ramdisks that sometimes caused CPU to drop to 19mhz.
Bug is present in all V4 kernels.(use SETCPU/Oc widget and
manually set the frequency in the V4 kernels to avoid this!!)
*Fixed a mistake I made when performing freemem tweak on the V4 kernels,
those who used the V4 kernels with freemem killer tweak that experienced
lag/slowness/stuff closing when it shouldn't/, should have no problems with
the vUV kernels with freemem killer tweak.
[b]v4[/b]
*Added 710mhz default, and 768 mhz default versions(both clockable to 768 using an OC app)
*Added separate update.zips for Fresh, Damage, Honeybun, and Infinitefx
in an attempt to solve problems with failed boots on infinitefx rom, and to
allow for lowmem tweaks in fresh roms without effecting damage roms!
*Tweaked lowmemkiller settings for Fresh and Infinitefx roms
(Honeybun is already using a tweak; gumbo.sh. and
Damage control has lowmemkiller settings accessible in Dconfig)
*A Fresh 2.0b version, just for fun!(I was testing with Fresh 2.0d and had
problems trying to use the ramdisk from fresh 2.1.2
[b]v3[/b]
*Fixed Wifi, was broken in v2!
[b]v2[/b]
*Fixed for touchscreen lag
*Fixed improper auto detect maximum frequency
(reporting as 787 while actually only being 768)
[b]v1[/b]
*Initial release
________________________________________________________________
****Many thanks to Darchstar for compiling the kernel, Toastcfh for his kernel source, Beezy420(from android central) and Jus10o for creating the flashable ZIPS with the proper ramdisks, and everyone envolved in testing, or who gave any input!!****
________________________________________________________________
Links:
Original Thread at AndroidCentral
DarchDroid, the rom the kernel was pulled from
Excellent guide on Kernel Compiling
Toast's Kernel Source =D
urushiol said:
I just realized I don't have time to finish this post atm, I'll have to do it when I get off work, but this makes for a great teaser!
so I'll just say.......
COMING SOON(tonight)
****Many thanks to Darchstar for compiling the kernel, Toast for his kernel source, Beezy420 from android central for creating the flashable ZIPS with the proper ramdisks to work with fresh and damage!****
Click to expand...
Click to collapse
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
At least that's what I interpreted from the thread at Android Central
.....
Zen also moved away from #89 and BFS because of the onslaught of problems that hampered his ROM with it. He's back at #65 too.
I think we're better off either waiting for Toast to fix up the kernel source (and using #65 in the mean time) or fixing it ourselves. But if this is Darch's kernel that you're coupling the Ramdisks with, you might end up with more problems than what you're trying to fix(but who knows, good luck).
Decad3nce said:
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
At least that's what I interpreted from the thread at Android Central
.....
Zen also moved away from #89 and BFS because of the onslaught of problems that hampered his ROM with it. He's back at #65 too.
I think we're better off either waiting for Toast to fix up the kernel source (and using #65 in the mean time) or fixing it ourselves. But if this is Darch's kernel that you're coupling the Ramdisks with, you might end up with more problems than what you're trying to fix(but who knows, good luck).
Click to expand...
Click to collapse
So far so good. Its only untested on DamageControl.
**UPDATED FIRST POST WITH LINKS TO DOWNLOAD AND INFORMATION**
Can I flash this over the DC2.09 with #89 already on it? or will I have to wipe? I want to test it
Also is there a way to remove the original OC flash or someway to leave me back to stock speeds?
overthinkingme said:
Can I flash this over the DC2.09 with #89 already on it? or will I have to wipe? I want to test it
Also is there a way to remove the original OC flash or someway to leave me back to stock speeds?
Click to expand...
Click to collapse
Simply Nandroid first (incase the **** hits the fan), and flash the zip posted above for damage roms =D. No need to wipe.
Someone could build you an Update.zip using damages rom zip to restore the original kernel, if you wanted to go back to that.
Good luck, and let me know how it goes =D.
I'm using the rom posted by nfinitefx45 with DB-F-OC-Boot(fresh), testing with good results
does this also fix the GPS not locking on?
or is that just me?
i've tried 4 different OC roms and each of them i can't lock onto my position on GPS *closest is within 1000m*
on non OC roms it locks on to even what room i'm in in my house.
151jcolon said:
I'm using the rom posted by nfinitefx45 with DB-F-OC-Boot(fresh), testing with good results
Click to expand...
Click to collapse
Excellent!
gonzoangel said:
does this also fix the GPS not locking on?
or is that just me?
i've tried 4 different OC roms and each of them i can't lock onto my position on GPS *closest is within 1000m*
on non OC roms it locks on to even what room i'm in in my house.
Click to expand...
Click to collapse
I know this was common on early DarchDroid Builds, but has since been resolved, I never knew of the issue on sense based roms. But on a side note, I can say the GPS works great for me on honeybun+this kernel as well as fresh 2.1.2+this kernel.
what OC roms have you tried gonzoangel?
[FIX][Overclocking Kernel]FIXED force Close on phonecall and lock on wifi tether stop
Flashed the DC one and so far so good
Also using 2.08 based rom for the testing
-------------------------------------
Sent via the XDA Tapatalk App
Flashed over Toast's, tested like crazy trying to provoke FC, and couldn't do it. AMAZING job!!!
Decad3nce said:
So it's just Darch's kernel for Darchdroid coupled with the ramdisk for Fresh/Dama(which are the same)?
Click to expand...
Click to collapse
Its my kernel, but not the same found in darchdroid. I compiled specifically for this purpose as the OP requested it. It'll only work with sensui roms as it uses the htc touch synaptics source.
darchstar said:
Its my kernel, but not the same found in darchdroid. I compiled specifically for this purpose as the OP requested it. It'll only work with sensui roms as it uses the htc touch synaptics source.
Click to expand...
Click to collapse
Ah nvm then. I posted just based on the thread at Android Central(before the explanation). Was wondering about the synaptic drivers but wasn't sure who did the edits. Good stuff!
Just flashed and tested on DamageControl 2.09 - works great! TetherWiFi stops without causing my phone to hang - not sure about the phone call problem, as it only happened twice to me. Other than that, great job!
Decad3nce said:
Ah nvm then. I posted just based on the thread at Android Central(before the explanation). Was wondering about the synaptic drivers but wasn't sure who did the edits. Good stuff!
Click to expand...
Click to collapse
Lol, the explanation over at android central was terrible. That post was just like "here u go, a kernel. it may seem like i did all the work. lets just leave it at that"
I needed this! Thank you
darchstar said:
Lol, the explanation over at android central was terrible. That post was just like "here u go, a kernel. it may seem like i did all the work. lets just leave it at that"
Click to expand...
Click to collapse
Ha yeah. I tried my best to interpret it but was completely lost when I tried to piece everything together with my past knowledge about the differences between your kernel and toasts(notice the 15 edits on my first post LOL). So can we safely blame BFS(or at least its implementation)?
Called my phone more than 20 times in various states with no issues. Sick work!
Does this do anything for the occasional loss of a data connection issue?
http://androidforums.com/sprint-htc-hero/101113-losing-data-connection-2-1-update.html
thx.
very nice work.
ronnienyc said:
Does this do anything for the occasional loss of a data connection issue?
http://androidforums.com/sprint-htc-hero/101113-losing-data-connection-2-1-update.html
thx.
Click to expand...
Click to collapse
I can't comment on this issue, because I have not experienced data connection drops with the sprint kernel, toasts kernel #89, or this kernel.
Be sure your on the newest PRL, and have updated your profile. Do you have mobile data always on enabled or disabled?
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!
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
******************Sources up at https://github.com/AKToronto/Canuck ********************************
****currently working off the testing branch I created****************
Hi folks,
Im posting this kernel because there might be a number of people who want to use a custom CM10 base ROM and just want to get some better battery life. Basically its for someone who would be interested in a kernel synced with the latest CM10 sources for 4.1.2 JB and who doesn't want to go to CM10.1 ROMS yet until they become more stable.
Huge thanks goes out to Zarboz as well as ShowP1984
ShowP1984 and Zarboz are real kernel masters. I am still just a simple padawan learner, lol.
Most of the custom source code for this kernel is either cherry-picked, merged or inspired by their work.
For more information on custom kernel settings, governors, schedulers, modules, etc, please check out:
http://forum.xda-developers.com/showthread.php?t=1369817
Please let me know if anything doesn't work! ie reboots or other programs not working. Give the kernel some time to settle too before reporting.
And dont blame me if your device gets borked, lol. "Insert standard disclaimer here"
v1.0 Canuck Kernel
-CM10 JB Kernel sources synced 3.0.61 linux
-Governors included (and code cleaned up a bit) - brazilianwax, intellidemand, SavagedZen, interactiveX, smartass, smartassV2, lagfree, interactive, conservative, userspace, powersave, Lionheart, ondemand, performance (originally from klin's source)
-mpdecision using ShowP's code from Zarboz's AOZP source added
-Force MHL @720p60hz (also from Zarboz's AOZP)
-regular 4.6 eabi toolchains for now
v1.1
Synced with latest 3.0.62 linux
**GPS appears to be fixed and locking properly
v1.2
-Added Undervolting and Overclocking to 1.89gz (1.89 seems the most stable for folks) (taken from Zarboz Beastmode Bricked sources)
v1.3
-various fixes to undervolting, gpu overclock and to default on demand governor (also removed 2 phase on it for now).
v1.4
-removed some more problematic governors (that I also noticed were not compiled in Beastmode)
-enabled two phase ondemand
-added badass governor and cleaned up some of the badass code so that default phase frequency settings stick
v1.5
-thermald added to userspace (allows user to configure settings for when the device gets hot! ie lower cpu clock speed, etc)
-added lower default values to badass governor
**an experimental 2.1 ghz overclock version is also compiled, but that is experimental***
v1.6
-Wheatley governor added (likely the last governor I will add)
-enabled xz compression
-Fixed GPU OC so that settings stick (i recommend 266 for 2d and 320 or 400 for 3d)
-both 1.89 and 2.1 ghz versions added 2.1 ghz seems stable, just make sure you are undervolting correctly (dont undervolt a lot at the higher frequencies)
v2.0 ***Huge update thanks to Zarboz
-Rebuilt with Linaro 4.7 toolchains with -O3 compression flags
-Updated ThermalD and mpdecision source code (hot off the press stuff here!)
-Latest sweep 2 wake added
-various other fixes
v2.1
-Real -O3 compression this time ( on v2.0 it was really only -O compression)
-updated to latest CM10 sources and 3.0.63 linux
v2.2
-Added force mhl to ville defconfig for compile (feel free to test)
-Synced with 3.0.66 linux sources
v2.3
-Faux tweaked intellidemand
-Dynamic fsync enabled (by faux)
-Fastcharge enabled
v2.4
-Removed faux tweaked intellidemand (I didnt like the faux tweaks personally. Im just not sure that governors that try tie in to GPU clocks have
the right default settings to work well on the One S, regular intellidemand could be combined with other the other governors and not introduce instability. I had issues with tweaked plus smartass v2 for example)
-rebuilt using rmbq's cortex-a15 optimized toolchain (this seemed pretty cool, and I thought I would try it out. Seems like the device boots faster now too)
To use sweep to wake, when your screen is off, put your finger on the back button, then sweep all the way to the right in one motion. It works best when you do it fast. To turn the screen off, sweep in the opposite direction.
Compatible ROMs currently include (all CM10 base, not CM10.1):
-Latest CM10 nightlies http://goo.im/devs/cm/ville/nightly
-Latest PAC Man ROM
-Latest AOKP http://forum.xda-developers.com/showthread.php?t=2141549
-Latest Dark Jelly (I think)
-Any other CM10 AOSP ROM that is synced with the latest jellybean branch (not the old jellybean-stable branch) of https://github.com/CyanogenMod/android_kernel_htc_msm8960
Install instructions:
1. Navigate to your /system/bin folder and rename the file mpdecision to something else like mpdec_backup (IMPORTANT)
2. Navigate to your /system/bin folder and rename the file thermald to something else like therm_backup (IMPORTANT)
2. Fastboot flash the boot image from your bootloader
*step one and two is needed because the kernel uses its own mpdecision and thermald controls and the ones included in your ROM are not needed and can only cause problems.
DOWNLOAD LOCATION:
http://www.androidfilehost.com/?a=show&w=files&flid=3192
****BE CAREFUL WITH UNDERVOLTING... Just want to give a fair warning... Undervolting too much, especially below 900, etc on the low end is not recomended. Read up on undervolting before doing too much more. In fact, if you are experienceing issues, try increasing the voltages.
Also recommend using kernel tuner to tweak (found in the app store), following Zarboz's suggestion. It's a good program and let's you set governors for individual cpus, tweak governors, mpdecision, gpu overclock and thermald, and settings tend to stick well.
hello there i was just going to tell you i fastbooted the kernel and it does not go past the splash screen.
Nerd019 said:
hello there i was just going to tell you i fastbooted the kernel and it does not go past the splash screen.
Click to expand...
Click to collapse
Interesting. What ROM are you on? Seems to work just fine with latest PAC Man ROM on my HTC One S. Again, not much was edited at all from the CM10 Jelly Bean source. If stock AOSP JB doesnt boot for you, then neither would this. But it should work just fine on ROMs like JellyBam and PACMan, etc, etc... If it still doesnt work I will double check my upload and the boot.img.
Also, not sure if legacy files from other kernels are causing issues for folks switching over... Using http://forum.xda-developers.com/showthread.php?t=2121584 might help too....
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
I'm on Baked Blackbean 7.1 im actually building the rom as we speak
Sent from my HTC One S using xda app-developers app
Nerd019 said:
I'm on Baked Blackbean 7.1 im actually building the rom as we speak
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ahhh theres the answer (I think). I think 7 and 7.1 of your awesome baked ROM already use the CM10.1 base.
This kernel was not built off of the CM10.1 base, but just the straight up CM10 Jellybean. It should work with 4.1.2, but no guaruntees on 4.2.1. Does that make sense?
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
yes it does as well i want to thank you for a new kernel
Sent from my HTC One S using xda app-developers app
AW: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
Always nice to see some new things here in the one s forum.
Gesendet von meinem Nexus 7 mit Tapatalk 2
support mhl ?
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
Good to see a new face around man don't hesitate to reach out if you need anything
And who cares who else is building kernels ate fun
Sent from my HTC One XL using xda app-developers app
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
Very pleased to see this new development after Klin announced his fusion kernel obsolete today!
I have recently switched to a sense based ROM to satisfy my need for custom kernels, but can't wait to switch back to CM10 once you get this up and running.
I will be following this thread closely
Sent from my HTC One S using xda app-developers app
Successful boot on Jellybam 4.1.0! Govs and SIO showing up properly, going to start testing them individually.
For a first step, you've done an awesome job! I'm really looking forward to more releases from you. You have some serious potential. I'd be happy to test anything you need tested!
Edit: Still testing, so far so good. No broken governors!
Protip: Change your title up a bit. Replace "first build" with V1.0 and throw in an [AOSP] to draw attention.
awesome job got it to boot with jellybam 4.1.0.
Everything seemed fine but i couldnt get the Wifi to turn on.
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
Hmm interesting with the wifi... Did you have those issues with the stock CM10 kernel too? Wifi seems to work just fine on PACMan Rom for me and worked when I tried Jellybam too... I wonder if the kernel cleaner app would help you, if you had been flashing lots of other kernels on your Rom build?
Sent from my HTC One S using xda premium
With the latest nightly WiFi works fine. 2 days of use with out any problems . Thanks you for your work
Re: [KERNEL][JB 4.1.2][AKToronto][First build, Feb 3, 2013]
AKToronto said:
Hmm interesting with the wifi... Did you have those issues with the stock CM10 kernel too? Wifi seems to work just fine on PACMan Rom for me and worked when I tried Jellybam too... I wonder if the kernel cleaner app would help you, if you had been flashing lots of other kernels on your Rom build?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I actually only tried out the kernel with the jellybam ROM I had installed already.
kernel cleaner? I'm going to check that out when I have time.
and i did do a couple of flashes before trying out your kernel.
I'm going to try it out on a clean install of jellybam and PAC man and I'll let you know what works for me. thanks for the response
No wifi problems here, it's likely caused by legacy kernel files. Try out the solution in Post #3 before you wipe everything. If that doesn't work, post what HBOOT you're device has.
Very nice. Thanks.
Is there a chance of getting s2w?
Kernel updated. Main update was some cleanup of some code around the governors and adding of kernel based mpdecision. This is mainly off of Zarboz's work and of course ShowP and his awesome mpdecision coding.
I know folks will want sweep to wake and a few other settings too im sure. Those things will come in time. Any other governors that people find useful? I have heard badass can be pretty good too...
Re: [KERNEL][JB 4.1.2][AOSP][Canuck][v1.0][3.0.61 linux]
can i use it on baked rom?
Sent from my HTC One S using xda app-developers app
Nerd019 said:
can i use it on baked rom?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
depends on what version of baked. If your already at CM10.1 or v 4.2.1 of Android then no. You should go for one of the other two new kernels floating around for CM10.1 They look promising.
Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!