Related
Noma kernel for Huawei U8150
I'm introducing my custom kernel for Huawei U8150 IDEOS phones. In Kenyan Swahili noma usually means "tight," as in: "That music is tight!" It can be used in other ways too, but I like this connotation the best.
GoalsMy aim is to learn about Linux kernel internals, practice software development using git, and to share with the community. In addition to that, I want to explore and test tweaks which lead to increased/optimized performance on this bargain phone (it's very popular in Kenya). Some of the areas of improvement I have in mind are:
CPU scheduling (UI responsiveness, reducing lag)
CPU frequency scaling governors (smartass? ondemandX? interactiveX?)
I/O scheduling and filesystems (flash disk performance, throughput, latency, maybe simpleio scheduler?)
Security (network, local)
Newer drivers (mainstream, community kernel sources)
Newer GCC compilers (CodeSourcery, Linaro)
Easy rooting
Integrate ClockWorkMod Recovery
Integrate busybox
Explore different compression algorithms (LZO, gzip, LZF, etc) for zImage...
Compcache (zram) (info, announcement)
SLOB memory allocator for better memory allocation? (info)
Current features
Code:
- multi-touch gestures (on devices with [url=http://mjanja.co.ke/2011/08/does-your-huawei-u8150-support-multi-touch-gestures/]supported hardware[/url])
- over/under clocking of CPU frequencies
- Tiny RCU ([url=https://lwn.net/Articles/323929/]info[/url])
- BFQ I/O scheduler ([url=http://algo.ing.unimo.it/people/paolo/disk_sched/]info[/url])
- simpleio scheduler ([url=https://github.com/erasmux/hero-2.6.29-flykernel/wiki/Smartass]info[/url])
- "ck" patch set, including the Brain **** CPU scheduler (BFS) ([url=http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck2/]info[/url])
- optimized memcopy/memmove ([url=https://github.com/alanorth/kernel_huawei_u8150/commit/871656cbba8ee70d0896ac5cae35a31c2e0873e3]info[/url])
Downloadsfastboot-flashable boot images:
20120514v1: info, download
20110903v83: info, download
20110827v56: info, download
20110824v49: info, download
20110823v47: info, download
noma_20110711v26_boot.img (the "oops, I messed up my phone" kernel... safe, stable defaults; close to "stock" Huawei)
Possibly more here (on github)
Change logChange logs are a pain in the ass to keep up to date, but you can see changes live in the git repository itself. See the commit history of the below branches if you're curious:
froyo-noma-dev commits (dev, bleeding edge)
froyo-noma commits (stable)
Source code
I respect the GPL (the license covering the Linux kernel), so all the up-to-date source code for this kernel is available on github. My kernel is, in turn, based on the publicly-avaiable Froyo kernel sources from Huawei. You're free to fork, modify, and re-release the code as your own, but you must provide the source code for your resulting work. Doing so ensures you honor the terms of the license, but you're also giving back to the community. Basically, don't be a ****.
Credits
I've written zero lines of C code for this kernel. My work is merely to search for interesting modifications to the Linux kernel and add them to a git repository. The real work has been put in by the following people:
Linus Torvalds and all the other Linux kernel hackers around the world
tj_style (multi-touch gesture support)
Stefano Viola (over/underclock)
Renaud Allard for his Galaxy S awesome sauce (kernel, initramfs, etc)
Erasmux (smartassV2)
Let me know if I've left you out.
Donations
Hahaha! No seriously, save your money; I am gainfully employed and I just do this for fun (and lulz)! Instead, just hit "thanks" on this thread. Or, if you're ever in Nairobi you could always buy me a cup of coffee.
Reserved for flashing instructions...
Could you please post fashing instructions via custom recovery?
Im a bit of a noob.
Thanks.
Use fastboot!
Antownee said:
Could you please post fashing instructions via custom recovery?
Click to expand...
Click to collapse
I usually just flash from fastboot lately, as I'm between ROMs too much and I don't bother installing a custom recovery. I suppose I should modify my build scripts to make recovery-flashable zips... hang tight!
... or, if you can't wait, check out my in-depth blog post about compiling and flashing custom kernels on Huawei 8150. I wrote it a few weeks ago when I was a U8150 n00b.
v47 (20110823)
Changes in 20110823v47 (from the git commit log):
Add new, lookup3-based jhash. See: http://burtleburtle.net/bob/hash/doobs.html
pids: fix a race in pid generation that causes pids to be reused immediately
lib/decompress_bunzip2.c: fix checkstack warning
kbuild: drop unifdef-y support
net sched: fix some kernel memory leaks
net/ipv4: Eliminate kstrdup memory leak
Add noma_defconfig. `ARCH=arm make noma_defconfig` to use.
Mostly security and memory leak fixes. The new jhash implementation is based on lookup3.c, a newer, more-efficient implementation (more info here). It's mainly used in the kernel's ipv4 and ipv6 stacks, so don't expect revolutionary performance increases, but it's backwards compatible with the old implementation, so it couldn't hurt to include it.
Default IO scheduler is now deadline (the same as stock Huawei) until I can do some performance tests of other schedulers on this device. Note: I've included BFQ, Anticipatory, CFQ, and noop as well, so you can use those if you like!
Download: noma_20110823v47_boot.img
v49 (20110824)
Changes in 20110824v49 (from the git commit log):
Default to ZLO compression of kernel and ramdisk. LZO has roughly the same (but worse) compression, but is much faster to decompress.
Add LZO compression support for initramfs and old-style initrd
Add support for LZO-compressed kernels on x86
Add support for LZO-compressed kernels for ARM
Add support for LZO-compressed kernels
LZO compression is not as efficient but should be faster than the default compression (gzip), which should improve boot time. See: http://free-electrons.com/blog/lzo-kernel-compression/.
Download: noma_20110824v49_boot.img
Why are you working on Froyo and not on Gigerbread?
Why I'm still working on Froyo
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
As this is basically a research project (for both me and the community), the primary reason I'm still "working" on Froyo is that most U8150s are still running Froyo. It's an incredibly popular phone in Kenya (maybe 250,000 - 500,000 units sold?), but I have a hunch very few of them are running non-stock ROMs. Sure, CyanogenMod 7 has a fairly-active U8150 port in progress, but it's not widely used yet.
Like I said, this is primarily a research project, so I'm experimenting for my own curiosity. A part of that is to help people get into Linux kernel, Android, and open-source software development. I want to help set an example of openness, collaboration, documentation, etc.
Also, a lot of the mods I'm making can just as well apply to Gingerbread when we finally get there.
Custom kernel booting on U8150 CM7
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
Fun times... I just got a custom kernel to boot on CM7. It's nowhere near as usable as tilal's kernel, but it is a good exercise. More info here on my blog.
I suppose that whenever I get bored enough with Froyo I could always hop over to CM7. AOSP is where my heart is anyways.
v56 (20110827)
Changes (from the git commit history):
Add su, Superuser.apk, and busybox. This kernel/boot.img will now actively root Huawei stock ROMs.
Remove pre-zipped ramdisks as they are now generated on the fly from the compile scripts.
Correct the name of the compressed ramdisk (mkbootfs technically creates a cpio archive, which I then zip).
Make sure `make clean` doesn't delete our pre-compiled wireless module.
Add mkbootfs for creating ramdisks, and update compile.sh to create ramdisks on the fly instead of using a pre-zipped one.
Add ramdisk from U8150 V100R001C18B842
The build system is now a little more flexible and generates ramdisks on the fly. This should make it more powerful and complete. I've also included su, Superuser.apk, and busybox to enable a very cool new feature: rooting! If you haven't forked or cloned my kernel repository yet, what are you waiting for?
Regarding "rooting," forget what you've heard (it's probably wrong). Here's what it actually means:
Copying the su binary to /system/bin/su
Copying the Superuser.apk application to Superuser.apk
Period. What this means is that Android applications can call on the su binary whenever they want to do perform system administration actions (ie, not normal user actions), such as removing system applications with Titanium Backup. The Superuser.apk application is simply a frontend for su; whenever an application tries to execute su, a Superuser dialog pops up asking you to allow or deny the request. This notion, known as "privilege separation," is a common one in all operating systems.
Download: noma_20110827v56_boot.img
v83 (20110903)
Changes (from the git commit history):
sched: export nr_running symbol for use by smartassV2 CPU governor.
config: sync with latest config
sched_fair: Restore less extereme latency values (latency of 6ms)
sched: enable HRTICK
sched_fair: Enable HRTICK
cpufreq: add smartassV2 governor
Switch busybox, older version (1.18.4) but slimmer, more appropriate for our needs (from https://faramir.eriador.org/r/).
Minimum frequency to 122MHz at boot, as well as smartassV2 governor.
Optimized ARM RWSEM algorithm
Cleanup after installation of su stuff. We're on a ramdisk after all, we need to conserve memory.
Change location of root stuff so it isn't in the $PATH
Add Simple I/O Scheduler
Add V(R) i/o scheduler
Update to latest Linaro GCC 4.6 compiler.
Two major changes are the addition of the simpleio IO scheduler and the smartassV2 CPU governor. The simpleio scheduler is based on/around the noop and deadline schedulers, designed specifically with non-rotating media in mind (flash disks, hello!). The smartassv2 CPU governor controls how your CPU switches between frequencies (from 122MHz at idle to 672MHz when in use). I haven't done any benchmarks, but these should improve responsiveness and battery life (in theory at least!).
Other than that, the latest Linaro GCC 4.6 compiler, some small optimizations to ARM-specific functions, and ramdisk/boot cleanups. If you're curious about smartassV2 there's more info here, on erasmux's github page here.
Download: noma_20110903v83_boot.img
cm7 nightly bugged one ?????? i dnt like it iz there iz n e fixed cm7 for ideos ????
btw your kernel doesnt works with cm7 and can u please make a kernel for samsung galaxy gio with smartass v2 ??
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
This kernel is meant for stock ROMs
Den15 said:
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
Click to expand...
Click to collapse
Yeah, this kernel was really meant for Froyo stock ROMs. It won't work on CyanogenMod builds because the ramdisk's init scripts are not compatible.
My U8160 kernel repo has a kernel which works on CM7... but you'll have to compile it yourself
nice kernel ........... working fine on ideos u8150-B .... I flash it with stock rom ................. battry becomes efficient ...
Good Job!
Hello aorth,
I'm now using the LEANdroidMOD 5 based on your kernel and I have to say the name NOMA suits it to a tee. It's my default ROM now when I'm not testing your or tilal6991's builds. Thanks and you have yourself a happy holiday season!
hello,
will there be any update of your noma kernel? this is my fav because all roms out there eat my battery like mad, so i just use your kernel and i'm happy with it
greetings
oh man please update, this is one nice kernel!
CM7 u8150 april 5th
IS this already built in to your CM7 last updated april 5th rom or is that a diffrent kernel? which one is better? would it be hard to install it on that rom? whats the advantages over the built in cm7 rom? Thanks sounds awsome anything to make that baby faster is great. Good work
SU Binary Outdated notification
flasehd v83 on the stock 2.2.1 kenya 1 mutli touch rom all went good but whenever i restart the phone su binary shows the notifications bout su binary being outdated which i updated , i did it multiplie times but it comes up everytime the phone is rebooted , other than that su binary working ok ,
dont know how to fix it , other than that the phone is working so responsive , enjoying it
when i flashed the kernel , the phone was already rooted
cheeeeeeeeeeers
G3MOD TEAM
Founder
dharamg3
Kernel Developers
hillbeast , moikop , cool.darshak
Application Developers
dympy , andreapier
ROM/Theme Developers
Stylooo , RafayelG , aarrun
Kernel Features:
Non-OC Version: 83MHz - 667MHz
OC Version: 83MHz - 1200MHz
RootADB
Busybox 1.19
File System Support: rfs/ext2/ext3/ext4
Init.d Scripts
1% Battery Mod
OverClocking
UnderVolt
data2sd
BFQ I/O Scheduler
Voodoo v10
CWM Touch Recovery
Configurable CompCache
BootLogo
TinyRCU
MultiBoot
Kernel Hz: (Non-OC: 250, OC: 500)
tun.ko
100MHz CPU clock stepping
DMA Enabled in G3D
Dynamic OC
Hybrid kernel (supports every firmware for Galaxy 3)
Hybrid Data2SD
Multi Data
NTFS read-only support (but no auto mounting SD card yet)
BLN Support. (Thanks to marcellusbe)
JFS and HFS+ support
CWM Features:
1) Reboot
2) Extended Power Menu
1.1) Power Off
1.2) Reboot
1.3) Reboot Recovery
1.4) Download
3) Update.zip's
3.1) Update.zip from sdcard Root
3.2) Select .zip from sdcard
3.3) Toggle Signature Verification
3.4) Toggle Script Asserts
4) Multiboot
4.1) Switch ROM's
4.2) Backup ROM
4.3) Switch Kernel's
5) Data / Factory Reset
6) Wipe
6.1) Data / Factory Reset
6.2) Cache
6.3) Wipe dalvik cache
6.4) Wipe Battery Stats
7) Backup and Restore
7.1) Backup
7.2) Restore
7.3) Advanced Backup 7.3.1) Boot 7.3.2) System 7.3.3) Data 7.3.4) Cache 7.3.5) sd-ext
7.4) Advanced Restore 7.4.1) Boot 7.4.2) System 7.4.3) Data 7.4.4) Cache 7.4.5) sd-ext
8) Mounts And Storage
9) Advanced
Kernel Downloads:
http://code.google.com/p/g3modteam/downloads/list
Kernel Changelog:
v2.5 (15/05/2012
Supports CM7a8.1
Supports ICS (if colours are screwy, update OpenFIMG)
CWM5 with touch
General source code fixes
v2.4.1 (23/02/2012)]
CM7 A7 support!
Fixed filesystem covertion system.
Lagfree governor properly implemented.
Added BLN support.
Fixed wifi for CM7 (Thanks to Arakmar).
v2.3 (15/12/2011)
Hybrid initramfs: Added support for ICS-based roms.
Multiboot: Fixed dalvik-cache restoring.
Multiboot: Added support for backing up android_secure.
AOSP Proximity sensor support added.
Initramfs: Optimized init.rc files and added usb.rc file.
MAX8998 Driver: Removed led blinking support since it isn't being used anymore.
v2.2.2 (21/11/2011)
Went back to old BLN system, this seems to work fine.
New NON-OC Kernel Hz: 250.
Should have a better battery backup
v2.2.1 (16/11/2011)
JFS Utilities permission fixed.
BLN System fixed.
v2.2 (15/11/2011)
Support for new BLN system.
Optimized SIO Scheduler for flash devices.
Added JFS Utilities (forgotten in the previous release).
Dropped OC+ version support.
v2.1 (09/11/2011)
Lagfree Governor.
83Mhz steps for Non-OC and OC+ version
Lowmemorykiller.c tweak.
Reverted ondemand performance tweak.
Updated BFQ I/O Scheduler to v2.1r1.
Data2SD tweak: Improved IO Performance for non-Data2SD users and fixed *incompatibility* with Kyrillos's App2SD script.
Added Hybrid Data2SD internal System cache.
Compcache is now configurable.
Fixed battery drain problem.
BLN Support. (Thanks to marcellusbe)
Removed InteractiveX governor due to problems.
JFS and HFS+ support.
v2.0 (02/10/2011)
Hybrid kernel (supports every firmware for Galaxy 3 (except Eclair))
CM6.2 and CM7 Support (obviously but it must be said twice)
Adjusted battery driver (more accurate)
83MHz minimum on OC kernel
Hybrid Data2SD
Multi Data
Compcache toggleable
InteractiveX CPU frequency mode
SIO scheduler
MD5 hash disabled on nandroid
More stable at idle
Reduced power drain at idle
jhash3 removed as it increased power drain.
v1.9 (09/09/2011)
tun.ko included and enabled
100MHz CPU clock steppings: you can now set your speed to anything between 100 and 1400MHz in 100MHz step (100, 200, 300...)
CPU minimum frequency now 100MHz on Performance, Ultimate and Extreme
jhash3 for improved HSDPA/3G/EDGE speeds.
Multiboot improved for data backup and recovery
Added Reboot and Wipe Data/Dalvik Cache to main menu of CWM.
DMA enabled in G3D - Thanks marcellusbe
Added InDroid and CM7 to Multiboot
v1.8 [30/08/2011]
Reworked Battery Driver
Reworked CWM Recovery
Now 11 ROM's support in Multiboot
v1.7 [15/08/2011]
Multi Boot
Power off Option in CWM
Dynamic OC (ability to change the maximum freq)
Modify the max_blk_count value to prevent overflow.(sdcard related)
mmc: core: Fix dereferencing after NULL check (sdcard related)
Lower vfs_cache_pressure 100->25.
ARM: fix some sparse errors in generic ARM code
lib: Improve the performance of memcpy and memmove of the general version
lib: Introduce some memory copy macros and functions
ashmem: fix deadlock when system is low on memory
v1.6 [11/08/2011]
Batter Driver Back to Original - Only Change is added Compensation for Data On
Stable OC
UV Works for All Frequencies - Can be checked via dmesg
Removed SavagedZen and SmartAss for now.Giving Problems. Will come back in future versions.
SDCard Partitioning Problem Solved - Ext3 partitioning for mmcblk0p2 - Can be converted to Ext4 Using g3mod app.
Kernel Flashing via CWM Recovery Working
Kernel Hz: Lite:256 Performance:300 Ultimate:500 Extreme: 1000
Noop I/O Scheduler by default
Fixed Typo in Bootlogo
v1.5 [05/08/2011]
CompCache
BootLogo
TinyRCU
Battery Driver Reworked - Please test and give feedback
v1.4 - 31/7/2011
CWM Recovery In Kernel
Fixed CPU Freq Driver. SetCPU now shows properly.
UV working properly now.Can Be Checked in dmesg.
A 1300MHz freq Step in Extreme Version for those who want 1300MHz overclocking.
Changed Kernel Hz to 300 for Better Battery Backup.
v1.3.4 - 27/7/2011
Overclocking Stable (Less freezes) - To Test
BFQ I/O Scheduler - http://algo.ing.unimo.it/people/paolo/disk_sched/
Extreme Version Screen Off Bug Solved
No OC bus for any versions - (For those who want OC Bus, please use v1.3.0 for the moment. I will try to make OC bus in some better manner)
v1.3.3 - 25/7/2011
5 Touch Mod
Removed RAM Optimization Script
Overclocking Stable (Less freezes) - To Test
Solved Bug which showed wrong freq in SetCPU and PimpMyCPU
Solved Time In State for SetCPU
Extreme Version has OC Bus 200MHz
Frequently Asked Questions
For NOOBS
Q) How to flash the kernel
A) Just apply update.zip from Recovery or flash tar file using ODIN.
Q) Will i lose my data if i flash kernel?
A) No, you wont lose any data nor do you have to wipe data or cache.
Q) Does my battery need to be 100% to flash?
A) Not at all
Q)Flashed CM 6.2 Kernel on Froyo Rom and WIFI doesnt work?
A) There are two versions of Kernel. One is for Froyo Rom and other is for CyanogenMod Rom 6.2 (CM 6.2). if you are on Froyo rom and flash CM 6.2 then your wifi wont work and vice versa.
Q) 1400 Mhz (Extreme version) doesnt work for me
A) Not all Galaxy 3 suppport overclocking as high as 1400 Mhz. If it doesnt work then keep frequency lower or flash Ultimate, Performance or Lite version
Q) What does this data2sd in g3mod do?
A) data2sd is method by which all your /data partition goes to your sdcard thus giving you more space for downloading apps. Its suggested to use data2sd only if your sdcard class is higher than Class 6
Q) Internel Memory shows 0kb
A) Check if you have fs.data2sd at this location /sdcard/Android/data/g3mod/ If yes then delete it or else your sd card doesnt have sd-ext partition
Q) How can i go to recovery mode
A) Press MENU+VOLUME UP+VOLUME DOWN+POWER button and bingo!!!
Q) Should i use multi boot even if i am having 2 gb card class 2 ?
A) Sd card with any class can use multiboot
Q) Data Wipe Necessary When Switching Between CM and Froyo ?
A) Yes data wipe is necessary for switching roms between CM and Froyo. But we have given option to Backup data also in recovery.
Q) My APP is not working after Flashing KERNEL
A) Its not a kernel problem
Q) What is tun.ko?
A) It is basically used to setup Open VPN connections
Q) What is jhash3?
A) jhash3 improves the HSDPA/3G/EDGE speed
For Advanced users
Q1) Battery is draining fast?
A) After flashing the kernel please calibrate your battery or else let 3-4 full battery cycles pass.
Q2) Which profiles should i use?
A) Lets take example that you are using Ultimate kernel. Keep the governor ondemand (Like every good boyfriend fulfills all demands of his girlfriend ondemand governor does the same for your CPU ).
Make profiles:-
1) Time Profile - 12 am to 6.00 am Freq 100 Mhz to 400 Mhz Priority 100
2) Screen Off - Freq 100 Mhz to 600 Mhz Priority 95
Q3) What are advanced settings in the SetCPU mean?
A) Sampling rate is rate at which the frequency of your CPU changes. Up Threshold is limit at which CPU will change freq on load (Scales Up). Down Threshold (conservative only) is limit at which CPU will change freq on load (Scales Down). Powersave bias is used for saving the power of CPU, it will slow down the CPU and affect the performance also 200 in powersave bias mean 20%...250 means 25% and so on.
Q4) I want performance and also good battery what profiles should be i use?
A) Refer to Q2 for Profiles Set up and now go in Advanced tab and Keep Sampling Rate 10000 or 15000. Upper Threshold to 90 and Powersave bias to 200 (20%). Since we are using powersave bias, this will affect the performance as it slows down the CPU so to increase the performance we are lowering the Sampling rate thus we get perfect balance of Performance and good battery backup.
NOTE: ABOVE SETTINGS ARE JUST EXAMPLE..PLEASE PLAY AROUND AND CHOOSE SETTINGS WHICH SUITS YOU THE BEST
WATCH THIS NOOBS
Donations:
If you want to donate to the team as a whole, please divide the amount and donate separately to each member. Sorry for the trouble caused.
Thank You for considering to donate.
dharamg3 -
hillbeast -
moikop -
cool.darshak -
Steps for Multi boot:
1) Flash Kernel v1.7+
2) Go to CWM Recovery -> Multiboot -> Backup ROM.
3) Backup your Current ROM to ROM1 (It will backup the system.img at /sdcard/Android/data/g3mod/roms/romname_ROM )
4) Add the system.img of your 2nd ROM to /sdcard/Android/data/g3mod/roms/romname_ROM and similarly for different ROM's.
5) Use the CWM Recovery -> Multiboot -> Switch ROM option to switch between different ROM's.
6) If switching between Froyo ROM and CM6.2 RoM, you will need to wipe data and also change kernel's via update.zip method.
7) Use the data backup and restore option to prevent loss of data when switching between Froyo and CM6.2 ROM's.
Note: Ask the developer of the ROM's to provide you with the system.img for their ROM
How to use Hybrid Data2SD
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo hybrid > /sdcard/Android/data/g3mod/fs.data2sd'
4) Create a text document in Notepad with a list of all the directories you wish to move. Example:
Code:
app
log
dalvik-cache
---LEAVE A BLANK LINE AT THE END---
5) Save the file and call it 'data2sd.dirs'
6) Do 'adb push data2sd.dirs /sdcard/Android/data/g3mod/'
7) Reboot your phone
8) Once your phone has booted, run 'adb shell cat /data2sd.log' to ensure it is running correctly.
How to enable Multi Data
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdcard/Android/data/g3mod/multiosdata'
4) Multi Data will automatically backup your data upon booting into a different OS.
Make sure to not wipe your SD-EXT partition. Doing so will erase the backups from other firmware. Only wipe it if you wish to erase data for everything.
You can also use Multi Data to quickly restore data if your phone has become corrupted. It will restore it back to the last multi-boot switching
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdext/lastos'
4) Reboot the phone
Directories for Multi boot:
//ROM Dir
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod6_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod7_ROM"); //Add CM7 Support
__system("mkdir /sdcard/Android/data/g3mod/roms/G3MOD_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyrillos_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Grigora_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/AOSP_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/DutchMods_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyorarom_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Indroid_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom1_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom2_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom3_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom4_ROM");
//Data + sd-ext Backup Dir
__system("mkdir /sdcard/Android/data/g3mod/data/Froyo_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM6_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM7_DATA");
//Kernel dir
__system("mkdir /sdcard/Android/data/g3mod/kernel/Froyo");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM6");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM7");
How to configure compcache:
If you want to use default configuration (as up to now.. 62 MB aprox.), you don't have to do anything different as what you have been doing. But if you want to use a more/less memory, here are the steps:
Inside that /sdcard/Android/data/g3mod/compcache file, write ONLY the number of MegaBytes you want to use for compcache.
Reboot.
If compcache file is empty or contains a "0" inside, it will use default configuration.
How to: BLN
This is only "needed" if you have a i5801 | i5800L or any other Galaxy 3 model with back button lights and want BLN in it.
How to install:
First, download the lights.GT-I5800.so file from google code. Then execute this commands:
adb remount (or if this doesn't work: mount -o remount,rw /dev/stl6 /system)
adb rm /system/lib/hw/lights*
adb push [Location of this file] /system/lib/hw
After that, reboot and now you have BLN working
Steps for Changing the Max Freq(Dynamic OC):
There is an entry in /sys/devices/system/cpu/cpu0/cpufreq/plls_table where you can put your own value for APLL.
Before doing this, set "PERFORMANCE" governor on and min and max frequencies to the maximum.
Code:
// Do this in adb
echo "0 a[SIZE="5"][B][U]258[/U][/B][/SIZE]0[SIZE="5"][B][U]3[/U][/B][/SIZE]01 a14d0303 c07e13fc cf850240" > /sys/devices/system/cpu/cpu0/cpufreq/plls_table
You need to replace the 258(Hex Value) with your desired value.
Here 258 means
(2*16*16) + (5*16) + 8 = 600
and 3 means it is 600*2 = 1200
Therefore, a2580301 means 1200MHz.
This is a temporary method. For a permanent Method, add this line to a init.d script. Name the script to something like S10_Dyanmic_OC.
Help Others: If you calculate a Hex Value for a particular frequencies add it here:
https://docs.google.com/spreadsheet/viewform?formkey=dG5hdnpsWFdTNExiY2t3dy16VzBvaWc6MQ
You can view all the frequency Hex value's calculated by others over here:
https://docs.google.com/spreadsheet...G5hdnpsWFdTNExiY2t3dy16VzBvaWc&hl=en_US#gid=0
Kernel Related Media:
5 Touch Support:
BootLogo and Progess Bar
Multi Boot
g3mod_v1.3.4_LITE.tar (5.9 MB)
http://www.multiupload.com/3BIF9S2IES
g3mod_v1.3.4_LITE.zip (6.1 MB)
http://www.multiupload.com/9IJTKFIJDX
g3mod_v1.3.3_LITE.tar (5.9 MB)
http://www.multiupload.com/DDMMU0U9YB
g3mod_v1.3.3_LITE.zip (6 MB)
http://www.multiupload.com/DW1QZPDQOY
g3mod_v1.3.4_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/H53ZTO5ULW
g3mod_v1.3.4_PERFORMANCE.zip (6.1 MB)
http://www.multiupload.com/WWFL3EXH0Y
g3mod_v1.3.3_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/Y9CDMFVH61
g3mod_v1.3.3_PERFORMANCE.zip (6 MB)
http://www.multiupload.com/0MQQRR1KV8
g3mod_v1.3.4_ULITMATE.zip (6.1 MB)
http://www.multiupload.com/I4JCH7E5JE
g3mod_v1.3.4_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/TEQXRZMKPQ
g3mod_v1.3.3_ULITMATE.zip (6 MB)
http://www.multiupload.com/97DV0V4OQC
g3mod_v1.3.3_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/KV9SSVWWZ7
g3mod_v1.3.4_EXTREME.tar (5.9 MB)
http://www.multiupload.com/EGZKK89JTZ
g3mod_v1.3.2_LITE Odin
g3mod_v1.3.2_LITE CWM
g3mod_v1.3.1_LITE Odin
g3mod_v1.3.1_LITE CWM
g3mod_v1.3.0_LITE Odin
g3mod_v1.3.0_LITE CWM
g3mod_v1.3.2_PERFORMANCE Odin
g3mod_v1.3.2_PERFORMANCE CWM
g3mod_v1.3.1_PERFORMANCE Odin
g3mod_v1.3.1_PERFORMANCE CWM
g3mod_v1.3.0_PERFORMANCE Odin
g3mod_v1.3.0_PERFORMANCE CWM
g3mod_v1.3.2_ULTIMATE Odin
g3mod_v1.3.2_ULTIMATE.zip CWM
g3mod_v1.3.1_ULTIMATE Odin
g3mod_v1.3.1_ULTIMATE CWM
g3mod_v1.3.0_ULTIMATE Odin
g3mod_v1.3.0_ULTIMATE.zip CWM
g3mod_v1.3.2_EXTREME Odin
g3mod_v1.3.2_EXTREME CWM
g3mod_v1.3.1_EXTREME Odin
g3mod_v1.3.1_EXTREME CWM
g3mod_v1.3.0_EXTREME Odin
g3mod_v1.3.0_EXTREME CWM
Source For Developers:
https://github.com/dharamg3
Note:
We am learning how to develop kernels.
We willl add different features as and when we can implement them.
The main goal of this kernel will be to keep the phone stable and fast.
There will be nothing as alpha or beta releases.
We will give out the kernels directly, but if anything goes wrong and you have to reflash the ROM or kernel, please dont start shouting.
You may give us different ideas on what features to implement. We will try our best to implement all the features you want
Many of the features implemented in this kernel, are taken from marcellusbe's Fugumod Kernel, and we shall be ever thankful to marcellusbe for the fugumod kernel
Warning:
We are not responsible for any damage caused to your phone (softbrick or hardbrick)
Credits:
marcellusbe for all his help, awesome fugumod kernel
supercurio for voodoo v10
Paolo for BFQ I/O Scheduler
All developers for making this an awesome phone
Everyone who is helping is solving different issues with this kernel
Please let us know if we miss anyone ...oh we did already miss someone..thanks G3MOD TEAM too
What to the old thread?
Nm read that
Btw 6th post got some errors...
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
kyrillos13 said:
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
Click to expand...
Click to collapse
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
hillbeast said:
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
Click to expand...
Click to collapse
getting 2.5 to support other partitions will be a better idea...coz for CWM 4 you need complete CM7 source, and also most of the update.zip's on the g3 forums use amend...and CWM 4 supports only edify....
All the best to the future process
Sent from my GT-I5800 using XDA App
Right, I want to work on USB OTG but lack the cable, and the only way I can do it with what I have is if I destroy my only USB cable for my phone. So if someone wants me to do USB OTG, then buy me a cable and I'll do it
All the stuff is there to do it, I just need to get the phone to switch into host mode.
I think v1.9 is going to come sooner than expected...excellent work by the whole team...
Will this root my phone if I install this in Stock ROM?
[email protected] said:
Will this root my phone if I install this in Stock ROM?
Click to expand...
Click to collapse
it will give you ADB Root, but not the superoneclick root...
dharamg3 said:
it will give you ADB Root, but not the superoneclick root...
Click to expand...
Click to collapse
Ok thanks.....
I am a newbie at this...
But, which root did I get when I installed Kyrillos' ROM?
Fusion Ultimate Kernel for all Sense-based 4.0.3 ROMs
Latest Version: v3.4 (9/1/12)
Disclaimer:
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.
* 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. :P
* blah blah blah you get the point.
*/
As many of you probably already know, I had another 'Fusion' kernel for the S4 HTC One S. However, because I incorporated mdeejay's patches, the kernel did not play nice with the CPU and whatnot. I nuked my repo, imported the T-Mobile US kernel sources, and re-built the kernel from scratch. I wanted to start a new thread so people would not mix up this and the old kernel.
Click to expand...
Click to collapse
Post #1: Release, Features, and Downloads
Post #2: Changelog
Post #3: How to compile from source
Post #4: Frequently Asked Questions
Features
[*]CPU frequency control from 192Mhz 1.89Ghz
[*]your choice of stock or overclock options
[*]universal package
[*]zip package with modified init.qcom.post_boot.sh and thermald.conf
[*]voltage control (use System Tuner Lite/Pro)
[*]SmartassV2, Interactive, Conservative, LagFree, Lionheart, BrazilianWax, Intellidemand, InteractiveX, SavagedZen, and Smartass CPU governors added
[*]Simple IO (SIO) and V(R) scheduler added
[*]capacitive LED lights dimmed to 2mA
[*]improved media scanning times (increased readahead buffer)
[*]good multitasking
[*]enabled zRam (see FAQ for a detailed explanation of what it does)
[*]greatly improved I/O performance (disabled fsync() )
[*]XZ kernel compression
[*]overall good battery life and performance
[*]optimized and tweaked
[*]much more; check the changlog or my GitHub if you want to know the specifics
Click to expand...
Click to collapse
Downloads
Do NOT flash versions 3.0 and higher in recovery!! They are 7zips!!
I purposely made it a 7zip archive so people don't flash it. Instead, extract the appropriate zip from the package and then flash like before. You get options of whether you want overclock or stock clock. The zip will flash the correct files and modules according to your choice and then clean out conflicting init.d scripts for the best possible compatibility.
All Downloads are HERE
How to Install
For hboot 1.09 and below:
Just flash the zip in TWRP recovery. It will automatically flash the boot.img for you.
For hboot 1.13 and up:
you have two options
Option #1
Use TWRP's HTC Dumlock feature. It is a pretty neat workaround that allows you to flash boot.imgs in recovery even on a higher hboot.
Look here for instructions from TeamWin. If you are not comfortable with this method, then follow option #2 to manually flash in fastboot.
Option #2
In addition to flashing the zip, you will have to extract the boot.img from the package and flash it manually with fastboot. Blame HTC for the half-assed 'unlock bootloader' offering they give us. Hopefully we will get S-OFF soon...
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
Look here for a guide.
Sources
initramfs: https://github.com/klin1344/initramfs_ville
kernel: https://github.com/klin1344/kernel_ville_US
Enjoy
Changelog/Complete Feature List
Changelog
v1.0 (Initial Release 7/24/12)
re-wrote overclock code
completely re-based on the TMOUS source
init.d scripts support with Busybox run-parts
overclocked up to 1.89Ghz
added 192Mhz step
added SmartassV2 CPU governor (still finicky; needs more testing)
enabled Conservative and Interactive CPU governors
added SIO scheduler and enabled as default
increased readahead buffer
various tweaks for UI responsiveness
stable
v1.1 (7/27/12)
cleaned up CPU code (all frequency issues should be gone by now; check github for full details)
added LionHeart CPU governor
added LagFree CPU governor
reduced capacitive LED brightness to 2mA (looks better)
tuned Interactive CPU governor parameters
many optimizations; check github for more details if you want
v2.0 (7/29/12)
added voltage control capabilities (use SetCPU or similar app to UV)
cleaned up CPU code again to try to get frequencies to stick
v2.1 (7/31/12)
added V(R) IO scheduler
change to a zip package
modified init.qcom.post_boot.sh and thermald.conf
added modules in the zip so it shouldn't break WiFi on EU ROMs anymore
allowed undervolting minimum of 400mV
tweaked minfree and ADJ values for multitasking and performance; the used values were from the V6 OOM Calculator
Conservative CPU governor as default for battery life (use an app to change it if you want)
defaulted CPU frequencies to 192Mhz 1.5Ghz on boot
v2.2 (8/2/12)
enabled zRam
adjusted VM ratios
added NEON and Snapdragon optimizations
v3.0 (8/8/12)
fixed SmartassV2 for performance and battery life
available with overclock or stock CPU clock
enhanced compatibility with many ROMs
cleaned up post_boot script and many parameters now handled @ kernel
fixed CPU reverting to min 384Mhz
overall much, much cleaner implementation and settings will stay
v3.1 (8/16/12)
a universal package
disabled fsync() for I/O improvement
optimized Ondemand CPU governor settings
v3.2 (8/22/12)
lighter OOM and ADJ settings for better multitasking
v3.3 (8/29/12)
added BrazilianWax, Intellidemand, InteractiveX, SavagedZen, and Smartass (V1) governors
added tun.ko and cifs.ko
XZ kernel compression
optimized SmartassV2 CPU governor
v3.4 (9/1/12)
added wifi module to the zip
tun.ko and cifs.ko now built into kernel
tweaked deadline I/O scheduler for better performance
make kernel use AC charging mode for unknown chargers
various lowmemorykiller fixes
fixed and tweaked a few other things
Click to expand...
Click to collapse
For Developers
How to build this kernel from source:
This is assuming you already have your Linux environment setup and installed the required packages for compiling a kernel.
1. Clone my initramfs and kernel sources.
Code:
git clone git://github.com/klin1344/kernel_ville_US.git
git clone git://github.com/klin1344/initramfs_ville_4.0.3.git
2. Compress the ramdisk into a gzipped archive. First navigate to the initramfs_ville_4.0.3 directory, then:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.gz
3. Grab the toolchain from DoomLord's handy repo:
Code:
git clone git://github.com/DooMLoRD/android_prebuilt_toolchains.git toolchains
4. I have created an easy build script. Modify the top four lines to be applicable to your setup. Make sure CROSS_COMPILE is set to the directory of the toolchain we just downloaded earlier (there are two; not the Linaro one). And change INITRAMFS_DIR to the directory of the ramdisk.gz you created earlier.
5. Build. First navigate to the kernel_ville_US directory.
Code:
./build.sh ville_defconfig
for the stock option or
Code:
./build.sh ville_oc_defconfig
if you want the overclocked option.
The script will detect the number of cores of your CPU and automatically make with the optimal -j#.
6. If all goes well you should end up with a boot.img in the kernel_ville_US directory.
FAQ.... Please read this before posting questions!!!
FAQ
Frequently asked questions. Please read all of this first, and then if it doesn't answer your question, feel free to ask in the thread. I just don't want to have to keep answering Is this kernel SENSE based? or How do I jailbreak my HTC One S??? type of questions. Lol. :silly: Thank you.
Click to expand...
Click to collapse
What ROMs is this kernel compatible with?
As stated in the OP, this kernel is compatible with all S4 devices running a 4.0.3 Sense-based ROM. It is NOT compatible with the new 2.21 RUU, which is Android 4.0.4 based. We will have to wait until HTC releases the new kernel source because the differences are not only in the initramfs.
What is the best governor for me to use?
It really depends on what you're looking for. If you want performance, go with Lionheart or Ondemand. If you want battery life, go with Conservative. And if you are looking for a balance between battery life and performance, then use either SmartassV2, Interactive, or LagFree. These are just my opinions. Look here for a great reference of all the CPU governors. Test them out and decide which works best for you.
Which I/O scheduler is the best?
I personally use SIO, but you can test and decide which is the best for you. Read here to find the pros and cons of each one.
How do I overclock?
The kernel should default at 192Mhz 1.5Ghz CPU clocks. To overclock, use SetCPU, No-Frills CPU, System Tuner Lite/Pro, or any similar CPU control app. Some apps don't allow the settings to stick properly. I recommend using No-Frills or System Tuner.
How do I undervolt?
Right now, the only app that works for voltage control is System Tuner. Both the Lite and Pro versions allow you to change the voltages. Do not use SetCPU as it doesn't work.
Here is the voltage table I am currently using:
Code:
1890mhz: 1250 mV
1809mhz: 1225 mV
1728mhz: 1200 mV
1674mhz: 1175 mV
1512mhz: 1150 mV
1458mhz: 1137 mV
1404mhz: 1125 mV
1350mhz: 1125 mV
1296mhz: 1100 mV
1242mhz: 1100 mV
1188mhz: 1075 mV
1134mhz: 1075 mV
1080mhz: 1025 mV
1026mhz: 1000 mV
972mhz: 1000 mV
918mhz: 975 mV
864mhz: 975 mV
810mhz: 950 mV
756mhz: 950 mV
702mhz: 900 mV
648mhz: 900 mV
594mhz: 875 mV
540mhz: 850 mV
486mhz: 800 mV
384mhz: 725 mV
192mhz: 650 mV
Please just take these as a grain of salt; not all chips are created equal! Some devices can become an ass when it comes to undervolting, while others can starve the CPU to death and still run fine. Experiment little by little until you find your perfect voltages.
What is zRam and how does it work?
Originally Posted by faux123
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Click to expand...
Click to collapse
WiFi doesn't work???
Flash the alternative modules package in the OP. It is for EU based ROMs as well as MIUI Sense-based. You only need to flash it once, unless you change or update your ROM.
Nice..Will do testing...
Hopefully it give the best battery life than stock
Thank you sir!
(S4) HTC 1s
Here is a zip to flash the kernel! Testing with Axiom S v1.8, will test battery with SmartassV2
nieves53 said:
Here is a zip to flash the kernel! Testing with Axiom S v1.8, will test battery with SmartassV2
Click to expand...
Click to collapse
Thanks. But unfortunately the reason I did not make it a zip is because that some of us who are on hboot 1.13 or higher can't flash boot.img's in TWRP recovery at all. The same goes for radios. I stupidly ran the 1.78 RUU, which update my hboot from 1.09 to 1.13. :crying:
klin1344 said:
Thanks. But unfortunately the reason I did not make it a zip is because that some of us who are on hboot 1.13 or higher can't flash boot.img's in TWRP recovery at all. The same goes for radios. I stupidly ran the 1.78 RUU, which update my hboot from 1.09 to 1.13. :crying:
Click to expand...
Click to collapse
Should have just flashed the radio
How do you like the new radio? I seem to be getting a lot better service and a more stable WiFi connection.
Liking the kernel so far
Sent from my HTC VLE_U using xda premium
Bug I found -
-While install apps it take awhile for it to install. (1mins or 2min). I just phone the sit until it finish install
-After reboot ...the kernel take awhile for it kick in. For example..If you have email it will take awhile to prompt on notication bar .
Is it possible you can post zips for download in the OP? Thanks. Will try tomorrow.
x1tyme said:
Bug I found -
-While install apps it take awhile for it to install. (1mins or 2min). I just phone the sit until it finish install
-After reboot ...the kernel take awhile for it kick in. For example..If you have email it will take awhile to prompt on notication bar .
Click to expand...
Click to collapse
Maybe try wiping data / factory reset? To be honest those sound more like rom issues rather than kernel related issues.
I cannot reproduce it.
Sent from my One S
klin1344 said:
Maybe try wiping data / factory reset? To be honest those sound more like rom issues rather than kernel related issues.
I cannot reproduce it.
Sent from my One S
Click to expand...
Click to collapse
My fault. I was lazy and flash the flashable zip on post #7 and create this error. Reflash rom and fastboot usb and works like a charms..:good:
If you need another guy to test a 4.0.4 Pre-Release...
(i'm under Trick 6.0)
plakers said:
If you need another guy to test a 4.0.4 Pre-Release...
(i'm under Trick 6.0)
Click to expand...
Click to collapse
+1 but the thing is a bit complicated because we need current modules because of better wifi signal.
I guess we'll just have to wait for the new kernel source from 2.21 base
just flashed it with axiom v1.8.0
everything seems to be working fine.. it's fast smooth stable
nice stuff, Klin
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Elloco305 said:
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Click to expand...
Click to collapse
Have anybody experience there screen blink? Or just Rom issue
Sent from my HTC VLE_U using Tapatalk 2
Elloco305 said:
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Click to expand...
Click to collapse
What app are you using? I use No-Frills CPU and it has the "apply on boot" option.
klin1344 said:
What app are you using? I use No-Frills CPU and it has the "apply on boot" option.
Click to expand...
Click to collapse
Setting don't stick after reboot. I'm using setcpu
Also, When I applied this kernel..my screen flick across the screen while exit app (es explorer)
hi guys...Greets from Italy! i've builded this kernel for getting optimal performances with my acer liquid glow. This can be used with Stock rom and with Vache's glowing liquid rom.
HOWEWER , SINCE THAT SOME USERS REPORTED THAT VACHE'S KERNEL(LIKE ME) DOESNT' WORK ON SOME DEVICES, DO A NANDROID BACKUP WITH CWM RECOVERY FIRST.
Flash this .zip with recovery
This is the changelog
V1:
Added lazy, smartassv2, intellidemand, lagfree governor (change that with nofrills or setcpu)
Added Sio and vr I/O schedulers (change with nofrills or setcpu also that)
Added a Cortex A5 optimization
fixed wrong format for Adreno200 (first was RGBA_8888 now it's RGB565 that's is handled well with this GPU)
increased read-ahead values
new memory allocator : SLUB
improved the performances of memcpy and memmove of the general version
Click to expand...
Click to collapse
Download Link: https://hotfile.com/...nel_v1.zip.html
Sources are here: https://github.com/l...uid_Glow_Kernel
I also want to thanks Vache for his hints and porting recovery to this device. Without his help this couldn't be possible.I'm also starting to work to jelly bean update but i have no time for now
Links are not good with the '...'
[EDIT] Found correct link in other forum, will try it soon
Some random reboot, directly in fastboot mode, but very rare and less than Vache's kernel. If I do a clean cache and dalvik, it's ok for 3 weeks, and boom, reboot.
New Edit: I found this thread with V3 version, will try it soon:
Hey all,
This kernel works on stock 4.2 ROM's only.
Disclaimer
This kernel, in any way, won't make your device fly or break antutu charts. What I can only promise is a consistent performance with reliable battery life.
Instructions:
flash zip in recovery
Features:
Integrated CWM
Linaro 4.9.1
kexec hardboot support
Full SELinux Support with upstream fixes
Userspace voltage control
Updated prima wlan with CAF fix for delayed notifications
1.2 GHz max frequency
More GPU clocks with optional overclock to 450 MHz
CAF backport fixes
vibrator intensity control
Kill debug wherever possible to reduce overheads
general tweaks here and there
Note: For full in-depth info, checkout my commits and release notes. I am not huge fan of bloated feature list since end-user may find it too difficult to grasp.
Although every feature is controllable through sysfs, I would still recommend trickster mod or kernel tuner app for tweaking.
Kernel will boot with my recommended settings but you can change them if you know what you're doing.
Download
Source
Release Notes
1. r1
* Initial release
* Hotplug driver: This kernel uses stock mpdecision by qcom. I won't be switching to other custom hotplug driver in a foreseeable future.
* Single initrd: I wasn't happy with standard method of packing two ramdisks inside an initrd. This caused unnecessary cpu overheads while decompressing boot ramdisk especially heavily compressed ones like xz and rewriting data to rootfs /. So I forked a process from init.rc to detect keychecks and exec recovery init from stock initrd itself. This improves upon the situation above by having everything we need in stock initrd itself. Boot times also become relatively shorter. I would recommend kernel developers to switch to this method.
* Kexec Hardboot : zip will automatically install all required kexec binaries.
Place your zImage and ramdisk.img in /sdcard/kexec/* and in terminal type:
do-kexec.sh
kexec -e
* Vibrator intensity control:
sys interface is located at /sys/devices/virtual/timed_output/vibrator/level
* Updated Prima: Stock fw used ancient prima 3.2.1.1h. I upstreamed it to 3.2.2.0 with CAF fix for delayed wifi notifications.
* sched_mc_power_savings = 1
Tries to group tasks into least cores possible. Battery friendly. 1 is moderate. 2 is extreme. 0 disables it.
* Userspace voltage control by @faux123:
I modified the original code by introducing a useful pr_info to actually output voltage change requested in mV. Also some cosmetic conditional and looping changes.
To determine the last voltage change, type dmesg | grep requested
The sys interface is located at:
/sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels.
Sample command to decrease voltages at all frequencies by 10mV
echo "-10000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
By default, kernel comes with 20mV undervolt.
* patch CVE-2014-0196
* add row and sio iosched
* Enable writing to hardware rtc
* More gpu scaling levels : 450 MHz and 128 MHz
* External modules.zip : cifs.ko, ntfs.ko, nls_utf8.ko, hid-sony.ko
* HID driver for Sony / PS2 / PS3 BD devices : hid-sony.ko
ramdisk will automatically insmod it if found.
* VM_MAX_READAHEAD512
* sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
* lib: Update RWSEM to Linux 3.10
* lib/int_sqrt.c: optimize square root algorithm
* enable some more TCP Cong methods
* deadline tweaks
* partially nuke cci stuff
* switch to noatime and nodiratime
This option stops recording the last file access time when the file is just read. The noatime option eliminates all the writes to the disk each time a file was just read which previously used to happen with atime. However a write is made to a disk in case if a file is being changed/written. Easy on cpu and battery.
* tick: Upstream fixes
* xz compression for zImage ( best compression ratio ) and gz for ramdisk
* kill debug such as DETECT_HUNG_TASK, DEBUG_ATOMIC_SLEEP etc. which cause unnecessary CPU overheads
* enable adb RSA authentication
ro.adb.secure=1
* ro.debuggable=1
* Various CAF backport fixes including fixes to SELinux
Please don't ask for:
1. Anything that ends with *to-wake/sleep/dance
Got a bug?
cat dmesg and pastie me.
Credits:
@faux123: for voltage control
@franciscofranco: for some patches I took from his mako repo
@varun.chitre15 : for some patches i took from his caf repo
1.17 fw + vengeance r1 super smoooooth thank you
Great work
Thanks a lot
Sent from my C2105 using XDA Premium 4 mobile app
Ah, another great work from you. Gonna try it tomorrow!
Again, thanks for the work! I'm your loyal kernel-user since i got my miro vengeance-ed
Offline charging was borked due to ramdisk. Links reupdated with fixed version. Also softer vibrate when entering recovery.
Make this kernel available to CM11 4.4.4 KitKat please
Because most of us are currently using CM11
Sparksys said:
Make this kernel available to CM11 4.4.4 KitKat please
Because most of us are currently using CM11
Click to expand...
Click to collapse
although im agree with your comment "Make this available for cm", if there is no devs for JB, then this device will die. Its nice to have someone who still developing JB Kernel
FajarMF28 said:
although im agree with your comment "Make this available for cm", if there is no devs for JB, then this device will die. Its nice to have someone who still developing JB Kernel
Click to expand...
Click to collapse
You are right
Even TZ and phantom must back to support jb
Sent from my Xperia L using XDA Premium 4 mobile app
Great work!!
Hello everyone. I tell them that I decided to try this kernel. Return to the stock ROM, take a few hours and the phone is going well, really feel the change, note the phone faster, more stable, the battery has performed very well so far no trace of the sensor bug the only bad thing as it is that if we turn off the phone's date and time settings are lost.
i need flash external modules too?? *unsure*
for now i flashed vengeance zip only ... how to fix date error?
thedemon786 said:
i need flash external modules too?? *unsure*
for now i flashed vengeance zip only ... how to fix date error?
Click to expand...
Click to collapse
You can read more about external modules in release notes.
Can you clarify a bit more on date issue?
rachitrawat said:
You can read more about external modules in release notes.
Can you clarify a bit more on date issue?
Click to expand...
Click to collapse
i think he mean that
Time and date rest in every reboot
Like is happened before with kk ROMs (just think)
Sent from my Xperia L using XDA Premium 4 mobile app
david makarove said:
i think he mean that
Time and date rest in every reboot
Like is happened before with kk ROMs (just think)
Sent from my Xperia L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Strange. I just rebooted my phone and there's no reset. Maybe I'll investigate later. I have been busy lately. [emoji1]
i was sent to 1970 LOL ... only at first boot ... its fine now
thedemon786 said:
i was sent to 1970 LOL ... only at first boot ... its fine now
Click to expand...
Click to collapse
Why some heavy 3d games have random stuttering effect after some time of playing them.. (frontline:commando 2 for example)
When i clock it to 1188 it does give me that lag free performance of some heavier games compared to stock kernel. (actuly it gives me the best performance in terms of gaming.... beats almost all other kernels. Even thunderzap and phantom can't reach this type of smoothnes in terms of gaming...but then again its custom 4.4 so i got used to lag).
Games runs amazing on 1188 but after some time it just get random freeze and start stuttering...can't even get to handle my phone to quit from the app because it wont get back to normal)
Any specific solution to this problem?
PS: Im back on stock because it doesn't have this issue with stuttering and if it does it only last for few seconds but the performance is quite lower then vengeance...
vuk030 said:
Why some heavy 3d games have random stuttering effect after some time of playing them.. (frontline:commando 2 for example)
When i clock it to 1188 it does give me that lag free performance of some heavier games compared to stock kernel. (actuly it gives me the best performance in terms of gaming.... beats almost all other kernels. Even thunderzap and phantom can't reach this type of smoothnes in terms of gaming...but then again its custom 4.4 so i got used to lag).
Games runs amazing on 1188 but after some time it just get random freeze and start stuttering...can't even get to handle my phone to quit from the app because it wont get back to normal)
Any specific solution to this problem?
PS: Im back on stock because it doesn't have this issue with stuttering and if it does it only last for few seconds but the performance is quite lower then vengeance...
Click to expand...
Click to collapse
try permormance gov maybe?
thedemon786 said:
try permormance gov maybe?
Click to expand...
Click to collapse
It has nothing to do with gov settings...
I encountered this with older version of phantom or thunderzap for JB also but never had it on kitkat.
Problem is that current kitkat kernels doesn't give that much of a boost in termps of gaming..... (atleast not for me)
I remember Varun mentioning about flashing the kernel immediately after u flash the ROM file, ftf in this case. Try that. Also means you will have to format your device.
Great Kernel
rachitrawat said:
Strange. I just rebooted my phone and there's no reset. Maybe I'll investigate later. I have been busy lately. [emoji1]
Click to expand...
Click to collapse
Greetings friend, I congratulate you for your great contribution, I am testing and everything is going well. In my case also is being presented the problem that I lose the time and date settings every time I reboot the phone. addition also happens that my manager asks me root file permissions every time I go to do some operation (copy, paste, etc.) and folders are appearing very strange names in both internal and external memory. Thanks for your help.
Yep, date and time resetted every boot. Just like the old version of Thunderzap JB bugs. I think Varun has already fixed that.