Related
I absolutely take no creative credit in making this kernel as all I have done is putting them together and build based on the LEO kernel tree. The real credit goes to them.
I am using a TMobile HD2 / ChuckyDroidROm / Radio 2.12.50. Please note that the HAVS does not work well with interactive governor (but it may still works for you device). If you are experiencing scrolling lag, try the kernel without BFS feature.
I did not go through each one of them. I have only tested the BFQ-OC-UV-AXI-850mv-0.1.e with darkstone's HD, which works fine on my HD2. Its bit slow at start once everything is settle down, its pretty fast and no lag for me. But this might not be the case for you.
In the future, i will only provide the kernels that are popular. Right now, there are just too many combinations and takes really long time to upload them.
feature:
AB: Audio Boost
AXI: AXI frequency tweak
BFQ: BFQ IO scheduler (default CFS)
BFS: BFS cpu scheduler (default CFS)
HAVS: Hybrid Adaptive Voltage Scaling (Static Voltage Scaling - SVS is default)
OC: OverClock
UV: UnderVolt
OC, UV and AXI features are the standard feature for EVO based kernel.
EBAT: Extended battery (please provide feedback to hastarin http://forum.xda-developers.com/showthread.php?t=787588)
By default, the EVO based kernels are not overclocked. Please use setCPU or userinit.sh/user.conf script to enable overclock.
You can choice the combination you want.
EVO based kernel:
version 0.1.h (I will do another kernel update tomorrow as there is a new commit which fixes random ts freeze)
BFQ-OC-UV-AXI_850mv-0.1.h-evo.zip
BFQ-OC-UV-AXI_925mv-0.1.h-evo.zip
BFQ-OC-UV-AXI_1000mv-0.1.h-evo.zip
BFQ-OC-UV-AXI_1050mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-AB_850mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-AB_925mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-AB_1000mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-AB_1050mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT_850mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT_925mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT_1000mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT_1050mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT-AB_850mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT-AB_925mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT-AB_1000mv-0.1.h-evo.zip
BFQ-OC-UV-AXI-EBAT-AB_1050mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI_850mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI_925mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI_1000mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI_1050mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-AB_850mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-AB_925mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-AB_1000mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-AB_1050mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT_850mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT_925mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT_1000mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT_1050mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT-AB_850mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT-AB_925mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT-AB_1000mv-0.1.h-evo.zip
BFS-BFQ-OC-UV-AXI-EBAT-AB_1050mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI_850mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI_925mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI_1000mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI_1050mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-AB_850mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-AB_925mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-AB_1000mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-AB_1050mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT_850mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT_925mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT_1000mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT_1050mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT-AB_850mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT-AB_925mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT-AB_1000mv-0.1.h-evo.zip
BFS-HAVS-BFQ-OC-UV-AXI-EBAT-AB_1050mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX_850mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX_925mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX_1000mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX_1050mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-AB_850mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-AB_925mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-AB_1000mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-AB_1050mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT_850mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT_925mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT_1000mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT_1050mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT-AB_850mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT-AB_925mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT-AB_1000mv-0.1.h-evo.zip
HAVS-BFQ-OC-UV-AX-EBAT-AB_1050mv-0.1.h-evo.zip
Click to expand...
Click to collapse
if you are experiencing scrolling lag, try the kernel without BFS.
N1/htc-msm-2.6.32.9 based kernel (I tested the BFS-HAVS-BFQ-OC-UV-AXI_850mv-0.1.b kernel works fine so far.):
version 0.1.d
BFQ-OC-UV-AXI_850mv-0.1.d-n1.zip
BFQ-OC-UV-AXI_925mv-0.1.d-n1.zip
BFQ-OC-UV-AXI_1000mv-0.1.d-n1.zip
BFQ-OC-UV-AXI_1050mv-0.1.d-n1.zip
BFS-BFQ-OC-UV-AXI_850mv-0.1.d-n1.zip
BFS-BFQ-OC-UV-AXI_925mv-0.1.d-n1.zip
BFS-BFQ-OC-UV-AXI_1000mv-0.1.d-n1.zip
BFS-BFQ-OC-UV-AXI_1050mv-0.1.d-n1.zip
BFS-HAVS-BFQ-OC-UV-AXI_850mv-0.1.d-n1.zip
BFS-HAVS-BFQ-OC-UV-AXI_925mv-0.1.d-n1.zip
BFS-HAVS-BFQ-OC-UV-AXI_1000mv-0.1.d-n1.zip
BFS-HAVS-BFQ-OC-UV-AXI_1050mv-0.1.d-n1.zip
HAVS-BFQ-OC-UV-AXI_850mv-0.1.d-n1.zip
HAVS-BFQ-OC-UV-AXI_925mv-0.1.d-n1.zip
HAVS-BFQ-OC-UV-AXI_1000mv-0.1.d-n1.zip
HAVS-BFQ-OC-UV-AXI_1050mv-0.1.d-n1.zip
version 0.1.c
BFQ-OC-UV-AXI_925mv-n1-0.1.c.zip (2.21 MB)
version 0.1.b
BFQ-OC-UV-AXI_850mv-0.1.b.zip
BFQ-OC-UV-AXI_925mv-0.1.b.zip
BFQ-OC-UV-AXI_1000mv-0.1.b.zip
BFQ-OC-UV-AXI_1050mv-0.1.b.zip
BFS-BFQ-OC-UV-AXI_850mv-0.1.b.zip
BFS-BFQ-OC-UV-AXI_925mv-0.1.b.zip
BFS-BFQ-OC-UV-AXI_1000mv-0.1.b.zip
BFS-BFQ-OC-UV-AXI_1050mv-0.1.b.zip
BFS-HAVS-BFQ-OC-UV-AXI_850mv-0.1.b.zip
BFS-HAVS-BFQ-OC-UV-AXI_925mv-0.1.b.zip
BFS-HAVS-BFQ-OC-UV-AXI_1000mv-0.1.b.zip
BFS-HAVS-BFQ-OC-UV-AXI_1050mv-0.1.b.zip
HAVS-BFQ-OC-UV-AXI_1000mv-0.1.b.zip
HAVS-BFQ-OC-UV-AXI_1050mv-0.1.b.zip
HAVS-BFQ-OC-UV-AXI_850mv-0.1.b.zip
HAVS-BFQ-OC-UV-AXI_925mv-0.1.b.zip
Click to expand...
Click to collapse
EVO Log:
version 0.1.h
- based on git commit. Check gitorious for detail
* ts improvement (Markinus committed code to improve TS performance, This should reduce/eliminate the scrolling lag)
version 0.1.g
- based on git commit. Check gitorious for detail
- BFS 357
- minor change to BFQ
version 0.1.f
- based on git commit
- patch to 2.6.32.24
version 0.1.e
- based on git commit
* Working compass. A big thanks to Rajko!
- Extended battery support by Hastarin
- Thanks to michyprima's patch to fix issue with Airplane mode freezing the phone
- Memory leak fixed in firmware
- Mutex bug fix
- fix dma_sync_single_range*
- fix incorrect optimization for cpu govenors
- remove rwsem lock from CPUFREQ_GOV_STOP call (second call site) in CPUFREQ
- EXT4
* flush delaloc blocks when space is low
* fix async i/o write beyond 4GB to a sparse file
* correctly calculate number of blocks for fiemap
* prevent creation of files larger than RLIMIT_FSIZE using fallocate
* Ensure zeroout blocks have no dirty metadata
* fix possible lost inode write in journal mode
* fix memory leaks in error path handling of ext4_ext_zeroout()
* fix BUG_ON at fs/buffer in no journal mode
* fix potential quota dealock
- CIFS
* remove bogus frist)time check in NTLMv2 session setup code
* don't attemp busy-file rename unless it's in same directory
* fix malicious redirect problem in DNS lookup code
- CFS cpu scheduler
* fix over scheduling bug
* implement different treatment for idle shares
- fixes voltage table for both HAVS and SVS
Many of these patches are from kernel.git and all credit goes to the linux project
version 0.1.d
base on commit a8211687
- patch by gauner1986
* add video clean up and many twaking by gauner1986
* enable dot11n (gauner1986)
* add INT_AD6_EXT_VFR to fake irq (gaunner1986)
- add hastarin compass offset
make sure you add "nand_boot=0" parameter to kernel cmdline argument in startup.txt. eg.
{{{
set cmdline "rel_path=Android nand_boot=0"
}}}
version 0.1.c
add interactive cpufreq governor (as i forgot to apply the patch in previous versions).
version 0.1.b
disable framefuffer console to reduce wake up delay and high standby power consumption
version 0.1.a (EVO based commit
- BFS version 318
- BFQ I/O scheduler
- msm_kgsl mod
* enable shadow write to improve video performance
* Use writecombine flag to map vmalloced memory (video performance improvement)
- Overclock to 1.152GHz
- Provide four different undervolt versions 850mV, 925mV, 1000mV and 1050mV(default)
- Audio boost
- Interactive governor
- Some minor tweaking to on-demand and conservative governor
- Ext4 is enabled by default
Click to expand...
Click to collapse
N1 Log:
version 0.1.d
- minor BFQ update
- BFS 357
version 0.1.c (experimental)
- fix the TS freeze issue (i haven't encounter freeze yet)
- Working compass. A big thanks to Rajko! (haven't test it yet)
- add ElBartoME's BT port (not sure this is working or not)
- patch kernel to 2.6.32.24 (for BFS testing)
version 0.1.b
minor HAVS changes
version 0.1.a N1 based commit )
- BFS version 318
- BFQ I/O scheduler
- msm_kgsl mod
* enable shadow write to improve video performance
* Use writecombine flag to map vmalloced memory (video performance improvement)
- Overclock to 1.152GHz
- Provide four different undervolt versions 850mV, 925mV, 1000mV and 1050mV(default)
- Audio boost
- Interactive governor
- Some minor tweaking to on-demand and conservative governor
- Ext4 is enabled by default
Click to expand...
Click to collapse
The purpose of HAVS is to minimize the power consumption by
dynamic adjust the optimal voltage, and limit the maximum voltage.
The optimal voltage is actively determined for each frequency and
temperature. HAVS actively adjusts the CPU voltage as the CPU
frequency and temperature changes.
Click to expand...
Click to collapse
BFQ(Budget Fair Queueing) is a I/O Scheduler. BFQ is a proportional
share disk scheduling algorithm, based on CFQ, that supports
hierarchical scheduling using a cgroups interface.
BFQ generally performs better (for desktops) were perceived intractability
(vs real throughput) is preferred. CFQ may unwittingly penalise a well written
program with fast throughput, in favour of a slower program by virtue of its
reliance on allocated 'throughput' vs BFQ's 'time' reliance.
http://algo.ing.unimo.it/people/paolo/disk_sched/
http://groups.google.com/group/zen_kernel/browse_thread/thread/88871a70cecd707b#
Click to expand...
Click to collapse
What is BFS(Brain **** Scheduler):http://ck.kolivas.org/patches/bfs/sched-BFS.txt
FAQS about BFS:http://ck.kolivas.org/patches/bfs/bfs-faq.txt
WIKI http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Click to expand...
Click to collapse
Credits:
ridikolous, ReX83, eyanlaya (for testing)
HTC LEO kernel tree (base kernel, based on NEXUS one/HTC-MSM-2.6.32 kernel tree)
HTC LEO kernel tree (base kernel, based on HTC EVO kernel tree)
Con Kolivas (BFS)
Fabio Checconi (BFQ)
Ian (Overclock, undervolt and AXI)
pershoot (voltages and other fixes)
IntersectRaven (HAVS)
and many other developers.
Click to expand...
Click to collapse
I hope someone can take advantage of the source and make it better as i have limited time to test and improve them.
My gitorious for evo based kernel (something wrong with my old tree, so i recreate a new one)
if you like the work i do, you are always welcome to buy me a cup of coffee
thx good work
http://forum.xda-developers.com/showpost.php?p=8050200&postcount=8
Hi,
is the freeze fix from gauner1986 include (previos post)?
with friendly greet
starbase64
support for extended battery , PLZZZZZZZZZZZZZZZZZZZZ
how to use this ??? are these zimages ...--(but wats this tun.ko and bcm4329.ko?)
Hi,
copy and overwrite the ko files to /system/lib/modules.
with friendly greet
starbase64
Does this fix the battery consumption and wake-up from sleep problems which were encountered with the G-sensor fix kernel?
support for extended battery included?
mattc 1.7 ppp
Nice have to test it out.
Testing on DarkStone's Sense V2
does this include darkstones graphic improvement mod?
edit: just tried it and the accelerometer response is slow and so is the touchscreen. That said the performance is very good and it played ashalt 5 the smoothest i have seen any kernel do. Im using the 850 undervolt version with mattc 1.7 rmnet. Thanks for the kernel but i think ill wait until these issues are fixed
Thank you..
this kernel is very nice for Froyostone v2.
starbase64 said:
Hi,
copy and overwrite the ko files to /system/lib/modules.
with friendly greet
starbase64
Click to expand...
Click to collapse
thankuuuu brother
peace
Nice...look good for freeze problem
What is this for this guy not even answering that question
testing in bangter 1.2a
my quadran result 1920 (of max cpu speed )
chris-m said:
testing in bangter 1.2a
my quadran result 1920 (of max cpu speed )
Click to expand...
Click to collapse
can you use anyone of these?
no sorry, i'm using bangters relase for the quotidian usage
and i use kernel 1050mV(default);
i shall test the other builds if the battery wears out too fast..
These kernels are provided as-is without warranty. I'm not responsible for any problem you can encounter with your phone or if your cat suddenly dies.
Although, don't expect support even if I will eventually help since I love cats.
{
"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"
}
Note : These kernels are only compatible with CyanogenMod 9 based roms.
Use them on any other rom at your own risks.
Overview :
- 3.1.9 linux base
- LiveOC
- Custom Voltage
- Battery Life eXtender
- DIDLE v2
- Voodoo Sound 10
- PMFAST mode for best wifi performance
- USB host mode support
- Various tweaks for more speed and battery saving
CHANGELOGS IN #2 POST
By default, no overclock/undervolt is applied.
You'll need NSTools to use/enable all the features of this kernel. (Available for free on the Android market)
Downloads
Glitch kernel (CWM flashable only)
Glitch Kernel Updater app now available on the Android market to support us !Captivate:
- 23/01/2012 - V14 B6
Other supported devices : Captivate, Vibrant, Telus Fascinate, Verizon Fascinate
OLDER RELEASESLIVE OC GUIDEFAQ, Changelogshttp://forum.xda-developers.com/showpost.php?p=21703700&postcount=2http://forum.xda-developers.com/showpost.php?p=21703700&postcount=2
Do you want to discuss on this kernel, get the fresh news on development, or become a kernel tester ?
Join the IRC channel from your web browser herehttp://webchat.freenode.net/?channels=glitchkernel ! No registration needed
Make sure the channel is "#glitchkernel" and you're set.
For those who already have an IRC client,
here is the server : irc.freenode.net
port : 6667
Channel : #glitchkernel
-------------------------
Source :
- Glitch repo : https://github.com/organizations/Glitchkernel
Who is the Glitch team ?
- Kernel developement : ssewk2x & Tk-Glitch.
- Public relations / web hosting : Sixstringsg.
- App developement : Smasher816.
- Extreme overclocking testing : Shaolin95
- Beta testers team, with members coming and leaving
Credits :
Pawitp, jt1134, Morfic, Ezekeel, Zacharias.maladroit, Supercurio, lippol94, sztupy, Eugene373, Franciscofranco
Thanks to the donators and everyone bying the Glitch Kernel Updater app from the market, it's much appreciated and encourages us to continue our work !
Thanks to the beta testers team and to everyone helping me to debug and find new useful things to integrate !
Without all of you, this kernel wouldn't be !
Changelogs :
V14
24/03/2012 - BETA 6 :
- Upstream sync (modemctl, compass fix..)
- Fixed BLN, and added blink support
- Disabled Samsung sleep patches from Teamhacksung to prevent SODs
- Fascinate : Ported ssewk2x phantom keypress filter code from Glitch V13.1
- Vibrant : Merged GPS changes from FaultException
- Moved back to Deadline ioshed as default to fix nandroid
- Added Derteufel's selective LiveOC mod - It will prevent low frequency steps to OC, potentially providing enhanced stability and powersaving
- Fixed potential bug in vfat fs driver
- Fixed bug in ext4 fs driver
- Merged some audio changes from Teamhacksung
- Added touch support in Glitch recovery (incomplete)
- Some cleaning
22/02/2012 - BETA 5 :
- Voice audio through dock, thanks to xcaliburinhand (should fix related issues with Glitch volume boost hack)
- Renamed SmartassV2 governor to "GlitchassV2" to prevent latest NSTools version hanging
- Added FranciscoFranco Conservative governor tweaks for more speed
- Added a DIDLE enabler into screensate scaling script to kill BT in sleep and make DIDLE work with both TOP=ON and TOP=OFF. You'll need to enable screenstate scaling in Glitch menu from recovery in order to get DIDLE to use this (disabled by default). It's mostly for testing purposes - Feel free to report your experience with it.
- Moved back to previous sysinit to prevent the DIDLE enabler script to make the phone hanging on the bootlogo. Also fixes screenstate scaling making the phone unbootable, and some SOD/COD issues for guys using some other tweaking scripts
- Implemented BLN9 port from Derteufel with NSTools compatible sysfs. This way all the unsupported roms will get led notifications, and CMLed haters will hopefully stop to yell..
- The flash-time script has been updated to be able to clean more stuff
- A few fixes on the wifi driver to work better with our devices Please report your experience with DIDLE enabled. It may be required to disable DIDLE on some phones to prevent SOD/COD/softreboots or other instabilities. Also MAKE SURE YOU HAVE A DAMN GB BOOTLOADER !
- Reverted modemctl changes from Teamhacksung - should fix data issues some are having
21/02/2012 - BETA 4.1 :
- Reverted sleep GPIO stuff from THS stock samsung port. Should fix SODs some are encountering.
21/02/2012 - BETA 4 :
- Fixes on LiveOC and custom voltage from Ezekeel
- Fixes + various enhancements on I/O scheduling (up to 50% I/O speed improvement compared to beta 3)
- Fixed touchscreen freezing randomly
- Fixed various bugs here and there
- Back from Eugene's DIDLE to Ezekeel's DIDLE v2 mod (available through NSTools again) -> You may encounter SoD if enabled with wifi ON.
- Load balancing improvements
- Updated FIOPS I/O sched
- Sync with THS latest source
09/02/2012 - BETA 3 :
- LiveOC frequency steps changed again - Now all steps are using a 200MHz bus by default, so pushing liveOC % will give the same bus speed on all steps
- Default Int voltage for 1GHz set to Samsung's default to fix instability on bad overclocker devices
- Fixed recovery not displaying long lists items as well as cosmetic fixes - updated to latest source from Koush
- Fixed init.d support
- Switched to Tiny SHMEM, better on small devices
- Ext4 optimizations for more speed
- Readahead values tweaked a bit - should be better overall
- Fascinate : Use GB driver for i500 to fix prox/light sensors, and updated RIL init (Thanks to Sbrissen)
- Fsync() enabled again to prevent/limit data loss while experimenting with overclocking, and to (probably) fix the reboot->bootloop issue
- Disabled frame pointer, FIQ debugger, and some more debug stuff, Morfic-like
- Some writeback quickfixes
- Updated wifi drivers with added net fixes and optimizations
- GlitchOndemand polling tweaking for more stability
- Misc tweaks
29/01/2012 - BETA 2 :
- Updated to linux 3.1.10
- A few fixes on LiveOC (Thanks Ezekeel)
- GPU load affecting CPU frequency scaling (200 vs 100MHz) is back
- Removed CFQ and BFQ, and added SIO & the all new flash oriented FIOPS i/o schedulers - FIOPS is now default
- Better VM tweaks
- Fixed GlitchOndemand polling to fix stability issues some are encountering
- i/o-less dirty throttling backport from linux 3.2 (thanks to Franciscofranco)
- Added dynamic writeback & various writeback fixes
- Proportional rate reduction for TCP (thanks Google )
- Small fix on Lazy gov from Ezekeel
- Captivate : Port battery charging/fuel gauge code from stock --> Improves (but does not completely fix) phone turning off while
charging for some users (charging death). (Thanks to Pawitp)
- Vibrant : Headset buttons fix (Thanks to FaultException)
- Fixed and now built-in CIFS
- Changed OC steps (1152 step is now 1160, with 200MHz bus, 1440MHz step removed, added 1400 and 1500 MHz steps)
- Moved back to "old" DIDLE implementation for now
- Glitch call volume hack is back
- Various optimization and CPU load reduction in some typical cases
- Verizon Fascinate : fix for boot issue on preview 5 and BETA 1
- Updated USB host driver to build 5
23/01/2012 - BETA 1 :
- Dock audio support.
- Added gamma V1 hack and MDNIE bypass mode.
- Added more governors to play with & tweaked interactive and ondemand.
- DIDLE V2 added back for people who want to mod their framework (It may/will cause sleep of death on some devices, as always)
- Battery charging calculation fix (BLX will now show 100% as default).
- Changed overclocked steps for more stability and easier setup.
- Dm-cache support.
- Updated linux base to 3.1.9.
- Improved memory management and cache handling.
- General speed enhancements.
- Fsync disabled.
- Added an entry in the GLITCH menu (in recovery) to choose between mtp and mass storage USB mode.
- USB host mode (OTG) - updated to build 4, from sztupy - thanks to him and everyone involved in this !
- Bootmode injection fix from pawitp.
- Optimized RWSEM algorithm.
- VM and I/O performance enhancements.
- Added BFQ i/o scheduler.
- More cleaning, various optimizations and power management tweaks.
PREVIEW #5 : (For build 13+)
- Even better 720p video recording.
- Fixed Vibrant GPS.
- Added back various governors.
- New colors from Samsung stock.
- Toolchain sorcery with linaro 4.4.5, and using NEON and hardfloat optimizations.
- Bootmode injection support.
- Various speed enhancements.
PREVIEW #4 :
- Fixed softkeys on Captivate and Fascinate.
- Refresh rate back to 60Hz as the uncap breaks colors (it'll help to get better smoothness on heavy games too).
- Better 720p video recording.
- Tweaked governors and schedulers for testing.
- Big cleanup.
- Removed DIDLE for now - useless anyway, the rom prevents it to work correctly.
PREVIEW #3 :
- Added color adjustments to Nexus S framebuffer.
- Dock audio stuff back in.
- Cleanup.
PREVIEW #2 :
- Fixed GPS issues.
- Moved to Nexus S Framebuffer (stock colors, no more color adjustment available).
25/12/2011 - V14 Preview #1
- Compatible with Teamhacksung's ICS/CM9 builds 10 or higher.
- Now using linux 3.0.8 base from the Nexus S drop
- Upstream synced to the latest from THS (TVout, cleanup, 3.0 port..)
- Reverted to stock CM LED Notifications (fixing all the previous problems some users encountered with BLN) / No more BLN app needed, enabled by default.
- Removed Voodoo Color, and back to stock implementation.
- Added support for a new low power mode on wifi chipset, enhancing signal reception and stability, at the cost of a bit higher power consumption.
- Back to NEON mfpu for now
- Full support for init.d scripts
- Readahead value back to 1024 for better results (SDcard read Cache)
- Fixed headset buttons
- Fixed randomly freezing softkeys
- Big cleanup and rewrite of some stuff
- Removed the 200MHz lock when the GPU is active for battery life. Depending on your launcher and/or widgets, you'll get some slowdowns. Change min freq to 200 to fix it.
Major additions, ported from Ezekeel's work on the Nexus S (thanks Morfic !) :
You will need NSTools app, available for free on the market, or here : http://forum.xda-developers.com/showthread.php?t=1333696
- Added "LiveOC" system, giving access to GPU/bus overclocking on the fly, per 1% step.
- Added "Custom Voltage" control, giving access to ARM and Internal voltage undervoling and overvolting. (This makes the previous leakage system obsolete, which is now removed.)
- Added "Battery life eXtender" mod, allowing the user to limit the maximum charge percentage to preserve the battery life (not the battery runtime obviously)
- Added support for DIDLE V2, a very low power mode that will help battery life in many idle/semi-idle cases.
- Lazy governor sysfs, to enable or disable the frequency ramping up when screen is off (to end tasks quicker to sleep faster).
Keep in mind CM9 is at early stages of development and contains many bugs still.
Fantastic! I hope this fixes the sleep and charge deaths I have been getting on preview 5.
flashing now..... tried to flash by just wiping cache and davlik cache over preview 5 phone got stuck on at&t screen for about 10 mins... wouldnt go into cwm either..... so going back to stock and starting over again
Are you getting them with no UV because I have not seen any reports about it from any of the testers. At least none that I have seen have reported that.
hehe 1st page! awesome release
yea no uv.... i was using live OC but i cleared ns tools settings then wiped caches and installed.... got stuck on the att screen... but now im up and running went to stock jf6 flashed ics buld 14 and then glitch.... loving the splash screen..... first impressions are awesome!!
Thank you guys!
Shuts down when screen goes off, probably sleep death. At 100% live o/c. Also seems slower than Preview 5.
Been tinkering around and so far all is well, running it at 1440MHz with the usual UV.
so far so good here! much snappier!
Sent from my SGH-I897 using xda premium
Lag city with no UV at 110% Live OC 1267MHz. Don't know what's wrong but its slower than Preview 5. I've tried back to stock. Just have to try something else and see what happens.....
Update:
Went back to stock KI2 with bootloaders and flashed Build 14 and Icy Glitch and its literally flying now. Thanks for the awesome work
Hot dang! Man I would be clapping with joy if I still had my cappy...! Awesome sixstringsg!
Sent from my Galaxy Nexus
Just in time! Thanks for making my cappy snappier
phone is doing awesome OCd to 1512... no lags very snappy.... no issues so far
daskanda said:
phone is doing awesome OCd to 1512... no lags very snappy.... no issues so far
Click to expand...
Click to collapse
Nice. That is my current OC as well. Are you tweaking voltages or still stock voltages?
Is there any reason that ever since I flashed this kernel I can't send text messages. I can receive just not send, also I can no longer run any speed test. I have tried 4 different modems.
Sent from my SGH-I897 using xda premium
shaolin95 said:
Nice. That is my current OC as well. Are you tweaking voltages or still stock voltages?
Click to expand...
Click to collapse
yea i tweaked my voltages too:
arm voltages
1304 - 1425 mv
1152 - 1400 mv
1000 - 1375 mv
800 - 1250 mv
400 - 1125 mv
200 - 950 mv
100 - 925 mv
int voltages
1304 - 1250 mv
1152 - 1225 mv
1000 - 1200 mv
800 - 1175 mv
400 - 1150 mv
200 - 1125 mv
100 - 1025 mv
any ideas on how to tweak these more?
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Wdustin1 said:
Is there any reason that ever since I flashed this kernel I can't send text messages. I can receive just not send, also I can no longer run any speed test. I have tried 4 different modems.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
are you apn settings okay?.... i have no problems with this kernel and THS ICS runing very smooth and really fast.... no problems with texting
---------- Post added at 11:24 PM ---------- Previous post was at 11:06 PM ----------
just wondering whats the difference between glitchondemand governor and the regular ondemandx?..... i usually use smartassv2.... which one do u recommend glitchondemand or smartassv2...... and why (just so i can feel smart)
oc'd to 105 as well with this kernel and yeah it's great
daskanda said:
yea i tweaked my voltages too:
arm voltages
1304 - 1425 mv
1152 - 1400 mv
1000 - 1375 mv
800 - 1250 mv
400 - 1125 mv
200 - 950 mv
100 - 925 mv
int voltages
1304 - 1250 mv
1152 - 1225 mv
1000 - 1200 mv
800 - 1175 mv
400 - 1150 mv
200 - 1125 mv
100 - 1025 mv
any ideas on how to tweak these more?
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
are you apn settings okay?.... i have no problems with this kernel and THS ICS runing very smooth and really fast.... no problems with texting
---------- Post added at 11:24 PM ---------- Previous post was at 11:06 PM ----------
just wondering whats the difference between glitchondemand governor and the regular ondemandx?..... i usually use smartassv2.... which one do u recommend glitchondemand or smartassv2...... and why (just so i can feel smart)
Click to expand...
Click to collapse
gonna try out your settings tomorro ;-) on another note i see we have deep idle now....just read the article and wow! excited to test this tomorro!
Sent from my SGH-I897 using xda premium
ptesmoke said:
gonna try out your settings tomorro ;-) on another note i see we have deep idle now....just read the article and wow! excited to test this tomorro!
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
let me know how the settings work out.... btw im on the 1304 step live ocd by 116% so max freq is 1512
Hey xda´s,
here i´ll post some kernels for SGSIII. If anyone knows another plz give me a link and i´ll add it with link to devs original thread.
-----------------------------------------
CF-Root 6.2 - SuperSU+CWM5.5+CWMManager
stock as possible
-----------------------------------------
★TITANIUM KERNEL★ OC/UV • CIFS • TUN • SIO • And lots more!
Features - What my Kernel is made up of-
Root, Busybox
Bootanimation Support (/system/media/bootanimation.zip)
CIFS/TUN Support
XZ Compression and Decompression Used
PegasusQ and Adaptive Governer along with other stock Governers
Readahead size set according to disk size
Many lowmemorykiller Tweaks
CFS Autogroup
SLUB Memory Allocator with slight improvements
Some mm Parameters Tweaked
Used memcopy macros and functions
Used Makefile Optimizations!
Disabled GENTLE_FAIR_SLEEPERS
Overclock upto 1.8Ghz (Thnx to AndreiLux)
Undervolt, and UV_mV_table support (Thnx to AndreiLux)
Added Simple IO Scheduler
Triangle Away Compatible Kernel.
CFS Parameters tuned for best performance
Refer to my github and changelogs for more details!
Known issues-
WIFI
Mounting of external SD-CARD
-----------------------------------------
Perseus [OC/UV][WIP]
Features:
Perseus alpha11 (10/06):
ro.secure=0
Recovery renamed as busybox in /sbin. I'll compile a proper busybox later on, or remove it alltogether when a recovery with autoinstall is released by CF or somebody else.
Perseus alpha10 (8/06):
Overclocking up to 1800MHz. Voltages in ASV table are somewhat scaled up until 1600MHz, after that you're on your own and have to optimize yourself.
Intel claims maximum sustainable safe voltage for 32nm HKMG to be 1.4V, above that may cause electron migration to the silicon and permanently deteriorate your chip. 1700 and above only for avid overclockers and benchmark freaks. Credit to tvanhak for playing lab rat with his phone.
Samsung frequency limitation removed to scale above 1400MHz, full credit goes to Gokhanmoral for finding this hack in the kernel as it is in a very sneaky location.
Perseus alpha7 (5/06):
Reduced regulator voltage initialization minimum to 600mV, you can now undervolt that far. Be aware of crashes.
Added SIO scheduler
Some network and CRC related patches
Perseus alpha6 (4/06):
UV_mV_table support, apps like SetCPU work now.
If you have a voltage set at for example 1187500µV the output will be rounded up to be displayed at 1188mV. If you set a voltage non multiple of 12.5mV then for example, 1190mV, it will round it to the nearest valid step, being 1187.5mV. UV_uV_table is there for finer grained control but no app suports that yet.
Perseus alpha3 (4/06):
Mali: disable state tracking
Mali: GPU frequency, scaling and voltage control
Governor pegasusq: make up_threshold_at_min_freq and freq_for_responsiveness configurable values. This is the reason the Galaxy S3 is so smooth, it has super aggressive scaling values for the governor until default 500MHz.
Enabled 1500MHz per defconfig and added voltage values to ASV table for it
Added UV_uV_table for voltage control on the CPU; this is not compatible for any programm which supports undervolting right now, we need UV_mV_table for that and since we have 12.5mV steps being fed to Vdd it's not compatible for now.
Boot partitions are made visible.
-----------------------------------------
SiyahKernel S3-v1.0
Features:
CPU over/underclock: 100-1800MHz 18-steps
CPU underclock (600mV-1500mV). vdd_levels and UV_mV interfaces.
GPU undervolting/overclocking (40MHz-800MHz)
Insecure adb even though we have ro.secure=1
optional smooth_scaling for those who wants to limit fast scaling of governors (such as ondemand)
triangle-away app support
added hotplug governor and modified it to support quad-core
Auto-root. You can also remove root via ExTweaks app and install it without rebooting your phone again. Auto-root can be disabled as well.
You can completely disable android logger using ExTweaks app
Adjustable charging speeds for AC and USB
Cpu governor optimizations
Gpu voltage, clock and stepcount interfaces in ExTweaks
governor-aware stand-hotplug for old conventional governors
Available CPU Governors: Pegasusq (default), Hotplug, Ondemand, Lulzactive, Conservative, Performance, Userspace, Powersave
CIFS as module
Available I/O schedulers: CFQ (default), noop, Deadline, SIO, V(R)
init.d support
ARM topology support (SCHED_MC)
default idle mode is IDLE+LPA (highly recommended). however you can change the default to AFTR+LPA using ExTweaks.
Automatic EFS Backup
Samsung proprietary ExFat modules are loaded
Lots of I/O tweaks and filesystem optimizations via some parts of thunderbolt scripts.
NTFS automounting for USB sticks. When you plug in an NTFS formatted USB flash it will be automatically mounted to /mnt/ntfs folder.
Almost everything is configurable such as scheduler features, hotplug thresholds, GPU frequencies, voltages, arm topology modes... and they are configurable via simple and free ExTweaks App from Google Play
mDNIe negative effect toggle with home button (press it four times). the purpose of this feature is to inverse the colors especially when the background is white or bright. making the background darker will make your battery last longer.
and some more not worth mentioning as separate items such as disabling mali state tracking and disabling some unnecessary debugging etc...
-----------------------------------------
Abyss S3 kernel 1.0 Final Stable Version by Angelom
Full Changelog Abyss S3 kernel 1.0 Final:
- Based on Update 1 Samsung Sources, with update up to 3.0.33 patches
- CPU overclocking & undervolting (50MHz-1704MHz 18-steps, UV_mV, UV_UV and vdd_levels interfaces)
- Added and enabled smooth scaling for battery life
- Added and enabled frequency regulation based on screen on/off events
- Added selectable ASV Table (form 0 to 11), set to 4 as default
- Added adjustable vibrator levels
- Added BFQ, v(r) and sio I/O schedulers
- Set v(r) i/o scheduler on boot
- Selectable idle mode (AFTR as default)
- Selectable Sched_MC power-saving (off as default)
- triangleaway support
- GPU undervolting & overclocking (600mV-1200mV, 40MHz-800MHz)
- Added Abyssplug, lulzactive v2, lazy, interactive, smartass v2, intellidemand, lagfree governor
- autorooting
- Auto backup EFS
- Added and Enabled CGROUP_TIMER_SLACK
- sched-features: enabled HRTICK, disabled GENTLE FAIR SLEEPERS
- Added and enabled Joe's RCU
- Added SLQB Allocator
- mali: disabled STATE_TRACKING
- Added and enabled sync & sw_sync frameworks
- slicing-by-8 algorithm for crc32 and crc32c
- Introduce some memory copy macros and functions.
- Added ext4 tweaks
- Added Support for Multi-Core interface (Thanks Simone201)
- Added NTFS module and CIFS module
- init.d support
- Added Abyss Logo
- Added New S90uvabyss and S90ASVabyss script
- Other functions of Abyss kernel for GS2
-----------------------------------------
franco.Kernel r1
Features: will be edited
-----------------------------------------
Hacre's Kernel
Features:
Inc...
-----------------------------------------
plz post some experience for them.
greets
F1tty
Isn't this why we have the dev section?
Sent from my GT-I9300 using XDA
yes but not all are listed here ...you should know.
we already have a thread for this:
http://forum.xda-developers.com/showthread.php?t=1674286
Darkside Agent said:
we already have a thread for this:
http://forum.xda-developers.com/showthread.php?t=1674286
Click to expand...
Click to collapse
i never look into generall if i search for custom stuff...btw there are only xda´s threads i can easily find my self here...and in my thread can be talket about kernel and own experience...whats wrong on it ? i didnt like such big threads with all stuff in it and i believe most of users too.
best regards
Moved to general, please read this thread for more information about what belongs in each section.
Siyah is my Favorite atm!
Fast, stabile & smooth
Gesendet von meinem GT-I9300
Added Franco kernel :thumbup:
Runs like a hunted bunny^^
Gesendet von meinem GT-I9300
exfat support is in v0.94b (the OP is a little outdated for siyahkernel).
since I have no thread, I will answer the questions that I receive via PMs here for this time: I need some more testing and also some more things to implement/fix before releasing v1.0. I have very limited time to work on the kernel in this week. so, don't expect v1.0 anytime soon.
.
gokhanmoral said:
exfat support is in v0.94b (the OP is a little outdated for siyahkernel).
since I have no thread, I will answer the questions that I receive via PMs here for this time: I need some more testing and also some more things to implement/fix before releasing v1.0. I have very limited time to work on the kernel in this week. so, don't expect v1.0 anytime soon.
Click to expand...
Click to collapse
thanks for 0.94....device is stable and seems to have lower temperature in standby...little cooling my hands
Init.d folder
gokhanmoral said:
exfat support is in v0.94b (the OP is a little outdated for siyahkernel).
since I have no thread, I will answer the questions that I receive via PMs here for this time: I need some more testing and also some more things to implement/fix before releasing v1.0. I have very limited time to work on the kernel in this week. so, don't expect v1.0 anytime soon.
Click to expand...
Click to collapse
Hi there,
Thanks for your work and finally I installed it due it supports EXfat format SD Card. I have a nood question, does your kernel normally has init.d folder?
Thanks.
Edit: My Quadrant score decreases from 5611 down to 3507 after using Siyah kernel 0.94b using 1400mhz ondemond.
will try that new siyah
Boeffla Kernel App Profile Sharing Thread
In this Thread you can share your Profiles based on the Awesome Boeffla KernelOfficial Boeffla Kernel Thread by Lord Boeffla -> here#Downloads:
- [Official] CM11s/CM11/CM12 Builds by Lord Boeffla -> here
- Linaro(l474)/Sabermod(sm484) Builds by ZaneZam -> here
more information about the Linaro/Sabermod builds here
- Boeffla Config App -> here
#How to Activate the Profile:
- download .bcprofile
- put it into /data/media/0/boeffla-kernel-data
- activate profile through Boeffla Config V2
- open Boeffla Config V2, tap on DEFAULT, then LOAD FOREIGN, choose downloaded profile, activate it in the list (it should be blue)
You can post your Profile with some information about it and I will add it in post #2
Now we can start sharing profiles and discuss about it!
Have a lot of Fun
If you like to read more about Battery saving tips/performance tips/Governors/IO Scheduler -> here
Boeffla Kernel FAQ -> here
Profiles
ZZMove Basic Profiles in one Package: Package Info & Download
==========================================
@P1nGu1n_ Profile
- P1nGu1n_ Profile
==========================================
@PhrAok
- PhrAok Normal and Gaming Profile
==========================================
@S1ay3r666 Profile
- Slayer_Normal_OPO Profile
==========================================
@raybit10 Pofile
- raybit10 Battery Profile
==========================================
@real_pac Profile
- real_pac
==========================================
@BlakeSm Profile
- BlakeSM
==========================================
@ZaneZam Profile
- Information about the Profile -> here
- ZaneZam Profile
==========================================
@rlsroufe Profile
- rlsroufe Battery Profile
==========================================
@Clark789 Profile
- Clark789´s Profile
==========================================
KCAL COLOR PROFILE Amoled Style:
Colors: 255,255,255
Saturation: 285
Hue: 0
Display: 255
Contrast: 264
Gamma: 0
reserved #2
Slayer_Normal_OPO for CM12
The first profile I like to share allows smooth scrolling and normal Gaming without lags for CM12,
while being Battery friendly:
- SmartMax
- Stock Cpu Speed
- I/O: Deadline 512
- CPU Tweaks: Aggressive
Download: Slayer_Normal_OPO
Good idea. Hopefully people will explain their choices too so we can understand and learn not just copy.
What I use is a balance between performance and battery life. If you have such a powerful device you don't want it to lag just so you have an extra 30 mins screen of time...
My settings give you a stable and fluid experience while saving you some juice. On average I have 5-6 hours screen-on time and 2 days in stand-by with wifi always on and using 4g.
What I use most of the time running CM11s:
Governor: zzmoove - optimal
Scheduler: zen
Hutplug profile: optimized
Touch boost frequncy: 1190 MHz
AC charge current: 1800 mA
The rest is stock.
Have not experimented with GPU yet, curious about everyone elses findings
Download link: P1nGu1n.bcprofile
P1nGu1n_ said:
What I use most of the time:
Governor: zzmoove - optimal
Scheduler: zen
Hutplug profile: optimized
Touch boost frequncy: 1190 MHz
AC charge current: 1800 mA
The rest is stock.
Have not experimented with GPU yet, curious about everyone elses findings
Click to expand...
Click to collapse
Do you like to upload your profile to a hoster?
Then i will add it to second post ?
My Config:-
Governor - zzmoove - optimal
I/O Scheduler - zen
Readahead - 1536
CPU Min - 268MHz
CPU Max - 2457 MHz
GPU -27MHz
Hotplug - zzmoove
Multicore Powersaving - ON
Boeffla Sound - ON
Head phones - +2
Speakers - -2
A/C Current - ON /w 1500mAh
Swappiness - 10%
Touch Boost -1267Mhz
LED Tweaks - ON (6 & 85 respectively)
ViditM14 said:
My Config:-
Governor - zzsmoove - optimal
I/O Scheduler - zen
Readahead - 1536
CPU Min - 268MHz
CPU Max - 2457 MHz
GPU -27MHz
Hotplug - zzsmoove
Multicore Powersaving - ON
Boeffla Sound - ON
Head phones - +2
Speakers - -2
A/C Current - ON /w 1500mAh
Swappiness - 10%
Touch Boost -1267Mhz
LED Tweaks - ON (85 & 6 respectively)
Click to expand...
Click to collapse
Same for you export you profile in a file and upload it. Then i will add it to the second post.
And you can post some Screenshots with your sot.
Cheers Slayer
S1ay3r666 said:
Do you like to upload your profile to a hoster?
Then i will add it to second post
Click to expand...
Click to collapse
Done, I edited my post. Could you link to my post instead of directly to the download link of my profile? It has an explanation and this way I could update my profile without the OP needed to be updated.
S1ay3r666 said:
Same for you export you profile in a file and upload it. Then i will add it to the second post.
And you can post some Screenshots with your sot.
Cheers Slayer
Click to expand...
Click to collapse
I am against screenshots. People will probably post the best result they ever got and brag about it, which is not that interesting. Battery life depends on many factors, like wifi and 2g/3g/4g/no data and your reception of both, if you've gamed and your number of apps. I'd rather have everyone posting their average screen-on and stand-by time with a context. For example: on average 5-6 hours screen on time, 2 days of stand-by time with wifi always on and using 4g.
The first profile is the one I use most of the time. Stable and battery saver, is my good compromise between fast response, with undervolting and underclocking. The second I use for gaming, it automatically activates with Tasker. I can not share my file to avoid the obvious problems related to undervolting because we have different grades of cpu.
First "normal" :
Governor: zzmoove
Governor profile: zzmoove - Optimal
Scheduler: fiops
Readahead buffer: 2048
CPU freq max: 1497mhz
CPU freq min: 268 mhz
Hotplug profile: zzmoove native 2 cores min (kernel v2.2 beta 1)
Multicore powersave: Off
UV profile: -100mv THIS THREAD
GPU governor: powersave
Touch boost frequency: off
Miscellaneous
System tweaks: Boeffla tweaks
Second "gaming" :
same as "normal" but with
CPU freq max: 1958 mhz
Governor profile: zzmoove - game
Miscellaneous
Touch boost frequency: 1497 mhz
System tweaks: Speedmod tweaks
General configuration:
Screen on time 9 hours (best)
2 days complete (light use) - Wifi and 4G are activate when screen is activate with task to periodically sync
All android animations are off
ROM: CM11 CARBON ROM with Boeffla kernel 2.2-beta1
P1nGu1n_ said:
I am against screenshots. People will probably post the best result they ever got and brag about it, which is not that interesting. Battery life depends on many factors, like wifi and 2g/3g/4g/no data and your reception of both, if you've gamed and your number of apps. I'd rather have everyone posting their average screen-on and stand-by time with a context. For example: on average 5-6 hours screen on time, 2 days of stand-by time with wifi always on and using 4g.
Click to expand...
Click to collapse
I tend to agree. We want useful posts, not bragging.
How many times do you see screenshots with massive SOT and no apps usage.
P1nGu1n_ said:
Done, I edited my post. Could you link to my post instead of directly to the download link of my profile? It has an explanation and this way I could update my profile without the OP needed to be updated.
I am against screenshots. People will probably post the best result they ever got and brag about it, which is not that interesting. Battery life depends on many factors, like wifi and 2g/3g/4g/no data and your reception of both, if you've gamed and your number of apps. I'd rather have everyone posting their average screen-on and stand-by time with a context. For example: on average 5-6 hours screen on time, 2 days of stand-by time with wifi always on and using 4g.
Click to expand...
Click to collapse
Just Perfect thats the way we go!
Will always link the post with the Description and pls include a Download link!
Cheers Slayer
PhrAok said:
The first profile is the one I use most of the time. Stable and battery saver, is my good compromise between fast response, with undervolting and underclocking. The second I use for gaming, it automatically activates with Tasker. I can not share my file to avoid the obvious problems related to undervolting because we have different grades of cpu.
First "normal" :
Governor: zzmoove
Governor profile: zzmoove - optimal
Scheduler: bfq
Readhead buffer: 2048
CPU freq max: 1497 mhz
CPU freq min: 268 mhz
Hotplug profile: zzmoove native hotplug
Multicore powersave: Off
UV profile: None with -115 mV for all entries !!! not to do if you don't know what you are doing !!
GPU governor: simple_ondemand
Miscellaneous
System tweaks: Boeffla tweaks
Second "gaming" :
same as normal but with
CPU freq max: 2457 mhz
Governor profile: zzmoove - game
UV profile: -100 mV for all entries !!! not to do if you don't know what you are doing !!
Miscellaneous
System tweaks: Speedmod tweaks
General configuration:
Screen on time 7 hours (best)
2 days complete - Wifi and 4G are activate when screen is activate with task to periodically sync
Click to expand...
Click to collapse
I will add it to second post, but can you say me for which type of rom (CM11s/Cm11/Cm12)?
So we will get a bit of structure.
Thanks
S1ay3r666 said:
I will add it to second post, but can you say me for which type of rom (CM11s/Cm11/Cm12)?
So we will get a bit of structure.
Thanks
Click to expand...
Click to collapse
sorry you are right, post edited.
PhrAok said:
sorry you are right, post edited.
Click to expand...
Click to collapse
Perfect! post #2 updated!
Zzmoove - yank
Zen
Max 1958
Readahead 1024
Light undervolt
Hot plug default
Gpu max 389
Touchboost off
Current stats
On battery : 1 day 14 hours - 40% left.
Screen on : 4hours 45minutes.
LTE only.
Trying this for everyday light use and haven't come across any hangups so far. Just flashed this kernel a couple days ago so this is my first run.
Hi guys, I just tried PhrAok's config, but I may did anything wrong because my phone freezed and rebooted after quitting boeffla app, and at each reboot.
I tried to wipe dalvik cache, flash my rom again and delete boeffla app, but still freezing after reflashing boeffla...
Anyone have an idea ?
Thanks in advance.
Tweetix said:
Hi guys, I just tried PhrAok's config, but I may did anything wrong because my phone freezed and rebooted after quitting boeffla app, and at each reboot.
I tried to wipe dalvik cache, flash my rom again and delete boeffla app, but still freezing after reflashing boeffla...
Anyone have an idea ?
Thanks in advance.
Click to expand...
Click to collapse
Instead embarrassing, for next time with kernel 2.0 beta 18 you can reset all settings due to a configuration problem with boeffla-config-reset.zip in boeffla-kernel-data folder, flash in recovery.
if you don't already done, maybe you should delete the boeffla-kernel-data folder that contains the profile that you had previously registered before reflashing boeffla kernel.
Thanks, it worked like a charm !
I did not knew that a reset file was on the phone, I looked on the web for a similar file that I had on my S3 (called ultimate kernel cleaning script), but I didn't find anything...
Thanks again !
Custom kernel for Samsung Galaxy S Advance
Code:
/*
* Your (probably expired) 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.
*/
Hi there!
Because of numerous issues found in 3.4.113 kernel, I'm temporarily moving to development on 3.0.101 base.
What is difference between chrono kernel (CK) and CK refresh build? CK was mostly tested on MM-based ROMs, but appeared not to work stably on Android 4.4.x. Aim of this build is to properly enable support for older ROMs (like kitkat), and when done, merge these changes to 3.4.113 kernel.
This build is based upon chrono kernel r4.1 build, so to avoid versions confusion, I'm creating a separate topic.
Features:
CPU, GPU and DDR OC support
more governors and I/O schedulers
Lite kernel - some kernel features moved as modules
F2FS support
ABB-charger tweaks
many others features and tweaks...
Credits:
@dh.harald and @hafidzduddin for contribution on U8500 platform sources
@ Team Canjica for a base for this kernel
@ Nova Fusion for F2FS implementation
@zwliew for contribution on TC kernel
@cocafe for LiveOPP, GPU OC, abbamp and abb-charger tweaks and many cool patches which I've used from his kernel
@faux123 for dynamic Fsync implementation
@Christopher83 for dynamic management of dirty page writebacks implementation
@KINGbabasula for contribution on TC kernel sources
@boype for SIOPlus tweaks and OndemandPlus governor
@Adi_Pat for abbamp, kernel tweaks
@PolishVodka for initramfs scripts for 4.2.x and 5.0.x
@Rox for help in fixing initramfs scripts for 4.1.2
@ace2nutzer for optimization CPU OC and for whatever scripts which I have used in my kernel
@Meticulus for BLN, Sweep2wake and Doubletap2wake
@mkaluza for huge LiveOPP/Mali improvements and Dynamic governor
@yanpol199 for help with F2FS support in TWRP
@ all users who tests this kernel and directs the development along the right path
@ all those users, who I forgot to mention (PM me if so)
Team Win for TWRP recovery
Samsung for opening kernel source
Linus Torvalds for Linux sources
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source Code:
LK 3.0.y based releases
Installation:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Notice: this kernel is not compatible with NovathorSettings app, be sure to remove it before installing a kernel!
Download:
FTP
XDA:DevDB Information
Chrono Kernel Refresh, Kernel for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, cocafe, faux123, zwliew, mkaluza, Meticulus, KINGbabasula, ace2nutzer, TeamCanjica
Source Code: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/refresh-3.0.101
Kernel Special Features:
Version Information
Status: Testing
Stable Release Date: 1974-11-11
Beta Release Date: 1974-11-11
Created 2018-03-22
Last Updated 2018-03-23
Changelogs
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs)
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.
R4.6
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
R4.1
Initial build for janice (kernel sources based on Chrono Kernel r4.1)
LiveOPP: updated to r5.7.1 kernel version
Exfat: test fixes for Stock 4.1.2 ROM (not tested)
Enabled CONFIG_STE_TRACE_MODEM (test fix for Stock ROM incoming / outgoing calls)
Kexec: added janice support
Misc
Storages switch
By default, this kernel comes with internal and external storages switched. You can revert this behavior, by changing the line
Code:
use_swap=1
to
Code:
use_swap=0
in file /ramdisk/fstab_specs.txt and flashing the kernel package. This setting will remain until you format /ramdisk partition.
Thank you Chrono again.
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
The nice thing is I find multitasking working far better, phone seems to be more responsive in situations where more apps are running at the same time, this is very good to me!.
Another big point is installation went fine and recovery is working perfectly, so problems with possible bootloops are solved (and after some more usage I will go further to your more updated roms )
If there is something more to provide you, test or informations missing, please ask me Chrono
I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
-If I set 1000 Mhz as maximum clock of the dynamic governor, the phone becomes slower and a bit hot on the back.
Multitasking is severely affected by that clock. Multitasking is more stable at 800 Mhz, despite it's still slow.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
In my attachment there is a meminfo that I took while the phone was under load.
If it isn't enough, I attached a full logcat. There are some errors and crashes.
@Pdevo, @isaak, thanks for testing!
I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
Click to expand...
Click to collapse
Probably I've rushed things, or sort of. I had a hard time trying to find a considerably stable kernel 3.0.101 base (this one appeared to work stably, though not best, in terms of the performance). Nevertheless, the multitasking should already be better (at least better than in r5.7.1, as in this one LowMemoryKiller appeared not to work at all). I'm updating the sources to a new kernel base, r4.6 which should be even better in multitasking term.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
Click to expand...
Click to collapse
Should be fixed in upcoming release.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
Click to expand...
Click to collapse
It's a bug in CM11 ramdisk, I've took another one from Codina, and now this issue should be resolved as well.
Pdevo said:
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
Click to expand...
Click to collapse
I'm afraid that exfat driver built in the kernel is not compatible with this userspace mount.exfat-fuse utility. I won't be able to fix it, until I find a time to return to stock & rebuild either mount.exfat-fuse or kernel driver in order to make them compatible each with other.
As for the deepsleep issue, I can say that at least 4.4.4 is not affected by this bug. Try making sure that no apps are preventing deep sleep (Better battery stats or Wakelock detector can help in that).
New build r4.6 is up!
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
ChronoMonochrome said:
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
Click to expand...
Click to collapse
Tested on Lineage Os 11 without CCleaner.
After flashing this new kernel I had to force a Media scan with Fx File Explorer (that detected over 300 changed files) because the phone was really slow. That was sufficient to speed up the multitasking that now it's much better than previous 4.1 build.
Additional observations:
- Do you think it's possible to improve Media scanner reactivity via kernel?
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!
isaak said:
- Do you think it's possible to improve Media scanner reactivity via kernel?
Click to expand...
Click to collapse
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
Click to expand...
Click to collapse
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
Click to expand...
Click to collapse
Ok, I'll consider of tuning CPU governor in order to provide more battery friendly setup. I was afraid that the battery usage might be too high, but that was a necessary evil, I guess. In the meantime, as a temporary workaround, the maximum CPU frequency can even be lowered to 800 MHz, it should be still fast enough.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!
Click to expand...
Click to collapse
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
ChronoMonochrome said:
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
Click to expand...
Click to collapse
Nevermind.
ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
Click to expand...
Click to collapse
I'd like to revert the behavior, so I would appreciate If you could provide the same instructions here and in the other kernel thread..
ChronoMonochrome said:
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
I would suggest deadline, noop, sioplus, zen (plus the existent FIOPS).
ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
Personally I really appreciate and find useful the external sdcard storage as primary one, should be the default behaviour for me, it makes sense and also I never liked to have some files on one unit and some files on another one (download, pictures, recordings on extsdcard, apps folders, screens, other apps downloads etc on internal), I really like the idea of sdcard as main, like the old times of galaxy mini
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
I will test this build and especially the deepsleep issues, to see if there are apps causing phone not to sleep, the problem is I didn't add any app, just using the same enviroment that with cocore was going to deepsleep. I will report soon, anyway, good job chrono, keep it up
Pdevo said:
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
Click to expand...
Click to collapse
Yes, FIOPS is good. I just think that having 2 or 3 additional schedulers to select would be better for different uses.
In my previous post I replaced sioplus with zen, according to the conclusions of this guide. There is an useful (up to date) list of recommended IO schedulers, ordered for everyday usage, battery life, heavy multitasking, etc.
New build r4.6.1 is up!
Hey guys and sorry for having to wait that long for a new releases!
I'm still working on 3.4.x kernel - no great news here, but at least I've found a more less stable sources base, so the only what needed now, is a time to bring up some stability fixes and feature changes.
For now releasing a 3.0.101 kernel with some minor changes:
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.
ChronoMonochrome said:
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage
Click to expand...
Click to collapse
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.
For me the minimum freq was correctly 400 mhz as expected, as always running on stock 4.1.2.
After two days of use I can say you are following the right path.
This time I wanted to remove every possible source of doubts and I went for a clean installation, so doing a complete reset and flashing your kernel, of course after the temporary one. I still have the phone not going to deepsleep and the call issues (basically it is impossible to do and receive phone calls on stock rom).
A part from these I can say I didn't noticed any other issue at all, finding memory management a little improved compared to previous release and battery life still good, considering the phone isn't going to sleep mode.
I think this will continue to improve and soon all these glitches will just be gone away, thank you so much chrono also hoping to settle for a bit on your ultimateROM, only waiting for the vibration working, because that is basically the only notification for me
isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.
Click to expand...
Click to collapse
1) Isn't an issue here, the showed CPU frequency is 200 MHz, but the actual CPU pll clock set at 400 MHz. Might be confusing, but yet that is better for a battery life.
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?
ChronoMonochrome said:
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
Click to expand...
Click to collapse
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
Click to expand...
Click to collapse
Honestly I don't know how to disable perf profiles. If it's a simple thing to do (like a command or two to execute), please tell me how to do it because it's enough for me, otherwise I'd like to try the third way and see.
ChronoMonochrome said:
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
Click to expand...
Click to collapse
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
Click to expand...
Click to collapse
Yes, "Set on boot" options are correctly set for both Processor and I/O Scheduler.
And I keep "Enable per-app profiles" option turned off.
@ChronoMonochrome
UPDATE 1: It occurs only randomly and with particular combinations. The best way to reproduce is to set these, one at a time:
1) Zenx as governor, min. 200 max 800, Noops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Fiops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Sioplus scheduler. Reboot.
After the first, the second or the third reboot, some of these values you've set will change spontaneously on their own.
UPDATE 2: I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, it's ok now, but I've noticed that this value is not kept after a reboot.
Do you need a specific log?
In case please write me any command and I'll give you the output.
isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs: .....
Click to expand...
Click to collapse
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
ChronoMonochrome said:
....
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?
Click to expand...
Click to collapse
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:
ace2nutzer said:
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:
Click to expand...
Click to collapse
Sorry for so late response, I had to take a break in a development because suddenly got sick with a flu (I'm fine now, btw) :silly:
I think I've found a temporary solution to this bug, take a look if you're interested:
https://github.com/ChronoMonochrome...mmit/bd0dcce403633543f1bf11e5f8b476a3e88322cb
New build is up!
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs) *
Hey there! I've been testing 6.0.1 / 7.1.2 ROMs and I've recently got some issues with camera on 3.4.x kernel build, so I've decided to release a new refresh build (based on 3.0.101 sources).
I've rebased the most of recent changes to CM14.1 branch in order to support these ROMs (so if you're using older ROMs like stock 4.1.2 then better to use previous release cause some patches might be missing here).