{
"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"
}
Code:
#include
/*
* 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 modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
FEATURES:
-Based on latest sources
- Compiled off Linaro 4.9.3!
- Philz Recovery 6.48.4
-Insecured
-/system mounted as rw
-CPU Overclockable upto 1.7Ghz
-GPU Overclockable to 500Mhz
-Optimized RWSEM Algorithms
-LZO compression for faster boot
-Disabled GENTLE_FAIR_SLEEPERS
-Dynamic Fsync control
-Optimized AES and SHA1 routines
-Neon optimizations
-Removed old SHA1 routines
-Optimized git implementation for SHA1
-Lowered vfs cache pressure size to 20
-Enabled ARCH_POWER
-Optimizations to default SLUB allocator
-Patch for depleting entropy requiring no need of frandom or any rngd tweaks
-Tuned CFS parameters
-Asynchronous I/O latency to a solid-state disk greatly increased
-Optimized conservative governor
-Optimizations to Android lowmemorykiller
-Faster NOATIME and NODIRATIME fs mounting flags
-CPU Voltage Control
-Lowered log buffer shift
-O3 Optimizations
-Optimized apply_slack() method for size and speed
-Lock initial TCP window size to 64k (Improves network ping and output)
-Dynamic management of dirty page writebacks
-Philz recovery
- Introducing Intelli_thermal - A new thermal protection mechanism ported to MSM8930 by me, originally developed by faux123 (Replaces stock msm_thermal)
- Introducing ThunderSonic Sound Engine - A sound control driver wholly developed by me
- Introducing Charger Control 2.0 - A charger current rate control driver wholly written by me
- Nullified all the RAM and battery issues by disabling some unnecessary stuff!
- Added zSwap from Linux 3.11 [More RAM love? ]
- Added frontswap
- Added vnswap - a virtual swap page file residing the RAM memory pool.
- Disabled FRAME_POINTER slowing down the kernel
- Added Intelli_active governor
- Tuned the kernel for Cortex-A15
- Disabled lots of debugging
- Added native LZ4 compression support
- Added full support for Android Kitkat in separate version
- Fixed second core frequency overiding issue
- Now powered by AROMA Installer
- Disabled proc fs config storage swelling the kernel
- Added generic input joystick support
- Loads of other code cleanups and arbitrary optimizations
- Introduced in GPU Voltage Control
- Added BFQ IOScheduler
- FIOPS IOScheduler
- Added Assload of new TCP Congestion controls
- Improved IO throughput
- Merged some writeback patches to improve vmscan module
- Added native Samsung F2FS filesystem support
- Linux MM Readahead set to 256k
- Recovery some RAM by reducing android logger memory allocation
- Patches to improve deep sleep
- Disabled useless userspace and powersave governors
- Switched to XZ kernel compression
- Removed ARM tracer debug code
DOWNLOAD:
Mirror 1
GPL Compliance:
http://bit.ly/1cypvyz
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to this kernel. If you want to include my kernel in your project or use my source code, please mention it in your post, give proper credits.
Opensource does not mean 'Out-of-credit'
Thank you.
Credits:
@DD-Ripper : For amazing logo design!
@faux123- For his various kernel patches and features.
And all others mentioned on my github in contributors tab.
XDA:DevDB Information
ThunderZap Kernel, Kernel for the Sony Xperia L
Contributors
varun.chitre15
Kernel Special Features: Stability coupled with Velocity!
Version Information
Status: Stable
Created 2013-09-22
Last Updated 2015-08-29
Reserved
ThunderZap 4.9 - November 7
Code:
- Compatibility with CM12 beta 2
- SELinux enabled and set to permissive
ThunderZap 4.8-r2 - Not released
Code:
- Fix un-bootability issues with some phones
- 1.7 Ghz OC now available for Kitkat variant too
- SELinux enabled and set to permissive
ThunderZap 4.8 - November 22
Code:
- Lollipop compatibility
- ThunderSonic Engine 2.0 - Implemented locking mechanism
- Pushed CPU Clock to 1.7Ghz - (Lollipop only)
- Merged Lollipop patches from CAF
- BFQ IOScheduler updated to v7r6
- Optimized Low memory killer to reduce aggressiveness
- Memory management patches from Nexus 6 kernel
- CPUFreq optimizations from Nexus 6 kernel
- Patches to TCP from upstream
ThunderZap 4.7 - September 14
Code:
- Updated exFAT to latest upstream version
- Huge bunch of Samsung F2FS updates
- TWRP 2.8.0.0New
- Philz Touch 6.57.5 Updated
- Dual recovery is here!New - TWRP+Philz Touch
- Fixed in-recovery 1970 timing mismatch
- Optimizations to cpufreq driver
- New governor: SmartMax: This is my new favorite governor, an ideal choice for optimum performance and battery backup
- New IOScheduler: TripNDroid: My second favorite scheduler after BFQ!
- Optimized GPU flags
- Sysfs interface to control GENTLE_FAIR_SLEEPERS on the fly
- BFQ scheduler optimized for SSD
- Disabled add_random method for improved IO performance
- Moved to Linaro 4.7 from Linaro 4.6
- Enabled aggressive multi-core power savings
- Updated base CAF sources with over 100 new patches that go to VIDC, Adreno GPU driver, qssecom daemon, touchscreen driver etc
- Updated wifi driver from latest CAF sources
- Speedup in /proc/net/unix access
- Optimizations to ext4 filesystem from upstream.
v4.6 - July 10
Code:
Introduced in GPU Voltage Control - instructions on Post #3
- Pushed CPU clock to 1.6Ghz
- Added BFQ IOScheduler v7-r5 (my favorite one)
- Brought back FIOPS IOScheduler
- Added Assload of new TCP Congestion controls
Code:
* .westwood (default)
* .reno
*. bic
*. highspeed
*. hybla
*. htcp
*. vegas
*. veno
*. scalable
*. yeah
*. lp
*. illinois
- Improved IO throughput
- Merged some writeback patches to improve vmscan module
- Added native Samsung F2FS filesystem support
- Linux MM Readahead set to 256k
- Recovered some RAM by reducing android logger memory allocation
- Patches to improve deep sleep
- Disabled useless userspace and powersave governors
- Switched to XZ kernel compression
- Removed ARM tracer debug ****
- Philz touch updated to 6.48.4
- Merged all CAF kernel changes
- Compatibility to latest CM releases(model number issues)
v4.5-r1 - June 16
Code:
- Merged in all CAF kernel changes
- Philz touch updated
- Compatibility with new CM build
v4.5 - June 14
Code:
- Added compatibility for Kitkat
- CPU freq down to 1.5Ghz
- Philz recovery
- Updated wifi driver
- Updated CAF source to Android 4.4.3
- Fixes to Thundersonic Engine for future app compatibility
- Removed some unused features, rest all features intact!
v4.1-r2 - Mar 20
Code:
- Added compatibility to CM11-M4
- [Color="Red"]Workaround for internal storage - Now you can have full access to your internal storage at a new mount point in /storage/sdcard2! on any 4.4 ROM
[/Color]
v4.1 - Mar 10
Code:
- Removed GPU OC, ROW & FIOPS IOscheduler
- Updated TWRP to latest 2.7.0.0
- TWRP : Working implementation of reboot recovery
- Fixed the shutdown and logolooping problems
v4.0 - Mar 06 - Major release
Code:
- Introducing Intelli_thermal - A new thermal protection mechanism ported to MSM8930 by me, originally developed by faux123 (Replaces stock msm_thermal)
- Introducing ThunderSonic Sound Engine - A sound control driver wholly developed by me
- Introducing Charger Control 2.0 - A charger current rate control driver wholly written by me
- Nullified all the RAM and battery issues by disabling some unnecessary stuff!
- Upgraded sources to 3.4.82 [More than 3000 new improvements]
- Added SELinux support
- Overclocked upto 1.7Ghz - With the second core overiding issue almost vanished we don't have any issue with higher OC
- Added support for Microsoft XBox 360 Xpad controller (experimental)
- Added zSwap from Linux 3.11 [More RAM love? ]
- Added frontswap
- Added vnswap - a virtual swap page file residing the RAM memory pool.
- Disabled FRAME_POINTER slowing down the kernel
- Asynchronous Fsync from HTC kernels
- Added Intelli_active governor
- Added ROW IOScheduler
- Added FIOPS IOScheduler
- GPU OC upto 533Mhz
- Enabled hardware real-time clock write access - Fixes mismatched timestamps in recoveries and their backups
- Tuned the kernel for Cortex-A15
- Disabled lots of debugging
- Added native LZ4 compression support
- Added full support for Android Kitkat in separate version
- CD-ROM emulation via sysfs lun file (Thanks to @FrozenCow)
- Fixed second core frequency overiding issue
- Added TWRP 2.6.3.0(latest) in separate version
- Updated CWM to 6.0.4.7(latest)
- Now powered by AROMA Installer
- Disabled proc fs config storage swelling the kernel
- Added generic input joystick support
- CWM Recovery changes: Completely working reboot recovery implementation
- Loads of other code cleanups and arbitrary optimizations
v3.1 - Dec 28
Code:
- Disabled Memory compaction - should fix overusage of RAM issue
- Optimized and reduced voltage table by 62mV
- Merged 15.3.A.1.12 sources - Kernel is now future compatible with the new firmware
- Boosted the display panel frame-rate slightly for more smooth UI
- Added back the Westwood TCP Congestion control and set it as default - Should manage all Network traffic more efficiently!
v3.0 - Nov 28
Code:
*. Major update - Read changelog [URL="http://forum.xda-developers.com/showthread.php?p=47935391"]here[/URL]
v2.0-rc1 - Aug 07
Code:
*. Voltage table fixed causing phone freeze
v2.0 - Aug 03
Code:
*. Initial release
FAQs
Well lets begin, almost all features can be controlled using the TricksterMOD
How to access recovery?
Keep pressing volume down button when you see Thunderzap logo
Now special things about this!-
1. You can also use camera key to boot into recovery! hell yeah! BUT remember, NOT to use it for your first recovery boot. Make first recovery boot only using vol down key! Remember this. If you do so, phone will stuck up on ThunderZap logo and your key combo will get swapped and remapped to Volume up and you would need to use Vol up to boot into recovery until the next kernel flash.
2. You can also reboot to recovery from your Android OS directly! Yes I have done it! But same criteria as above! not to use that way for first boot. After you are done with first recovery boot you can use camera key, terminal way anytime!!
So how to use the terminal way?
Open terminal emulator[NOT adb shell]
Gain su permissions and type
Code:
start-cwm
And within a minute you will be in CWM!
How to determine which TCP congestion to use??
Latency - Download - Upload
cubic:
1st run: 15ms - 10,75Mbps - 7,82Mbps
2nd run: 14ms - 10,84Mbps - 8,06Mbps
reno:
1st run: 13ms - 15,51Mbps - 6,73Mbps
2nd run: 13ms - 14,73Mbps - 8,51Mbps
bic:
1st run: 12ms - 10,38Mbps - 8,61Mbps
2nd run: 13ms - 10,78Mbps - 8,62Mbps
westwood:
1st run: 11ms - 17,65Mbps - 8,30Mbps
2nd run: 13ms - 13,28Mbps - 8,29Mbps
highspeed:
1st run: 13ms - 10,76Mbps - 7,94Mbps
2nd run: 16ms - 14,42Mbps - 8,52Mbps
hybla:
1st run: 14ms - 11,19Mbps - 7,44Mbps
2nd run: 14ms - 13,47Mbps - 7,56Mbps
htcp:
1st run: 14ms - 13,24Mbps - 7,03Mbps
2nd run: 15ms - 10,85Mbps - 8,00Mbps
vegas:
1st run: 14ms - 8,49Mbps - 6,62Mbps
2nd run: 14ms - 12,00Mbps - 7,07Mbps
veno:
1st run: 13ms - 9,58Mbps - 8,13Mbps
2nd run: 13ms - 8,50Mbps - 7,64Mbps
scalable:
1st run: 18ms - 12,01Mbps - 8,73Mbps
2nd run: 14ms - 13,96Mbps - 8,23Mbps
lp:
1st run: 14ms - 14,90Mbps - 8,68Mbps
2nd run: 14ms - 13,44Mbps - 8,72Mbps
yeah:
1st run: 14ms - 13,37Mbps - 8,28Mbps
2nd run: 17ms - 13,89Mbps - 8,14Mbps
illinois:
1st run: 13ms - 12,93Mbps - 8,24Mbps
2nd run: 16ms - 13,97Mbps - 6,46Mbps
Click to expand...
Click to collapse
See above chart and decide which to use! But westwood has been set as default!
Some of them from above chart won't be present, so watch only those which are present in feature list.
Q. How to use vibration intensity control?
echo "your-value" > /sys/devices/virtual/timed_output/vibrator/level
Values range is 12-31. None other
Q. How to use ThunderSonic Engine?
It is a sound control driver. There are two interfaces which you can control
1. Headphone boost - I made this feature because louder volume than max volume in earphones rushes more adrenaline in me making music more enjoyable.
Turning this On will give you instant significant volume boost in earphones which is greater than what you get when the volume is max. Just make the volume maximum and turn this ON and you will notice it
How to turn on:
In terminal emulator/ adb shell, get su permissions and then type
Code:
echo 1 > /sys/kernel/thundersonic_engine/headphone_boost
and use 0 to turn off
2. Speaker boost - In crowded areas I felt speakers of XL fall short in terms of volume magnitude. So I made this to increase speaker volume speakers beyond its limit and now my phone sounds even louder than those dirt cheap china phones
This is 8-leveled boost interface. That means there are 8 boost levels. The default is 3 on TZ
How to turn on
Code:
echo X > /sys/kernel/thundersonic_engine/speaker_boost
where X can be any value from 4 to 8 depending upon the volume boost you require To reset back to default use value 3
Use above features with caution. Using headphone boost for a long time may damage your ears. And do not use speaker boost for a long time. If for some songs you hear crackling of speakers then reset its boost level to 3 or a relatively lower level of 4 or 5
Q. How to use charger control?
1. AC current control: In times of hurry I felt the charging times to be too long and so I made this. With this you can control the charging current rate through wall charger.
Before doing anything you first need to enable the master switch of the control or else the values you write will be negelected
How to enable master switch
Code:
echo 1 > /sys/kernel/charger_control/enabled
After this you can use custom current values like this
Code:
echo X > /sys/kernel/charger_control/custom_ac_current
where X can be any value in mA (Milliamperes) I use 1600 i.e 1600mA which completes my phone's charging from 3% to 100% in around 1 hour 30 mins.
The stock current ranges from 1000-1100mA and takes around 2 hour 30 mins to 3 hours. Avoid using values higher than 2200.
2. USB current control: Everyone knows the charging rate from PC via USB is damn slow. Many new PC's have newer USB ports which can offer current rates higher than 1500mA but still our kernel only pulls 500mA. I made this to control it yourself
As usual you need master switch enabled to write the new values.
How to use
Code:
echo X > /sys/kernel/charger_control/custom_usb_current
where X can be any value in Milliamperes. I use 1500 i.e 1500mA
Q. How to use GPU Voltage Control?
Currently there are no GPU voltage controlling apps. The upcoming ThunderZap control app supports that.
Obtain current voltage values
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_mv_table
Output will be something like this:
945 mV
1050 mV
1150 mV
Change these values:
Code:
echo "930 1000 1100" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_mv_table
This will change the voltages as below
930 mV
1000 mV
1150 mV
Q. I am having abnormal battery drain
Most of the time the kernel isn't responsible for this.
a) Make sure you are on stock frequency of 1Ghz. Sometimes the frequency is getting overridden to 1.5Ghz even if you didn't set that. To avoid such situations use frequency lock option from Trickstermod kernel app.
b) The kernel is not pre-undervolted any more. You can undervolt it on your own. Optimum value is 75mV. Don't undervolt more than that
Q. How to use extra modules provided
Best way is to use init.d script to load them on boot.
e.g If you want to use the NTFS file system module. You have to first place the ntfs.ko module provided in /system/lib/modules. Then you need to create an init.d script in /system/etc/init.d with any name say 99modules with following code
Code:
#!/system/bin/sh
insmod /system/lib/modules/ntfs.ko
Next you need to give that file all permissions and reboot the phone and you are done!
P.S: Loading external modules affects battery life of the phone.
reserved
Good work.
All the best.
Good job man.
Best of luck! :highfive:
Post #3 updated with all controlling stuff!
Enjoy!
I've some concerns :-
1) As you can see from screenshot, default boot frequency of cpu0 is 1188 MHz while of cpu1 jumps to 1566MHz on load.
This is one of few reasons I disabled overclock in my kernel. One should enable intelliplug and disable mp decision to fix this.
Code:
su
stop mpdecison
2) Eco-Mode? Isn't it for quad core devices? Turning it off disables two cores. And we've only two.
3) Intelliplug works well.
4) Your voltage table is wrong. 1242MHz runs at lower voltage than 1188MHz. It's also irregular.
for example all 384,432,486 MHz run at same voltages.
5) Your ramdisk.cpio contains another ramdisk.cpio + pack script. Remove these junks.
6) xz -e offers best compression ratio but it's way slower than lzop (which in turn has poorest compression ratio).
So, xz compressed kernel is light weight but takes longer time ( usually 3-4 seconds more to decompress fully) than lzop compressed one.
You can see benchmark comparsion of gzip,xz,lzma etc here
In all xz compressed kernel doesn't boot fast in any way.
That's it for now
Rachit Rawat said:
I've some concerns :-
1) As you can see from screenshot, default boot frequency of cpu0 is 1188 MHz while of cpu1 jumps to 1566MHz on load.
This is one of few reasons I disabled overclock in my kernel.
2) Eco-Mode? Isn't it for quad core devices? Turning it off disables two cores. And we've only two.
3) Intelliplug works well.
4) Your voltage table is wrong. 1242MHz runs at lower voltage than 1188MHz. It's also irregular.
for example all 384,432,486 MHz run at same voltages.
Click to expand...
Click to collapse
1. True (I will be releasing a 1.2Ghz version of kernel tomorrow who are not that much concerned with gaming)
2. This is true as well. But this works with dual core too according to my last 20 days testing and I have noticed gradual improvement in battery backup. I will contact faux123 to reconfirm my observations.
4. Thanks! Didn't observe that. Will fix it with tomorrow's minor update
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
@Rachit Rawat
Quick fix for the issue 1 of cpu1 getting maxed out!
Do this- Change freq to any other step and put it back to original. Now try doing a heavy task and see where cpu1 is getting capped at!
Just try it out
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
varun.chitre15 said:
@Rachit Rawat
Quick fix for the issue 1 of cpu1 getting maxed out!
Do this- Change freq to any other step and put it back to original. Now try doing a heavy task and see where cpu1 is getting capped at!
Just try it out
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
why not just turn on intelliplug and disable mpdecision?
Rachit Rawat said:
why not just turn on intelliplug and disable mpdecision?
Click to expand...
Click to collapse
I already have done that and I saw the maxing out of cpu1 myself right after you posted even though I have intelli_plug on
The trick I mentioned fixed that
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
May I ask for a simple explanation concerning intelli_plug?
So it is a hotplug alternative, that means it switches unused cpu-cores off. Which results in same speed and half battery - consumption in cost of stability if cpu is in heavy use? And Eco-mode keeps the second core switched off permanently, or nearly?
If I am getting this correctly, then we transform our device into a single-core phone (which would be good itself, we can easier the cpus use with greenify to reduce background processes, right?).
My questions are:
Can that harm the processor (if we dont overclock?) and
if we do not use Eco-mode, will we have the single-core-effect and lagfree games?
Greets
Sent from my C2105 using xda premium
keenofhiphop said:
May I ask for a simple explanation concerning intelli_plug?
So it is a hotplug alternative, that means it switches unused cpu-cores off. Which results in same speed and half battery - consumption in cost of stability if cpu is in heavy use? And Eco-mode keeps the second core switched off permanently, or nearly?
If I am getting this correctly, then we transform our device into a single-core phone (which would be good itself, we can easier the cpus use with greenify to reduce background processes, right?).
My questions are:
Can that harm the processor (if we dont overclock?) and
if we do not use Eco-mode, will we have the single-core-effect and lagfree games?
Greets
Sent from my C2105 using xda premium
Click to expand...
Click to collapse
No, let me try.
Hotplugging means plugging out second core when not needed and plugging it in back when phone is doing some heavy work.
Consider few situations.
1. You are using a mere app like Instagram. In this case there is no need of second core and only first core can process the app smoothly. Here the second is asked to go offline and only first core runs.
2. Now you open NFSMW which is a heavy game. Now the phone understands that there is situation of heavy load, so it plugs in second core that is asks it go online and start sharing the workload from first core.
So this mechanism was managed by mpdecision named service previously. Intelli_plug is alternative mechanism to it. It is more efficient than mpdecision. That is improved algorithms of detecting whether second CPU is really needed or no. It determines that very intelligently and performs a very quick action providing much smoother User experience.
Now ECO-Mode , it just makes intelli_plug a bit lazy. It avoids plugging in second core for many situations and forces first core to do all work as far as I observed. It does plug in second core when phone is in very need of it. This saves a lot of battery.
And no, these features do not cause any harm to hardware because mpdecision does same thing but inefficiently.
I hope everything is clear here.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
varun.chitre15 said:
No, let me try.
Hotplugging means plugging out second core when not needed and plugging it in back when phone is doing some heavy work.
Consider few situations.
1. You are using a mere app like Instagram. In this case there is no need of second core and only first core can process the app smoothly. Here the second is asked to go offline and only first core runs.
2. Now you open NFSMW which is a heavy game. Now the phone understands that there is situation of heavy load, so it plugs in second core that is asks it go online and start sharing the workload from first core.
So this mechanism was managed by mpdecision named service previously. Intelli_plug is alternative mechanism to it. It is more efficient than mpdecision. That is improved algorithms of detecting whether second CPU is really needed or no. It determines that very intelligently and performs a very quick action providing much smoother User experience.
Now ECO-Mode , it just makes intelli_plug a bit lazy. It avoids plugging in second core for many situations and forces first core to do all work as far as I observed. It does plug in second core when phone is in very need of it. This saves a lot of battery.
And no, these features do not cause any harm to hardware because mpdecision does same thing but inefficiently.
I hope everything is clear here.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
nice kernel varun
one question
Can i turn off both intelli-lug and mpdecision at same time ? and i cant see any setting for intelli-plug in trickstermode i mean how can i turn it off , only MPdecision setting is der
Thanks
naitik2012 said:
nice kernel varun
one question
Can i turn off both intelli-lug and mpdecision at same time ? and i cant see any setting for intelli-plug in trickstermode i mean how can i turn it off , only MPdecision setting is der
Thanks
Click to expand...
Click to collapse
Don't turn both of them off, you will face heavy battery drain. Turn off mpdecision and turn on intelli_plug
And switch for intelli_plug is there in trickstermod in special tab.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
@varun.chitre15 can you upload to mediafire? I have problems downloading from goo.im
Sent from my C2105 using xda premium
PayPal Donations
please do the following:
Sign in to your PayPal account page
Go to 'Send Payment'
Enter my email id "[email protected]"
option "Personal payment" doesn't work for India, please set "Online purchases". and check Goods or Service (preferably service)
Make the payment of the desired amount of donation you want to send.
Thank you for your kind donations!
Super kernel
varun.chitre15 said:
Click to expand...
Click to collapse
Super stable. Reserved for more detailed review :laugh:
varun.chitre15 said:
I have mirrored the kernel on dev-host.
Check first post.
Sent from my Sony Xperia L (C2104) using Tapatalk 4 beta
Click to expand...
Click to collapse
one more thing
Any news about JetMode ?
Related
[KERNEL] [2.6.32.24] [HAVS] [BFS] [BFQ] KiNgxKernel #11/#11 "Con is an Artist"
I DO NOT have an HTC Evo, but would LOVE to have one for development, and am saving for one. Bear with me until then I just wanted to say thank you to the few who have donated. I am almost there, any help is appreciated!!! I plan to have my HTC Evo fairly soon
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
So, just as the name implies, this is an Evo kernel with SVS (Static Voltage Scaling) & HAVS (Hybrid Adaptive Voltage Scaling.) A huge thanks to estes for the havs code and raven for being the first to implement it into the nexus kernel. What this does is provide SUPERIOR BATTERY life with stability to boot. Just flash the .zip in your favorite recovery image. Enjoy and post any bugs with a logcat please.
This is compatible with any 2.2 Sense ROM
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
Code:
While we are at it, some info on BFS:
What is BFS(Brain **** Scheduler):http://ck.kolivas.org/patches/bfs/sched-BFS.txt
FAQS about BFS:http://ck.kolivas.org/patches/bfs/bfs-faq.txt
nugzo said:
I have full adb. I didnt have it when i upgraded from previous king kernels. Had to do a full wipe. Reinstalled rom and installed kernel before rebooting. adb works perfect. full access.
Click to expand...
Click to collapse
ENJOY!
Credits: Cyanogen, Netarchy (epson fps panel fix), toastcfh, ffolkes - all for bits of their code (see changelog), Koush for his any kernel .zip, AssasinsLaminent (nova fix), and most importantly, HTC for their kernel source
Download: CFS Kernel #11 & BFS Kernel #11[/URL] Date: 10/28/10 9:40 PM PST
If you Like my work follow me on twitter:
All my code is on github:
I am not responsible for anything that happens to your device
ChEeRs
BFS Changelog
Kernel #11
- HAVS is now OUT. We are not currently using it
- Using SVS for voltage regulation at the moment
- Battery life should be great now
- I forgot about an awful lot of longs and ints that will overflow on 32 bit now with u64 deadlines. Fix them.
- Add some macro tidiness
- Make sched_clock sanity checking robust and standardised, using jiffy
difference as upper limit, and use nominal 1us when difference cannot be
trusted.
- In layman's terms these are all MAJOR fixes to his BFS scheduler
- These fixes will provide a performance and stability boost
- Higher clockspeeds are more stable!
- More I will add
Kernel #10
- Performance boost!
- More stable due to BFS overhaul
- Patched up BFS scheduler to BFS 330
- Patched in *NEW* BFS TEST patch that applies over 330 (from CKolivas himself)
* Major overhaul of queued changes
* Micooptimise multiplications/divisions to be shifts where suitable
* Drop the "skip_clock_update" concept as we update the niffies each time we
update the rq clocks, thus we want to update it more often
* Add a local last_task variable to each runqueue which keeps a copy of the
last non-idle task that ran on this CPU. Use this value to determine that a
task is still cache warm on this CPU even if it has run elsewhere in the
meantime. This improves throughput on relatively idle systems with >2 logical
CPUs
* Change SCHED_BATCH tasks to refill timeslices and reset deadline every time
they're descheduled as they've been flagged as latency insensitive, likely
fully CPU bound tasks. This should decrease the impact running batch tasks
has on other tasks
* Bypass rechecking deadline when we know that prev will run again in schedule
* Change all deadline accounting to use nanosecond values
* Rework try_preempt
* MUCH MUCH more check my patch code if you please
- Voltage tweaks for stability
- Compiled with toolchain optimizations
- Neon optimizations this time around
Kernel #9
- Finally released
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- You guys are going to like this one
Kernel #8
- Reverted BFS Scheduler to 318
- Reverted GPU changes causing stutters
- Other minor fixes
Kernel #7
- Updated BFS Scheduler all the way up to 330
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- More I will add
Kernel #6
- Minor code cleanup
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- Other things I will add
Kernel #5
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- More I will add
Kernel #4
- BIG update
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- More I will add
Kernel #3
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
Kernel #2
- Updated BFS Scheduler all the way up to 318
- Manual patches made by me to successfully get it working 100%
- Minor bug fixes
- Things I'll add
Kernel #1
- Fresh sources
- FAST
- Based off of CFS Kernel #7
- Applied BFS 313 (Brain **** Scheduler by Con Kolivas)
- HAVS implemented
- Minor bug fixes
CFS Changelog
Kernel #11
- Kernel now patched up to 2.6.32.24
- Bug fix causing battery drain
- Reverted some UV levels causing instability
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
* sched: Fix granularity of task_u/stime()
* sched, cputime: Introduce thread_group_times()
* sched: Fix select_idle_sibling()
* sched: cpuacct: Use bigger percpu counter batch values for stats counters
* sched: fix racy fair sched*trq
* sched: Cleanup select_task_rq_fair()
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
* ext4: Consolidate inlign pages
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
* mutex: Don't spin when the owner CPU is offline or other weird cases
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
- SLAB fixes
- drm: Only decouple the old_fb from the crtc is we call mode_set*
- arm fixes: arm: fix really nasty sigreturn bug
- RDS memory leak fixed
- mm: page allocator: update free page counters after pages are placed on the free list
- mm: page allocator: calculate a better estimate of NR_FREE_PAGES when memory is low and kswapd is awake
- So much more, check my code if you please
Kernel #10
- Patched up to Linux Kernel version 2.6.32.17 (all commits an android kernel would need, no extra bloat) *All credit goes to the linux project, check my github for authors please*
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- Much more I will add
Kernel #9
- Board files fixed to allow lower undervolt
- Undervolted to 825Mhz for safe frequencies
- Higher clockspeeds WILL be more stable now
- Compiled CIFS module per request
- Regulator tweaks
- Removed some bloat
- Now using ondemand governor by default, feel free to change it
- Battery charging tweaks (like my inc kernel)
- MANY fixes to HAVS code *thanks for some of them netarchy*
- Regulator being properly used now
- Usleep fixes for sleep mode *via nnode*
- Longer battery life as a result of these major changes
- Volume boost tweaks
- Torture test disabled
- Torture test support disabled
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #8
- Added BFQ I/O Scheduler
- Default scheduler is bfq
- Fixed atomic functions in bfq *thanks cyanogen and co*
- Cleaned up/removed unneeded code
- HAVS is still included and functioning
- Code cleanup
- Undervolted even more (Battery life is LONG)
- Compiled with neon optimizations
- Conservative governor threshold tweaked (via netarchy)
- Conservative Governor sampling rate tweaked per user request
- GPU edits for performance
- 5MB of memory reserved for the Adreno GPU
- Kernel will boot faster as a result of "set read ahead" changes
- Various wifi module tweaks
- Packet Filtering set to turn off after 1s
- Bluetooth sleep bug fixed *via kmobs via kernelzilla*
- Rpc changes/tweaks
- V4L2 code disabled now for media interface
- Vmalloced tweaks via @cyanogen *PERFORMANCE BOOST*
- Tweaks for stability
- Now undervolted to 825Mv! *Longer batter life*
- Ksgl tweaks for performance
- Higher clock speeds should now be more stable
- Wifi module tweaks
- More I will add
Kernel #7
- Added new CPU Governor - 'Interactive Governor' thanks Mike Chan @google
- Still using Conservative Governor
- Now overclockable to speeds up to 1.26Ghz (Not all phones can run 1.26, if your phone locks up, OC lower)
- Bluetooth tweaks (double check that bluetooth works for me please)
- Even more undervolted
- Wireless 'n' support
- Switched to 'cfq' scheduler
- Open VPN Modules
- Other things I will add
Kernel #6
- Overclocking should be 100% functioning
- SetCPU works now
- Overclockable up to 1.113 (Will raise this number soon )
- Added CPU Governor "OnDemand"
- Added CPU Governor "UserSpace"
- Added CPU Governor "Performance"
- Added CPU Governor "Conservative"
- Default CPU governor changed to "Conservative"
Kernel #5
- Five point multitouch (thanks for the code ffolkes)
- ADB working for most.... (wierd)
- Speed tweaks
- CPU Governors updated
- CPU tables updated
- Code is live
Kernel #4
- Much faster
- Much smaller kernel, removed all bloat
- ADB should work now, let me know
- Overclocking should work, let me know
- Switched scheduler to deadline
- More audio tweaks (per request, I forget who asked)
- Included a slew of modules, should cover any module you'd need
- More I will add
Kernel #3
- OC capability should work via terminal
- Netfilter (Wifi tether) built into the kernel
- Added OnDemand CPU governor
- Added UserSpace CPU governor
- Added Conservative CPU governor
- Default governor is currently OnDemand
Kernel #2
- Speed boost
- Five point multi touch support (believe this was ffolkes, thank you)
- FPS unlocked now! (thanks toast)
- Audio Boost Tweaks (LOUD)
- Integrated code to use 3 point for sensors that do not support 5 (thank you ffolkes)
- Kernel should work on CM6 now (let me know)
- Kernel should now detect screen arch on boot (thanks cyanogen)
- Should support both epson and n
- OC Capable now - up to 1.26 Ghz!
- Voltages lowered significantly for even better battery life
- Changed default scheduler to cfq
- Cleaned up unneeded code
- More I will add
Kernel #1
- First kernel for the HTC Evo
- Based off of the HTC source code - 2.6.32.12
- Added drivers for Static Voltage Scaling (SVS)
- Added drivers for Hybrid Adaptive Voltage Scaling (HAVS)
- Using CFS
- No OC capabilities as of now
- Cameras should work fine
- WiFI should work fine
- Bluetooth should work fine
- All things you would expect to work should be working, let me know
Any chance we could see some of the Desire's audio values in this kernel?
neckface said:
Any chance we could see some of the Desire's audio values in this kernel?
Click to expand...
Click to collapse
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
kingklick said:
You evo users have no idea what HAVS is like
Click to expand...
Click to collapse
Well, for me, I have no idea what it is at all lol
Mind explaining what it does plz? =P
kingklick said:
if I can find the code for it, yes.
You evo users have no idea what HAVS is like
I can't wait to see the feedback
Click to expand...
Click to collapse
If you don't find it before I get home, I'll pm the directory to you.
And yeah, I haven't a clue what that is. Lol
This is interesting... any more details?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
What on Earth is HAVS?
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
david279 said:
after a little googling...
Hybrid Adaptive Voltage Scaling (HAVS)
Click to expand...
Click to collapse
MMhhh can't wait to try this one out
Is FPS unlocked on this?
Does this work for all 2.2 roms?
bigant262 said:
Is FPS unlocked on this?
Click to expand...
Click to collapse
as of now, most likely not. It can easily be implemented
jaysmi32 said:
Does this work for all 2.2 roms?
Click to expand...
Click to collapse
YUP! should have no issues
If one was to push this to their device on top of whatever custom kernel/rom running.. would things start to get messy?
whats the best recommendation ?
kingklick said:
as of now, most likely not. It can easily be implemented
YUP! should have no issues
Click to expand...
Click to collapse
Thanks for the quick reply. I'll wait until you put it in. Will look forward to updates on this.
ok guys kernel is live =)
let me know if you have any other questions
I'm done playing for the day but I'm def keeping an eye on this thread. I can't wait to see some real world test results. I have a feeling this thread is going to blow up by the time I get up in the morning.
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
cosine83 said:
While I would absolutely love HAVS, I also don't want to lose the modifications in netarchy's kernel with the FPS cap unlocked. Any way you could possibly integrate that into your kernel?
An update.zip would be grand, too.
Click to expand...
Click to collapse
Yup, if he sends me his code
HondaCop said:
I have netarchy kernel 4.0.3a with Fresh 3.1.0.1... can i simply flash this over it?
- Sent via my EVO 2.2 (Fresh 3.1.0.1) from the back seat of your Momma's car.
Click to expand...
Click to collapse
yes, use fastboot to flash the kernel itself, then adb push the modules
Kernel Files:
Change Log: http://faux.androidro.ms/pyramid/ics/changelog.txt
******* LATEST BETA By YANK555 with AROMA! Ice Cream Sandwich (Android 4.0.x) ******* (Linux 3.0.37)
[ CFS ] (Ultimate Edition)
http://forum.xda-developers.com/showpost.php?p=29072369&postcount=7579
******* Ice Cream Sandwich (Android 4.0.x) ******* (Linux 3.0.42)
[ CFS ] (Ultimate Edition)
The File ==> Sensation Kernel (1.73 GHz, GPU @ 320MHz, ZRAM) <==
******* Gingerbread (Android 2.3.x) ******* (Linux 2.6.35.14)
[ CFS ] (Mainline Edition)
The File ==> Sensation Kernel 029 (1.73 GHz, ZRAM) <==
[ CFS ] (Ultimate Edition - should work with most phones but NOT GUARANTEED!)
The File ==> Sensation kernel 029 (1.73 GHz, ZRAM, ZCACHE, GPU @ 320MHz) <==
[ Optional: ]
[ For Kernel Devlopers ONLY: ]
The File ==> My Global VDD_TABLE for under volt patch <==
The File ==> KGSL Ring Buffer Power Management Patch for Cordy and Ninja Jump <==
Optional Under voltage: Version 0.1.4+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table Example
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Optional: Stock Clock Frequencies for Dual CPUs
Code:
su
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/cpufreq/online
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Optional: ZRAM (Compressed RAM swap space )
Code:
su
mkswap /dev/block/zram0
swapon /dev/block/zram0
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
Installation Instructions:
Here's a step by step instruction to install this kernel:
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
{
"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"
}
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 1.72 GHz for performance, 1.2 GHz for battery
Min clock - MHz 192 MHz for both
CPU Governor - Ondemand for performance, Intellidemand for battery
mpdecision - Off
Set On Boot - On
SOC Control
Set On Boot - On
C0 - On
C1 - On
C2 - On
Voltage Control
Set On Boot -
Global CPU Voltage - Your preference
intellidemand gov control
Up Threshold - 90 for both
Two Phase Freq - 1134000 for both
Limit Max Freq - 1728000 for performance, 1512000 for battery
Sampling Rate - 30000 for both
Set On Boot - On
GPU Control
GPU Governor - ondemand for both
GPU Clock - 300Mhz for performance and 266Mhz for battery
GPU Vsync Toggle - On for both
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - SIO for both
Readhead Size (eMMC) - 384 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Vibration Control
Set On Boot - On for both
Vibration Control - Your own Preference
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
Above is what I use personally. MAY NOT be optimal for all :fingers-crossed:
Gingerbread Version History
Version 001 (deprecated)
- Based on 100% HTC source code!
- EXT 4 Support, CIFS + UTF-8 (NLS Support)
- Kineto_gan Support (WiFi Calling)
- CFQ I/O Scheduler default
- CPU Min/Max Frequency Enabled
- SmartAss 384MHz~1188MHz Default, Screen Off 594MHz
- SmartAss, MinMax, and Interactive Governors Added
- SmartAss Governor Set as Default for CFS
- TUN VPN support added
- SLQB memory allocator added and made default
- BFQ I/O scheduler added and made default
Version 002 (deprecated)
- Fixed SmartAss Governor
- Added NEON and other Snapdragon Compiler optimizations
Version 003 (deprecated)
Patched kernel to version 2.6.35.14
Version 005 (deprecated)
Added OC capability up to 1.512 GHz
Tweaked Voltage Table for more stability
Added REAL SmartAss Governor
(I was contacted by Erasmux's friend who informed me about the kang hax smartass I had!
I don't know where I got it from )
Patched BFS (step 1, not working yet)
Allowed unaligned memory access
Version 006 (deprecated)
Reverted CPU Clock Table back to CAF version
OC up to 1.512 GHz CAF Fast Version
Added CAF Patches to msm/cpufreq
Version 007 (Long Term Stable Release, Official GB2.3.3 )
The File ==> Sensation Kernel 0.0.7 <==
OC CPU up to 1.782 GHz, L2 Cache up to 1.512 GHz
Added CAF Patch to force max frequency for all cores via sysfs mfreq
Added Bluetooth BNEP support
Version 008 (deprecated, GB2.3.4)
Applied CAF USB Composite Patch
Removed USB Switch Mute conditions
Version 009 (deprecated, Hacked GB2.3.4)
Introducing Synchronous L2 Cache (1.56 GHz version ONLY)
Introducing L2 Cache Bandwidth Boost (from max 310MHz to 360MHz)
Introducing SmartAssV2 Official Version directly from Erasmux's Commits (Major props to Erasmux)
Version 010 (Short Term Release, Hacked GB2.3.4)
The File ==> Sensation kernel 0.1.0 (1.78 GHz) <==
The File ==> Sensation Kernel 0.1.0 (1.56 GHz Sync L2) <==
CAF Patch msm: acpuclock: Subscribe to _FROZEN CPU notifiers
CAF Patch msm: pm-8x60: Remove redundant code for restoring ACPU Clock Rate
CAF Patch msm: acpuclock-8x60: Use hotplug notifications for CPU, L2, BUS, voltage
SmartAssV2 is removed (temporary until I fix it)
Added back Scaling_Available_Frequecies sysfs entries (For Mike1986 and other ROM devs)
Introducing GPU 2D/3D Overclocking
2D Engine from 228.5 MHz to 266.6 MHz (this one is CPU limited, so will only see benefit with faster CPU clock such as my 1.78 GHz kernel variant)
3D Engine from 266.6 MHz to 320 MHz (both versions will benefit from this boost)
Version 012 (deprecated, Official GB2.3.4)
Re-Based on HTC MR release! (new baseline)
Introducing Joe's RCU (Performance boost, designed for aSMP architecture, garbage collection limited to master CPU, slave CPU only need to do what it needs to do)
Fast NoHz RCU (An RCU designed for Tickless kernel, which is our kernel)
Re-patched HTC MR release 2.6.35.13 to kernel.org 2.6.35.14
GPU 2D/3D is now same as stock (Due to screen tearing issues experienced by some users)
CAF msm: clock-8x60: Refresh PDM and TSSC halt bits at boot (Bug Fix)
CAF msm: 8660: Add barriers to SMP boot code (Stability patch)
CAF msm: clock-local: Add memory barriers for later move to _relaxed accessors (Stability patch)
CAF ARM: SMP: Make resched-ipi-while-offline warning less verbose (Slight performance tweak)
CAF msm: clock-8x60: Vote for mmfpb_a_clk at 64MHz (Bug fix)
CAF mmc: core: put eMMC in sleep (cmd5) mode before suspend (Power Saving)
CAF msm: clock-8x60: Don't disable clocks in reg_init (Bug fix)
Version 013 (deprecated, Official GB2.3.4)
Introducing GPU Turbo Boost (Max GPU clock from 266MHz to 320MHz, increased bandwidth from 2.48GHz to 2.87GHz)
KGSL Patch: Fixed Sleep Issue (Bug fix to actually allow GPU to go to sleep when it is idling)
KGSL Patch: Allow Large memory buffer request from User land (Let apps allocate large GPU memory buffer)
KGSL Patch: Save more GPU registers (Avoid register corruption due to context switches)
KGSL Patch: Check for Null Pointer (Safety precaution to avoid null pointer exception in kernel)
KGSL Patch: Do not trash general work queue (bug fix, work queue was corrupted)
KGSL Patch: Make GPU governors visible via sysfs interface
Version 014 (deprecated, Official GB2.3.4)
Introducing Global CPU Voltage Table (Under volt capability via sysfs interface, inspired by snq adapted for Snapdragon Dual-Core by me )
Re-coded GPU Turbo Boost. Fixed GPU Scaling governor (scaling was disabled)
Joe's RCU option is deprecated (based on download stats)
Version 015 (deprecated, Official GB2.3.4)
Added 1.674 GHz option (L2 Freq up to 1.566 GHz)
Applied many FrameBuffer patches from CAF
Applied couple more KGSL patches from CAF
Version 016 (deprecated, Official GB2.3.4)
Revenge of CFS, CFS Enhancement (Interactive latency greatly reduced, make it BFS like)
Version 017 (deprecated, Official GB2.3.4)
Fixed the derp that was 0.1.6
Applied many FrameBuffer patches from CAF yet again
Version 018 (deprecated, Official GB2.3.4)
Added New Early suspend drivers for 2D and 3D GPU engines
Re-Enabled KGSL Ringbuffer Power Management Overrides
Updated to JHash3
Updated Cpufreq to copy policy from siblings
Fixed memory leak in cpufreq stats
Removed CPU from NoHz Idle fair cgroup
Shorten 1080P start up latency
Fixed USB Gadget Serial Crash
Applied more MSM FrameBuffer updates from CAF
Version 019 (deprecated, Official GB2.3.4)
Fixed random SPI Operational State Invalid error
Added histogram capability for MSM video
Added lock/unlock for KGSL Early Suspend Drivers
Updated KGSL power level change
Revert Reg Init Patch from earlier (cause of instability)
Optimized memcpy and memmove for string library calls (real working version )
fixed audio unmapped memory crash
fixed inaccurate D-Cache size Macro
Version 020 (deprecated, Official GB2.3.4)
CFS Autogroup Version 2.0 (Super Charged CFS)
Fixed Kernel/Timekeeping issue
Fixed Full / Stretched Screen issue for Video Player
Patched FB and KGSL
Fixed Random Reboot issue (took me a week to verify this fix )
Revenge of JRCU (JRCU tweaked for better performance and battery savings)
Removed ALWAYS ON ADM Clock to save battery
Moved Data Mover to early suspend for cleaner exit
Version 021 (Deprecated, Official GB2.3.4)
Added XZ Compression support to 2.6.35 kernel
Added XZ Compression support for kernel image
Added XZ Compression RAMDisk support (boot time)
Added SquashFS support based on new XZ Compression (very high compression ratio File System)
Updated Camera Driver FPS to 120 (mdeejay )
Used the git implementation of SHA-1 to reduce boot time by 11%
Updated qdsp6v2 to block write until buffer is full
Updated trivial bug fix for SMP macro
Introducing ZRAM (compressed RAM == MOAR RAM )
I have successfully back ported ZRAM from 2.6.38 kernel to our older 2.6.35.xx kernel This should alleviate the memory pressure introduced by Sense UI.
ZRAM bug fixes and latest patches (up to latest greatest beyond Linux Kernel 3.1-rc8)
Version 022 (deprecated, Official GB2.3.4)
Increased ZRAM allocation for even MORE data in RAM
Added newly optimized CRC32 Improves EVERYTHING that uses it including TCP/IP, File Systems etc...
Added newly optimized CRC32c improves EXT4 metadata performance and anything else which uses CRC32c
Patched msm_serial_hs_lite (better battery life)
Patched qdsp6v2 to fix unexpected power consumption (better battery life)
Patched mdp4_overlay to flush RGB pipe when solid fill mode is used (better battery life)
Patched clock-8x60 to add a lower gsbi_uart_clk entry to save power (better battery life)
Lowered Camera Flash limit from 30% to 10%
Tweaked conservative governor for better interactive performance
Enabled Deep Power Management Options (better battery life)
Lowered CPU Minimum Voltage (better battery life)
Gate smi_2x_axi_clk off when smi_clk is disabled (better battery life)
Fixed performance level computation for VCD (better performance)
Added local control of vpe_axi_clk and rot_axi_clk (better battery life)
Removed unnecessary checks from DMA engine (more efficient DMA Engine == performance)
CleanCache(using Zcache)+FrontSwap optimizations (this concludes the ZRAM/Swap optimization)
Version 023 (deprecated, Official GB2.3.4)
CleanCache (zcache disabled due to incompatibility with mpdecision, blame HTC )
ARM Patch: Use CTR for the I-cache line size on ARMv7 (better performance)
lowmemkiller: make it swap friendly (better performance)
Enabled inline locks for ARM (performance)
ZSL Driver backport (part 2, CODE ONLY, not enabled)
CPU workqueue optimization (limit some workqueues to single thread)
Conservative Governor minor tweak
patched qdsp6v2 to Set tx and rx flags based on current device
patched display to avoid staging up two pipes at same mixer_stage
patched display to avoid staging up two pipes at same mixer_stage
Added GPU slumber (whenever screen is off, GPU is set to sleep)
Added idle wait support for SMP
Fixed AXI clock bug in GPU
Fixed L2 Cache Synchro bug (better performance)
Updated spin lock code (better performance)
Reduced WiFi voltage to min recommended by datasheet (better battery)
Reduced other sub-system voltages by 5~10% (better battery)
Eliminated unnecessary macro from decompressors (code clean up)
Wind down GPU turbo mode if idling (better battery)
compiled with latest code sourcery (better performance)
Fixed Power Management memory leak
Added 2 way call record capability (thanks to mdeejay!)
Patched wakelock to latest AOSP
Patched audio DSPs
Patched Ondemand Governor for better power savings.
Version 024 (deprecated, Official GB2.3.4)
NoHz RCU set as default
Disable BCM4329 wake irq when stopped (battery saving fix)
Re-order PPP packets in PPPoLAC and PPPoPNS (VPN bug fix)
PLL clock training with higher frequencies for better stability (stability enhancements)
mfd - Fix memory leak in debug probe
Introducing GPU 2D scaling governor (Enabled, completely original coding from me)
-- now it will scale from 145.455MHz~200 MHz depending on usage (this should save additional battery while screen is on).
Introducing IntelliDemand CPU governor
-- Built-in Screen Off profile (like SmartAss)
-- Built-in Browsing detection (enabled, completely original coding from me)
(this will limit cpu clock to max 1.0 GHz while browsing web, book, email etc)
Adjusted 3D and 2D GPU scaling and initial states for better compatibility with Rosie
Version 025 (deprecated, Official GB2.3.4)
msm72k_udc: Replace dma_coherent_pre/post_ops with mb/rmb
nfs: writeback pages wait queue
block: limit default readahead size for small devices
make default readahead size a kernel parameter
smd_pkt: Extend read operation to receive data larger than SMD FIFO
pet watchdog from console driver
Correct the number of slave ports in the system
watchdog: increase pet time to ten seconds
led: enable dynamic LED brightness
mm/vmalloc.c: eliminate extra loop in pcpu_get_vm_areas error path
Revert "qup_i2c: Calculate combined write length for multiple write transactions" (broke Sensors )
restart: call secure code to disable arbiter
restart: Handle reset interrupt from pmic
pmic8058-xoadc: request's done late into suspend
pmic8058-xoadc: Add mpp_config call on configure
Remove pm_runtime_suspended() from __pm_generic_call
HDMI: Support for 480p 16:9 in HDMI Driver
qdsp6v2: Reduce the pcm write timeout value
enable ldo's in PHY resume path (usb)
Add suspend/resume for TSENS (thermal sensor)
While powering down flush all the rpcrouter workqueues (rpc)
Reader thread to allocate memory without holding a spinlock (rpc)
Reorganize the usage of spinlocks in RPC Router reader thread
Update RPC client's cb_list_lock to use spinlocks
Retry callback registration on timeout (rpc)
Add smd_tiocmset api without spinlocks
Close smd ports upon failure to open.
print lock name for lockdep_init_error
execute lockdep_init as early as possible
board:clocks: add comments to make trouble shooting easier
smd_tty: restrict DS port platform driver
smd: add closing state to subsystem restart
smd_pkt: add subsystem restart loopback server reinit
smd_tty: add subsystem restart loopback server reinit
smd: add check for LOOPBACK_TTY platform device
Add 10 microsec delay before fetching setup_data (usb)
Simplify ACA state machine to support standard ACA (usb)
Recovery point SEI support for ISDB-Tmm (vidc)
Copy the End of Sequence flag (vidc)
Fix H.263 30fps standard resolution encoding.
Override SP profile to ASP for MPEG4 decoding.
Remove check for allocation of sequence buffer size. (vidc)
Update firmware memory size. (vidc)
Fix GOB Header for H.263 encoding.
Increase the decoder input buffer size.
Return the correct error code for IOCTL. (vidc)
Set correct divx codec type.
Handle b-frame not supported error.
Increase the kernel SMI memory size. (vidc)
Report bitstream errors to driver client.
add change to print MFC firmware version
Removed check for comparing DPB Size
add Check for infinite intraperiod configuration.
Fix to handle non-fatal sequence header errors. (vidc)
Fix not coded vop handling in decode order.
add mdp revision number
increase mdp max burst size
Calculate combined write length for multiple write transactions (i2c)
Fix input handler crash (ondemand, intellidemenad)
Add htc off-alarm support from XE source
updated sii9234 tpi driver from XE source code
USB misc code updates from XE source
enable android USB gadget projector support
Added thermal trip critical retry from XE source
updated DMA engine from XE source
fixed minor HTC battery driver coding derp
Added HTC Beats headset support from XE source
kernel:sched: avoids loadavg Moire
don't call task_group() many times in set_task_rq()
block level disk cache target for device mapper
Do not destroy old sched domain on cpu_up
Do not block when waiting to free old root domain
Check for extended quiescent state at start of gp (rcu)
Don't allow cpu to get console lock during hotplugging (printk)
Add the function 'cpu_hotplug_inprogress'
Remove extraneous boot_secondary delay
Version 026 (deprecated)
PM / Sleep: fixed coding derp from "Drop pm_op() and pm_noirq_op()"
mfd: timpani-codec: Handle register write for numbers more than cached one
mfd: timpani-codec: Write register defaults when disabling devices
msm_fb: Remove Audio Packet Control Register setup
mfd: timpani: Retry upon I2C failure.
msm_fb: Check for ACP and ACFG register before reset core.
msm_serial: add PM_RUNTIME code from CAF
mm: retry page fault when blocking on disk transfer
msm: kgsl: Do not allow SLUMBER from INIT
PM / Sleep: Drop pm_op() and pm_noirq_op()
PM / Sleep: Unify diagnostic messages from device suspend/resume
sched/rt: code cleanup, remove a redundant function call
ARM: Add optimised swahb32() byteswap helper for v6 and above
hugetlb: Replace BUG() with BUILD_BUG() for dummy definitions.
kernel.h: Add BUILD_BUG() macro.
msm: kgsl: New low power level
msm: vidc: print message as kernel info instead of error
camera:gemini: update gemini engine from hTc Ruby
battery: battery driver and charging driver update
mm: Android Ashmem update from hTc Ruby
misc: android pmem update from hTc Ruby source code
mfd: marimba core update from hTc Ruby
board: ARM kernel update from Ruby source code
cpufreq: add two-phase to ondemand and intellidemand
Version 027 (deprecated)
input/misc/gpio: update input GPIO driver from PyramidLE source
vidc: 1080p: Override profile to ASP for XVid/Divx456
Re-enabled ZRAM
Version 028 (deprecated)
Updated Zcache and ZRAM to latest Linux-next patches
Added Google's Snappy Compression for ZRAM
Version 029 (Current, Official GB2.3.4)
Init: Multithread initcalls to auto-resolve ordering issues.*
memcg: let css_get_next() rely upon rcu_read_lock()*
idr: make idr_get_next() good for rcu_read_lock()*
mm: implement WasActive page flag (for improving cleancache)*
zcache: fix deadlock condition*
Revert "msm: kgsl: Clocks should be set to the active level during NAP"*
Revert "partition_sched_domains: Do not destroy old sched domain on c…*
mmc: core: Prevent too long response times for suspend*
aww man finally i luv ur work on the mytouch series happy to have u here bro
Welcome to the sensation forums faux.
You need to note that current source is incompatible with android 2.3.4 builds, nice work getting smartass working!
Sent from my s-off HTC sensation running LeeDrOiD Sensational
Flashing as I type
Edit: So far so good, booted back up in about three minutes. Speeds aren't autodetected by setcpu yet, but I assume that'll come when oc comes.
GideonX said:
Flashing as I type
Edit: So far so good, booted back up in about three minutes. Speeds aren't autodetected by setcpu yet, but I assume that'll come when oc comes.
Click to expand...
Click to collapse
Use CPU Master for now.
faux123 said:
Use CPU Master for now.
Click to expand...
Click to collapse
Just a heads up for anyone trying CPU Master, it reboots me as soon as I hit apply on any governor changes
The slider also doesn't allow you to choose any speeds between 192 or 1188.
Finally Fauxy! This is gonna be a real treat having your kernels for the S4G! Thank you!
nice to see you on the sensation faux love your work! can we expect to see some of your AOSP work and kernel support for 2.3.4 ROMs as well?
You mention its for 2.3.4 Builds but if it is based on htc sources this cant be? They only released 2.3.3 Kernel sources...?
Or did you hacked it to work with 2.3.4?
xtcislove said:
You mention its for 2.3.4 Builds but if it is based on htc sources this cant be? They only released 2.3.3 Kernel sources...?
Or did you hacked it to work with 2.3.4?
Click to expand...
Click to collapse
dude are you even reading it say nothing about its for 2.3.4
Welcome faux, love your work in the G2x
Glad your finally here faux..
Sent from my HTC Sensation Z710e using XDA Premium App
phonegod said:
dude are you even reading it say nothing about its for 2.3.4
Click to expand...
Click to collapse
NOTICE: This is COMPATIBLE with ALL Sensations Rooted Stock and Custom ROMs
(Except the new 2.3.4 ROMs)
!? oh wtf -.- im so sorry ! My english isnt very well!
faux123 said:
NOTICE: This is COMPATIBLE with ALL Sensations Rooted Stock and Custom ROMs
(Except the new 2.3.4 ROMs)
Hi XDA members and fellow Sensation users:
This is my tenth kernel hack. I want to thank Erasmux, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
THIS KERNEL is BASED ON HTC Source Code. So it is COMPATIBLE ONLY WITH HTC Gingerbread Sensation Builds.
Please DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
MinMax Governor (Battery Saver)
This governor will try to minimize the frequency jumps/changes which cause voltage spikes/changes which supposedly drains more battery life... Supposedly designed to work with SetCPU... so give it a whirl...
SmartAss Governor (Balanced)
This governor has a built-in "profile" similar to SetCPU, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Interactive Governor (Performance)
This governor is designed to put more priority to User Interface (UI aka Apps) tasks, therefore appears more responsive then the traditional OnDemand governor. So if you want the smoothest UI interaction, this governor is for you...
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor specifically for user interface type systems such as desktop/smart phone devices where user interaction is MORE important than serving 1 million web requests (CFS, the default scheduler) at the same time (think of nimble desktop workstations vs large corporate servers).
SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate). Not all kernels are using SLQB including CM7 main line...
Fair Budget Queue (BFQ I/O scheduler)
This I/O scheduler is an improvement on top of Completely Fair Queue (CFQ). CFQ is fair in terms of time but not in terms of throughput / bandwidth, so BFQ make sure that both time and throughput / bandwidth are balanced across all requests.
Installation Instructions:
Here's a step by step instruction to install this kernel:
[ CFS-Smartass ] (Mainline)
The File ==> Coming Soon <==
The File ==> Sensation Kernel 0.0.1 CFS Stock Voltage <==
[ BFS-Interactive ] (Enthusiast Edition)
The File ==> Coming Later <==
The File ==> Coming Later <==
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the 2 versions!
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
NEWS BULLETIN:
Version 0.0.1 is OUT!
1. Initial Kernel (no overclocking / undervolting yet)
Please don't hesitate to talk among yourselves and help each other out... The MT4G/XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 1.x.x -- Haven't thought about it yet...
History:
See Post below...
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
Click to expand...
Click to collapse
Thanks for all that information, very useful.
Hey there fellow Kanger
Namit1994 said:
Thanks for all that information, very useful.
Click to expand...
Click to collapse
You really had to quote the whole op just to say "thanks" ? Lol
Good to see you in here faux, we've been waiting for youu
Sent from my HTC Sensation Z710e using Tapatalk
One more great dev...welcome to sensation ... can't wait for stupid htc to release the updated kernel sources for 2.3.4.
Sent from my HTC Sensation Z710e using XDA Premium App
Faux.!!! thanks for your work man. Good seeing you hear missed this kernels coming from mt4g.
Sent from my HTC Sensation 4G using XDA App
{
"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"
}
Kernel for Sense-based ROMs
LATEST STABLE RELEASE: ElementalX-8.3.2 (Sept 26, 2013)
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
FEATURES:
based on HTC Sense 5 Android 4.2.2 source code
Aroma installer
choose CPU optimization level: vanilla, elementalx, or ultra
optimized for extended battery life
overclocking options
choose max screen off frequency
user voltage control
choose voltage profile in installer
GPU overclocking
button light notification
sweep2wake
doubletap2wake
pocket detection (prevents accidental wakes in pocket)
/system writable
force fastcharge
NTFS r/w support
exFAT support
i/o schedulers: FIOPS (default), SIO
option to disable fsync
faux sound control support
increased refresh rate for HDMI output via MHL adapter
optimized -O3 linaro 4.7
DOWNLOAD
Sense 5 Android 4.2.2
ElementalX-8.3.2
mirror: http://www.androidfilehost.com/?fid=23212708291674213
If you experience cell signal drops and reboots, you need the latest firmware and matching radio.
Earlier versions
ElementalX-7.0.2
Previous releases:
ElementalX-6.7
ElementalX-6.6
ElementalX-6.5
ElementalX-6.4
ElementalX-5.4
ElementalX-5.2
ElementalX-JB-v2.5: http://goo.gl/I9DHA
Please hit the Thanks button if you download this
If you really like it, please consider buying me a beer
Actually, I won't spend it on beer. I'm saving it all up to buy my next device
Thanks to those who have donated!
INSTALLATION
1. Install zip from TWRP Recovery
2. Follow the instructions, if you don't know what to do, use the preselected option
3. Reboot!
S-OFF required!
First boot will take a while. Let it load all the way, then let it settle in for a few minutes, then reboot again.
FAQ
Q. I installed ElementalX and now I'm stuck in a bootloop
A. Go to this thread and get S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Q. I installed ElementalX and now my phone is laggy/sdcard is corrupt/camera doesn't work/other random problem not related to the kernel
A. Please don't fill up my thread with vague complaints. As long as you pick reasonable voltage and frequency settings, this kernel is 100% stable and problem free. I know what I'm doing and I don't do anything to the kernel that will mess up your phone. If you have problems, it's because of something else you've done. If you think you've found a bug with the kernel, please include dmesg output or /proc/last_kmsg
Q. I installed ElementalX and I get random reboots
A. If the reboots occur when your phone is idle, increase your voltage or increase your max screen off frequency. If the reboots occur while you are using the device, scale back your overclock and/or increase voltage. If all else fails, choose the vanilla option.
Q. What if I am still having problems?
A. If you are having problems the key to getting help is to provide appropriate detail.
Number 1: Description of your issue
I'm most cases people in this thread will try and help you. The more information, the better chance someone in the thread will be able to help you.
If you can't be helped by one of the experienced ElementalX users it would generally be referred to the dev
Number 2: Details of installation options e.g.
- ElementalX 6.5 Vanilla
- CPU Max: 1.7ghz
- CPU Min: 384mhz
- GPU OC: On
- S2W: On
- fsync: On
- Zram: On
Number 3: Logs, refer to the following details on gathering appropriate logs
In the below example the adb path is c:adb
Open command prompt type cd c:adb
The following two commands can be used to provide logs to help troubleshoot slowdown/freezing issues.
adb shell top -n 1 > c:top.txt
adb shell dmesg > c:dmesg.txt
If you experience a non-user initiated reboot please follow the below steps to provide last_kmesg
* After reboot issue is encountered boot to recovery
* use the file manager to copy /proc/last_kmsg to sdcard/download/
* mount usb and copy it to your computer
* zip it
* post it with details of your issue in this thread.
* restore your nandroid and boot into your last stable config
Click to expand...
Click to collapse
Special thanks:
zarboz and Sbryan12144 for porting S2W to our device
jrior001 for CPU1 fix
backfromthestorm for fstrim
xHausx and amarullz for installer stuff
anarchychris for FAQ and troubleshooting
tbalden for BLN
NOTES:
Configuration
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps are interfering with your settings If you're on ViperXL, make sure your settings in Venom Tweaks are the same as the ones in /etc/elementalx.conf (for example, sweep2wake settings)
Kernel Tuner
You don't need Kernel Tuner because the ElementalX installer sets everything up automatically, but if you want to check or change settings, Kernel Tuner is recommended. Just be aware that Kernel Tuner is set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
Venom Tweaks force close
If Venom Tweaks closes when you try to access the CPU tab, go to Settings->Apps->Venom Tweaks and push the Clear Data button. This should fix the problem.
CPU Optimization
Vanilla: stock voltages, stock l2 cache frequency, stock bus bandwidth
ElementlaX: increases l2 cache frequency and bus bandwidth, allows you to choose voltage level in installer
Ultra: increases l2 cache frequency and bus bandwidth even more. May cause instability, please test thoroughly for stability if you use this option.
Overclocking
Overclocking (underclocking) is optional. Whatever frequency you chose in the installer will be set at boot for both CPUs. Frequencies can be changed any time using apps like No Frills or Kernel Tuner. WARNING: not all devices can handle overclocking. The stock maximum CPU frequency is 1.5GHz. In versions of the kernel prior to 6.4, the frequencies were labeled wrong so you won't be able to overclock as high with version 6.4+.
CPU voltages
CPU voltages can be changed with Venom Tweaks, Kernel Tuner or System Tuner. Be careful, lowering voltages could cause instability. If you have stability problems even at the highest voltages, try the vanilla version
Minimum CPU frequency
Sets the minimum CPU scaling frequency. 192MHz is the recommended default and should work fine on the vast majority of devices. The 384MHz option is available for devices that experience random reboots while the device is idle. It is recommended that you try increasing the minimum voltage by 25mV before changing the minimum CPU frequency.
Max screen off frequency
This sets the highest CPU frequency available while the screen is off. It is recommended to disable this for stability. Also, do not set this to 192MHz or 384MHz, as many devices experience random reboots at these frequencies. The default is 486MHz, which should be safe for most devices. If you experience random reboots while the device is asleep, set this to a higher frequency. This setting can be changed in /etc/elementalx.conf or using an app like Venom Tweaks.
GPU frequencies
3D GPU: 480 (overclocked) or 400 (stock)
2D GPU: 266 (overclocked) or 200 (stock)
Governors
Intellidemand is the default CPU governor. There are other governors included, however, intellidemend is recommended for best balance of battery life and performance.
Installing a new ROM
If you install a new ROM, it will overwrite /etc/init.d/99elementalx and /etc/elementalx.conf. The kernel will run perfectly fine without these files, but you will lose your settings and certain features.
Sweep2Wake
Sweep2wake (S2W) allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). There are now options for sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use ViperXL, make sure to enable sweep2wake in Venom Tweaks.
/sys/android_touch/sweep2wake
0=disabled
1=enable sweep2wake + sweep2sleep
2=enable sweep2sleep only
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping in the bottom inch or so of the screen, including the capacitive buttons. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0=disabled
1=enable doubletap2wake
Pocket Detection
Pocket detection protects against accidental wakes while S2W, DT2W or L2W are enabled and the phone is in your pocket. Pocket detection uses the proximity sensor. A few people have a problem with their proximity sensor that makes DT2W not work, so I've made an option to disable pocket detection. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification. As soon as the screen comes on, BLN is canceled and the lights will no longer blink until you have another notification. Please note that if you have your screen set to turn on when a message arrives, you will not see the buttons blinking because once the screen comes on, the button light notification is canceled. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/class/leds/button-backlight/bln
0 = disabled
1 = BLN enabled
What is zRam
zRam creates a compressed block device in RAM that is used as swap. Although it claims some of your RAM as swap, everything written to swap is compressed. This increases the apparent memory available to the system and helps with multitasking. Swap files on disk are very slow, but with zRam the swap is on RAM so it can be read as quickly as regular memory. Even though the data need to be decompressed, modern CPUs can decompress quicker than if it had to be to read from disk. The penalty is cpu usage, which could drain battery; however, this is likely negligable in daily use. I didn't enable this by default because not everyone will want it. This is for heavy multitaskers and will allow you to quickly switch between more apps and have more tabs open in your browser without refreshes.
zRam is disabled by default. If you want to enable it, edit /etc/elementalx.conf
change ZRAM=0 to ZRAM=1 and reboot.
You can check if zRam is working by typing the command "free" into the terminal. You should see the total used and free swap. If these are all 0, then zRam is not enabled. Please ensure that other apps are not changing your minfrees, zRam works best with low minfrees and high swappiness.
NTFS support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS filesystem. You will need Stickmount or a similar app, HTC Sense+ won't detect NTFS.
Enable/disable fsync
Disabling fsync can increase filesystem performance. However, there is a small risk of data loss if the system suddenly crashes. If you can't afford to lose data, keep fsync enabled. Many custom kernel disable fsync, I leave it enabled by default for safety reasons.
XBox controller support
There is an experimental module that supports XBox gamepads, however, some people have reported that it draws too much power and doesn't work. I've suggested trying a powered USB hub, but still not sure if it works.
CHANGELOG:
Sept 26, 2013 - ElementalX-8.3.2
-fix fsync setting
-fix BLN setting
-battery saving and speed tweaks
Sept 22, 2013 - ElementalX-8.2
-compile with linaro 4.7
-fix touches registering during calls with sweep2wake
-update installer
-start fresh with HTC 4.2.2 source
-remove zram
-remove 192 min freq
-default governor is ondemand
-default i/o scheduler is fiops
August 18, 2013 - ElementalX-7.0.2
-fix installer
-fix init.d support
August 17, 2013 - ElementalX-7.0.1
-fix installer
August 16, 2013 - ElementalX-7.0
-remove OTG whitelist to enable more devices
-build with Linaro 4.8
-add TCP congestion control algorithms
-enable Netfilter XT target log support
-update installer
May 26, 2013 - ElementalX-6.7
-dt2w works with buttons
-no pocket detection when screen is on
-fix fm radio
-revert autogroup: group by current UID
May 17, 2013 - ElementalX-6.6
-add DoubleTap2Wake (DT2W)
-add button light notification (BLN)
-enable/disable pocket detection
-pocket detection (prevent accidental wakes with s2w and dt2w)
-enable/disable s2w and dt2w separately
-add faux sound control support (untested)
-other minor tweaks and fixes
April 5, 2013 - ElementalX-6.5
-modification to work with SD Manager in ViperXL 3.2.7
April 5, 2013 - ElementalX-6.4
-correct oc frequencies
-adjust l2 cache frequencies
-gpu overclock frequencies now 480 3D and 266 2D
-fix max screen off limit
-various patches from Linaro and CAF
-WiFi module fix (thanks thicklizard)
-avoid loadavg moire
-enable automatic process group scheduling
-max screen off frequency can be disabled
March 13, 2013 - ElementalX-5.4
-optimized build compiled with -O3
-linaro 4.6.3 -> linaro 4.7.3
-force ac for unknown chargers
March 10, 2013 - ElementalX-5.3
-re-add use glibc memcpy
-re-add use glibc string
-adjust dirty_background_ratio = 10
-adjust vm_dirty_ratio = 20
-revert fudgeswap
-revert minfree stats
-tweak clock settings
-add /dev/frandom
-add force fastcharge
March 3, 2013 - ElementalX-5.2
-review and clean up code
March 1, 2013 - ElementalX-5.1RC
-tweak GPU settings
-change installer defaults
-made sure that if you flash boot.img in fastboot you get vanilla version
February 26, 2013 - ElementalX-5.0.6-beta
-add another CPU optimization setting (Ultra)
-switch do_fsync() to fget_light()
-adjust readahead to 2048
-tweak GPU clock settings
February 24, 2013 - ElementalX-5.0.5-beta
-updated aroma installer
-CPU optimization options: Vanilla or ElementalX
-zram enabled by default
-small tweaks to GPU settings
-fstrim at boot
February 23, 2013 - ElementalX-5.0.4-beta
-dual zram
-use zcache instead of qcache
-use zsmalloc instead of zxmalloc
-CPU1 governor can be set independently
-set max screen off frequency
-choose 192 or 384 minimum CPU frequency
-update cpupower according to cpu load
February 21, 2013 - ElementalX-5.0
-fix installer conflicts
-option to install new ElementalX bootsplash
-option to install HTC bootsplash
February 19, 2013 - ElementalX-v4.5beta
-default i/o scheduler is now ROW
-add fix for crash when wp_mod.ko loaded
-add fudgeswap
-disable gentle fair sleepers
-xz kernel compression
February 17, 2013 - ElementalX-v4.4beta
-add lionheart, badass governor
-add row i/o scheduler
-adjust l2 cache frequencies
-re-add 200MHz step for 2d GPU (ElementalX-v4.4beta only)
-remove smartassv2 (broken)
February 16, 2013 - ElementalX-v4.3beta
-based on HTC source code 3.17
-overclock to 2.1GHz
-minimum frequency 192MHz
-optional overclock GPU
-full voltage control
-enable/disable fsync
-intellidemand default governor
-fiops default scheduler
-add sweep2wake
-add zRam with snappy compression
-init.d support
-ntfs r/w support
-fix HDMI refresh rate
February 3, 2013 - ElementalX-JB-v2.5
-added 384 MHz frequency step when selecting 192MHz as min frequency (needed because CPU1 will not stay at 192MHz)
-adjustments to init script
-option to install extra governors (lionheart, lagfree, interactivex2, and badass)
January 26, 2013 - ElementalX-JB-v2.2
-choose minimum CPU frequency (192MHz or 384MHz)
-option to leave minimum voltage at default
-optimized CPU control module, now reads PVS efuse and sets appropriate voltage levels
-streamlined options and config file
-optional XBox controller support
January 21, 2013 - ElementalX-JB-v2.1
-Option to completely disable overclocking/undervolting
-If overclocking, choose between optimization for stability or performance
-stability option does not increase L2 cache frequency and bus bandwidth
January 20, 2013 - ElementalX-JB-v2.0
-added intellidemand governor (default)
-added fiops i/o scheduler (default)
-optional zram with snappy compression
-optional ntfs r/w support
-select minimum voltage (800, 825, 850, 875, or 900mV)
-added 1134 and 1242 MHz underclocking options
-increased bus bandwidth
-many changes to installer and configuration files
January 14, 2013 - ElementalX-JB-v1.5
-minor fixes to init script
January 12, 2013 - ElementalX-JB-v1.4
-fix low 3D GPU setting
-undervolt option now undervolts 384MHz frequency step to 800mV
-boost L2 cache frequency for extra performance
-increase readahead buffer to 4096
January 8, 2013 - ElementalX-JB-v1.3
-added voltage options
January 2, 2013 - ElementalX-JB-v1.2
-removed 1998MHz frequency step
-added 1647MHz frequency step
-increased voltages slightly for stability
-added option to install without boot.img
January 1, 2013 - ElementalX-JB-v1.1
-minor tweaks to install method
-adjust lowmemorykiller
December 31, 2012 - ElementalX-JB-v1.0beta
-same max freq for both CPUs
December 29, 2012 - ElementalX-JB-v0.4alpha
-new overclocking method
-more frequency choices, underclock or overclock
-option for completely stock CPU
-increased overclock voltages
December 28, 2012 - ElementalX-JB-v0.3alpha
-enable system write
December 24, 2012 - ElementalX-JB-v0.2alpha
-overclock to 1998MHz
Click to expand...
Click to collapse
Source:
ElementalX-v7.x
ElementalX-v8.x
XDA:DevDB Information
ElementalX-8.3.2 | OC | UV | S2W | DT2W | BLN | Sense 5, a Kernel for the AT&T HTC One X
Contributors
flar2
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 8.3.2
Stable Release Date: 2013-09-26
Created 2013-09-23
Last Updated 2013-11-04
Reserved
flar2 said:
Kernel for Sense-based Jelly Bean ROMs
LATEST VERSION: ElementalX-JB-v0.1alpha (December 23, 2012)[/size]
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
WARNING: This is an alpha build. For testing purposes only!!
I will add more features and get things working properly later.
Download
ElementalX-JB-v0.1alpha: http://goo.gl/24bdo
Instructions:
Install from TWRP recovery
init.d not starting at the moment, so execute /etc/init.d/40overclock as root
Notes:
1. I will be away for the next week and a half, so progress will be slow, otherwise I'd have things going right away
2. CPU Spy doesn't show the real frequency
3. I can't wait to add more stuff
4. New stuff will be: min frequency 192MHz, Intellidemand, Zram, NTFS support
Click to expand...
Click to collapse
Thank you
Dang. Great work! Can't wait til this is stable with all the features. If you need help let me know!
Does this happen to bypass the write protection on /system?
absolutelygrim said:
Does this happen to bypass the write protection on /system?
Click to expand...
Click to collapse
No
I don't have the source, all I can do is add modules. I don't know if wp can be disabled using a module. I'll look into it next week when I'm back from Christmas holidays. Starting tomorrow, I'll be away from any decent computer.
UPDATE: Yes, this does bypass write protection
flar2 said:
No
I don't have the source, all I can do is add modules. I don't know if wp can be disabled using a module. I'll look into it next week when I'm back from Christmas holidays. Starting tomorrow, I'll be away from any decent computer.
Click to expand...
Click to collapse
Well, looks like we have to get you a decent laptop don't we? :L
Sent from my HTC One XL using Tapatalk 2
Anyone know if this works on newts Rom or a jb Rom I could flash that this works on?
WhatTheAndroid? said:
Anyone know if this works on newts Rom or a jb Rom I could flash that this works on?
Click to expand...
Click to collapse
It would work on any jelly bean sense rom
Edit:Nevermind
How do we know if it installed properly, I didn't check the kernel name before the flash but it looks stock. Is this correct, and as you said apps are not showing the over clock.
I got a 6475 with no OC, forgot to do Antutu.
With the kernel I got: 6189 (I know quadrant can be inaccurate)
Antutu: 11659
Sent from my HTC One XL using Tapatalk 2
EDIT: Got scores in the 7000's after some tweaking.
lsmod in terminal should show oc_mod. But right now, basically if you don't know how to check stuff like this you shouldn't install. My first step was getting a module to load, now I've got to get it working properly.
Nice will be watching to see how the this progresses
Sent from my HTC One X using Tapatalk 2
How do you execute the 40overclock? Yes I'm asking!
Sent from my HTC One XL using Tapatalk 2
monkboy24 said:
How do you execute the 40overclock? Yes I'm asking!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Use script manager app
Sent from my Nexus 7 using Tapatalk 2
currydude said:
Use script manager app
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I used script manager to execute 40overclock and it says oc_mod exists already. And then permission is denied on the next operation. So if I have the oc_mod file it must have worked?
flar2 said:
lsmod in terminal should show oc_mod. But right now, basically if you don't know how to check stuff like this you shouldn't install. My first step was getting a module to load, now I've got to get it working properly.
Click to expand...
Click to collapse
I used adb shell, su, then lsmod and I got the output:
oc_mod 1902 0 - Live
So I guess I'm all good.
Sent from my HTC One XL using Tapatalk 2
Can't wait for this! Thank you so much!
Viper Rom, baby!
Tried playing around with this.. Don't understand too much.. Was hoping to get rebelrom screaming even more that it already is
Sent from my HTC One XL using Tapatalk 2
Thanks for a great JB kernel. Anyway to have 2 way call recording patch in the future version of ElementalX kernel as there isn't any patch for HTC ONE XL till now. Thanks in advanced and waiting for 2 way recording feature!
Sent from my HTC One XL using xda premium
Just uploaded version 0.2
Should "just work" (init.d support is added)
The only feature is rudimentary overclocking still, I haven't a chance to work on any of the good stuff.
Attention
/*
I'm not a developer, im taking effort to put more choices of kernel for our community.
This kernel is tweaked for my own taste.
Please do not request for more features because i want to ensure the stability of the kernel first.
And thank you for using this kernel.
*/
Disclaimer
Code:
/*
* 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.
*/
WARNING !! Please read before proceeding to download section as to avoid any confusion happen !
CODE NAME: Stable VERSION
Features
- Compiled with latest Built with latest custom Gcc 5.1 ArchiToolchain optimized for Cortex-A7
- Optimized ARM RWSEM algorithm
- -O3 optimization and others more
- Add AutoSMP hotplug driver (really nice)
- Add Mako hotplug driver (more conservative hotplug - more likely in 2 core mode, quad core will only be use when greater load detect)
- Faux Sound Control
- updated Sched/fair structure/RCU from upstream
- Enable ULPS(Ultra Low Power) and partial update for panel
- AKM8963 driver used lcd notifier (keep phone sensor suspend during LCD off to save more power usage)
- Use new hotplug infrastructure from 3.10.x kernel
- used CPU-Boost caf ( can put different frequency for each core )
- improve Suspend and Resume timer
- ZEN, SIO, FIOPS, VR IO schedulers
- add lcd notifier for dt2w/s2w and akm8963 usage
- implement doubletap2wake, sweep2wake and sweep2sleep
- implement s2w dt2w with pocket mode
- Intelli Demand governor
- intelli Active governor (disabled for temporary)
- zzmoove Governors with tweaked profile for moto G - please read #4 post for more information
- yanactive governor
- impluse governor
- filter WAKEUP from francisco
- powersuspend - USERS cant configure it (no sys support) - all hotplug driver in this kernel use powersuspend
- KCAL support for post processing control [v2]
- WQ_POWER_EFFICIENT for power oriented workqueues
- cfg80211 driver from aosparadox kernel
- selinux in permissive
- Enabled all kind Advance TCP
- Disable many debug option to reduced overhead of the kernel
- silenced various kernel logs
Kernel Sources : - Github
https://github.com/hurtsky/android_kernel_motorola_msm8226
Please ensure that you already used latest version of CM, thank you.. :-
Installation Guide :
Using TWRP
1. Reboot to recovery > Install > Pick the kernel > Confirm to Flash > Reboot
or
2. Flash it using Flashify
Code:
[I]Credit to :-[/I]
- CyanogenMod Developer team for providing the source
- developers that contributed in my github changes - all credit goes to them
- xda-developers.com
- and to all my kernel users, thanks.
XDA:DevDB Information
[Kernel][5.1][-O3][-graphite][FINAL] HurtSky Stable 13 [dt2w/s2w/s2s] 30/11/2015, Kernel for the Moto G
Contributors
hurtsky
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: stable 5
Stable Release Date: 2015-10-09
Created 2015-03-23
Last Updated 2015-12-02
READ BEFORE HAVING A THOUGHT OF POSTING QUESTIONs
FAQ - Freaking Annoying Question
THIS KERNEL WORKING IN STOCK ROM ????
1. NO, this kernel for ROM that based on CM kernel
KERNEL DID NOT FLASH/THE VERSION STILL THE OLD VERSION
1. Put the kernel ZIP at folder /sdcard and flash it.
2. Please use recommended recovery for this kernel >>> CLICK HERE
SYNAPSE NOT WORKING SUDDENLY ????
1. Read this >>> CLICK HERE
IF HAVING ANY REBOOT? WHAT TO DO?
1. upload file last_kmsg that located in /proc/last_kmsg
2. infomation about what setting that you use : example: intelli plug with zzzmove
3. if only state that youre having reboot without any logs will be ignore.
ERROR DURING OR AFTER FLASHING THE KERNEL
1 . if you comes from others kernel or after flashing the kernel you had this following "error : Fastboot Reason : Fall-through from normal boot mode" or any error during flashing, please dirty flash your rom again to clean up any conflict from different kernel script.. let it reboot.. and flash this kernel..
2. If still happen, flash recommended recovery for this kernel >>> CLICK HERE
OWN CUSTOM SETTING FOR KERNEL DID NOT STICKING AFTER BOOT
1. Make sure you used only 1 kernel tweaks and make sure you did change anything in "advance setting", remove the others apps and start tweaking your own favorite config. (i always suggested to use only Kernel Adiutor for tweaking the kernel)
2. Some ROM had they own boot script that will force the user to stick with it, this happen normally with interactive and cpu-boost config (in this kernel i already disabled completely cpu-boost so no need to worry about this). change interactive to another governors if you did not like what the ROM already did for you. (but i always recommend interactive, as it the most stable governors and updated for current time)
WHAT THE BEST OR RECOMMENDED CONFIGURATION FOR THIS KERNEL??
1. Default configuration is always the best for me because i already tweaked and tested by my own and with my tester before release it to the forum.
2. If you did not like default config, just do your own way (google,do research or re-read all post in this thread because there are some advance users posted their own configuration) and i wont answer or provide any advice for this kind of questions because i always stick with my own configuration
A LITTLE UNRESPONSIVE TOUCH AFTER DOUBLETAP2WAKEUP
1. Please read 4th post in dt2w/s2w/s2s section.
Click to expand...
Click to collapse
DOWNLOAD SECTION
>>>>PLEASE CLICK HERE TO DOWNLOAD<<<<
Note : - if you comes from others kernel or after flashing the kernel you had this following "error : Fastboot Reason : Fall-through from normal boot mode" or any error during flashing, please dirty flash your rom again to clean up any conflict from different kernel script.. let it reboot.. and flash this kernel.. thank you
Changelogs of Hurtsky Kernel
CHANGELOGS for STABLE VERSION > CLICK HERE
Click to expand...
Click to collapse
Please do not expect me to explain all changes, mostly can be found by googling them or look into the commit changes in github, also those information can be found in xda forum itself and i will not entertain those question. thank you
Note : - if you comes from others kernel or after flashing the kernel you had this following "error : Fastboot Reason : Fall-through from normal boot mode" or any error during flashing, please dirty flash your rom again to clean up any conflict from different kernel script.. let it reboot.. and flash this kernel.. thank you
.
Special features and sysfs settings All Credits to @Christopher83
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)
To change the value you can use Performance Control to suit your own taste
Click to expand...
Click to collapse
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.
To change the not killable process you can use Performance Control to include it to the list.
Click to expand...
Click to collapse
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 this 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
Click to expand...
Click to collapse
KCAL support for post processing control [v2]
Please click the link below for more information, and how to use it : - all credits to savoca
[DEV][PATCH] KCAL - Advanced color control for Qualcomm MDSS 8x10/8x26/8974/8084
Click to expand...
Click to collapse
ZZMoove Governor Profile
use tools like Android Tuner ,SetCPU or similar tools which are supporting the change of multible tuneables on-the-fly
or just do it directly in kernel sysfs via a terminal emulator and give the tuneable "profile_number" one of the following values:
1 for Default Balanced Profile
2 for Yank Battery -> Better battery, try to use lower freq as possible
3 for Yank Battery Extreme -> Aggressive Battery profile, by trying to reduce hotplugging as can as possible and with this profile the user will suffer abit in performance side
4 for ZaneZam Performance -> Extreme tuned for performance, aggressively try to hold on high frequency to obtain higher performance
5 for ZaneZam Relax -> Moderate tuned, more to balance but abit performance
Click to expand...
Click to collapse
Dt2w/S2w/S2S
Implemented Pocket mode, in which, each time proximity sensor been covered, it will suspend touch to avoid sudden screen wakeup. Normally proximity sensor will active to covered when it detect any object about 3cm from phone distance.
Known bug for this features for now is:
1 - touch will less responsive during first wakeup after doubletap
How to use this features
- enable the features by using Kernel Adiutor or others apps that support this feature
- DOUBLETAP2WAKE (dt2w) >>> double tap the screen during screen off to wakeup the screen
- SWEEP2SLEEP (s2s) >>> sweep from right to left at Navbar to off the screen
- SWEEP2WAKE (s2w) >>> sweep from LEFT to RIGHT to wakeup the screen
Click to expand...
Click to collapse
MSM_LIMITER
This function will limit the cpu in certain condition such as frequency during suspend, resume and min frequency. This features enabled in default and the frequency already been set for suspend freq to 600Mhz (screen off), min freq 300Mhz, resume freq 1.2Ghz. This feature may can reduce power consumption as it limit our cpu frequency after the screen off.
Bugs:
1. this msm limiter also should be able to set different freq of each cores, due to some out-of-date/lack of knowledge of mine, its appear only can change the freq of cpu0 and it will applied the same policy to anothers cpus rather than can set different freq to each cpus.
Click to expand...
Click to collapse
.
Download links
i will be first to try.... but I don't see download links.....
sachoosaini said:
i will be first to try.... but I don't see download links.....
Click to expand...
Click to collapse
just finish upload it, now available at download section
Everything is working fine...
Doing late reply but was waiting to see deep sleep working. Well kernel is working pretty good.... i got stable battery life till this report. Linux set to enforcing(great security feature).. Screenshots attached....So here i assume that xposed will not work, which is not all necessary. ROM was pacman nightlies 21st march.. i didn't tweaked anything....
Welcome and Thank you for a decent start.
Tried your kernel on Exodus ROM. Using Interactive with deadline and mpdecision hotplug. Slightly fine tuned Interactive to scale conservatively in my usage. Going good. You may gain feedback from few more users and proceed to add great features mainly the Hotplug replacement by Intelliplug Thanks...!
EDIT: Faux clock refuses to alter Governor tunables and doesn't show list of I/O schedulers with this kernel. Going fine with TricksterMod.
sachoosaini said:
Doing late reply but was waiting to see deep sleep working. Well kernel is working pretty good.... i got stable battery life till this report. Linux set to enforcing(great security feature).. Screenshots attached....So here i assume that xposed will not work, which is not all necessary. ROM was pacman nightlies 21st march.. i didn't tweaked anything....
Click to expand...
Click to collapse
==vj== said:
Welcome and Thank you for a decent start.
Tried your kernel on Exodus ROM. Using Interactive with deadline and mpdecision hotplug. Slightly fine tuned Interactive to scale conservatively in my usage. Going good. You may gain feedback from few more users and proceed to add great features mainly the Hotplug replacement by Intelliplug Thanks...!
Click to expand...
Click to collapse
intelliplug still in testing.. for some reason on my earlier test mode, the rom side give out many warning.. so i decided to stay with mpdecision.. mainly reason for this kernel is stability..
thanks for trying this kernel
Great ...new kernel
Seems good
update to version 2 / V2
In general update: -
- Add Faux Sound Control with Quality Preset in default thanks to Alin for the patch
- Update powersuspend to v1.5
- Add msm_hotplug
- Add conservative mode to rq_stats/mpdecision
- more patches stated in 2nd post
recommend setting
- conservative
- hotplug enable
- bfq (optional)
hurtsky said:
update to version 2 / V2
In general update: -
- Add Faux Sound Control with Quality Preset in default thanks to Alin for the patch
- Update powersuspend to v1.5
- Add msm_hotplug (can run it with mpdecision)
- Add conservative mode to rq_stats/mpdecision
- more patches stated in 2nd post
recommend setting
- conservative
- hotplug enable
- bfq (optional)
please download it at Alternative Link in 3rd post, i cant upload it to xda server for now..
thank you
Click to expand...
Click to collapse
Awesome Kernel!!!
This kernel is awesome !!!!
Nothing anymore
No, you can use twrp. Just change file to image and boot partition and it will work fine!!!
working great so far with PAC man 26 nightlies
update to version V3 29/3/2015
Added features
- Intelli Plug
- Intelli Demand
- intelli Active
- Intelli Thermal V2
- Kexec Support
- Lowmemory Killer : Management of not killable process (refer to 3rd post for more information)
- Selinux - Permissive
- others patches at 2nd post
@hurtsky: I am using V3 of your kernel. Everything is smooth, but i can't enable Intelli Thermal in Synapse App -> in the case i try to enable it, the phone reboots.
The other thing is to enable simple ondemand gpu governor:This causes also a reboot of the phone.
hurtsky said:
update to version V3 29/3/2015
Added features
- Intelli Plug
- Intelli Demand
- intelli Active
- Intelli Thermal V2
- Kexec Support
- Lowmemory Killer : Management of not killable process (refer to 3rd post for more information)
- Selinux - Permissive
- others patches at 2nd post
Click to expand...
Click to collapse
Everyone who used this saying no Issues so it must be good kernel. I will flas it as soon as I am back home
Volkan66 said:
@hurtsky: I am using V3 of your kernel. Everything is smooth, but i can't enable Intelli Thermal in Synapse App -> in the case i try to enable it, the phone reboots.
The other thing is to enable simple ondemand gpu governor:This causes also a reboot of the phone.
Click to expand...
Click to collapse
thanks, i will fix it in next version.
[KERNEL] [ROOT] [SM-N920P Exynos 7420] [19 February] SkyHigh TW 5.1.1 Kernel [ v4.5 ] [Synapse ++]
WARNING
Code:
[COLOR="Red"]PLEASE SHOW RESPECT TO ACTUALLY [COLOR="PURPLE"][B]READ POSTS #1-3[/B][/COLOR]
[URL="http://forum.xda-developers.com/announcement.php?a=81"][B]XDA RULE #1 "SEARCH BEFORE POSTING"[/B][/URL] (GOOGLE, XDA & THREAD),
IF YOU DON'T LIKE A UP-FRONT "MATTER OF FACT" APPROACH,
[B]THEN DON'T BOTHER POSTING[/B]. [/COLOR]
FEATURES
Code:
* Based on official Samsung source: [URL="http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920"]Samsung OSRC[/URL]
* ramdisk source: N920PVPS2AOK3
* Compiled with Linaro gcc-linaro-4.9-2015.02-3-x86_64_aarch64-linux-gnu
* Linux 3.10.96
* [COLOR="red"]AUTO-ROOT binary v2.52[/COLOR] & Install busybox v1.24.1-Dorimanx
* [COLOR="Red"]KNOX WARRANTY VOID: 1[/COLOR]
* [COLOR="red"]SELinux PERMISSIVE[/COLOR] (for Titanium Backup and other apps to work correctly)
* adb insecure
* stock dt.img
* init.d script support (drop in script & set permissions to 755 or 777 and reboot)
* [COLOR="red"]DEEP SLEEP FIX[/COLOR]
* [COLOR="red"]IN-CALL REBOOT BUG "FIX"[/COLOR]
* Possible Screen Mirroring / AllShare Cast fix
* Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
* RAM management tweaks
* GearVR [U]reported[/U] working (depends on ROM/firmware version installed)
* [B]Synapse app support[/B] for many kernel configurations + more !!
* Many descriptions are in the app ! If you require more info, don't be lazy, please [B]SEARCH[/B] like I did ;)
SYNAPSE FEATURES
ABOUT
PayPal Donation link
SkyHigh kernel thread link
Up time
Total
Sleep
Awake
A57 CPU
A57 big Cores Frequency Scaling
live frequency
MAX: 2400 MHz (stock 2100 MHz is default)
MIN: 500 MHz (stock 800 MHz is default)
A57 VOLT
HPM voltage control
A57 big Cores voltage control
A53 CPU
A53 LITTLE Cores Frequency Scaling
live frequency
MAX: 1600 MHz (stock 1500 MHz is default)
MIN: 200 MHz (stock 400 MHz is default)
A53 VOLT
HPM voltage control
A53 LITTLE Cores voltage control
CPU GOV
CPU governors
interactive (default)
on-demand
conservative
ktoonservative (hotplug)
userspace
performance
Interactive governor live load at current frequency (A57+A53)
Interactive governor tuning (profiles)
Default
Battery
PerformanceTurbo Mode
A57 GOV
A57 governor tunables
A53 GOV
A53 CPU governor tunables
MULTICORE
HMP threshold tuning profiles
Default
Performance
Battery
HMP threshold controls for up/down migration
Power Aware Scheduling control
HMP LITTLE Packing
PEWQ (Power-efficient Workqueues) control
Exynos Core Control Interface (choose 5 > 8 cores online)
CPU STATS
CPU0 time in state
CPU4 time in state
BOOST
Input-Booster profiles
key
touchkey
GPU
GPU stats
Current clock freq
Live Frequency Utilization (load)
Time in state
GPU power policy control
coarse_demand (default)
demand
always_on
GPU frequency scaling
Max freq control to 852 MHz (700 MHz is default)
Min freq control to 100 MHz (stock 266 MHz is default)
GPU Governor
Default
Interactive (default)
Static
Booster (more graphic and benchmark performance)
GPU Interactive Governor tunables
highspeed clock
highspeed load
highspeed delay
GPU VOLT
HPM voltage control
GPU voltage control
THERMAL
Sensor temperatures
A57
A53
GPU
ISP
CPU thermal control
normal temp
critical temp
GPU thermal control
On/Off thermal manager
temp levels 1 > 5
throttling freq levels
Memory thermal control
normal temp
critical temp
ISP (Image Signal Processor) thermal control
temp levels 1 > 5
BUS
Memory Bus HPM voltage control
Memory Bus voltage control
Internal Bus voltage control
ISP (Image Signal Processor) voltage control
IO
I/O Schedulers
BFQ (tweaked for SSD)
DEADLINE (tweaked for SSD)
FIOPS
CFQ = default (tweaked for SSD)
NOOP
ROW (tweaked)
Storage read-ahead (256 KB)
General IO tuneable
Add random
IO stats
Rotational
No merges
RQ Affinity
NR requests
I/O scheduler tunables
MEMORY
Memory state
Total
Free
Low Memory Killer Profiles
Low
Medium
Custom (recommend)
Default (default)
Aggressive
Exterminate
Low Memory Killer minfree tuning (OOM LMK)
Adaptive Low Memory Killer
vmpressure_file_min
Samsung SPCM Service control (Enabled = default/stock)
Ultra Kernel SamePage Merging (UKSM)
UKSM stats
Scan Delay Interval
UKSM Governor
Max CPU consumption
Dynamic FSYNC control (enabled)
Dynamic dirty page writeback control (enabled)
Dirty writeback active
Dirty writeback suspend
Virtual Memory
Virtual NAND Swap control (VNSwap)
ZSwap memory pool
Adaptive Dirty Background Ratio on suspend / resume
Adaptive Dirty Ratio on suspend / resume
Drop caches (Clear VFS cache after boot)
Laptop Mode
Swapiness
Adaptive vfs_cache_pressure on suspend / resume
ADVANCED
Entropy (max 4096)
Gentle Fair Sleepers control (disabled)
Arch Power control (enabled)
randomize_va_space control
pm_freeze_timeout control
Google Play Services Battery Drain Fix
Driver wakelock controls
SensorHub
ssp_sensorhubSSP
sig_motion_sensor
pickup_gesture
grip_sensor
tilt_detector
proximity_sensorbcm4773
bcm4773_gps
POWER SUSPEND
Modes:
Autosleep
Userspace
Display Panel
Hybrid (Autosleep + Display Panel) = default
PowerSuspend State (enable only with Userspace mode set)
Version push button
AUDIO
(Sound Control by AndreiLux)
Jack media volume control
L/R channel volume
mono mixer
Speaker volume control
Earpiece volume
Main Equalizer
Advanced Stereo Equalizer
SCREEN
Live panel brightness
sweep2sleep control
NETWORK
TCP congestion control
All available enabled.
Default = westwood+
Screen mirror/allshare cast fix control (enabled)
Clean WIFI Lease
WIFI Passwords
Save
Restore
WiFi Power Mode While Screen-On/Off
Force Off
Off
Fast (default = screen ON)
Max (default = screen OFF)
WiFi DTIM Interval While Screen-On/Off
RX wakelock timeout control
TCP/IP network security
3G DNS speed & security tweak
Google
OpenDNS
Comodo, Level3
Norton_DNS
Smart_Viper
GPS time-zone
Original
Asia
Europe
Oceania
North America
South America
Africa
IPV6-protocol
IPv6 Test push button
IPv6 enable / disable
optimistic detection
SECURITY
KNOX control
NO_ACTION (default)
Disabled
Enabled
SELinux
Live status
BATTERY
Battery info
Charging controls
HV power supplies
A/C Mains
A/C Mains (screen-on)
Standard downstream port
Dedicated charging port
Charging downstream port
Accessory charging adapter
MHL power
Wireless power
Store Mode
enable / disable (master control)
Store Mode Maximum
Store Mode Minimum
Battery SCALING calibration (fuel gauge reset)
LED
LED disable control
LED Fade-in/out Time Period
LED Fade control
Fade-in
Fade-out
Test notification push button
Stop notification push button
FS (File System)
Display FS Type
FS Controls
remount System r/w r/o
remount RootFS r/w r/o
Scrolling cache control
Optimise Databases (SQLite3)
FSTrim lagfix
Wipe options
cache reboot
dalvik-cache reboot
cache & dalvik-cache reboot
Clean up
clipboard cache
/data/tombstones
/data/anr logs
/data/dropbox logs
lost+found
CORTEXBRAIN
Live status
Cortexbrain-Background-Process (Master Switch)
CortexBrain Functions
WiFi Auto
Media Manager
System-Tweaks
Kernel-Tweaks
nmi_watchdog
CRONTAB
Live status
CronTask (Master Switch)
Cron Tasks
Clean RAM cache (every hour)
Google Service restart (every 3 hours)
Clean app cache & junk (every day at 4:30AM UTC)
clipboard cache
/data/tombstones
/data/anr logs
/data/dropbox logs
lost+foundOptimize databases (every day at 4:40AM UTC)
File system trim (every day at 4:50AM UTC)
Battery scaling calibration (every Sunday at 5:00AM UTC)
Test Cron Task jobs
USB
USB status
USB mode selection
MTP
PTP
CD_ROM (drivedroid support)
USB_Keyboard-Mouse
MODULES
CIFS
NTFS
ISO9660_FS
UDF
XPAD
BACKUP & RESTORE
Name - Restore - Delete - Backup
profiles
kernel image
LOGS
Android Logger control (enabled)
LogCat
Kernel Logger control (enabled)
dmesg
last_kmsg
REBOOT
Reboot device
Recovery Mode
Download Mode
Power Off
Clear Synapse Data & Reboot
Restart Synapse
INFO
Reduced logging
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount partitions NOATIME and NODIRATIME by default
FSTrim on boot (ensure consistent IO throughput)
Entropy tweaks
Increased boot frequency
Power-efficient workqueue (PEWQ) efficiency patches
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
LZO de/compression algorithm
Slub tweaked
Much more - check source commits & Synapse
CREDITS
My family !!
@Chainfire - root & SuperSU / @Manh_IT - auto-root method
@AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
@halaszk88 - patches and Synapse code I adapted to many of my kernels
@dorimanx - BusyBox and various ramdisk tweaks/ideas
@apb_axel - I adapted and used many of the Synapse controls to suit my kernels
@arter97 - various source fixes/patches
@ktoonsez - ktoonservative hotplug governor
@LuigiBull23 - ktoonservative profiles I've adapted
XDA
Samsung OSRC
and many others!
check github source credits
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Note 5 Exynos 7420 Sprint Kernel, Kernel for the Sprint Samsung Galaxy Note5
Contributors
UpInTheAir
Source Code: https://github.com/UpInTheAir/SM-N920
Kernel Special Features: Synapse ++ | EXT4 | exFAT | NTFS | CIFS
Version Information
Status: Stable
Current Stable Version: 4.5
Stable Release Date: 2016-02-19
Created 2015-12-02
Last Updated 2016-02-19
Warning - ChangeLog - Requirements - Installation - Download - Source
** DISCLAIMER : FLASH AT YOUR OWN RISK **
WARNING :
Code:
[COLOR="Red"]* Under-volting can cause instability
* Over-clocking can cause freeze/reboot, heat & damage to CPU, GPU or other hardware
* Any customizations may void warranty
* May not be suitable for your device or customizations
* UpInTheAir is NOT responsible, the person you see in the mirror is !![/COLOR]
CHANGE-LOG
Open GitHub Change-Logs
Tap/click "Full Change log" under the latest version (i.e. v4.5)
Example: ALL commits (changes) for v4.4 > v4.5 are visible at the top section
Tap/click any commit and will display all comments in the top section and code changes in the bottom section for particular commit
REQUIREMENTS
Variant support for:
SM-N920P
Watch >>> THIS <<<
IF YOU WISH TO BUG REPORT: Stock UNMODIFIED TouchWiz (TW) 5.1.1 ROM (I DO NOT HAVE YOUR DEVICE !! )
Custom recovery i.e.. TWRP or Philz
INSTALLATION
If you have systemless root installed, then you must REMOVE it as this kernel will auto-root a proven and stable 2.52 binary into system.
Open SuperSU app
Select "Full unroot" option
Reboot (or flash kernel)
Re-install SuperSU app
Uninstall any CPU control apps, tweaks and init.d scripts etc.
Recommend: Disable or remove KNOX (you can disable with Synapse once kernel is flashed)
Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!
Device Settings:
Enable Developer Options > OEM UNLOCK
If flashing from previous SkyHigh kernel > Device settings > Applications > Synapse > Force Stop > clear data
If not installed > Install SuperSU from Google Play:
Boot into custom recovery and flash SkyHigh_kernel____.zip FOR YOUR DEVICE and reboot
After boot:
a) wait at least 120 secs to stabilize
b) Open Synapse
c) Tap "Understood"
d) DO this step so some defaults are set !!
1. tap the square menu button top right hand corner
2. tap the three dots button
3. "select all globally"
4. tap the back button next to it
5. apply
DOWNLOADS
SM-N920P [ v4.5 ]
________________________________________________________________________
OLDER SkyHigh kernels > HERE
________________________________________________________________________
OTHER international & dual SIM thread > HERE
________________________________________________________________________
SM-N920-T / W8 thread > HERE
SOURCE
ALL KERNELS COMPILED WITH SAME SkyHigh SOURCE !!
Github
.
Help & FAQ
THREAD RULES & PROTOCOLS FOR THIS DEVELOPMENT THREAD:
I might not have your device variant and or able to reproduce your "issue". With this in mind, without providing as much information as possible, and resetting your device to a stable unmodified baseline, any potential troubleshooting or logs could be meaningless. So please follow the guidelines set out below. Thanks
BY POSTING YOUR ISSUES IN THIS THREAD, YOU ARE AGREE TO HELP YOURSELF FIRST BY PROVIDING INFO REGARDING:
Code:
1. DEVICE MODEL ?
2. ROM and firmware version (build number, boot-loader etc) ?
3. EXACT steps taken to reproduce YOUR issue
4. Screen-shots (if applicable)
5. Did you read Posts #1-3 completely?
6. Did you search the thread, XDA or GOOGLE?
7. Did you follow the install instructions EXACTLY?
8. What was your previous kernel?
9. Do you have any other known kernel tweaking apps, scripts or mods? ([B]remove them[/B]). [COLOR="Red"]This includes Xposed etc[/COLOR]
10. Try older kernel (if available)
11. Factory reset ?
12. Try latest stock [B]UNMODIFIED[/B] firmware (without custom ROM - if you have installed) and factory reset
13. Delete your ROM BusyBox (kernel uses it's own in /sbin)
ONLY IF YOU HAVE TRIED SUGGESTIONS ABOVE:
Turn on logging in Synapse and save logs AT TIME OF ERROR. AND post together with ALL the above information.
ELSE, DON'T WASTE MY TIME, YOU WILL BE IGNORED AND/OR POST REPORTED !!
THANK YOU :good:
NO FAST CHARGE
If using the pathetic original cable, try disconnect and reconnect the USB cable whilst power is still turned on to the charger
Use a thicker / better cable, will work every time (ie. Note4 OEM cable)
CAN I BUILD A KERNEL FOR YOUR __XX DEVICE ?
I will not build for any device that I can not compile using SAME source, personally test method or debug. Some device variants can compile with same source.
Sorry. I don't have the spare time for any more variant support.
"NO UCI SUPPORT"
It's a ROM busybox compatibility issue
Three choices:
Device > settings > applications > Synapse > force close & wipe data and REBOOT
OR
Remove your ROM busybox from /system xbin and /system/bin (Synapse will use the kernel busybox in /sbin).
Force stop Synapse and delete app data (device settings > applications)
Re-flash kernel as per Installation Instructions
OR
Try install a different busybox
Force stop Synapse and delete app data (device settings > applications)
Re-flash kernel as per Installation Instructions
Synapse or BACKUP/RESTORE ISSUES
It's a ROM busybox or sqlite3 compatibility issue
Remove both your ROM busybox & sqlite3 from /system xbin and /system/bin (Synapse will use it's own from kernel /sbin).
Device > settings > applications > Synapse > force close & wipe data
Reboot or re-flash kernel as per Installation Instructions
BACKUP & RESTORE
DO NOT restore profiles from different kernel version
Refer to THIS post for "how-to" screen-shots
Refer to THIS post for a "how-to" video (thanks @aldoblaga )
LOADABLE MODULES AREN'T WORKING
Check your /system/lib/modules directory. Are any ____.ko present?
Did you flash a ROM or wipe the system partition at any point? Doing this will remove them !
Re-flash the kernel will install the modules.
If modules aren't installed after flash, then re-flash and manually mount system in recovery first.
You can check running modules in terminal with:
Code:
lsmod
KTOONSERVATIVE GOVERNOR
Some info from the author: http://forum.xda-developers.com/showpost.php?p=60223338&postcount=3
DT2W & COLOUR CONTROL
No, I cannot make it work properly with single source for all supported variants
CPU POWER CONSUMPTION
The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC (by ANANDTECH - Andrei)
F2FS SUPPORT
It's not needed. You wouldn't see any difference or measure much, if anything. Not worth the potential trade-off. This is not eMMC anymore
http://bgr.com/2015/03/17/galaxy-s6-storage-benchmarks/
STUCK ON SAMSUNG BOOT LOGO AFTER FLASH
Ensure you flashed the correct kernel for your device model
Ensure your download is not corrupted. Check MD5 hash or re-download
Your current base firmware (ROM, boot-loader version etc.) may be incompatible - UPDATE to latest with Odin and try again.
CM SUPPORT
Read Post #12
"Unauthorized actions have been detected, reboot to undo changes"
As it's a common warning found with all KNOX enabled android devices, you would have found the answer by Google search and also that it is actually unrelated to kernel and also unrelated to this kernel development..............
It is caused by the process of rooting/modifying your device. Unless you use KNOX, don't worry.
[Q] How to disable
[A] Freeze or delete your KNOX & Security related apps/processes manually (using root explorer or titanium backup (pro) or use Synapse > Security > disable KNOX
CAN I USE OTHER KERNEL CONTROL APPS
No, many features and options won't be available. Remove all other control apps to avoid conflicts !
Synapse is the recommended and has everything you need
BATTERY TIPS
Try some (or combination) of the CPU MULTICORE features in Synapse:
HMP profile = Battery
Power Aware Scheduling (slight performance cost) = Enabled
HMP LITTLE Packing (slight performance cost) = Enabled
PEWQ (power-efficient workqueue) (slight performance cost) = Enabled
Set A57 & A53 Interactive governor profile = Battery
Set Input-Booster for key/touchkey profile = Battery
Multi-tasking: enable UKSM & "low" or "quiet" profile (slight performance/battery cost)
Set all Advanced wake-lock controls to 1, except GPS. Set it to 4
Set WiFi wakelock control to 2 or 3
PERFORMANCE TIPS
Set A57 & A53 Interactive governor profile = Performance
Set A57 & A53 Interactive governor = Turbo Mode (battery cost)
Once in a while:
Optimize Databases
FSTrim
RANDOM REBOOT
Don't UV or UC CPU or GPU
Use SkyHigh defaults
Use a stock UNMODIFIED ROM for your device variant
No tweaks, Xposed or other CPU control apps installed
ASV_GROUP (ALL DEVICES ARE NOT CREATED EQUAL)
This is an example from my Exynos5420 source. Similar idea for Exynos420
http://forum.xda-developers.com/showpost.php?p=61579949&postcount=202
CAN I INCLUDE SkyHigh KERNEL IN MY ROM
Although I do appreciate your contribution here, if you could please do not include my kernel in any ROM package etc. This policy goes for anyone.
Having my kernel distributed outside my development thread just removes a lot of credit and more importantly, constructive user feedback that could be helpful to my development or user issue.
DOWNLOAD LINK NOT WORKING
I want to keep this project all in one place - ☆☆ NO MIRRORS ☆☆
Please try again in a few minutes
POOR CPU/GPU BENCHMARK or GRAPHICS PERFORMANCE
Disable any CPU MULTICORE options in Synapse
Disable any Battery profiles in Synapse. Set to default or Performance.
Allow the device to cool. Repetitive testing will heat the device hardware and invoke thermal throttling and lead to decreased benchmark.
HIGH CPU/GPU OC >> excessive heat >> thermal throttling >> reduced clock frequency >> DECREASE PERFORMANCE
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
* [Christopher83]
This feature allows to have two different intervals for dirty page
writebacks and to dynamically manage them when the system has been
resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature,
set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page
writebacks when the system is active (screen on)
- dirty_writeback_suspend_centisecs is the interval for the dirty page
writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's patch:
https://github.com/franciscofranco/mako/commit/34d79548cf16b69c7d0154836018e7f258a22947
Click to expand...
Click to collapse
TCP/IP NETWORK SECURITY
* Thanks to zeppelinrox & V6SuperCharger
Hardening the TCP/IP stack to SYN attack
Bump up tw_buckets in case we get DoS'd
Ignore pings
Don't cache connection metrics from previous connection
Don't pass traffic between networks or act as a router
Enable spoofing protection (turn on reverse packet filtering)
Don't accept source routing
Don't accept redirects
- Further reading:
http://www.cyberciti.biz/faq/linux-kernel-etcsysctl-conf-security-hardening
http://www.symantec.com/connect/articles/hardening-tcpip-stack-syn-attacks
CHROMECAST - STREAMING PROBLEMS
* Thanks to @AtLmd Post
Lock screen MUST be enabled (simple screen lock swipe) I don't know why but it breaks the chromecast app's ability to resume smoothly if switched off
Synapse > Network > DTIM (both screen ON & OFF) = 1
Synapse > Network > WIFI Power Mode (screen OFF) = FAST
.
Great work!
It feels so much smoother and faster and is using less power.
@UpInTheAir
No rush but at some point, would you mind adding a .tar.md5 odin flashable version as well?
I can create one for you if it would help you out. :good:
tdunham said:
@UpInTheAir
No rush but at some point, would you mind adding a .tar.md5 odin flashable version as well?
I can create one for you if you need help with that. :good:
Click to expand...
Click to collapse
I have recently modified my build scripts to auto create both .tar.md5 and .zip flashable archives. I choose to release just the .zip because I have it wipe the cache and also gives the user the chance to backup original kernel before flash.
UpInTheAir said:
I have recently modified my build scripts to auto create both .tar.md5 and .zip flashable archives. I choose to release just the .zip because I have it wipe the cache and also gives the user the chance to backup original kernel before flash.
Click to expand...
Click to collapse
Ok, no problem.
We'll keep you updated on how its running for us.
The users don't have too many choices for roms here since mine are the only ones released so far for our Note 5 variant (other than stock) so it shouldn't be too difficult to test.
Did u forget c is coming. Wont derail this project.
Sent from my SM-N920P using XDA Premium HD app
Do you have a google+ community?
rayraycarter4 said:
Do you have a google+ community?
Click to expand...
Click to collapse
I started one for another device a year back, but returned to XDA after many "dev" kang my work without permission and/or credit. Many still do. ...
So I just don't have the time for it, one or the other.
Kernel is running good so far
Sent from my SM-N920P using XDA Premium HD app
Been running all day now issues
v2.5 released
v2.5 update for SM-N920-P device variant
Check out the change-log in Post #2.
NOT TESTED. I DO NOT HAVE YOUR DEVICE !
XDA RULE #1 'SEARCH BEFORE POSTING". Please READ Posts #1-3 BEFORE flashing !!
Please CLEAR SYNAPSE DATA before flash: device settings > Applications > Application manager > Synapse > force stop > clear data
Have fun
Cheers
UITA
So far kernel is running great on Moar 1.3 rom. Just have default settings applied with Synapse. Any specific settings I should adjust for better performance or battery? Not too smart when it comes to adjusting the settings on kernels lol
Is this kernel fixes bad memory ram management ?
Been running this this kernel since yesterday and I'm pretty happy with the performance so far!
Quick question with Synapse, as I haven't used it before. When I clear data, and then flash the 2.5 update, do I need to go back in and re-tweak the kernel settings?
powerstroke said:
So far kernel is running great on Moar 1.3 rom. Just have default settings applied with Synapse. Any specific settings I should adjust for better performance or battery? Not too smart when it comes to adjusting the settings on kernels lol
Click to expand...
Click to collapse
Please read Post 3 (again)
torchec said:
Is this kernel fixes bad memory ram management ?
Click to expand...
Click to collapse
Please read OP (again)
weavr said:
Been running this this kernel since yesterday and I'm pretty happy with the performance so far!
Quick question with Synapse, as I haven't used it before. When I clear data, and then flash the 2.5 update, do I need to go back in and re-tweak the kernel settings?
Click to expand...
Click to collapse
Yes, and also never restore profiles between kernel version releases unless stated otherwise Can cause issues.
v2.6 released
v2.6 update for SM-N920-P device variant
Check out the change-log in Post #2.
NOT TESTED. I DO NOT HAVE YOUR DEVICE !
XDA RULE #1 'SEARCH BEFORE POSTING". Please READ Posts #1-3 BEFORE flashing !!
Please CLEAR SYNAPSE DATA before flash: device settings > Applications > Application manager > Synapse > force stop > clear data
Have fun
Cheers
UITA
I dont know why but since i put 3g on on my sprint note 5 the device started to reboot itself i made some changes in synopse i think that was the reason because when i restablished the default settings it hasnts done that can someone help me????
I want to know What settings should I try to save some battery with 2.6v without compromising the performance?