Database Info

[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 !!!!

[JFLTEXX] Need help in choosing rom

Hello guys!
I would like to ask you for opinion what is best ROM for you. I recently rooted my I9505 and installed CM 12.1 but I want to check another viable ROMs, but there are SO many ones in android development section
Since I love to play many games on my phone, Im looking for a rom that is categorized in order by:
- Maximum performance and fps stability
- System stability (yes it is at second place )
- Battery usage (Im using greenify)
- Features
Im open to any suggestions. In few days these is some free time for testing ROMs

Optimized CM13 or AOSP 6 by JDC Team. In Stweaks app, select the extreme performance profile. Antutu scores over 35000 while other roms score around 32000.
Yet for gaming, I believe 5.1.1 is better, JDC Team made those as well.

^ what he/she said.
When it comes to performance, JDCTeam roms are best, due to the included alucard kernel.
Switch to the extreme performance profile and you're good to go. Note that not all settings take effect after applying the profile, so you may need to reboot.
You will also get good up time, because the kernel automaitically switches to a low power mode when the screen is off.
But when it is in use you will get about 2 hours SOT.
With extreme battery you may get around 4-5 hours SOT.
The stock cm kernel, that comes with pretty much every rom, is ok and all for everyday usage, but when it comes to performance it kinda sucks compared to custom kernels.

@GDReaper Paradoxically, on CM 12.1 with performance battery profile (in notifcation bar) I get AnTuTu score near 38k. However, when I tested JDCTeam optimized CM 12.1 and changed to performance battery mode in notification bar, I got at least 30k score (however I haven't modified kernel via STweaks yet). Maybe I should give it a try .
By the way, is Alucard custom kernel contains fast charging feature? I wanted to test it as well

That battery mode from CM only changes the CPU governor to Performance.
Alucard kernel changes many different settings depending on the kernel profile.
Also, the S4 does not have fast-charge built-in. Only the newer phones have that feature.

Then I don't know why standard CM rom gave me so high score.
However I will test again Optimized CM 12.1 and reply back tomorrow (making backup and so on)

Optimized CM13 by JDC Team is the best in my opinion.

I would go for stock based one like lollirom v8
best stability, no lag over time...

Thank you all for answers
Checked Optimized CM 12.1 and changing profile in STweaks to extreme performance really gives huge boost (over 38k score) as well as extreme battery cuts its performance when battery is more important (under 30k score).
The only cons is that changing between profiles takes about 20-30 seconds but it doesn't bother me so much
EDIT: I read that when you install Lollirom v8 you have to change modem to HPA1 to make WiFi work properly. Is that really needed?
Im not convinced to modify anything other than system. Is it possible to backup my modem easily so I can restore it if something goes wrong?

I will be doing the same as you!! Ive been using Golden Eye for quite some time now, but am ready for something new

KonowaL said:
Thank you all for answers
Checked Optimized CM 12.1 and changing profile in STweaks to extreme performance really gives huge boost (over 38k score) as well as extreme battery cuts its performance when battery is more important (under 30k score).
The only cons is that changing between profiles takes about 20-30 seconds but it doesn't bother me so much
EDIT: I read that when you install Lollirom v8 you have to change modem to HPA1 to make WiFi work properly. Is that really needed?
Im not convinced to modify anything other than system. Is it possible to backup my modem easily so I can restore it if something goes wrong?
Click to expand...
Click to collapse
You can use a custom kernel to avoid the WiFi issue.
I don't know if there is any way to backup the modem, but changing the modem isn't hard either.
Lollirom will not change your modem, only official stock roms can change your modem.

[APP][ROOT][Yureka Thermal Control][Gaming][Balanced][Conservative]

The Yureka Thermal Control is an android application written by me for rooted users of YU Yureka+/Yureka, this app gives you the ability to change the thermal configuration of your device. This will help the users to switch according to their requirements, I consider this a very useful application for all Yureka users since no one is satisfied with the performance to heat ratio.
The Yureka Thermal Control has four different settings explained below, if you use this app, make sure to test for minimum 12 hours before saying anything, you cannot judge anything just by 1 hour of usage. Below is the explanation of the available settings -
1. Gaming -
Using the gaming thermal config will help gamers and heavy users, this option is meant for those who don't like cores turning off quickly even with mild heat. With this config, cores will not be hotplugged easily, cores will start hotplugging only when cpu temperatures are above 56-58 range, hence gamers and heavy users won't face any lags with extended usage.
2. Balanced -
This is the thermal config which comes inbuilt with my builds of RR Rom, this is a precisely tweaked version of the stock Yureka thermal config. The stock config only turns off cores when device heats, in addition to that this config will also ramp down cpu and gpu frequency by one step. This helps in further reduction of heat with mild battery backup improvement.
3. Conservative -
The conservative thermal config is meant for those users who don't use many heavy applications on their device, this config is slightly more aggressive in terms of throttling and hotplugging compared to the balanced config. This config controls heating to a great extent at the cost of mild performance drop which is only noticeable in heavy games.
4. Ultimate -
The ultimate thermal config is meant for those who have light usage like internet messaging or browsing the web and basic phone operations. This config will control heat generation most aggressively at the cost of performance drop. Since throttling and hotplugging is fastest with this config, battery backup will also be increased with this config.
Compatibility -
Yureka thermal control is only for rooted users.
Tested on lollipop and marshmallow roms.
Don't try this on other devices.
Instructions -
Install the yureka thermal control application
Select the desired configuration
Press apply button
Reboot device
Important -
This app requires root permissions and will replace your /system/etc/thermal-engine.conf, If you want to verify which thermal config you are using, find a file named thermal in your internal sdcard and open it as text, your current thermal config status will be written there.
Download Yureka Thermal Control
Thank you for reading :fingers-crossed:
XDA:DevDB Information
Yureka Thermal Control, App for all devices (see above for details)
Contributors
Umang96
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2016-07-02
Created 2016-07-02
Last Updated 2016-07-01

Reserved

Working On MM?

Hell7 said:
Working On MM?
Click to expand...
Click to collapse
Yes

Is this works on cm13 ?

is it okay if you just uninstall the app any time? because there is no revert to default option in the app

Pixel experience vs miui 10.2.1 vs resurrection remix 7.0

Guys which one is better in terms of performance??

MIUI is always better
Wysłane z mojego Redmi Note 5 przy użyciu Tapatalka

Kriskuthu said:
Guys which one is better in terms of performance??
Click to expand...
Click to collapse
Depends on your personal preference because there is no huge difference in performance
-If you like stock android experience use Pixel Experience
-If you like stock android experience with plethora of customizations then go for RR7
-and if you just want better battery than go for miui
Pakistani

Resurrection remix is much better than pixel experience.
However miui is more optimised for the phone.

You want speed and performance?
I suggest you flash latest Aosip and flash Mihran's Twrp recovery and format your data partition to f2fs.(note that by formatting your data to f2fs will wipe your internal storage) You will forget everything else.

More smoothness go for PE
ALL Customisation go for RR
If you want ads go for miui

customroms can never beat the Vendor Stockrom
all Custom roms 8.1 / 9.0 that i have tried ( and i tried nearly 25 roms) and THE ONLY two ADVANTAGES i have found over MIUI are
1. Dirty Unicorn Customizations ( navbar tweaking, statusbar tweaking, display screen tweaking etc)
2. Kcal advantage to set saturation and screen tints and values according to you eyes
the following disadvantages i have found in almost all custom roms (main because all roms are using AnyKernel Source by Osmosis) (derp / insignix / noname kernels etc)
1. Random Reboots while disconnecting call/ gsm call or whatsapp call or messenger calls ( in Oreo) (works fine if Headphone jack instered)
2. screen fails to wakesup when mobile removed from ear to disconnect call! (oreo) (works fine if headphone jack is inserted)
3. whatsapp voice notes acts funny and makes screen off for first 2 seconds while playing any recieved whatsaap not (OREO/PIE) (works OK if headphone jack is inserted
MIUI 10x
1. smooth rom with better screen colors then miui9
2. kcal doesn't work even if you change kernels (the values only sticks until you don't switch off the screen)
3. amazing batterlife!
4. heavy on ram! even 6gb ram is 52% always full (mainly due to rich MIUI blobs

@YasuHamed
These two apps are the alternative for kcal on MIUI, one for the saturation and the other has an option to control the RGB with also some nice features and that's more than good enough.
Let the apps start on boot from auto-start setting or simply you can convert them to system apps and forget.
https://play.google.com/store/apps/details?id=com.xda.sa2ration&hl=en
https://play.google.com/store/apps/details?id=eu.chainfire.lumen&hl=en
Edit: @RUSHI6 Is really removing msa.apk is that hard? LOL!

rocker00 said:
@YasuHamed
These two apps are the alternative for kcal on MIUI, one for the saturation and the other has an option to control the RGB with also some nice features and that's more than good enough.
Let the apps start on boot from auto-start setting or simply you can convert them to system apps and forget.
https://play.google.com/store/apps/details?id=com.xda.sa2ration&hl=en
https://play.google.com/store/apps/details?id=eu.chainfire.lumen&hl=en
Edit: @RUSHI6 Is really removing msa.apk is that hard? LOL!
Click to expand...
Click to collapse
yes i have tried both , they are good B grade substitution for Kcal as none of them allows your to change screen output values, and control contrast. if you compare whatsapp screen of RN5p on MIUI with Samsung or Huwaie or Sony, you will see Major difference where thier color/contrast values always define chat borders and easy to read!

RUSHI6 said:
More smoothness go for PE
ALL Customisation go for RR
If you want ads go for miui
Click to expand...
Click to collapse
well but in miui you can use dual apps while RR and PE require third party apps which also contain ads such as parallel space

YasuHamed said:
customroms can never beat the Vendor Stockrom
all Custom roms 8.1 / 9.0 that i have tried ( and i tried nearly 25 roms) and THE ONLY two ADVANTAGES i have found over MIUI are
1. Dirty Unicorn Customizations ( navbar tweaking, statusbar tweaking, display screen tweaking etc)
2. Kcal advantage to set saturation and screen tints and values according to you eyes
the following disadvantages i have found in almost all custom roms (main because all roms are using AnyKernel Source by Osmosis) (derp / insignix / noname kernels etc)
1. Random Reboots while disconnecting call/ gsm call or whatsapp call or messenger calls ( in Oreo) (works fine if Headphone jack instered)
2. screen fails to wakesup when mobile removed from ear to disconnect call! (oreo) (works fine if headphone jack is inserted)
3. whatsapp voice notes acts funny and makes screen off for first 2 seconds while playing any recieved whatsaap not (OREO/PIE) (works OK if headphone jack is inserted
MIUI 10x
1. smooth rom with better screen colors then miui9
2. kcal doesn't work even if you change kernels (the values only sticks until you don't switch off the screen)
3. amazing batterlife!
4. heavy on ram! even 6gb ram is 52% always full (mainly due to rich MIUI blobs
Click to expand...
Click to collapse
I never expierienced random reboots, screen fails or "funny" voice notes. But I had several phones where the custom rom was way better than the stock rom. Especially when the stock roms are bloated with useless ****.
heavy on ram doesn't make any sense. The OS isn't supposed to have a lot of free ram laying around doing nothing. If you think it should, then you probably also "cleaning" apps out of your recent history.
Shojimeguro said:
well but in miui you can use dual apps while RR and PE require third party apps which also contain ads such as parallel space
Click to expand...
Click to collapse
This function is probably useful for like 5% of the users. But obviously there are apps without ads for that function.
https://f-droid.org/en/packages/net.typeblog.shelter/

sukk0r said:
I never expierienced random reboots, screen fails or "funny" voice notes. But I had several phones where the custom rom was way better than the stock rom. Especially when the stock roms are bloated with useless ****.
heavy on ram doesn't make any sense. The OS isn't supposed to have a lot of free ram laying around doing nothing. If you think it should, then you probably also "cleaning" apps out of your recent history.
This function is probably useful for like 5% of the users. But obviously there are apps without ads for that function.
https://f-droid.org/en/packages/net.typeblog.shelter/
Click to expand...
Click to collapse
Wow gotta try this free apps, thank you ~!

[EAS-KERNEL][libra/aqua]Watermelon kernel-v3.0-stable-linaro-5.4.1

Introduction
WKernel is a custom EAS kernel compatible with libra/aqua and on android pie(LOS16,MOKEE9,crdroid).
Click to expand...
Click to collapse
Features
-the newest wlan driver modules
-EAS schedule(sched)
-add f2fs support
-Disable storage CRC check. (reduce IO overhead)
-FSync on/off. (off by default)
-overclocking/underclock msm8992(cpu)
-linaro 5.3.1 compiled
-GPU adreno 418 OC to 650mhz
-adv tcp “htcp,bic,westwood”
-Certified safety net
-A few more optimization.
Click to expand...
Click to collapse
Thanks everyone help me
Eas（energy aware schedule） is developed by arm and linaro,after google cover to bullhead(nexus5x)
focusing on energy consumption. I backported it to Xiaomi 4c. You can use multiple charging rate to feel how it battery.
*some new phone use "Schedutil", also based on EAS. It was made by Intel after kernel mainline msm-4.9
Download link:
download
Click to expand...
Click to collapse
UPDATE LOG:
Code:
2.4 version
EAS schedule
Fsync control
overclocking/underclock msm8992(cpu)
Disable storage CRC check,ssd random read
lz4 and zram Algorithm update
optimited ext4 block read
Certified safety net
2.5 version
add wakelock blocker 1.1.0
add sdfat(otg any softwave filesystem)
add power efficient wq
add usb fastcharge
add wireguard importer
add tcp “htcp,bic,westwood”
update EAS Eeergy Profile(for A57)
sched/fair(EAS) idle balancing
2.5.1 version
sharp rsp61322 screen framerate to 75HZ
A few more optimization.
2.6.1 version
enable usb fastchg by defualt
optimized memcmp
Align to cache and preload
2.7 version
add devfreq boost from sultan
add sio/fiops
3.0 version
1,remove sultan devfreq-EAS can boost cpufreq less power energy
2,fix RCU pointer task p->mutex (More important for performance)
3,update 8992 dts energy profile from Qualcomm Trepn app
4,Avoid EAS using SMP load balance when heavy loads
5,More optimization(fix gcc 5.4 warning)
6,sched governer by default
Watermelon kernel-3.0 stable
smp governer(tripping point->average load balance)
heavy load task migration caused CFS load up to a value and change smp governer work on big.little leads to game delay,
CFS unfriendly on the EAS,harmful for battery.
now,Watermelon kernel-3.0 is better on play game,no touch delay.
no need to offline core or cluster.
more power saving on daliy-life.
have a good time!
XDA:DevDB Information
[EAS-KERNEL]Watermelon kernel, Kernel for the Xiaomi Mi 4C
Contributors
Tianjingbaozi2
Source Code: https://github.com/Gah0/android_kernel_xiaomi_libra
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2019-10-09
Current Beta Version: all old version
Beta Release Date: 2019-07-05
Created 2019-07-05
Last Updated 2019-10-08

how about CrDroid ?

rianawirawan said:
how about CrDroid ?
Click to expand...
Click to collapse
Working on mine

Tried on Pixel Experencie Pie, from Kenga, but is very unstable (freeze, reboot, etc)
Did you notice speed improve with EAS scheduler?
Thanks

Tested on Mokee stable 8.1.0 =))))) but kernel version is unavailable, is it okay?

Somehow this kernel breaks double tap to wake on mokee stable 8.1 But this is a great kernel anyway. Keep up the good work =))))))))

try to install on crdroid but twrp say invalid partition. anybody face this problem too?

Tried on CrDroid, main problem is freeze and random reboot.

rianawirawan said:
Tried on CrDroid, main problem is freeze and random reboot.
Click to expand...
Click to collapse
It's strange, I don't have any problems on crDroid.

Working fine on my crDroid. IMO EAS is too conservative.
I also have regular random reboot but I think it's edxposed related.

YiPing_Huang said:
Working fine on my crDroid. IMO EAS is too conservative.
I also have regular random reboot but I think it's edxposed related.
Click to expand...
Click to collapse
How is the battery life with this kernel?. I'm using the latest crDroid available and it's pretty bad with stock kernel.

edu27 said:
How is the battery life with this kernel?. I'm using the latest crDroid available and it's pretty bad with stock kernel.
Click to expand...
Click to collapse
I would say so-so.
But I don't demand too much from this old 2015 device.
Plus my battery is probabily worn out a lot.
I use crDroid for customizability and this kernel for native Wireguard support.
Always have a Xiaomi slim powerbank standby.
Edit:
I no longer experience random reboot with version 2.5.1.
Fast charge seems to be off by default. I have to enable it using FK Kernel Manager.

Hello. I have crDroidAndroid-9.0-20190716-libra-v5.6.zip running with the latest Wkernel(Pie)-EAS-V2.5.1.zip and I'm getting reboots. It was continuously rebooting overnight, I noticed and switched the phone off and I have now just switched it back on and again it's rebooting randomly. Thx.

Better use in crdroid 9, los16, or mokee9
I noticed that the usb fastcharge looks like it has been closed all the time. I will open it in kernel on the next version.
im using crdroid-20190716 on 3days，everything is stable
These days I am adjust kernel on crdroid0716
Cpu hotplug busy drop threshold can be reduced to 25, busy up is 50, set in cpu hotplug, animation lag problem will not easily appear, the big.Little architecture is too old, the task transfer is too inefficient in msm8992.

Hello Tianjingbaozi2. I have since reverted back to the ROMs kernel with no reboots now. I did notice the battery massively improved with this Watermelon kernel but the phone now reboots randomly. I read in here others have had reboot issues too? I don't have anything major installed just the rom crDroid, gapps/pixelmodgapps and root magisk. I haven't toyed with the kernel with any kernel manager app. I did charge the phone with Watermelon kernel on and it did say fast charge. Thx.

I have tested this kernel on AEX 7.1 Nougat and got only one problem. The screen is kinda dimmer and I want more brightness.
The reason of flashing this kernel on AEX 7.1 for me are Energy Aware Scheduling and 75Hz screen. Sound, camera and etc. are working.
So the only problem is brightness. I hope someone can help me to tweak some files and get higher max brightness.

Works fine on mokee 9 but the performance in games with eas is terrible.

C0dyCZ said:
Works fine on mokee 9 but the performance in games with eas is terrible.
Click to expand...
Click to collapse
I agree that
You should need to close the big cluster via exkernel manager when you play games

This kernel also works on Nougat
Arman Yuzbashyan said:
I have tested this kernel on AEX 7.1 Nougat and got only one problem. The screen is kinda dimmer and I want more brightness.
The reason of flashing this kernel on AEX 7.1 for me are Energy Aware Scheduling and 75Hz screen. Sound, camera and etc. are working.
So the only problem is brightness. I hope someone can help me to tweak some files and get higher max brightness.
Click to expand...
Click to collapse
I also have this, low brightness. I use this kernel on RR 5.8.5 nougat. Everything works well, only brightness is very low. How is the brightness on Pie? I have used this kernel from 2.6.1 'till the latest 2.7
For the dev, thank you, good work ?

Version 2.7 works fine on my mi4c with crDroid (crDroidAndroid-9.0-20190716-libra-v5.6). The battery life is much more better.
One thing not working fast is the GPS. Google Maps takes a long time (2-10 minutes) to find signal. And sometimes, if the network signal is bad, Maps never find your position.
Apart from this, the general responsiveness of the phone is very correct.
A big thank you to the contributors!