[Kernel] CeXstel v0.62 (Y300/G510) [Stock/CM] [29/03/14]

[Guest Victod]

Very good 0.57, look antutu bench and Quadrant

Can u post detailed scores from Antutu?

Edited January 19, 2014 by Victod

[Guest bossman123]

I must admit ive been critical about this kernal, but ive just installed this along with a fresh install of b199 stock and so far its very good..7500 in antutu..dont know how you got 8000+ though ^^^

 

arhh ure on the G510..still, impressive

Edited January 19, 2014 by bossman123

[Guest ZolaIII]

I must admit ive been critical about this kernal, but ive just installed this along with a fresh install of b199 stock and so far its very good..7500 in antutu..dont know how you got 8000+ though ^^^

arhh ure on the G510..still, impressive

7.5K is standard score i got 8K some time ago...

[Guest jaccs]

this score is take with Gamer RomV3 final

[Guest NaqiKiller]

Why my device is working slow?? :(

[Guest knueller]

Dont know, mine is 400 Points slower than yours.

[Guest SH3H1]

@NaqiKiller

No it isn't :P

Why do you think that?

You scores are not bad ;)

What Jaccs post was the score for G510 with gamer ROM v3...so your phone is fine :*

[Guest NaqiKiller]

Really......

[Guest NaqiKiller]

Great...

[Guest mockingbird]

Great...

Your phone is in bad shape is gonna explode at that low score , how can it boot up ? Lol *trollface* In a non troll way , forget about antutu scores , those mean s**t , that scores doesn't show the actual performance of the device.

[Guest bossman123]

RAM Free seems to be really low with this kernal..355MB used and 51MB free, hardly no apps installed to be fair, stock kernal used to be about 140MB free, why the big hit??

[Guest ZolaIII]

RAM Free seems to be really low with this kernal..355MB used and 51MB free, hardly no apps installed to be fair, stock kernal used to be about 140MB free, why the big hit??

It's not kernel or predefined OOM, it's something you did with probability OOM settings...

[Guest Wetito]

i have a G330. My Antutu score is 7740!

 

RAM Free seems to be really low with this kernal..355MB used and 51MB free, hardly no apps installed to be fair, stock kernal used to be about 140MB free, why the big hit??

 

i have 200mb free

[Guest Domino2115]

And what rom are you using. Any stock one?

[Guest Wetito]

cm10.1 by Kratos

[Guest Reasonz21]

This is kernel for our y300 and g510.

It's beta version .

Features:

-3.4.2 kernel version

-New Freq Table - 19Mhz / 65Mhz / 98Mhz / 196Mhz / 320Mhz / 480Mhz / 700Mhz / 1008Mhz / [1209Mhz - g510]

-Underclock

-Dynamic fsync v2

-Increase available ram (depends on version which you choose)

-CPU voltage control VDD sys interface (only for y300)

-Schedulers : fiops / noop / dedline / cfq / sio / row / vr / zen / fifo

-Governors : interactive / conservative / userspace / powersave / ondemand / preformance / smartassv2 / smartmax / badass / asswax / wheatley / dancedance / intellidemand / lulzactive / hyper / lionheart

-TCP congestion control algorithms: westwood / vegas / veno / cubic / reno / bic / htcp / lp / scalable / yeah / llinois / hybla / highspeed

-TCP westwood as default

-Optimized AES and SHA1 routines

-LowMemoryKiller management of not killable processes

-Timer slack controller

-CK3 Tweaks

-Optimized SLUB memory allocator

-Dynamic management of the minimal timer slack value during suspend/resume

-Compile with -O3

-ARM flags optimization

-Linaro 4.6.2

-FRandom

-Swap support

-Lowered swappiness 60->45

-Zram (?)

-Dynamic dirty page writebacks

-Doubled readahead values

-Fast Charge (untested but i think it need some fixes)

-A little bit overclocked gpu [gpu freq steps : 192Mhz / 245Mhz / 320mhz]

-Different compresion type

-Disabled Gentle Fair Sleepers for better UI performance

CeXstel v0.57 for CM10 :

v0.57 (407MB ram)

v0.56 (407MB ram)

v0.55 (420MB ram) *

v0.55 (407MB ram)

v0.55 (~400MB ram)

v0.55 (393MB ram)

v0.47

CeXstel v0.57 for CM10.1 :

v0.57 (407MB ram)

v0.56 (407MB ram)

v0.55 (420MB ram) *

v0.55 (407MB ram)

v0.55 (~400MB ram)

v0.55 (393MB ram)

v0.54

v0.5

v0.47

CeXstel v0.57 for Stock :

v0.57 (407MB ram)

v0.56 (407MB ram)

v0.55 (420MB ram *

v0.55 (407MB ram)

v0.55 (~400MB ram)

v0.55 (393MB ram)

v0.54

v0.5

v0.47

v0.3

*unsupported (only for advanced users)

Changelog

 

v0.57

-update of kernel from 3.4.1 to 3.4.2

-Compile with -O3

-ARM flags optimization

-back to linearo 4.6.2

-deleted CIFS support

-fix backlight buttons on CM

 

v0.56

-new cpu governors : intellidemand, lulzactive, hyper, lionheart

-vibrator intensity sysfs

-deleted some patch from v0.52

v0.55

-fix problem with video (?)

-four variations of kernel

-deleted ARM RWSEM algorithm

-deleted all process from "do not killable list"

v0.54

-lowered minimal cpu freq : 19Mhz

-better support for VPN over IPsec

-new freq step for gpu - 245Mhz

v0.53

-CK3 Tweaks

-optimized ARM RWSEM algorithm

-lowered swappiness 60->45

-fix lags

v0.52 (big update)

-timer slack controller

-dynamic management of the minimal timer slack value during suspend/resume

-extra free kbytes tunable

-optimized SLUB memory allocator

-softirq: reduce latencies

-changes in ramdisk

-lowMemoryKiller management of not killable processes

-change initial readahead window size calculation

v0.5

-optimized AES and SHA1 routines

-tweak vm dirty ratios

-new schedulers : vr / zen / fifo

-fix booting on g510

-deleted 1104Mhz

v0.49

-new cpu governors : badass, asswax, dancedance, wheatley

-fix booting on g510 (?)

-deleted 1305Mhz

v0.48

-tcp congestion control : yeah, llinois, hybla, highspeed

-tcp westwood as default

-new scheduler : row

-underclock for all devices (like g510 etc.)

-add overclock for g510 (1104mhz & 1305mhz) [untested]

-fixed radio fm

v0.47

-some changes in memory mapping [experimental]

-increase available ram from 393mb to 403 mb

v0.46

- dynamic dirty page writebacks

- tcp congestion control : scalable & lp

- some other changes

v0.45

- underclock (min = 65mhz)

- dynamic fsync v2

- doubled readahead values

- tcp congestion control : bic & htcp

- zram

v0.43

-TCP congestion control algorithms: westwood ,vegas ,veno ,cubic, reno

-fixed dancing screen on g510

v0.42

-update of kernel from 3.4 to 3.4.1

-Disabled Gentle Fair Sleepers for better UI performance

-CPU voltage control VDD sys interface

v0.4 (big update)

-CIFS

-Linaro 4.8.2

-FRandom

-new scheduler : fiops

-different compresion type

-small size now only ~4.4mb

-Fast Charge (untested but i think it need some fixes)

-temporarily deleted cpu oc

v0.3

-fixed "milk screen" (thanks dazozzo)

-improved stability

-fixed bluetooth

-fixed some random reboots

v0.25

-a little bit overclocked gpu (from 300mhz to 320mhz)

v0.21

-swap support

v0.2

-smaller screen issuse

-improved stability

-a bit better performance

-only two schedulers (sorry for this I will add more in next version)

-cleanup source

v0.1

-Initial Release

Buglist:

-zram on stock

-19Mhz need some fixes (?)

-video on 420mb ram version

Special features:

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.

How to enable/disable the Dynamic FSync (default enabled):

1) By downloading and using Trickster MOD

2) By directly editing the file /sys/kernel/dyn_fsync/Dyn_fsync_active and setting 1 to enable the dynamic fsync, 0 to disable it (note that set value will be lost after a reboot/shutdown)

Dynamic dirty page writebacks

This feature has been developed by me 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).

- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off).

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)

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.

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

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)

LowMemoryKiller management of not killable processes

This feature allows to define processes and system processes white-lists filled with the preferred process names and to not be killed by lowmemorykiller, unless it is absolutely necessary.

This feature exposes four new lowmemorykiller parameters:

- donotkill_proc, is the flag to enable / disable this feature for the processes chosen by the user

- donotkill_sysproc, is the flag to enable / disable this feature for the system processes chosen by the user

- donotkill_proc_names, is the list of process names (comma separated) chosen by the user to be preserved from killing

- donotkill_sysproc_names, is the list of user system process names (comma separated) chosen by the user to be preserved from killing

When the lowmemorykiller needs to free ram, it will first kill the processes not included inside the two process name lists chosen by the user.

If there are no more standard killable processes, then it will be necessary to kill one of the processes included inside one of the two white-lists, to prevent system hangs, slowdowns, etc

How to customize the white lists of processes to preserve from killing:

1) By directly editing the files inside /sys/module/lowmemorykiller/parameters (note that set values will be lost after a reboot/shutdown)

2) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)

Frandom - Fast Random Generator

As Eli Billauer (the creator of this module) said, Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.

(source - xda forum)

Thank to Christopher83 for description

Thanks :

Kra1o5

Christopher83

Asis92

Dazozzo

ZolaIII

hey could you tell me how install the kernel?

[Guest Gliwusss]

install zip with kernel from recovery :)

[Guest vitals]

1209Mhz does not work on g510

Edited January 24, 2014 by vitals

[Guest Domino2115]

What is better this kernel or stock one?

[Guest fonz93]

What is better this kernel or stock one?

this

[Guest EloYGomeZ]

CM11 ????

[Guest noemi.abril]

of course this kernel is best

[Guest Victod]

@Ceastel..!
 
Where is located Frandom.ko module?

and, in my results of Frandom test, seems that this feature is not optimized according to Christopher83's post.

 

 

Frandom - Fast Random Generator

As Eli Billauer (the creator of this module) said, Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.

How to test if frandom builtin module is correctly working:

 

- Download the script named frandom_test.sh
- Using your preferred file explorer, copy the file inside the folder /data/local of your device
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Open Terminal Emulator
- Run this command

/data/local/frandom_test.sh

You should see a result similar to this one:

 

If the urandom tests take more than 1 or 2 seconds and are more different than related frandom tests, then the random number generation is not fully optimized for your currently used kernel...

http://forum.xda-developers.com/showthread.php?t=2183378

[Guest ZolaIII]

Nothing uses random in Android! With a possible expectation of Google map's?!

You don't need aditional/faster fill in sources as nothing use it.

If the pool is full it will only represent potential security threat!

& its not integrated as external (ko) module bat internal sh.

Edited January 25, 2014 by ZolaIII

[Guest eilex17]

Hi!! This kernel work msm8225q??? Sorry for my bad english, im spanish,,,