Database Develop

[ROM] AOKP 4.2.2 milestone1 [July-20] - HTC Vivid, Raider, Velocity

AOKP (Android Open Kang Project) Milestone1 - Jellybean 4.2.2
{
"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"
}
Updates:: Here is AOKP milestone1 (Android 4.2.2) built from source using my CM repos and kernel. Should run about just as well as the CM version with all of the same bugs or lack there of
Screenshots
Installation Instructions
Requirements
* Rooted (obviously)
* A brain
Installation
1: If you are coming from another ROM do a full wipe
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
1b: if your device is S-ON you must flash your boot.img either with fastboot or some type of GUI program EVERY FLASH (google is your friend)
2: Flash gapps (download below)
3: Reboot
4: Enjoy AOKP
Please read the whole post for changelog, Download links, and other important info
. As always: remember it takes a FULL charge from AC, and a full discharge then re charge batteryt to be accurate. Also leave it plugged in for up to an hour at 100%, Another thing i find helps battery life is to make custom auto-adjustment values if you use auto-brightness. Check below for full changelog Feedback always welcome Please read the Kernel section for more info and full config options for the kernel.
Albinoman887
Working
SMS/MMS
Wi-FI
Data
GPS
Audio
Radio
Camera
Google Now
Internal/External SD card
Bluetooth
H/W Accelerated Video Playback
Native Wi-Fi Tethering
1080p Video Recording
Not Working
????????????
Changelog
July-20
* Synced with upstream - maybe gallery issue will be fixed?
July-18
* initial build
Kernel
ChronicKernel
* Compiled with linaro
* Set flash to disable if battery is below 10% to prevent the random shut-off when taking a pic
* Removed/Disabled KSM
* Removed ZRAM
* User-configurable GPU OC (Not OC'd by default)
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* Reverted CRT hack to smooth animation in Android 4.2.2
* Increased PMEM_MDP as it is needed in Android 4.2.2 to fix soft-reboots
* PM_FAST enabled by default (high power wi-fi when screen is off)
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. If you want more features of the Sultan kernel feel free to flash it, but support will not be provided in this thread.
Other Features of the kernel include:
* OC to 1866Mhtz (default 1566Mhtz)
* Undervolted
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = SIO)
* User-configurable badass gonvernor (default = balanced)
* Sweep2Wake
You can edit many of the settings in /system/etc/init.d/99kernel, here is a snippet of the script with all the config options
Kernel init script: Click Show Content to expand
Code:
#Script originally made by Axetilen. Modified by Sultan (android1234567)
#Updated for albinoman887's ChronicKernel (98% of the credit goes to android1234567. Thanks so much man :)
# Configure your options here #
# Config default CPU Gonvernor (Disabled by default: When disabled uses internal Kernel setting)
# For better battery life switch to badass
# Kernel Default: ondemand
# Possible values
# badass
# ondemand
# interactive
#= lagfee
# performance
GOV=ondemand;
# Config I/O scheduler
# deadline
# cfq
# noop
# vr
# sio (default)
IO=sio;
# Config CPU max frequency
# Default: 1566000 (1566Mhtz)
# Overclockable to - 1836000 (1836Mhtz)
# for badass set to 1566mhtz (best performance/battery life)
MAXFREQ=1566000;
# Config CPU min frequency
# Default: 384000 (384Mhtz)
# Range 384000 - 1944000 (384Mhtz - 1944Mhtz)
MINFREQ=384000;
# Config 3D GPU clock
# 228571000 = 228mhz
# 266667000 = 267mhz (default)
# 300000000 = 300mhz (Recomended For balance of Performance and Battery life)
# 320000000 = 320mhz
GPU=266667000;
# Config 2D GPU clock
# 145455000 = 145mhz
# 160000000 = 160mhz
# 200000000 = 200mhz (default)
# 228571000 = 228mhz (Recomended For balance of Performance and Battery life)
# 266667000 = 267mhz
DD=200000000;
# Badass
# possible values
# 1 = performance
# 2 = balanced
# 3 = battery saving
BADASS=2
# Enable Sweep2Wake
# 0 = disabled (default)
# 1 = enabled
# 2 = enabled (with no button backlight during sweep)
SWEEP=0
# Enable Fastcharge
# 0 = disabled
# 1 = substitute AC to USB charging always
# 2 = substitute AC to USB charging only if there is no USB peripheral detected
FASTCHARGE=0;
# Fsync Control
# Disabled by default (recomended)
# 2 = Fsync disabled
# 1 = Fsync enabled
FSYNC=2;
# TUN
# Disabled by default
# 0 = Disabled
# 1 = Enabled
TUN=0
# End of configurable options #
Please note this is not the full script just a small portion, Check /system/etc/init.d/99kernel for the full script
Bugs
* MHL doesn't work
* Sweep2wake sometimes causes issues with the proximity sensor during calls
Notes
* As of AOSP 4.2.2 ADB now has a whitelist feature. On first connect with adb it will say device offline You need to update your ADB then with the phone connected. Disable and Re-Enable Android Debugging in the Developer Options menu. It will ask if you want to accept and show the PC's RSA key. Select Yes and it will now work as expected
* As of AOSP 4.2.1 Developer Options and Performance setting menu options are hidden until you go into about phone and tap build number repeatedly (aprox. 6 times) this only needs to be done once
* If you are having a lot of soft reboots when waking the device set you min CPU freq. to 384htz in Performance settings. (What? no Performance settings? ummm look up hehe)
* If you are coming from another ROM i highly recommend you perform and Wipe Date/Factory Reset in recovery menu when applying this ROM.
* The gapps linked to does not have photosphere. As far as i know it's not supposed to. If you want photophere search for the flashable zip
* If you can't get MMS to work. Send yourself a MMS. or just wait a day. eventually they will work again
* For the best battery life I suggest the stock settings with the exception of the ONDEMAND governor. Switching to BADASS will yield best battery results
DOWNLOAD
ROM : aokp_holiday_Albinoman887_2013-07-20.zip
Gapps : gapps-jb-20130301-signed.zip
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *
Source Code
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/AOKP
Credits
* android1234567 for getting this porting project going, it was a joint effort between us to get this going
* billibox for his relentless testing
* of course cyanogen, the CyanogenMod project and all who contribute.
* The AOKP project and all who contribute
* And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
* dastin1015 for answering all my n00bish questions, and providing helpful hints and solutions
* android1234567 for all the help with the kernel, without you we wouldn't have new kernel
* tarfu for fixing camera p2z
* NLJ for fixing the Sweep2Wake proximity sensor issue
* A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
Donations
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
For more information, like kernel info (and possibly newer kernel builds) from our kernel chef android1234567 read the 2nd post
Happy Flashing
Albinoman887

Reserved

Too much ROMs omg good work albino and bili
Sent from my Vivid 4G using xda premium

lol

Since these ROMs all seem to be the same, this one have a center clock? Only thing I don't like about CM
Sent from my Vivid 4G using xda premium

joe3681 said:
Since these ROMs all seem to be the same, this one have a center clock? Only thing I don't like about CM
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
What do you mean? And these Roms are very different.

camo_flage said:
Too much ROMs omg good work albino and bili
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
If you think this is too much you're in a whirl of trouble my friend....

Can't even turn on WiFi
Sent from my Vivid 4G using xda premium

joe3681 said:
Can't even turn on WiFi
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
Did you flash boot img??

No. I'll try that. Works without flashing on other roms
Sent from my Vivid 4G using xda premium

NIiice
OT:
I was trying myself to sync the AOKP repos a few weeks ago (when you had first got CM10.1 up) but it ened up freezing half way through some 20 million lines of w.e it was doing and after like 70gb of w.e. was downloaded. I gave up after hours of nothing happening lol.
So am I glad that a dev came through on this thank you! I really dont know how you even keep all that source stuff straight..I am no noob with computers by any means but jeez lol thats some confusing-ness.
ROM REPORT:
So, first build aannnd....its AWESOME! So far everything works as expected. So far no reboots (knock on wood), sound, data, wifi, calls, etc. work great. Seems smooth and very stable (in the few hours I have been testing).
THANKS:
Thank you thank you for helping the few of us left. And they said we couldn't have CM10 because of mic...if we just had these devs when phone came out, I think it would have got way more spotlight. Which is quite sad because I think this phone is one of the nicer on the market (for a 2011 phone).

Thanks, and no problem
Sent from my SGH-M919 using Tapatalk 2

another good rom, much faster then pac, and a little faster than cm10.1, and what i like - it just works)
albinoman887, thank you very much for your work)

I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?

ulsigem said:
I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?
Click to expand...
Click to collapse
My DU rom does the same thing I believe. Albino and I are talking about it
EDITED!: Don't listen to whatever i posted before this was edited
I'm a crazy tired guy xD We will see whats up

ulsigem said:
I am having a bit of a problem with the gallery app. I did flash the correct one for this version of jellybean.(gapps-jb-20130301-signed.zip)
It can't find my other photos and the app force closes after selecting "details" on a newly taken picture.
I can open my other photos by opening them through the file manager and selecting gallery. Anyone else experiencing similar problems?
Click to expand...
Click to collapse
I am thinking so.
I had a weird one happen too. I think maybe I took a few pictures, had dropbox installed and setup to transfer instantly to my account. After a few shots, dropbox just started FCing along with a system.media FC. I could not even log in to dropbox after that, it kicked me out and FC any time I hit log in, along with the media FC.
I tried clearing data of the app, no go. Tried wiping dalvik in recovery. No go. Then noticed all my photos were missing in gallery before my few pictures I took with this build (I only saw those few pics). I thought weird, I hope they didnt get deleted during install of ROM. But nope, I flashed the sense 4.1 backup I had (its the most stable I got) and everything went back to normal, all pics were there, dropbox works fine, no FC.
I think something is indeed weird with the gallery. 'IS' anyone else having any issues too?

i know it sounds dumb but anyone try redoing permissions? either with "fix permisions" or just running chown -R 1000:1000 /sdcard/ and then chmod -R 644 /sdcard/
if not... try taking the gallery2.apk from cm and see what happens

bilibox said:
My DU rom does the same thing I believe. Albino and I are talking about it
EDITED!: Don't listen to whatever i posted before this was edited
I'm a crazy tired guy xD We will see whats up
Click to expand...
Click to collapse
sorry for offtopic, but.. can you build aosp? (just 4.2.2 without any options.. like vanilla android on nexus devices?) (+root)

kkruglov said:
sorry for offtopic, but.. can you build aosp? (just 4.2.2 without any options.. like vanilla android on nexus devices?) (+root)
Click to expand...
Click to collapse
Ill look into it in the morning

i'll be updating this rom sometime today....just got a lot to compile

Related

Code:
#include <standard_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to use these modifications upon your own choice, and if
* you point the finger at me for messing up your device, I'll just sit and laugh at you.
*/
​
FEATURES
1- Using Brain F*ck Scheduler (BFS) as default cpu task scheduler. It should give perfomance boost in 3d games and benchmark as the way BFS works is to give higher priority to any given task that request more resource from the cpu.
2- SIO as default io scheduler used. Previously use noop but maybe noop is too simple. Yes its the fastest but too simple, in rare occasion where phone shutdown improperly maybe will result in data loss, but noop is still included as choices for anyone who still adores it. v/r, deadline and bfq also included as alternative.
3. 2-way call recording enabled.
4- 10 cpu frequencies/steps which is
- 120000
- 160000
- 240000
- 320000
- 400000
- 480000
- 600000
- 670000
- 735000
- 800000
*** u can change these cpu frequency using NoFrills CPU Control or using SetCPU (need root) ***
5- added custom governor
- ondemandX
- interactive
- interactiveX
- smartsa**
- smarta**V2
- savagedzen
6- other small improvement taken from various source eg g3mod kernel, savagedzen kernel, franco kernel etc.
Click to expand...
Click to collapse
HOWTO USE/INSTALL
First and most important is u need to disable all autorun app or script that set cpu governor/frequency on boot eg nofrills, setcpu, cm advanced settings etc. Also u need to manually delete all mumbo jumbo script to prevent any compatibility issue with newer kernel before flashing. Download the zip attachment below, put it in sdcard, reboot into clockworkmod recovery and flash it. Tested with jusada's ics and grif_07's cm7 rc1. Starting from beta 1 THIS WILL NO LONGER WORKS WITH STOCK ROM OR CUSTOM ROM BASED ON STOCK
Click to expand...
Click to collapse
BUGS / ISSUE
None that i know of and can replicate myself. for the future dont report bug if u use my kernel with any scripts whatsoever. if u already deleted all the script and reboot, and the problem still persist then thats a true bug.
Click to expand...
Click to collapse
TODO
u tell me. give some suggestions
Click to expand...
Click to collapse
The zip file with "patch" name in it is not for you if you not a dev. dont download it.

FAQ
will this works on <insert rom name here> or <insert rom name here>?
if its pure aosp or cm7 rom or custom rom based on aosp or cm7, yes this will work. But if its stock rom or custom rom based on stock, no this will not work.
what is this ondemandx, interactivex, bfq, sio and **** that u mumbling all the time? I couldnt understand squat of those!
u can read here for better explanation and for further understanding of those things.
why my quadrant score suddenly drops using this?
does higher benchmark score means your phone becoming a speed demon and is "better" than all other phone here? *seriously yes this is my answer (or question) for above question*
would u be the father of my future babies?
sure why not
Click to expand...
Click to collapse
CHANGELOG
v 1.5
1. Add kernel-wide snappy compression library.
2. Add snappy compression API for crypto and make it default instead of lzo.
3. Tweak cpu governors.
4. Fix rate limit no-hz.
5. Add retries instruction in acpucock.c when lowering vdd level and axi clock.
6. Bluetooth code from 3.0rc6 kernel.
7. Added CPU-supported unaligned accesses and use it as default instead of software emulated alignment trap.
8. Tweak installer script.
v 1.4
1. 2-way call recording enabled.
2. Tweak lowmemorykiller using patch from cm.
3. Proportional rate reduction for TCP from Google patch.
4. Some TCP tweaks.
5. Fixed some kernel memory leaks.
6. Patch sched with rate-limit nohz.
7. Optimized lib/checksum.c
8. Wakelock fix.
9. Tweak page writeback and vm swappiness ratio.
10. Moved reset_modem.ko module to ramdisk and make it load automatically on boot.
11. Using AROMA Installer (aroma-nightly_1.60-120225-025b) and updated install script to do a little bit of cleaning before kernel flashing.
v 1.3
1. Updated kernel source from 2.6.35.7 to 2.6.35.14.
2. Readd bfs cpu scheduler and use it as default instead of default cfs.
3. Updated timer.c using patch from CodeAurora
4. Added Google's Snappy compression library & staging for zram compcache and use it as default instead of default lzo compression.
5. Enabled Kernel SamePage Merging (KSM).
6. Added optimized crc32 algorithm.
7. For devs, the updated sourcepatch is a clean patch and not incremental patch. I've modify build script (the make_kernel_GT-S5830.sh file) to make kernel building more pleasant and easy, it'll create a folder named "output" in the kernel source tree and after finish compiling, the zImage file along with all compiled module (*.ko) will be copied into that folder. Compiling also produce a log file named log.txt in that folder.
v 1.2
1. Revert previous 1% battery driver because it gives problem to many users
2. Revert previous axi bus underclock as some user said phone somewhat laggy with it.
3. Turned off most of kernel debugging that constantly spamming dmesg, should improve perfomance without those.
v 1.1
1. Rewrite battery driver to include 1% step that hopefully solve stupid jumpy battery issue.
2. Underclock axi bus
3. Using sio as default io scheduler
4. Added bfq io scheduler
5. Added savagedzen cpu governor and fine tune it to cope better with cpu freqs.
6. Using xz kernel compression which is better than previous lzma.
7. Updated zram compcache
8. Include wifi module so no more wifi error
v 1.0
1. Using samsung's source code as i cant seems to fix led backlight issue and add bln support if using teamhacksung's source.
2. Fix random led backlight issue
3. Added bln support
4. Added v/r and sio disk io scheduler
5. Fine tune deadline, v/r and sio io scheduler to suites flash memory better.
6. Fine tune ondemandx, interactivex, and smarta**v2 even more.
7. Lowered battery polling interval from 60 seconds to 30 seconds.
8. Fix that make phone poweroff correctly. Previous beta 3 if choose to poweroff phone when usb or charger is connected, phone just reboot into android again and not poweroff.
Beta 3
1. Fix native cm torchlight. It works now.
2. Use tiny preempt rcu as default.
3. Increase framebuffer ram size to 5mb
4. Fine tune ondemandx, interactivex, and smarta**v2 to cope better with freq steps.
5. Added "noload" kernel mountpoint option in ramdisk that supposedly mount ext4 filesystem without journalled.
Beta 2
1. Fix zram compcache, now it works.
Beta 1
1. Now supports cm7 or rom based on cm7, using kernel source from teamhacksung's github.
2. Revised frequency steps, now using only 10 because previous 14 steps make phone reboot with certain iosched.
3. Removed bfs cpu scheduler due to misbehaving with frequency steps, maybe will re-add later after further test.
4. Added autogroup cpu sched and make default on boot
5. Updated to jhash3
6. Using lzma kernel compression for smaller size kernel.
7. Added ondemandx cpu scaling governor.
8. Added stochastic fair blue (sfb) network scheduler.
9. Undervolt wifi driver a little bit.
10. Raise battery polling interval from 10 seconds to 60 seconds
alpha
1. Initial release
2. Using samsung's source
3. Using 14 cpu frequency
4. Added bfs cpu scheduler.
5. Use noop iosched as default disk iosched.
5. Added 4 cpu scaling governor; interactive, interactivex, smarta** and smarta**v2
Click to expand...
Click to collapse
CREDITS
Google for making android and for making it such awesome platform.
Samsung for this device and for releasing its kernel sourcecode
Codeaurora for many patches i've use
Teamhhacksung for many patches i've use
Ketut.kumajaya for helping me when i've got trouble with module mismatched and bln
amarullz for the amazing AROMA Installer script
<insert your name here if you feel i should also mention your name>
Click to expand...
Click to collapse
so thats it, i think got all sorts out. please dont ask stupid question like will this work on cm? will this work on this rom? will this work on that rom? i dare u to ask
{
"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"
}

an0nym0us_ said:
reserved for future and upcoming use.
Click to expand...
Click to collapse
same as above, again reserved for future use.

I would like to try....but I am waiting for ext4 and a2sd :/
Forever living in my Galaxy Ace using XDA App

looks cool....but its still in alpha,am gonna sit tight for the stable release...
+1 for the good work....

When you release a build that supports at least ext4 and a2sd I'll try any version .
Forever living in my Galaxy Ace using XDA App

EmoBoiix3 said:
When you release a build that supports at least ext4 and a2sd I'll try any version .
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
or maybe use rare filesystem like btrfs or reiserfs

an0nym0us_ said:
or maybe use rare filesystem like btrfs or reiserfs
Click to expand...
Click to collapse
*faints*
I don't understand . XD
Forever living in my Galaxy Ace using XDA App

Its will be great if you can include OC kernel

Does it work on CM7? And yes OC would be great...
Sent from my GT-I9100 using xda premium

edint3000 said:
Does it work on CM7? And yes OC would be great...
Bro.. please read the thread.. it was clearly mentioned that this is not for CM7..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Sent from my GT-S5830 using XDA App

if u choose to install my kernel on rom other than zckpa, i've added on first post wifi module that works (taken from zckpa). extract and move it to /system/wifi and give proper permission. now wifi should work. but do take note that its not advisable to use this kernel with other rom than zckpa, because its only tested with zckpa rom. whatever u choose to do, do it on ur own risk.

Diliban said:
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I wont argue with you here, but are you sure that it is stated on first page?
Take a look

FINALLY! I think this will add undervolt kernel in the future!
waitin' for CM7 port.
THANKS!

May I ask, having more frequencies available, is it better? More battery friendly I suppose, on interactive governors?
Anyway if ext4 is the most efficient filesystem yet, it'll be good to include the support! I hope you'll move towards voltage work

consegregate said:
May I ask, having more frequencies available, is it better? More battery friendly I suppose, on interactive governors?
Anyway if ext4 is the most efficient filesystem yet, it'll be good to include the support! I hope you'll move towards voltage work
Click to expand...
Click to collapse
yes, its obvious
i really hate how stock kernel just jump from 480 to 800, its almost halfway
btw my fav gov is smartassv2 now

have you found any bugs??

an0nym0us_ said:
yes, its obvious
i really hate how stock kernel just jump from 480 to 800, its almost halfway
btw my fav gov is smartassv2 now
Click to expand...
Click to collapse
I was following smartass v2 in other threads! Anyway, does Gingerreal use the same chinese firmware? I thought I read somewhere that his didn't have the call additional functions.

Do I need to have rfs or bfs before flashing? Because on stock kph, kpn , kpo I am stuck at the samsung galaxy ace pre boot screen. I'm also on ext4
Sent from my GT-S5830 using XDA App

Nope GR doesn't
Sent from my GT-S5830 using XDA App

*** NOTE: All kernels are now officially end-of-life (EOL).
Please do not expect any more updates for them in future, no maintenance and no bugfixing. ***
Hi all,
this is the thread about the well-known Boeffla-Kernel for the Samsung Galaxy S3 international.
Compatibility
Important: This kernel is only meant to be compatible with official Samsung Stock firmware and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Notes:
Never install it on CM or AOSP based roms!!!
Kernel version 5.x are only for Samsung based Jelly Bean 4.3.x roms!!!
Kernel version 6.x is only for ported Samsung based Kitkat 4.4.2 roms (e.g. Archiport) !!!
Kernel version 7.x is only for ported Samsung based Kitkat 4.4.4 roms (e.g. back-to-n00t) !!!
Kernel versions 1-4 are only for Samsung based Jelly Bean 4.1.x roms!!! (no development anymore)
For the CM Boeffla-Kernel, please go HERE.
If you have questions to settings, presets, others configuration and wanna share your configuration, head over to the unofficial Boeffla-Config App Config sharing thread:
http://forum.xda-developers.com/showthread.php?t=2621308
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Android 4.3 kernels: KLICK HERE
Change log for Android 4.4.2 kernels: KLICK HERE
Change log for Android 4.4.4 kernels: KLICK HERE
Features
* To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from here: DOWNLOAD
* Upstreamed to Linux 3.0.101 (www.kernel.org)
* Based on Samsung source code GT-I9300_JB_Opensource_Update13
* Initramfs from xxugml2 kernel
* CPU "soft" overclocking to 1500 or 1600 MHz
* CPU undervolting interface
* GPU frequencies configurable (underclocking, overclocking up to 700 MHz)
* GPU voltages configurable (undervolting, overvolting)
* Configurable zRam (Turbo zRam with up to 4 devices)
* Configurable touch-to-wake
* Configurable touch boost frequency
* Configurable early suspend time (for screen off animations, 100ms default)
* Configurable LED for fading mode, speed and brightness
* Configurable charger rate for AC, USB and wireless (default increased to 1100 mA for ac charging)
* Charging logic supports ignore unstable power and remove safety margin
* Charge information display support via Boeffla-Config V2 app
* Boeffla-Sound engine V1.6.5 to unleash the power of the Galaxy S3 audio chip
* Additional governors: zzmoove 0.7d, pegasusqplus, smartassv2 and lulzactiveq
* Governor profiles for pegasusq, pegasusqplus and zzmoove for performance, battery saving etc.
* Additional schedulers: ROW, ZEN, BFQ (v6r2) and SIO
* Schedulers configurable separate for internal and external SD memory
* Hardcore speedmod sharpness fix implemented (default is off)
* Black crush fix for better balanced display
* SD card read ahead buffer configurable separate for internal and external SD memory (default increased to 256 kB)
* Ext4 File system tweaks (default to on, can be disabled)
* System Tweaks predefined supported (default is off, new Mattiadj tweak set included)
* WIFI Multicast filter for better battery life
* WIFI wakelock times reduction
* Proportional rate reduction for TCP
* TCP congestion changed from Cubic to Westwood
* Wifi mac address change support
* Dynamic fsync 1.2 implemented
* Timeout for external SD card changed to improve handling of crappy SD cards
* Custom boot animation support
* Swap supported (but not recommended, use zRam instead)
* init.d support (in /system/etc/init.d - set correct permissions!)
* exFat opensource (Samsung OSRC) instead of proprietory modules
* NTFS (read-only access only!) compiled as a module
* CIFS compiled as a module
* NFS compiled as a module
* XBox controller support as module
* exFat support switchable (switch it off if you do not need it)
* Battery monitor wakelocks reduced
* Kernel can root if required (create file "autoroot" on internal sd and reboot)
* Android logger can be disabled
* Kernel logger can be disabled
* Disabled various debug logs and traces
* Frandom compiled as a module (for mods like Crossbreeder)
* Triangle away supported
* Automatic EFS backup to external (priority) or internal SD Card (fallback) - now compatible with tools like kTool
* Kernel initialisation log file (with history of 3 log files)
* Exynos vulnerability and sudden dead issue fixed
* Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
* Compatibility to common standard apps (Voltage Control, SetCPU, System tuner etc.)
* EFS V1 modem supported (also on Android 4.3)
* Compiled with Google arm 4.7 toolchain
* Internal kernel busybox version 1.21.1
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History
Basically I created Boeffla-Kernel as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
This said, I will definitely NEVER implement:
dual boot (I do not need it)
color "calibration" (I do not like it, but I like the crispy stock colours)
real hard overclocking higher than 1600 MHz as this is outside of Exynos specs
f2fs - it is known to cause various issues and compatibility problems
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it. Everything else I am happy to check and decide.
Compatibility
To reiterate it again: This kernel is only for Samsung based Jelly Bean (Android 4.1.x) firmwares. It is not designed to run on AOSP based roms!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
Donation
If you like my work, feel free to donate: Donation-Link
You will receive a personal donation code which unlocks some nice comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* Yank555
* ZaneZam
* Hardcore
* Chainfire
* Harunjo
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Supercurio
* Mialwe
* Entropy512
* Faux
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi

reserved1
--- reserved for future usage ---

reserved2
--- reserved for future usage 2 ---

nice new kernel good luck

Sounds very promising. Glad to see some people will keep their s3. Sending u a beer soon installing now
Ps. Fix the links
Sent from my GT-I9300 using Tapatalk 2

This is weird. I just tried on PC and Phone, both working for me...
Can you maybe try again? What browser are you using?
Cheers
Andi
Jack Barrett said:
Sounds very promising. Glad to see some people will keep their s3. Sending u a beer soon installing now
Ps. Fix the links. Redirects to downloading html page.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse

Tried stock & chrome. Downloads html page (same page)
Sent from my GT-I9300 using Tapatalk 2

Very weird, but ok. As a quick fix I will upload the kernel to the OP now.
Stay tuned, you will find in a vew minutes.
Thanks
Andi
Jack Barrett said:
Tried stock & chrome. Downloads html page (same page)
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse

I had no problem getting into your homepage or dl both kernel and cleaner script..
Will flash your kernel tomorrow..
Anyway welcome to gs3

Downloaded via PC. 5 min on it and I love it. Keyboard seems faster than before. Cleaned RAM twice, no redraw. Maybe launcher is locked in memory?
Here's your beer. Cheers and best of luck!
{
"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"
}
Sent from my GT-I9300 using Tapatalk 2

Download links now avaialbe in OP
EDIT: Have done some setting changes to the homepage, it should be working now also from your mobile devices. If not, please PM me...
For all those having trouble to download from the homepage to the mobile device: I have temporarily added download links into the OP as well.
Sorry for the inconvenience.
Thanks
Andi

i m testing this kernel since first betas quietly with my rom builds and i can say nothing but only best words.
This is the best kernel i ve ever had.
I m not going to say that other kernels are bad, not at all.
But for me stability and dailly use comes first and i cannot see lag anywhere......everything seems fast and it dont need overclock for sure....it is perfect out of the box

testing now and will announce the results after !

This is nice....
) ) ) over the air on Galaxy SIII ( ( (

sotmax said:
i m testing this kernel since first betas quietly with my rom builds and i can say nothing but only best words.
This is the best kernel i ve ever had.
I m not going to say that other kernels are bad, not at all.
But for me stability and dailly use comes first and i cannot see lag anywhere......everything seems fast and it dont need overclock for sure....it is perfect out of the box
Click to expand...
Click to collapse
I am also testing it till beta. I know for sure that this Kernel for me is the BEST. Very Smooth ,no lags..
Thank you Andi

This looks great man!
Nice to see new kernels here...
Is there a possibility to add cpu/gpu oc mate?
Thank you for contributing to the community.
Cheers,George.

nfsmw_gr said:
This looks great man!
Nice to see new kernels here...
Is there a possibility to add cpu/gpu oc mate?
Thank you for contributing to the community.
Cheers,George.
Click to expand...
Click to collapse
You need to read the first post about OC

good luck mate will test it

Exactly... OC is really not on my roadmap for the time being.
I see not a big point in it, the device is also fast enough for daily usage without OC.
But if you insinst on OC, there are plenty of other absolutely great kernels around for it
Thanks
Andi
efegue said:
You need to read the first post about OC
Click to expand...
Click to collapse

Download from homepage now working fine
Hi,
just a small update on the download issue from the homepage yesterday:
I completely swapped out the old download component in the CMS and replaced it by a different one. Now it has been confirmed (Thanks to Jack Barrett) to be working fine.
By the way - there is a known issue with auto root reported (in both 1.0 and 2.0-beta1 versions), I am currently working on it and expect a new beta version very soon.
Cheers
Andi

Blazing Kernel v16​
**Note: Those coming from older versions and has dual booted, you must extract and place the whole "system/lib/modules" folder from the kernel zip package into /sdcard/SDRoms/update, so it will be like this: /sdcard/SDRoms/update/system/lib/modules. Just reboot and everything will be fine!
Standard disclaimer from CyanogenMod:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Oh yeah!!! I finally made it! A kernel similar to Siyah kernel! You can use this on AOSP 4.2.2 ROMs or stock Sammy 4.1.2 ROMs, it will work in both! Plus, using a similar dual booting method like what @fuss132 did, you can now dual boot stock+stock, AOSP+AOSP or stock+AOSP!
Features:
** Most of my kernel features can be controlled using Trickster Mod Kernel Settings
- Can be flashed directly using stock recovery!
- Supports DUAL BOOTING
- Compiled using CM source
- Compiled using Linaro toolchain 4.7.4 by me! (optimised for Cortex-A9 architecture by me)
- Linux kernel version 3.0.98
- 3 versions of recovery available (different zImage): Philz, TWRP and CWM!
- Modified CWM to support /preload partition and gesture control: https://github.com/Ryuinferno/android_bootable_recovery
- Default scheduler is cfq
- Default governor is interactive
- MMC_CAP_ERASE already disabled by Samsung -> no more brick bug
- Supports CIFS
- Supports NFS
- USB fast charge
- Custom voltage settings
- Frandom support!
- Patched /dev/random
- More RAM (original=769 MB, Blazing Kernel=774MB)
- Additional governors: HYPER, Scary, wheatley, abyssplug, minmax, lulzactive, lazy, pegasusq, lagfree, smartassV2
- Addtional I/O schedulers: vr, sio, row
- swap support
- zRAM support
- exFAT module support
- Dynamic Fsync
- Dynamic Dirty Page Writeback
- Battery Life eXtender (BLX)
- CK3 tweaks
- Timer slack
- Dynamic timer slack control
- Miscellaneous tweaks
Stock only features:
~ Custom bootanimation (just place bootanimtion.zip in /system/media; to restore original bootanimation, just delete the bootanimtion.zip in /system/media) [AOSP already has this]
~ Custom boot sound (just place PowerOn.ogg in /system/media; to mute, create an empty file named "mute" in /system/media; to unmute, create an empty file named "unmute" in /system/media ; to restore original boot sound, create an empty file named "ori_sound" in /system/media)
~ Init.d scripts support (Place scripts in /system/etc/init.d or /data/etc/init.d) [AOSP already has this]​
Bugs:
** These bugs in AOSP are a compromise to get the kernel working, the code used for vibrations and touchkey lights are completely different, until I become a sensei in C, it can't be fixed for now
AOSP 4.2.2
- Cannot control vibration intensity
- Cannot control touchkey light duration or turn on/off
AOSP 4.3:
- Cannot control vibration intensity
- Slim ROM: Cannot control touchkey lights because Slim is still using old method for now
Stock:
- Cannot control touchkey light duration or turn on/off Solved​
Requirements:
- Running a stock 4.1.2 Samsung ROM or stock 4.1.2 based ROM
- Running a AOSP 4.2.2 ROM
- Running a AOSP 4.3 ROM
- At least 3 GB in internal storage if you want to dual boot​
Instructions:
Flash via stock or custom recovery (Safest and easiest method):
1. Choose your recovery type: CWM6 or TWRP.
2. Download the corresponding zip package.
3. Place in sdcard (external sdcard for those running stock recovery)
4. Flash the zip.
5. Reboot. It may take a little while as the kernel has lots of things to configure.​
NOTE:
To those who wanna provide logs, kindly refer to this post: http://forum.xda-developers.com/showpost.php?p=39014273&postcount=201​
Downloads:
Dual Boot Setup:
Terminal Emulator (Play Store link)
Terminal Emulator (Direct APK link)
DualBoot_BL_v3.apk
v16:
Blazing_Kernel_v16_CWM6_MOD.zip
Blazing_Kernel_v16_TWRP.zip
Blazing_Kernel_v16_PHILZ.zip
v15:
Blazing_Kernel_v15_CWM6_MOD.zip
Blazing_Kernel_v15_TWRP.zip
Blazing_Kernel_v15_PHILZ.zip
v12:
Blazing_Kernel_v12_CWM6_MOD.zip
Blazing_Kernel_v12_TWRP.zip
Blazing_Kernel_v12_PHILZ.zip
v11:
Blazing_Kernel_v11_CWM6_MOD (old).zip
Blazing_Kernel_v11_CWM6_MOD.zip
Blazing_Kernel_v11_TWRP.zip
Blazing_Kernel_v11_PHILZ (old).zip
Blazing_Kernel_v11_PHILZ.zip
v10:
Blazing_Kernel_v10_CWM6_MOD.zip
Blazing_Kernel_v10_TWRP.zip
v9:
Blazing_Kernel_v9_CWM6_MOD.zip
Blazing_Kernel_v9_TWRP.zip​
Thanks to:
@codeworkx
@fuss132
@chuandinh
@superatmos
@bluefa1con
@Phil3759
@mnazim​
XDA:DevDB Information
Blazing Kernel v16, a Kernel for the Samsung Galaxy S II
Contributors
Ryuinferno
Kernel Special Features: Dual boot and various kernel optimisations!
Version Information
Status: Stable
Created 2013-07-07
Last Updated 2013-10-24

Kernel Features Explained
What is frandom?
v6 and onwards supports frandom, which is a faster (10-50 times) random number generator than urandom...it generally decreases lag in GUI...if you are using CrossBreeder, it will automatically utilise it...if not, place this script in /etc/init.d and set permissions as rwxrwxrwx (name it whatever you want) and reboot:
Code:
#!/system/bin/sh
# Ryuinferno @ XDA
chmod 666 /dev/frandom
chmod 666 /dev/erandom
mv /dev/random /dev/random.ori
mv /dev/urandom /dev/urandom.ori
ln /dev/frandom /dev/random
ln /dev/erandom /dev/urandom
It is working if you have /dev/random.ori and /dev/urandom.ori after a reboot...to revert, just remove the script (or else, it will be applied on every boot)...
What is swap?
Swap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk (‘swapped’). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android’s Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android’s Memory Manager more efficient that swap.
To use swap, the easiest way is to install Swapper2
What is zRAM?
android1234567 said:
That looks accurate, but it's a little hard to understand. A basic explanantion of zRAM is that zRAM compresses an actual block of RAM in order to have more RAM available to the system. If you make the compression too high with zRAM then your device will actually go slower as a result. An example of going over the top would be adding 256MB of RAM using zRAM on a phone that only has 768MB RAM (that's almost a 50% compression rate because ~600MB is available to the user). zRAM also requires the CPU to compress and decompress the data.
Click to expand...
Click to collapse
To use zRAM, the easiest way is to install Trickster MOD Kernel Settings
What is exFAT?
Read this: http://www.differencebetween.net/technology/software-technology/difference-between-exfat-and-fat32/#ixzz1k5uLzt4l
Summary:
1.exFAT allows for higher drive capacities than FAT32.
2.exFAT has a larger file size limit than FAT32.
3.exFAT uses a free space bitmap while Fat32 doesn’t.
4.FAT32 has greater support than exFAT.
5.FAT32 doesn’t have file number limits while exFAT does.
What is BLX?
This feature has been developed by Ezekeel and allows to set a customized battery charging limit (100% is the default stock value, if you want, you can set a lower value).
As Ezekeel said, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
If you set a charging limit equal to 100, this feature will be disabled.
What is Dynamic Fsync?
This feature has been developed by Faux123 and allows to dynamically manage the synchronous writes performed on file system (FSync).
It uses asynchronous writes when the screen is on, instead of synchronous writes, to have better performance and a slightly lower battery drain, while when the screen is off the synchronous writes are re-enabled to flush all the outstanding writes and prevent possible data loss.
What is Dynamic Dirty Page Writebacks?
This feature has been developed by Christopher83 and allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off.
It is based on a commit of Francisco Franco, but instead of using hard coded values and of disabling at all the dirty page writebacks while the screen is on (possibility of data loss), I preferred to use a customizable higher dirty page writebacks interval (15 seconds) than the default one (5 seconds) while the screen is on and a customizable default interval (5 seconds) when the screen is off.
By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
How to customize the dynamic dirty page writebacks feature (default enabled):
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
1) By directly editing one of the file written above inside /proc/sys/vm and setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic dirty page writebacks feature
Code:
su
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
- Or run this command to re-enable the dynamic dirty page writebacks feature
Code:
su
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
- Run this command to set customize the two intervals (30 seconds while the screen is on, 10 seconds when the screen is off)
Code:
su
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs
What is timer slack controller and dynamic management of the minimal timer slack value?
The timer slack controller is a feature developed by Kirill Shutemov and it allows to set the minimal timer slack value for every process contained within a control group (cgroup).
A timer slack allows the kernel to manage processes wakeup requests at some future time.
Thanks to this feature, the kernel can set a specific timer slack for the involved processes, minimizing the number of wakeups and allowing a lower system's power consumption.
For further info: Timer slack for slacker developers
Chirstoper83 also implemented a new feature in addition to the above one that allows the dynamic management of the minimal timer slack value.
So, it's possible to use different minimal timer slack value when the system is active and when has been suspended.
How to customize the dynamic timer slack controller feature:
Three new cgroup parameters are exposed inside each processes hierarchy contained in /dev/cpuctl path:
- timer_slack.min_slack_ns is the timer slack used when the system is active for the current processes hierarchy
- timer_slack.min_slack_suspend_ns is the timer slack used when the system is suspended for the current processes hierarchy
- timer_slack.effective_slack_suspend_ns is the timer slack currently used
At the moment, the values chosen and used by Blazing Kernel are the following:
- core processes (/dev/cpuctl), 0 ns when the system is active, 50000 ns when the system is suspended
- foreground apps/processes (/dev/cpuctl/apps), 0 ns when the system is active, 250000 ns when the system is suspended
- background non interactive apps/processes (/dev/cpuctl/apps/bg_non_interactive), 100000000 ns when the system is active, 250000000 ns when the system is suspended
1) By directly editing one of the file written above inside /dev/cpuctl and inside each hierarchy subfolder, by setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to set the minimal timer slack for generic and core apps/processes
Code:
su
echo 0 > /dev/cpuctl/timer_slack.min_slack_ns
echo 50000 > /dev/cpuctl/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in foreground
Code:
su
echo 0 > /dev/cpuctl/apps/timer_slack.min_slack_ns
echo 100000 > /dev/cpuctl/apps/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in background and non interactive
Code:
su
echo 100000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns
echo 250000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_suspend_ns
What are CK3 tweaks?
They are actually patches by Con Kolivas (author of BFQ scheduler), more info in commit message here: https://github.com/Ryuinferno/Blazing_Kernel_t1/commit/3fa18eb9feee1c204b20a63f16136dc2b066581d

ROMs Supported:
Basically ALL ROMs!
- stock Samsung ROMs [4.1.2]
- stock based ROMs [4.1.2]
- MIUI [4.1.2]
- CM 10.1 [4.2.2]
- CM 10.1 [4.3]
- CM 10.1 based ROMs [4.2.2]
- CM 10.2 based ROMs [4.3]
- AOKP [4.2.2]
- AOKP based [4.2.2]
- AOKP based [4.3]
- AOSP based[4.2.2]
- AOSP based[4.3]
CHANGELOG:
Code:
[U]v16:[/U]
- Support for PAC ROM
- Support for CM's newly implemented multi-sim framework
- Updated to Linux kernel 3.0.101 (EOL)
- ExFAT module now compiled from source
- Updated recovery to CWM 6.0.4.4
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v15:[/U]
- Support for Android 4.3
- Updated to Linux kernel 3.0.98
- Reduced size of kernel modules (kernel zip package now a lot smaller
- Updated recoveries to CWM 6.0.4.0, TWRP to 2.6.3 and Philz to 5.15.0
- New modified CWM recovery! Features:
- Touch control!
- Battery status
- Prompt before commencing backup (avoids accidental backups)
- Advanced restore for /preload
- Rainbow mode! (to activate, scroll down the list for 5 times, scroll back up again to deactivate)
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v12:[/U]
- Full rebase of kernel source! Now it is at [url]https://github.com/Ryuinferno/Blazing_Kernel_t1[/url]
- With the rebase of sources, hiccups are eliminated, try it and you will know why...;)
(there were some code errors when patching the old source)
- Updated to Linux kernel 3.0.88
- Data usage stats fixed
- Compiled with Linaro 4.7.4 toolchain optimised for Cortex-A9 (yes, toolchain compiled by me too)
- Updated recoveries to CWM 6.0.3.5, TWRP to 2.6 and Philz to 5.08.5
- Timer slack and dyanmic timer slack control
- CK3 tweaks
- Updated graphics driver (now also compiled with Linaro!)
- For explicit changelogs, refer to my Github (commits are more detailed now)
[U]v11:[/U]
- Updated to Linux kernel 3.0.75
- BLX
- Dynamic Fsync
- Dynamic Dirty Page Writeback
- Dyanmic mutex spin management
- CRC32 algorithm
- Updated voltage control
- Latest sync with CM for better compatibility
- Fixed MTP not working in stock for certain people
- Philz recovery now available!
- Compiled using Linaro 4.7.4 toolchain
[U]v10:[/U]
- Updated to Linux kernel 3.0.60 (this is a real update, applied patches [B]step by step[/B] instead of skiping those in between
(there's one kernel that skipped most of the patches and went to 3.0.75 straight away lol,
reverted the 3.0.76 and applied 3.0.77, and claims that it is on 3.0.77 now...lol...
and I tried to advice him, but always ignored...:silly:))
- Fixed random reboots in recovery
- Removed interactiveX governor (main cause of the reboots)
- zRAM support (for fun...lol)
- swap support (for fun...lol)
- exFAT module support (sdcards can be formatted in exFAT format now)
- Compiled using Linaro 4.7.3 toolchain
[U]v9:[/U]
- Initial dual base kernel commit
- Bring forward all features from v8
- Dual boot support
Source code:
https://github.com/Ryuinferno/GT-I9100G-Blazing_Kernel (old)
https://github.com/Ryuinferno/Blazing_Kernel_t1 (new)

Dual Booting
This feature requires extra attention, so please read carefully!
1. Decide which ROM you want to place as secondary ROM. The most suitable ROM would be the one that has less updates and stable. Keep in mind that currently all secondary ROMs will start off clean, means ALL DATA WILL BE CLEARED, and /data is 1GB in size.
Now, decide between step 2 or 3:
Step 2 (Current ROM->Primary, another ROM->Secondary)
1. If you decide to keep using the current ROM you are running as primary ROM, please make a FULL BACKUP now.
2. Since you decide to use another ROM as secondary ROM, AFTER making a backup, flash the other ROM. Then, flash the latest kernel zip package.
3. Now, reboot the phone and install the control app & Terminal Emulator (install Terminal Emulator first). You will see this:
{
"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"
}
4. Hit the Deploy Files button, then the Dual Boot Setup button and wait for the process to finish.
5. The default ROM now is your phone ROM (primary ROM). To boot into SD ROM (secondary ROM) or from SD ROM to phone ROM, hit the Switch ROM button.
6. Restore your primary ROM now. But remember to flash the kernel zip package again.
7. Booting time may take longer as you are dual booting and dalvik-cache is building up.
8. Repeat all the steps above every time you wanna change new ROMs (means new zip packages).
Step 3 (Current ROM->Secondary, another ROM->Primary)
1. If you decide to use the current ROM as secondary and do not mind about data loss, please flash the latest kernel zip package now.
2. Now, reboot the phone and install the control app & Terminal Emulator (install Terminal Emulator first). You will see this:
3. Hit the Deploy Files button, then the Dual Boot Setup button and wait for the process to finish.
4. The default ROM now is your phone ROM (primary ROM). To boot into SD ROM (secondary ROM) or from SD ROM to phone ROM, hit the Switch ROM button. (Will show current ROM in the future)
5. Flash the new ROM you want to use as primary now. Remember to flash the kernel zip too.
6. Booting time may take longer as you are dual booting and dalvik-cache is building up.
7. Repeat all the steps above every time you wanna change new ROMs (means new zip packages).
**NOTE: MTP, USB mass storage or ADB and GPS does not work on secondary ROM

Aosp + Stock dualboot?
Wow hows that working?
All in one kernel?
Sent from my GT-I9100G using xda app-developers app

And here we go.

fuss132 said:
Aosp + Stock dualboot?
Wow hows that working?
All in one kernel?
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Yeah, took me a lot of brain juice...published the code in Github...
iXanza said:
And here we go.
Click to expand...
Click to collapse
Wohoo~~

Guys, anyone using stock based MIUI ROM, please check in /system/framework and see whether you have a file named "framework2.jar" or not...If you don't have, DO NOT use this on MIUI yet! I repeat, DO NOT USE IT YET! I need to configure more files......and please report back here...
Yup, confirmed working...

congrats mate
really excited to see this original work from you
best of luck

Gonna test this soon
Sent from my GT-I9100G using Tapatalk 2

Great work.... Since v3 am with you.... Great progress....:thumbup:
Sent from my GT-I9100G using xda premium

WOW , stock+AOSP dual boot

Holy $h!t XD
Sent from my GT-I9100G using xda app-developers app

Oh my god!!!!! Was my first expression wen i read the title......
Oh [email protected]#k was the reaction wen i read op......
Awesome work brother......
Lots and lots of thnx to u buddy.....
Genius is the only word tht comes to me for u now.....:thumbup:
Sent from my GT-I9100G using xda app-developers app

Well.....................................I'm IMPRESSED! :beer:
Sent from my GT-I9100G using Tapatalk 2

fantastic =).....any question...do you compile it with cm source and this command
. build/envsetup.sh
breakfast i9100g
make bootimage
or no ? =) thanks for all

Hmmmmmmmmmm don't know what 2 say yet but will still stay on v8 for a couple of days b4 trying this out cos I just flashed v8 2day......wanna ask if some1 doesn't want 2 dual boot, do d person really need this kernel over v8.....? Looks like d v8 will be as stable as pre 8 for me....its working fine since mrng....so this thread means d other thread is closed I guess
Well I can't forget 2 say thanks 4 d progress.....thumbs up
Sent from my GT-I9100G using xda premium

biagio7xD said:
fantastic =).....any question...do you compile it with cm source and this command
. build/envsetup.sh
breakfast i9100g
make bootimage
or no ? =) thanks for all
Click to expand...
Click to collapse
No
mortallkombat said:
Hmmmmmmmmmm don't know what 2 say yet but will still stay on v8 for a couple of days b4 trying this out cos I just flashed v8 2day......wanna ask if some1 doesn't want 2 dual boot, do d person really need this kernel over v8.....? Looks like d v8 will be as stable as pre 8 for me....its working fine since mrng....so this thread means d other thread is closed I guess
Well I can't forget 2 say thanks 4 d progress.....thumbs up
Sent from my GT-I9100G using xda premium
Click to expand...
Click to collapse
Just flash it over...the source used for compilation is different from v8...you can use the kernel as usual...the dual boot is just for those who wants it (which requires extra steps)...

Ryuinferno said:
Just flash it over...the source used for compilation is different from v8...you can use the kernel as usual...the dual boot is just for those who wants it (which requires extra steps)...
Click to expand...
Click to collapse
so this mean that this is totally different from v8 blazing kernel ?

One word..Ryuinferno rule..:thumbup::thumbup:
Sent from my GT-I9100G

CyanogenMod 10.1.2 Jellybean 4.2.2 - KANG
CyanogenMod is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices. Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, an enhanced reboot menu, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as wi-fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. CyanogenMod does not contain spyware or bloatware. In many cases, CyanogenMod may increase performance and reliability compared with official firmware releases.
Source: CyanogenMod Wiki​
Screenshots
Installation Instructions
Requirements
* Rooted (obviously)
* A brain
Installation
1: If you are coming from another ROM do a full wipe
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
1b: if your device is S-ON you must flash your boot.img either with fastboot or some type of GUI program EVERY FLASH (google is your friend)
2: Flash gapps (download below)
3: Reboot
4: Enjoy CyanogenMod 10.1
Please read the whole post for changelog, Download links, and other important info
Updates:: First build since initial release, mainly cosmentic changes. although a couple important fixes. Anyways please take the time to read the whole post, as well as post #2
. As always: remember it takes a FULL charge from AC, and a full discharge then re charge batteryt to be accurate. Also leave it plugged in for up to an hour at 100%, Another thing i find helps battery life is to make custom auto-adjustment values if you use auto-brightness. Check below for full changelog Feedback always welcome Please read the Kernel section for more info and full config options for the kernel.
Albinoman887
Working
SMS/MMS
Wi-FI
Data
GPS
Audio
Radio
Camera
Google Now
Internal/External SD card
Bluetooth
H/W Accelerated Video Playback
Native Wi-Fi Tethering
1080p Video Recording
Not Working
????????????
Changelog
Aug-19
* Here is a test CM-10.2 build. please post your results. if they are good i will open a new thread...
Aug-6
* Synced with upstream
* Kernel updated to Linux 3.0.85
* One more go at the low mic in call issue
* Build is now on a new super fast server. i will still use goo.im due to the OTA update function but the new server will be the main download link
July-23
* Fixed a few rare graphical glitches (no not with Maps 7)
* Any and all upstream changes at time of compile
* Disabled Sweep2wake since it doesnt work (it does on pyramid and shooter so will revisit this bug one day)
July-15
* CM tagged 10.1.2 (security fixes)
* 2nd go at fixing sim card message
* Fixed torch turning off with screen
* Fixed soft reboots!!
* Enabled FauxSound
* General cleanup
* Any upstream updaes to CM at time of compile
July-2
* Fixed all the issues with the last release and black screen
* Really fixed video recording - NOTE!: if dirty flashing you must clear data and cache of Gallery app
* Kernel: Enabled mpdecision (I forgot)
* Fixed "SIM card inserted" message on boot
* Fixed issue where some people had to toggle airplane mode to get service
* General cleanup of code, seems more stable
* Kernel: Changed version string to ChronicKernel to conform with my pyramid/GS4/glacier kernels
* Added qcom-post-boot service to startup (was missing)
* Upstream CM Changes
June-30
* Fixed Low volume
* Fixed LED flashlight toggle not being selectable for notification drawer
* Fixed Video recording
* Fixed Dock options not showing in settings
* Fixed volume rocker wake not showing in settings
* Fixed issue with soft-reboots during heavy usage
* Added init script for configuring some kernel settings (GPU OC, fsync, etc) (located:/system/etc/init.d/99kernel)
* Set min CPU freq to 384mhz like on other msm8660 devices (192mhz is a buggy freq)
* Fixed big margins on homescreens with trebuchet after clean install
* Upstream CM changes
June-29 - initial build
notable changes since cm10
* Kernel: GPU drivers updated to jb-chocolate from CAF
* Kernel: Genlock updated to jb-chocolate from CAF
* Kernel: vidc updated to jb-chocolate from CAF
* Kernel compiled with linaro and -o3 optimizations
* Kernel: updated to Linux 3.0.80
* All issues from development builds squashed
Kernel
ChronicKernel
* Compiled with linaro
* Set flash to disable if battery is below 10% to prevent the random shut-off when taking a pic
* Removed/Disabled KSM
* Removed ZRAM
* User-configurable GPU OC (Not OC'd by default)
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* Reverted CRT hack to smooth animation in Android 4.2.2
* Increased PMEM_MDP as it is needed in Android 4.2.2 to fix soft-reboots
* PM_FAST enabled by default (high power wi-fi when screen is off)
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. If you want more features of the Sultan kernel feel free to flash it, but support will not be provided in this thread.
Other Features of the kernel include:
* OC to 1866Mhtz (default 1566Mhtz)
* Undervolted
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = SIO)
* User-configurable badass gonvernor (default = balanced)
* Sweep2Wake
You can edit many of the settings in /system/etc/init.d/99kernel, here is a snippet of the script with all the config options
Kernel init script: Click Show Content to expand
Code:
#Script originally made by Axetilen. Modified by Sultan (android1234567)
#Updated for albinoman887's ChronicKernel (98% of the credit goes to android1234567. Thanks so much man :)
# Configure your options here #
# Config default CPU Gonvernor (Disabled by default: When disabled uses internal Kernel setting)
# For better battery life switch to badass
# Kernel Default: ondemand
# Possible values
# badass
# ondemand
# interactive
#= lagfee
# performance
GOV=ondemand;
# Config I/O scheduler
# deadline
# cfq
# noop
# vr
# sio (default)
IO=sio;
# Config CPU max frequency
# Default: 1566000 (1566Mhtz)
# Overclockable to - 1836000 (1836Mhtz)
# for badass set to 1566mhtz (best performance/battery life)
MAXFREQ=1566000;
# Config CPU min frequency
# Default: 384000 (384Mhtz)
# Range 384000 - 1944000 (384Mhtz - 1944Mhtz)
MINFREQ=384000;
# Config 3D GPU clock
# 228571000 = 228mhz
# 266667000 = 267mhz (default)
# 300000000 = 300mhz (Recomended For balance of Performance and Battery life)
# 320000000 = 320mhz
GPU=266667000;
# Config 2D GPU clock
# 145455000 = 145mhz
# 160000000 = 160mhz
# 200000000 = 200mhz (default)
# 228571000 = 228mhz (Recomended For balance of Performance and Battery life)
# 266667000 = 267mhz
DD=200000000;
# Badass
# possible values
# 1 = performance
# 2 = balanced
# 3 = battery saving
BADASS=2
# Enable Sweep2Wake
# 0 = disabled (default)
# 1 = enabled
# 2 = enabled (with no button backlight during sweep)
SWEEP=0
# Enable Fastcharge
# 0 = disabled
# 1 = substitute AC to USB charging always
# 2 = substitute AC to USB charging only if there is no USB peripheral detected
FASTCHARGE=0;
# Fsync Control
# Disabled by default (recomended)
# 2 = Fsync disabled
# 1 = Fsync enabled
FSYNC=2;
# TUN
# Disabled by default
# 0 = Disabled
# 1 = Enabled
TUN=0
# End of configurable options #
Please note this is not the full script just a small portion, Check /system/etc/init.d/99kernel for the full script
Bugs
* MHL doesn't work
* Sweep2wake sometimes causes issues with the proximity sensor during calls
Notes
Most vivid users are S-ON, if you don't know what this is you are. This means you must flash the boot.img EVERY FLASH either with fastboot or similar, if you fail to do this you WILL have problems, including broken wifi and instability
* As of Feb-19 CyanognMod changed the way the reboot menu works. To enable the "Advanced Reboot" menu with recovery and bootloader go to Settings>Developer Options and Check Advanced Reboot
* As of AOSP 4.2.2 ADB now has a whitelist feature. On first connect with adb it will say device offline You need to update your ADB then with the phone connected. Disable and Re-Enable Android Debugging in the Developer Options menu. It will ask if you want to accept and show the PC's RSA key. Select Yes and it will now work as expected
* If your homescreen does not look right (big margins) go to System Settings>Launcher>homescreen[/B] click Stretch screens. Then choose grid size and set rows to 5.
* As of AOSP 4.2.1 Developer Options and Performance setting menu options are hidden until you go into about phone and tap build number repeatedly (aprox. 6 times) this only needs to be done once
* If you are having a lot of soft reboots when waking the device set you min CPU freq. to 384htz in Performance settings. (What? no Performance settings? ummm look up hehe)
* If you are coming from another ROM i highly recommend you perform and Wipe Date/Factory Reset in recovery menu when applying this ROM.
* The gapps linked to does not have photosphere. As far as i know it's not supposed to. If you want photophere search for the flashable zip
* If you can't get MMS to work. Send yourself a MMS. or just wait a day. eventually they will work again
* For the best battery life I suggest the stock settings with the exception of the ONDEMAND governor. Switching to BADASS will yield best battery results
DOWNLOAD
ROM : cm-10.1-20130806-Albinoman887-holiday.zip
Gapps : gapps-jb-20130301-signed.zip
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *
Source Code
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
Credits
* android1234567 for getting this porting project going, it was a joint effort between us to get this going
* billibox for his relentless testing
* of course cyanogen, the CyanogenMod project and all who contribute.
* Bruce2728 for doing all the leg-work originally to get get CM-10 on our Sensation, most of which was used for CM-10.1
* Evervolv Team for their device tree. This was largely what was needed to get the build going.
* mikez for all his work on the Evervolv/pyramid tree.
* NLJ for making the diff patch of Evervolv's frameworks_av repo to get camera working
* jiggs82 for all his helpful hints.
* And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
* dastin1015 for answering all my n00bish questions, and providing helpful hints and solutions
* android1234567 for all the help with the kernel, without you we wouldn't have new kernel
* tarfu for fixing camera p2z
* blahb14hblah for his hint to the extra scrolling tweak in frameworks/base
* NLJ for fixing the Sweep2Wake proximity sensor issue
* Skipjacks for maintaining the Q&A thread
* A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
Donations
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
For more information, like kernel info (and possibly newer kernel builds) from our kernel chef android1234567 read the 2nd post
Happy Flashing
Albinoman887

Reserved

Reserved for future kernel fun

Awesome job guys, it was great to see this in development and finally finished. And THANK YOU for the DevHost mirror, its way faster than too... I'm getting between 5-10Mb/s
{
"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"
}
Sent from my CyanogenMod Vivid using Tapatalk 4

Hey I'm downloading it right now and I'm wondering if the ROM still has low call volume problems?

Wooow, I really thought this phone had no more hope (excluding the dev thread). And here it is...nice work everyone that put in the time. We all GREATLY appreciate it.
Time to test this out and report some bugs.
Thank you again!!!

HTC_Vivid said:
Hey I'm downloading it right now and I'm wondering if the ROM still has low call volume problems?
Click to expand...
Click to collapse
Seems like I can barley hear voicemail so I would say yes...

I'm assuming that's being dealt with in those kernel changes that were hinted about in the OP. Can't wait to test this out.

switchy85 said:
I'm assuming that's being dealt with in those kernel changes that were hinted about in the OP. Can't wait to test this out.
Click to expand...
Click to collapse
It hasn't been fixed the entire time CM10 has been out... So if these guys find a fix I would be amazed!

switchy85 said:
I'm assuming that's being dealt with in those kernel changes that were hinted about in the OP. Can't wait to test this out.
Click to expand...
Click to collapse
Don't get your hopes up I've already tried fixing it many times in the kernel without any luck.

Excellent news! Going to bed to word of "I don't know what else to try" and waking up to a new thread and a fully functional ROM!!!
May I be so bold and ask what the last missing but was for getting WiFi working?
Big thanks in any case to all, known and unknown, that participated so far.
François

frankieGom said:
Excellent news! Going to bed to word of "I don't know what else to try" and waking up to a new thread and a fully functional ROM!!!
May I be sobold and ask what the last missing but was for getting WiFi working?
Big thanks in any case to all, known and unknown, that participated so far.
François
Click to expand...
Click to collapse
Some firmware was missing for it. As far as I know.

bilibox said:
Some firmware was missing for it. As far as I know.
Click to expand...
Click to collapse
Thanks

Well flashed it on my phone and it is awesome. Get ready for the flood of 4.2 ported roms. Already working on two rom ports from the HTC Sensation just need to finalize and get permission from the devs hopefully will have booting roms up by Friday as I am going on a holiday.
Sent from my HTC One using Tapatalk 4

After some quick initial testing, it appears everything in OP WORKING list, WORKS .
Data, SD, Wifi, Sound, and more. Seems VERY snappy too. Ohh some really good work

Thanks guys for your great work :thumbup:
One question 1080p video can be played with hardware playback ? Cm10 can't do this
Sent from my HTC Holiday using xda app-developers app

Only bug that I find is that it takes quite a long time to wake up the screen compared to cm10.
Sent from my HTC One using Tapatalk 4

Since this is 4.2.2, will BaNkS Gapps will work OK?
Sent from my Vivid 4G using Tapatalk 2

Can't wait to flash
Sent from my Vivid 4G using xda premium

bruce7373 said:
Since this is 4.2.2, will BaNkS Gapps will work OK?
To answer myself: yes, so far so good.
Click to expand...
Click to collapse
I see there's still the issue of CM not mounting the external sdcard when USB connected that exists with CM 10. I was hoping things would be different with 4.2.2, but apparently not. The workaround is to go into Recovery and mount it there, then connect. So this must be a CM issue, since the problem doesn't exist with PAC (4.1.2). Or maybe how CM works with the Vivid. Anyone have any idea?
Sent from my Nexus 10 using Tapatalk HD

| CyanogenMod 10.2 - Android 4.3.1 - Jellybean |
{
"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"
}
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
If you ask any questions that are answered in the first two posts your question will be ignored. If you don't search prior to posting you will be ignored. If you don't read you will be ignored. If you've done all that and still don't have an answer then feel free to ask your question. Ambiguity doesn't help anymore. Elaborate. It's that simple.
Click to expand...
Click to collapse
Built from CM source
Service
Text
Call
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Camcorder
UMS
Maps 7 has graphical glitches. See "Extras" section in 2nd post for older glitch free version
On first phone call after a reboot, mic volume is very low. either hang up and call back or blow into the mic real fast and the gain will be corrected
Do NOT use superwipes
Wipe data, cache, and dalvik cache
** (if you are simply applying an update to this rom base this might not always be required)
*** ((but do not report bugs if you didn't full wipe))
[*]If you are S-ON flash the boot.img either via fastboot or some other tool (this is esential!!)
Flash ROM
Flash GAPPS
Reboot
???
Profit
To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
Read the FAQ thread here before posting any questions in this thread: FAQ
billibox for being my dedicated tester
And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
NineInchNails for being an awesome dev partner, moral support and friend!
dastin1015 for being an awesome dev partner and friend!
A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
All my supporters!
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Thanks and happy flashing!
Download link is in 2nd post

Oct-31
* Signal issues are fixed once and for all
* Kernel: updated bluetooth drivers to match CAF kernel
* Kernel: imported bluetooth stack from Google's Common Kernel
* Kernel: Misc updates to help power usage
* Kernel: Updated to Linux 3.0.101 EOL
* Kernel: Misc optimization tweaks
** Note: goo.im is undergoing a server move so their filesystem is read-only for the next week. So builds won't be uploaded there until their move is complete
Oct-28
* Fixed data issues from last build, still takes awhile for initial connection
* Fixed strange signal strength reporting (asu was way off)
* Kernel is compiled with -o3 (optimize alot) flag now
* Fixed issue where switching from FFC to back cam results in a FC
* Fixed issues with viper4android (DSP app)
* Fixed issue with random crashing of gallery when finalizing a video recording over 30secs
* Upstream changes
Oct-19
* Android updated to 4.3.1
* Fixed bluetooth
* Fixed Video Recording
* Added 1080p Video Recording
* Merged scrolling build.prop tweaks from pyramid
* Removed hardcoded tcp values from ramdisk (is defined by init.cm.rc, better data speeds)
* Removed old dalvik heap size build props from ICS days
* Increased WI-Fi scan interval to match pyramid, Should reduce battery drain
* Tried to fix distortion at higher volumes
* Disabled noise suppression in Phone calls to try and fix low volume
* Updated libril source to match cm-10.2 source
* Fixed Random data drops/cycling data
* Fixed cell signal strength
* Removed some old depreciated build.prop settings
* Removed some gps related build.prop settings which seem to yield a faster lock
* Kernel: Updated bluetooth code to match pyramid
* Kernel: Updated to Linux 3.0.100
* A lot of upstream changes including camera fixes and more
Oct-10
* Attempted to fix bluetooth (attempt 2)
* Fixed Torch turning off with screen
* Updated kernel to Linux 3.0.99
* Updated msm8660 power hal (should fix skipping with music playback)
Oct-6
* Attempted to fix bluetooth
* Attempted to fix video recording
* Attempted to fix sweep2wake
* Data indicators are fixed
* Lots of other upstream changes and cross-device changes I can't remember right now
Sep-17
* Fixed Camera
* Fixed battery drain
* Fixed bluetooh (untested)
* Added CMAccount
* Updated VibratorHW permissions to allow for sensitivity adjustment in CM settings
* Fixed USB Mounting of internal and external sd cards
* Added some audio libs that were missing from build (logcat was complaining, nothing more)
* Disabled Touch-to-Snapshot in video recording as our device doesn't support it
* Fixed Touch-to-focus with video recording
* Fixed FC with multiple video recordings (there are no shutter sounds for starting and stopping video recording for this fix to function)
* Kernel: Fixed issue where some apps (including CM setttings) would only apply Min/Max CPU freq changes and/or governor changes to the first cpu core only
* Kernel updated to Linux 3.0.94
* Upstream: Android tagged: "Android-4.3 r3" Build ID: "JLS36C"
* Some updates to the display and media codec libs to conform with Android 4.3 better
* Any and all upstream changes at time of compile
Aug-29
* Data/Service fixed
* Tried to fix camera (not much better)
* Some cleanup from CM-10.2 bringup
* Any upstream changes at time of compile
Aug-27 - Initial release
notable changes since last build:
* CM-10.2
* Addressed signal strength issue
* no longer using a hacked prebuilt init binary
* Tried to address only external sd card mounting via usb mass storage
* Tried to address the camera bugs in the test cm-10.2 builds (please post results!)
ChronicKernel
Kernel now based on Bruce's kernel with a few changes by me, including:
* Compiled with linaro
* Set flash to disable if battery is below 10% to prevent the random shut-off when taking a pic
* Removed/Disabled KSM
* Removed ZRAM
* User-configurable GPU OC (Not OC'd by default)
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* Reverted CRT hack to smooth animation in Android 4.2.2
* Increased PMEM_MDP as it is needed in Android 4.2.2 to fix soft-reboots
* PM_FAST enabled by default (high power wi-fi when screen is off)
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. If you want more features of the Sultan kernel feel free to flash it, but support will not be provided in this thread.
Other Features of the kernel include:
* OC to 1866Mhtz (default 1566Mhtz)
* Undervolted
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = SIO)
* User-configurable badass gonvernor (default = balanced)
You can edit many of the settings in /system/etc/init.d/99kernel, here is a snippet of the script with all the config options
Kernel init script: Click Show Content to expand
Code:
#Script originally made by Axetilen. Modified by Sultan (android1234567)
#Updated for albinoman887's ChronicKernel (98% of the credit goes to android1234567. Thanks so much man :)
# Configure your options here #
# Config default CPU Gonvernor (Disabled by default: When disabled uses internal Kernel setting)
# For better battery life switch to badass
# Kernel Default: ondemand
# Possible values
# badass
# ondemand
# interactive
#= lagfee
# performance
GOV=ondemand;
# Config I/O scheduler
# deadline
# cfq
# noop
# vr
# sio (default)
IO=sio;
# Config CPU max frequency
# Default: 1566000 (1566Mhtz)
# Overclockable to - 1836000 (1836Mhtz)
# for badass set to 1566mhtz (best performance/battery life)
MAXFREQ=1566000;
# Config CPU min frequency
# Default: 384000 (384Mhtz)
# Range 384000 - 1944000 (384Mhtz - 1944Mhtz)
MINFREQ=384000;
# Config 3D GPU clock
# 228571000 = 228mhz
# 266667000 = 267mhz (default)
# 300000000 = 300mhz (Recomended For balance of Performance and Battery life)
# 320000000 = 320mhz
GPU=266667000;
# Config 2D GPU clock
# 145455000 = 145mhz
# 160000000 = 160mhz
# 200000000 = 200mhz (default)
# 228571000 = 228mhz (Recomended For balance of Performance and Battery life)
# 266667000 = 267mhz
DD=200000000;
# Badass
# possible values
# 1 = performance
# 2 = balanced
# 3 = battery saving
BADASS=2
# Fsync Control
# Disabled by default (recomended)
# 2 = Fsync disabled
# 1 = Fsync enabled
FSYNC=2;
# TUN
# Disabled by default
# 0 = Disabled
# 1 = Enabled
TUN=0
# End of configurable options #
Please note this is not the full script just a small portion, Check /system/etc/init.d/99kernel for the full script
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
ROM : cm-10.2-20131031-Albinoman887-holiday.zip
GAPPS: : HERE
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *
The new maps 7 from google has graphical glitches due to our old hacked adreno libs. Click the following link Maps-6.apk for glitch free version

first create the folder structure for your source. I suggest creating android/system n your home directory.
Now cd into this directory enter this command
Code:
repo init -u git://github.com/Team-Hydra/android.git -b cm-10.2
repo sync
( if you have a pretty decent /internet connection (10-20mbps+) you can add -j and then a number ater repo sync i recomend something like repo sync -j10 )
Once you have done that your ready to go. simply run:
Code:
. build/envsetup.sh
./vendor/cm/get-prebuilts
lunch cm_holiday-userdebug
mka bacon
make sure before you start a new build to always run make clobber
If anyone would like to help bug bash with me feel free. if you make any progress send me a pull request
P.S. I HIGHLY recomend setting up ccache if you are going to compile a lot you can read more about ccache here: Initializing a Build Environment and scroll down to the "set up ccache" section
Happy Developing,
Albinoman887

tried to fix a few remaining bugs from the test builds. please check this out

no service and data.
camera is ok, takes photo/video.

kkruglov said:
no service and data.
camera is ok, takes photo/video.
Click to expand...
Click to collapse
Do the videos crash. When stopping. I know how to fix data I forgot something
Sent from my SGH-M919 using Tapatalk 2

when i opening recorded video at first time - gallery stops, but on second time it is ok.
waiting for fix.. or something for data.

kkruglov said:
no service and data.
camera is ok, takes photo/video.
Click to expand...
Click to collapse
Same although I'm more worried about Service than data but I'm going back to cm10.1 until this is fixed. :/

kkruglov said:
when i opening recorded video at first time - gallery stops, but on second time it is ok.
waiting for fix.. or something for data.
Click to expand...
Click to collapse
no i mean when you press stop to finish the recording.....does it crash?

p.s. i'm going to sleep. but i started the new build. it should end up here when its done: http://chronic-buildbox.dyndns-server.com/holiday/tests/
check in about 40 mins or so
again just go here http://chronic-buildbox.dyndns-server.com/holiday/tests/
it should be there if not check again after a few mins

TheROMGuy said:
Same although I'm more worried about Service than data but I'm going back to cm10.1 until this is fixed. :/
Click to expand...
Click to collapse
read above post...it was a screw up on my end that broke data. the next build will have it working just go the the above link in about 45 mins. i'll move it to the OP when i wake up

albinoman887 said:
no i mean when you press stop to finish the recording.....does it crash?
Click to expand...
Click to collapse
nope, i recorded 10-15 seconds, it's fine.

kkruglov said:
nope, i recorded 10-15 seconds, it's fine.
Click to expand...
Click to collapse
What about like 40s? And does 1080p worl
Sent from my SGH-M919 using Tapatalk 2

can't say more now, sorry, restored backup with sense 4.. ;(
see new build, will try it.
---------- Post added at 02:46 PM ---------- Previous post was at 02:25 PM ----------
about new build:
service/data ok, sdcard ok, video 1080p - no, if i enable 1080p in settings, it just do nothing after click on record button, 720p - tried to record 50+ sec video, when i press stop, it do nothing for about 5-7 seconds, and then camera crashes, after that i cant do photos or videos, it just "cant connect to camera", after reboot - all is fine.
and in call volume isn't bad.

Awesome!

Everything works great as far as I can tell. Thanks for the hard work!

Bluetooth?
Anyone else have an issue with bluetooth not wanting to turn on? When I toggle it, it says turning bluetooth on, then goes right back to saying turn bluetooth on to see available devices. I'm pretty dependent on bluetooth, esp with the low call volume...

rassawyer said:
Anyone else have an issue with bluetooth not wanting to turn on? When I toggle it, it says turning bluetooth on, then goes right back to saying turn bluetooth on to see available devices. I'm pretty dependent on bluetooth, esp with the low call volume...
Click to expand...
Click to collapse
Yes, the same at mine.
Sent from my Vivid 4G using Tapatalk 4

kkruglov said:
Yes, the same at mine.
Sent from my Vivid 4G using Tapatalk 4
Click to expand...
Click to collapse
Ok, then I'll report it as a bug, if it isn't already. Did you you do full wipe before flashing?
edit: doesn't look like a bug report link is up yet...

rassawyer said:
Ok, then I'll report it as a bug, if it isn't already. Did you you do full wipe before flashing?
edit: doesn't look like a bug report link is up yet...
Click to expand...
Click to collapse
Having big battery drain. Anyone else?