Database Info

[9001][KERNEL][GB] SkyHigh V1.5 [Updated 08-02-13] [Additional BigMem edition]

This is the official thread of my SkyHigh kernel for the Samsung Galaxy S Plus aka GT-I9001. V1.5 is my final release, please read the FAQ in post #2 for more details. Please refer to post #3 for changelogs of new releases, all available downloads are at the bottom of this first post. If you don't know how to get back to stock kernel you MUST NOT install this !
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this kernel and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.
Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.
If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.
It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.
Obey the rules !
Kernel feature list
- OC up to 1.8 GHz, UC down to 122 MHz (customisable eg. via AnTuTu CPUmaster/SetCPU)
- Undervolted (750 mV minimum) with VDD support (customisable eg. via AnTuTu CPUmaster/IncrediControl)
- many CPU governors included, smartassV2 is default
- many I/O schedulers, SIO is default
- optimized for high performance AND extreme low battery usage
- JFS and CIFS support
- TUN included (VPN support)
- cleancache (up to V1.4d)
- increased loudness
- all useful Thunderbolt and Adrenaline Shot main tweaks combined, optimized for I9001 and integrated
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures)
- Thunderbolt's LMK60 addon (aka adrenaline shot's supercharger V6 tweak) already built-in, DO NOT install separately !
- Thunderbolt's remount script integrated
- Thunderbolt's zipalign script integrated
- Thunderbolt's graphics addon integrated
- Thunderbolt's binary addon integrated
- Thunderbolt's sqlite addon integrated
- Thunderbolt's screenstate_scaling script not included but compatible
- enhanced 3D graphics (updated internal kernel drivers)
- I8150 GPU libraries included in CWM package up to V1.4d, optional in V1.5
- custom bootanimation support (animation NOT included, place your own here: /system/media/bootanimation.zip)
- custom bootsound (/system/etc/PowerOn.wav)
- sdcard speed increased
- improved jpg quality for better camera pics
- GPS faster fix in V1.4x only
- in V1.5 stock GPS files are untouched
- and some more which I already have forgotten
​
This kernel is meant for use with ANY Gingerbread stock ROM and custom ROMs as well (i.e. Android V 2.3.x only !). To prevent compatibility problems with custom ROMs that include system tweaks like Thunderbolt and Adrenaline Shot any existing init.d folder will be purged while installing the SkyHigh kernel. This is not a bug but a mandatory feature !
If you think you have an important script you will still need with SkyHigh like the screenstate_scaling script, copy it to your (internal) sdcard first then copy it back to the empty init.d after installing SkyHigh.
init.d support means that SkyHigh kernel will execute any scripts inside a folder /system/etc/init.d automatically but obviously only if these exist.
If you are using a custom ROM without init.d folder or any stock ROM you might have to create the init.d folder yourself. For more details there are tutorials in this forum.
Install instructions:
1. If you don't have CWM (FeaMod Recovery) install this first. If you never heard of that learn all about it here:
http://forum.xda-developers.com/showthread.php?t=1331164
2. Now make a complete nandroid backup of your phone with CWM
3. Download the attached CWM zip package
4. Copy it to your internal sdcard
5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"
6. Select the downloaded file "GT-I9001_SkyHigh_kernel_V1.x_CWM_signed.zip"
7. Confirm install with "Yes"
8. Wait till you see the message "Reboot to use SkyHigh kernel V1.x !"
9. Do so like the message says.
10. On first boot this may take a while. You will see the Samsung logo and then a black screen for at least 2 minutes up to 5 minutes. If this happens hang on, don't touch anything and don't switch the phone off or pull the battery. This would most probably break your ROM !
11. Usually many files and databases are optimized on first boot but eventually you will see the lock screen or PIN dialog. Then you are all set and beginning with the next boot this will be much faster, promised
Remark: especially on preoptimized (custom) ROMs this won't happen since there's not much to optimize. So it's no bug but a feature when it doesn't happen and your phone boots up in less than a minute
​
If you want FeaMod Recovery together with SkyHigh kernel just follow the install instructions above. Install desired version of FeaMod first and then SkyHigh. You will end up with the combination you wanted.
If anything went wrong during install just try again.
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure. I will never ever even touch your sdcard(s). But it is always a good idea to have a rather current backup of the sdcard(s) handy. CWM makes no backup of these, so you have to do that manually.
If your phone doesn't boot even after 10 minutes waiting (see step 10.) or you end up with a damaged system because you didn't wait long enough just go back into CWM and restore the backup you made.
If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.
If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.
If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above or in the FAQ below.
While V1.3 lacks some of the features above (especially the Thunderbolt/AS tweaks) it is totally safe with sd cards, at least I never got a single report on that issue. The older V1.3 is still added as attachment for your convenience although V1.4d already fixes all sd card problems.

FAQ
For personal reasons resulting in a tremendous lack of time I have to pause all my xda development for an indefinite time. Sorry about that, but I also really can't answer all the questions you might have so please stick to this FAQ and otherwise ask other experienced users/developers in Q&A section.
Besides I'm planning to get a new phone device in just some months so this also means that SkyHigh V1.5 is my last contribution to the i9001 development section. So SkyHigh V1.5 is provided AS IS and there will be no further support whatsoever on my behalf. But V1.5 was beta tested thoroughly for about 3 weeks by several experienced users here before it was published so it is very unlikely that there are still any crucial bugs in SkyHigh V1.5.
Last but not least broodplank1337 offered to maintain SkyHigh in the future but since he is also quite busy please don't press him and give him the time he needs to answer any requests.
Thanks to all members who respect the work of the developers and obey the forum rules for a great time and experience, maybe we will see again one day in another device section on xda-devs.
1. Q: I have sd card issues with SkyHigh kernel, what can I do ?
A: This was fixed in V1.4d, don't use any other 1.4 version ! For more details please refer to post #190 (http://forum.xda-developers.com/showpost.php?p=24247858&postcount=190) first, then have a look at the changelog (V 1.4d) below in post #3.
2. Q: What's the status of my CM7 port ?
A: this is a very complex topic and I paused the development in mid March in favor of this improved kernel. I continued on CM7 for about two weeks in April but now I had to stop it permanently (see first sentence of this FAQ).
I lost any contact to YardE since months so I guess he also surrendered his i9001 development. I still supported some very dedicated users with my knowledge and experience to help them to continue the CM7 porting project but none of them is an advanced developer or even coder so they are all still in learning phase.
3. Q: What about the car dock recognition ?
A: The card dock is not recognized correctly in any custom i9001 kernel that is compiled from Samsung's original i9001 source codes (Linux kernel version 2.6.35.7). However the phone will be at least charged in the car dock with kernels that are compiled from Linux version 2.6.35.14. SkyHigh V1.5 is mainly based on 2.6.35.14 (with some exceptions for Gingerbread compatibility reasons) so the charging works with SkyHigh V1.5 (only). This was tested and verified by Rhonin86, thanks mate.
4. Q: How do I provide a log for debugging ?
A: You must be familiar with adb to do so, if you are not you can only read the adb guide and learn everything about it here:
http://forum.xda-developers.com/showthread.php?t=879701
Then use the following commands to generate two different log files:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"
5. Q: Is Script Manager needed to run any scripts in init.d or bolt_scripts or somewhere else ?
A: Not at all. You can delete bolt_scripts if you still find that on your sdcard or somewhere else. You can uninstall Script Manager if you like. And screenstate_scaling script (or any other) will run automatically if copied to init.d with correct file permissions (755 or rwxr-xr-x)
6. Q: May I use SkyHigh kernel with my own custom ROM and publish that on xda-dev ?
A: Of course you can if you don't ask for money for your ROM. This is not a piece of proprietary commercial rip-off nonsense and must not be (re)selled. I am glad if you find it useful, but leave it well alone if you don't like it
7. Q: What are the best cpu governors, i/o schedulers, overclocking and undervolting settings and so on ?
A: the default ones ! Don't touch anything here if you are not 100% sure what these settings do and how they will help you. The given settings base on over 5 month experience and testing on my own i9001 and some others. But as stated in post #190 no two phones are exactly the same so not all of our phones work best with the very same settings. Therefore I added the possibility to customise all these settings if really necessary. But you shouldn't change any of these settings at all if you don't have severe kernel related problems with your phone.
8. Q: The feature list says that bootanimations are NOT included but supported. After I installed version 1.4/1.5 I've got a new bootanimation
A: that's not a new animation, that is just one that was already in your ROM before (in /system/media/bootanimation.zip) but never showed up so far. Most probably it got there with a custom ROM or UOT kitchen or any other mod/app that supports the android default animations. This file normally isn't used on the i9001 because Samsung implemented a proprietary bootanimation method. SkyHigh reverts the Samsung bootanimation procedure to the android default one which is also used on AOSP ROMs like CyanogenMod. So this is also one of many necessary modifications to make a kernel AOSP compatible !
9. Q: How do I install a custom bootanimation ? All my attempts failed.
A: look at FAQ #8 above and at kernel feature list in post #1 !
​

Changelog
Final update to V1.5 and V1.5bm [08-02-13]:
- source files updated from original patch level 7 (Linux kernel version 2.6.35.7) to patchlevel 14 (Linux kernel version 2.6.35.14). This can be regarded similar as a service pack release of Windows (more stability and less bugs overall)
- especially kernel GPU drivers for the Qualcomm Adreno 205 chip are more stable on my device (had some issues with one app that was solved by this update)
- also the car dock driver is improved, battery is now charged in Samsung's original car dock (though car dock mode still isn't activated, see also FAQ #3 above)
- EGL graphics libraries that come with SkyHigh V1.4x (these libraries are OUTSIDE the kernel, but included in the CWM install package) are EXCLUDED now and only come in an optional library pack (because these are the only ones that have at least significantly better performance in benchmarks, but some users say they are more laggy in everday use).
This means for V1.5 that everybody can decide for himself if he wants to use the EGL libraries that come with his ROM or the i8150 libraries or even any other versions that he will just install himself. More details can be found in post #566 http://forum.xda-developers.com/showpost.php?p=37391142&postcount=566
- faster GPS fix that comes with SkyHigh V1.4x was also EXCLUDED since it didn't work for some people. SkyHigh V1.5 doesn't even touch any GPS related files or drivers, there is just the original Samsung stock driver inside the kernel, nothing else.
But after installing a new kernel or ROM the first initial sat fix usually takes really long (2-5 minutes). This is normal ! But after that it should be faster, about 5 to 60 seconds depending on factors like position, movement, shielding and so on.
So if you have any GPS issues it is NOT due to the kernel but due to your (custom) ROM or any other GPS related factors (and there are many). Please refer to the following posts to learn more about possible GPS issues. These posts were only meant for V1.4x since only this version replaces gps.conf but they also provide some general details about GPS issues: http://forum.xda-developers.com/showpost.php?p=24301498&postcount=205 and here: http://forum.xda-developers.com/showpost.php?p=24565586&postcount=319
- finally there is a separate BigMem edition of SkyHigh called V1.5bm
This BigMem edition provides 376 MB available internal memory but breaks 720p video recording on some devices. While it still works on some devices there are rumors that it is also still possible on any device but by some alternative method. I never tested nor even used 720p recording on my own device since with such a poor camera it is totally pointless to even try HD recording IMHO. So if you want SkyHigh V1.5 WITH 720p video recording you have actually 3 choices:
1. you are lucky and everything works with V1.5bm anyway
2. try to find an alternative solution for video recording, maybe another camera app or a custom ROM is the solution. BTW: hiej claims that it works on his device with BigMem edition, maybe it's a feature of his GingerRevenge ROM so you should test that one first
3. just use the normal V1.5 of SkyHigh, it has 359 MB available memory which is still better than the stock kernels
Update to V1.4d [06-04-12]:
- sdcard problem fixed
In prior 1.4x versions the external SD card is suspended ("ejected") when the phone goes into sleep mode. On some phones the automatic re-detection of the SD card fails several times at wakeup so that it can't be accessed any longer. No data is corrupted though and reboot of the phone or reinsertion of the card are possible workarounds. As this is not practical in everyday use V1.4d solves this sdcard issue by reverting the sdcard power management routines to the original Samsung source version.
Just to be on the safe side I recommend everyone to use this modified V1.4d instead of V1.4 even if you have no sdcard issues so far. At least I do so
Update to V1.4c [06-04-12]:
- obsolete
Update to V1.4b [05-04-12]:
- obsolete
Update to V1.4a [02-04-12]:
- obsolete
​

Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)

Sounds amazing! This is the same one in broodrom 4 or is this updated?
So far it is working perfectly for me.
Thanks!
Richie
Sent from my GT-I9001 using XDA

no good for me.. hangs and reboots with simplistic F1

broodplank1337 said:
Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)
Click to expand...
Click to collapse
The kernel is the same but I fixed the install script

skywalker01 said:
The kernel is the same but I fixed the install script
Click to expand...
Click to collapse
Ok great won't need to change it then for now ^^

carlese said:
no good for me.. hangs and reboots with simplistic F1
Click to expand...
Click to collapse
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.

skywalker01 said:
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.
Click to expand...
Click to collapse
cranium v6 works good with simplistic..

carlese said:
cranium v6 works good with simplistic..
Click to expand...
Click to collapse
OK, if you can provide me some logs I can have a closer look into that, maybe it also applies to others.
But I will need the output of these two adb commands:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"

WOW - THX for your work
Hi Skywalker01,
nice to see the resuts of your intense work. Will try it later due to the fact that work is calling
By the way did you find a way to make the kernel recognize the original charging dock meanwhile ? Or if not is it still in your focus ?
I wish you success porting CM and keep on your good work.
Cheers
Rhonin

thanks for the kernel
i can't mount my sdcard in cwm. i currently use this kernel with brood rom.
first time i had this problem was after installing vitaliys kernel. changing kernel and doing a hard reset via *2767*3855# helped (as you can imagine you can't reset it in cwm since you have to mount the sdcard which doesn't work). so i got the suspicion that this is a kernel issue.
i know you said
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure
Click to expand...
Click to collapse
but i'm not sure if this is what you mean since you made mods on the sdcard.

your kernel is amazing sky. i think you made the best kernel for 9001. my phone is like an f-16 because of your kernel

awesome kernel <3 (i got a little question how is the CM7 development going?) (offtopic)

skywalker01 said:
...
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures) ...
Click to expand...
Click to collapse
So this means we don't need SM to run all init.d scripts run at boot?
Sent from my GT-I9001 using Tapatalk 2 Beta-2

Hi
Tq for ur kernel...its very amazing the music sound wad better..keep it up bro...
Sent from my GT-I9001 using xda premium

Seems like i am building a new version of Simplistic afterall. Thanks a lot for the great kernel!
Sent from my GT-I9001 using Tapatalk

Woow this sounds promising. Im gonna use it for my ROM if you don't mind...
Sent from my GT-i9001 @ LionROM

How's the battery like with this one?

[KERNEL] Chacha kernel 2.6.35.14 by Tokafondo.

Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.

tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Click to expand...
Click to collapse
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?

mohabmoka said:
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?
Click to expand...
Click to collapse
Yes, you will have to flash it by using fastboot:
(remember to have a cwm backup just in case you want to reflash your original boot partition)
Code:
fastboot flash boot bootv6initd.img
Swap partition goes as second partition of SD card. Swapper2 will work to format it as 'swap' type.

hm, happy to see still chacha development is active....did anyone tested it?

eager
ajeevlal said:
hm, happy to see still chacha development is active....did anyone tested it?
Click to expand...
Click to collapse
I'm eager to try it but I just love your port man, I will get a new phone in march so I will have the time to test more things on my chacha

hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)

nice
ajeevlal said:
hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)
Click to expand...
Click to collapse
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom

swashie said:
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom
Click to expand...
Click to collapse
you could do it man !!

tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!

kronflux said:
tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!
Click to expand...
Click to collapse
Thanks. I'm not that into the trying to port or get things to be done in ChaCha for fun. I don't see the benefit of having the latest version of Android working just because I could be done. 2.3.5 and Sense does the trick and allows me to work with my phone.
I would like to have some external reports of success or failure with my kernel. I did it for myself but though others could also benefit from it -- if there is a benefit at all.

kernel tested - no WiFi
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.

johan111 said:
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.
Click to expand...
Click to collapse
My mistake!!! :silly:
You have to copy the modules included in the attached zip file to
Code:
/system/lib/modules
you should be able to connect to wifi after that.

I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
Click to expand...
Click to collapse
i cant file called sysinit in system/bin !! or i must create it and type the code inside it?

It's a text file you should create. Type in the code, set owner and permissions and you are done.

Custom Kernel Not Supporting on Chacha with Stock Rom (Rooted with Busybox)
tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.
Click to expand...
Click to collapse
The moment I install the provided zip, and reboots, the phone becomes un-stable and the screen flickers constantly with the icons.
Android :2.3.3
Stock Chacha Sense 2.1 based on India: 1.20.720.1
Kernel: 2.6.35.
Any help !!

[Kernel][ROM][Ovation][CM 10.1.3][emmc] "Yellow kernel"

I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
It's packaged as a complete rom to avoid kernel module difficulties. The rom is completely stock minus the boot animation, kernel and kernel modules. Thanks to everyone who has made this possible.
Both the kernel and PVR module have been compiled with linaro.
The kernel has numerous performance and stability enhancements over any other kernel to date.

Great Work. Thank you very much!

Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<

wahidx said:
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
Click to expand...
Click to collapse
I appreciate the last_kmsg. I apologize for using everyone as beta testers, but this demonstrates why it is a good idea- because I have been running OC5 for a few days without a single hiccup at all. I am actually surprised OC4 did so well for you. OC4 was also the first version to sport a new pvr module.
One thing I had been noticing before being able to compile my own pvr was that I could have one kernel play well with the stock pvr, and I could have a kernel right after that not play well with the pvr at all. This was my major motivation to be able to compile my own pvr so that it could match kernel space every time.
Ok, with that said, I compiled the pvr against OC4, and didn't bother updating it against any subsequent kernels. I probably should have known better, but it was working well enough for me.
Your error looks suspiciously like a missmatch between the pvr and kernel space. So if you want to try this update:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
and let me know if it works any better. I made sure to compile the pvr to specifically match the kernel.
Also, when I compiled the pvr before, I used PLATFORM_VERSION=4.1. I used this as an excuse to try
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.2.2
I don't know if it makes a difference or not.
Another thing I noticed you have slightly different hardware than I do. You have elpida ram versus samsung which is what I have.
I modified samsung ram timings to be slightly faster, but the other ram types were left at stock speeds. I may eventually try to clock the elpida ram the same as I have done with samsung, that may or may not make a difference. This may affect pvr performance as well. (It seems your pvr was a little slow bringing up power a few times). Then again, it could be my pvr source (although it works flawless for me, it may be hardware differences- I dunno.

thx for fast replay man,
i will try this release and give you feedbacks.
i have the bad feeling that something is wrong with my hardware. can be the only explanation, why my device reboot so often with CM10.2, CM11 and your OC6 release :/
//EDIT
actually i had just 1 reboot after some hour OC6 using, i will try OC6 for the next 2-3 days, maybe it was just a bad accident. after that i will try your OC7
regards
//EDIT #2
OC6 Test
after 2 days more, just 2 freez-->reboots (check last_kmsg) but still better than CM 10.2 and 11 on my device

Jon Lee said:
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
<snip>
The kernel has numerous performance and stability enhancements over any other kernel to date.
Click to expand...
Click to collapse
Hi Jon:
Hey, since we're asking for the moon, and since you're making THE oc kernel, any chance you can implement f2fs? I've got a Gal Tab 2 and an xda developer over there has a page about what he's done to get f2fs to work. Mostly it seems to require a .101 kernel. And he was kind to update TWRP so it would support f2fs. (I think to keep it from automatically formatting in ext4.) And he even wrote some zips to format /data, /system and /cache to f2fs.
My Tab 2 doesn't benchmark any faster but it sure is faster with f2fs. I image the HD+ would be faster too.

I'm new to flashing the Nook HD+. I was previously using the SDcard booting option for CM 10.1, but I would really like to get Nook off of this completely. Where do I start? I downloaded the ROM, and I have a boot IMG from another ROM on an SD card that takes me to recovery. Where do I put this ROM and how do I overwrite the actual Nook ROM?

install fails using verygreens internal recovery. is there a trick to installing this?

So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?

SynGamer said:
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
Click to expand...
Click to collapse
Yes, that means you still have stock recovery installed. You need to go to my HD/HD+ CWM thread linked in my signature and download and install the 6036 CWM from item 5 there.
Edit: but you know if you upgrade to CM10.2 you lose this kernel, right?
Sent from my BN NookHD+ using XDA Premium HD app
---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------
smatticus said:
install fails using verygreens internal recovery. is there a trick to installing this?
Click to expand...
Click to collapse
It depends on which verygreen internal recovery you are using. You need to have version 6036 or older to flash it. You can get one per my previous post.
Sent from my BN NookHD+ using XDA Premium HD app

Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?

i6941 said:
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
Click to expand...
Click to collapse
Does this work for CM11?

andtron said:
Does this work for CM11?
Click to expand...
Click to collapse
I think the answer is no, when you flash cm11 the OC kernel will be overwrite. But I didn't try this.

As the thread title indicates, this kernel is only for 10.1.3.

it says there is a new update from the option -- about menu...should I?

Jon Lee said:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
Click to expand...
Click to collapse
I couldn't find a tabletUI patch to match the final cm10.1.3 stable so here's one for anyone else downgrading like me.

Here's another experimental kernel update.
http://www.mediafire.com/download/1lkesmn6si6hd1e/ovation-kernel-cm10.1.3_v5.zip
I'm using it on OC7 pvr without issue (?).
1) reduced elpida and hynix ram timings.
2) updated vivante gc320 gcx 2d composition drivers to gitorious.org/gcx staging/alexei-dev. These are significantly different from original. (FWIW Staging/master branch threw memory map bverror 2 logs, but otherwise worked fine).
3) reduced dsp carveout memory. Increased system memory.
If needed, here is just the plain kernel for OC7, should anyone wish to revert back to that for any reason. (So as to not have to flash the entire ROM).
http://www.mediafire.com/download/z4r59n8dasxgz93/ovation-kernel-cm10.1.3_v4.zip
Kernel source for OC7
http://www.mediafire.com/download/6rngvee6x471cc3/android_kernel_bn_omap-cm-10.1_v3.tar.gz

So oc7 has been very unstable for me. I started with a completely clean slate, but it's frequently rebooting and not waking up from sleep. I may remember having these same problems when I was regularly using cm10.1 last year.
I've gone back to cm10.2.1. You should consider developing your kernel for that one.

Ya'know, I make these for me first and foremost. They reflect what I'm working on, trying to fix or improve the performance of my device.
Each one is different, some have worked better than others, but I notice an overall improvement from the original kernel. It is substantially different than any other nook kernel out there and works the best for me.
Here's the last. I think it works well. Made some additional changes to mmc/sdio to try and improve stability with wl12xx.
Source (which includes the vivante driver change from before):
http://www.mediafire.com/download/v4ihnr46eo9ap4d/android_kernel_bn_omap-cm-10.1_v4.tar.gz
Flashable kernel
http://www.mediafire.com/download/c9bsziswrf7y0e4/ovation-kernel-cm10.1.3_v6.zip

I like 10.3.1 but it has two downsides. 1) No automatic TRIM. 2) Unsafe manual TRIM because of Samsung MAG2GA EMMC bug.
Is it possible to implement the workaround used for 10.2.1 and later? Then manual TRIM by using console "fstrim" should be safe.
http://wiki.cyanogenmod.org/w/EMMC_Bugs
I assume the source for the 10.2.1 kernel would have the ported patch.

[KERNEL][9305] HboKernel v0.3 - 02.02.2015 (NamelessRom 5.0)

Hi all​
Introduction
I cannot call myself a developer or a kernel master at all. I'm just good at discovering and learning new things and in fact that's the way my journey with kernels started. At this point I want to start a new thread for something different from my earlier work, porting Boeffla kernel.
Features included:
Compiled with 4.9 Linaro toolchain
CPU OC up to 1600Mhz
ZZmoove as default governor (with moderate profile) - best for smoothness/battery life
Zen and Row I/O schedulers
Undervolting interface introduced
Configurable Touchboost
Configurable Touchwake
Charging interface
Boeffla Sound 1.6.6
Dynamic Fsync
Switchable Sharpness Tweak
Led configurable (fading, strength)
Configurable Android logger
Configurable printk logging
Readable: asv level, CPU temperature
Disabled some debug
Few minor tweaks (check github if interested)
If I forgot something - Github is up !
What kernel features may we expect?
F2FS support
Dualbooting support (if I can handle it properly)
What you say?
Compatibility
Flash only on proper roms!
As for now we have only Lollipop version, compatible with NamelessRom (you may try with others LP).
Download
You can download the most recent kernel here -> Click
Source
Github link - Click
Credits
These men never refused to give me a helping hand, advised me what to do and, more important, without their work this kernel wouldn't even exist (opensource doesn't mean no respect!).
@JustArchi
@Lord Boeffla
@Yank555
@ZaneZam
@arter97
Samsung :good:
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can't 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 anything.

Camera bug info: (hidden, only applies to Samsung ROMs)
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 solutions:
Option 1 is good for people that rarely change their ROMs (and it fixes EVERYTHING), whether option 2 is better for people changing their ROMs more frequently (however, it's always good to have backup of your SlimISP on sdcard).
Option 1. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my HboKernel
Option 2. 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 )
Option 3. Read this thread and follow steps --> click
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

I say, may good luck be with you accomplishing these features in the kernel :good:

Best of luck with this project Hbohd

Thanks to you, there is some life potential remaining for i9305!
Long life to i9305 and may the (dev) force be with you HboHd!
Thanks for your work!

+1 Nice one.

Hbohd said:
What you say?
Click to expand...
Click to collapse
I say: it's freaking interesting!!!!

Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3

aaz03 said:
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
Click to expand...
Click to collapse
Hmm.. Isn't 'Screen mode' under Display settings enough? It gives a little bit of difference without need of additional kernel's code modification.

New alpha 0.1
Okay, to keep this project alive, to show off some progress step by step and to satisfy flashoholics - I've decided to release my small achievements in form of alpha kernels
Firstly, let's restart naming convention of the kernel. It will be simple x.x now, starting from available below 0.1 version :cyclops:
Small changelog:
removed debugging in many places
compiled with linaro 4.9
few tweaking commits
Let's say that due to my 'stupidity' or magic ability to forget something, I've spent on it many hours today :silly:

Is Insecure ADB fixed?

Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin

This is for old bootloader only?

SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..

@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!

ShonkUK said:
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
Click to expand...
Click to collapse
sham79 said:
This is for old bootloader only?
Click to expand...
Click to collapse
I haven't stated anything different from what is true I mean, if I write that you can you use it with new bootloader or SE is disabled - then it would be true
I think that in next release I will disable it (simply forgotten due to my compiling problems mentioned earlier).
Oh, and I don't need another changelog when everything is written in the git I haven't just suceeded in uploading it to the github yet :/
machotecba said:
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
Click to expand...
Click to collapse
Yeah, someone mentioned it already. I will try to fix it for next version, thanks!
djb77 said:
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
Click to expand...
Click to collapse
Will be in for the next so-called 'alpha'

Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?

fpriot said:
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
Click to expand...
Click to collapse
Yep, you are right

If I may suggest @Hbohd... Could you please start with the power features implementation? Charging rates, ignore unstable power and margin...
Because these are the ones I really miss... My chargers and/or cables are not good and I need these mods to charge properly...
Thanks!

Firsty thanks for all your hard work.
The phone no longer charges from the car dock. This was the same for the stock kernels in 4.1.2 & 4.3 - still withold bootloader. 4.1.2's was fixed with Pegasus kernel and 4.3 was fixed by your Beoffia 5 kernel.

[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F

[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F
Q&A for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Thanks
@Cl3Kener: Big thanks for your hard work. Installed your kernel yesterday, and can definately see some improvements.
 @ramjet73: Big thanks to you too. I followed your posts/instructions and flashed rastapop+uber and am happy i finally took the plunge.
Now for my question: I have the tricksterMOD and I can't see any color profiles (except the default). How can I apply other profiles? I only see one.
Regards,

On LiquidSmooth LP 4.0 with UBER-L 3.4.105
Governer = optimax
Scheduler = zen
Read Ahead Buffer Size = 3072
Everything is running smooth and fast! Good battery life!

Low brightness after install
Hello, I gave a question... When I installed a last Uber kernel L v4.10 from 9 December of 2014... I have a very low brightness... How can I fix it...
Also I cannot make OC more than 2.7 or 2.8 ... Phone doesn't boot... And how I can fix it...
Thank you for a answer

Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04

Are there any negative consequences for clocking the minimum frequency at 96MHz?

Usb-otg f2fs
I'm currently using the latest version of UBER-L kernel (01/01/15).
I have formatted my Micro USB to F2FS and would like to use it with my phone. TWRP recognises the USB and mounts it successfully, but the ROM (OptiPop) does not mount the USB. Both mount the USB fine when it is formatted to FAT32.
Is it possible for me to use F2FS using USB-OTG?
Thanks.
Edit: Got it working by using the 'Stickmount' app. ^_^

FloGatt said:
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Click to expand...
Click to collapse
I disabled trimming and I dont see a difference with f2fs. I would conclude that it isn't necessary with f2fs

Is there changelog of the new kernel version?

FloGatt said:
Is there changelog of the new kernel version?
Click to expand...
Click to collapse
Its all on github. The link is on the OP of the original thread. (The one with the download links)

GPU clock not going above 450MHz
Hey, I'm using this kernel (latest version as of now), on a clean flash of Optipop (also latest as of now - 11/01) with F2FS.
I set the max gpu clock to 650000000 in the uber_v1.3.cfg file in /etc
(also by terminal as in the 2nd post just to be sure) (echo "650000000" > the path and all)
Apps like System Monitor Lite and CPU-Z confirm that the max gpu clock is 650Mhz (Adreno 330 @ 650Mhz).
I have also set the performance governor (in the config file, and I tried via synapse + UKM 3.6.1 too) (I have set synapse not to apply settings on boot, so that should not be interfering with the init config of uber kernel until I set something in it.) I have no other kernel tweaking apps anyway.
However, the clock only goes up to 450MHz no matter what. It goes directly to 450 when touching the screen due to the performance governor, so I know settings are being applied.
However System Monitor, CPU-Z etc all show, current clock: 450MHz, Max Clock 650Mhz.
Even benchmarking with GFX bench gives results basically identical to the stock Nexus 5 with 450MHz, so there is no performance and FPS difference that should be there.
I searched the developer thread and found a few posts from many months ago that the gpu overclock was working properly for many people, with an appropriate improvement in FPS and benchmarks, with a couple of people also having my issue, that whatever of 650/533/450 max I apply, gpu doesn't go over 450MHz. However I couldn't find any solution.. it stopped working properly at some point between those builds when Chet introduced 533/650 and now?
I can't post in the dev thread (less than 10 posts).
This is reproducible, right after a clean boot, not a thermal issue (am not overclocking CPU, not running any CPU benchmarks, temp is less than 50C).
Hope someone can help. Thanks!

Installed Optipop back onto my N5 today. After a few hours of the phone being on the UI starts to act up then eventually needs a reboot to get back to being functional. I then flashed UberL kernel and now my screen is fuzzy and glitches out. Never had this problem in the past with Optipop or UberL. Please don't ask if I dirty flashed or deleted the android folder. I completely wipe my phone before I install a new ROM. I have been installing ROMs for a good minute now and have never seen this before. I have tried at least 5 other rom/kernel combos.....none have the same affect as UberL and Optipop. Yes I've tried F2FS ONLY Permissive Only and EXT4/F2FS Permissive and Enforcing with no luck.

Has the issue with the missing charging icon when the phone is turned off and plugged in reappeared? I have System, Data, and Cache formatted as F2FS and flashed F2FS-ONLY-Lollipop-Kernel-Cl3Kener-Kexec-Permissive.zip before flashing UBER, but I am still having this issue. Everything else appears to be running smoothly.

Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.

sirarduin said:
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
Click to expand...
Click to collapse
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.

JayR_L said:
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
Click to expand...
Click to collapse
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions

sirarduin said:
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
So you are saying that fixes the issue with the cfg file?

JayR_L said:
So you are saying that fixes the issue with the cfg file?
Click to expand...
Click to collapse
After 2 Benchmarks, i can say that doing this fixed MY problem. Uber/sabermod is now working realy well for the performance. Uses AnTuTU to check if its working. It upgraded a lot the performance for me.

Which governor gives me more performance?

[email protected] said:
Which governor gives me more performance?
Click to expand...
Click to collapse
performance ?! but it will drain your batterie a lot.