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?

[ROM][JellyBean][4.3]Unofficial CM10.2 - 10/27/2013 - Butter - MTD - OC Kernel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
About
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices (See above for supported devices & how to install CyanogenMod on said devices). Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc. CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
Brought to infuse by scott.hart.bti
Special Thanks to Nun (Thanks for teaching me to do things the right way.), Yuma (Thanks for being able to answer every build/git question i have), JT (Thanks for fixing a majority of the issues we had), Araemo (Although you dont have much free time, you have spent alot of it helping out to get this build on track, Thank you for that.), PoX(Thanks for suggestions and feedback and heapsize changes), Entropy for all your contributions that you make everyday, elliot.newnham for making the OP look great! ... the list would go on forever, Everyone else that has contributed... The list would go on for days
Donate to Cyanogenmod
Donate to scott.hart.bti
​
Instructions
Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here (the latest for JB 4.2.1 - 12/12/12) - Working swipe! ---- Here (the latest for JB 4.1.2) - New GAPPs 10/11/2012
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Coming from JB(4.1)
CWM: Wipe Cache / Factory Reset Note: You should be fine without this step, but it is HIGHLY recommended as it makes certain all bugs are wiped clean.
Install ROM: Scroll down for downloads
Install OC kernel [Optional]: Scroll down for downloads
Install Gapps: Here (the latest for JB 4.2.1 - 12/12/12) - Working swipe! ---- Here (the latest for JB 4.1.2) - New GAPPs 10/11/2012
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Downloads
Make Certain you read this ENTIRE post before Downloading... I know you didn't, so Go back and read it! :good:​Unofficial CM10.2 - 4.3 - 10/27/13 - MTD - Mirror - Please install latest GAPPs for Android 4.3 from http://www.goo.im/gapps
Unofficial CM10.2 - 4.3 - 9/23/13 - MTD - Please install latest GAPPs for Android 4.3 from http://www.goo.im/gapps
Unofficial CM10.2 - 4.3 - 9/22/13 - MTD - Please install latest GAPPs for Android 4.3 from http://www.goo.im/gapps
Hints
Our webpage: http://www.cyanogenmod.com/
If you have lost your IMEI, look here or follow instructions starting with "Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)" (Yes you need to ODIN back to stock)
If you are having GPS connection issues place you phone in direct view of sky with maps open, Data ON, GPS ON, and screen timeout to never. Let it obtain a full lock. This will download/update your AGPS data and should improve lock times.
If you are having battery issues, please let the phone settle down. This may take a couple days for data to 100% sync and SD cards to be fully searched. Reboots often fix "Android OS" battery issues.
If you would like to try out different modems: Flashable Modem Thread for MTD. Thanks to blscallions!!
Trouble
If you have an issue and you want to call our attention, here's what you do:
1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.
2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.
3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...
... stay friendly, do not demand anything, do not threaten
... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread
... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.
Change Log
Unofficial CM10.2 - 4.3 - 10/27/13 - MTD - Mirror
* Merged latest CM sources. Everything up to date.
* Few kernel optimizations and reverted a questionable change from past build.
* Finally converted the infuse device settings to the new CM 10.2 CMHW standards. Vibrator control tested and is working fine with new setup. Accessed from settings - more - other device options. mdnie controls are accessed from settings - display - advanced display settings.
Unofficial CM10.2 - 9/23/2013 - MTD
* Same as before + telephony fix to finally fix the issue where data would drop during voice usage. Huge thanks to pawit for the fix!
Unofficial CM10.2 - 9/22/2013 - MTD
* Selinux finally added and working for the infuse. Tooks alot of updating and backporting, but its working.
* couple fixes kernel side.
* Added sync to kernel
* Added sw sync to kernel
* Added cgroup timer slack to the kernel
* Latest CM sources as of a couple hours ago.
Unofficial CM 10.2 - 8/5/2013 - MTD
* Android 4.3!
* Fixed 'crackling' (it only takes one bug report and one confirmation for me to fix something... not pages of complaints.)
Unofficial CM10.1 - 7/14/2013 - MTD
* Merged sources from CM with numerous fixes/improvements and additions
* **** ton of kernel improvements and fixes.
* updated net/data/wireless source files.
* Fixed 2g/3g toggle
* Bootmode support added to the kernel. Fixes rare cases where when the user reboots they end up rebooting into recovery instead of booting normally.
* Tons of improvements and fixes kernel wide.
CM10.1 - 6/16/2013 -
With all the kernel/device improvements, please DO A FULL wipe/format before flashing!
* HUGE HUGE HUGE progress Kernel side. Updated kernel wide.
* Added Viper Audio! This app is AMAZING. You NEED to try it. When you first open it, it will ask to install a lib, just select "CortexA8 with NEON" from the list. After that, just reboot and your good to go.
* Updated our touchscreen drivers so they no longer need legacy code to suppor them
* Ported cpufreq and cpuidle drivers to latest kernel source code
* Improved Ondemand and Interactive governors - No longer any legacy code
* Updated kernel workqueue... no longer legacy
* Numerous fixes from CodeAurora kernel wide
* Updated our File system drivers
* Updated Lowmemorykiller, Timed GPIO, and Binder. (kernel)
* Updated our UV/OV code. Much more efficient. (Kernel)
* Updated to BFQ v4 (kernel)
* Much much much more work to the kernel.
CM10.1 - 5/19/2013 -
Mainly kernel changes/optimizations
Merged latest CM source code
Added Vibration intensity controls! - Settings - advanced - vibration controls
Added autogrouping abilities on the kernel side
Minor wifi changes
Backported BFQ scheduler
Backported Interactive governor (includes boost support)!
****Definitely recommend a full wipe/format before flashing!****
CM10.1 - 5/9/2013 - New CM build is up with the new partition layout. DO NOT proceed without reading this first. You may want to remove your external sdcard as there have been a few reports in the past that it messed things up. Safety first! When you go to flash it, it will give you a warning about being incompatible and it will erase your data... You will need to flash it again for it to start to flash. It will reboot and go back into flashing.... It will reboot again and come back to normal recovery screen. From this point, the build is finished installing and you can install GAPPs or any extras you may want to use. DO NOT, i repeat DO NOT under any circumstance flash the old BLNnTouchwake packages until i update them... You will be completely F'ed.... Need i say more? - 5/12/2013 - BLN packages updated. Please use links above.
Enjoy the new partition layout and remember to thank araemo for figuring out what was needed to use the new partition setup for our device.
Latest CM sources have been merged and overlay has been added to our device tree to finally fix dock audio. It now works and routes correctly.
CM10.1 - 5/4/2013 - Id highly suggest a full wipe/format when flashing the new build. There have been a bunch of kernel changes and board changes on the device end. Failure to wipe could result in ****ty underwear and a ****ty experience. Optimized the kernel as much as possible with our current setup. Also merged latest CM sources.
CM10.1 - 3/30/2013 - Browser issue from the 3/28 build is fixed.
CM10.1 - 3/28/2013 - Status/notification freezing issue finally resolved! Another source update and changes on the device/kernel end to keep up with changed source.
CM10.1 - 3/24/2013 - Another source update and changes on the device/kernel end to keep up with changed source.
CM10.1 - 3/16/2013 - Another source update and changes on the device/kernel end to keep up with changed source.
CM10.1 - 3/2/2013 - Nothing major, just a 'keep up to date' build. Alot of minor fixes and cleanups on the CM source side.
CM10.1 - 2/15 - Android 4.2.2 has been stuffed into cm10.1! Not going to list the android source changes, look them up on your own. As for the build, I removed the p2p code as it wasnt working as it shouldve been anyways (actually should have done this awhile back). Removed the overlay for notification light settings since we dont have them. used the default audio policy from the cm build instead of the device specific one we were using. Few other things i dont recall at this time. Merged latest CM source code.
CM10.1 - 2/3 - New build is up. Couple minor changes in the device tree, but nothing worth noting. Mostly CM source update.
CM10.1 - 1/14 - New build is up. Sorry for the delay. Couple minor kernel changes and a minor bluetooth change device side. Other then that, this is mainly just a build to keep up to date with CM source code since its been awhile.
CM10.1 - 12/29 - Freed up more RAM!! We are now up to 501 MB of free RAM. Not sure there is anything else left that we can squeeze RAM out of. If you remember correctly, with ICS and early jellybean builds, we had 444 MB of RAM or somewhere around there... So in total, jut under 60 MB of RAM has been freed since the jellybean builds have started. I did some very minor cleanup on the device side (nothing major as our device repo is right where it needs to be). I also cherry-picked a couple options to add the rocket launcher option back into the mix. You can use this by going to settings -> display -> day dream -> rocket launcher. Just a neat little thing that i decided to add. Also added a commit from JT that adds slight transparency to the status bar notification background. Other then that, just alot of CM source merges. Check it out!
CM10.1 - 12/19 - Pretty much a must have as far as im concerned if your running cm10.1, you want to update to this build. I have added the latest linaro tool chain to the kernel and built it with linaro. For those of you that are not aware of linaro, please do some searching before posting about it. This is the first time ive built the kernel with a linaro tool chain, but have heard good things so figured we would give it a shot. Updated the kernel compression files which should improve boot time. I also went and disabled the tvout and mhl files from building into the kernel. I cant prove that it was hurting anything having them included, but it seemed that every kmsg had lines in it referring to tvout issues, so i figured id disable it since it should have been disabled a long time ago since we do not have working MHL and tvout at this point... and probably not any time soon. Reverted a couple changes that i think may have been causing minor issues for us which should prove to make things even more solid. Not much was done on the device side of our repo this update. The important things are the changes i have mentioned to the kernel and also merged the latest CM source code, which is always a good thing since they are still adding code at an impressive rate.
CM10.1 - 12/16 - This update should fix issues with Bluetooth. The only changes in this build are for bluetooth and also merged latest CM source since last night. Im 99% sure that BT is now fixed..
CM10.1 - 12/15 - This is a big update, you definitely want to update to this one. Both wifi and wifi tethering have been fixed. Wifi sleep disconnect issue should be better now thanks to code from pawtip without any of the negative side effects. Wifi tethering has been fixed thanks to entropy forwarding the legacy wifi tether code, seems to be working as it should. The bluetooth button from the settings menu is working again and seems to be fine. Alot of new code has been merged in the CM side of things. They have some new things that they added as well as things ported from the original CM10. There is also a new gapps package available, but i had to modify it as the gapps were outdated and causing issues. I updated the gapps and uploaded the 12-12 package on my goo found at http://www.goo.im/devs/scotthartbti/gapps.
CM10.1 - 12/11 - Will update tomorrow. Link is up.
CM10.1 - 4.2.1 - 12/2 - enabled/merged source for samsung stk. Made another change to GPS and it should be all set. Added overlay to our device source files to modify the clock dpi settings so that it fits correctly from the lock screen. Couple of changes to wireless on the kernel side of things to adjust for the way 4.2.1 is setup. Wireless should be working perfectly at this point. Specified a limit of 5 user profiles and CM source has it setup that you can add the user profile switching to the power menu for quick switching. Re-enabled expanded desktop mode. Alot of other CM source code changes have been pushed out and continue to be pushed out. All and all, 4.2.1 is coming together incredibly smooth. Please use the GAPPs package i have on my goo account located at http://goo.im/devs/scotthartbti/gapps. It is the 11-29 package and does not give me any issues. I modified the package so that the text swipe is now working correctly and the web browswer does not force close. Please make sure you do a full wipe and wipe dalvik and FORMAT /SYSTEM before flashing this new build and the modified 11-29 GAPPs package.
***Note, if you use a different GAPPs package then the one i suggest and have any issues, do not post about it.***
CM10 - 4.2.1 - 11/29 - Performance options are hidden by default with the developer options (cm change, dont blame me). To get them back, just simply tap the build number in the about phone section numerous times until you see a message saying you are a developer. USB is fully functional and even better... so is USB tethering. Wifi seems to be working pretty good and i have not noticed any drops since a change that was made on the kernel side. Live wallpapers are working fine also. Now... on to GPS... I do have it working, but its not 100 percent yet. This is the deal. If you try to use GPS and it does not work within a minute or two, you need to toggle wifi on and off. Dont ask me why, but that is what is causing it. When you do that, reload maps or gps test (whichever you are using) and you should be good. If not, repeat the previous steps. Ill still look into this and im sure it will be better soon, but for now, its atleast functional. Re-enabled zram and it seems to be working fine. Also merged latest CM source code which includes numerous forward ports from the original cm10 to work with 4.2.1. Overall, 4.2.1 is coming together pretty nice.
CM10 - 11/18 - For those of you that were reporting issues from the previous build, this is an update for you. Download and Flash this Kernel. I reverted some of the minor changes that more then likely caused the trouble. I have no idea why some of you were having horrible problems and why some of you were not, but i guess that pretty much indicates how horribly F'ed our kernel is and that the smallest freaking change causes havoc for some users. Going forward, im not even touching the kernel or looking into changing anything kernel wise unless its a standard cm change for ALL samsung kernels.
Anyways... download from above, reboot into recovery, wipe cache, wipe dalvik cache, flash kernel fix, reboot.
CM10 - 11/4 - First and foremost... Fixed my mistake that took away the 8mp option for camera... That is now back (thanks to everyone that pointed it out). Next... OC kernel has been migrated into main kernel. That means no more separete OC kernel. Just one kernel with 1400 and 1600 mhz steps. Now... With this option added, Please use caution using those levels and use common sense. If the phone reboots or you have any issue at 1600 and think that something is wrong with the build, please change frequency back down to stock 1200 and if it stops, then obviously oc isnt working good for you. DO NOT REPORT IT as a bug in the build! JT added an option into the cm source files that allows us to set long press actions from the lock screen. Its pretty neat... You can specify values such as flashlight control and media controls from the capacitive keys and to activate, just long press whichever button you set. That option can be found in settings - lockscreen. I optimized more of the kernel values (again) and gave us an extra 13 MB of RAM. I updated wifi drivers again. There have been a small number of reports that when the phone goes into deep sleep and then they wake, wifi does not reconnect. Im not sure if the wifi update fixed that or not, but if you happen to be one of the few that experience this issue, just download and use wifi fixer. I tested it with no issues or complaints. Updated kernel compression/decompression files. Added encryptable footer (fixes cryptofs errors in logcat). Enabled expandable desktop option. Few kernel changes/optimizations here and there. Removed CMupdate app since we are not an official device. CM created and included their file manager into the build package. Merged latest CM source code.
CM10 - 10/28 - Just updated the stock CM kernel to have the option of 1400mhz. You can download Kernel From Here. This is just as stable as original stock kernel, even when using the 1400mhz OC frequency. Now, Since the stock kernel is going to include the stable 1400mhz level, that means i am going to discontinue the separate OC kernel i have been releasing. I made one more change to the OC kernel and put together a final release. Download CM OC Kernel V8.1 the final release from here.
CM10 - 10/27 - This is pretty much a maintenance build here. Reverted one or two questionable changes to ensure stability. Added a few changes on the kernel side to make dvfs code more efficient, fixes for wifi (only a couple minor ones.), update touchscreen driver, update kvm code to handle pages more efficiently. Corrected the camera preview/picture sizes (they seemed to be off before). Removed unused/unsupported code on device side. Added overlay config for the home key to unlock device feature to work correctly and the option is found from settings - lock screen - screen security - home unlock. Fixed up the lines needed for goo manager updates, I messed them up before (so OTA probably wont work until I release next build). Other then that, I merged in latest CM source code as always. Like i said... minor things, but a solid update nonetheless. FYI.. I was unable to get interactive boost working. I am still looking into it and hopefully by next build we will have boosting for our interactive governor as well as ondemand.
CM10 - 10/22 - Changes for this build: dock audio is now working thanks to the work of araemo. You can enable dock audio by going to setting - advanced - dock. pulled in wifi drivers from siyah kernel which should update our drivers a bit. Disabled ipv6 as it was causing havoc on our WiFi activity and caused hanging at times. It was also causing the delayed lock times with GPS. With this disabled, GPS is as good as it ever was if not better. This is a temporary work around until we can get ip6 support squared away. For now, sending a code to disable on start up will suffice. Fixed our calibration driver as it wasn't pulling the correct file at start up. CM fixed up our power hal and it now recognizes when we change governors... which means no more annoying log cat errors from power hal and also re enables boost pulse if you choose on demand governor again. Pulled a couple minor fixes for ksm code on the kernel side. Included goo manager and added the necessary lines to build prop to allow ota updates going forward. Please ignore the version I have specified... its just a way for setting up future updates. Found an issue with our audio drivers that would very very rarely cause a crash. Basically audio was not allowing suspend and in turn caused a crash. Pulled in latest cm source code.
CM10 - 10/15 - This build is mainly little bug fixes and missed things from the 4.1.2 source merge, but there are some key things from our device end that make it worth downloading. I optimized our kernel code a bit and freed up about 35 - 40 mb of RAM without sacrificing anything at all. I added a patch from Humberto to automatically enable the zram function after you select the value you want and reboot (this means no more manually having to run the script, reboot and your good to go.). Added option to allow changing ISO modes for camera (thanks to JT for that one). I've added 'lazy' governor by Ezeekel. Lazy governor is basically a modified ondemand governor and it seems to be pretty efficient. I have enabled installation of unknown apps by default (was tired of having to enable it everytime id restore from titanium)... I know there are a few other small things im missing, merged latest CM source.... Which includes a new addition to the battery styles that you can pick from. Please dont forget to update your GAPPs from the link above!
CM10 - 10/10 - Android 4.1.2 is here and ready to go on the infuse! Please search for Android OS changes from 4.1.1 to 4.1.2 as im not going to list every single change they have made. I have fixed up the power HAL this build, should be fully functional now (Thanks araemo). Added zRam, which is enabled/disabled from settings - performance. Slight clean up in device tree. Made a change that should improve GPS lock time. Everyone that i had test it reported improvements.... remember, it may still take a minute or two for the initial lock, but after that it should be good to go, atleast it was for myself and the people who tested. Merged latest CM source code. *** Previous GAPPs will work, no need to go searching for newer GAPPs.****
CM10 - 10/5 - New partition layout to increase /system to 400mb to avoid any possible space issues. We previously had 350mb and we were cutting it very close! Added power HAL for our device and also added pulse boosting to the ondemand governor... Its pretty nice. Few minor fixes here and there. Cleanup, bugs fixed. Merged latest CM source code. - PLEASE READ THIS BEFORE DOWNLOADING AND FLASHING!!!!: I had people test the following install and they left their external SD cards in the phone and had no issues, but if you do have an issue, remove external sdcard and try again. This latest build has been repartitioned so that /system is larger. system was previously 350mb and we were running out of space, so in order to avoid space issues, /system has been increased to 400mb. Now, since the partitions have changed, that means that they are going to wiped out and setup again when you flash the zip. This is going to cause the same behavior as the initial bml to mtd conversion flash. If you are on the previous MTD partitions, When you first flash, it will give you a warning message saying that your data will be erased in converting and you must flash again to and stop and you will see the dead android guy. This is just a warning message and is meant to be seen!!!. You will then need to flash again and this time it will start the conversion and then reboot into recovery and finish the conversion and then reboot into recovery again when it is finished. If you are on BML and converting to MTD for the first time, once you flash the package it will just start to install and reboot 2 times during the install process. When it comes back up the second time, you are finished and can proceed. You can then install GAPPs if needed or just boot up like normal. One last FYI... If you use an OC kernel, you need to use the newest one with the new partitions laid out or your gonna have some issue. Do NOT use old OC kernel on this new build.
CM10 - 9/26 - Fixed Battery drain issue from 9/23 build that was removed. Fixed data indicator issue. Added support for suspend mode in charging, merged latest source - USB Tethering is now working thanks to thebecoming! Reverted a couple changes that i believe was causing issues for a couple people on last build, you guys should be good now. Added smartassv2 and interactive governors. Tweaked Conservative governor (thanks entropy). Cherry picked a commit for promixity sensor settings from phone - settings. Various upgrades to kernel. Merged latest CM source code.
CM10 - 9/14 - Only a couple updates here, but ones that i thought were worthy of posting a new build. The MMS issue that some have reported should be completely fixed and shouldnt be an issue now. Also, we HAVE TORCH!!!! Thanks to araemo for finding the fix, we now have fully functional torch that is included in the package. I have removed the other flashlight app from the package as we do not need it now. Thanks again araemo! Fixed how the search key is referred to so you can set the hardware key options for it now and they will work. Also, as always... merged latest cm source. (coming shortly)
CM10 Changelog
All of the source code for PA/CM builds can be found Here: My Github

You're a Hero man!

Wait is over......
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Wow, that's greats news, downloading, thanks sir you're amazing....
Sent from my SGH-I997 using xda premium

kalebdevil said:
Wow, that's greats news, downloading, thanks sir you're amazing....
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Just remember that this is a work in progress and all that works now is it boots up and you can navigate using 2 finger technique..

this is AWESOME news to start my work week!!! thank you sir!!

awesome! ill give it a try tonight when i get home. thanks for the effort man!

Roger that... just for fun
Sent from my SGH-I997 using xda premium

Good job Scott. Might have to get my infuse out tonight just to flash this.

scottx . said:
Good job Scott. Might have to get my infuse out tonight just to flash this.
Click to expand...
Click to collapse
Well if your going to bust out your infuse just for this, you may wanna give it a couple days... Hopefully by that time ill make some additional progress.

Have yet to try this, maybe when I get home... gotta see what's going on (and not going on).
Have to look at the JB source and see where search gets its info from for G Now... stub? Data? I know its linked in the kernel because it won't work in ICS for that reason.
Excellent work Scott, I know you're gonna get a lot of love for this.
Sent from my SGH-I997 using xda app-developers app

Congrats on the progress with this Scott. I know you've been working hard on this, and what you and others find here will give a nice head start for when CM10 is ready. A luxury we didn't have when ICS came out. I haven't been following this as close as I should. Are you documenting what you are doing somewhere so the community can see and help with the process?
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

jscott30 said:
Congrats on the progress with this Scott. I know you've been working hard on this, and what you and others find here will give a nice head start for when CM10 is ready. A luxury we didn't have when ICS came out. I haven't been following this as close as I should. Are you documenting what you are doing somewhere so the community can see and help with the process?
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks man i appreciate it. I did list briefly what I did... If i went in depth with exactly what i did, it would take me hours. Ill summarize it the best i can.
I synched the CM10 repo and the aries common files for CM10 that dustin provided.
I then Merged in The Infuse files from entropy's github.
I had to edit a bunch of the .mk script files in order to get the build to start correctly for the infuse.
Once i started building from CM10 source with the infuse included, i encountered numerous errors throughout, but was able to work around them.
The build almost finished, but was unable to create the zip and some of the files did not get created correctly.
Id say I had about 70% of the files correct.
So what i did.. Was take the MKalter V0.45 (or whatever is named) JB ROM and extracted the contents.
I copied over everything from the system folder and pasted into my working folder.
I made sure to use the boot.img with the edited ramdisk.img for our device.
I Then took the 70% of the files that i built from source and pasted them to replace almost all the mkalter files.
I also verified that major components such as gps, camera, hw, things like that were from the infuse.
Some of the files i needed to copy from the latest Infuse 7/10/2012 CM9 build that i created.
Thats all...
I am going to start a new build tonight and see if i cant do a little better and hope that i get more system files to use.

You're the man! thank you.

Sent from my SAMSUNG-SGH-I997 using xda premium

scott.hart.bti said:
Thanks man i appreciate it. I did list briefly what I did... If i went in depth with exactly what i did, it would take me hours. Ill summarize it the best i can.
I synched the CM10 repo and the aries common files for CM10 that dustin provided.
I then Merged in The Infuse files from entropy's github.
I had to edit a bunch of the .mk script files in order to get the build to start correctly for the infuse.
Once i started building from CM10 source with the infuse included, i encountered numerous errors throughout, but was able to work around them.
The build almost finished, but was unable to create the zip and some of the files did not get created correctly.
Id say I had about 70% of the files correct.
So what i did.. Was take the MKalter V0.45 (or whatever is named) JB ROM and extracted the contents.
I copied over everything from the system folder and pasted into my working folder.
I made sure to use the boot.img with the edited ramdisk.img for our device.
I Then took the 70% of the files that i built from source and pasted them to replace almost all the mkalter files.
I also verified that major components such as gps, camera, hw, things like that were from the infuse.
Some of the files i needed to copy from the latest Infuse 7/10/2012 CM9 build that i created.
Thats all...
I am going to start a new build tonight and see if i cant do a little better and hope that i get more system files to use.
Click to expand...
Click to collapse
Fyi... I'd like to add... about 50% of the bin files were from mkalter rom...
if I stop the build before it tries to finish tonight I should be able to grab all the infuse cm10 source bin files. If that's the case I think we should make some progress as it will obviously eliminate the mkalter bin files... let's keep our fingers crossed.

This thread will be stickied for a while.
Good luck with the project,
YZ.

Nice work Scott - great progress!
I'm looking forward to seeing where you take this.

zen arcade said:
nice work scott - great progress!
I'm looking forward to seeing where you take this.
Click to expand...
Click to collapse
mind is blown!!!

Thank you all for your support. It makes all the hard work ive put into this the past 3 days worth it. I think i found a nice starting point on the whole needing to use 2 fingers on the touch screen issue... Im going to try to swap a few files, and if that doesnt work, im going to have to go kernel editing... let the fun begin. Ill start on this tonight after work and keep everyone posted. Thanks again for the support.

[2ndboot][04-10-2012] Custom kernel... this time with radio

It seems that finally I was able to boot custom kernel with working radio
It's not very stable yet(it stops/crashes at bootanimation quite frequently), and is quite laggy just after boot, but once it boots it seems to be almost usable. Wifi works, sdcard also. Haven't checked bluetooth.
Credits for this goes to:
* milestone1 devs... for sharing 2ndboot source code and providing so much info regarding milestone1/2 phones
* Motorola ... for providing source code(not fully working, but was a great help anyway) for enabling UART over micro usb for debugging purposes(without this I woudn't make any progress)
* tezet... for making quite good roms used by 2ndboot
If you wish to try it(BEWARE THAT IT MIGHT BRICK YOUR PHONE, SO DON'T SAY THAT I HAVEN'T WARNED YOU ), then do as follows:
1. Install tezet's JB10(if you don't have one already).
2. extract 2ndboot.tar(attached) into /data folder, check that /data/2ndboot/hbootuser file has execute permissions.
3. overwrite /system/bootmenu/script/2nd-boot.sh(DON'T TOUCH 2nd-init.sh!!!) with the one from tar(2nd-boot.sh.tar) and check it has execute permissions.
4. reboot into bootmenu
5. change the default boot method to 2ndboot
6. Restart your phone. Most likely it will crash few times at bootlogo, but be patiant, it finally should boot
7. If you wish to get back to 2nd-init, then enter bootmenu again and change default boot method back to 2nd-init, or manually boot 2nd-init
Click to expand...
Click to collapse
Please let me know if someone actually run it and was able to boot(so that to find out if I haven't forgot to include some more files(see changelog for 03.10.2012)
KNOWN LIMITATIONS
Boots very sloooowly
Its' quite laggy just after boot.
GPS does not seem to work yet
Click to expand...
Click to collapse
CHANGELOG
01.10.2012 - corrected battery problems(thanks to Quarx and kabaldan)
03.10.2012 - corrected ramdisk(previous one was calling some script which I forgot to attach to this post, new one has this script inside), so that now you should be able to boot it; updated instructions how to install it; enabled TLS in the kernel(thanks to kabaldan)
04.10.2012 - touch driver updated, now should work with lastest JB(thanks to Eleanor_Ir, Quarx), adb fixed(I hope, stability fix(thanks to Quarx)
Click to expand...
Click to collapse
NOTES for devs
In milestone2(as probably in many others UMTS phones made by Motorola) the BP is somehow very sensible and does not like to be disconnected/reenumerated. The main goal of this 2ndboot is then to not allow it to be disconnected. To do this, in the new kernel I've skipped a few resets(EHCI, TLL, individual port resets), and instead of enumerating BP, I've used the hardcoded usb device address(which for milestone2 seems to be equal to 2).
I attach patch(radio.patch) with the changes I've done to the kernel sources from here:
http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/
This seems to work(sometime) for both milestone2 and defy.
For other motorola phones:
1. First of all, check with lsusb what's the address and vendor/product id of your BP(for milestone2 it's 0x22b8 and 0x40e6).
2. If the BP usb device address is 2, then just apply the patch(probably it will need some small modifications), and check if it works.
3. If the BP usb device address is not 2, then edit usb/core/hub.c function hub_port_init(providing that it's there for your kernel), and replace 0x02 in the place where usb_control_msg to get descriptors is sent with address of your device
If it does not work, then you can try the following:
Create a procedure to send usb GetDescriptors request using omap3 ehci registers, and call it at different boot stages/usb initialization stages to find out how long the radio remains attached, and comment/change appropriate fragments of kernel code, to preserve this until usb port is initialized. If you wish, I can share the procedure I've written(in the patch file this is that czecho_get_descriptors called in many places) for milestone2, but it probably would need some modification to work with your device).
2ndboot module sources are here:
https://github.com/czechop/2ndboot

Wow, thats perfect This could bring M2 development to another level.
Holding thumbs up and keep it up!

Great news! Thx for your work. I've just bought an OTG cable to start playing with kernel stuff and here's a surprise

Fabulous! That means it starts a new era in the development of our MS2 Roms!

Wonderful job man

Brilliant
Sent from my A953 using Tapatalk 2

I'm gonna try on the Motorola Bravo as soon as PA is done uploading. Hopefully this'll work on Froyo kernels as well :fingers-crossed:
What kernel are you using? A recompiled MS2 GB kernel unmodified?
Awesome job man. This could possibly be the start of a new generation of roms for our common platform if this works on other similar phones like the Defy\Bravo. Only time will tell .

Well good work OP, can this be implemented on other Moto phones like Defy?

Great work !
I see that your work is based on Moto's Linux kernel (2.6 branch as far as I remember...)
Any hope of using another kernel source one day ?

Great News!, Thanks
Waiting for source code

Wow! Tezet and Quarx on the same thread?! I feel like up on the Mount Olypmus lol
Great job, man!...been following your work from General section.
P.S. add Kabaldan to the list Clash of the Moto Titans

skeevy420 said:
I'm gonna try on the Motorola Bravo as soon as PA is done uploading. Hopefully this'll work on Froyo kernels as well :fingers-crossed:
What kernel are you using? A recompiled MS2 GB kernel unmodified?
Awesome job man. This could possibly be the start of a new generation of roms for our common platform if this works on other similar phones like the Defy\Bravo. Only time will tell .
Click to expand...
Click to collapse
Yes, I use MS2 GB U6_4.1-22(http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/) kernel... but with modified usb host driver.

nidhish91 said:
Well good work OP, can this be implemented on other Moto phones like Defy?
Click to expand...
Click to collapse
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning

czechop said:
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning
Click to expand...
Click to collapse
XT720 users also waiting for instructions for new kernel tuning, cause we have working 2ndboot without radio. =)

boorce.com said:
Great work !
I see that your work is based on Moto's Linux kernel (2.6 branch as far as I remember...)
Any hope of using another kernel source one day ?
Click to expand...
Click to collapse
It should be easy to apply some(perhaps most) 2.6.32 upstream patches to the motorola kernel sources.
Don't know however how difficult it would be to start from another kernel version. Don't know also how motorola proprietary modules/libs would behave with newever kernel version. But, as they say, impossible is nothing

czechop said:
I think it can be.
With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning
Click to expand...
Click to collapse
In kernel only modified usb driver or some more changes for boot?

fjfalcon said:
XT720 users also waiting for instructions for new kernel tuning, cause we have working 2ndboot without radio. =)
Click to expand...
Click to collapse
Will share source code probably early next week(currently am at work, and during weekend most likely won't be sober enough

Quarx said:
In kernel only modified usb driver or some more changes for boot?
Click to expand...
Click to collapse
In 2ndboot module I've added code to disable lcd before starting new kernel(otherwise new kernel could not initialise properly dss), and in new kernel I've only modified usb driver(perhaps more things will need to be modified, as I'm facing problem with BATTD sayins something about power ic fail, BTW, does someone know what that could mean?), so that it skips restaring EHCI, TLL and don't start enumeration, but just used the old usb device address(assigned by the original kernel), which for M2 is always 2(at least during my tests).

I2c Fail can be caused by wrong permissions for /dev/cpp*
I tried your prebuilt binaries on defy http://pastebin.com/jKjQ2ykn
Black screen + buttons lights and reboot after ~20sec

Quarx said:
I2c Fail can be caused by wrong permissions for /dev/cpp*
I tried your prebuilt binaries on defy http://pastebin.com/jKjQ2ykn
Black screen + buttons lights and reboot after ~20sec
Click to expand...
Click to collapse
Thanks for hint regarding permissions...will check that
Regarding prebuilt binaries on defy, hard to say what's wrong(not sure how much the phones differ). Anyway, you probably would need to use devtree from your device. Also you could unpack ramdisk, and check the init.*.rc scripts if they are ok(e.g. I mount system partion using p21, not sure if that's the same for defy, and staff like that).

[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 !!

[ROM][7.1.2_r36][grouper][OC 1700MHz/F2FS]Resurrection Remix 5.8.5 for Nexus 7 2012

*** Disclamer
By downloading and installing this ROM you agree that you do so at your own risk, and that you understand that it probably voids your warranty. Installing this ROM may distroy your device, you may loose your data, your money, your friends, ...
If you are not sure what you are doing - leave it!
Introduction
I like Resurrection Remix but i could not find find it here, so i tried to make it on my own.
Here is the result - on my Nexus 7 it works, but i dont use it very much.
If you want to overclock your device (up to 1700MHz) you can change you kernel settings - use "Kernel Adiutor"
About me
I am not a developer! I just build it or fun and because i want to use it. Don't expect much support from me - my time is limited.
Installation instructions
Be sure you are on the latest TWRP https://dl.twrp.me/grouper/ or on the last CWM (Google for it)
Back up your data
Download ROM from link below
If you want to use Google Apps (openGAPPS):
Download GAPPS from http://opengapps.org/ Platform=ARM, Android=7.1, Variant=pico
Download gapps-config.txt (attached). Without removing something - configured in gapps-config.txt - you do not have space to install GAPPS in system partition
Put all files in the same directory
Wipe system, cache, dalvik, data (only for the first install)
If you like you can change the filesystem of the partitions "cache" and "data" to F2FS. Do not change "system" partition !!!
Install the ROM and optinal GAPPS.
Reboot into system - first boot may take 5 ... 10 Minutes!
Enjoy
Video by @Majid2000 uses CWM-Recovery.
If you want to root your device:
You have to add a root manager to root your device - there is no root by default.
Option 1: Look for Magisk on XDA and install it
Option 2: Install SuperSU or any Superuser
Only versions from July 2017 onwards come without "root".
If you want to add Googleapps:
With default settings it will give an error about insufficient space. To avoid that, take the smallest Gapps package you can get. I recommend opengapps.org (select Platform:ARM Android:7.1 Variant: pico).
The easy way:
Attached you will find my "gapps-config.txt" file. Feel free to change it to your needs. The name must be "gapps-config-grouper.txt" or "gapps-config.txt"
Copy this file to the same directory as you have your opengapps.zip file. The opengapps updater-script will look for it there when you install opengapps.
Pay attention: This script will remove some system apps from your device. If you still need them do this steps before installing gapps:
1) root your device or use twrp to execute following steps
2) copy all needed apps from /system/app or /system/priv-apps to any non /system directory (/data or external storage may be a good idea)
3) install gapps
4) install saved apps (you may need to change your settings to allow install of apps from an unsafe place)
You have to repeat it on every clean install or if you want to updete your apps with a fresh version.
Backgroundknowledge:
You have to deinstall some packages:
The easiest way is to follow these instructions:
https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
My file gapps-config.txt contains this:
Code:
DialerFramework
PackageInstallerGoogle
CMAccount
CMUpdater
CMSetupWizard
CMAudioFX
CMFileManager
CMMusic
CMScreenCast
CMWallpapers
CMWeatherProvider
BasicDreams
DashClock
Galaxy
Hexo
HoloSpiral
PhotoTable
CalculatorStock
FMRadio
Gallery
Gallery2
LiveWallpapers
MMS
PicoTTS
VisualizationWallpapers
GoogleTTS
(NexusLauncher)
(Eleven)
(Email)
(Contacts)
(Jelly)
(AudioFX)
(Calendar)
(ExactCalculator)
MusicFX
LockClock
Terminal
LRecorder
SoundRecorder
StorageManagerStock
LiveWallpapers
Studio
WhisperPush
ClockStock
Reboot.
WAIT for system to settle before you decide it is slow. Some of the app optimization which used to happen during initial boot now seems to happen in the background. When it's finished, responsiveness will improve.
Kernel settings
The kernelspeed is set to 1300Mhz by default. If you want more you have to change it. Use "Kernel Adiutor" or any tool of your choice.
Accordding to the architecture of the CPU the maximum speed is 1500Mhz if running in multikernel mode. If running in singlekernel mode it can go up to 1700Mhz. If you want maximum speed use 1700Mhz even this speed is mark as unused in monitoring tools. You are allways in multikernel mode if your display is on - use with care!
ZRAM is enabled by default.
CPU-Voltage is editable so u can undervolt if you like - use with care!
Download
Build 16.12.2917 (RR 5.8.5):
with December security patches.
androidfilehost
Build 20.11.2017 (RR 5.8.5):
With November security patches.
Google-Drive
androidfilehost
------------------------------------
Historical versions:
------------------------------------
RR 5.8.4:
Androidfilehost
------------------------------------
RR 5.8.3:
Androidfilehost
Note: From this version on there will be no root manager included.
------------------------------------
RR 5.8.2:
Androidfilehost
------------------------------------
RR 5.8.1:
Androidfilehost
---------------
RR 5.8.0:
Androidfilehost
--------------
Credits / Thanks
Google / AOSP
CyanogenMod / LineageOS
Resurrection Remix
@aaopt: I took the basics from his thread https://forum.xda-developers.com/nexus-7/development/rom-lineageos-14-1-nexus-7-2012-t3530261
@AndDiSa https://github.com/AndDiSa
https://github.com/aperomsik for his device tree
@daniel_hk for the DC-Kernel from his Github
@1lyharry for gapps-config.txt
and all the others who helped to keep our device alive and up to date
Known bugs
thumbnails in gallery show wrong colours - see attached screenshot -affects all ROM on my Nexus 7 started with Android 6
Problems with Bluetooth keyboard were reported

If you like to build it on your own, here is a brief instruction (for detail instructions use the web, there are plenty of them):
Make sure your system is set up to compile Android and your crosscompiler works and is in your env.
Setup Resurrection Remix: [url]https://github.com/ResurrectionRemix/platform_manifest[/URL]
Add a file ".repo/local_manifests/roomservice.xml" inside your RR directory with the content from [url]https://github.com/wilmsn/android_manifests/blob/cm-14.1/grouper.xml[/URL]
Add this to your ".bashrc"
Code:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
Then call
Code:
repo sync --force-sync
. build/envsetup.sh
make clobber
brunch grouper

Version 20170323:
March security patches
Merged kernel changes from @AndDiSa (thanks for your work)
Version 20170225:
RR System:
Upgrade to RR Version 5.8.2 with February security patches
Version 20170209:
Kernel:
Overclock and governors implemented (from former OC kernel). Kernel starts with 1300Mhz, if you want higher speed you have to change it.
ZRAM enabled by default.
Voltage table is editable now.
RR System:
Upgrade to RR Version 5.8.1

Nice! Testing right now
Edit: just installed. Smooth and with the 5th Jan security issue. Thanks!
Edit: after two days use, there are a couple of minor issues I've found. Just to say:
- The screen brightness seems to blink sometimes. Besides, if you adjust the screen brightness through the status bar swiping, the behavior is not perfect. Sometimes the screen get turned off Edit 2: I'm retarded and I had the auto brightness feature turned on
- Force close apps are sadly common when trying to start an app. However, restarting that app normally works. If the FC persists, switch the orientation of the tablet.

@wilmsn, did you have to do anything special to build the ROM? I'm building it by myself and I succeeded with your recipe, but it seems that
- My build is a bit slower than yours in terms of runtime performance. It's only an impression
- mp4 files won't play. VLC does not work at all, and internal video player only will play the audio tracks on these video files
Thanks!!
Edit: never mind, it seems that I configured something (I don't know what) in the improper way. Reinstalled my self-built ROM and mp4 files are being played properly .

@pacorrop
I use:
Code:
Pkg.Desc = Android NDK
Pkg.Revision = 13.1.3345770
and set this in my .bashrc:
Code:
CROSS_COMPILE=/home/norbert/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Hope it helps!

Might I make a suggestion?
You may want to see if you can integrate DC-Kernel into this rom. I use this kernel all the time on my grouper and love Ressurection Remix. But the two don't play nice together currently. I would love to have the option to Oveclock and all that with this Rom.
If not, no worries. Rom is running rather well as it sits, would just like to have the added boost if needed.
Thanks for reading. Keep up the good work.
Thanks for reading

The~Skater~187 said:
Might I make a suggestion?
You may want to see if you can integrate DC-Kernel into this rom. I use this kernel all the time on my grouper and love Ressurection Remix. But the two don't play nice together currently. I would love to have the option to Oveclock and all that with this Rom.
If not, no worries. Rom is running rather well as it sits, would just like to have the added boost if needed.
Thanks for reading. Keep up the good work.
Thanks for reading
Click to expand...
Click to collapse
I will try to build it - so stay tuned ...

wilmsn said:
I will try to build it - so stay tuned ...
Click to expand...
Click to collapse
Thank you. I'm working on syncing sources myself because I was going to try to get it working. But I'm extremely New to kernel development
Resurrection-Remix5.7.4 Boeffla/Venom powered SM -G900P

DC Kernel added
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
 @The~Skater~187 hope you can use it - i did only a quick test.
Norbert

wilmsn said:
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
@The~Skater~187 hope you can use it - i did only a quick test.
Norbert
Click to expand...
Click to collapse
Thank you. I will flash and report back.
Sent from my Nexus 7 using Tapatalk

wilmsn said:
I just added DC-Kernel to OP. You can overclock the device up to 1700MHz.
Use with care and on you own risk.
@The~Skater~187 hope you can use it - i did only a quick test.
Norbert
Click to expand...
Click to collapse
How did you go about flashing? I keep getting stuck at boot animation. Been there for about ten minutes now?

The~Skater~187 said:
How did you go about flashing? I keep getting stuck at boot animation. Been there for about ten minutes now?
Click to expand...
Click to collapse
Strange .... I just use rashr => flash kernel from storage and then reboot wait about 2 Min. or so in Google animation. After that RR animation

wilmsn said:
@pacorrop
I use:
Code:
Pkg.Desc = Android NDK
Pkg.Revision = 13.1.3345770
and set this in my .bashrc:
Code:
CROSS_COMPILE=/home/norbert/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Hope it helps!
Click to expand...
Click to collapse
Thank you very much!
It's weird because, as far as I know, I don't have the NDK installed how am I able to compile? Geez :laugh:

wilmsn said:
Strange .... I just use rashr => flash kernel from storage and then reboot wait about 2 Min. or so in Google animation. After that RR animation
Click to expand...
Click to collapse
Got it working, thank you. Only thing I've noticed over the last day or two is that any kernel tweaks such as over clock or changing of governors don't seem to stick. Tried with many different apps and as soon as you close the app, it all goes back to default.
Sent from my SM-G900P using Tapatalk

The~Skater~187 said:
Got it working, thank you. Only thing I've noticed over the last day or two is that any kernel tweaks such as over clock or changing of governors don't seem to stick. Tried with many different apps and as soon as you close the app, it all goes back to default.
Click to expand...
Click to collapse
The only thing i use is overclocking. On my N7 OC works fine up to 1500MHz. If i go to 1600 or 1700 it is taken from the system but if i look at the statistics it runs only at 1500. I can change the governor and when i look it up it is still set to the right value.
The rest is DC kernel with no changes.
You are sure you gave root access to the tools you use?
BTW: I use kernel adiutor to change settings.

wilmsn said:
The only thing i use is overclocking. On my N7 OC works fine up to 1500MHz. If i go to 1600 or 1700 it is taken from the system but if i look at the statistics it runs only at 1500. I can change the governor and when i look it up it is still set to the right value.
The rest is DC kernel with no changes.
You are sure you gave root access to the tools you use?
BTW: I use kernel adiutor to change settings.
Click to expand...
Click to collapse
I tried kernel auditor myself, don't seem to stick. I'll give it a try again. I've recently been trying to use the performance control app DanielHK recommends for dc kernel. I did check to make sure all kernel as I've tried had root permission.
Sent from my SM-G900P using Tapatalk

Fantastic and I cannot say that enough!! I do have a remedial question as I have been out of the AOSP Roms for some time. I cannot get the Gapps to work. I used the pico and followed the steps. I am still have the same error and when. It boots back up they are not there. Can you help please?

hackwoof said:
Fantastic and I cannot say that enough!! I do have a remedial question as I have been out of the AOSP Roms for some time. I cannot get the Gapps to work. I used the pico and followed the steps. I am still have the same error and when. It boots back up they are not there. Can you help please?
Click to expand...
Click to collapse
Did you do a full wipe (system and data) bevor installing?

wilmsn said:
Did you do a full wipe (system and data) bevor installing?
Click to expand...
Click to collapse
Yes sir. I followed everything as closely as possible. I'm not sure where I made my error. Is there an easier how-to for the Gapps maybe there's something I'm missing? Again I'm coming back to AOSP after many years and definitely different.