{
"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"
}
In this thread you may find my customized kernel 3.0.x for JB 4.1.2 and JB 4.2.2 rom (CM10, CM10.1 and derivatives) that use PMEM memory allocations.
I hope it will be useful, and ensures better performance and battery life.
Of course, your feedback, as always, are welcome and certainly valuable.
The main features are the following:
- Kernel 3.0.x
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my custom Linaro 4.8.3-2013.11 toolchain optimized for Cortex-A8
- Built with Cortex-A8 and NEON VFP optimization flags (both kernel and modules)
- Built with -O3 optimization flag (both kernel and modules)
- CPU overclockable up to 1824 MHz
- CPU frequencies undervolted (UV version) or extremely undervolted (EXUV version)
- CPU voltage control VDD sys interface (click for more details)
- 360MB, 370MB or 390MB of free RAM
- Init.d support
- Fast Charge support (default disabled, click for more details)
- Battery Life eXtender support (default disabled, click for more details)
- Ram Console support (click for more details)
- Backlight Notification v9 (BLNv9) (click for more details)
- USB OTG support (if also implemented on rom side)
- Customizable vibration intensity (click for more details)
- Lowered display panel voltage
- Lowered touchscreen voltage
- Lowered wifi voltage
- Lowered swappiness (60 -> 45)
- Increased CPU frequency during boot
- Optimized AES and SHA1 routines for ARM cpu architecture
- Fixed 100% battery notification after charger unplug
- Increased audio volume on board side
- Con Kolivas' CK3 Tweaks
- Optimized SLUB memory allocator
- Optimized ARM RWSEM (read/write semaphore) algorithm
- Optimized asynchronous I/O latency on solid state disks
- Optimized string and memcopy libs
- Disabled Gentle Fair Sleepers for better UI performance
- Filesystem dynamic read-ahead (based on disk size)
- CIFS support on boot
- Fast Random generator (frandom) support (click for more details)
- New display drivers from Samsung Galaxy SII
- Updated light sensor driver and display driver light sensor changes
- Phantom key presses filter (click for more details)
- Dynamic FSync v1.2 (click for more details)
- Dynamic dirty page writebacks (click for more details)
- VM tweaks for performance and less battery consumption
- Revised LowMemoryKiller parameters for better performance (click for more details)
- Customizable timeout for touchkeys backlight after a key press or touchscreen press (click for more details)
- Customizable activation status of touchkeys backlight on touchscreen press (click for more details)
- Timer slack controller (click for more details)
- Dynamic management of the minimal timer slack value during suspend/resume (click for more details)
- LowMemoryKiller management of not killable processes (click for more details)
- exFAT support
- Additional TCP Congestion algorithms
Available CPU governors:
- Adaptive
- BrazilianWax
- Conservative
- Hyper
- Intellidemand
- Interactive
- InteractiveX
- LionHeart
- LulzActive
- OnDemand (default)
- OnDemandX
- Performance
- Powersave
- SmartAssV2
Available I/O schedulers:
- BFQ
- CFQ
- Deadline
- Noop
- ROW (default)
- SIO
- V(R)
Kernel Downloads for JB 4.1.2:
K^Kernel JB-4.1.2 Mediafire Folder
[QRCODE]http://www.mediafire.com/?l9vakf1dadf37[/QRCODE]
- v3.1 -
for CM 10
and the other roms based on latest CM 10
Kernel Downloads for JB 4.2.2:
K^Kernel JB-4.2.2 Mediafire Folder
[QRCODE]http://www.mediafire.com/?pd9zpuideo7zm[/QRCODE]
- v3.1 -
for ADC CM 10.1 Release 9
and the other roms based on this CM 10.1
- v3.0 -
for ADC CM 10.1 Release 8
and the other roms based on this CM 10.1
Howto install the kernel:
1) Download the preferred kernel zip file to sdcard or external sdcard
2) Reboot to recovery mode
3) Flash the kernel zip file
4) Wipe cache and dalvik cache
5) Fix permissions
6) Reboot the system
Kernel sources (on GitHub):
Development branch of K^Kernel 3.0 for JB 4.1.2
Development branch of K^Kernel 3.0 for JB 4.2.2
Useful info:
- Special features and sysfs settings
- Frequently asked questions
Rom and kernel 3.0.x known problems:
- For the builds with 390MB of free RAM, the camera works and the video recording works only in 480p mode
- Possibile graphical glitches in camera preview
- Wifi Tethering doesn't work on new CM 10.1 roms that use 3.4 kernels
Tables:
Changelog:
Code:
[B]29/11/2013 - K^Kernel v3.1 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.101
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.8.3-2013.11 toolchain optimized for Cortex-A8
- fs/sync: Make sync() satisfy many requests with one invocation (credits to Paul E. McKenney)
- usb: gadget: mass_storage: added sysfs entry for cdrom to LUNs (credits to FrozenCow)
- Update default and custom defconfigs for additional TCP Congestion algorithms (credits to Christopher83)
- add exfat support (credits to radu)
- Update default and custom defconfigs for exFat support (credits to Christopher83)
- acpuclock-7x30: Raised some standard UV and stock voltages for high OC cpu frequencies (credits to Christopher83)
- input: Updates to Phantom Key Presses filter (credits to Christopher83)
- softirq: reduce latencies (credits to Eric Dumazet)
- fs: vfat: reduce the worst case latencies (credits to xiaogang)
- jiffies conversions: Use compile time constants when possible (credits to Joe Perches)
- Makefile: Use -fno-inline-functions to build with Linaro GCC 4.8 toolchains (credits to Christopher83)
Additional commit for JB 4.1.2 only
- msm: display: Prevent fb suspend in charging mode for ancora only (credits to Christopher83)
Additional commit for JB 4.2.2 only
- qt602240_ts: updated touchscreen driver in according of Multi-touch protocol (credits to CastagnaIT)
[B]27/10/2013 - K^Kernel v3.0 for JB 4.2.2[/B]
- Kernel 3.0.101
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.10 toolchain optimized for Cortex-A8
- Resolved problems of magnetic, proximity and orientation sensor (credits to CastagnaIT)
- gp2a_proximity: readded wakelock is necessary to avoid problems with answer calls and some cleanups (credits to CastagnaIT)
[B]10/10/2013 - K^Kernel v2.9 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.99
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- New bootsplash logo
- mm: remove compressed copy from zram in-memory (credits to Minchan Kim)
- lib/lzo: Rename lzo1x_decompress.c to lzo1x_decompress_safe.c (credits to Markus F.X.J. Oberhumer)
- lib/lzo: Update LZO compression to current upstream version (credits to Markus F.X.J. Oberhumer)
- lib/lzo: huge LZO decompression speedup on ARM by using unaligned access (credits to Markus F.X.J. Oberhumer)
- ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations (credits to Ivan Djelic)
- ARM: 7670/1: fix the memset fix (credits to Nicolas Pitre)
- msm: vidc: return error in case of init failure (credits to Pushkaraj Patil)
- Switched to SIO I/O scheduler
- Fixed change conflicts between custom settings and init.d settings during boot
- Possibility to disable the redirection to frandom number generator
Additional commits for JB 4.1.2 only
- Revert "video: msm: Fix LCD enable sequence for ancora lcd rev.3" (credits to Arco68)
- msm: display: Prevent fb suspend in charging mode for all (credits to Arco68)
[B]11/09/2013 - K^Kernel v2.8 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.95
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.08 toolchain optimized for Cortex-A8
- Bluetooth: Fix for the l2cap layer crashes while turning OFF BT (credits to Nitin Shivpure)
- Enable setting security contexts on rootfs inodes (credits to Stephen Smalley)
- ariesve_sensors: updated all sensors to match with the new opensource libsensors for CM 10.1 kernel (credits to CastagnaIT)
- board_ariesve: cleanup mdp_pdata and added missing mem_hid (credits to CastagnaIT)
- net: ipv6: add missing lock in ping_v6_sendmsg (credits to Lorenzo Colitti)
- net: ipv6: fix wrong ping_v6_sendmsg return value (credits to Lorenzo Colitti)
- msm_fb: Correct R and G offsets for correct mapping (credits to Jeevan Shriram, thanks to Arco68)
- USB: gadget: Cleanup boot-up message with default usb composition (credits to Mayank Rana, thanks to Arco68)
- cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay (credits to Minsung Kim, thanks to Arco68)
- CIFS support on boot
[B]05/08/2013 - K^Kernel v2.7 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.89
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- Revert "ARM: 7765/1: perf: Record the user-mode PC in the call chain.", this should solve the battery charging failures (credits and thanks to Arco68)
[B]25/07/2013 - K^Kernel v2.6 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.87
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- msm: msm_fb: remove mmio access through mmap (credits to Manoj Rao, thanks to Arco68)
- writeback: Fix occasional slow sync(1) (credits to Jan Kara)
- cfq-iosched: Fix null pointer dereference (credits to Sujit Reddy Thumma)
- staging: android: timed_gpio: Fix unreg order (credits to Olav Haugan)
- msm: cpufreq: Only apply driver limits for scaling_min/max_freq writes (credits to Deepak Katragadda)
[B]15/07/2013 - K^Kernel v2.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.86
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- Fixed lost of the touchscreen configuration after suspend (credits and thanks to CastagnaIT)
- LowMemoryKiller management of not killable processes (implemented by me, thanks to CastagnaIT for the original idea of this feature)
[B]07/07/2013 - K^Kernel v2.4 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.85
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Timer slack controller (credits to Kirill A. Shutemov, thanks to Boype and Stuffynet)
- Dynamic management of the minimal timer slack value on suspend/resume
[B]30/06/2013 - K^Kernel v2.3 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.84
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Updates and fix to Interactive CPU governor (credits to Lianwei Wang, thanks to Arco68)
- dpram: Some minor changes from ics-3.0 (credits and thanks to Arco68)
- Revert Temporary workaround for flicker brightness after screen on
- Fixed flicker brightness when turning on the screen (credits and thanks to CastagnaIT)
- Fixes to graphic drivers (credits to Suman Tatiraju, thanks to Arco68)
- Fixes to ipv6 (credits to Hannes and Lorenzo Colitti, thanks to Arco68)
- Other minor fixes (from CAF sources)
- CK3 tweaks (credits and thanks to Con Kolivas)
- Increased battery check interval from 5 seconds to 15 seconds
- New static Cyanogen boot logo (credits and thanks to Stefano187)
[B]24/06/2013 - K^Kernel v2.2 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.83
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Updates and fixes to Interactive CPU governor (credits to Todd Poynor and Minsung Kim, thanks to Arco68)
- Squashed update of BFQ-V6 to BFQ-v6r2 (thanks to Arco68)
- Corrected an unmanaged gamma for autobrightness
- Customizable timeout of touchkeys backlight after a key press
- Customizable activation status of touchkeys backlight on touchscreen press
- Fix for discharging battery issue while charging to 100% (credits to Skywalker01)
- Fix to dynamic fsync to don't disable fdatasync (credits to Faux123)
- Enabled CleanCache
[B]10/06/2013 - K^Kernel v2.1 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.81
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.05 toolchain optimized for Cortex-A8
- Re-added optimized string and memcopy libs (credits and thanks to Miao Xie)
- Dynamic Fsync (credits and thanks to Faux123)
- Dynamic dirty page writebacks
- VM tweaks for better performance and less battery consumption
- Revised LowMemoryKiller parameters for better performance
[B]27/05/2013 - K^Kernel v2.0 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.80
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.05 toolchain optimized for Cortex-A8
- Remove a not needed mmc_power_off (credits and thanks to Arco68)
- Some display fixes (credits and thanks to Arco68)
- Some changes to the touchscreen power-on routine
- Fixed display regulators init
- Updated LCD regulator (credits and thanks to CastagnaIT)
- Power management support on S6E63M0 display driver
- Fixed double activation of the regulators of the display (credits and thanks to CastagnaIT)
- Lowered Vibetonz voltage
- Adjusted some voltage regulators
- Restored min read ahead (from 32 kbytes to 16 kbytes)
- Other fixes and optimizations to RWSEM (read and write semaphore) taken from 3.10 kernel
[B]13/05/2013 - K^Kernel v1.9 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.78
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Removed pop-up noise at the end of power off sequence (credits and thanks to CastagnaIT)
- Fixed bluetooth files transfer, the issue was present only on CM 10.1, ported from 3.4 kernel branch (credits and thanks to Arco)
- Changes to fix the suspend problems caused by BLN
[B]28/04/2013 - K^Kernel v1.8 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.75
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Added Intellidemand CPU governor (credits and thanks to Faux123)
- Imported the new LowMemoryKiller from 3.4 kernel
- Changed the debug level of the LowMemoryKiller from 2 to 1
- Added Voku and Dorimanx tweaks to LowMemoryKiller (credits and thanks to them)
- Removed PMEM reservation for audio (credits and thanks to Arco68)
- Updated light sensor driver and display driver light sensor changes (credits and thanks to CastagnaIT and Ivendor)
[B]19/04/2013 - K^Kernel v1.7 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.74
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Phantom key presses filter, changed the default home_allowed_irqs parameter from 2 to 4
- Disabled Gentle Fair Sleepers for better UI performance
- Lowered touchscreen voltage
- Added BrazilianWax CPU governor
- Various changes and updates to ARM RWSEM (read/write semaphore) algorithm
- New available memory configuration with 390MB of free RAM (camera works, video recording works only in 480p mode)
[B]15/04/2013 - K^Kernel v1.6 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.73
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Phantom key presses filter (new module developed by me)
- New display drivers s6e63m0 from Samsung Galaxy SII (credits and thanks to CastagnaIT)
[B]06/04/2013 - K^Kernel v1.5.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.72
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Fixed WEP Connections (credits and thanks to Ivendor)
[B]02/04/2013 - K^Kernel v1.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.71
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Revised PMEM allocations to preserve more memory for Surface Flinger
- Removed optimized lib/string and lib/memcopy, cause performance issues
- Added Adaptive and Hyper CPU governors
[B]26/03/2013 - K^Kernel v1.4.6 for JB 4.1.2 and JB 4.2.2[/B]
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Backlight Notification v9 (BLNv9) (credits and thanks to CastagnaIT)
- Customizable vibration intensity (credits and thanks to CastagnaIT)
[B]24/03/2013 - K^Kernel v1.4.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.70
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Fixed performance issues
- Ram Console support (credits and thanks to Ivendor)
- Different builds with RAM Console support or without (seems to be more responsive)
[B]18/03/2013 - K^Kernel v1.4 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.69
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Built with my latest custom Linaro 4.7.3-2013.03 toolchain optimized for Cortex-A8
- Optimized SLUB memory allocator (thanks to CastagnaIT)
- Optimized ARM RWSEM algorithm (credits and thanks to Ashwin Chaugule)
- Optimized lib/string and lib/memcopy (credits and thanks to Miao Xie)
- Filesystem dynamic read-ahead (based on disk size) (credits and thanks to Chad Goodman)
- Fast Random generator support (frandom) (credits and thanks to Eli Billauer)
- Optimized asynchronous I/O latency on solid state disks (credits and thanks to Dave Kleikamp)
- Various fixes
[B]11/03/2013 - K^Kernel v1.3.5 for JB 4.1.2[/B]
- New Broadcom Wireless drivers adapted by Samsung (dhd.ko) support for CM 10 (JB 4.1.2) by Ivendor Beta 3 and next builds
[B]10/03/2013 - K^Kernel v1.3.5 for JB 4.2.2[/B]
- New Broadcom Wireless drivers adapted by Samsung (dhd.ko) support for CM 10.1 (JB 4.2.2) by Xistance Alpha 5 and next builds, CM 10.1 by Doomsday94 builds released from 11/03/2013
[B]09/03/2013 - K^Kernel v1.3 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.68 sources synched with jb-3.0 repos of Ivendor and Arco68
- Built with my custom Linaro 4.7.3-2013.02 toolchain optimized for Cortex-A8
- Added Cortex-A8 and NEON VFP optimization flags (both kernel and modules)
- Added -O3 optimization flag (both kernel and modules)
- Added more CPU frequencies and overclockability up to 1824 MHz (thanks to Doomsday94)
- Added CPU frequencies undervolted (UV version) and extremely undervolted (EXUV version) options (thanks to CastagnaIT and Smeroni for the initial implementation for our device)
- Added 5 additional CPU governors (InteractiveX, LionHeart, LulzActive, OnDemandX, SmartAssV2)
- Added 2 additional I/O schedulers (SIO and VR)
- Some fixes and tuning to LuzActive CPU governor for better battery life
- Added CPU voltage control VDD sys interface (thanks to Doomlord)
- Added 360MB or 370MB of free RAM options (thanks to Diablo555 and Doomsday94)
- Added optimized AES and SHA1 routines for ARM cpu architecture (credits and thanks to CastagnaIT)
- Added Fast Charge support (credits and thanks to Ivendor)
- Added Battery Life eXtender support (thanks to Ezekeel), adapted by me for I9001 and I8150
- Lowered display panel voltage
- Lowered wifi voltage
- Lowered swappiness
- Increased CPU frequency during boot (for faster boot process)
- Fixed 100% battery notification after charger unplug
- Increased audio volume on board side
- Old Broadcom Wireless drivers (dhd.ko) support for CM 10 (JB 4.1.2) by Ivendor Beta 2 and previous builds
- New Broadcom Wireless drivers (bcmdhd.ko) support for CM 10.1 (JB 4.2.2)
Credits and Thanks to:
Arco68 and Ivendor for their awesome work and their kernel sources
CastagnaIT for his awesome work, his 2.6 kernel sources where I learned many things and for the useful features inspiration
Xistance for his wonderful work to give us the CM 10.1 rom
Ezekeel, Doomlord, Faux123, Stratosk, Tegrak, ErasmuX, Imoseyon, Doomsday94, Hadidjapri, Diablo555 and other devs I'm surely missing
CyanogenMod, Kernel.org, Code Aurora Forum, [Google], Linaro GCC developers
XDA:DevDB Information
[GT-I9001][PMEM] K^Kernel 3.0 for JB 4.1.2 and JB 4.2.2, Kernel for the Samsung Galaxy S I9000
Contributors
Christopher83
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v3.1
Stable Release Date: 2013-11-29
Created 2013-09-13
Last Updated 2014-08-30
Special features and sysfs settings (Part 1):
Here you can find some useful scripts that can be used with the following described features:
Scripts
Phantom Key Presses filter
This feature is an attempt to workaround a well known hardware bug of some Samsung devices.
Pratically, the high activity of the radio hardware, in particular the antenna, could cause interference on Melfas chip, which is located very close to the antenna.
This interference could induce bad interrupts that are seen by the chip as possible HOME, MENU or BACK key presses.
These phantom key presses are happening expecially in 2G mode.
The solution includes a new device module (phantom_kp_filter), which also allows the filtering parameters customization, and various changes to cypress-touchkey and pmic8xxx-keypad modules.
The phantom key presses filtering is enabled by default for incoming MENU and BACK touch keys, because for these keys is simpler to recognize a bad interrupt or an invalid key press, instead it's disabled for incoming HOME key (read the next howto infos to enable it).
I also developed a new app to better manage the filtering status and the filtering parameters customization, you can find it on this thread:
Phantom Key Presses Filter Manager
How to enable/disable the feauture and customize the filtering parameters:
The new device module allows to show the number of ignored key presses and to customize the filtering parameters by means of a sysfs interface, at the following system path: /sys/class/misc/phantom_kp_filter
The interface exposes these files:
home_enabled: show/edit the enable status of the phantom HOME key presses filtering (0 = disabled and 1 = enabled, disabled by default)
home_allowed_irqs: show/edit the allowed max number of incoming interrupts to consider a HOME key press as valid (from 1 to 32, default = 4), a lower value allows to have a more aggressive filtering, instead a higher value allows to have a more permissive filtering
home_report_wait: show/edit the wait time in ms before report the collected HOME key presses (from 5 to 25 ms, default = 12 ms), the key presses during this wait time are collected and reported only if the system received a number of interrupts less than or equal to the allowed max number of incoming interrupts (home_allowed_irqs parameter)
home_ignored_kp: show the ignored possible phantom HOME key presses
menuback_enabled: show/edit the enable status of the phantom MENU and BACK key presses filtering (0 = disabled, 1 = enabled, enabled by default)
menuback_interrupt_checks: show/edit the number of interrupt checks to be performed for the incoming MENU and BACK key presses (from 1 to 10, default = 10), a lower value is more permissive, a higher value securely avoids most of the bad interrupts
menuback_first_err_wait: show/edit the time in ms to wait after the first error on MENU or BACK keys if there are many invalid key errors in rapid sequence (from 50 to 1000 ms, default = 500 ms), the default value is optimal and well tested
menuback_last_err_wait: show/edit the time in ms to wait after the last error on MENU or BACK keys if there are many invalid key errors in rapid sequence (from 50 to 1000 ms, default = 100 ms), the default value is optimal and well tested
menuback_ignored_kp: show the ignored possible phantom MENU and BACK key presses
version: show the module version
To change the filtering parameters:
1) By downloading and using my new app PkfManager
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)
- Download the script named 05pkf_alt
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred filtering parameters (the downloaded script has the default filtering parameter values and enables the phantom HOME key presses filtering)
- Copy the new file inside /etc/init.d
- 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)
- Reboot
3) By directly editing the files inside /sys/class/misc/phantom_kp_filter (the values you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands
Code:
su
echo [COLOR="Blue"][I]value[/I][/COLOR] > /sys/class/misc/phantom_kp_filter/[COLOR="Green"][I]parameter_name[/I][/COLOR]
where value is the value you want to set and parameter_name is one of the previously described editable parameters
For example, these commands will enable phantom HOME key presses filtering:
Code:
su
echo 1 > /sys/class/misc/phantom_kp_filter/home_enabled
To show the number of ignored key presses (possible phantom key presses):
1) By directly opening the files /sys/class/misc/phantom_kp_filter/home_ignored_kp and /sys/class/misc/phantom_kp_filter/menuback_ignored_kp
2) By using Terminal Emulator
- Open Terminal Emulator
- Run these commands
Code:
su
cat /sys/class/misc/phantom_kp_filter/home_ignored_kp
cat /sys/class/misc/phantom_kp_filter/menuback_ignored_kp
Customizable timeout of touchkeys backlight after press
This feature is available for v2.2 kernel and next releases, it allows to set a customized timeout of touchkeys backlight after a key press or touchscreen press. The default value is 1600 ms.
How to set the timeout of touchkeys backlight:
1) By downloading and using the related setting inside NsTools
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)
- Download the script named 20backlight_timeout
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred timeout (the downloaded script will set the status to 0 = disabled)
- Copy the new file inside /etc/init.d
- 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)
- Reboot
3) By directly editing the file /sys/class/misc/notification/bl_timeout (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to set the timeout of touchkeys backlight to 1000 ms (1 second)
Code:
su
echo 1000 > /sys/class/misc/notification/bl_timeout
Customizable activation status of touchkeys backlight on touchscreen press
This feature is available for v2.2 kernel and next releases, it allows to enable/disable the touchkeys backlight after a touchscreen press.
How to set the status of touchkeys backlight on touchscreen press:
1) 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)
- Download the script named 25touchlight_status
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred status(the downloaded script will set the status to 0 = disabled)
- Copy the new file inside /etc/init.d
- 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)
- Reboot
2) By directly editing the file /sys/class/misc/notification/touchlight_enabled (the value you set will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to disable the touchkeys backlight on touchscreen press
Code:
su
echo 0 > /sys/class/misc/notification/touchlight_enabled
- Or run these commands to enable the touchkeys backlight on touchscreen press
Code:
su
echo 1 > /sys/class/misc/notification/touchlight_enabled
CPU voltage control VDD sys interface
This feature allows to customize the voltage assumed by each cpu scaling frequency.
It could be useful if you'd like to decrease one or more voltages for battery saving purposes (undervolting), or to increase/adjust them to prevent phone freezes (overvolting).
How to customize the voltages:
1) By downloading and using Trickster MOD
or IncrediControl and changing the voltages table inside the SVS tab
2) By using customized init.d scripts (the custom values will be always restored after a reboot, if you don't format the system partition)
- Download one of the script named 01vdd_levels*
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your customized voltages, where each line has this syntax
Code:
echo "[I][B][COLOR="Blue"]cpu_freq_HZ[/COLOR][/B][/I] [I][COLOR="SeaGreen"][B]mV[/B][/COLOR][/I]" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
cpu_freq_HZ is the cpu frequency in Hz you'd like to change
mV is the voltage you want to set
For example, the following line means that when the cpu frequency is 1516800 Hz = 1516 MHz, the voltage used will be 1175 mV
Code:
echo "1516800 1175" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
- Copy the new file inside /etc/init.d
- 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)
- Reboot
3) By using Terminal Emulator (note that the values you set will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands
Code:
su
# Run a command for each cpu frequency voltage you'd like to change
echo "[I][B][COLOR="Blue"]cpu_freq_HZ[/COLOR][/B][/I] [I][COLOR="SeaGreen"][B]mV[/B][/COLOR][/I]" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
cpu_freq_HZ is the cpu frequency in Hz you'd like to change
mV is the voltage you want to set
For example, the following line means that when the cpu frequency is 1516800 Hz = 1516 MHz, the voltage used will be 1175 mV
Code:
echo "1516800 1175" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Alternative Extreme Undervolted (ExUV) settings
If after overclocking your I9001 you noticed some freezes when on ExUV kernel builds, you may use an alternative extremely undervolted setting with the init.d script you can find here: 01vdd_levels_alt_exuv
- Download the script
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Copy the new file inside /etc/init.d
- 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)
- Reboot
Customized vibration intensity
This feature has been developed by CastagnaIT and allows to set a customized vibration intensity (121 is the default stock value).
It could be useful if you don't like the stock vibration intensity and you'd like to have a lower / stronger vibration.
The setting will affect the haptic feedback and the notification vibration intensity.
How to set a customized vibration intensity:
1) By using the related setting inside System->Advanced->Vibration (only on CM 10 Beta 4 and next releases)
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)
- Download the script named 10vibetonz
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred vibration intensity (the downloaded script will set the vibration intensity to 70)
- Copy the new file inside /etc/init.d
- 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)
- Reboot
3) By directly editing the file /sys/class/vibetonz/immDuty/pwmvalue_intensity (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands (changing the intensity value = 70 with the preferred one)
Code:
su
echo 70 > /sys/class/vibetonz/immDuty/pwmvalue_intensity
Backlight Notification V9 (BLNv9)
This feature allows to notify you of missing calls, messages, emails, etc... by lighting up or blinking the Menu and Back buttons.
With BLNv9 enabled you don't need to unlock the screen to see if you have new notifications.
How to configure the BLNv9:
1) By downloading and using BLN Control Free, BLN Control Pro or NsTools
2) By directly editing the file /sys/class/misc/backlightnotification/enabled and setting 1 to enable the feature, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to enable the feature
Code:
su
echo 1 > /sys/class/misc/backlightnotification/enabled
- Run, instead, this command to disable the feature
Code:
su
echo 0 > /sys/class/misc/backlightnotification/enabled
Work in progress (init.d, blinking and other settings)...
Force Fast Charge
This feature allows you to force AC charging for any charger that is detected as USB (eg. PC USB ports, USB Car Chargers) and pull the full current the charger can support, in such a way as to speed up the time required for a complete battery recharge.
By enabling this feature, the USB / ADB data transfers will be disabled (security limitation to protect your data).
How to enable/disable the Force Fast Charge:
1) By using the related setting inside System->Advanced->Force Fast Charge (only on CM 10 Beta 3 and next releases)
2) By downloading and using Trickster MOD
or IncrediControl or NsTools
2) By directly editing the file /sys/kernel/fast_charge/force_fast_charge and setting 1 to enable the force charge, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to enable the force fast charge feature
Code:
su
echo 1 > /sys/kernel/fast_charge/force_fast_charge
- Then, when you want to restore the normal status, run this command to disable the force fast charge feature
Code:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
4) By using a customized init.d script, but I don't recommend it because you have to remember to disable the feature every time you want to connect your device to a pc for data transfering after every reboot
Battery life extender (BLX)
This feature has been developed by Ezekeel and allows to set a customized battery charging limit (100% is the default stock value, if you want, you can set a lower value).
As Ezekeel said, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
If you set a charging limit equal to 100, this feature will be disabled.
How to activate this feature and set a customized charging limit:
1) By downloading and using Trickster MOD or NsTools by setting the customized battery life extender charging limit
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)
- Download the script named 15blx
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred charging limit (the downloaded script will set the charging limit to 95%)
- Copy the new file inside /etc/init.d
- 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)
- Reboot
3) By directly editing the file /sys/class/misc/batterylifeextender/charging_limit (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands (changing the charging limit = 95 with the preferred one)
Code:
su
echo 95 > /sys/class/misc/batterylifeextender/charging_limit
LowMemoryKiller
The LowMemoryKiller driver is used to kill a selected process and free the memory when it is under one of the defined thresholds.
The tuning of the driver could be achieved by means of two parameters exposed by the kernel module via sysfs interface:
- /sys/module/lowmemorykiller/parameters/minfree
This file includes a comma separated array of the threshold numbers for minfree memory size (in page units).
The parameter value set for K^Kernel is "2048,4096,6656,9216,14336,19456".
- /sys/module/lowmemorykiller/parameters/adj
This file includes the comma separated array of oomadj factors, if the corresponding minfree threshold has been reached, one of the process with an oomadj greater than this number will be killed.
The oomadj factor is a property associated to each process, its value is in a range from -17 to +15, the processes with a higher oomadj factor will be the first to be killed when a specific minfree threshold has been reached.
The parameter value set for K^Kernel is "0,20,50,100,250,500".
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
Code:
/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...
RAM Console
This feature is useful expecially for development and debugging purposes, when occurs kernel panic / unexpected shutdowns or reboots. Pratically, the kernel messages are also stored inside a little RAM portion and restored during reboot after a kernel panic, inside the file /proc/last_kmsg.
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)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic fsync feature
Code:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
- Or run this command to re-enable the dynamic fsync feature
Code:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
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), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
In my kernel builds, during boot, I set other customized values:
- an interval of 30 seconds while the screen is on
- an interval of 10 seconds when the screen is 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)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic dirty page writebacks feature
Code:
su
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
- Or run this command to re-enable the dynamic dirty page writebacks feature
Code:
su
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
- Run this command to set customize the two intervals (30 seconds while the screen is on, 10 seconds when the screen is off)
Code:
su
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs
Special features and sysfs settings (Part 2):
Timer slack controller and dynamic management of the minimal timer slack value
The timer slack controller is a feature developed by Kirill Shutemov and it allows to set the minimal timer slack value for every process contained within a control group (cgroup).
A timer slack allows the kernel to manage processes wakeup requests at some future time.
Thanks to this feature, the kernel can set a specific timer slack for the involved processes, minimizing the number of wakeups and allowing a lower system's power consumption.
For further info: Timer slack for slacker developers
I also implemented a new feature in addition to the above one that allows the dynamic management of the minimal timer slack value.
So, it's possible to use different minimal timer slack value when the system is active and when has been suspended.
How to customize the dynamic timer slack controller feature:
Three new cgroup parameters are exposed inside each processes hierarchy contained in /dev/cpuctl path:
- timer_slack.min_slack_ns is the timer slack used when the system is active for the current processes hierarchy
- timer_slack.min_slack_suspend_ns is the timer slack used when the system is suspended for the current processes hierarchy
- timer_slack.effective_slack_suspend_ns is the timer slack currently used
At the moment, the values chosen and used by K^Kernel are the following:
- core processes (/dev/cpuctl), 0 ns when the system is active, 50000 ns when the system is suspended
- foreground apps/processes (/dev/cpuctl/apps), 0 ns when the system is active, 250000 ns when the system is suspended
- background non interactive apps/processes (/dev/cpuctl/apps/bg_non_interactive), 100000000 ns when the system is active, 250000000 ns when the system is suspended
1) By directly editing one of the file written above inside /dev/cpuctl and inside each hierarchy subfolder, by setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to set the minimal timer slack for generic and core apps/processes
Code:
su
echo 0 > /dev/cpuctl/timer_slack.min_slack_ns
echo 50000 > /dev/cpuctl/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in foreground
Code:
su
echo 0 > /dev/cpuctl/apps/timer_slack.min_slack_ns
echo 100000 > /dev/cpuctl/apps/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in background and non interactive
Code:
su
echo 100000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns
echo 250000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_suspend_ns
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:
On K^Kernel the feature is enabled by default and the provided processes white lists are the following:
- donotkill_proc_names = "com.cyanogenmod.trebuchet,com.anddoes.launcher,com.teslacoilsw.launcher,org.adwfreak.launcher,gtp.nextlauncher,android.inputmethod.latin,com.touchtype.swiftkey"
this means that Trebuchet Launcher, Apex Launcher, Nova Launcher, ADW Launcher, Next Launcher, stock keyboard and SwiftKey keyboard will be preserved from killing
- donotkill_sysproc_names = "android.process.acore,com.android.phone,com.bel.android.dspmanager"
this means that the system process, the phone process and DSP Manager will be preserved from killing
1) 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)
- Download the script named 80dnkp
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred status and processes list
- Copy the new file inside /etc/init.d
- 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)
- Reboot
2) By directly editing the files inside /sys/module/lowmemorykiller/parameters (note that set values will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands if you want to enable the feature
Code:
# To enable this feature for the processes chosen by the user
echo 1 > /sys/module/lowmemorykiller/parameters/donotkill_proc
# To enable this feature for the system processes chosen by the user
echo 1 > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
- Run these commands if you want to disable the feature
Code:
# To disable this feature for the processes chosen by the user
echo 0 > /sys/module/lowmemorykiller/parameters/donotkill_proc
# To disable this feature for the system processes chosen by the user
echo 0 > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
- Run this command if you want to add, for example, Trebuchet Launcher (CM default launcher) and the default keyboard to the processes white list
Code:
echo "com.cyanogenmod.trebuchet,android.inputmethod.latin" > /sys/module/lowmemorykiller/parameters/donotkill_proc_names
- Run this command if you want to add, for example, the system process, the phone process and DSP Manager to the system processes white list
Code:
echo "android.process.acore,com.android.phone,com.bel.android.dspmanager" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc_names
Work in progress...
FAQ - Frequently asked questions:
Q: What are the differences between EXUV and UV kernel versions?
A: The EXUV kernel versions have extremely undervolted settings for the cpu frequencies, they allows to have a very low battery drain, instead the UV kernel versions have undervolted settings a bit higher than EXUV versions, but always lower than stock kernel settings (take a look at the comparison table on the first post).
The EXUV kernel versions could give some problems (freezes, shutdowns, huge lags) on some devices because the cpu doesn't support too low voltage settings.
For a lower battery consumption, I suggest you to try EXUV versions first and to switch to UV versions only if you encounter one of the above mentioned problems.
Q: What are the differences between 360MB, 370MB and 390MB versions?
A: 360MB, 370MB and 390MB kernel versions have different free ram available for user space, with a higher free ram your device will work better with heavy apps, many concurrently used apps, heavy games, etc.
- 360MB versions have additional 8 MB of free ram than stock kernels (352 MB of free ram), they are suitable for the users that use the device primarly for calls, messages, simple apps and simple games. The camera, video recording (both 480p and 720p modes) and video playback are fully working.
- 370MB versions have additional 18 MB of free ram than stock kernels, they are suitable for the users that use the device also with heavy apps, various concurrently used apps and games. The camera, video recording (both 480p and 720p modes) and video playback are fully working.
- 390MB versions have additional 38 MB of free ram than stock kernels, they are suitable for the users that use the device also with heavy apps, many concurrently used apps and heavy games. The camera and video playback are fully working, the video recording works only in 480p mode.
Q: How can I get the Performance and Developer Options entries inside Settings menu?
A: Go inside Settings -> About Phone -> Scroll down and tap 7 times on Build number (it's an Easter Egg).
Q: How can I get the log after an unexpected shutdown / reboot?
A: After an unexpected shutdown / reboot of the device, if the problem may be kernel related, you should have the /proc/last_kmsg, if so, send me that log and I'll check it to find the possible cause of the problem.
Q: How can I get the logs when I encounter strange system issues while it's running?
A: Check first if the problems could be related to an app you're using and if you changed something in the last days before facing those issues.
If the problem started after installing the kernel, then let me have you logcat and dmesg:
- Open Terminal Emulator and execute these commands:
Code:
su
dmesg > /sdcard/dmesg.txt
locat -v time -d > /sdcard/logcat.txt
- Open you preferred file manager and go inside the internal sd card partition /sdcard
- Send me the dmesg.txt and logcat.txt files, if you want zip them first
\o/ Thank you and good luck!
Wow, this is well formatted thread
Thanks Christopher, will try now
---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------
What's the difference between 360 and 370mb kernel?
woooowwww !! THANKS !!!! you're great !!:good:
Awesome job man. Make sure to get the new kernel ready as my next build is coming with ALL wifi problems fixed with the new driver. It uses a different kind of dhd.ko instead of the old one or bcmdhd.ko.
R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 and JB 4.2.2 v1.3 [09/03/2013]
TwinHeadedEagle said:
Wow, this is well formatted thread
Thanks Christopher, will try now
---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------
What's the difference between 360 and 370mb kernel?
Click to expand...
Click to collapse
Thank you too!
360MB version has more ram allocated by Surface Flinger, should be more stable, suitable for who uses his I9001 primarly for calls, browsing, and not heavy playing.
370MB version should be useful for players.
Sent from my GT-I9001 using xda premium
R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 and JB 4.2.2 v1.3 [09/03/2013]
Xistance said:
Awesome job man. Make sure to get the new kernel ready as my next build is coming with ALL wifi problems fixed with the new driver. It uses a different kind of dhd.ko instead of the old one or bcmdhd.ko.
Click to expand...
Click to collapse
You are great! I'll be ready.
Sent from my GT-I9001 using xda premium
Amaaaaaaaaaazing kernel. For me, the user experience is better on 10.1. In term of performance I can't imagine it can be better. the only thing missed is DeepSleep From Ezekeel which not implemnted yet. more than 10% of drain in the night on my phone
inhirz said:
Amaaaaaaaaaazing kernel. For me, the user experience is better on 10.1. In term of performance I can't imagine it can be better. the only thing missed is DeepSleep From Ezekeel which not implemnted yet. more than 10% of drain in the night on my phone
Click to expand...
Click to collapse
Deep sleep is the built in suspend feature of embedded Linux systems, it's not developed by Ezekeel...
The BLX feature has been developed by Ezekeel.
Released new v1.3.5 kernel versions for CM 10.1 Alpha 5.
The new Broadcom Wireless drivers adapted by Samsung are correctly working
Christopher83 said:
Released new v1.3.5 kernel versions for CM 10.1 Alpha 5.
The new Broadcom Wireless drivers adapted by Samsung are correctly working
Click to expand...
Click to collapse
What about Doomsday CM10.1? I can use this kernel on his rom?
Harrocan said:
What about Doomsday CM10.1? I can use this kernel on his rom?
Click to expand...
Click to collapse
Yes you can use v1.3
AW: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/2
Does this kernel use the OC table from diablo?
Sent from my GT-I9001 using xda app-developers app
XeLLaR* said:
Does this kernel use the OC table from diablo?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
It's similar to CatagnaIT one...
Remember that you can customize each frequency voltage using IncrediControl, the kernel has Voltage Control interface on sysfs...
AW: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/2
Wttffff this **** is incredible
Awesome bro :thumbup: CM 10.1 is flying <3 its so damn smooth, thanks :thumbup:
Sent from my GT-I9001 using xda app-developers app
R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/20
I can't play videos 720p with kernel 360mb and 370mb for cm10.1
I have alpha5 xistance
Inviato dal mio GT-I9001 con Tapatalk 2
Good Good Good christopher awesome kernel for me is very smooth and the WiFi works great!!
Related
I'm compiler kernel and need tester. The kernel compatible only with Gingerbread Rom and can flash with CWM.
And may be this flashable will conflict with another mods/script in init.d (stuck in splash screen or bootloop)
Please nandroid backup before use it. Because use it at your risk.
Download Test 9 (New & Final Version):
http://d-h.st/SGx
Download Test 8:
http://d-h.st/gSD
Download Test 7:
http://d-h.st/72f
Download Test 6:
http://d-h.st/oFd
Download Test 5:
http://d-h.st/pO8
Download Test 4:
http://d-h.st/3bA
Download Test 3:
http://d-h.st/Q1k
Download Test 2:
http://d-h.st/gOu
Log Test 9:
- Fix USB Tethering (need change dnsmasq_dhcp patch & make run dnsmasq_dhcp when USB Tethering running)
- Fix segment fault when zipalign script execute
- Add dnsc binary to ping url address and this binary function to know when you online or not. If you online crossbreeder script run/execute
- Remove sqlite3 and system server binary (not stable and broken something)
- Change value of scripts
**) For flash this need clean rom and this kernel CAN'T update from previously kernel. If you have issue with wifi tether, you can use app Barnacle Wifi Tether from play store.
Recommend kernel and everything look like stable for me. May be this final version if i don't found any bugs again
Log Test 8:
- Fix dnsmasq dhcp only need 1 process and previously version i got trouble connection issue while tethering
- Change path dnsmasq_dhcp binary to crossbreeder folder (from /system/bin/* change to /system/etc/CrossBreeder/*)
- Fix Clean Dalvik script and now work with schedule
- Add dalvikvm binary and system_server binary from jellybean (may be can boost performance)
- Use some value of tweak from ThunderBolt/Pikachu01
- Change some value of tweak
**) For flash this need clean rom and this kernel CAN'T update from previously kernel. If you have issue with wifi tether, you can use app Barnacle Wifi Tether from play store.
Log Test 7:
- Fix crossbreeder (low RAM because duplicate dnrd process and dnsmasq_dhcp process. Fix in this version)
- Fix haveged script (need link /dev/random to /dev/urandom). Entropy always stay in 4096. To check this you can type in terminal emulator
Code:
su
entro
- Remove extendedmenu and rngd
- Use only two dnsmasq_dhcp/dnsmasq process. If you check in terminal emulator with
Code:
su
ps | pgrep dnsmasq_dhcp
or
Code:
su
ps | pgrep dnsmasq
You'll found only 2 process running and always got 2 dnsmasq process everytime (in other version you'll get many dnsmasq and make low RAM).
- Fix build.prop tweak
**) For flash this need clean rom and this kernel CAN'T update from previously kernel. If you have issue with wifi tether, you can use app Barnacle Wifi Tether from play store.
Log Test 6:
- In this version you can choose use haveged or rngd (default use haveged)
- Add build.prop tweak in init.d (can disable in extended menu)
- Tweak now 80% complete for get maximal performance for this phone (i don't have any idea again to get more better than this. Thank you )
**) For flash this need clean rom and this kernel CAN'T update from previously kernel. If you have issue with wifi tether, you can use app Barnacle Wifi Tether from play store
Log Test 5:
- Fix script init.d
- Fix Crossbreeder more better and less aggressive to check DNS and IP Address
- Fix hosts and save more memory
**) For flash this need clean rom and this kernel CAN update from previously kernel test 4. If you have issue with wifi tether, you can use app Barnacle Wifi Tether from play store
Log Test 4:
- Use GCC 4.4.3 to compiler kernel (much more stable)
- Remove unnecessary module
- Add random optimize in kernel (3 commit github)
- Remove haveged and use rngd
- Combine crond script to one script and run every 45 minutes. Save more ram for this (script are Fast Engine Flush, Fast Engine Swap and Reduce Wifi TX Power)
- Add script Read Write Partition tweak and I/O Scheduler Tweak
- Update CrossBreeder. Much more save ram and now use blank gif for ADBlock (every things work).
- Boot more faster than before (optimize script more efficient) and more performance
**) For flash this need clean rom and can't update from previously kernel test (a lot of difference things)
Log Test 3:
- Fix All CPU Governors source code (i hope it)
- Try with difference egl.cfg value
- Change Fast Engine Flush script run every 60 minutes
- Change Fast Engine Swap script run every 45 minutes
- Change Haveged script run every 20 minutes
- Add Reduce TX Power script and this script run 30 minutes after you turn on your wifi/wifi tethering
- Add CrossBreeder script and script little difference with original (give me more ram with all feature from CrossBreeder work and run without problem).
And you can use AdAway apps to enable or disable hosts file (It will be work together with AdBlock CrossBreeder)
- Add Audio Lag Reduction in huawei extended menu :laugh:
- Fix huawei extended menu and make all feature can be enable or disable it
Log Test 2:
- Revert back with linaro toolchain => android ndk result is random reboot and kernel panic for me
- Revert back with haveged binary, remove rngd & problem solved now
- Add Haveged Script => Entropy Lag reduction and this script run every 5 minutes with crond style (script are difference with idcrisis/crossbreeder because use crond to execute)
Log Test 1:
- Cpu Governors: Virtuous, AssWax, Superbad, Brazilianwax, Lagfree, Minmax, Smoothass, SavagedZen, InteractiveX, Interactive, SmartassV2, Conservative, Ondemand, Userspace, Powersave, Scary and Performance => Default CPU Governors use Scary
- I/O Scheduler: Noop, Anticipatory, Deadline, cfq, Sio, bfq, vr and Zen => Default I/O Scheduler use Zen
- Min-Max CPU Default: 61MHz-600Mhz
- Add experimental module
- Add new egl.cfg and libGLES_qcom.so
- Add KickAssKernel Script
- Add SQLite database vaccum Script => this script run every 1 week
- Add Automatic ZipAlign Script => this script run every 1 week
- Add Clean Dalvik Cache and Cache Script => this script run every 1 week
- Add Crond Script
- Add Fast Engine Flush Script => drop caches script and this script run every 45 minutes with crond style
- Add Fast Engine Swap Script => drop swap script and this script run every 30 minutes with crond style
- Add RNGD/Seeder Script => Entropy Lag reduction
- Add Dexo Script => Create Odexed framework file (please read post 2 for instruction)
Credit:
All Huawei Dev
Zeppelinrox
McByte jkSGS3
Ryuinferno
tommytomatoe
idcrisis
Pikachu01
Other???
FAQ
How to know my script in init.d work?
You can see all log in /data/*.log
Why first boot so long?
Be patient. Because 3 script do it a job first time (SQLite database vaccum Script, Automatic ZipAlign Script and Clean Dalvik Cache and Cache Script).
The second boot will fast.
How to know rngd or haveged run?
You can type in terminal
Code:
su
extendedmenu
How to make/create Odexed framework file?
You can type in terminal, use adb or qtadb
Code:
su
dexo
And your phone will reboot if the script finish do a job
How to know CrossBreeder AdBlock work?
You can try to view file /system/etc/hosts and try one url in that file. Try it in your internet browser and you can get [ADBLOCK] (in NEW VERSION you'll got blank gif).
Can I disable ADBLOCK CrossBreeder?
Yes, you can. Try to enable or disable with huawei extended menu or use AdAway apps to disable hosts file and reboot to see result
Can I enable or disable feature of this all tweaks?
Yes, you can. Try to enable or disable with huawei extended menu
reserved
You should probably provide a link to your kernel source.
tulangabol said:
I'm compiler kernel and need tester. The kernel compatible only with Gingerbread Rom and can flash with CWM.
And may be this flashable will conflict with another mods/script in init.d (stuck in splash screen or bootloop)
Please nandroid backup before use it. Because use it at your risk.
Download Test 2:
http://d-h.st/gOu
Log Test 2:
- Revert back with linaro toolchain => android ndk result is random reboot and kernel panic for me
- Revert back with haveged binary, remove rngd & problem solved now
- Add Haveged Script => Entropy Lag reduction and this script run every 5 minutes with crond style (script are difference with idcrisis/crossbreeder because use crond to execute)
Log Test 1:
- Cpu Governors: Virtuous, AssWax, Superbad, Brazilianwax, Lagfree, Minmax, Smoothass, SavagedZen, InteractiveX, Interactive, SmartassV2, Conservative, Ondemand, Userspace, Powersave, Scary and Performance => Default CPU Governors use Scary
- I/O Scheduler: Noop, Anticipatory, Deadline, cfq, Sio, bfq, vr and Zen => Default I/O Scheduler use Zen
- Min-Max CPU Default: 61MHz-600Mhz
- Add experimental module
- Add new egl.cfg and libGLES_qcom.so
- Add KickAssKernel Script
- Add SQLite database vaccum Script => this script run every 1 week
- Add Automatic ZipAlign Script => this script run every 1 week
- Add Clean Dalvik Cache and Cache Script => this script run every 1 week
- Add Crond Script
- Add Fast Engine Flush Script => drop caches script and this script run every 45 minutes with crond style
- Add Fast Engine Swap Script => drop swap script and this script run every 30 minutes with crond style
- Add RNGD/Seeder Script => Entropy Lag reduction
- Add Dexo Script => Create Odexed framework file (please read post 2 for instruction)
Credit:
All Huawei Dev
Zeppelinrox
McByte jkSGS3
Ryuinferno
tommytomatoe
idcrisis
Other???
Click to expand...
Click to collapse
Hi,
thank's a lot for new U8150 gingerbread kernel, i'm testing it on official cm 7.2, but only a question:
why isn't possible to use frequency 30 and 49 whit scary governor?
Sorry for my (and google translate) english.
Bye
aorth said:
You should probably provide a link to your kernel source.
Click to expand...
Click to collapse
Sorry i don't have github and don't have enough bandwidth to upload it :angel:
This kernel not enough good. But i'll share my kernel with other
ep690d said:
Hi,
thank's a lot for new U8150 gingerbread kernel, i'm testing it on official cm 7.2, but only a question:
why isn't possible to use frequency 30 and 49 whit scary governor?
Sorry for my (and google translate) english.
Bye
Click to expand...
Click to collapse
I'll try to fix it :fingers-crossed: and add more feature :laugh:
Sorry for my poor English
tulangabol said:
Sorry i don't have github and don't have enough bandwidth to upload it :angel:
This kernel not enough good. But i'll share my kernel with other
Click to expand...
Click to collapse
You have a responsibility to upload the source after releasing your compiled kernel to the public. If you don't, your thread will be locked. Learn more about the GPL license and how it impacts your activity on XDA here: http://forum.xda-developers.com/showthread.php?t=1993721
psyke83 said:
You have a responsibility to upload the source after releasing your compiled kernel to the public. If you don't, your thread will be locked. Learn more about the GPL license and how it impacts your activity on XDA here: http://forum.xda-developers.com/showthread.php?t=1993721
Click to expand...
Click to collapse
That truely i don't have enough bandwith to upload.
I don't have enough knowledge about kernel too. I'm learning alone to compiler that and my teacher is google
My Thread may be close i think
I'll learn more about that. Thank you
[9001][ROM][PMEM][KK][4.4.1][KOT49E] CyanogenMod 11.0 by ADC-Team - Alpha 3 (EOL) - Kernel 3.4.x
{
"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"
}
Hi everyone,
We are back! And we are proud to present our build of CyanogenMod 11.0 for the Galaxy S Plus (GT-I9001).
Currently the team is composed by the following members: (in alphabethic order)
[Dev] CastagnaIT, Christopher83, Educk, Ivendor, Krislibaeer
[Tester] smeroni68, ktulu84, Xellar
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
BLNv9
USB/Wifi tethering
VSync
USB OTG (Only FAT32 support) (check HERE the cables needed)
Phantom key presses filtering
Fixed and working:
Screenshot
Multitasking preview
Lockscreen slider shortcuts
Quick panel tiles
Partially working:
Some graphical glitches in Panorama preview
Web browsing with stock brower not really good (install Chrome or other browser for better use)
Not working:
AOSP keyboard do not work if used with swipe (app related bug)
SD swap do not work (not yet implemented)
Screenshots
CM11.0Installation Guide
Note: CM for Galaxy S Plus is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Download CM11.0 and gapps zips and put them in /sdcard
WARNING: TO FLASH YOU MUST USE ONE OF THE RECOVERY OF THE TEAM... IT'S NOT AN OPTIONAL CHOICE!!!
20131207 Alpha 3 (DL from Dev-Host)
MD5SUM: 43d4a53a399e067bccc93a2e95b332a6
ROM:
AriesParts: add LowRam status (credits to krislibaeer)
ramdisk: mountpoints like in aosp description (credits to krislibaeer)
ramdisk: internal_sd noemulated and external_sd auto type (credits to krislibaeer)
Synced with CM sources (KitKat v4.4.1 - KOT49E)
20131207 KERNEL: (DL from Dev-Host)
MD5SUM: aaded2fd824af9c2dda125c952f2f4de
ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
Kernel 3.4.72
20131116 ADCT GApps (DL from Dev-Host)
MD5SUM: 381d117be483cf672ac33887d212d765
Please verify the md5sum to be sure you got the right one.
Previous versions:
20131201 Alpha 2 (DL from Dev-Host)
MD5SUM: 4fd0b5178227f2db23d5269889bed325
ROM:
media_codecs: Add Google's VP8 and VP9 decoders for 4.4 (credits to erik96)
overlay: remove adb by default cm 11.0 is running (credits to krislibaeer)
BoardConfig: remove deprecated usb config (credits to krislibaeer)
AriesParts: improve low_ram switch (credits to krislibaeer)
BoardConfig: add QCOM_ENHANCED_AUDIO flag (credits to krislibaeer)
BoardConfig: add BOARD_HAVE_PRE_KITKAT_AUDIO_BLOB := true flag (credits to krislibaeer)
BoardConfig: Enable support for mHeap based screenshots (credits to Christopher83)
20131201 KERNEL: (DL from Dev-Host)
MD5SUM: 8b42f021aab0ba062f07b791ba3a2d46
ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
Kernel 3.4.71
crypto: msm: Check for invalid byte offset field (credits to Mona Hossain)
crypto: msm: Check destination buffer write access (credits to Mona Hossain)
crypto: msm: Fix issues related to non-zero byteoffset input (credits to AnilKumar Chimata)
crypto: msm: Fix null pointer exception in qcrypto_count_sg() (credits to AnilKumar Chimata)
crypto: msm: Use scnprintf() instead of snprintf() (credits to AnilKumar Chimata)
20131124 Alpha 1 (DL from Dev-Host)
MD5SUM: 877c516052ff1303a1ae84a6a8962cb1
ROM:
Change some mount points (credits to Arco68)
ariesve: switch to kernel build during compile rom (credits to krislibaeer)
Initial support for the hardware tunables framework (credits to Czobor)
Overlay: Add custom arrays to base frameworks (credits to erik96)
BoardConfig: woraround create the folder /usr to prevent the build from failing (credits to krislibaeer)
Disable PhaseBeam scrolling (credits to Michael Bestas)
Set ro.telephony.call_ring.multiple=0 (credits to Arco68)
ril: Updates for Android 4.4 alias kitkat (credits to krislibaeer)
BoardConfig: Use cortex-a8 error on scorpion (credits to krislibaeer)
libsensors: fix build error (credits to krislibaeer)
overlay: remove disable the home key unlock settings in frameworks_base for now (credits to krislibaeer)
recovery: change graphics.c to fit with new changes (credits to krislibaeer)
BoardConfig: add TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := true new feature on 4.4 (credits to krislibaeer)
ariesve: add ro.config.low_ram new feature on android 4.4 (credits to krislibaeer)
ramdisk: apply changes to wlan to get it working (credits to krislibaeer)
BoardConfig: add USE_SET_METADATA := false, for now we need this because otherwise the flashable zip is not flashable (credits to krislibaeer)
overlay:apps: change Phone to Telephony (credits to krislibaeer)
ramdisk: changes to sdcard mount Android 4.4 (credits to krislibaeer)
ariesve: add a bit debug stuff (credits to krislibaeer)
sepolicy: Add policy configuration for SELinux (credits to Christopher83)
ril: fix sim PIN handling (credits to Pawit Pornkitprasan)
ariesve: build memtrack (credits to krislibaeer)
ramdisk: change also usbdisk mount for android 4.4 (credits to krislibaeer)
BoardConfig: add flag BOARD_EGL_WORKAROUND_BUG_10194508 := true (credits to krislibaeer)
BoardConfig: let camera working again (credits to krislibaeer)
overlay: add Enable lockscreen translucent decor (credits to krislibaeer)
ramdisk: add KSM by default (credits to krislibaeer)
ariesve: Disable JIT cache (credits to krislibaeer)
ariesve: disable preloading of EGL/GL drivers in Zygote at boot time (credits to krislibaeer)
overlay: add extraFreeKbytes - new feature Android 4.4 (credits to krislibaeer)
AriesParts: add low_ram switch (credits to krislibaeer)
ril: aligned custom ariesve ril to SamsungExynos3RIL (credits to CastagnaIT)
Corrected the ril property and some updates (credits to CastagnaIT)
BoardConfig: removed no longer needed BOARD_USE_LEGACY_TOUCHSCREEN (credits to CastagnaIT)
20131124 KERNEL: (DL from Dev-Host)
MD5SUM: 0560e06571327b4076029e75e84b3483
ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
Kernel 3.4.70
msm: kgsl: Avoid turning on GPU clock if already off (credits to Ananta Kishore K)
Update defconfigs to enable some netfilter options (credits to Christopher83)
Revert "ALSA: fix oops in snd_pcm_info() caused by ASoC DPCM" (credits to Christopher83)
Add exFAT support (credits to radu) (Tested on Samsung 64GB SDXC uhs1 PRO card)
Update defconfigs for exFAT support (credits to Christopher83)
msm: vidc: Reset stop_called state when START is called (credits to Deepak Verma)
msm: vidc: set EOS on output buffer pending transaction (credits to Deepak Verma)
Clone ion.h to msm_ion.h (credits to Arco68)
Add extra free kbytes tunable (credits to Rik van Riel)
input: Updates to Phantom Key Presses filter (credits to Christopher83)
SELinux: include definition of new capabilities (credits to Eric Paris)
msm: vidc: Check validity of userspace address (credits to Deepak Verma)
ALSA: pcm: check for integer overflow during multiplication (credits to Phani Kumar Uppalapati)
base: genlock: Zero a structure before sending it to user space (credits to Jordan Crouse)
qt602240_ts: updated touchscreen driver in according of Multi-touch protocol (credits to CastagnaIT)
20131116 ADCT GApps (DL from Dev-Host)
MD5SUM: 381d117be483cf672ac33887d212d765
Before you install CM11.0: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Here you can find the CWM Recovery and TWRP built by our Team:
WARNING: TO FLASH YOU MUST USE ONE OF THE RECOVERY OF THE TEAM... IT'S NOT AN OPTIONAL CHOICE!!!
>>>> CWM & TWRP Thread
WARNING: We built and tested these recoveries, but always remember that we are not responsible for any damage by using these software!!
They are based on safe kernel on emmc side!!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM10 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
WARNING: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM11.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM11.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Credits
CyanogenMod Team
Arco68 for his huge work for our device
AriesVE Dev Connection Team
Nello96 for Team logo's
anakin174 for the team spare phone
Sources
All our sources are on AriesVE-DevCon-TEAM GitHub
FAQ
For recovery bootloop problem you should at this post
BLNv9 feature recap:
It is activable/deactivable from BLN Control Application (Free or Pro version)
You can launch it from Settings->Device->Advanced
XDA:DevDB Information
[GT-I9001][KK 4.4.1] CyanogenMod 11.0 by ADC-Team - Kernel 3.4.x, a ROM for the Samsung Galaxy S I9000
Contributors
DevConnection_Team, smeroni68, CastagnaIT, Christopher83, educk, ivendor, krislibaeer, ktulu84, XeLLaR*
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-11-25
Last Updated 2013-12-21
Calibration of Magnetic/Orientation/Acceleration sensors
MAGNETIC / ACCELERATION / ORIENTATION SENSORS CALIBRATION
This procedure is necessary in case of ROM update and anyway when magnetic sensor has residual magnetism (so it do not give reliable readings).
CALIBRATION PROCEDURE:
1) Standard horizontal calibration through the CM advanced menu, by placing the phone over a flat and horizontal surface and pressing Calibrate touch button
2) Magnetic field calibration by following an 8 shape to be done as shown in this video: HOW TO CALIBRATE ELECTRONIC COMPASS
The calibration movement is a combined one over all axes, and will result in a residual magnetism removal (reset).
This calibration seems like a stupid game, but really this is the right way to recalibrate with a slow movement following the video shape; it is not important the direction to be used, just do once or more times until you get the calibration.
To know if the calibration has been done, you must know where is approximately the North and look with an app if the needle is pointing there; if yes, try rotating the phone of 90, 180, 270 and finally back to 360 degrees and look if the needle is pointing everytime to North during the rotation... If this easy test give positive results, your phone is calibrated!
Note1: After this procedure, the orientation and magnetic field sensors will give the correct values with all apps.
Note2: Our phone is known to have a native shift of some degrees respect to the North, but this is a hardware limitation due probably to the orientation of the chip welded on the board...
Note3: This procedure can be used also after a new flash of a compatible custom kernel or Rom in case of orientation not correct...
Reserved
F.A.Q - CyanogenMod 11
"The rom is stuck at splash screen, bootloop!"
-Use the NEWEST TWRP/CWM from US. Do not use any other recovery except the linked one in the thread!
"Is it PMEM or ION?"
- At the moment CM11 is based on PMEM. We are working on ION in the backround and it should be ready soon.
"I heard on KitKat the statusbar is transparent. Why not in this rom?"
We have enabled the low_ram token by default. This disables the transparent effects and saves ram. If you want the statusbar transparent, open your appdrawer and choose ariesparts. Now go to "Enable/Disable Low Ram" and press the switch button, reboot and done!
"Why I can't add widgets on lockscreen?"
We have enabled the low_ram token by default. This disables in general and depending on app some features to save ram. If you want to add widgets on lockscreen, open your appdrawer and choose ariesparts. Now go to "Enable/Disable Low Ram" and press the switch button, reboot and done!
"Where are the CyanogenMod settings (Battery styles etc..)?"
- CM11 is still WIP, build after build the settings will be there again.
"Will there be builds for the Galaxy W (same chipset)?"
-We dont know. When we finish the work on ION and have some free time, we will discuss about it.
"What is ART?"
First - ART is in the "DEVELOPER OPTIONS" for a reason!!
ART is the new selectable runtime virtual machine included in KitKat and intended to replace Dalvik VM in the future.
At the moment, the default runtime virtual machine (VM) on KitKat and the only one available on previous Android versions is Dalvik VM.
Apps, excluding their native parts, are compiled from Java source code (but also written with other high-level languages) to a particular intermediate-level language, called byte-code, architecture independent, portable and runnable on every system that has the same/similar runtime VM. When the app is launched, its various required byte-code parts are loaded from disk, interpreted by the VM, compiled in machine code and then stored in RAM ready for the real execution. This process (known as JIT, just-in-time) requires some time and is not so efficient in terms of execution performance and cpu use, expecially on a device with a single core cpu...
With ART runtime VM every app is compiled directly in machine code when downloaded from Play Store or during the first boot process after enabling this kind of VM.
This means that there's no need to compile again and again the app byte-code when an app is launched, less time required to launch the app, less cpu use, better performance.
At the moment, ART is in an experimental stage and not all apps are supporting it (they simply force closes when launched).
But in the future, this will be surely a second life for our device.
(Thanks to Christopher83 for this nice explaination!)
"Why does ART result in a bootloop?"
-The conversion from Dalvik to ART can take around 20 - 60 minutes, depending on how many apps you have installed. The bootanimation will be visible for a long time, so stay petient. BTW - If you installed Xposed framework ART will stop working.
"Why does ART result in app-fc`s?"
-Art is still very very alpha. In fact, there were people who wanted to remove it from the CM builds because of that, but it didnt happen. We recommend you to use Dalvik if you want to use this rom as daily driver.
"Are the DevCon-GApps odexed or deodexed?"
-The DevCon-GApps are made by XeLLaR*, he kept the odex files to let ART work for experiments. Long story short: odexed.
"Why are all browsers except for Opera and Chrome so laggy?"
-Google changed the native browser engine from WebKit to Chromium. This means only Chrome based browsers will work usable on CM11 till we update the rom from PMEM to ION.
"Gesture typing doesnt work?"
-AOSP Bug, please install Google Keyboard from the Playstore or as .apk. Also Swiftkey works correctly.
"Are 64GB Micro SD cards supported?"
-Yes, they are. Smeroni68 is using one in his phone, and it works very well. (Tested on native exFAT Samsung 64GB SDXC uhs1 PRO card)
"Where are the AriesParts/Advanced settings?"
-CyanogenMod has removed it from settings. You can find the Advanced settings inside the Appdrawer.
"Playstore doesn work after Upgrade to newer build of CM11!"
-Reinstall DevCon-GApps. You should do this everytime you flash a rom!
"When will you release the ION Roms?"
-As soon it is ready for public release and our tests are finished!
"MX-Player says "Not supported Android version"
Update MX-Player from market up to v1.7.21
"Where is the "Performance menu"?"
To add Developer Opitons & Performance menu, you have to open Settings -> Device Info and tap 7 time on Build Number.
"Where is the AOSP Calendar App?"
-Not longer present in AOSP,CM - use Google Calendar from Playstore, it looks exacly the same.
hmhm great! :] its pmem or ion?
Have fun with it guys!
P.S: Its PMEM
And thanks to Krislibaeer we included something very special and unique in the AriesParts.
You can switch between Android 4.4's Low Ram and Normal mode at any time.
The Low_Ram token sets a special mode where some features such as Transparent statusbar are disabled, but saving around 40-60MB Ram (depends on installed apps).
Gesendet von meinem GT-I9001 mit Tapatalk 2
Amazing work !! Thanks a lot !!
Amazing, thank you so much, will flash immidiately
Great work Team I wait a bit when the Rom will be more stable
Gesendet von meinem GT-I9001 mit Tapatalk
Performance are a little bit better than 4.2.2, i noticed no lag at all in UI. The problems are just the glitches included in OP, but it's really really nice for an alpha 1.
Also, little glitch in lockscreen if using PIN Unlock, but i think it's a source problem. Am I wrong or Cyano Team hasn't realeased a stable release for any device yet? You were so fast! Great guys, keep it up!
Thank you, I wait impatiently that the rom is stable.
Amazing !!!!! Thank you !!
Wysłane z mojego GT-I9001 przy użyciu Tapatalka
That's AWESOME !!!
Sent from my GT-I9001 using xda app-developers app
Cool. Thanks guys
Just wait for feedback from others - but I'm trying CM10.2 R1 for the next time before switching to this ^^
Wow. Such awesomeness
Immediate install, been waiting this eagerly :cyclops: I bet there'll be a stable release in a week, with such a dev team :highfive:
Nice to see these old devices ain't dead yet
Important features introduced in latest builds
Hi guys,
inside this first build you can find:
- Better memory management for our device that has a low amount of free memory (credits to Arco68 and krislibaeer)
- The touchscreen driver has been updated, it's no more a legacy touchscreen (credits to CastagnaIT)
- The old RIL class (phone and network data connection) has been replaced by SamsungExynos3RIL, more updated and supported by CM (credits to CastagnaIT)
- exFAT filesystems support (credits to radu)
- Phantom key filter module V2, updated to be more reliable when HOME key filtering is enabled, also with more permissive settings (credits to Christopher83)
- Low Ram switch inside AriesParts (credits to krislibaeer)
thank youuu!!!!
Big thanks to you guys!
It's really great, that KitKat is coming for our device but i was wondering what are the differences between Android 4.3.1 and android 4.4 according to S+
Compare both OPs then you will know
Also this are Alpha and CM10.2 are in Releasephase...
Cannot find Battery look and similar options that existed in 4.2.2? Any thoughts?
I DONT OWN P51xx, so use at OWN RISK !!!
{
"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"
}
AGNi pureCM v4.4
I/O schedulers: ROW, V(R), BFQ I/O schedulers, SIO, zen
CPU Governors ZZmoove, Interactive,hotplug
implemented CPU OC and GPU OC support (Default: 1GHz CPU, 307MHz GPU)
implemented CPU UV interface (Default: -50mV)
GPU undervolted for lesser heat (-75mV)
added "Westwood" TCP congestion control
Supports inbuilt AGNi Control app for all KERNEL CONFIGURATION
added 300MB Dual-Zram with LZ4 compression
preloadSWAP [enable/disable] via the app (Default: off)
X-Box XPAD support, Ralink & Realtek 8187 USB WiFI NICs support, Added USB Ethernet Support, USB GSM/CDMA Dongle support
cleancache, Zcache enabled
uses special busybox needed to support swap device priorities
kernel uses LZMA compression
Linux kernel 3.0.101
Implement SAMSUNG OSRC exFAT kernel support v1.2.5
PVR SGX540 [email protected] GPU driver
GCChf 4.8.3 linaro cortex-a9 optimised
Added 180 MHz lowest CPU scaling frequency
Introducing AGNi Main user profiles (Extreme Battery Save / Battery Save / Normal / Gaming) & user can override settings at will
drop & forget for init.d scripts (user doesnt need to set permissions manually)
Disabled lot of kernel debugging ( performance boost !)
internal & external SD read_ahead_kb values user tweakable
Implemented Power Saving CPU load balancer (sched_mc_power_savings), Implemented CPU boost driver
Implemented dynamic Fsync control v1.2 , Implemented frandom, tweaked "random" (the default linux kernel RNG/PRNG device), added Frandom option
(ANY CM11 OFFICIAL/UNOFFICIAL :victory::victory::silly: ) :-
==> Introducing my "ANYROM" kernel flash method AKA "Kernel Patcher-v4.3"
(Implementation of my old GALAXY ACE WORKS ) :-
It extracts the installed kernel boot.img from the device
It cracks it open to get the zImage and ramdisk
it extracts this old ramdisk
it removes any unwanted or conflicting elements with AGNi kernel (typically other custom CM kernel ramfs elements)
It adds/removes/patches the files on this extracted ramdisk as necessary
it packs this ramdisk and builds a new flashable boot.img using AGNi compiled zImage
It places its log at /data/.AGNi which is refreshed on each pureCM kernel install
This new boot.img is then flashed !!! Voila !
NB: you wont find any boot.img in this installer zip, dont freak out
also it wont work over non-standard structured boot.img kernels like the ones supporting dualboot so u need to reflash rom without wipe then flash this
THIS "ANYROM" INSTALLATION METHOD DIFFERS WITH "ANYKERNEL" AS IT HAS THE FLEXIBILITY TO MODIFY RAMFS CONTENTS AS REQUIRED
arm unaligned memory access, arch/arm/vfp: change compile flags - Neon & hard-float support ,ARM: Add optimised swahb32() byteswap helper | ARM-spinlock: use ticket algorithm for ARMv6+ locking implementation | ARM: L1 cache optimization | LMK minfree tweakable from AGNi Control and integrated with AGNi profiles | Proportional Rate Reduction for TCP | filter multicast packages while suspended
F2FS filesystem implementation ( /system /data /cache /preload automounted as ext4 or f2fs) | cfg80211: Fix memory leak | added sysrw & sysro | new compiled busybox v1.23 with expanded features (1.7MB sized at /sbin) | fix non boot on omni with f2fs | disabled background_gc for f2fs mounts | ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations | backport: smp: patches from mainline 3.5 to hopefully help with hotpluging | backport SLUB from Linux 3.3 (thanks to faux123)
added option to enable/disable on-boot filesystems checking (ext4/f2fs) log placed on internal storage | added option to delete battery stats on each boot | implemented AROMA GUI installer v2.70 RC2 | added option to set selinux permissive or enforcing
20-03-2014 Update v3.7 (CM11)
Rectify some cpu freq scaling issues & no more freezes on hotplug governor | removed cpuboost driver | tweaked some HOTPLUG tunables | set ROW/HOTPLUG as defaults | reduced F2FS active_logs from 6 to 2 | optimised FS_checker code | changed auto-installation method of AGNi Control app | [v3.7 R2: disabled Dynamic Fsync by default | set internalsd and externalsd read_ahead_kb to 512 & 1024 respectively | disabled some build.prop mods ] | [v3.7 R3: LMK updated | added ExternalSd USB UMS switching option | added all inbuilt Zzmoove v0.8 profiles | set zzmoove ZaneZam-Optimised profile as default with better hotpluging ]
17-04-2014 Update v3.9 (CM11)
mm/page_io: remove duplicated compressed pages in memory | logger: reduce reserved memory | cpufreq: Manage only online cpus | another round of debugging disabled , reverted some P3110 Jb Update 1 files (attempted fixing battery drain)
04-05-2014 Update v4.0 (CM11)
zram, zsmalloc, zcache, cleancache updated from 3.9 | updated lz4, lzo compressor/decompressor and crc32 algorithm | compiled by GCChf 4.9.1 linaro toolchain | reverted some commits | sync CM kernel updates (dm commits)
10-07-2014 Update v4.1 (CM11)
108 newer f2fs commits | 28 ARM specific commits | sync cm kernel sources | Implemented SLQB memory allocator | support for kernel mode NEON | arm/crypto: Add optimized AES and SHA1 routines | Enable ARCH_POWER | reduced active zrams to one and set 200MB default size | Zzmoove v0.9_beta2 | fs/exfat: update v1.2.5 to v1.2.7 (SAMSUNG OSRC SEA KK N7100XXUFND4) | Implement co-existing versions of SAMSUNG's sdcard filesystem - sdcardfs (Android 4.3 ) - sdcardfskk (Android 4.4+) | SAMSUNG OSRC SEA KK N7100XXUFND4 HID KK Updates | AGNi sdcard1<-->sdcard0 Switcher v1.3 (extsd2intsd replacement for CM using sdcardfs) | fixed Agni Control settings restore and added forced init.d execution option without reboot | fix derp arch/arm/mm/cache-l2x0.c | Fix CVE-2014-3153 | Boeffla-Sound: Engine 1.6.6 | Implement Update BFQ v6r2 -> v7r2 I/O sched | Introduce timer slack controller | fs: vfat: reduce the worst case latencies | Backport AIO from Linux 3.6.x | pegasusq modifications with firelock(default governor now) | backport Intelliactive cpu governor | bcmdhd: Enable wifi mac address changing | [ 15-07-2014 R2 : attempted fix memory related issues ]
17-07-2014 Update v4.2 (CM11)
video: sii9234: dynamically register and unregister input device | integrated dock keyboard support to kernel without module
01-11-2014 Update v4.3 (ALL AOSP)
True CD-ROM emulation" support | Implement USB HID Keyboard/Mouse ROLE support for Android device (https://github.com/pelya/android-keyboard-gadget) needs supported APK from HERE | drivers/cpufreq/cpufreq_lulzactiveq.c : set dual core mode and fix scaling (Andi) | ext4: remove some debugging functions by Samsung & sync with kernel.org | fs: default to noatime/nodiratime | Input: Send events one packet at a time | deadline: Allow 0ms deadline latency, increase the read speed | ZZmoove Version 1.0 beta1 | [PATCH] nohz: Fix update_ts_time_stat idle accounting (ZaneZam) | fs/exfat: update to v1.2.9 | Boeffla Sound v1.6.7| net: Performance fix for process_backlog | ext4: Speedup WB_SYNC_ALL pass called from sync | freezer: shorten freezer sleep time using exponential backoff | irq: Set CPU affinity right on thread creation | cpuidle: remove cross-cpu IPI by new latency request | nohz: Reduce overhead under high-freq idling patterns | ARM: smp: Wait just 1 second for other CPU to halt | timer: optimize apply_slack() | cpuidle: make a single register function for all | cpufreq: Fix policy stucking if user & kernel min/max don't overlap | cpuidle: Fix NULL pointer dereference during hotplug | Migrate to GCChf arm-cortex-a9 4.9.2 toolchain | ksm: check and skip page, if it is already scanned (Pradeep Sawlani) | ksm: Provide support to use deferred timers for scanner thread | Asynchronous I/O latency to a solid-state disk greatly increased | sdhci: deploy delay on host power down | mmc: Disregard pending irqs in sdio | ext4: Add support for FIDTRIM, a best-effort ioctl for deep discard trim | pegasusq: enable io_is_busy by default | bdi: allow block devices to say that they require stable page writes | ASoC: jack: Use power efficient workqueue | ASoC: pcm: Use the power efficient workqueue for delayed powerdown | ASoC: pcm: Use the power efficient workqueue for delayed powerdown | fbcon: queue work on power efficient wq | block: queue work on power efficient wq | PHYLIB: queue work on system_power_efficient_wq | workqueue: Add system wide power_efficient workqueues | workqueues: Introduce new flag | WQ_POWER_EFFICIENT for power oriented workqueues
29-11-2014 Update v4.4 (ALL AOSP)
Migrated to GCChf linaro 4.9.3 toolchain | attempted battery drain fix by 1N4148
Regarding AGNi sdcard1<-->sdcard0 Switcher when enabled:
- original sdcard0 obb data is available at /data/media/obb
- new sdcard1 obb data is available at /mnt/shell/emulated/Android/obb
- original sdcard1 userdata is available at /mnt/shell/emulated
you can move data between these as required.
KNOWN BUG:
Boeffla sound has minor incompatibily issue which makes its equalizer ineffective and its DAC-direct option needs to be kept ON for sound output
NOTE: CM 11 variant will set SELINUX PERMISSIVE
================================================================================
WHAT IS Flash-Friendly File System (F2FS)?
================================================================================
NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
been equipped on a variety systems ranging from mobile to server systems. Since
they are known to have different characteristics from the conventional rotating
disks, a file system, an upper layer to the storage device, should adapt to the
changes from the sketch in the design level.
F2FS is a file system exploiting NAND flash memory-based storage devices, which
is based on Log-structured File System (LFS). The design has been focused on
addressing the fundamental issues in LFS, which are snowball effect of wandering
tree and high cleaning overhead.
Since a NAND flash memory-based storage device shows different characteristic
according to its internal geometry or flash memory management scheme, namely FTL,
F2FS and its tools support various parameters not only for configuring on-disk
layout, but also for selecting allocation and cleaning algorithms.
FURTHER READING:
https://github.com/psndna88/AGNI-pu...-N7100-4.3/Documentation/filesystems/f2fs.txt
https://lwn.net/Articles/518988/
F2FS FORMAT TOOLS: http://d-h.st/users/psndna88/?fld_id=34001#files (formating /DATA with these will wipe your internal storage in single shot !)
EXT4 FORMAT TOOLS: http://d-h.st/users/psndna88/?fld_id=34000#files (formating /DATA with these will wipe your internal storage in single shot !)
PSN TWRP v2.7.0.x (F2FS Modified):-
P5100 : HERE
P511x : HERE
YOU HAVE TO USE F2FS supported kernel like AGNi for now
TWRP Drawbacks:
1: it doesnt ask which filesystem to format, but if u have ext4 previously, wiping that partiton is done in ext4 and same with f2fs, so u have to use above tools once atleast for partitons of ur choice
2: it doesnt support restore of ext4 backups to f2fs formatted partitions, so u have to clean wipe to fully convert to f2fs (titanium backup is ur best friend)
3: I SUGGEST MANUALLY COPYING INTERNAL STORAGE DATA TO PC and making titanium backups before trying to format /data to f2fs
4: to flash rom to f2fs formatted recovery you have to edit the updater-script and put a # before the "format" line and # before all unmount lines and manually mount system and data in twrp prior to flashing any zip. (i will post detailed updater-script modifications lateron)
5: on formatting /data to f2fs from ext4 or vice versa, twrp fails to mount /data, reboot to recovery again and all will be fine
App Screenshot: (v2.0)
About LZ4 compression/decompression:
LZ4 is a very fast lossless compression algorithm, providing compression speed at 300 MB/s per core, scalable with multi-cores CPU. It also features an extremely fast decoder, with speed in GB/s per core, typically reaching RAM speed limits on multi-core systems.
ADVANTAGE OF LZ4 OVER SNAPPY = higher speed with almost same marginal cpu usage for Zram
DOWNLOAD HERE v4.3+
NEWER CM11 VERSION (v4.2):
CLICK HERE
NEWER CM11 VERSION (v4.1_R2):
CLICK HERE
NEWER CM11 VERSION (v4.1) :-
CLICK HERE
OLDER CM11 VERSIONS (v3.3 to v4.0) DOWNLOAD :-
HERE
XDA:DevDB Information
AGNi Kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
psndna88
Kernel Special Features: Based on Cyanogenmod espresso10 Sources, upstreamed to 3.0.101 with selected picked mods/patches to be near to stock as possible.
Version Information
Status: Stable
Created 2014-07-10
Last Updated 2014-11-29
First
Cool, seems like quite lot of work..... I can't await to try
A question: I suppose both kernel and recovery are capable of either ext4 or f2fs, right?
tetakpatak said:
First
Cool, seems like quite lot of work..... I can't await to try
A question: I suppose both kernel and recovery are capable of either ext4 or f2fs, right?
Click to expand...
Click to collapse
correct.
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
Wonderful thanks for your hard work!
Freshly flashed TWRP and kernel, worked like a charm (P5110)
Kernel works lovely with Andi's Omni unofficial, feels fast and smooth
tetakpatak said:
Wonderful thanks for your hard work!
P.S. please just add something like "kernel" before download link on the bottom, I nearly didn't find it. All files downloaded now!
---------- Post added at 04:30 PM ---------- Previous post was at 03:43 PM ----------
Freshly flashed TWRP and kernel, worked like a charm (P5110)
Kernel works lovely with Andi's Omni unofficial, feels fast and smooth
Click to expand...
Click to collapse
u were the first tester and it works
EXPLORE THE FIRE APP
CHECK THIS OUT:
AUTO DETECTING (PRE-BOOT) INTELLIGENT FILE SYSTEMS CHECKER LOG:-
Code:
################################################
AGNi FS_CHECKER LOG
################################################
DATED: Mon Mar 17 16:36:35 UTC 2014
/system EXT4 CHECKING....
1846 inodes used (2.06%)
18 non-contiguous files (1.0%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1534
130832 blocks used (36.50%)
0 bad blocks
0 large files
1445 regular files
88 directories
0 character device files
0 block device files
0 fifos
0 links
304 symbolic links (304 fast symbolic links)
0 sockets
--------
1837 files
/data F2FS CHECKING....
F2FS-tools: fsck.f2fs Ver: 1.3.0 (2014-02-06)
Info: sector size = 512
Info: total sectors = 25280478 (in 512bytes)
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x1dc4bd]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x1364]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x1364]
[FSCK] valid_inode_count matched with CP [Ok..] [0xb4e]
Done.
/cache F2FS CHECKING....
F2FS-tools: fsck.f2fs Ver: 1.3.0 (2014-02-06)
Info: sector size = 512
Info: total sectors = 1433600 (in 512bytes)
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x11]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x9]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x9]
[FSCK] valid_inode_count matched with CP [Ok..] [0x6]
Done.
/preload F2FS CHECKING....
F2FS-tools: fsck.f2fs Ver: 1.3.0 (2014-02-06)
Info: sector size = 512
Info: total sectors = 1048576 (in 512bytes)
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x2]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x1]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x1]
[FSCK] valid_inode_count matched with CP [Ok..] [0x1]
Done.
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
Now I'm going to flash it
Inviato dal mio GT-P5110 utilizzando Tapatalk
Sammy854 said:
Now I'm downloading... But can I flash it using the Andi's unofficial twrp?
Inviato dal mio GT-P5110 utilizzando Tapatalk
Click to expand...
Click to collapse
yes but if u have f2fs formtted partition(s) it wont mount, this does it
(these recoveries are andi's recoveries , modified slightly)
psndna88 said:
u were the first tester and it works
Click to expand...
Click to collapse
LOL cool
I have no fear of testing kernel.
With self-made bootloader, you would wait for me long
BTW don't you own a P51xx?
tetakpatak said:
LOL cool
I have no fear of testing kernel.
With self-made bootloader, you would wait for me long
BTW don't you own a P51xx?
Click to expand...
Click to collapse
i have only P3100 & I9300
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
I cant use this kernel with omni unofficial rom too many system.ui force close back to Dhollmen kernel
Sent from my GT-P5113 using XDA Premium 4 mobile app
@psndna88
Working great here.
Shalom and well done , john. (P5110)
Sent from my GT-P5110 using XDA Premium 4 mobile app
Ok to try with CM11 M4 from Andi??? Very curious and interested. Either way, thanks much for your efforts. Looks as if we have another awesome dev out there keeping the dream alive.
EDIT: Went for it. 1st thing I noticed was that I can not change governor or increase speed. Stays on Interactive and 1008. Maybe I am missing something. I'll play around for a bit and see. Thanks to psndna88 again.
Mine is P5110 btw
EDIT #2 Going back to Dhollmen. I gotta stay with the known for now. Thanks again
Wow, it works very well with Omni ROM (I'm using the 20140308 build of Omni by Andi) :good:
I have a P5113 and the 180MHz clock works fine. One nice surprise is my OTG cable works now with this kernel. Even ExFAT USB drives work. I'll have to try formatting F2FS and re-installing later.
What does the AGNi Control app do, and is there a guide?
ADB in recovery....
@psndna88
There is no ADB connection in the recovery mode with this TWRP version.
The reason is, that your F2FS recovery version is based on the TWRP 2.7.0.0 ported by @Android-Andi, and strangely, there was also no ADB connection in recovery mode on the P5110 Tab in 2.7.0.0 and 2.7.0.1. But Andi has just figured out half hour ago where to search for the problem, he might find it very soon now.... and if we kindly ask him...
I see now that for migration to F2FS nandroid backups made with ext4 can not be restored in F2FS. I will repack the zip when I am less tired then, I had a hard day. I can't await to see what it does. Is your P3100 rapidly faster with F2FS?
Stuck on boot animation with CM11 Nightly 3/18, back to Dhollmen Kernel here.
Sent from my GT-P5113 with XDA Premium HD app
CSP III said:
Ok to try with CM11 M4 from Andi??? Very curious and interested. Either way, thanks much for your efforts. Looks as if we have another awesome dev out there keeping the dream alive.
EDIT: Went for it. 1st thing I noticed was that I can not change governor or increase speed. Stays on Interactive and 1008. Maybe I am missing something. I'll play around for a bit and see. Thanks to psndna88 again.
Mine is P5110 btw
EDIT #2 Going back to Dhollmen. I gotta stay with the known for now. Thanks again
Click to expand...
Click to collapse
use agni control app.. easy n simple..
ron12 said:
Wow, it works very well with Omni ROM (I'm using the 20140308 build of Omni by Andi) :good:
I have a P5113 and the 180MHz clock works fine. One nice surprise is my OTG cable works now with this kernel. Even ExFAT USB drives work. I'll have to try formatting F2FS and re-installing later.
What does the AGNi Control app do, and is there a guide?
Click to expand...
Click to collapse
agni control app is to tweak most kernel aspects
.. not made guide yet but its simple to use
BlackRenegade said:
Stuck on boot animation with CM11 Nightly 3/18, back to Dhollmen Kernel here.
Sent from my GT-P5113 with XDA Premium HD app
Click to expand...
Click to collapse
u should flash it over rom and not over a pre-flashed custom kernel.
u can reflash rom without wipe then gapps then this kernel.
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
tetakpatak said:
@psndna88
There is no ADB connection in the recovery mode with this TWRP version.
The reason is, that your F2FS recovery version is based on the TWRP 2.7.0.0 ported by @Android-Andi, and strangely, there was also no ADB connection in recovery mode on the P5110 Tab in 2.7.0.0 and 2.7.0.1. But Andi has just figured out half hour ago where to search for the problem, he might find it very soon now.... and if we kindly ask him...
I see now that for migration to F2FS nandroid backups made with ext4 can not be restored in F2FS. I will repack the zip when I am less tired then, I had a hard day. I can't await to see what it does. Is your P3100 rapidly faster with F2FS?
Click to expand...
Click to collapse
lets see when its fixed...
i get better write performance with f2fs
psndna88 said:
use agni control app.. easy n simple..
Sorry....I could find this where??? Would like to give it another go.
Click to expand...
Click to collapse
CSP III said:
psndna88 said:
use agni control app.. easy n simple..
Sorry....I could find this where??? Would like to give it another go.
Click to expand...
Click to collapse
it should be auto installed ...
in case its not auto installed, install the two apks present in data/app folder in the installation zip.
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
Click to expand...
Click to collapse
psndna88 said:
CSP III said:
it should be auto installed ...
in case its not auto installed, install the two apks present in data/app folder in the installation zip.
Didnt notice it, but installed apks anyways. Right on, much much thanks. Very Nice!!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Dear Galaxy Ace 3 LTE users, yesterday succesfully compiled CM11 for our beloved device! Credits go to @szezso for his device tree and @TheWhisp for his cwm 6.0.4.9 recovery that is able to install kit-kat roms
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Click to expand...
Click to collapse
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
All you questions here: Q&A! This is a development Thread
Click to expand...
Click to collapse
BUGS
-NFC
-If using OTG reboot after finishing using it, because a wakelock occurs
-You might have random reboots sometimes
Click to expand...
Click to collapse
WORKING
-Everything Else!
Click to expand...
Click to collapse
Code:
Link to the cwm recovery needed: [url]http://d-h.st/pak[/url]
Code:
Latest Release is [COLOR="Red"]20160820[/COLOR]!
[URL="https://www.androidfilehost.com/?fid=24591000424956016"]Download[/URL]
Screenshots
{
"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"
}
INSTALLATION
Enter download mode (Volume Down + Home + Power Button)
Install cwm recovery given above via odin v3.0.9 (put it in AP place WITHOUT auto reset option enabled)
when finished press and hold Vol Up + Home + Power Button to enter recovery mode without turning off the device
Wipe data factory reset
Install zip from sdcard/extsdcard --> choose zip from sdcard/extsdcard --> cm-11-XXXXXXXX-UNOFFICIAL-loganreltexx.zip
Reboot system now
Click to expand...
Click to collapse
Video - How to install
Click to expand...
Click to collapse
Code:
ENABLE ART(need fresh install)
1. Reboot into recovery mode
2. Wipe data, cache and dalvik cache
3. Format /system partition
4. Flash cm11
5. Reboot
6. Enable ART
7. Reboot into Recovery
8. Flash Gapps
9. Reboot
Code:
If you experience problems with wi-fi:
All you have to do is to set country code to your country in Wi-Fi settings
If you experience problems with any external applications try switching from ART to DALVIK before asking or sending a private message
Click to expand...
Click to collapse
If you have random reboots, this is the solution that is reported to solve the problem, thanks @mohamed786
Click to expand...
Click to collapse
All the builds will be hosted here: Download
***Mirroring my ROM and builds is not appreciated***
Click to expand...
Click to collapse
Video Preview
Thanks @AeroMiku
Another video preview
Click to expand...
Click to collapse
Thanks list
@arco68
@TheWhisp
@mir3k
@Rox
@faux123
@CM team of course,
without all this help and contribution, I wouldn't have done almost anything
*If I forgot someone, excuse me, send me a pm, and I will add you
Donate to those guys if you can. They helped me a lot, especially arco
Click to expand...
Click to collapse
Official facebook page: Page
Click to expand...
Click to collapse
Code:
Releases:
[COLOR="Red"]-20160820-[/COLOR]
*CM sources update
*August security patch level
*Kernel: HID: hiddev: validate num_values for HIDIOCGUSAGES, HIDIOCSUSAGES commands (CVE-2016-5829)
*Kernel: net: ipc_router: Bind only a client port as control port (CVE-2016-2059)
*Kernel: msm: kgsl: Defer adding the mem entry to a process (CVE-2016-2504)
*Kernel: ashmem: Validate ashmem memory with fops pointer (CVE-2016-5340)
*Kernel: msm: board-8930-pmic: Remove PMIC LED driver
*Kernel: msm: Fix bus vector for DFAB clk setting
[COLOR="Red"]-20160107-[/COLOR]
*CM sources update
*Latest android security patch level(2016-01-01)
[COLOR="Red"]-20151113-[/COLOR]
*CM sources update
*More security patches brought by Cyanogen
[COLOR="Red"]-20151110-[/COLOR]
*CM sources update
*Security patches from Cyanogen
*rootdir: init.target.rc: update sensors from stock ramdisk
*rootdir: Remove read ahead tunings
[COLOR="Red"]-20150824-[/COLOR]
*Include custom Kernel
*Kernel: Re-implemented kexec hardboot
*Kernel: Fixed last_kmsg
[COLOR="Red"]-20150814-[/COLOR]
*CM sources update
*Patches for stagefright vulnerability
*Kernel: Support for kexec hardboot
*Kernel: Add Fiops i/o scheduler
*Kernel: Add smartmax_eps cpu governor
[COLOR="Red"]-20150701-[/COLOR]
*CM sources update
*Fix compass
*Cleanup init.qcom.power.rc for unnecessary stuff
*Update interactive governor values
*Kernel: Misc patches
[COLOR="Red"]-20150501-[/COLOR]
*CM sources update
[COLOR="Red"]-20150424-[/COLOR]
*CM sources update
*Remove hdpi from PRODUCT_AAPT_CONFIG
*Disable cpu.notify_on_migrate feature
*Enable mpdecision by default
*Kernel: Misc patches
[COLOR="Red"]-20150324-[/COLOR]
*CM sources update
*Web security patches applied
*Kernel:Misc patches
[COLOR="Red"]-20150320-[/COLOR]
*CM sources update
*Remove setting permissions for non-existent fmradio dev
*Enable separated headset mic
*Update snd_soc_msm_2x
*Drop NFC support
*Kernel: Avoid some memleaks
*Kernel: Misc patches
[COLOR="Red"]-20150312-[/COLOR]
*CM sources update
*Revert: "Move custom AAPT config to cm.mk"
[COLOR="Red"]-20150308-[/COLOR]
*CM sources update
*msm8930-common: camera: Modify base.common.version API define
*Re-enable QCOM's HW AAC encoder
*Kernel: Fix QCOM's HW AAC encoder
*Revert "rootdir: Create native cgroup"
[COLOR="Red"]-20150305-[/COLOR]
*CM sources update, mostly translations
*Fixed camcorder
[COLOR="Red"]-20150228-[/COLOR]
*Enable QCOM's HW AAC encoder"
*Disable LPA
*Set default country index to Europe in FM app
*Create native cgroup
*Move custom AAPT config to cm.mk
*Kernel: Tune voltage table
*Kernel: Misc patches
[COLOR="Red"]-20150219-[/COLOR]
*CM sources update
*Kernel: Re-add intelliactive cpu governor
*Kernel: Re-add sio i/o scheduler
*Kernel: Probably fixed random reboots
*Kernel: eCryptfs: Remove buggy and unnecessary write in file name decode routine
*Kernel: Νetfilter: conntrack: disable generic tracking for known protocols
[COLOR="Red"]-20150120-[/COLOR]
*CM sources update
*Revert: Remove chmod of /proc/cmdline
*Kernel: Optional overclock up to 1.7GHz
*Kernel: Update intelli_plug to v3.9
*Kernel: Add intellimm cpu governor
*Kernel: Misc patches
*Fix encryption after factory reset
[COLOR="Red"]-20150102-[/COLOR]
*CM sources update
*Disable QCOM's HW AAC encoder
*Disable audio offload
*Update media_profiles
*Fix: Now audio from videos plays on both sides of headphones/speaker
[COLOR="Red"]-20141225-[/COLOR]
*CM sources update
*Don't show mobile plan preference
*Load fastrpc module after boot
*Minor cleanup in init.carrier.rc
*Move wcd9310 symlink creation to msm8930-common
*msm8930-common:Create wcd9310 symlinks during build process
*Enable smooth-streaming video-playback
*Don't mount persdata
*Revert: Enable large heap for Trebuchet
*Minor kernel patches
[COLOR="Red"]-20141205-[/COLOR]
*CM sources update
*Remove qrngd service
*Add SettingsProvider
*Update ueventd.qcom.rc
*Minor cleanup of init.qcom.rc
*Enable large heap for Trebuchet
*Fix hostapd service to use correct config folder
*Remove chmod of /proc/cmdline
*Change NTP_SERVER in gps.conf to use izatcloud
*Set default locale to en_UK
*Remove obsolete option
*msm8930-common:Cut EGL cache size in half
*msm8930-common:Define correct path to hostapd files
*msm8930-common:Some camera wrapper cleanup and changes
*msm8930-common:Disable CCX support in Prima config
*msm8930-common:Remove unused option from camera makefile
*Many kernel patches
[COLOR="Red"]-20141125-[/COLOR]
*CM sources update
*Increase read ahead to 512KB
*Revert: Enable face detection
*Revert: Change ADCBID for PROXY Rx
*Revert: Loganre: Enable proximity wake option
*Disable interactive governors sync_freq feature
*Add back couple of missing lines in media_codecs.xml
*Disable wpa_supplicant log spam
[COLOR="Red"]-20141115-[/COLOR]
*CM Sources update
*Added Binaries for IPv6 tethering
*Fixup input paths
*Removed Fauxsound, it caused calling bug
*Fixed FM Radio
*Updated media codecs
[COLOR="Red"]-20141112-[/COLOR]
*CM Sources update
*Use bottom mic for speaker phone
*Change ACDBID for PROXY Rx
*Enable face detection
*Audio config improvements
*Fixed audio playback
*Wlan: prima: Sync with kk_2.7
*Milestone M12 release
[COLOR="Red"]-20141107-[/COLOR]
*CM sources update
*Ramdisk updates
*GPS config improvements
*GPS HAL improvements
*Move power management to a separate init.qcom.power.rc
*Revert:add VR headset to use case, it was breaking mic on phone calls in my tests
*Official toolchains used
[COLOR="Red"]-20141102-[/COLOR]
*CM sources update
*Kernel: Reduced max OC for both CPU(1.5GHz) and GPU(475MHz) for safety
*fixed "com.qualcomm.timeservice has stopped"
[COLOR="Red"]-20141101-[/COLOR]
*CM sources update
*fstab updates, now you can mount USB-OTG without a 3rd party app (EXT4 filesystem tested)
*re-enabled triple framebuffer
*audio/snd_soc_msm_2x: Add VR headset use case
*Disabled mpdecision service, we have intelliplug
[COLOR="Red"]-20141028-[/COLOR]
*CM Sources Update
*Kernel:Add Fauxsound, thanks @Paul
*Kernel:Squashed update of wifi regulatory database
*Kernel:CPUfreq Updates
*Overlay cleanup
*Add some blobs
*Enabled GPS XTRA servers
*Camera HAL code cleanup
[COLOR="Red"]-20141023-[/COLOR]
*CM Sources Update
*Finally stock camera rotation bug is FIXED!!!, thanks Arne Coucheron, Abhisek Devkota
*Removed AGPS_USE_PSC from GPS HAL again
*Build.prop updates
*Kernel: Add GPU OC up to 627 MHz including stock frequencies this time
*Kernel: Add Intelli_plug hotplug driver as well as msm_hotplug, credits @Faux123
[COLOR="Red"]-20141020-[/COLOR]
*CM Sources Update
*Changed Network buffer sizes from stock
*Kernel: Manage Offline CPUs
*Add USB_OTG back to storage menu
*Add USB-OTG support in kernel (Needs testing, for undesired wakelocks)
*Some kernel update
*Reverted Some GPS HAL changes
[COLOR="Red"]-20141017-[/COLOR]
*CM Sources Update
*Correct cpu voltage table in kernel
*Added Underclock again up to 162 MHz
*Increased Overclock limit up to 1.7 GHz
*Removed USB-OTG from storage menu
*Device tree cleanup/update
[COLOR="Red"]-20141010-[/COLOR]
*CM Sources Update
*Revert: KSM enabled by default
*M11 milestone release
*msm8930-common: camera: Don't forcefully enable ZSL
*Add Overclock: 1.24 GHz, 1.35 GHz, 1.45 GHz
*Added SmartassV2, Intelliactive CPU governors
*Added sio and sioplus I/O governor
[COLOR="Red"]-20141007-[/COLOR]
*CM Sources Update
*Fixed Superuser settings force close
*Fixed Terminal Emulator force close
*Kernel Downgrade to 3.4.0, it should be more stable
*Kernel is built with Linaro 4.7 now
*Update Camera HAL API (arco)
-Features still present in kernel:
*Change readahead to 512kB.
*Voltage Control
*Optimize KSM
*USB Fastcharge
-Features removed from kernel(due to perfomance issues and stability):
*GPU Overclock
*GPU Optimizations
*Graphite Kernel Optimizations
*O3 Kernel Optimizations
*Cortex A15 Optimizations
[COLOR="Red"]-20141005-[/COLOR]
*CM Sources Update
*Kernel Update up to 3.4.103, thanks @F4k
*Remove useless dual sim stuff from ramdisk
*GPU Overclock up to 627 Mhz (Be careful)
*GPU Optimizations
*CPU Voltage Control (Be careful)
*Enable KSM by default
*Many, many Kernel Updates
*Graphite Kernel Optimizations
*-O3 Kernel Optimizations
*Change Kernel readahead to 512KB
*Optimize Kernel SamePage Merging
*Cortex A15 Optimizations
*Kernel compiled with Linaro 4.9.2 now
*Usb Fastcharge support
*More, more and more
[COLOR="Red"]-20141003-[/COLOR]
Changelog:
*CM Sources Update
*Fix in liblights
*Kernel was built with Sabermod 4.7.4 toolchain
*Updated Recovery (CWM 6.0.5.1)
[COLOR="Red"]-20140930-[/COLOR]
Changelog:
*CM Sources Update
*Updated Build Fingerprint From Latest Stock Rom
*Updated fstab
*Add Missing Device Permissions
*Kernel Update
*Overlay Sar Levels(Settings->About Phone->Status->SAR Levels)
[COLOR="Red"]-20140919-[/COLOR]
Changelog:
*CM sources update
*Kernel Updates
*Adreno libs update
[COLOR="Red"]-20140916-[/COLOR]
*CM sources update
*Adjustments to power HAL
*CyanogenMod M10
[COLOR="Red"]-20140913-[/COLOR]
Changelog:
*CM sources update
*Kernel Updates
*Wifi Driver Update
[COLOR="Red"]-20140910-[/COLOR]
Changelog:
*CM sources update
*Update Ramdisk
*Add Support for GT-S7275T
*Allow more background services
*msm8930: Enable triple framebuffer
[COLOR="Red"]-20140904-[/COLOR]
Changelog:
*CM sources update
*Fixed Missing Preferred Network type under Network Settings
*msm8930-common: Merge in some wifi config changes from stock KK
[COLOR="Red"]-20140903-[/COLOR]
Changelog:
*CM sources update
*Some Kernel Update
[COLOR="Red"]-20140901-[/COLOR]
Changelog:
*CM sources update
*Updated GPS config
*Fixed WMA audio files playback(Apollo couldn't play .wma files)
[COLOR="Red"]-20140831-[/COLOR]
Changelog:
*CM sources update
*Massive KitKat Blobs Update from Express 2 and Serrano
*Added missing OMX decoder
*Stability should be increased
*Reworked GPS (arco)
*Add Support for GT-S7275B
[COLOR="Red"]-20140829-[/COLOR]
Changelog:
*CM sources update
*Modified Stock Power Profiles to fit our device(corrected cpu states and more)
[COLOR="Red"]-20140827-[/COLOR]
Changelog:
*CM sources update
[COLOR="Red"]-20140823-[/COLOR]
Changelog:
*CM sources update
*Added Soft Reboot option in Reboot options
[COLOR="Red"]-20140818-[/COLOR]
Changelog:
*CM sources Update
*Fixed mic on loudspeaker while calling again
*CM sources update
[COLOR="Red"]-20140816-[/COLOR]
Changelog:
*CM sources update
[COLOR="Red"]-20140813-[/COLOR]
Changelog:
*New Kernel Config, should improve some things, thanks @arco68
*Removed SmartassV2 governor, reported to use highest frequency all the time
*CM sources update
*Device tree update from @arco68
*Added Blobs from stock ANF2 firmware, thanks @arco68
*Added Google Camera in build, camcorder lag should disappear
*Use stock ANF2 ril blobs, should improve network
*Audio improvements by @arco68
[COLOR="Red"]-20140806-[/COLOR]
Changelog:
*Probably fixed MMs again, need testing and feedback
*CM Sources Update
[COLOR="Red"]-20140801-[/COLOR]
Changelog:
*CM sources update
*Removed USB OTG due to wakelock bug
[COLOR="Red"]-20140724-[/COLOR]
Changelog:
*CM source Updates
*Fixed missing option from storage settings: Unmount SDcard
[COLOR="Red"]-20140721-[/COLOR]
*CM sources update
*Kernel Changes, now camera seems a little more stable to me
[COLOR="Red"]-20140719-[/COLOR]
Changelog:
*Voip Fix
*CM source Updates
*Kernel Sources Update
Add Dock Headset to audio policy
[COLOR="Red"]-20140716-[/COLOR]
Changelog:
*Using custom power HAL (Should improve battery)
*CM sources update
*Audio config improvements and cleanup
Sources
Device Source: https://github.com/kostoulhs/android_device_samsung_loganreltexx
Kernel Source: https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0_mod
Click to expand...
Click to collapse
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=2397942"]GAPPS[/URL]
Code:
If you like it, give me a thanks :)
Wifi Working
kostoulhs said:
Dear Galaxy Ace 3 LTE users, yesterday succesfully compiled CM11 for our beloved device! Credits go to @szezso for his device tree and @TheWhisp for his cwm 6.0.4.9 recovery that is able to install kit-kat roms
ROM IS BETA, fixes needed!
WORKING
Ril
Bluetooth
Data (I think there is an issue, but seems to work)
FM radio
BUGS
Camera
Wifi
NFC
Auto-rotate
You tell me
link to the cwm recovery needed: https://www.dropbox.com/s/wluzefvek281x8n/cwm-6.0.4.9-loganre.tar.md5
Link to the rom if you wanna test: https://drive.google.com/file/d/0B7Bqo5x_z18ENjl2V1hfM0pic28/edit?usp=sharing
INSTALLATION
Enter download mode (Volume Down + Home + Power Button)
Install cwm recovery given above via odin v3.0.9 (put it in AP place WITHOUT auto reset option enabled)
pull out battery when finished
Enter recovery mode (Vol Up + Home + Power Button)
Wipe data factory reset
Install zip from sdcard --> choose zip from sdcard --> cm-11-XXXXXXXX-UNOFFICIAL-loganreltexx.zip
Reboot system now
PS: I am not responsible for any damage to your device
Click to expand...
Click to collapse
Wifi working! Thanks mir3k from github https://mega.co.nz/#!80kh3S5A!-5UDhZ9931RS44eCVqBvvTmZ1vXcPpgvyye1smwx3MQ
kostoulhs said:
Wifi working! Thanks mir3k from github https://mega.co.nz/#!80kh3S5A!-5UDhZ9931RS44eCVqBvvTmZ1vXcPpgvyye1smwx3MQ
Click to expand...
Click to collapse
Hey, I have some questions.
1. For wich models is it?
2. Gapps?
3. Exactly version of Kit-Kat?
4. Who is the developer of this ROM?
5. How to enable/disable ART?
Answers
Arcanister99 said:
Hey, I have some questions.
1. For wich models is it?
2. Gapps?
3. Exactly version of Kit-Kat?
4. Who is the developer of this ROM?
5. How to enable/disable ART?
Click to expand...
Click to collapse
1) For GT-S7275R
2) http://www.devfiles.co/download/7m2VdVjQ/gapps-kk-20140105-signed.zip
3) Android 4.4.4
4) Device tree originaly created by @szezso , then modified a little by me and another guy from github, compiled by me and the guy from git
5) About phone --> tap 5 times on "Build number", then "Developer options" should be enabled. After that --> "Developer options" all the way down you will see "Select Runtime" tap on it and select ART, the phone will reboot
You need CWM provided
kostoulhs said:
1) For GT-S7275R
2) http://www.devfiles.co/download/7m2VdVjQ/gapps-kk-20140105-signed.zip
3) Android 4.4.4
4) Device tree originaly created by @szezso , then modified by a little by me and another guy from github, compiled by me and the guy from git
5) About phone --> tap 5 times on "Build number", then "Developer options" should be enabled. After that --> "Developer options" all the way down you will see "Select Runtime" tap on it and select ART, the phone will reboot
Click to expand...
Click to collapse
PS: you need provided CWM because mahound's cwm can't install kitkat roms
Can you link me to your sources ? I wanna help you in developmet
https://github.com/kostoulhs/android_device_samsung_loganreltexx or https://github.com/mir3k/android_device_samsung_loganreltexx-1
Thanks to them
That's cool
Rox said:
Can you link me to your sources ? I wanna help you in developmet
Click to expand...
Click to collapse
Those repo's given are the used ones, actually they are the same
Camera Issue
UPDATE
Camera issue almost resolved (there are some errors and also crashes in video mode)
Big thanks @mir3k
GPS issue also resolved
Thanks @mir3k for the hard work and tests
kostoulhs said:
GPS issue also resolved
Thanks @mir3k for the hard work and tests
Click to expand...
Click to collapse
Cool. Post 1 Rom link broken for me. One further down worked though.
Compiling one new right now
Houndcatcher said:
Cool. Post 1 Rom link broken for me. One further down worked though.
Click to expand...
Click to collapse
My pc is too weak to compile fast so compilation takes about 6-8 hours when it finishes i will upload new build
Houndcatcher said:
Cool. Post 1 Rom link broken for me. One further down worked though.
Click to expand...
Click to collapse
Here it is : https://drive.google.com/file/d/0B7Bqo5x_z18EQ3FPWjl3UUF1ZzQ/edit?usp=sharing
kostoulhs said:
Here it is : https://drive.google.com/file/d/0B7Bqo5x_z18EQ3FPWjl3UUF1ZzQ/edit?usp=sharing
Click to expand...
Click to collapse
Installed.
Houndcatcher said:
Installed.
Click to expand...
Click to collapse
A first performance feedback ?
wechstef said:
A first performance feedback ?
Click to expand...
Click to collapse
Not played with it much yet as I've been working and it's not my main phone but it seems OK. I will give it a good run over this weekend :good:
wechstef said:
A first performance feedback ?
Click to expand...
Click to collapse
A friend of mine has it and he told me that it's good. However, after some weeks it gets laggy
Enviado desde mi GT-S7275R usando Tapatalk 2
Huge update
Fixed Camera and Camcorder but it may get laggy sometimes
kostoulhs said:
Fixed Camera and Camcorder but it may get luggy sometimes
Click to expand...
Click to collapse
Uploading now... :laugh:
Based on new device tree
Now both cameras work! Device tree can be found here: https://github.com/kostoulhs/android_device_samsung_loganreltexx
Download link: https://drive.google.com/file/d/0B7Bqo5x_z18EemxFcGJfZUQ0ZkU/edit?usp=sharing
:laugh: :good: :victory:
Wipe Data after flashing
About AnyKernel:
AnyKernel is a template for an update.zip that can apply any kernel to any ROM, regardless of ramdisk. -Koush
The concept of AnyKernel has been around for awhile, (originally by Koushik Dutta/ClockworkMod,) which allowed a device-specific kernel zImage to be flashed over device-specific ROM and use the ramdisk that came with the ROM to reduce the chance of any issues arising from the custom kernel pairing.
Jelly Bean:
Jellybean kernel can used to all Jellybean based ROM like AOSP, MIUI, Lewa, Etc
3.4.5 Jelly Bean kernel by @kirito9:
Features:
1) Added Governers
2) Added Double tap to wake
3) Added Sweep to wake
4) Many more
Link:
https://mega.nz/#!S4cAzY7Q!Mxr6zwbTUnbpH3QZA8jhOlgWh6WIQketaiJ08Ci7G3M
3.4.5 OverClocked Jelly Bean kernel by @chijure:
Features:
1) Based on the STOCK Source OT_4015D_20140610.tar.xz from Alcatel
2) Toolchain: Built with GCC 5.2 toolchain from Linaro
3) Linux: 3.4.5
4) CPU OC: Up to 1.4GHz
5) Thunder Sonic Sound Control Engine
6) Thunder Charge Fast Charge Driver
7) Thunder Quake Engine 1.0 - Vibration Intensity Controller for MTK vibrators
8) Swap
9) KSM: Kernel Same-page Merging enabled
10) Dynamic management of dirty page writeback
11) Dynamic Fsync: Faux123's Dynamic File Sync v1.5
12) Sweep2wake
13) Doubletap2wake
14) Lowered swappiness (60 -> 70)
15) Optimized AES and SHA1 routines for ARM cpu architecture
16) Optimized SLUB memory allocator
17) Enabled arch power
18) Disabled CRC check in MMC for 30% extra performance with IO
19) Block:
•Added SIO IOScheduler
•Added BFQ IOScheduler
•Added fiops scheduler
20) Disabled Gentle fair sleepers
21) NOATIME and NODIRATIME
22) Dynamic management of dirty page writebacks
23) Mali:
•GPU cache Optimizations
•Increase L2 cache max read size
•Disable state tracking
•Reduce GPU utilization timeout
•Increase kernel memory buffer size
24) Additional Governors:- SmartassV2
25) Additional I/O Schedulers:
•NOOP
•BFQ
•FIOPS (by default)
•SIO (SImple Ondemand)
Link:
https://mega.nz/#!C99z3JQR!7ECpzlgKzjWSY11ayCAbqLw-tIzRlHlv9PyZOxStu6I
KitKat:
KitKat kernel can used to any KitKat ROM such as AOSP, MIUI, CM 11. This kernel also used in Lollipop ROM such as CM 12.1 and CM 12.1 Based ROM. Also used in Marshmallow ROM such as CM 13.0 and CM 13.0 based ROM and AOSP 6.0.1 ROM. This not used in MTK based 5.1 Lollipop ROM
3.4.113 OverClocked KitKat kernel by @getakgt1:
Features:
1) Upstreamed to 3.4.113
2) OverClocked to 1.4GHZ
Link:
https://mega.nz/#!3pl2FJqR!zD4UnHbt16CVqsot3uqULTaANCWW4FK4ubmyKO5NwNM
Instructions:
1) Download any kernel zip
2) Place it in SDCard
3) Reboot to recovery
4) Flash Zip
5) Reboot to system
6) Done
Credits:
1) @kirito9
2) @chijure
3) @getakgt1
4) Team Dev Pop
5) GETAKGT1
6) Team Panther
7) @osm0sis
8) @Koush