Hi, I wanted to try something for the Galaxy Player 4.0. I know that the hummingbird processor inside of it had a lot of potential and I want to extract all the power it has to offer . To do so I had to use any tools that could help me achieve that objective . Now enough with the talk and more with the actual content of this kernel. Note that this kernel works for both versions (US and Intl, Korea can work but it hasn't been tested).
Disclaimer: This is a MTD kernel, it will only work with CM based ROMS (CM10.1 and up). Flashing it in a GB ROM could result in a brick, Also I'm not responsible to any bricks caused by this kernel.
Features:
Linux 3.0.101
Compiled it using Christopher83 custom Linaro 4.7.4 toolchain optimised for Cortex-A8 chipsets (4.9.1 For Android 4.4 and up)
Cranked it up with -O3 optimisations and -Ofast optimsations for GPU
LZ4 Compression for kernel and crypto
OC available up to 1.2 GHz (through 100 MHz steps)
Available governors (8): Lulzactive, SmartassV2 Intellidemand, Conservative, Ondemand, Interactive, Userspace and Powersave.
Available I/O schedulers (5): Noop, Deadline, Fiops, Row, Cfq, Sioplus, Bfq (Row is enabled by default)
Updated GPU drivers ([email protected] )
Tweaked and optimised I/O schedulers
Sound improvements (ALSA, PCM)
ARM RWSEM optimisations
Optimised SLUB memory allocator
Timer slack controller support
Backported CPUidle from 3.5 kernel
Support for swap
CIFS
TUN
Zram
Ext4 optimisations
Fast Charge
Fast wifi while in standby
Support for OTG connectivity
NTFS and FAT read and write support
Undervolted the LCD panel by 20%
LMK backported from kernel 3.4
Minimum brightness lowered (Needs confirmation)
Always up-to-date with Bbelos and Cyanogenmod Aries sources
720p Video recording support
Download:
4.4:
r7.1: r7.1 CWM Download
r7: r7 CWM Download
r6: r6 CWM Download
r5: r5 Download
4.3:
r4.6: r4.6 Download
r4.5: r4.5 Download
r4: r4 Download
r3: r3 Download
4.2:
r2.1: r2.1 Download
r2: r2 Download
r1: r1 Download
Installation:
Flash the zip with CWM. (Yes it's that simple )
Note: with the newer version of CWM, you'll need to flash the zip from the internal sdcard ONLY. If you want to use the external sdcard to flash the zip, please mount the internal one first as it will cause your device to be stuck in the samsung logo.
Sources:
Here you can find my sources if you want to do something.
https://github.com/zaclimon/impulse_ypg1
Thanks:
Bbelos
Mevordel
DerTeufel
Kasper_h
Alberto96
DerRomtester
Christopher83
Android1234567
Koala888
Changelog:
4.4.x
r7.1 (26/06/14)
Compiled with 4.9.1 GCC from Christopher83 (2014.06)
Patched futex exploit (Towelroot)
r7 (27/05/14)
Synced with the dev repo
Smaller kernel size
Compiled with the 4.9.1 Optimized GCC from Christopher83. (2014.05)
r6 (18/04/14)
Synced with the *regular* aries repo
Compiled with the newer 2014-01 Christopher83's toolchain
Removed 1.3 and 1.4 GHZ OC for stability purposes, however I added 1.1 GHZ if you needed it.
Added the BFQ I/O Scheduler
Added support for the 720p video recording as well as some fixes for preview
Misc optimisations.
r5 (17/01/14)
Android 4.4 support (KitKat)
Stuff synced from the dev repo as well (Front cam fix, lvm etc...)
Changed some optimisation flags
Optimised with newer 2013-12 Christopher83 toolchain
Fixed some other stuff
4.3.x
r4.6 (17/02/14)
Fixed the rotation (for the camera)
Misc fixes
r4.5 (12/12/13)
Updated to Linux 3.0.101
Increased the voltage on 1.3 Ghz OC (should fix the SOD's)
Included the fix for newer CM and Pac-Man Roms
Updated to the 11/13 toolchain from Christopher89
r4 (14/10/13):
Upstream changes from bbelos and aries tree (resized the /system and /cache partition)
Added 1.1 and 1.3 GHZ OC steps
Backported Cpuidle from 3.5 (not deep idle as it's been reported that it causes stability issues)
Updated the GPU drivers to [email protected]
Added a new I/O scheduler: sioplus (based from sio but better)
Enabled LZ4 compression and decompression for kernel and crypto
Added a fix for PACman users who was stuck
Misc improvements and fixes, check github for details
r3 (15/09/13):
Linux 3.0.95
Fully compatible with android 4.3 roms (cm10.2, PAC)
Used the newer 09/13 linaro toolchain from christopher89
ALSA PCM patches from newer kernel versions
Ext4 Optimisations
Timer slack controller support
Optimised SLUB Allocator
Optimised ARM RWSEM
Fixed right speaker
Updated the intellidemand governor (should be more efficient and shouldn't cause SOD's if it was the case before)
Misc optimisations (check github for more details)
4.2.x
r2.1(31/07/13):
Increase voltage to 1.4 Ghz OC in order to fix the freezing issue.
r2 (27/07/13):
Updated to linux 3.0.86
Revamped the I/O schedulers core drivers (Noop and Row tweaked as well, thanks to Derteufel)
Added FIOPS I/O scheduler
Enabled zram
LiveOC support (it may be half baked, would need the implementation of custom voltage to reveal it's full potential)
Replaced Wheatley with SmartassV2 as per user requests
Fast charge support (Download NS tools or a fast charge app to enable)
Updated BCMDHD drivers to 5.90.195.114
Enabled PM_FAST config for wifi (wifi speeds while sleeping should be as fast as when turned on)
Lowered the brightness down to the hardware's maximum
Added USB OTG host support (I would need confirmation as it's support) Enabled full FAT and NTFS read and write support into the kernel
Tweaked the VM values (Dalvik stuff)
Some under the hood refinements
r1 (08/07/13):
Initial release
Things planned to be implemented:
You propose
Digital FM radio works, which does sound better than the salsa method.
Bottom speaker still sounds quieter.
How fast is fast charge?
Sent from my YP-G1 using Tapatalk 2
dorfd1 said:
Digital FM radio works, which does sound better than the salsa method.
Bottom speaker still sounds quieter.
How fast is fast charge?
Sent from my YP-G1 using Tapatalk 2
Click to expand...
Click to collapse
I don't know how much time it takes for fast charge. Actually fast charge is only something that makes your device think that you're using AC when you charge with your computer. And I still yet implemented it.
Wow, I am happy that you decided to make kernel
props
About lowering screen brightness.
Sometimes kernel modification works, but framework lets us only set it to stock lowest minimum brightness. Try rootdim and see if it allows you to set your brightness lower
I will have a closer look at your repo when I will be on PC
Wysłane z mojego Nexus S za pomocą Tapatalk 4
as a future feature could you force enable adb? otherwise porting roms is impossible because I can't get a bootloop logcat
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
crancpiti said:
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
Click to expand...
Click to collapse
I believe you need 4.2.2
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
theraf said:
as a future feature could you force enable adb? otherwise porting roms is impossible because I can't get a bootloop logcat
Click to expand...
Click to collapse
I don't know well as far as the 4.2.2 kernel related, adb needs to be enabled from the dev section (because of security reasons) except for the first boot where it is doing an initial logcat than lock itself. I can try to do something though.
crancpiti said:
Awesome work! I will flash it this weekend
I'm still in 4.1 though can i just flash it or do i need to do it from the start?
And what are features like CIFS and TUN?
Click to expand...
Click to collapse
It can work but I'm not giving support for it. Also cifs is known for mostly remote file access and tun for vps servers.
Envoyé depuis mon Nexus 7 avec Tapatalk
Great work on this! I have one suggestion though. Can the amount of available ram be increased? I know the kernels on the 5.0 have done it, so I don't see why it would not be possible on the 4.0 (and everyone loves more ram!).
WHib96 said:
Great work on this! I have one suggestion though. Can the amount of available ram be increased? I know the kernels on the 5.0 have done it, so I don't see why it would not be possible on the 4.0 (and everyone loves more ram!).
Click to expand...
Click to collapse
I would need to find the right amount of ram that the camera needs (which could take some time).
Base on others sources
Wysłane z mojego Nexus S za pomocą Tapatalk 4
KOala888 said:
Base on others sources
Wysłane z mojego Nexus S za pomocą Tapatalk 4
Click to expand...
Click to collapse
I can't use the same amount of ram as the 5.0 because it will crash the camera, I will try to put 10000 instead of 14000.
I've been using this for a day and a half or so. Looking good so far.
At 1GHz, UI performance compared to the "regular" 3.0 kernel feels the same. Sunspider completes about 300ms faster, and Nenamark2 is consistently 1fps higher, but no difference with any other benchmark I tried. Modern Combat 4 now also runs with no stutters- I figure since Linaro has no performance benefits this must be due to the -O3/-Ofast optimizations (which by the way: what is O3 and Ofast? Can't find any info searching).
Battery life seems good so far.
Haven't experienced any odd crashes or lags.
Great job so far, I'll continue playing around with this- might use it in a future ROM.
zaclimon said:
I can't use the same amount of ram as the 5.0 because it will crash the camera, I will try to put 10000 instead of 14000.
Click to expand...
Click to collapse
I ment sources of kernels for different devices using same soc as yours
Wysłane z mojego Nexus S za pomocą Tapatalk 4
KOala888 said:
I ment sources of kernels for different devices using same soc as yours
Wysłane z mojego Nexus S za pomocą Tapatalk 4
Click to expand...
Click to collapse
Hmm well I checked venturi and derteufel sources, no good. I'll check p1 and Crespo later.
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Hmm well I checked venturi and derteufel sources, no good. I'll check p1 and Crespo later.
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
make a poll on the thread
but yes, definitely
zaclimon said:
Hey guys I'm considering this, would you like to get TWRP instead of CWM as far as the recovery solution goes?
Click to expand...
Click to collapse
I have TWRP on my Galaxy S4 and comparing it to CWM on my Player (and even the original CWM on my ancient s3c6410 devices), they all do what they need to do about the same. So it really doesn't matter to me.
TWRP would be nice but it does not matter to me. I would like to see aroma file manager working.
Sent from my YP-G1 using Tapatalk 2
Ok I put up the pool in OP, as for aroma FM, I don't want to mess with including touchscreen drivers (I feel sometime too lazy I know )
Related
This is my modded kernel for Mediapad. Based on latest Huawei sources
Features:
-updated to newest stable kernel base (3.0.42)
-CPU CAN be overclocked up to 1,9 Ghz , on default boots at 1,2 Ghz, use SetCPU, Sytem Tuner or similar app to set desired freq
-Overclock'd 3D GPU @ 300Mhz (6 Stages 3D GPU scaling)
-Overclock'd 2D GPU @ 266Mhz(3 Stages 2D GPU scaling)
-Boosted L2 cache (1566 Mhz max)
-Increased bus frequency - 360 Mhz from 1,5 Ghz slot upwards
-governors: ondemand (default), badass, interactive, lazy, smartass2, lagfree, conservative
-VDD interface (undervolting range between 750-1350 mv) - to set with System Tuner app from the market
-complied with Snapdragon optimized flags (-O2)
-optimized CRC32 and ARM RWSEM Algorithm
-CPU-supported unaligned accesses
-SIO scheduler(default)
-XZ Kernel Compression -> smaller kernel size
-arkusuma's touchscreen driver mod
-JHASH v3
-KSM and Automatic process group scheduling
-JRCU
-Init.d support
-Fsync control more about this feature here
more on github...
https://github.com/bart594/mediapad_kernel
Thanks to:
SebastianFM, showp1984, simone201, franciscofranco, Ezekeel, faux123, arkusuma, aftersilence and all guys how are involved in development on many different platforms
Installation:
1. Use fastboot mode to flash boot.img
2. Copy all modules to \system\lib\modules
Good lecture about governors and how to tweak them[/SIZE]
http://forum.xda-developers.com/showthread.php?t=1369817
Changelog:
07.31 R00 initial version
08.01 R01 new govs: lagfree, smartass2, lazy, interactive; arkusuma's touchscreen driver mod updated (now you can customize it by yourself)
08.02 R02 undervolting fixed, LMK from kernel 3.4, 2D GPU scaling to save some juice, and other minor patches
08.04 R03 smartass tweaked a bit, new CPU OC steps (1,9 Ghz max), GPU 2D/3D OC, second core behavior fixed (it was ramping up to the max no matter what was set as max freq), recovery version thx to aftersilence!
08.07 R04 new governor: badass with two steps at 1188000 and 1512000 and tweaked for performance , fsync control, autobrightness driver: it reports now 6 levels but we need to edit framework to use those new levels
08.15 R05 updated to 3.0.40 plus some "under the hood" fixes
08.25 R06 clean start with all previous features on 3.0.41 base , i hope that i got rid of all those nasty random reboots (voltages are little bit higher on default), no CM9 support - its good enough on its own , fastboot version only (due to problems with recovery update script) , JRCU, autobrightness levels reworked once again, CAF patches
09.03 R07 cpu1 stall at 1,2 ghz fixed, CAF patches to gpu,videodecoder, hdmi, and framebuffer
09.05 R07_1 dialer reboot fixed
09.12 R08 LMK updated, kernel base updated
If someone want to help out with JB developing or has some other questions related to ROM/Kernel developing please use irc channel
#mediapad_dev on http://webchat.freenode.net
does it provide better battery life?
i don't now, i didn't test battery life that much
but higher cpu clocks usually means shorter battery life
Looks good. Can you add this to your kernel? http://forum.xda-developers.com/showthread.php?t=1792713
//ok sorry I didn't see it
it's already there:
-arkusuma's touchscreen driver mod
Already tried that! Mass improvement!!!
Thank you for the great work! Keep up that way and make MediaPad even better!
Tnx dude! Works, and looks fine!
athanaso77 said:
Already tried that! Mass improvement!!!
Thank you for the great work! Keep up that way and make MediaPad even better!
Click to expand...
Click to collapse
can you explain better what do you mean for "mass improvement"?
thanks
can i specify value for last mod of "touchscreen filtering" on this kernel?
Sent from my HUAWEI MediaPad using xda premium
If I tried to change the VDD with system tuner, it automatically jumps to 1350mv and stuck at that voltage.
bart594 said:
This is my modded kernel for Mediapad. Based on latest Huawei sources
PROBLEMS
-native WIFI Tehtering doesn't work -> blame Huawei for obsolete Wifi driver (on stock kernel too)
-there is no source for huawei's wifi driver so i needed a hack to make it work
Customization possibilities are a little bit limited because of this
Click to expand...
Click to collapse
Have you look at this (bcm4329):
https://android.googlesource.com/platform/hardware/broadcom/wlan
I haven't tried to compile it though.
rurou said:
If I tried to change the VDD with system tuner, it automatically jumps to 1350mv and stuck at that voltage.
Click to expand...
Click to collapse
You have right It's broken I will try to fix it
While you're at it, can you change the value of touch_thres in touchscreen mod for the default 10 (or 9?) to 25...or 20. Better yet, ask arkusuma for his latest mod where it's user adjustable
Sent from my HTC Glacier using Tapatalk 2
arkusuma said:
Have you look at this (bcm4329):
https://android.googlesource.com/platform/hardware/broadcom/wlan
I haven't tried to compile it though.
Click to expand...
Click to collapse
BCM4329 is actually the old driver. With ICS google introduced new bcmdhd driver
Huawei was so lazy and took old gingerbread driver, that's why thetering don't work
maybe you can add in some additional governor.
rurou said:
While you're at it, can you change the value of touch_thres in touchscreen mod for the default 10 (or 9?) to 25...or 20. Better yet, ask arkusuma for his latest mod where it's user adjustable
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
That's a good proposal!
I use S7-302u ,Android4.0.3,C232B001.
Can i flash this kernel ?
thank you for advice.
nice work, sounds good.
My Mediapad doesn't work with my Nikon D7000 DSLR together. (If I plug a Canon EOS in (which works), the D7000 works afterwords with DSLR Dashboard, Helicon Remote,... until I reboot my tablet again)
Sound strangs, I know! ^^ (But the D7000 is recognised always @ USB Host Controller and also at dmesg)
Maybe this kernel will help me!
Sorry, but I'm a newbie in generell (@ Android):
I tried already some firmwares to solve this, but only with the SD-card, which isn't very hard to do.
Can you make a more detailed install instruction?
With which firmware I can use this kernel mod?
many thanks
Michael
ZEII said:
I use S7-302u ,Android4.0.3,C232B001.
Can i flash this kernel ?
thank you for advice.
Click to expand...
Click to collapse
according to this
http://forum.xda-developers.com/archive/index.php/t-1743025.html
there is no difference between those two versions so i think you can safely flash the kernel. If it's for whatever reason not gonna boot up you can always revert to original kernel
empi00 said:
nice work, sounds good.
My Mediapad doesn't work with my Nikon D7000 DSLR together. (If I plug a Canon EOS in (which works), the D7000 works afterwords with DSLR Dashboard, Helicon Remote,... until I reboot my tablet again)
Sound strangs, I know! ^^ (But the D7000 is recognised always @ USB Host Controller and also at dmesg)
Maybe this kernel will help me!
Sorry, but I'm a newbie in generell (@ Android):
I tried already some firmwares to solve this, but only with the SD-card, which isn't very hard to do.
Can you make a more detailed install instruction?
With which firmware I can use this kernel mod?
many thanks
Michael
Click to expand...
Click to collapse
If you are on newest Android for Mediapad (ICS 4.0.3) you can flash the kernel
but i really don't now if its gonna help with your problem. I haven't touched USB part in the kernel (apart from regular linux kernel update)
To flash you need to use fastboot mode and those two commands
fastboot flash boot boot.img
fastboot reboot
To boot into fastboot just install Quick Boot from Google Play and choose Bootloader there
MiRaGe is a lean and efficient kernel for the stock Nexus 4 ROM with the optimizations and updates that are not included in Google's stock kernel. MiRaGe kernel fits squarely in the stock Nexus 4 ROM; all of the modules are integrated in the kernel just like the stock kernel and it should work with all AOSP ROMs that work with the stock kernel and boot image. However, only the current stock ROM is tested. If you decide to use MiRaGe, just flash and forget it since I have avoided adding more sysfs parameters. It is not my goal to enable all possible tweaking options and add every possible feature to the kernel such as multitude of governors, io schedulers, sweep2wake, fastcharge, etc. This kernel is not intended as a tweaker's kernel. You can, of course, tweak it as much as you want since that is your phone and kernel. But please try removing your tweaks before posting any problems. I always test the latest builds with the current stock ROM before posting here.
I am sharing exactly what I have developed for myself and posting here so that I can return at least a small part of what I have received from the open source community. I thought the amount of time I have spent for MiRaGe could be useful for others as well. In short, take it if you want it, leave it if you don't. But comments, suggestions are always welcome when they make sense.
Source Code:
Source code is based on Google's msm kernel source (currently android-msm-mako-3.4-lollipop-mr1.1) and a summary of my changes are below. You can find the full details of my changes and the complete source code in my repo.
Changes:
- synced with mainline Linux 3.4.110
- cleaned up kernel configuration and removed many unnecessary options
- removed kernel debugging options
- built with the Linaro toolchain (gcc 4.9.4 - 15.06) using standard krait and -O2 optimization
- removed AOUT and OABI support
- disabled both user-space msm_mpdecision and kernel-space msm_mpdecision
- removed msm_run_queue_stats, dcvs, and stock msm_mpdecision in the kernel
- added autosmp, a simple and efficient (by me) multi-core cpu hotplug driver
- disabled the user-space thermald and switched to kernel-based msm_thermal
- replaced CFQ with the latest BFQ as the default IO scheduler
- backported random and prandom updates from Linux 3.13 (no entropy depletion anymore)
- backported workqueue from Linux 3.8 to include many important improvements
- backported rwsem from Linux 3.11 to include lock stealing improvements
- backported mutex and rcu locking from Linux 3.10 and 3.8, respectively
- backported slub memory allocator updates from Linux 3.8
- backported cpufreq driver, ondemand, and conservative governors from Linux 3.12
- updated interactive CPU governor from AOSP and CAF
- disabled userspace CPU governor,
- enabled callback-free CPUs (RCU_NOCB_CPU)
- backported TCP Small Queues and CODEL net scheduler from Linux mainline and set as default
- updated kernel scheduler, msm-hotplug, msm-idle, msm-pm code from CAF and Linux mainline
- applied patch [v4] binfmt_elf.c: use get_random_int() to help with entropy depleting
- enabled autogroup scheduler and applied patch per-uid task group for Android
- added optimized ARM RWSEM algorithm
- added optimized ARM SHA1/AES routines
- enabled CPU-supported unaligned accesses
- disabled gentle fair sleepers in scheduler
- updated Qualcomm HW RNG driver from CAF
- enabled BPF JIT compiler for packet filters
- applied glibc patch to improve the performance of memcpy and memmove
- applied word-at-a-time ARM API patches
- enabled CPU overclocking up to 1.728 GHz with user-space vdd control
- optimized vdd curves, L2 and bus speeds for better performance and efficiency
- removed unneeded a2xx and a4xx components from kgsl driver
- modified the prima wifi driver to disable debug code
- removed PMEM completely, MiRaGe is pure ION
- add support for kernel mode NEON and NEON acceleration
- add NEON optimized SHA1, SHA256, and SHA512 crypto code
- add LoUIS API for cache maintenance ops to improve cpu hotplug latency
- added and enabled power_efficient workqueue
- added and enabled msm memutils
- added screen gamma, user space cpu voltage control, and dt2w
- backported devfreq driver from CAF and switched kgsl 3d governor to simple_ondemand
- backported many other fixes/updates/optimizations from CAF and Linux mainline, see the repo for details
- init.d supported if /etc/init.d and busybox are available
- a diff file of changes to ramdisk is here
Downloads:
Boot image for stock ROM:
LMY standard kernel Built: 10/25/15 MD5sum: a315cc446499d60cb4b3a61ea7bfa8f8
LMY overclock kernel Built: 10/25/15 MD5sum: 7c72a66830f511b025968db2bb743429
Anykernel updater for custom ROM:
Revert back to stock kernel to restore the original ramdisk and flash anykernel package of MiRaGe after that. This is not needed in the next anykernel update.
LMY standard kernel Built: 10/25/15 MD5sum: 85b4136ac0ada793da7b80763193095a
LMY overclock kernel Built: 10/25/15 MD5sum: 2924fb6a963b40087c296a7b1abfc1d3
KTU standard kernel Built: 10/31/14 MD5sum: dca7d06933eb43c8da3ba7941bb6ac88
KTU overclock kernel Built: 10/31/14 MD5sum: dca7d06933eb43c8da3ba7941bb6ac88
The only difference between the standard and overclock builds is the ~100mV undervolt in the overclock build. Both kernels have maximum CPU_freq = 1.728 GHz, default CPU_freq = 1.512 GHz, overclocking, and user space cpu voltage control enabled. Since the CPU gets hot quickly in Nexus 4, I only recommend overclocking with the overclock build that has built-in undervolt. If the phone doesn't boot with overclock kernel, it means that your CPU is not able to handle the undervolt settings. In that case, you can just reboot into recovery and flash the standard kernel. No-frills CPU Control is recommended to set the max overclock frequency. Each CPU has different overclock/undervolt ability. Don't get disappointed if the OC build doesn't work for you.
Installation:
You can do one of the followings
- Flash the zip files in recovery, there is no need to wipe cache or dalvik-cache
- Flash the boot image in the zip file using either Flash Image GUI or fastboot
- Here is the original boot image for LMY48I build, in case needed for going back to stock. Either flash in the recovery or open the zip file to extract the boot image.
Credits:
- Special thanks to Linux, Google, CAF, Linaro developers in general.
- @tvall, @bedalus, @xboxfanj, @ihancioglu, @xenyz for collaboration
- @stratosk for the screen gamma interface and dt2w
- @defconoi for collaboration (see Unleashed Kernel Series)
- @mathkid95 for the any-kernel updater package
- @joeykrim for FlashImageGUI
- @Christopher83 for the optimized Linaro toolchain builds
- Other credits are given in the repo for each commit
Recommendations:
I am frequently receiving requests to add sound patches in the kernel. I agree that the sound is not very good but there are solutions. I am using the Viper4AndroidFX as a replacement sound processor. I recommend giving it a try. You need to go to the sound options and select ViPER4AndroidFX to use this sound processor or freeze MusicFX (I use Link2SD for this). There is plenty of information at the above link. With this available, I am not planning to add any sound patches.
Another frequent question is about choosing CPU governor and IO scheduler. In the earlier builds, interactive governor had the best balance of performance and battery life among other CPU governors and it is still available. In the latest builds, ondemand governor was backported from Linux 3.12 and replaced interactive as the default. The latest patches in the mainline Linux, especially stratosk's patch that optimized the load calculations made the new ondemand governor the better option regarding both power and performance. Regarding IO scheduler, BFQ scheduler has the best overall real-use performance and it is actively maintained/improved. You can use Nofrills CPU Control to change the governor and scheduler. But I would leave the defaults as BFQ scheduler and ondemand governor.
Since all of the cpu power control functions are contained in the kernel with MiRaGe, the userspace PowerHAL library will be giving the following messages in the logcat.
Code:
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
E/PowerHAL( 511): touch_boost: failed to send: No such file or directory
These are harmless but if you want to eliminate them, just make a backup and delete/rename /system/lib/hw/power.msm8960.so and power.mako.so. The single purpose of touch_boost is to enhance the system response to the user interaction. But using a service in the user space to send a touch boost signal to the kernel via slow sysfs file system is the wrong way of trying to achieve lower latency. In addition, every touch input doesn't need a CPU frequency boost which wastes battery power. The best way of achieving the low-latency system response to user interaction is improving the efficiency of existing CPU governor which raises the CPU frequency and hotplug driver which enables off-line cpu cores when needed. In MiRaGe, CPU freq is only controlled by the CPU governor based solely on the CPU load and the latency is low since efficiency is improved by reducing such unnecessary bloat. Additionally, highly-efficient autosmp hotplug driver works in-sync with the CPU governor to enable off-line cpu cores when the the CPU frequency reaches a high threshold and still more compute power is needed. Therefore, touch boost bloat is removed.
With some of the custom ROMs, root is lost after flashing MiRaGe because of using the init scripts in the ramdisk for starting the su daemon. SuperSU is the recommended solution. I might switch to any-kernel-updater to address this problem but as written in the OP, MiRaGe is primarily for the stock ROM. Also, having the full boot image in the zip file is more reliable than expanding/processing/repacking the boot image.
MiRaGe supports init.d if it is setup. To setup init.d do the followings either within ES File Explorer or terminal .
- install busybox (I use busybox on rails)
- create /system/etc/init.d and chmod to 755 (rwxr-xr-x)
- create your init scripts in the /system/etc/init.d directory. Name them 01yourscriptname (e.g. 01mysettings) and chmod 755. Make sure they are UNIX format (not in DOS/Windows).
example:
Code:
#!/system/bin/sh
echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled
- reboot
Here is how to add multiROM support
How to build:
If you are going to distribute your builds, please don't build your binaries with the same name (i.e. MiRaGe) and distribute in this thread. I would recommend you to start an alternative thread. Otherwise the problem reports will be too confusing for everyone.
First requirement is an ARM toolchain for cross compiling, i.e. using an X86 computer to generate ARM binary. I use Linaro tool chain for cross compiling like many others since Linaro specifically develops tool chains that produce optimized binary for ARM architecture.
Linaro toolchains can be downloaded from Linaro binary page. Christopher83 has built the latest Linaro-14.08 toolchain based on gcc-4.8.4 which is stable/reliable and I recommend starting the development with this toolchain.
The binary Linaro toolchain for Linux package needs to be expanded in a certain directory, probably inside the home directory. The source code for kernel is available in my Github repo, You can either download the kernel source as a compressed package or you can git-clone it with the following command (you will need git installed in your Linux computer)
Code:
git clone https://github.com/mrg666/android_kernel_mako.git
The kernel source can again be in a specific home directory.
After the source and toolchain are prepared, copy the configuration file for shooter, arch/arm/configs/mako_config, as .config to the root of the kernel source and use the following command to build the kernel
Code:
make ARCH=arm CROSS_COMPILE=~/untarred-toolchain-dir/bin/arm-linux-gnueabihf- zImage -j8
Replace j8 in the above command according to the number of cpus you have on your computer.
Also set CROSS_COMPILE based on the directory you have expanded the binary toolchain package in your home directory.
I always use the latest version of Xubuntu x64 (with custom built kernel) on my Linux workstation that has a AMD FX-8320 (overclocked to 4.2 GHz), 8 GB RAM, 500 GB HD. The compile time is about 2 minutes for me using all 8 cores. I have been using Ubuntu since version 10.04 to build Gingerbread, Jellybean, and Linux kernel and updated the OS to each and every new version, all of them worked just fine. There is no magic version of Ubuntu. The build problems arise from the package requirements not the OS version.
The flash package is easy. Just use any-kernel updater package in the OP as a template and replace zImage in /kernel directory with your build. If you want to create a boot image, see this post
Now that you have source and can build the kernel, you can add all the features you want to your own kernel
Woww greatt, thanks mirage
many thanks Mirage!
Does JSS come with caf video driver or it can be flashed on non-cm roms without problems?
Inviato dal mio Nexus 4 con Tapatalk
Good to see new kernel which goal is simplicity, not many of them are here. ill try it when clean instal comes to repertoar. just one question, you didnt mention -O3 and gcc 4.8.2, so i asume you didnt use them? Thanks.
Poslano sa mog Nexus 4 koristeći Tapatalk
I haven't updated the video driver from CAF ... yet. I will do after the 4.4 update if Google hasn't done yet.
Kernel is compiled with gcc 4.7.4 using -O2 optimization. gcc 4.8 was not giving me reliable builds yet. I will switch when 4.8 becomes stable. I have tried O3 optimization in the past and I didn't see any benefit of it. Plus, O3 optimization caused reliability issues especially with the latest gcc compilers.
MiRaGe should be compatible all AOSP-based ROMs, as long as the same user-space libraries are used with the stock 4.3 ROM. I can't claim universal compatibility since even stock JSS and JWR builds need different kernels.
Would you consider making a ZIP?
I found your kernel to be quite interesting, but I don't really like flashing via IMG file.
C.T.Richter said:
Would you consider making a ZIP?
I found your kernel to be quite interesting, but I don't really like flashing via IMG file.
Click to expand...
Click to collapse
you can download one of 1000 kernels around here and replace the kernel.img ... and wholà you have a zip version.
anarkia1976 said:
you can download one of 1000 kernels around here and replace the kernel.img ... and wholà you have a zip version.
Click to expand...
Click to collapse
Can't agree with you more but the problem with so many people on xda is that they rarely even open up a zip file to see how it operates. Guarantee most of the people will shy away simply because of the lack of a zip. Again I agree its not that hard to do but lets be honest here most have problems searching so taking a boot.img and putting it in a zip probably aint happening
I have just uploaded the alternative flashable zip files. I will remove the image files since they are in the zip files now.
Just flashed on slim and lost root... Just a heads up
Sent from my Nexus 4 using XDA Premium 4 mobile app
anarkia1976 said:
you can download one of 1000 kernels around here
Click to expand...
Click to collapse
LOL that's right!
QUIETLYloud said:
Just flashed on slim and lost root... Just a heads up
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That can't happen due to flashing the zip files in the OP since there is nothing in the zip file that touches /system, it is not even mounted.
Gonna give it a go on Vanir. I'll report back of my root gets effected. Happened a lot with 4.3 when it first came out
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
Gonna give it a go on Vanir. I'll report back of my root gets effected. Happened a lot with 4.3 when it first came out
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I am using CWM 6.0.4.4. It is constantly suggesting to restore my root although it is not lost. If this is what is mentioned here, just ignore it; root is not lost. SuperSU, su keep working. Actually, I am losing my patience with CWMT lately. Maybe it is time to switch to TWRP.
mrg666 said:
I am using CWM 6.0.4.4. It is constantly suggesting to restore my root although it is not lost. If this is what is mentioned here, just ignore it. Root is not lost. SuperSU, su keeps working. Actually, I am loosing my patience with CWMT lately. Maybe it is time to switch to TWRP.
Click to expand...
Click to collapse
I'd say it's long overdue to switch to twrp lol. Ever since I switched to twrp back on my rezound, I have NEVER looked back to cwm. Not to say cwm isnt/wasn't great.. But you know how it is lol.
Sent from my Nexus 4 using Tapatalk
DontPushButtons said:
I'd say it's long overdue to switch to twrp lol. Ever since I switched to twrp back on my rezound, I have NEVER looked back to cwm. Not to say cwm isnt/wasn't great.. But you know how it is lol.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I just don't like the "overdesigned" interface of TWRP. It is too fancy for my taste. But as long as it works when needed, it would be fine with me. I don't boot into recovery so frequently anyway since I flash the kernel in fastboot or Flash Image GUI.
Oddly enough, I lost root. I'm currently running the latest version of Paranoid Saberdroid.
C.T.Richter said:
Oddly enough, I lost root. I'm currently running the latest version of Paranoid Saberdroid.
Click to expand...
Click to collapse
Is it just what the recovery says? I use the stock JWR ROM and root is preserved when I flash although CWMT falsely complains about it.
Edit: I just tested with TWRP as well. Root is still preserved.
mrg666 said:
Is it just what the recovery says? I use the stock JWR ROM and root is preserved when I flash although CWMT falsely complains about it.
Edit: I just tested with TWRP as well. Root is still preserved.
Click to expand...
Click to collapse
Using TWRP there is no error message, it just says it was installed successfully.
I just tried it on a clean install, and the same thing happened.
Features:• Based on SEMC 2011 ICS sources, re-based on Linux kernel 2.6.32.61
• Built with linaro 4.7.4 toolchain
• CWM-v6.0.2.8
• Idiot-proof feature: will boot into recovery if an unsupported or no android version is found
• Custom mtd partitioning scheme suitable for JB
• Modular recovery flashing support
• Much more RAM than stock for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
• Patched to latest 2.6.32.61 release
• kgsl: SEMC 2011
• ARM: many backported fixes and optimizations from CAF 3.x
• Netfilter: many backported fixes and optimizations from CAF 3.x.
• net/iptables: Fully working networking and iptables support. Fully working traffic control via data limits menu of JB
• Backported tiny-rcu
• Superior AHB overclocking - improved responsiveness and performance. 'Buttery-smooth' experience
• improvements: memcpy, kmalloc, jhash, sha1, scheduler, optimized CRC32, LZO, vmalloc, pm_suspend
• Two-way call recording
• binder, lowmemorykiller fixes backported from CAF 3.x
• WEXT tiwlan
• pmem: backported from CAF 2.6.35
• modular undervolting
• tripple buffering support
• Supported IO Schedulers: NOOP, BFQ, AS, DEADLINE, CFQ, VR, SIO
• net: Stochastic Fair Blue scheduler
• ZRAM + google snappy compression backported from CAF 3.x
• ZCACHE backported from CAF 3.x
• Cleancache backported from CAF 3.x
• Kernel compression: LZO for best kernel booting times
• Makefile: optimization flags
• dcache: vfs_cache_pressure -> 25
• Proportional Rate Reduction for TCP
• fsync enable/disable toggle at: /sys/module/sync/parameters/fsync_enabled (enabled by default)
• Many many more fixes and improvements available @ github
*Optimize with -O3 flag
*fix deadlock when system is low on memory (thank you @xelyt)
*backport lowmemorykiller from CAF msm-3.4
download
http://yairpatch.com/blog/2013/10/yairpatch-kernel-for-xperia-x8/
version 1.0 Final - http://yairpatch.com/blog/2013/11/yairpatch-kernel-for-xperia-x8-version-1-0/
KITKAT and CM10.2 KERNEL - http://yairpatch.com/blog/2014/03/kitkat-kernel-for-xperia-x8alpha/
Install:•Backup
•Unlock your bootloader as described here: http://forum.xda-developers.com/show...77&postcount=3 or here: http://forum.xda-developers.com/show....php?t=1254225
•Download the latest kernel ftf file from here and move it to Flashtoolfirmwares so that Flashtool can pick it up
•Flash the kernel via Flashtool
•Reboot and you should see the coolest kernel boot animation
• (First time only) Get into recovery and format /system /cache and /data manually
Uninstall:•
Flash back to stock using SEUS
OR
• Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Any other way is completely unsupported, don't ask how to unbrick if you can't read the instructions
*thx goes to nAa for his great
Source:
https://github.com/yairpatch/msm7x27-2.6.32.x-nAa
XDA:DevDB Information
[KERNEL] yairpatch-JB[LINARO 4.7.4][31-10-13] , a Kernel for the Sony Ericsson XPERIA X8
Contributors
afi1982
Kernel Special Features:
Version Information
Status: Stable
Created 2013-10-31
Last Updated 2014-03-27
So Test, and report ; D
Howilion said:
So Test, and report ; D
Click to expand...
Click to collapse
already tested by me now it's your turn
I will test for now give you thanks and to amazing work ;D
This only work with your ROM ? Or another JB ...
Sent from my E15i using xda app-developers app
Sir Roven said:
I will test for now give you thanks and to amazing work ;D
This only work with your ROM ? Or another JB ...
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
every jb and GB rom
Everything seems to be stable and working on the first version for me..
Just one thing and it's not a bug
You know on the YairPatch kernel logo there seems to be a bit of an overlapping of the kernel version at the bottom.
No big deal but would look much better if it could be sorted out.
CtrlAltDelIrl said:
Everything seems to be stable and working on the first version for me..
Just one thing and it's not a bug
You know on the YairPatch kernel logo there seems to be a bit of an overlapping of the kernel version at the bottom.
No big deal but would look much better if it could be sorted out.
Click to expand...
Click to collapse
yeah i know but for 0.2 and 0.3 i'm using nAa ramdisk so thus "bug" is gone
Sorry for this question but... can you try to make something for poor 2.3 users? If you would find some time to fix bluetooth problems it'll be great.
iks8 said:
Sorry for this question but... can you try to make something for poor 2.3 users? If you would find some time to fix bluetooth problems it'll be great.
Click to expand...
Click to collapse
Why don't you upgrade to 4.1.2? Everything works and the speed is better in my opinion.
------------------------------------------------------------------------------------------------------------------------------------
Reflashed to 3rd kernel. I can really feel a speed difference. Really good job Yair!
@up: maybe it is but it's unusable for me: most of time I'm using my phone as my mp3 player and everybody knows how music on 4.1 is annoying :/
iks8 said:
@up: maybe it is but it's unusable for me: most of time I'm using my phone as my mp3 player and everybody knows how music on 4.1 is annoying :/
Click to expand...
Click to collapse
With Google Play Music it's great!
CtrlAltDelIrl said:
Why don't you upgrade to 4.1.2? Everything works and the speed is better in my opinion.
------------------------------------------------------------------------------------------------------------------------------------
Reflashed to 3rd kernel. I can really feel a speed difference. Really good job Yair!
Click to expand...
Click to collapse
Did you notice any trace of the "hard to wake" bug ?
afi1982 said:
Did you notice any trace of the "hard to wake" bug ?
Click to expand...
Click to collapse
None whatsoever!
CtrlAltDelIrl said:
None whatsoever!
Click to expand...
Click to collapse
Good to hear
afi1982 said:
Good to hear
Click to expand...
Click to collapse
I'm gonna restore my MiniCM7 backup and see how that goes. Just an experiment but I'm sure it interests you
Show logo nAa it´s normal ?
Sir Roven said:
Show logo nAa it´s normal ?
Click to expand...
Click to collapse
Yes
CtrlAltDelIrl said:
Yes
Click to expand...
Click to collapse
i honestly flashed a couple of times using different versions of flashtool. thought something was wrong lol.
on topic: i tried checking yair's site, as well as the op, and i can't seem to find the differences between 02 and 03 kernel. i've already tried both, and 03 seems to be much smoother.
cascabel said:
i honestly flashed a couple of times using different versions of flashtool. thought something was wrong lol.
on topic: i tried checking yair's site, as well as the op, and i can't seem to find the differences between 02 and 03 kernel. i've already tried both, and 03 seems to be much smoother.
Click to expand...
Click to collapse
That made me laugh. Thank you!
The differences are only in the compile flag optimisations. But yes, 03 is very smooth.
CtrlAltDelIrl said:
Why don't you upgrade to 4.1.2? Everything works and the speed is better in my opinion.
Click to expand...
Click to collapse
Little bit off-topic, but I remember when the minicm10 came out with the .32 kernel, you was happy with the incredible performance. And after a longer test period you always went back to froyopro or minicm7 due the better performance...
Okay, go back to the thread.
@cascabel: you can't find the differences between the o2 and o3 versions of the kernels because the two kernels source code is same, nothing different. The compiler settings is invisible, this is not add or remove features, the difference is only the increased/decreased performance/stability.
If you interested what is the difference and how to work the code optimization in gcc, use google and you can find lot of information about how to work the o2 and o3 optimization, about the strict-aliasing and tons of other optimization flags.
@afi1982: can you post the gcc flags what you used? Or simple changed to -O3 without additional flags? (now playing with the .32 code to build a gb only kernel).
Before anything I'd like to sincerely thank DooMLoRD. He was the first dev ever to bring multiple recoveries to Xperias since Xperia X10 days and he has done a lot to make this work. So if you like this, please consider donating him for his great work.
Click to expand...
Click to collapse
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* You may have voided your device's warranty.
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications on your device
* I absolutely disclaim any responsibility.
*/
Downloads
LINKS REMOVED. DISCONTINUED.
Instructions
-Installation
1. Download zip.
2. Flash via recovery
3. Reboot
Click to expand...
Click to collapse
-Booting into recovery
For philZ recovery 6.41.6 :
+ Press vol. up when phone vibrates
For twrp 2.7 :
- Press vol. down when phone vibrates
Click to expand...
Click to collapse
Changelog/Feature list
v4
- Flashable zip for kernel
- Kernel compressed with LZO for better compression/decompression speeds
- Doubled the VM readaheads
- Optimized CPU performace
- Boost networks speed by locking the initial TCP window size to 64K
- Entropy tweaks
- Enabled ARCH_POWER
- BFQ and SIOplus now working properly
- Properly fixed dynamic management of dirty page writebacks
- Enabled ARM_THUMBEE
- Disabled gentle fair sleepers
v3
- Cross-compiled with arm-cortex_a9-linux-gnueabihf-linaro_4.9.1-2014.04 toolchain with arm-gnueabi binaries.
- New logo
- Add sioplus i/o scheduler and bfq i/o scheduler
- Fixed n_tty_write crash when echoing in raw mode(thanks to peterhurley)
- O3 optimizations
- Dynamic management of dirty page writebacks
- Enabled 5 GHz band and cleancache
- Lots of optimizations and good speed boost.
v2
- PhilZ touch recovery instead of CWM
- Changes for LZO compression/decompression(thanks to Gava97)
- Frandom modules added(thanks to Gava97)
- Code optimized
- Used 4.7 toolchain instead of 4.4.3 GCC
v1
-Initial release
-Dual recovery
-AOSX kernel compiled from source
-One kernel compatible with all kitkat ROMs(Both CM and AOSP based)
Click to expand...
Click to collapse
CPU Governors and I/O schedulers
CPU Governors
interactiveplus
fantasy
pegasusqplus
dyninteractive
intellidemand
nightmare
sakuractive
abyssplug
wheatley
pegasusq
ondemandAX
lulzactiveq
hotplug
minmax
smartassV2
interactive
conservative
ondemand
userspace
powersave
Lionheart
performance
I/O Schedulers
bfq
sioplus
noop
deadline
cfq
sio
vr
row
zen
Usage of some features
Dynamic management of dirty page writeback
What is does?
- 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. By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
Thanks to Christopher83 and kingBABAsula.
Usage-
To enable it:
Code:
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
To disable it:
Code:
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
To customize intervals (in centisecs):
Code:
echo xxxx > /proc/sys/vm/dirty_writeback_active_centisecs
echo xxxx > /proc/sys/vm/dirty_writeback_suspend_centisecs
Commit list
5502c9d- LZO compression for kernel for better speed
3583d16- 2x(min,max VM READAHEAD)
85bc173- Change CPU performance
33eaf7c- Boost network speed
e4adc50- random: entropy tweaks are all the rage nowadays
b2f1fb2- Enable ARCH_POWER
58aa12b- IOsched update: Add BFQ and SIOPLUS in defconfig
982e2cc- Defconfig part for 96f9959
e07c683- Enable ARM_THUMBEE
ad5f538- Disable gentle fair sleepers
7ff3c51- Add new logo
eda4962- O3 optimizations
96f9959- mm: Dynamic management of dirty page writebacks
ab20cd6- block: Add BFQ I/O scheduler
cba2d5a- mutex: dynamically disable mutex spinning at high load
65581fa- n_tty: Fix n_tty_write crash when echoing in raw mode
2dcff35- Enable 5GHz band and clean cache
7a1805b- IOSCHED: Add SIOplus
231a11c- Add philZ touch recovery
713597e- lib/lzo: Optimize code for CPUs with inefficient unaligned access
a7e474f- lib/lzo: huge LZO decompression speedup on ARM by using unaligned access
548b108- lib/lzo: Update LZO compression to current upstream version
13cad97- drivers/char: add frandom modules
6096ed0- Dual recovery
Credits
linus(and other guys)- For linux kernel
ST-ericsson- For making the kernel compatible with montblanc board
Sony mobiles- For making the kernel compatible with riogrande
munjeni- For his great development and help
DooMLoRD- For dual recovery in other devices from which I could take reference and for helping me
AOSX team(Including me )- For development of 2012 xperia novathor devices
Phil3759- For PhilZ touch recovery
Dees Troy(and omnirom team)- For TWRP
cocafe- For work on u8500 samsung devices
KINGbabasula- Also for work on u8500 samsung devices
Christopher83- For modified linaro toolchains for cortex-a9
abcdjdj- For helping me in this
Gerald Carl- For testing it
Estape11- For testing it
#include<iForgotYou.h>
Sources
Kernel sources- https://github.com/Abhinav1997/AJ-Kernel
Ramdisk- https://github.com/Abhinav1997/AJ-ramdisk (other device devs/users can look into this to understand what changes were done)
Nice work bro
Great work bro
everything works fine !
tnx :good:
v2 released
Cheers,
AJ
been using triple recovery on xperia sp.
Will try this one on my xperia P :good:
Nice job ^^
But one question: is this 3.4 kernel, so yes can you make one for JB ?
Verstuurd vanaf mijn LT22i met Tapatalk
Dark Mist said:
been using triple recovery on xperia sp.
Will try this one on my xperia P :good:
Click to expand...
Click to collapse
Will soon bring triple recovery to this also
Pandemic said:
Nice job ^^
But one question: is this 3.4 kernel, so yes can you make one for JB ?
Verstuurd vanaf mijn LT22i met Tapatalk
Click to expand...
Click to collapse
Nope. This is 3.0.101 though I can bring dual recovery to stock JB kernel.
Cheers,
AJ
Abhinav2 said:
Will soon bring triple recovery to this also
Nope. This is 3.0.101 though I can bring dual recovery to stock JB kernel.
Cheers,
AJ
Click to expand...
Click to collapse
Wow bro, I would like to have that stock jb kernel with dual recovery...can you make one???
Sent from my LT22i using Tapatalk
Xperia_Fans said:
Wow bro, I would like to have that stock jb kernel with dual recovery...can you make one???
Sent from my LT22i using Tapatalk
Click to expand...
Click to collapse
Well yeah, I can but firstly I'll have to bring more features to this kernel
Cheers,
AJ
*mcdaonald theme song* tada tada dat da i am loving it :laugh:
cellabonez said:
*mcdaonald theme song* tada tada dat da i am loving it :laugh:
Click to expand...
Click to collapse
lol
BTW you can use it with carbon to get the netfilters working like you wanted
Cheers,
AJ
Abhinav2 said:
Well yeah, I can but firstly I'll have to bring more features to this kernel
Cheers,
AJ
Click to expand...
Click to collapse
ok bro no rush, take your time...I understand that
Abhinav2 said:
lol
BTW you can use it with carbon to get the netfilters working like you wanted
Cheers,
AJ
Click to expand...
Click to collapse
damn talk about side order :highfive:
Great work @Abhinav2! Just a quick suggestion. Maybe you could update the mali graphic driver and/or add OC feature to Cpu (and Gpu if you will)
Sent from my Xperia P using XDA Premium 4 mobile app
kopter3161 said:
Great work @Abhinav2! Just a quick suggestion. Maybe you could update the mali graphic driver and/or add OC feature to Cpu (and Gpu if you will)
Sent from my Xperia P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried update mali drivers and gralloc to 6 may update but unfortunately it didn't passed kernel logo. I'll try to debug it but it can take time. Also DevSwift1 tried GPU OC but it had no effect on device.
AJ
Abhinav2 said:
I tried update mali drivers and gralloc to 6 may update but unfortunately it didn't passed kernel logo. I'll try to debug it but it can take time. Also DevSwift1 tried GPU OC but it had no effect on device.
AJ
Click to expand...
Click to collapse
the first custom kernel for kitkat, thanks AJ!
1. dual recovery seems cool, but imo there is no real benefit when both of them do effectively the same. Again, great job that you managed to include both, but to me it becomes just "bloat". no offence.
2. I'm not a fan of overclocking but there are uses for better CPU/GPU controls. I would love to underclock and undervolt them to squeeze a little more battery out of my phone. God, it seems lots of those kids here care about their "gaming performance" and their "lagfree" "smoothness", but I use my phone as a phone and I don't give a sh... about that if I can get a couple more hours of use.
What's your opinion on this? Do you think we will ever get this working here like all the others (looking at those qualcomms and snapdragons in the other forums)? I mean we got more manufacturer sources than most of them, right? Or does it come down to sacrificing a phone to find those precious values for the right voltages, ...? Please shed some light on this for me, I never read a real answer from any dev out there.
3. On 4.1.2 we had this phantom kernel with a lot more CPU frequency steps. Some governors worked definitely better when they can scale over more frequencies. Maybe you can implement that?
stothegee said:
the first custom kernel for kitkat, thanks AJ!
1. dual recovery seems cool, but imo there is no real benefit when both of them do effectively the same. Again, great job that you managed to include both, but to me it becomes just "bloat". no offence.
2. I'm not a fan of overclocking but there are uses for better CPU/GPU controls. I would love to underclock and undervolt them to squeeze a little more battery out of my phone. God, it seems lots of those kids here care about their "gaming performance" and their "lagfree" "smoothness", but I use my phone as a phone and I don't give a sh... about that if I can get a couple more hours of use.
What's your opinion on this? Do you think we will ever get this working here like all the others (looking at those qualcomms and snapdragons in the other forums)? I mean we got more manufacturer sources than most of them, right? Or does it come down to sacrificing a phone to find those precious values for the right voltages, ...? Please shed some light on this for me, I never read a real answer from any dev out there.
3. On 4.1.2 we had this phantom kernel with a lot more CPU frequency steps. Some governors worked definitely better when they can scale over more frequencies. Maybe you can implement that?
Click to expand...
Click to collapse
1. Got many PMs asking for dual recovery so included it. And it won't slow down the boot process or make it laggy. Why?
If you extract the ramdisk you'll see that init.sh script controls the booting just like in CM(new builds)/AOSX. What the help of this script, ramdisk and recoveries are separately extracted so it doesn't extract and ramdisk or ramdisk-recovery until and unless the particular key assigned to it is pressed.
2,3. Honestly, I never looked at oc/uc, as I don't like playing with my CPU clock at all. Though I can try to integrate it and can only give a proper answer after trying
Cheers,
AJ
OK guys. I did read about OC CPU and various methods for our devices and basically all the kernels which say having OC aren't properly adding it. What they actually did was just adding CPU frequency names in the table in drivers/cpufreq/dbx500-cpufreq.c. Also it is quite hard(and maybe risky) to OC our kernel since I can't find the OC threshold anywhere. So it'd be better not to bring OC to it.
And about triple recovery, I won't be bringing it in this or kumquat kernel. DooMLoRD said that he wanted to keep it exclusive to DooMKernel and TBH I agree with him. He did put a lot of efforts in it and I respect his decision.
Cheers,
AJ
thanks for the amazing work
Build compiled from our CM branch sources with various optimizations / kernel features
Final build for 4.4.4 released (20th April 2015)
Many of the new features can be configured by kernel tools like Synapse. Install synapse app from market and UKM zip from downloads section.
We have moved on to Lollipop thread.
V7 [Changelog]
KERNEL:
- New hotplugs - ALUCARD, MSM
- MSM_limiter
- Fix synapse stuff - GPU etc..
- Governor tweaks
ROM
- Latest CM 11 sources.
- Fix chrome issues
- Fix button lighting-up when screen is off
Recommeded: Alucard governor with Alucard hotplug.
This is my synapse profile: http://goo.gl/3EbMUS
Note: For V6 and above (and specially for governors like zzmoove / alucard) , using Trickster/Synapse:
1. Disable MP-Decision
2. Enable intelli-plug
3. Enable intelli-thermal
4. And set to restore kernel settings on boot.
Old changelogs
V6 [Changelog]
- ROM sources updated to 20th November.
- Switch from O3 to Ofast [Even more compiler optimizations] and Re-enable Justarchi compiler optimizations [We have given up on exfat]
- GPU should now idle to 27MHz [instead of earlier 200Mhz]
- GPU overclocked to 535Mhz [earlier 500Mhz]
- CPU should now idle to 268Mhz (instead of earlier 300Mhz)
- Port few of my favorite governors from Oneplus one kernel these days - zzmoove and alucard: Both have been awesome for me (credits go to Oneplus one kernel developers - @Lord Boeffla, @ZaneZam, @alucard_24) - I will eventually start removing some of the older CPU governors. Looks like we have lots of them now.
- Various kernel patches - arch power, cpu boost, gentle fair sleepers, software crc is off
- Upgrade BFQ scheduler to BFQ-v7r6
V5.1 [Changelog]
- Newer sources from 20141107
- fsync is now disabled (Defers file writes but risk of data loss with crashes etc. Can be enabled in trickster)
- tweak intelliactive (hispeed freq was 2457, calm it down to 1985)
- voltage tweaks for speed 1 pvs 2
- default IO schd BFQ
- Frequency throttle limit increased slightly (Thermal policies can now be controlled through Trickster)
V5 [Changelog]
- Newer sources from 20141102 and use SaberMOD Toolchain, GCC 4.8.2 for kernel as well as entire build.
- Add a new hotplug engine - IntelliPlug (developed and used in famous Franco's Kernel) - I recommend to use this one, and switch off MP-Decision. (Enable in Trickster)
- Add a new thermal engine - Intellithermal (again from Franco) - Recommend to use this one. (Enable in Trickster)
- Add USB Fast charge (Enable in Trickster)
- Add another performance centric governor - SmartMAX (Combines features of OnDemand and SmartASSv2), Use it as gaming driver.
- Tweak intelliactive - Recommend to use this as default (Interactive is battery friendly but a bit laggy)
- Add powersuspend
- Reduce VM Swappiness to 10 (We have enough RAM)
- Some GPU tweaks
Other features
- CPU Overclocks of upto - 2457Mhz
- GPU overclocks of upto - 500Mhz
- Voltage control (UV)
- Additional CPU governors - Intelliactive, Intellidemand, InteractiveX
- Additional IO Schedulers - SIO, FIOPS, ZEN, VR
- Tweaked thermal policies (aggressive by default)
- Lower GPU clocks by default
- Reduced logging
- Net tweaks - Lock initial TCP window size to 64k
- FS tweaks disable atime and diratime
- Some mixer_paths patches (for higher audio) and button light fixes (to not glow on screen touch)
- Compiler optimizations
Branches(Github):
GCC4.8/Linaro/O3 related fixes/tweaks:
https://github.com/vikrant82/android_build
https://github.com/vikrant82/android_external_valgrind
https://github.com/vikrant82/android_external_fuse
https://github.com/vikrant82/android_external_exfat
https://github.com/vikrant82/android_art
Device tweaks
https://github.com/vikrant82/android_device_samsung_mondrianwifi
Kernel
https://github.com/vikrant82/android_kernel_samsung_mondrianwifi
Buttons Fix
https://github.com/vikrant82/android_frameworks_base
Downloads
Final release for 4.4.4
V444Final-20150419-SM482-Ofast-mondrianwifi.zip
UKM zip - UKM 3.6.1
Old releases
V6 ROM - V6-ROM-20141120-SM482-Ofast-mondrianwifi.zip
V6 Kernel - V6-Kernel-20141120-SM482-Ofast-mondrianwifi.zip
V5.1 ROM - V5.1-cm-11-20141107-SaberMOD-mondrianwifi.zip
V5.1 Kernel - V5.1-Kernel-20141107-Kernel-SaberMOD-mondrianwifi.zip
V5 ROM - V5-cm-11-20141102-SaberMOD-mondrianwifi.zip
V5 Kernel - V5-Kernel-20141102-Kernel-SaberMOD-mondrianwifi.zip
V4.1 (CPU 2457Mhz, GPU 500Mhz) - V4.1-cm-11-20140803-Linaro-O3-OC-mondrianwifi.zip
V4.1 Kernel (CPU 2457Mhz, GPU 500Mhz) - V4.1-cm-11-20140803-Kernel-Linaro-O3-OC-mondrianwifi.zip
V4.2 (CPU 2457Mhz, GPU 500Mhz) - V4.2-cm-11-20140809-Linaro-O3-OC-mondrianwifi.zip
V4.2 Kernel (CPU 2457Mhz, GPU 500Mhz) - V4.2-cm-11-20140809-Kernel-Linaro-O3-OC-mondrianwifi.zip
V4.3 (CPU 2457Mhz, GPU 500Mhz) - V4.3-cm-11-20140829-Linaro-O3-OC-mondrianwifi.zip
V4.3 Kernel (CPU 2457Mhz, GPU 500Mhz) - V4.3-cm-11-20140829-Kernel-Linaro-O3-OC-mondrianwifi.zip
Thanks @crpalmer @franciscofranco
XDA:DevDB Information
[SM-T320][ROM][KERNEL][4.4.4][-Ofast][SaberMod]CM11 [OC UV], ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
vikrant82
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-07-17
Last Updated 2015-04-19
excellent!
I'll try it later.
I always flash PurePerformances™X mod after every nightlie and it feels somewhat faster after it. I did flashed it on all my devices.
Maybe you can insert it in your future builds.
Keep them coming !
LE: mod link fixed
Thanks for this... Will give it a shot!
For anyone wanting to try this.. So far so good here. Hasn't been running long enough to make any major comparisons yet. Clean flashed, so not sure about dirty flashing.
I installed it over nightly and it runs pretty well but the playstore icons bug is pretty bad.
For now I moved on to the next nightly but if you can fix that bug I will surely flash it again.
csjneek said:
I installed it over nightly and it runs pretty well but the playstore icons bug is pretty bad.
For now I moved on to the next nightly but if you can fix that bug I will surely flash it again.
Click to expand...
Click to collapse
Should be fixed with Linaro 4.9 (thats next). Trying out a few more optimizations for next build (expect to post one on weekend).
vikrant82 said:
Should be fixed with Linaro 4.9 (thats next). Trying out a few more optimizations for next build (expect to post one on weekend). Target is to beat benchmark scores from stock.
Click to expand...
Click to collapse
Don't pay attention to benchmarks....
If you want to meet or beat stock, just turn off thermal throttling, enable all 4 cores and set performance as the governor. Make it a fair comparison...
Finally a linaro build!! Keep up the great work! Could you modify the kernel too? Overclock cpu and gpu would be awesome...
Gesendet von meinem SM-T320 mit Tapatalk
crpalmer said:
Don't pay attention to benchmarks....
If you want to meet or beat stock, just turn off thermal throttling, enable all 4 cores and set performance as the governor. Make it a fair comparison...
Click to expand...
Click to collapse
@crpalmer
I suppose we are talking about /etc/thermal-engine-8974.conf, /etc/thermal-engine.conf (symlinked to thermal-engine-8960.conf) and /etc/thermald.conf (symlinked to thermal-8960.conf) on cm builds. They seem to be using different set of values from stock.
Can't we not use these values/files directly-from/similar-to stock builds ? As the thermal engine libs and binaries we are directly picking from stocks ?
Is stock too aggressive or CM too defensive ?
Also noticed that these linked files are broken as well. (no thermal-engine-8960.conf and thermal-8960.conf). Some build script issues ?
vikrant82 said:
@crpalmer
I suppose we are talking about /etc/thermal-engine-8974.conf, /etc/thermal-engine.conf (symlinked to thermal-engine-8960.conf) and /etc/thermald.conf (symlinked to thermal-8960.conf) on cm builds. They seem to be using different set of values from stock.
Can't we not using these values/files directly-from/similar-to stock builds ? As the thermal engine libs and binaries we are directly picking from stocks ?
Is stock too aggressive or CM too defensive ?
Click to expand...
Click to collapse
I wasn't suggesting that you turn that off permanently, that's just what the stock ROM is most likely (automatically) doing when you run a benchmark. That's how you get a higher score, not how you have a better ROM...
My point being, don't worry about whether or not the scores are better, worry about the whole experience being better (which is very much is). On a phone of mine, CM was way more performant even though it scored less than half of stock's Quadrant score.
vikrant82 said:
@crpalmer
I suppose we are talking about /etc/thermal-engine-8974.conf, /etc/thermal-engine.conf (symlinked to thermal-engine-8960.conf) and /etc/thermald.conf (symlinked to thermal-8960.conf) on cm builds. They seem to be using different set of values from stock.
Can't we not using these values/files directly-from/similar-to stock builds ? As the thermal engine libs and binaries we are directly picking from stocks ?
Is stock too aggressive or CM too defensive ?
Also noticed that these linked files are broken as well. (no thermal-engine-8960.conf and thermal-8960.conf). Some build script issues ?
Click to expand...
Click to collapse
How is the new build? Linaro 4.9?
Gesendet von meinem SM-T320 mit Tapatalk
crpalmer said:
I wasn't suggesting that you turn that off permanently, that's just what the stock ROM is most likely (automatically) doing when you run a benchmark. That's how you get a higher score, not how you have a better ROM...
My point being, don't worry about whether or not the scores are better, worry about the whole experience being better (which is very much is). On a phone of mine, CM was way more performant even though it scored less than half of stock's Quadrant score.
Click to expand...
Click to collapse
I agree benchmarks are just academic (and just nice-to-have). I was just suggesting that we could use same thermal configuration files as found in stock builds. Are these even the files that would affect benchmarks (thermal-engine*.conf and thermald*.conf) ? Are you suggesting that stock build just shuts off any kind of throttling as soon as it detects benchmark tests ? I thought only some devices did that and they got caught.
I am building with linaro 4.9 and have swapped out those conf files from stock. Lets see how it goes.
vikrant82 said:
I agree benchmarks are just academic (and just nice-to-have). I was just suggesting that we could use same thermal configuration files as found in stock builds. Are these even the files that would affect benchmarks ?
I am building with linaro 4.9 and have swapped out those conf files from stock. Lets see how it goes.
Click to expand...
Click to collapse
Are the messed up icons fixed in play store?
iamnotkurtcobain said:
Are the messed up icons fixed in play store?
Click to expand...
Click to collapse
Expecting them to get fixed with this build. Lets see.
vikrant82 said:
Expecting them to get fixed with this build. Lets see.
Click to expand...
Click to collapse
I'll test as soon as it is available
iamnotkurtcobain said:
I'll test as soon as it is available
Click to expand...
Click to collapse
Unfortunately, Linaro 4.9 is breaking stuff. Getting into a bootloop n all. Need more time.
vikrant82 said:
Unfortunately, Linaro 4.9 is breaking stuff. Getting into a bootlock n all. Need more time.
Click to expand...
Click to collapse
Hope you can fix it!
iamnotkurtcobain said:
Hope you can fix it!
Click to expand...
Click to collapse
Been struggling with some adreno crashes on boot when using 4.9 toolchain. Earlier I thought it's the compiler optimizations not playing well with 4.9. But I run into same without any customizations -
Here's the logcat if anyone wants to take a look.
http://pastebin.com/eS0eHvzL
If I can't get around these in a day or two, we'll come back to 4.8 and carry on with other optimizations. I read somewhere the gibberish icons are fixed on newer play store.
vikrant82 said:
Been struggling with some adreno crashes on boot when using 4.9 toolchain. Earlier I thought it's the compiler optimizations not playing well with 4.9. But I run into same without any customizations -
Here's the logcat if anyone wants to take a look.
http://pastebin.com/eS0eHvzL
If I can't get around these in a day or two, we'll come back to 4.8 and carry on with other optimizations. I read somewhere the gibberish icons are fixed on newer play store.
Click to expand...
Click to collapse
Its probably the adreno libs built using older tool chains.
vikrant82 said:
Its probably the adreno libs built using older tool chains.
Click to expand...
Click to collapse
Just posted another build with today's sources with both CPU and GPU overclocks. Had to go back to older 4.8 toolchain. The overclocks are running surprisingly stable on device.
The playstore icons issue is still not resolved. Its being discussed here. However, I am not too worried by it.