[Kernel][Tuneable][STOCK/CM] SmoothMod Kernel for SM-T311 - Galaxy Tab 3 8.0 Android Development

SmoothMod Kernel (SMK) for Samsung Galaxy Tab 3 8.0 3G (SM-T311), also may work on WiFi version (SM-T310), all stock and CM ROMs.
Development discontinued, read reason here.
This kernel is developed to give you more smoothness and stability than you can have on stock kernel and others.
Warning. Kernel may work on your device/ROM and may not. For me it works at all ROMs and for many people (on 4PDA.RU forum) it works too. Some people say (or said before kernel worked, this also can be) it doesn't work. So do a kernel backup please before you flash it first time. I've never had boot or usage problems with SMK, but it could be because i'm its developer (though it can not be the reason for that I'm always successfully boot it..). So it seems that our devices of the same model might be different. Be careful as I can not help you.
Features:
- Kernel version updated up to 3.2.26 and keeps updating
- Safe CPU overclock to 1.9 GHz with CPU-Boost kernel driver developed also by myself
- Custom (and only here) governor Smooth that is made to give both good battery saving and absolute smoothness. Uses GPU load and io_wait to additionally increase frequency at the right time.
- Kernel has a custom Android service smkd that controls all its features and provides many tweakable settings that you can change very simply: through terminal command "smkd" (instructions below) or "by hands" at folder "/smk" (like usual linux kernel settings at "/proc/sys/{kernel|vm|net}"). The program is written in C language, not as a script, for performance (shell-scripts are very slow when comparing with optimized C-programs).
- Tweak Menu that can be found if you type 'smkd' in your terminal.
- SmoothnessControl - one of smkd's functions that tries to guarantee UI smoothness to your tablet even if there are very CPU-hungry (but not I/O) apps/programs running like android.process.media and others. By default disabled. To enable, type this: 'su -c "scd --enable"' in terminal emulator. To disable, type 'scd --disable'.
- CPU Undervolt controlled through smkd.
- DynBS program (also developed by me) used by smkd to improve battery saving by 40% and more.
- Boeffla Sound Engine with custom settings, not working with Boeffla Sound Control app because smkd controls them (it's needed because smkd fixes engine's sound effects bug). Settings are stored folder "/smk" in files beginning with "boeffla.".
- Cron scheduler configured from file /sdcard/cron/root.
- All the custom tweakable settings described upper are reloading instantly after you change them or on delete (cron schedule file is also under the same watch).
- Kernel is compiled with optimized HYPER-TOOLCHAIN with gcc version 6.0 and maximally optimized compiler configuration.
Customizing kernel:
There is now nothing that needs to be explained, as customizing is pretty simple! Just type command 'smkd' (without quotes) and go through the menu (by entering appropriate symbols) as you want, changing parameters as you need.
Ask, if you have questions
If you have questions or suggestions about my kernel, feel free to write about that here and I will try to answer.
F.A.Q.:
Q.: Do I need to wipe Dalvik/ART cache before/after flashing this kernel?
A.: It is even not useful to wipe caches because they are used by Android only, not by kernel. So, it's not needed.
Q.: The kernel does not boot! What do I have to do to boot it?
A.: Write a message in this thread providing info about what ROM do you use, what Android version it is and what kernel build (kk/lp/mm) and version you are trying to boot. I will reply to that message and try to fix that problem.
Author: me, igoryan94
Download from Google Drive
Before flashing this kernel please do a backup yours first!
Warning! If you have a Jellybean/Kitkat rom, then download the smoothmod-kernel-kk-... build. If you use Lollipop (CM12), then your build to download will be ...-lp.... If it is a Marshmallow (CM13), then download mm build.
Other choice will cause your device to not be able to boot!
(Sorry for my (maybe )bad english)

Plans:
-
Developing now:
-
Changelogs (old*):
1.2.1/1.2.2:
- Returned possibility to load a profile from command line (command 'smkd --load [name]' or 'smkd ld [name]')
- Added custom setting for apps CPU time, now it has two groups: idle and high.
Idle group gives an app very small amount of CPU time, use for hungry apps that you don't need.
High group grants an app a 95% of all CPU time. Use to speed up some apps or games.
It is all very similar to Greenify and others, excepting that this is not battery saving solution, only to smooth up your Android, as Greenify disables an app and CGroup lowers app's CPU execution time available to it.
- I/O settings fully rebalanced for smoothness for system processes and apps processes
- Also added control group for I/O that does like one for CPU, but for I/O and developed its correct (for Android) behavior.
- Current configuration name in smkd menu now correctly saves and loads after reboot.
- Default LMK level changed to 125
XDA->SMK:
1.2:
- Got a smoother UI with better CGroup tweaking
- In case of some situations smkd will notify user with drawing a small square of some color at the left upper screen edge (portrait orientation). For overheat the color is red. When SmoothnessControl gets to work, color is light blue/cyan. If device's load is too high, the color will be blue.
"Notification" will blink when screen updates because the framebuffer devices are not support this method of screen drawing. But it works for now and I think that it is very useful to know the reasons of device's lags and freezes.
- Menu now immediately reacts to input, instead of pressing some characters and then Enter. Modified all menus that way so the interface is now much better.
- When exiting menu, parameters are automatically saved to default profile. No need to care about it anymore...
- Added Quick settings also to RAM and I/O
- Main menu: moved all "p)" menu elements to main menu level, it is quicker to access now
- Some more Quick settings options added
- Added Quick settings to my menu templates, so I will add this to most of the new menus in the future
- Main Quick settings colors changed to blue, additional are still white
- Overclock to 1920 MHz lowered to 1800 MHz because 1800 is much more stable (1920 causes reboots on Marshmallow on my tablet)
- Device now reboots when charging speed is too bad. By default this is disabled. Also added setting "Charge cycle time" and Quick settings for that so you can quickly set up to what charge speed you need (reboots are helpful but not very good for users that want to play device when it charges).
- 'Boost' feature disabled so now DynBS will work as always even when device is laggy
Previous:
1.1.22:
- CPU, Boeffla Sound and Network setting menus in smkd now have the Quick settings feature that helps to configure them by one click instead of tweaking them each
1.1.21.1:
- DynBS updated: now it uses frequencies from 350 to 700 MHz too, so more battery can be saved.
1.1.21:
- smkd now has menu interface which opens by default by command 'smkd' without options.
- All setting commands are removed. Use menu instead.
- In Cyanogenmod ROMs SystemUI is restarted every time when screen becomes disabled, so you may never see it lags or freezes again.
- PCS renamed to SC (SmoothnessControl).
- Overclock enables when device is laggy even when it is disabled in settings
- Redone temperature control: now smkd monitors a device temperature instead of CPU. It leads to better smoothness. Also overheat situations disable some functions like I/O readahead, ZRam, KSM.
- Overheat prevention function fully removed
- Governor Smooth now enables both cores on gestures with two or more fingers instead of simple tap.
1.1.20:
- Added charging compensation: now when battery charging is too slow, CPU Topology and voltage will be changed appropriately for quicker charge.
- Touch boost changed from 1400 to 1000 MHz, but it also boosts busfreq to 400 instead of 267 MHz. Results in better reaction on screen touch.
- Governor Smooth's default sampling_rate changed from 27000 to 16000 for quicker reaction
1.1.19:
- Added ARM CPU Topology for better multithread scheduling
- Some CPU Scheduler changes for smoothness or power saving (tweakable)
- Improved smkd UI code
1.1.18.1:
- Fixed performance/smoothness problems.
1.1.18:
- Added new default configuration "throughput"
- GPU acceleration is now forced for all apps and it is changeable from smkd.
- I/O scheduler SIOPlus added.
- DynBS is returned (one user asked for it as it really saves battery, as he said).
1.1.17:
- User profiles are no more exist, replaced with default configurations" instead. They are: smooth, battery, ram and cool. After each launch of smkd (mostly on reboot) configurations are removed and recreated to always be fresh and up to date.
- Added ability to create, rename and delete profiles by normal way, but default profiles cannot be replaced, deleted or renamed through smkd (only "by hands").
- GPU settings: composition and forced GPU-acceleration from Android settings for developers.
- Tripndroid and Zen I/O schedulers are added.
1.1.16.1:
- Configurations loading is now be always successful (but only if appropriate file exists), without that annoying errors "try again later, please..."
- Small tweaks optimization
1.1.16:
- Overclock now disabled by default, as it was on 1.1.14 and before, for battery saving (overclock eats too much battery). Can be enabled with command 'smkd -c -o 1'. Temperature control is now optimized for both CPU overclock and hardware maximal frequency modes.
- smkd interface improved a little.
- KSM functionality added with some fixes for Mali GPU driver bugs in userspace.
- Default temperature limit is now 64 C (before it was 67 C). This is done for more stability when the weather is hot.
- Some changes for smoothness and stability...
1.1.15:
- Overclock is enabled now for any time when screen is enabled (no more boost).
- Developed overheat preventing functions that cool device when temperature is between 90% of threshold and higher. CPU frequency will be set according to temperature for the moment (for every 2% will be a different frequency). Function can be disabled but it is not recommended.
- All cooling functions now control voltage too to be more effective.
- Governor Smooth tweaked for more balance (oc_nr_run_threshold->6)
- Governor Smooth: changed logic: half-overclock (to 1.7 GHz) will occur if number of processes running is a half of oc_nr_run_threshold tunable.
- smkd now controls I/O scheduler and I/O readahead settings, they are tweakable with smkd command. Profiles change this parameters too.
1.1.14:
- smkd tweaker program fully translated to english and comes now in two languages. Now it uses Android's property 'persist.sys.language'.
If your device configured for any language excepting russian, then program will be in english for you. At the other case it will print out text and messages in russian.
- Improved custom configurations in smkd. Now it loads profiles synchronous with service (by using mutex) instead of relaunching it with shell stop/start (it was too slow and even buggy to do that).
- DynBS will not be in kernel anymore, it is not so effective as needed. Instead, I've added a profile tweaks for my governor Smooth, that tweaks easily changeable from smkd (cmd. "smkd -c -s [0-2]").
1.1.13:
- Cron scheduler now works correctly (i'm happy ), doing exactly what was scheduled by the user at the exact times.
- I don't remember what was in this version because forgot this as I worked on 1.1.14 intensively.
-----
* Newer versions contain changelogs in install archive itself.

Very good kernel. Use [5.1.1] Resurrection Remix 5.5.9 + SMK 1.0.20.1 lp.

Nerovinger said:
Very good kernel.
Click to expand...
Click to collapse
Thanks

stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app

so.hell said:
stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
What ROM do you use? Android version, SMK version?

AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app

so.hell said:
AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like it will not work on AICP ROM, on Cyanogenmod 13 and ResurrectionRemix kernel works fine (I've tested that)... Sorry The reason for that I can not fix this problem is that I do not know (even cannot know) how to make an init.rc (this file starts all Android services on boot) file universal (to support absolutely all ROMs at one time). This is also the reason for three builds of kernel: kk, lp and mm...

Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?

Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12

pawas99 said:
Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12
Click to expand...
Click to collapse
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.

Luis_0 said:
Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?
Click to expand...
Click to collapse
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
There are too much incompatibilities with builds that are now (they must work everywhere but they don't)...
Ok. Added one question to poll. There are three variants for ROM and two for working or not (six at all), for me all works fine, so I voted for the first three answers.
Version 1.1.14 developer testing ends now, smkd fully translated to english. I will now build the kernel and then begin uploading it to Google Drive.
(sorry for my incorrect english)

igoryan94 said:
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.
Click to expand...
Click to collapse
Stuck at bootanimation even after flashing on a clean ROM.

waiting for update..

Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again

Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.

igoryan94 said:
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
Click to expand...
Click to collapse
@gr8nole could help him in this?

xdaSEx10 said:
Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again
Click to expand...
Click to collapse
CPU frequency is automatically changed to 1920 MHz when special conditions are met (they are: "blocked" processes and waiting for I/O).. Version 1.1.5 will have full 1920 MHz CPU frequency.
I will now upload "developer" version of kernel 1.1.15_dev for KitKat users. If you want, test that) It is not fully contains all changes that i've done, but I'm not at home now and cannot compile new build... For now it has smooth overheat prevention and overclock fully enabled.
Hunter97 said:
Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.
Click to expand...
Click to collapse
Please wait for SMK version 1.1.15, it will use 1920 MHz as a default frequency always excepting overheat moments (that will disapear very quickly) and governor's battery saver mode.
You can also use a developer version 1.1.15_dev if you use JellyBean/KitKat as your ROM.
Ok, "dev" version released for testing.
When I will return home, I will release another testing version that has an I/O scheduler change functionality, optional Overheat Prevention and changing min_freq to minimal (50 MHz) when temperature event occurs. Maybe it will have even more features (I have smkd code with me, PC is only needed for compiling kernel and ramdisk).

on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.

jamax80 said:
on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.
Click to expand...
Click to collapse
SMK will not boot on T310. Only T311.

Related

[ROM-FroYo] SetR0M 4.5 |UVOC-HAVS-INTERACTIVE||FRF91||Cam-HQ||LED||ECHO| [26/07/10]

Thanks to richardtrip, pete, Kali, Manup456's, persiansown, jimbob343, pershoot, droidbasement
- Froyo A2SD use SpareParts to change where to store apps (internal or external)
- For old A2SD create a ext3-4 partitions and that's all, no need to change in Sapreparts, all apps are installed on ext partitions
- Thanks to #Teamdesire
IF YOU HAVE PROBLEMS WITH THE ROM, WIPE DATA + CACHE and try again BEFORE REPORTING BUGS!!!!
Now available through Rom Manager
HAVS what is it :
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.
Interactive governor what is it :
This governor is designed for latency sensitive workloads, UI interaction for
example.
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Existing governors sample cpu load at a particular rate, typically every X ms. Which can lead to under powering UI threads when the user has interacted with an idle system until the next sample period happns.
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to.
SetR0M Tools and goodies :
- Some nice wallpaper to your Froyo NexTheme here
- Revert to default fonts : SetR0M-AndroFonts
- Revert to default keylayout for wake up phone here
Things you have in 4.5 :
New Radio needed if you come from older version as SetR0M 3.6 (32.41.00.32U_5.08.00.04)
[FULL] SetR0M 4.5 stock kernel 998Mhz Max with interactive governor
[KERNEL] SetR0M 4.5 UVOC kernel 1113Mhz Max with interactive governor
- No wipe required
- HAVS kernel with interactive governor need more testing so coming soon
- Quadrant score 1677 w/UVOC 1113Mhz Kernel and interactive governor (screenshot added)
- Freshly compiled Kali kernel msm
- Added new interactive governor in stock (change governor as "scaling interactive" in setcpu)
- Fixed Led
- Fixed battery drain
- Updated Titanium backup, Fancy Widget, Rom Manager
- Fixed echo
Changelog SetR0M 4.0 :
- Freshly compiled Kali msm kernel and compiled with full optimization
- Updated Romamanager, Titanium Backup
- Fixed default brightness value (thanks to Defrost)
- Updated ADW Launcher and themed
- Fixed some optimizations
- Added new HAVS Kernel not as default download separately and flash like an update.zip
- Optimized theme and fixed some png
- UVOC kernel coming soon
Changelog SetR0M 3.6 :
- Freshly compiled Kali msm kernel
- Really fixed echo
- Fixed GSensor
Changelog 3.5
- Updated kernel last commit Kali (freshly compiled)
- Only stock kernel 998Mhz, OC-UVOC-HAVS coming soon
- echo fixed (thanks to Richardtrip)
- H264 Camcorder
- Updated mediaprofile 480p
Changelog in SetR0M 3.3 :
- Fixed Calendar widget
- Fixed Voice search
- Fixed Download notification bar
- Replaced default MusiGoogle with Music Mod (by Eliot Stocker)
Changelog 3.2
- Removed SetCPU (coolbho3000, author request)
- Updated Titanium Backup, ADW Launcher (themed), Rom Manager
- Fixed third party apps update
- Optimized and zipaligned
- Updated media profile HQ Camcorder (thanks to Defrost)
Changelog 3.1
- Fixed Youtube (Big thanks to Defrost)
- Complete redesign of the rom with last commit from Manup456's (NexTheme), a lot of news
- Added Setcpu and setcpu.txt in sdcard (use only if OC Kernel)
- Optimized internal Android Task Killer, no need apps for that now
- Kali 2.6.32.9 qdsp - Kernel freshly compiled today / LED FIXED thanks to IEF
- Portable hotspot (wifi tether)
- Fixed Openvpn
- ADW Launcher is default now, and themed
- Zipalign a each boot
- Phone.apk from Defrost Rom fix echo
- Camcorder fixed
- High res 800x480 camcorder
- Optimized and zipaligned
- fixed some permission
- optimized process implemented
- zipalign on boot possible with SetR0M tools
- Added Openvpn
- Added Fancy Widget, Rom Manager
- LiveWallpaper from Samsung I9000
- All media from Samsung I9000
- Custom Bootanimation (thanks Potter97)
- Themed all the rom
- Removed Twitter and Facebook (install from market)
- Added SpareParts and themed
- Added Titanium Backup
- Froyo A2SD use SpareParts to change where to store apps
- Superuser, busybox .....
Donator Thanks :
Choong Yoke Choy
stingerpl
Café King
Sophocleous
Ekowanz
Igor Grlica
skynapster
Lorenzo
Kolemar
Paprikapulver
Heinemann
Lee King Chi Kings
I you like my work buy me a
​
Nice! I'll give this a go once it's uploaded. What differences are there now it's de-odexed?
socktug said:
Nice! I'll give this a go once it's uploaded. What differences are there now it's de-odexed?
Click to expand...
Click to collapse
More free space, and now you can theming the framework
JupiterDroid said:
If we are coming from a defrost 0.7d rom, do we have to wipe? or can we just flash?
JD
Click to expand...
Click to collapse
Full wipe is required
Can I apply a Nexus One Cyanogen or Froyo theme to this?
Jeppfi said:
Can I apply a Nexus One Cyanogen or Froyo theme to this?
Click to expand...
Click to collapse
The theme are rom specific you can't
Downloaded, installed and booted. A promising start
Loving the fact the battery icon has the percentage in it...Although the percentage is very small!
Under the call settings menu, what is TTY mode? I don't think I've seen that before.
socktug said:
Under the call settings menu, what is TTY mode? I don't think I've seen that before.
Click to expand...
Click to collapse
text mode for deaf
do you have the battery drain display issue with this rom?
JD
JupiterDroid said:
do you have the battery drain display issue with this rom?
JD
Click to expand...
Click to collapse
I use only for 5-6 hours now but no battery drain, kernel is DeFrost 0.7d and battery drain is kernel specific i think
I think the battery icon in the notification bar is faulty. It hasn't moved from 80%. My battery is currently at 78% in settings.
Re: [ROM-FroYo]SetR0M RC1 Deodexed Froyo !!!
I think the battery icon in the notification bar is faulty. It hasn't moved from 80%. My battery is currently at 78% in settings.
Click to expand...
Click to collapse
Only 10 by 10
-------------------------------------
Sent via the XDA Tapatalk App
will you do me a favour and check your battery usage and tell me your stats please mate
JD
Yip, display is showing 62% after 20 minutes of uptime. So I'd say that bug is still to be sorted!
I'm getting linpack scores of 41.01 and It's not overclocked, so that's good!
is it the display bug, is your display high?
Also did you full wipe before you came to this rom? i did a logcat of the system on 0.7d and there was many errors generated, i think this is whats causing the problem, but getting a answer out of richard is like waiting for a solar eclipse
JD
JupiterDroid said:
is it the display bug, is your display high?
Also did you full wipe before you came to this rom? i did a logcat of the system on 0.7d and there was many errors generated, i think this is whats causing the problem, but getting a answer out of richard is like waiting for a solar eclipse
JD
Click to expand...
Click to collapse
I wiped using the new recovery in the rom manager. My brightness is set to auto, which is fairly low, and granted the display has been on a fair bit as I set it all up again!
I suppose a few hours will tell more. Considering this is based on richard's kernel I imagine the bugs will be here too. I have to say though that this one is a fast wee rom!
The display issue has nothing to do with excessive power drain, it's just the status software reporting an incorrect value for display.
So please, leave it be, and concentrate working on i.e video recording (720p any1? Wanna leave the iPhåne 4 in the dust! )
All respect goes to trip for his hard work, I prefer him working on the DeFroST rather than discussing all kinds of crap, wheter the cat should be neutered, or whatever
Troels
Denmark
puttitat said:
The display issue has nothing to do with excessive power drain, it's just the status software reporting an incorrect value for display..............
Troels
Denmark
Click to expand...
Click to collapse
Do you have a source for this?
socktug said:
Do you have a source for this?
Click to expand...
Click to collapse
I'am a (little) source. Before the desire i've had a milestone (stock android, no special interface like sense or something else). I've had the same batterypower like the desire but there were always display around 60 or 70% battery usage. so it seems that this is a wrong (or maybe right?) fact of the stock android.
you have to excuse my bad english^^...but i can the german language much better

[Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.4 (17-Mar-2011) Now With HDMwIn

NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
"netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
Click to expand...
Click to collapse
So what's in the kernel?
- Overclocking Support
- HDMwIn (As of 4.3.4)
- Audio gain tweaks (read: make it louder!)
- Fps Fixes
- tun.ko for openvpn users
- CIFS support (as of 4.2.2)
- BFS (in select builds)
- BFQ (in select builds)
- HAVS (as of 4.1.9)
- Assorted fixes/tweaks (that are sadly too numerous to list here)
- An army of rabid naked bunnies
Click to expand...
Click to collapse
The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).
Click to expand...
Click to collapse
mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
You can view this guide Here
Click to expand...
Click to collapse
Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4
Click to expand...
Click to collapse
A note on multitouch:
Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.
Click to expand...
Click to collapse
Disclaimer:
While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
As such your mileage may vary, use these at your own risk.
Click to expand...
Click to collapse
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
Click to expand...
Click to collapse
If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
Click to expand...
Click to collapse
-----------------------------
2.6.32-based Kernels:
Click to expand...
Click to collapse
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------
FAQ:
Code:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation
CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Q: Do I need to be rooted to use this kernel?
A: Yes, you need to be rooted, preferably a full root with nand unlock,
Q: How do I flash this kernel?
A: Copy the zip to your sdcard, and flash it from recovery mode
Q: My phone is suddenly unstable after using this kernel and I experience
weird things like reboots or other bugs
A: Are you overclocking? Try lowering the max speed of your overclock.
If the problems stop, you were overclocking too hard. If not,
please include the following information when reporting issues:
1. Your Baseband
2. What rom you're using
3. Your software number
4. Your panel type (Nova or Epson)
5. A Description of what's happening
Q: Why can I only overclock to 1152mhz? (In builds prior to 4.1.x)
A: Frequencies above 1152 have repeatedly turned out to be unstable for
a large percentage of users, so they have been removed to
eliminate the temptation to use them (and then complain because
they are unstable ;D).
Q: Does this kernel work with 2.2 (Froyo) roms?
A: The "Froyoized" kernels do
Q: Will this kernel work with my custom rom?
A: Maybe. The general population build of the kernel should work with
*most* custom roms, but as each custom rom can have it's own
customizations, your mileage may vary. In some cases, particularly
when a lot of customizations are in the rom's ramdisk, the kernel
must be repackaged with the ramdisk from the custom rom to be compatible.
Release notes:
Code:
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
Notes for Revision 4.3.2
- Wimax code updated, 4g should behave a bit better
- SD card read ahead fixed, higher class SD cards should
have an easier time reaching their potential speeds
Notes for Revision 4.3.1
- Screen tearing issues on sense roms should be fixed
Notes for Revision 4.3
- Camera drivers updated to support phones with the newer camera sensors
- ms79723's SBC v7 mod integrated for enhanced battery charging
- Misc speed tweaks/optimizations
Notes for Revision 4.2.2
- Kernel updated to 2.6.32.27
- Conservative set as default governor again
- Conservative governor defaults tweaked
- Less aggressive build has even more relaxed undervolting to aid those with REALLY picky phones
Notes for Revision 4.2.1
- Kernel updated from a 2.6.32.15 to 2.6.32.25
- Interactive governor added and tentatively set as default in some test builds
- Smartass governor added and tentatively set as default in some test builds
- Added BFS 357 smartass builds
Notes for Revision 4.1.9.1
- HAVS has made a return, this should help improve battery life by automatically dynamically undervolting the cpu when possible
Notes for Revision 4.1.8
- Added the BFQ I/O scheduler
- Split out kernel editions, now users have a choice between a CFS or a BFS kernel, if you don't like one, try the other ;D
- Enabled shadow writes on the gpu, which may result in better performance in opengl applications
Notes for Revision 4.1.7
- Add BFS to the kernel
- Allocate more memory to the gpu, this may result in better performance in opengl applications
- A rabid naked bunny vampire has materialized under your bed. Be afraid.
Notes for Revision 4.1.6
- Users with touchscreen issues should find their touchscreen is no longer as responsive as a stereotypical wife on her 10th anniversary
Notes for Revision 4.1.5
- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion
- Clock frequency table remains opened up, with static undervolting in place
- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
Notes for Revision 4.1.4
- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)
- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so
- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)
- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
Notes for Revision 4.1.3
- The ondemand governor is enabled as an option (switch to it in setcpu if you want to use it, remember you'll have to update your profiles to use it as well).
The default currently remains conservative to have a balance between performance and battery.
- The small segment of users getting bootloops due to the undervolting being too aggressive should be able to boot the kernel now (though if it persists the undervolting can still be adjusted)
Notes for Revision 4.1.2
- All frequencies above 1152 should now be properly visible/usable in setcpu (You may need to re-detect speeds in setcpu first)
Notes for Revision 4.1.1
- Hot on the heels of 4.1.0, a minor versioning fix ;D (4.1.0 reports itself as 4.0.3)
Notes for Revision 4.1.0
- Adapted HAVS for the evo, this may improve battery life by allowing the cpu to run at lower voltages when possible
- The overclocking range has expanded to allow attempting to clock above 1152, Remember that overclocking is unpredictable and potentially unstable by nature, if you encounter problems overclocking, lower the speed.
- Some threshold adjustments to the conservative governor in the interest of improving performance without obliterating battery
- Wired tethering should theoretically work, however if there are problems with the app, an alternative is azilink for wired tethering
Notes for Revision 4.0.3a
- An experiment of sorts, changing from the ondemand speed governor to the conservative governor (with some tweaks), in the interests of keeping good performance with less impact to battery life.
- Rewritten update scripts to hopefully alleviate the small number of people who seem to be having a problem flashing the kernel
Notes for Revision 4.0.2:
- People having stability issues with overclocking to 1152 *may* find it is a bit more stable (your mileage may vary)
Notes for Revision 4.0.1:
- Speed range should now allow underclocking to 128mhz (You may need to re-detect frequencies in setcpu)
- The Nova panel T2 register should be changeable again (for you Evo Switch/Novareq users)
Notes for Revision 4.0:
- Updated to the latest HTC released kernel sources (2.6.32)
- Camera should now be working properly
- HDMI output should be working in Froyo again
Notes for 3.7.8b-Froyoized
- Camera should no longer take dark snapshots when using the flash, the monster responsible has been severely beaten with a twig.
Notes for 3.7.8-Froyoized
- Camera app should no longer crash when changing from 5:3 widescreen to 4:3 standard ratio
- Camera app should properly allow 720p video recording and playback
- Japanese researchers have begun construction on a mecha-rabid naked bunny, codenamed: Bunnytron.
Notes for 3.7.7-Froyoized
- Re-integrate zipalign check and Dalvik cache tweak from the 2.1 line
- Some adjustments made to bluetooth-specific audio tweaks to combat distortion
- Audio adjustments to combat background noise overpowering the voice on the other end of a call
- Set version tag correctly (har har!)
- Super-mutant rabid naked bunny successfully created in lab conditions, however it disintegrates upon exposure to reality.
Notes for 3.7.6c-Froyoized
- SDcards with ext partitions added on should now cease confusing Froyo and allow the card to be mounted properly (Special thanks to Ninpo for directing me to the fix)
Notes for 3.7.6b-Froyoized
- Touchscreen adjustments, this may fix those who had touchscreen issues with 3.7.6
Notes for 3.7.6-Froyoized:
- Compatibility with the leaked 2.2 ota (and probably other 2.2-based roms)
- Working Camera (Limited to 3megapixels) EDIT: Reports indicate it claims 3mp but actually functions at 8mp
- Fps fix (of course ;D)
- Wireless Tether is reported as working with this as well
- 4g is confirmed as working
Notes for 3.7.5:
- Toned back audio boost tweaks a little to address distortion issues
- Updated gpu code for some 3d speed improvements
- Prevented the horde of mutant hairy toe-monsters from spreading toejam
all over the thread.
Notes for 3.7.4:
- Updated bluetooth code, courtesy of cyanogenmod
(You may have to re-pair your bluetooth devices)
- A new audio boost tweak has been applied
(This should not have the issues of the previous audio boost)
- Fixed an issue that would cause some Nova users to mysteriously
revert to 30fps. (Bad nova! no cookie!)
- Successfully avoided maiming any sabretooth'd tiger-striped cows
during the production of this update.
Notes for 3.7.3c:
- Some more tweaks to default performance (when not using setcpu/overclock widget)
Notes for 3.7.3b
- Killed that damn bug monster that decided yet again to sneak into one of my builds. Bad monster! No cookie.
Notes for 3.7.3:
- Adjusted the behavior of the speed scaling governor to give better performance out of the box for people that don't use setcpu or overclock widget
- Made adjustments to the general population build in the interests of making it compatible with Apps2SD by request.(Damage control users should have already been unaffected)
Notes for 3.7.2a
- Gave the monster holding wifi and 4g hostage a spanking (read: wifi/4g should be fixed)
Notes for 3.7.2
- Tweaked Nova settings in the interests of making sure everyone with a nova panel benefits from the fps fix
Notes for 3.7.1:
- Kernel should now have 100% more working HDMI output, no really, we mean it this time!
Notes for 3.7:
- HDMI output should now work in conjunction with boosted Nova/Epson fps
- tun.ko is now included by default for VPN users
Notes for 3.6.4:
- Behold, the return of 5point multitouch! This build should now automatically enable 5point multitouch for all phones that can support it. If the phone does not support 5point, it will default to 3point.
Notes for 3.6.3:
-Removed problematic audio boost patch that was giving issues with bluetooth
-Adjusted overclocking frequency tables to remove some problematic frequencies (Yes I know a small selection of you are going to be disappointed with the lowered cap, but I felt that the problems were more important at this time.)
-Evo switch ideally should not be required for decent framerates on Nova panels, but if users desire, by popular request, they can now use Evo Switch to tweak their T2 register [U]without[/U] it resetting after a screen cycle
-Default T2 value adjusted to 370, AssassinsLament believes this to present a good balance between out of the box performance and compatibility
-No fluffy pink bunnies were harmed in the making of this build
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Awesome, I have a Novatek. /facedesk.
jerryparid said:
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Click to expand...
Click to collapse
Should be flashable with either Clockwork or Amon Ra. Theoretically it might work on Froyo, but I've only tested it on Eclair.
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
mattrb said:
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
Click to expand...
Click to collapse
Yes the camera works on this in 2.1
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
jerryparid said:
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
Click to expand...
Click to collapse
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
imaxreed said:
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
Click to expand...
Click to collapse
umm? http://forum.xda-developers.com/showthread.php?t=711964
Best kernel on my epson screen. I like how i can overclock as well
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Thanks. I have seen that thread a hundred times but never entered it. The FPS doesn't bother me too much I am going to mess with this tomorrow i have the day off thank you.
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Yeah i'd love to see this fix for nova
netarchy said:
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
Click to expand...
Click to collapse
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
jerryparid said:
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
Click to expand...
Click to collapse
Hrmm, is it glaringly obvious in any particular app? I'd like to see if I can reproduce the experience myself.
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
krazyflipj said:
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
Click to expand...
Click to collapse
Trying it out now, no problems with youtube for me.
Tearing doesn't seem as bad as I remember, but still bothersome.
when i seen this, i jumped into the air with my fist up like a touchdown at the superbowl.
flashing in juuusssst a second..
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
same !!!!

[KERNEL][3.0.31][HDMI][FULL HD][GUIDE 1.8]JBX-Kernel Hybrid [1,5ghz]

/// JellyBeanX-kernel ///​
DISCLAIMER
Me, XDA-Developers.com and anyone else doesn't take any repsonsibilty for damages on your device!
Rooting your device will void your warranty!
Don't play with settings you aren't familiar with, you could burn your device!!
Click to expand...
Click to collapse
READ THIS: I added almost all important topics which have been discussed around the kernel thread to the OP and wrote this FAQ just that you guys don't have to browse through 100+ pages of the thread. READ BEFORE YOU ASK and HELP TO KEEP THIS THREAD MORE CLEAN! BUT ALSO BETTER ASK ONCE MORE BEFORE YOU MESS UP YOUR PHONE! If you find something missing in this OP/FAQ, please PM me and I will add it. Thank you!
You can find the FAQ at the bottom of this post!
This is a direct port of my RAZR-JBX-Kernel Hybrid for Motorola Razr!
This kernel is built of the Kexec Project which was initiated first by Kholk & [mbm] and finished by the STS-Dev-Team (Hashcode, Dhacker). Using this kernel will provide addtional features to your ATRIX 2.
LATEST CHANGES (for latest release and NIGHTLIES)
--> DETAILED CHANGELOG JBX-kernel Hybrid <--
Kernel Guide by Placca 1.8!!
Check the FAQ section at the bottom of this post to download it! It will make many things easier for you and help you to understand the kernel and its features!
FEATURES
JBX-Kernel Hybrid
Battery Friend toggle (a battery friendly mode)
Intelli-Plug (Kernel side replacement for msm MPDecisions) by Faux123 + patches by me (no hotplugging when screen is ON)
Dynamic Hotplug: Second core will be turned off ONLY while screen is off - independent from selected governor. (Not needed when using Intelli-Plug)
Optimized OPP Table for smooth CPU scaling
Frequencies: 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300
Modifed Smartreflex driver (Custom Sensor for detecting n-Value).
Smartreflex Tuning Interface: Set min/max calibrated voltage
Overclocking using Live OC (mine runs stable at a maximum frequency of 1,498ghz!)
hwmod, uart, IRQs - cleanups from pre-kexec config to safe power
CPU: lower voltages for CORE and IVA. Give CORE the abbility to scale up to higher voltage if needed
Added IVA_NITROSB
Dynamic fsync control: FSYNC interval is dynamic depending on screen state (SCREEN OFF: synchronous, SCREEN ON: asynchronous)
HTC's Asynchronous Fsync port - read explanation below*
Dynamic page-writeback: Page writeback interval is dynamic depending on screen state.
Frandom v2
JRCU / Tiny RCU (currently JRCU in use)
Raised voltage limits for mpu a bit
Raised the temperature limits from 64c* to 74c* (degrees)
optimized CRC32 algorithm (better code generation)
RW Readahead dynamically depending on storage device (automatic detection of the best value)
zRAM support
GPU has 4 scaling steps and OC to 384mhz (Base freq: 102 mhz --> 154 mhz, 307 mhz, 384 mhz)
GPU C4 states / GPU Control (Governors, Frequencies)
Multicore Power Saving Mode Control
ARCH Dependant Power feature
Gamma Control
Front Buffer Delay Control (draw in x msecs on early suspend)
Screen/Display: Modified OMAPDSS for sharpness and lightning colors
OMAPDSS: Added variable clock rate and OPP - allows the screen to scale down power and voltage
lowmemkiller: Heavy modified for R/W Speed and efficient performance
ZCACHE, ZSMALLOC, XVMALLOC backported from 3.4, 3.7 and 3.10 (ZCACHE currently not in use)
Custom Voltage Support
IO-Schedulers: SIOPlus, Fifo, Row, VR, Noop, Deadline, CFQ, BFQ
ROW Scheduler is heavily tweaked to be the fastest scheduler ever!
CPU: More Governors
Deep Idle
ARM Topology
Many improvements in overall OMAP PM
SELinux permissive
GREAT performance!
battery life!
Support for Trickster Mod Kernel Control App (Download from Gplay)
*]Too much stuff to list here. See "Sources" below and check my Github
* HTC's Asynchronous Fsync and Dynamic Fsync:
Asynchronous fsync (called "afsync" or "async fsync") from HTC is ported into this kernel. By default it's enabled and dynamic fsync is disabled (and as well it isn't needed anymore).
The dynamic fsync toggle in Trickster Mod is now serving both functions - the dynamic fsync AND the asynchronous fsync! How? By default Dynamic Fsync is disabled, and Afsync is enabled. If you now enable Dynamic fsync using the toggle, Afsync will be automatically disabled, so both functions are not conflicting each other - and this way we have a working toggle for both of them.
CAUTION
This is a work in progress! Some of the current features are still not in final stat. If you are facing issues report back here and DON'T spam the threads of the rom you're using!
Be careful with some settings such like Voltage and Overclocking!!! If you aren't experienced with these things, dont play with 'em!
Click to expand...
Click to collapse
REQUIREMENTS
Rooted device
Must use a Kexec Rom (CM, AOKP, AOSP)
Recovery (BMM, SS)
REMOVE any kernel modules you used before
DEACTIVATE ANY CPU tweaks, onboot settings etc otherwise your phone may not boot!
CAUTION: The kernel needs a clean setup related to CPU tweaks / Settings, etc...Keep your device as clean as possible regarding to Tweaks, CPU special settings, etc. The Kernel brings its own CPU settings and after you can boot it succesfully, you can set it like you want!
Some roms may use CPU tweaks. This can cause issues like reboots and freezes. Check the init.d folder for any CPU related stuff and Kernel modules - then remove it. E.g. Remove any scripts which include "insmod" commands.
The best setting is to have stock CPU settings set
This kernel may not work on all roms! Check and report.
TO DO LIST
- Fix bugs
- Fix compile warnings
- More features.
INSTRUCTIONS
NOTE: CLICK here for a detailled Installation Guide (about the Aroma Installer, the features to select and more)
Download zip file from below
Reboot into recovery
Flash the kernel (BMM users: DON'T use the "Flash Kernel" Option! This is a usual zip file!)
Reboot
Download Trickster Mod App from Gplay! Read the FAQ to learn about playing with kernel features!
Enjoy!
EMERGENCY RESTORE
If you have tried a Nightly build and you phone is acting crazy, you can follow these steps:
Check the thread or ask for the latest stable kernel build
NO WIPES!
Flash the Rom (Yes, again! That one you're currently using.)
Flash Gapps
Flash Kernel
Reboot
DOWNLOAD
JBX-Kernel 3.0.8 Versions:
0.8.x ==> Android 4.2.2
1.x == > Android 4.3
2.x == > Android 4.4
JBX-Kernel 3.0.31 Versions:
3.x == > Android 4.4
TEST BUILDs
Test builds are potential prerelease builds which need some more testing before pushing to all users.
CAUTION: Should be stable mostly! But use at your own risk though!!
---> TEST BUILDS [CF] <---
XPERIMENTAL BUILDs
These builds include features without promises to work.
CAUTION: There is no promise that these version are stable/working/whatever! Use at your own risk!!
---> XPERIMENTAL Builds [Dev-Host] <---
---> XPERIMENTAL Builds [CF] <---
Click to expand...
Click to collapse
Something went wrong?
If you think you have set wrong "on-boot-values" in Trickster Mod flash this:
TRICKSTER RESET: http://dtrailer.de/kernel/trickster_reset.zip
FAQ
CAUTION: This FAQ and the whole OP, additional informations about Governors, IO Schedulers and detailed informations about the usage of Trickster Mod and this kernel can be viewed in the awesome Kernel Guide by Placca!
Kernel Guide 1.8
PDF: http://www.mediafire.com/download/7zaddcmvtxfk9ry/JBX+Kernel+Guide_v1.8.pdf
CHM: http://www.mediafire.com/download/g3ck1bf1k3a3j38/JBX+Kernel+Guide_v1.8.chm
CLICK HERE TO OPEN THE FAQ
Please check the following points if you don't know how to use the features of the kernel or you are facing any kind of issues.
INDEX
1. Kernel Features
1.1 Smartreflex (Turn ON/OFF, adjust min/max range)
1.2 Live OC (Realtime Overclocking)
1.3 Custom Voltage (EMIF)
1.4 GPU Overclock
1.5 Gamma Control
1.6 Battery Friend
1.8 IVA Overclock
1.9 DPLL Cascading (Currently not in use)
1.10 HDMI toggle
1.11 Intelli-Plug
2. Issues
1.1 How can I change the smartreflex minimum/maximum voltage
What is Smartreflex?
SR is compareable with an CPU governor but not for scaling frequencies but for voltages. That means SR has a fixed range of voltage (min/max) and calculates the optimal voltage for each CPU frequency. In example on light use of the CPU it scales down to lower voltage - on heavy use it can sclae to higher voltage. This is an efficient system to save power! Compared to EMIF which uses the hardcoded voltages it saves more power because it's variable. EMIF cannot vary between the values.
This interface has a hardcoded range of 830mV min to 1450mV max. Usually there is no need to adjust these values but irt can be usefull in example when using high overclocked frequencies above 1,5ghz! Usually SR cannot handle frequencies above 1,5ghz and I have hardcoded the maximum range of 1,45mV which should allow SR to handle it. In prior times the users had to turn off SR when OCing above 1,5ghz which causes the CPU to eat more power. But you can try around and report your results.
CAUTION: Don't raise the maximum SR voltage too high! It can burn your board = no phone anymore! I recommend to not use higher values than 1490mV! As already mentioned: THe default value should be enough!
ANd also: USUALLY THERE IS NO NEED TO CHANGE ANYTHING ON SR! IF YOU DON'T KNOW WHAT YOU'RE DOING, PLEASE LEAVE IT ALONE!
Ok, now let's see how to do this:
Turn ON/OFF SR
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. You can toggle ON/OFF SR for each component (IVA, CORE, MPU)
Usually I recommend to keep SR ON because it saves power! But in some cases when overclocking the CPU (MPU) the device could freeze - whether you OCed too much or SR couldn't handle the frequency! In this case you can try to raise the vmax value of SR a little bit (CAREFULLY!) and try again. If it sitll freezes and you're sure that you didn't OC too much, turn SR OFF at least for MPU!
Maximum Voltage
Currently there is no app which supports the feature of adjusting the SR vmax value, because I wrote this feature some days ago.
But in the next Trickster Mod version this option will be supported!
example:
# To read the current vmax value. Replace XXX with one of the following:
sc_core - for core max sr voltage
sr_iva - for iva max sr voltage
sr_mpu - for mpu max sr voltage (mpu is most related for CPU scaling)
cat /sys/kernel/debug/smartreflex/XXX/vmax
# You will get an output, e.g. for mpu = 1450000 (1450mV)
# To set a new value, do the following command (replace XXX with a value like above - BE CAREFUL! USUALLY THE DEFAULT VALUE ENOUGH AND YOU CAN LEAVE IT UNTOUCHED!)
echo XXX > /sys/kernel/debug/smartreflex/XXX/vmax
Minimum Voltage
It's easy because Trickster Mod supports it!
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. Below each SR component (IVA, CORE, MPU) there is displayed a value (usually 830 default) which means this is the lowest scalable voltage for this component. You can try to decrease this value for the case you want to UV a bit more - or raise it a bit for the case you think that the set range is too low and causes freezes on your device.
1.2 How do I use Live OC (Live OVerclock)?
This feature allows you to overclock the CPU in realtime. It works with a multiplier value set by the user. The default multplier value is "100", which means: No OC! If you want to raise the OC frerquency, just raise this value step by step.
FOr my device the maximum working OC value is "111" which means the maximum frequency is running at 1498mhz!
NOTE: Keep in mind that you tunr Smartreflex OFF for higher freqs than 1500mhz - or raise the maximum SR voltage range for "MPU" a little bit and test if it works.
Ok, how to use Live oC in action:
Open Trickster Mod App and swipe to the tab "Specific". There you will find something like this:
Code:
MPU OC [100]
DON'T TOUCH THE "CORE OC" SECTION, IT WILL CAUSE FREEZES!
Now slowly increase the value "100" to something higher, e.g. "105". Tap the hook in the right upper corner to confirm. To see your new set of frequencies you can now whether close and restart Trickster Mod or just use any monitoring app like Cool Tool which will show your frequencies in real time. That's it!
CAUTION: You can damage your phone forever!!!! This feature allows you to set very high frequencies (also up to 2,0ghz...) - That DOESN'T mean that your phone can run these frequencies!
If your phone freezes or crashes you have probably set too high OC - or your voltage is too low.
1.3 How do I use Custom Voltage (EMIF)?
NOTE: This only adjusts the fixed voltage! When you have Smartreflex ON it can still vary! You have to see the bigger picture: This voltage value sets the "middle point" for voltages. Smartreflex is still able to increase or decrease the voltage. When Smartreflex is OFF the CPU will stay on this voltage you set here and probably eats also more power.
How does EMIF works together with Smartreflex:
Code:
-------
| CPU |
-------
|
------------------ ------------------
|Voltage 1015 mV | ---->| SMARTREFLEX ON| = 1015mV +/- "vmax"/"vmin"
------------------ -------------------
|
--------------------
|SMARTREFLEX OFF| ----> 1015mV FIXED! No changes!
-------------------
Thi smeans if you change the voltage for a scaling step (OPP) while SR is ON, SR will adjust the voltage from this value, means: mV-Value +/- SR vmin/vmax. WHen SR is OFF it will stay on this mV as a fixed value.
How to adjust the voltage?
Well, this feature can be used with all generic apps which are supporting voltage settings. But we are prepared well, you can adjust voltages also with the "Trickster Mod App".
When you open the app, head to the tab "Specific" and below the "Live OC Section" you will find your voltage table, which looks like this:
Code:
<-->
1200 [1398]
1000 [1388]
900 [1371]
...
..
..
Now just tap the arrows in the right upper above the first voltage value and just type or tap (per direction) a value, e.g. "-25". To apply it, confirm by tapping the hook in the right upper corner of your screen. That's it, your new voltage values are now set and applied. And also mind here: If your phone freezes you porbably have set it too low.
CAUTION: NEVER SET HIGHER VOLTAGE THAN 1490mv here!!!!! Or you might damage your phone FOREVER!
This voltage is not the same like Smartreflex! But it's still voltage! Just be carefull!!
1.4 How can I use GPU OC and GPU Governor?
GPU Overclock doesn't work like Live OC! You cannot really set custom frequencies for the GPU, but you can select and set the maximum frequency from a hardcoded range!
For the GPU there are the following available frequencies:
154mhz (FIXED!)
307mhz
384mhz
416mhz
The minimum frequency of 154 is FIXED! This means you cannot change it because the GPU needs a minimum speed to run with. But the kernel allows you to select the maximum speed. This can be usefull for playing games and also for saving power . In example when not playing games you don't need the GPU to run at 416mhz! Set it to 307mhz in this case and save power.
When you open Trcikster Mod and head to the "specific section tab", you will find "GPU MAX FREQUENCY" and it's currently set maximum frequency. Tap on it to select your preferred one:
- 154 Mhz
- 307 MHz
- 384 MHz
That's it. The new setting will be your new maximum GPU frequency.
Below there's another option called "GPU Governor". Just tap on it and select your prefered one.
NOTE: If you want to track current GPU frequencies and watch governor's behavior, just switch to Trickster's "Informations" - Tab and watch the frequencies clock.
1.5 How can I use Gamma Control?
What is gamma? The gamma setting sets the color range for the screen. You can compare it to the contrast. We all know that the touchscreen eats most of the power compaerd to all other components in a smartphone! A lower brightness causes less power consumption and a lower gamma or contrast range alos helps a little bit to save power.
In this kernel you can choose from a range of "5 - 10" while "5" is very bright while "10" is very dark. The default setting is "5" BUT CAUTION: Trickster Mod will display a range of "0" to "10" and the default setting will be shown as "0". This is caused by the fact that this feature was ported from the Gnex device where you can choose from a higher range. The only sideeffect is that the values "0" - "5" won't show any difference.
How to set the gamma value?
Well, once again open Trickster Mod and swipe to the tab on the right end. Just select your preferred value by using the slider.
Alternately you can use sysfs by terminal or adb:
OMAP Gamma interface:
echo i > /sys/devices/platform/omapdss/manager0/gamma
Replace i with 0-10 of your choice.
1.6 What is "Battery Friend and how to use it?
Battery Friend is a simple toggle (ON/OFF) which sets your device into a battery friendly mode without the need to play with all settings in Trickster Mod /sysfs until you find a good setting. In fact it does the job for you.
What does it affect?
NOTE: Doesn't lock anyx frequencies anymore!
locks dynamic Fsync enabled
locks Fsync disabled
Doesn't allow any OC (Live OC will not have any effect, Core OC is not allowed in this kernel)
Increases the dirty ratio interval to 90% (starts working at this value)
Enables Dynamic Hotplug: This doesn't allow hotplugging during device is active - and it will always turn CPU1 OFF during suspend! It also prevents from conflicts when user uses a hotplug governor (which isn't a good idea though) - but hotplug governors are causing higher battery drain!
Dynamic Page-writeback always enabled
How to toggle Battery Friend:
For now the only way is via terminal, adb shell or root explorer (text editor)
For terminal and adb:
Code:
echo 1 > sys/kernel/battery_friend/battery_friend_active /* Enable */
echo 0 > sys/kernel/battery_friend/battery_friend_active /* Disable */
For Root Explorer
Open Root Explorer
Navigate to sys/kernel/battery_friend/
Open "battery_friend_active" with Text Editor
Change "0" to "1" and safe the file to enable
Change "1" to "0" and safe the file to disable
1.7 Suspend Governor Control (CURRENTLY DISABLED)
Suspend Governor Control is a kernel module written by me. You can use it to set your preferred Screen-Off-governor.
For now it's only supported by sysfs (Trickster Mod will support all my current and upcoming features as soon as it gets updated with its new UI mode!
How to set suspend governor
Open a terminal or use adb shell
Code:
su
echo "x" > /sys/kernel/suspend_gov/suspend_gov
Replace x with one of these values:
0 = Ondemand
1 = Ktoonservative
2 = Conservative
3 = OndemandX
NOTE: No matter what governor you use for suspend mode, if Battery Friend is enabled the second core will be turned off during suspend!
1.8 IVA Overclock
What is IVA OC?
IVA OPPs are controlling the CPU load for sound events. It could be useful (in some cases) when you get sound related laggs. Just set the maximum frequency to highspeed. This will allow more CPU power for sound events but also will cause higher battery consumption.
How to use IVA OC?
If you want to check the current IVA frequency. Just type in Terminal or ADB:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/iva_clock
You will get an output like this:
Code:
132 Mhz
2. You can whether enable IVA highspeed: 130 - 430 Mhz ["1"] or enable IVA normal speed: 130 - 332 Mhz ["0"]
320 Mhz max: echo "0" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
430 Mhz max: echo "1" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
1.9 DPLL Cascading
DPLL: Davis–Putnam–Logemann–Loveland (DPLL) algorithm
To get more info about this please see wiki
But to sum it up shortly: It helps to use/stream media (music) in a low power mode.
NOTE: DPLL Cascading will be available to be switched easily via Trickster Mod App soon!
How to switch DPLL?
DPLL is ENABLED by default!
Open Trickster Mod -> Speicific Tab --> DPLL (soon)
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/dpll/dpll_active
Turn on:
Code:
echo 1 > /sys/kernel/dpll/dpll_active
1.10 HDMI toggle
Some users are facing a RAZR-sepcific problem: HDMI cable is detected, even though there is no cable plugged!
Therefor I included a toggle to switch HDMI wether ON or OFF. Additinally there's an init.d script included within the AROMA Installer you can select during the installation of JBX-Kernel.
To enable/disable HDMI on-the-fy:
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/hdmi/hdmi_active
Turn on:
Code:
echo 1 > /sys/kernel/hdmi/hdmi_active
1.11 Intelli-Plug
For intelli-plug hotplugging is now only allowed when the device enters sleep.
To enable hotplugging universally just change the value of the following entry whether to 1 (on) or 0 (off):
Code:
sys/module/intelli-plug/parameters/int_hotplug
*Unfortunately I don't have enough space in the OP to write all this into the FAQ, that's why the I only added the sysfs path, but the description is simply here
2. If anyone has the following issues:
Issue
Media Process FC
No SD-Card in File Explorer
My CPU Settings (frequencies, etc) won't be saved (it sets itself back to Kernel default after screen off)
My phone freezes/reboots always when I try to set options in Trickster Mod
The device is lagging very hard
Solution
Media FC: Open App settings, head to "Download Manager" and "Media Storage" and hit the "delete data" button. Reboot. Now it shouldn't give any FCs anymore and after a little bit of waiting it will find all Media (Pictures, Videos, etc..)
No SD-Card: Reboot into recovery, go to "Mounts & Storage", tick "mount int" or "mount ext".
USB: Make sure the screen is ON while plugging the cable in.
CPU Settings: This is a bug which cannot be solved at the moment. Temporary solution: In Trickster Mod just activate the "Frequency Lock" and your settings will persist.
Trickster Mod:: Open App settings, Trickster Mod and select "uninstal updates". Now it should work.
Crashes, Freezes, lagging, something doesn't work, etc
There are too many reasons which could cause crashes! So here is a checklist for you to look for. Check each point and try the following workaround:
- Your rom has CPU tweaks (e.g. Kernel modules, init.d folder, etc)
- You have set custom CPU settings (e.g. custom frequencies with apps like No-Frills CPU Control, Set-CPU, Antutu, etc...)
- You have undervolted too low
- You have overclocked too high
- You have applied higher "Core OC" value in Trickster Mod App
- You are running any other kernel tweaks which are regarding to the CPU and/or performance (e.g. Kernel modules by Whirleyes eventually set by init.d, etc..)
- After setting some settings (e.g. in Trickster Mod) your device doesn't boot anymore
- adb doesn't work / shows only "device offline"
- You are facing hard lagging
If any point here matches your setting, please revert from it:
- Remove any CPU init.d script from /System/etc/init.d
- Uninstall any CPU controling app (e.g. Set-CPU, No-Frills, etc..)
- Remove all extra kernel modules from system/lib/modules (e.g. cpu_control.ko, cpufreq_smartass2.ko, etc..)
- Unset any custom settings from any other kernel / CPU - tweaking app which is NOT Trickster Mod
- Maybe your governor causes issues. Hotplug is know for bugs at the moment...I'm going to fix it..
- NEVER set your CPU Settings (e.g. in Trickster Mod App) on boot!!!! - before you aren't sure that your settings are safe!!!
- You may flash the kernel again after reverting related settings
- to make adb work / show device online, download latest SDK platform-tools and confirm access on device (4.2 security feature of Android)
- Don't use any task killers, memory killers, seeder apps! They may conflict with the kernel/Rom settings.
If none of these suggestions work for you your rom may be incompatible. Please report it here that I can add the rom to the list of imcompatible roms
If you have any issue, please read this:
First check:
- is it really a kernel issue?
- did I see this bug with the roms original kernel?
- what are the people in the rom thread saying?
- what are the people in the kernel thread saying?
- can I find this issue on a bug list?
- how about my settings? Is it my fault it crashed?
- can I find something useful in the kernel FAQ?
- Is it maybe a well known issue and can be solved
withing seconds? Just like wifical.sh?
- Where to repeat that issue? Rom or kernel?
I know it's sometimes difficult to track the issues, and we can't know for sure if it's caused by the rom or by the kernel, but if you try at least to get some information you might find an answer sometimes. If you are able to understand logs, you may report whatever you find.
All this helps to keep the threads more clear. Thank you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DONATE
If you like my work and want to support me, I'd enjoy a little beer or coffee. You can find my beer mug below my username
SOURCE
3.0.8 Base:
JBX-Kernel 4.2.2
JBX-Kernel 4.3
CREDITS
Kholk & [mbm] - Kexec inital Release
Hashcode & Dhacker - Making Kexec stable and initiating compatible kernels
Motorola - 3.0.8 Kernel Source
Surdu_Petru - Sharing Knowledge and helping with problems
nithubhaskar - Hints and answering my questions
Ezekeel, Imoseyon - Custom Voltage, Live OC, Temp Control, Gamma Control Source Code
faux123 - Some features, like Intelli-Plug, Intellidemand, Intelliactive
bigeyes0x0 - Trickster Mod App
Team Trickster - Great support and adding new features from my suggestions
Placca - Awesome kernel guide
Click to expand...
Click to collapse
3.0.8 / 3.0.31
There is the classic JBX 3.0.8 Kernel (a hybrid of 3.0.8, 3.0.21, 3.4, 3.7, 3.8, 3.10, 3.11, mostly backports from these versions)
And now there is also JBX 3.0.31 (also a hybrdig including the above backports, but also from 3.0.101)
I won't list the whole version history, too long
3.0.31 first TEST-BUILD now coming!
- also reserved -
And it arrives...
Many thanks man...
Really appreciate you doing this...
---------------------------------------------------
May the -Mass times Acceleration-be with You...
I need the internal storage mount points from someone with stock kernel, please. I saw something about mmcblk0 - int ? Please anyone check the /mnt partitions and tell where the internal and external sdcards are mounted. thx
Edit: nevermind, I didn't know this device doesn't include an internal storage. Now I need to know if USB mount works on Devesh's Rom ports.
Used Stock ICS Based ROM on System 1 with BMM , and Mobile Terminal .
hope its ok .
Wow !
I see some awesomeness coming to our A2s *Respect*
All is set up. Everything works, so I will now build the first test kernel for you guys.
First test kernel in NIGHTLIES folder. Please test and report. Keep in mind that you have to be on one of Devesh's Rom Ports!
Edit: Sorry, forgot something! Please wait 5 mins...
Edit: Done!
Dirty flashed, liquid smooth slot 6 oc1350 running good.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
JB leak?
Sorry for asking dummy question. Can i flash it on the JB leak because we still need JB leak for installing kexec room right? So if I want to try what possibly would happen?
dtrail1 said:
First test kernel in NIGHTLIES folder. Please test and report. Keep in mind that you have to be on one of Devesh's Rom Ports!
Edit: Sorry, forgot something! Please wait 5 mins...
Edit: Done!
Click to expand...
Click to collapse
Man! You really are damn energetic and enthusiastic, aren't you? Really glad to have you around.. Thanks again.. :thumbup:
Sent from my MB865 using Tapatalk 2
amynjimmy said:
Dirty flashed, liquid smooth slot 6 oc1350 running good.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
Click to expand...
Click to collapse
How did you OC ? i just can't get the phone to Overclock properly with this trickster app ..
afeeq said:
Sorry for asking dummy question. Can i flash it on the JB leak because we still need JB leak for installing kexec room right? So if I want to try what possibly would happen?
Click to expand...
Click to collapse
You cannot. It needs a kexec Rom. So flash it first
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.6 - Tapatalk4
New nightly online with fixed CPU and live oc! @Brantuck84
Edit: sorry, wrong thread!
But ne nighty comes here too in 5 mins
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.6 - Tapatalk4
So with the current version there is a bug with OC ? ( i don't see TEST2 for Atrix like with the Razr version).
Yes, device starts lagging when OC too high (over oc value of ~107). But new release comes with fixes - OC up to 1,5ghz possible without any problems (Mine crashes when OC higher than 1,498mhz, each silicon is different).
I think I will push it as a release (not NIGHLTY) - only thing left to be fixed is the random black screen while booting. But that's not that important as long as the kernel works well when booted successful.
Edit. done!
Great can't wait to boot 1498mz!
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
Not boot, just set it after boot - and if you're sure you have it running stable, set the "Apply on boot" function in Trickster Mod with a delay of ~90 sec - just to be safe!
RELEASE for Atrix 2
CHANGELOG JBX-kernel 0.6 Hybrid
This version includes fixes for performance and stability
CPU: Set bootup policy to static frequency
CPU: Revert some accidently failed cleanups
CPU: Reset CPU delay on tickless
CPU: Changed margins and sr settings for some OPPs
CPU: Default trimmed dpll mpu
CPU: Added Uilization
SR: Fixed SR return value check
Decreased RCZ_CPU_STALL_TIMEOUT to 60
emif, lpddr: Re-added 466mhz timings
USB: Change ehci performance mode to static scaling freq
Disabled PM_DEBUG for performance
Reduced RW READAHEAD Buffer to 1024
OMAP, CPU, RCU: Re-enabled watchdog
Universal performance invreased
dtrail1 said:
Not boot, just set it after boot - and if you're sure you have it running stable, set the "Apply on boot" function in Trickster Mod with a delay of ~90 sec - just to be safe!
RELEASE for Atrix 2
CHANGELOG JBX-kernel 0.6 Hybrid
This version includes fixes for performance and stability
CPU: Set bootup policy to static frequency
CPU: Revert some accidently failed cleanups
CPU: Reset CPU delay on tickless
CPU: Changed margins and sr settings for some OPPs
CPU: Default trimmed dpll mpu
CPU: Added Uilization
SR: Fixed SR return value check
Decreased RCZ_CPU_STALL_TIMEOUT to 60
emif, lpddr: Re-added 466mhz timings
USB: Change ehci performance mode to static scaling freq
Disabled PM_DEBUG for performance
Reduced RW READAHEAD Buffer to 1024
OMAP, CPU, RCU: Re-enabled watchdog
Universal performance invreased
Click to expand...
Click to collapse
Is his gonna allow then use of 1498 then.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2

[Kernel]GalaTab3 KitKat & JellyBean Kernels for SM-T310 8.0 ONLY

GalaTab3 Kernels for either JellyBean or KitKat ROMS - SM-T310 8.0 - TouchWiz
Warning:
As always, flash at your own risk. I'm not responsible, in any way, for what you flash, copy, fiddle with, poke, molest or otherwise screw with on your phone or tablet....
*** Important ***
- I recommend using TricksterMod or a similar CPU/Kernel modification app to adjust the settings/configurations. Although I am a huge fan of Faux123 and his Kernel app, it does not play nice with Exynos CPU's or Mali GPU's (especially the two together). Maybe it will in time, but only someone of his genius can figure it out. But, I have implemented the features specifically to allow TricksterMod to have full access to the controls. You can get the app HERE
USB Audio Mod for JellyBean ROM's ONLY
Flash this file to allow USB Audio functionality to work 100%. This will work in conjunction with my kernel and allow you to use external DAC's and bypass the internal audio hardware/software completely. This provides MUCH better sound quality and higher bitrates (depending on the DAC you choose to use).
USB Audio Mod
_______________________________________________________________________________________________________
_______________________________________________________________________________________________________
Releases & Downloads
Version 14.7.16 (KitKat) - Download - KitKat ROM's ONLY
- STOCK KitKat NF4 4.4.2 Kernel
- Built from newly released source code by Samsung
- Added Root/SuperSU binaries
- Added Init'd Functionality
- Added mock location functionality in default prop
This is the base in which I will be building the new KitKat custom kernels from. Obviously, I wanted to add some of the basic functions, like Root and Init'd so nothing is reverted from any custom ROM's you may have flashed. This is not a copy of the kernel from the stock ROM.... This is built against the source code. I will be adding features and customizing this kernel shortly and will begin uploading the new versions ASAP. My main focus is to get it overclocked first and then I will fine tune some of the stock features and add new stuff along the way.
Version 14.5.27 (JellyBean) https://www.mediafire.com/?b0h9ii661x113d9
- Last JellyBean Kernel Release
- Same features as Version 14.4.8r2
- Camera now working. Fixed driver loading error.
- Refreshed source code and toolchain
- Adjusted charging current for USB, Dock and Misc charging modes. Now all register as "A/C" current.
- Misc code updates and fine tuning.
Version 14.4.8r2 (JellyBean)https://www.mediafire.com/?m29aztntz2jx613
- Cleaned up some code
- Speed modifications to allow for smoother daily use
- Transitioned some kernel modules to be built in primary image for faster load times
- Finished adding Sweep2Wake code - still needing to finalize trigger processes (so feature is not active yet)
- Adjusted USB Audio function at Kernel level. Will provide an updated framework file to implement this fully and allow for 100% native function. Allows total compatibility with external DAC's and complete bypass of internal audio hardware/software.
Version 14.4.3 (JellyBean)https://www.mediafire.com/?kv44k85q41878y9
- Reverted some edits to allow previous steady kernel workflow
- Added additional USB Audio/Video Kernel functions based on user requests
(You now do not need proprietary apps to play to external dacs or video decoders)
- Additional dock features added for broader compatibility
- Reverted Init'd files to previous versions
Version 14.3.25 r2 (JellyBean) http://www.mediafire.com/download/t60k13chcat5b3f/GalaTab3_Kernel_v14.3.25_r2.zip
- Fixed Init.d Functionality Problems. Now runs on boot as it is supposed to
- Revised several of the init.d scripts from past releases and added several new ones.
- Enabled Debugging & Mock Locations by default.
- Added several Audio Interface and DAC drivers (some as modules, some built in). This will allow for a much broader driver base for external DAC's connected via USB.
After flashing and booting, I highly recommend you set your Trickster settings again (and remember to set to boot). The new tweaks adjust some of the kernel performance values and if you use your old Trickster profile, it will reset these new values to those of previous releases. I will be evaluating and adjusting these new values in future releases to determine which have the best results on our devices.
"Stock" GalaTab3 Init.d Files (Flashable) - http://www.mediafire.com/download/u2slgste63dpx1l/GalaTab3_Original_Init.d_Files_Flashable.zip
Flash this if you want to use the normal Init.d Files with the new kernel.
Version 14.3.18 (JellyBean) http://www.mediafire.com/download/xbx12xq493n68e8/GalaTab3_Kernel_v14.3.18.zip
- Updated/Enhanced SLUB performance features. Allows for much faster ROM and file systems
- Adjusted ExFat file system calls within kernel. Now loads ExFat file systems twice as fast.
- Added initial code for Sweep2Wake and DoubleTap2Wake features. NOT FULLY IMPLEMENTED YET - need to fine tune some parameters to make these features compatible on our devices.
Version 14.1.6 (JellyBean) http://www.mediafire.com/download/8ycwqq7wt4kaqi5/GalaTab3_Kernel_v14.1.6.zip
- Added 3 CPU Governors for extra versatility - SmartAss3, Lulzactiveq & zzmoove (Thanks Civato!!!!)
- Updated LZO Compression code to allow for vastly improved performance and compression speed (helps with many aspects of I/O speeds and boot times)
OLDER RELEASES/INFORMATION
Since it's the holidays - I thought I would give you all your first gift...... in the form of a newly updated Kernel release! I know.... this was on the top of your list of crap needed......
Basically, I completely started again from scratch and an re-implemented past features and some new ones. I wanted to make sure that the features were 100% compatible and efficient for the Tab 3 and that additional features were not stacked on top of broken code. In short..... this has been a huge pain in the a*# and I can't believe how hard it has been to implement features that are so widely available on other architectures. Mainly, the Mali GPU has been the biggest pain - that and all of the errors and bugs in the stock firmware.
After speaking with MANY developers and observing other device forums, I'm happy to know that I'm not the only one. The new releases of 4.2.2, 4.3 and 4.4 ROM/Kernels have caused a lot of problems with both the poor code and dramatic architecture changes from Google and Samsung. But.... here you are..... a fresh new release that is running well.
Version 13.12.21r5 (JellyBean) https://www.mediafire.com/?ggruj3gqj3gywx7
- Completely Re-wrote Kernel Mod's and/or re-implemented functional features (that are known to be stable)
- Built against an updated & modified 4.7.3 Android Toolchain (up from 4.4.3)
- Added and Implemented Boeffla Sound Engine (You can use a few apps to control the engine)
- Fully implemented GPU Controls!!! Overclocked to 700mhz but works very well at 533mhz (without having to burn through your battery)
- Independent CPU and GPU throttling based on your use. (i.e. - GPU does not ramp up if you are processing heavy data)
*** Again, use TricksterMod to adjust GPU frequencies to your liking)
- Re-Implemented CPU Overclock from 50mhz - 1900mhz
- Rewrote and modified Hotplug for better performance and ramp up's
- Cleaned up several algorithms and eliminated code that is not used on our device
- Eliminated several debugging functions (thanks to ketut.kumajaya for his previous work)
- Added back several additional drivers for BT and USB connections
- Full OTG and Dock features - including charging while using OTG and MHL/HDMI
On a quick test before uploading - this new revision scored over 18000 on the benchmark without implementing "Performance" CPU or overclocking the GPU beyond 533mhz. I'm not a "gamer", so I'm sure some of you will put this to the test, but the core function of this kernel has surpassed the Galaxy III (which I also own). The GPU function and frame rates tripled compared to the last update a month ago!
ENJOY and HAPPY HOLIDAYS TO EVERYONE!!!!!
Version 13.11.08r2 (JellyBean) http://www.mediafire.com/?7cdajhmh5080075
- Modified CPU code and how algorithms function at idile and demand situations
- Updated OnDemand governor and ROW I/O scheduler to maximize performance
- Fixed black screen on device wake
- Adjusted idle frequency so both cores are utilized for better responsiveness
- Rewrote/Updated Hotplug code to be more efficient for the Tab3
- ***FINALLY BROKE 17000 ON BENCHMARK RESULTS!!!****** (Very close to the S3 now)
- Fixed updater script......again......
Version: 13.10.28r4 (JellyBean) http://www.mediafire.com/download/w...rnel_SM-T310_Tab3-13.10.28v4_w.Initd.cron.zip
Int'd Scripts Added:
- Swap/zRam Implementation (Run script in terminal emulator once and it will be on until turned off - thanks definitive!!!!)
- Performace & Battery tweaks
- ZipAlign Apps at boot
- Cron memory cleanup scheduling (hourly, daily & weekly)
- SQLite tweak upon boot
- Permissions set at every boot
- GalaTab3 Logging enabled
- Other various tweaks to maximize performance​
- Fixed Permissions on Installer Script (11/1/13)
- Increased eMMC SdCard Readahead speeds to 3072
- Several tweaks, adjustments and updates to existing code. Some items updated to Samsung's new i9500 versions/revisions
- Fixed the CPU Frequency limit when booting. Will now boot at max CPU limit rather than a flat 1600mhz
- Modified CPU logic function so the processor is more adaptive to actual processing needs
- Improved and Modified PM/Sleep registers and functions. Should not have problems waking device to a black screen anymore
- Added additional support for wireless modem features - Allows external modems and bluetooth dongles to be connected via USB
- Added Android Graphic Fence feature/function from AOSP - allows graphics and the media logic to run smoother
- Added Root FS Slave restrictions so the Davik Cache can mount system wide storage and utilize the memory more efficiently
- Adjusted signal reporting so that it show more accurately
- Modified writeback protocol so the memory is freed correctly an is not held for an indefinite time until user operations are suspended
- Transitioned to ASM Atomic memory allocations from the standard Linux version. Much more efficient....
- Disabled several debugging functions that were useless and took up CPU and Memory resources
- Several other tweaks, but I'm way too tired to remember them.....
To Enable/Disable Swap:
1) install a terminal emulator for Play Store
2) Open terminal
3) Type "su", then hit enter
4) Type "swapit", then hit enter
5) follow onscreen instructions
Download v13.10.14:
Version: 13.10.14r7 (JellyBean)
- Increased Overclock to 1900mhz (blazing fast now!)
- Reduced Underclocking to 50mhz (yep, that's right) (Thanks Civato)
- Re-implemented zRam and it's running smoothly (make sure to use a quality CPU app, like FauxClock, to turn on and adjust zRam function)
- Finalized HotPlugging feature and fully implemented
- Enabled/Added SVGA adapter support (a few users had requested)
- Stripped Debugging on a few features to shrink the size of the Kernel and burden
- Added and Optimized ARM R/W functions
- Modified OnDemand Governor for increased performance
- Increased Read-Ahead Values for Memory (2048)
- Added a LOT of PPP, networking & connectivity drivers - especially for Bluetooth and Network controllers via USB (This will allow you to connect Tab to external modems and several BT interfaces, including Serial)
- Added some additional OTG/Host controller features - allows broader compatibility based on User setup
- Added additional support for generic chargers
- Additional EXT4 File System support features
- Converted several features to Modules to allow Kernel to be less bulky (should increase some performance)
- Various Bug Fixes
Download v13.10.14: http://www.mediafire.com/download/dd3uc1i1nbabdfc/GalaTab3_Kernel_SM-T310_Tab3-13.10.14r7.zip
Version: 13.10.11 (JellyBean)
- Increased Overclock to 1800mhz
- Fully implemented SIO scheduler
Disabled zram (temporarily) while I modify how the kernel handles this feature.
Download v13.10.11 - http://www.mediafire.com/?ahqh6ukabsajtq2
Version: 13.10.7 (JellyBean)
Features:
- Based on MH2 4.2.2 Samsung Kernel
- Linux ver 3.0.31
- Overclocked to 1.6mhz (stepping this up slowly so we don't have any problems)
- Underclocked to 100mhz (Amazing battery savings)
- Fine tuned voltage controls
- Added ROW IO Scheduler (Foundation for SIO is implemented too, just need to finalize one thing and it will be active in the next release)
- Adjusted USB and Dock charging voltages to allow for MUCH faster charging on "USB" currents (basically, will charge twice as fast as before)
- Implemented and Enabled zRam. Now you can turn on/off zRam to allow for additional RAM/Swap
- Enabled ARCH power (allows for CPU to run much more efficiently and based on the need)
- Enabled Dynamic FSync (Thanks Faux123!!!)
- Added and Enabled ExFat support
- Several performance mods and fixed a lot of memory leaks...... This thing is running nicely now......
- Enabled Linux Atomic resources
- Several other tweaks, but I'm way too tired too remember.
Basically, this is a major improvement to our Kernel for the T310 and you will instantly see the performance gains.....Enjoy!
Download v13.10.7 - http://www.mediafire.com/download/iknplvhjvraud3p/GalaTab3_Kernel_SM-T310_Tab3-13.10.7.zip
I figured I would kick off some of the development for the 8.0 version of the Galaxy Tab 8. I've included the kernel I created recently which has helped with several performance issues and allows for OTG with Charging on our Tab 3 8.0.
Version: 13.9.20 (JellyBean)
Features:
- Based on MH1 4.2.2 Source from Samsung
- Compiled from ARM-EABI 4.4.3 ToolChain
- Added "OnDemand" CPU Governor support (Full)
- Added Support for Samsung's SmartDock, AudioDock, OTG and MHL Cable functions (added features/detection roles)
- Added full OTG support and function. This allows for various OTG compatibility and OTG Charging.
- Added MHL Chip Driver, 11 Pin Micro USB Connector Support and fix for MHL HPD Glitch
- Added additional USB Gadget support for devices (Including the Native Android USB Gadget Functions)
- Additional support for FUSE Filesystems - added functionality
- Several bug fixes
**** To enable OTG plus Charging, your OTG cable must have a 64.9k Ohm resistor between the ground and sense ID pins. This will engage the SmartDock function on the tablet, allowing for OTG/USB Hub, MHL, USB Audio and Device Charging simultaneously.
- Please search Google and XDA for making your own OTG cable. This thread is NOT for asking questions about building cables, problems with OTG function, etc..... I have enabled full function in this kernel and this has been extensively tested by several users - IT WORKS!!!!.****
- In order to utilize the OTG and MHL functions, you will need to add an additional hub or MHL port to your OTG cable. Again, this is not the forum for asking how to do this - use Google and XDA as resources on how to build. Chances are, if you don't know how to do this, then you should not be using this function anyway.....
- OTG Charging requires you connect the device to an AC Samsung Charger (OEM, the one that came with device) or a DC Charger that provides 5V, 2+ amp output. Connecting to another charger without this output will limit the functionality of the charging feature.
- I HIGHLY Suggest using an external powered hub to connect additional USB devices (Memory Sticks, Keyboards, Mouse, Bluetooth, Modem, Etc...).
This is just the beginning and the first release of this kernel. There will still be bugs and quirks that will need to be ironed out. I'm actively working on several features for our SM-T310 devices and future releases will contain major feature upgrades and bug fixes (that are native in Samsung's Source Code).
Enjoy and I will update the OP with add'l information on releases as I have them complete. Do not ask for ETA's!!!!! I will not release until I feel comfortable with the stability and functions. I'm almost finished with my ROM as well, which will contain this kernel. Just need to finalize some theming. I'll release that this week.
Stock Kernel Downloads
Original Stock JellyBean Kernel: Download - JELLYBEAN
Original Stock KitKat Kernel: Download - KITKAT
Install Instructions:
1) Reboot Into Recovery (TWRP Recommended)
2) Create Nandroid/Backup
3) Wipe Cache/Davik
4) Install Kernel
5) Reboot (First boot after flash may take a little longer - Kernel is building additional file structure and adding features)
6) Enjoy!!!!!
GitHub Source Code & Revisions
JellyBean Kernel Versions
KitKat Kernel Versions
Flashed the kernel and reboot. Will make some tests today!
Sent from my SM-T310 using Tapatalk 4
Finally a kernel for the tab 3 8.0. Will try to flash once I getmy tab 3 rooted. Congrats and good luck
Thanks arshull for your work, i will try as soon as i get home.:good:
Thanks.... can u make a T311 version.. please: D
Sent from my SM-T311 using Tapatalk 4
And for LTE variants too
Sent from xda app-developers app
This kernel works as a rocket. No issue found
Verstuurd vanaf mijn GT-I9300 met Tapatalk 4
Awesome
This kernel is like a bause!!!! Highly recommend this kernel. Did some benchmark and it perform better than on stock kernel..... Used nenamark 2 and scorked about 58.5 fps and quadrant it scored higher than the HTC one x. Kudos to the developer of this kernel
Glad everyone is liking it. As an update, I'm finalizing the tweaks on a few new features and should have an updated version posted in the next couple days. Trying to implement OC and some add'l Govs plus some tweaks for faster otg charging.
Are there any specific drivers that you are needing within the kernel? If so, let me know and if enough users need a specific driver for an accessory/gadget then I'll add it in.
Sent from my SGH-I747 using xda app-developers app
arshull said:
Glad everyone is liking it. As an update, I'm finalizing the tweaks on a few new features and should have an updated version posted in the next couple days. Trying to implement OC and some add'l Govs plus some tweaks for faster otg charging.
Are there any specific drivers that you are needing within the kernel? If so, let me know and if enough users need a specific driver for an accessory/gadget then I'll add it in.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
arshull thanks again for you exellent work,I have one question, i got a original Samsung MHL HDMI adapter that work great on my S4 but with theT310 only video works,but no the audio, is this because of a missing driver?, and if so can you add it in the new update.
Thank you in advance for your help.
arshull said:
Glad everyone is liking it. As an update, I'm finalizing the tweaks on a few new features and should have an updated version posted in the next couple days. Trying to implement OC and some add'l Govs plus some tweaks for faster otg charging.
Are there any specific drivers that you are needing within the kernel? If so, let me know and if enough users need a specific driver for an accessory/gadget then I'll add it in.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
maybe you can do something about the red cros sign in the battery during pc-charge? it has to do with volts....?
Thanks again for the excelent kernel!!
parabels said:
maybe you can do something about the red cros sign in the battery during pc-charge? it has to do with volts....?
Thanks again for the excelent kernel!!
Click to expand...
Click to collapse
I'm still trying to narrow.that down. That's an issue with the Sammy source and the multiple mA options available for allowed power sources. I'm hoping my revision to the.otg charging will eliminate the internal kernel glitch.
Sent from my SGH-I747 using xda app-developers app
Hi there bro,
Can this kernel be flashed on SM-T315? Its the LTE version of our tab3 8.0. Thanks for helping...
Sent from my SM-T315 using xda app-developers app
MAXPHREAK said:
Hi there bro,
Can this kernel be flashed on SM-T315? Its the LTE version of our tab3 8.0. Thanks for helping...
Sent from my SM-T315 using xda app-developers app
Click to expand...
Click to collapse
Sorry, no. That requires a separate source and config. Basically like a completely different device.
Sent from my SGH-I747 using xda app-developers app
Sorry for disturbing but will there be OC for the gpu and cpu for the next kernel or performance increase? Because i am sure the tab 3 8.0 has more power than it has right now. Thanks in advance
shahtheass said:
Sorry for disturbing but will there be OC for the gpu and cpu for the next kernel or performance increase? Because i am sure the tab 3 8.0 has more power than it has right now. Thanks in advance
Click to expand...
Click to collapse
Page 1 op says he's working on OC!
djjozo said:
Page 1 op says he's working on OC!
Click to expand...
Click to collapse
Oh ya...... Did not see that :fingers-crossed:
Hi,
i tried to connect a mhl vga adapter to the t310 after flashing your kernel but i have no image on the vga output.
is there something to do to make it work ?
Regards
acca said:
Hi,
i tried to connect a mhl vga adapter to the t310 after flashing your kernel but i have no image on the vga output.
is there something to do to make it work ?
Regards
Click to expand...
Click to collapse
It may be a specific driver for the chip set on the vga converter you're using. I'll look to see if there are any vga options in the source.
Sent from my SGH-I747 using xda app-developers app
Ok, thank you very much !

[Kernel][5.1][-O3][-graphite][FINAL] HurtSky Stable 13 [dt2w/s2w/s2s] 30/11/2015

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.

Categories

Resources