Related
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Froyo/sense kernels modified to work with the interface:
http://chad0989.dyndns.org/mirror/toastmod-4.3.4-cfs-havs-sysfs-less-nosbc-universal-signed.zip
http://chad0989.dyndns.org/mirror/toastmod-4.3.4-cfs-havs-sysfs-more-sbc-universal-signed.zip
Is this compatible with sense?
biglilsteve said:
Is this compatible with sense?
Click to expand...
Click to collapse
It should be as long as your kernel supports HAVS + sysfs. Feel free to test and provide feedback, it's greatly appreciated.
Giving it a whirl now! Been waiting for a voltmod or sense!
Won't start up on my device. I know my kernel is a HAVS kernel...not sure how to verify sysfs though...
biglilsteve said:
Won't start up on my device. I know my kernel is a HAVS kernel...not sure how to verify sysfs though...
Click to expand...
Click to collapse
What kernel are you running? Unfortunately I'm not familiar with the selection of kernels for the EVO. If you kernel supports HAVS the developer should be able to easily implement the sysfs interface if he is so willing. You can direct him to the following commit which he can pull a patch from, it will have to be modified because its for the inc, but it should be fairly easily patched in:
https://github.com/Chad0989/android_kernel_common/commit/4625ffe10406626c2a3cbf31236c889395f0e9d4
If the developer doesn't want to add it in, let me know and I will pull his source, add it, and post a build that does support it for you.
Yeah, I figured being an inc developer you wouldn't be too familiar with EVO kernels. I'm using netarchy-toastmod 4.3.4. It's a HAVS sense kernel. Today the developer discontinued support for it since it is a froyo kernel and just about everyone (not me) has moved onto gingerbread...
I'm using myn's Warm TwoPointTwo RLS5 rom
Kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=719763&highlight=netarchy
EDIT: I forgot to say THANK YOU for offering your help and even your willingness to take a shot at adding sysfs to that kernel
Hope this wasnt taken from Vipermod...
Regardless of whether or not it was taken from Vipermod, if it works for sense then it does something Vipermod can't.
Don't get me wrong, I rock Vipermod when I'm running MIUI and love it...but we need a solution like that for sense.
This has absolutely nothing to do with vipermod. In fact I was releasing undervolt scripts before viperboy was. I just stayed incredible only for a long time.
Sent from my ADR6300 using XDA App
workin nice on aosp (cm7) SZ kern thx very convenient
biglilsteve said:
Yeah, I figured being an inc developer you wouldn't be too familiar with EVO kernels. I'm using netarchy-toastmod 4.3.4. It's a HAVS sense kernel. Today the developer discontinued support for it since it is a froyo kernel and just about everyone (not me) has moved onto gingerbread...
I'm using myn's Warm TwoPointTwo RLS5 rom
Kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=719763&highlight=netarchy
EDIT: I forgot to say THANK YOU for offering your help and even your willingness to take a shot at adding sysfs to that kernel
Click to expand...
Click to collapse
Here you go. I'd highly recommend that you nandroid beforehand because I have no device to test it on.
http://www.incredikernel.com/wp-con.../download.php?id=netarchy_sense_havssysfs.zip
Looking forward to trying this out when we get a gb kernel tossed our way.
androidsupra said:
Looking forward to trying this out when we get a gb kernel tossed our way.
Click to expand...
Click to collapse
Shouldn't need one. As far as I can tell, there are gb kernels with havs and sysfs for the evo already.
Sent from my ADR6300 using XDA App
chad0989 said:
Here you go. I'd highly recommend that you nandroid beforehand because I have no device to test it on.
http://www.incredikernel.com/wp-con.../download.php?id=netarchy_sense_havssysfs.zip
Click to expand...
Click to collapse
I tried flashing this (I also run netarchy's latest) sent me into bootloops. I didn't nandroid back but I did have to reflash my kernel to get it to boot up. When I open the app all I get is a black screen. Hope this helps.
Sent from my PC36100 using Tapatalk
mrcrptguy said:
I tried flashing this (I also run netarchy's latest) sent me into bootloops. I didn't nandroid back but I did have to reflash my kernel to get it to boot up. When I open the app all I get is a black screen. Hope this helps.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Try this one:
http://chad0989.dyndns.org/mirror/netarchy_sense_havssysfs-2.zip
FYI on Sense: This probably won't work with 2.3.3 [Gingerbread] *YET* for the following reason:
No source from HTC. No HAVS kernels yet. Known fact that kernels for 2.2 [Froyo] won't work (or don't work well) with 2.3.3 [Gingerbread].
github said:
FYI on Sense: This probably won't work with 2.3.3 [Gingerbread] *YET* for the following reason:
No source from HTC. No HAVS kernels yet. Known fact that kernels for 2.2 [Froyo] won't work (or don't work well) with 2.3.3 [Gingerbread].
Click to expand...
Click to collapse
That's how it is with the inc as well. So at least everyone is on the same page there.
chad0989 said:
Try this one:
http://chad0989.dyndns.org/mirror/netarchy_sense_havssysfs-2.zip
Click to expand...
Click to collapse
Fantastic! This kernel boots and the app runs on myn's Warm TwoPointTwo!
I wish I were more specific on which variant of the kernel I am using:
netarchy-toastmod 4.3.4. cfs havs more sbc
Are you able to implement the sysfs on that variant?
Another question...after setting the voltages, is there a way to actually verify the new voltages have been taken?
biglilsteve said:
Fantastic! This kernel boots and the app runs on myn's Warm TwoPointTwo!
I wish I were more specific on which variant of the kernel I am using:
netarchy-toastmod 4.3.4. cfs havs more sbc
Are you able to implement the sysfs on that variant?
Another question...after setting the voltages, is there a way to actually verify the new voltages have been taken?
Click to expand...
Click to collapse
Open a terminal and type:
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
Alternatively you can just open and then close the app, when the app opens it reads the current voltages and displays them. So if the voltages remain at what you set them too, they took.
Also if you could confirm that the sysfs interface is definitely working for me that would be great. To do this I would like you to set the min and max voltage for whatever max frequency you use to something low and definitely unstable, lets say 1000, click apply (make sure set on boot is unchecked) and load your phone (open a game or something). It should lock up and/or reboot pretty quickly. If it doesn't lock, then the voltages might not actually be being set. In this case, let me know.
I used the most vanilla variant of the kernel, havs, nosbc, if you confirm it working I'll build an sbc version.
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
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.
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!
1. Motivation/overview
This is a kernel for the 2012 Nexus 7 (grouper/tilapia) which sticks as closely as possible to the stock/released kernel sources, while incorporating the features I want from other popular alternative kernels. I've built it because my Nexus 7 3G (tilapia) has trouble with all of the non-stock kernels I've tried -- something causing USB resets in a tight loop. I rebuilt the stock kernel and started adding my favorite features in order to rule out what was causing the problem, but ended up with a kernel I preferred for day-to-day use.
You might like it, too.
Note that there is very little original content in this kernel: see the credits below and the github repository for the sources of the included features.
2. Features
IO Schedulers
bfq
row
SIO
CPU Governors
smartmax
wheatley
Misc
Build with -Os (optimize for size)
GPU overclock
Experimental: remove baseband_xmm_power wakelock
f2fs driver (see note in second post)
ntfs r/w (see note in second post)
CPU voltage control
Mount slave namespace workaround
CPU overclock (against my better judgement).
3. Instructions
This kernel is intended primarily for use with the stock ROM. The first releases (mr1 and a20) were built with a stock ramdisk, and will generally not work on other ROMs. Later releases use an AnyKernel updater and may work on other ROMs. I am only able/willing to test on stock, however, so non-stock users, use at your own risk (even more than usual).
To install, boot into your custom recovery of choice and install one of the zips below. Or use Flashify. Be sure to make a backup with your recovery first.
4. Warning and disclaimer
I am not responsible for any harm caused to you, your tablet, or the integrity of the space-time continuum by this kernel. In the words of the GNU Public License:
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. Downloads
Milestone releases:
mr1: carcosa-kernel-mr1.zip
Alpha releases:
a20: carcosa-kernel-a20.zip
Includes experimental patch removing baseband_xmm_power wakelock.
a22: carcosa-a22-anykernel.zip
Includes changes to governor defaults, ntfs r/w support, and the f2fs driver.
a23: carcosa-a23-anykernel.zip
Includes voltage control (undervolting) interface.
a25: carcosa-kernel-a25.zip carcosa-a25-anykernel.zip
Includes mount slave namespace workaround, CPU overclocking (against my better judgement)
a27: carcosa-a27-anykernel.zip
4.4.3 update
a28: carcosa-a28-anykernel.zip
Remove baseband_xmm_power wakelock again, rather than making it time out.
a29: carcosa-a29-anykernel.zip
Add configurable baseband_xmm_power wakelock timeout
a33: carcosa-a33-lp-anykernel.zip
Lollipop update; adds SIO IO scheduler.
a35: carcosa-a35-lp-anykernel.zip
Lollipop 5.1 update (still works with 5.0.2). Adds hardware acceleration for kernel encryption routines.
6. Source
Sources are on github, which is also your best source for changelogs.
7. Credits
This kernel contains precious little original work -- it builds on the stock kernel release and applies cherry-picked patches from various sources, principally M-Kernel (Metallice) Franco-kernel (Francisco Franco), and Oxydo (Sgt. Meow), but also Faux123, Ezekeel, Maxwen, and many others. My main contributions have been picking the things I wanted, and resolving the occasional hairy merge. I have attempted to maintain the original authorship information in my git logs as much as possible; I apologize for any cases where the attribution of a particular patch has been lost.
Notes
F2FS support
While this kernel (from a22 on) includes the f2fs driver, it does not include any of the ramdisk or init tweaks that you would need to use f2fs. This is because I am not in a position to test f2fs myself. That said, the a22 (and later) kernel installer will not disturb any changes you have already made to your ramdisk or ROM to support f2fs, so if you have already got f2fs working on your device, it should continue to work after installing this kernel. Don't forget to do a nand backup in your recovery before installing, though. Seriously.
NTFS R/W support
This kernel (from a22 on) includes RW support for NTFS. However, in KitKat, NTFS USB drives mounted with StickMount are not writable due to SELinux policy. To write to an NTFS USB drive, you need to (from a root shell) 'setenforce off', then 'setenforce on' when you're done using it. I do not recommend that you put SELinux in permissive mode permanently. It's there for a reason, and this is just a workaround for a policy error in KitKat. The SELinux SetEnforce Toggle app is a convenient way to turn it off and on for this.
Mount slave namespace workaround
Android apps that mount filesystems (e.g. CIFS, Lil'Debi's loopback fs), mount them in a private namespace that is not shared with other apps (as explained by mkasick). There is a rom-based workaround applied in CM-based roms, and probably many others, but not in stock. Instead, I am applying his kernel/ramdisk based workaround. If you are on stock and need this workaround, do not use the anykernel build; use the one with the full disk image.
Configurable baseband_xmm_power wakelock timeout
This is based on work by Sgt. Meow, with some tweaks. It is controlled by the module param /sys/modules/baseband_xmm_power/bb_timeout, which defaults to 10, and represents the time, in 10ths of a second, that the baseband_xmm_power wakelock should be acquired for before timing out. 0 will disable the wakelock completely as in earlier versions of carcosa-kernel. These semantics are not the same as those for the same parameter in Oxydo, so be aware.
-------------------------------------------------------------------------------------------------------
Camilla: You, sir, should unmask.
Stranger: Indeed?
Cassilda: Indeed, it's time. We all have laid aside disguise but you.
Stranger: I wear no mask.
Camilla: (Terrified, aside to Cassilda) No mask? No mask!
– from Act 1, Scene 2 of The King In Yellow
Kernel rocks! Thanks!
bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
jfmcbrayer said:
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
Click to expand...
Click to collapse
I am using the alpha. I run a grouper rom on tilapia and didn't have any wake lock issues.
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
gremlin89 said:
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
Click to expand...
Click to collapse
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Nexus 7 using xda premium
Just flashed mr1 on bshiznit’s stock ROM earlier today. So far it's running nice and smooth. Nice work!
Sent from my Nexus 7 using Tapatalk
pjcanales said:
What ROM are you using?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Aospal
jfmcbrayer said:
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
Click to expand...
Click to collapse
Oh that would be really great. Is it easy to build such a rom?
gremlin89 said:
Oh that would be really great. Is it easy to build such a rom?
Click to expand...
Click to collapse
Not a ROM, just an updater zip. In principle, it should be easy. But somehow, I've never got it to work.
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
sengst said:
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
Click to expand...
Click to collapse
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
Just a question
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
jfmcbrayer said:
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
Click to expand...
Click to collapse
You are right: tilapia aosp and your a20 kernel.
ispukan said:
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
Click to expand...
Click to collapse
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
jfmcbrayer said:
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
Click to expand...
Click to collapse
So i can install what ever i want there is now difference for wifi only model ?
ispukan said:
So i can install what ever i want there is now difference for wifi only model ?
Click to expand...
Click to collapse
Right; you can run either on a Wi-Fi only (grouper) device, but the changes are only relevant to tilapia.
Hi, can I use this kernel on PA 4.1 beta on my tilapia? Currently using the Franco r77 kernel and still get massive baseband wakelocks! If this kernel doesn't work on the said ROM, how do I revert to the stock kernel? Using the FKA app and have a backup of stock kernel. Thanks
Sent from my Nexus 7 using XDA Premium HD app