Fix for heating issue without performance drop [Root Required] - Xiaomi Redmi 1S

Redmi 1s Indian version has some worst heating problem. During gaming or video recording the external device temperature gets to around 45-50 degree Celsius which makes it difficult to even hold the device and is also dangerous. The reason behind this is poor heat management and its a shame Xiaomi could not still fix it after many updates. They further made a mess with MIUI 5 v45 by killing the performance still having the heating issue.
After experimenting with the device for about one month, I noticed that hot plugging decreases the battery backup and performance. It consumes more current for low performance. [Tested manually with 3C Cpu Manager and Cpu Temp Apps.] So I concluded Cpu Performance, Battery Performance and Hotplugging should be used optimally to extract the maximum out of this device without any sacrifice.
It is possible to have Good Performance with almost No Heating by enabling the default qualcomm MP decision, Core Control and Thermal Driver and a modified thermal config.
We can fix this in two simple steps [Make sure you have root access]
First Fixing Heating Issue
Download Device Control App from Play Store
Open the app and grant root permissions
1. Go to Extras in the Performance menu and select Thermal Driver and enable Core Control and MSM-Thermal.
2. Now go to Cpu Setting in the menu and enable MPdecision.
3. Goto Preferences >> Reapply on boot and choose Cpu settings and Extras.
4. Close the app and go to Security App >> Permission >> Auto-start management >> Add auto-start apps and choose Device Control
Second Restoring Performance
Go to this Thread by ravinder0003and download either Balanced Config or Gaming Config
Flash it in recovery or extract the thermal-engine-8226.conf file and move to /system/etc manually (Don't forget the permissions).
Now your device can be used at its full potential without any heat issue
This will work almost in every kernel with qualcomm thermal drivers and is found to the most efficient way of fixing Redmi 1s Performance without affecting battery backup.
If the thermal-engine-8226.conf file is deleted once and rebooted in the past then heating issue will occur even after above settings- try after installing the firmware again through recovery.
Other Settings
Go to Extras >> Powersaving >> Power Scheduler >> 2 - Aggressive in Device control App. It forces the tasks into 2 cores and doesn't wake the other two cores for simpler tasks improves battery backup.
Set the CPU Maximum frequency to 1344Mhz using Device Control if you don't want any heat on the device and get maximum battery backup.
If you want to use the device while plugged in to mains while watching movies or use youtube set the CPU Maximum Frequency to 600Mhz or 998Mhz. [Its highly recommended not to use the device while charging via mains].

Heating Issue for Redmi 1s
I have two questions ?
1. Whether the phone has to be rooted.
2. Whether it will work for the latest update of MIUI V50 for Redmi 1s
Thermal Patch by ravinder.

dangerjaison said:
Redmi 1s Indian version has some worst heating problem. During gaming or video recording the external device temperature gets to around 45-50 degree Celsius which makes it difficult to even hold the device and is also dangerous. The reason behind this is poor heat management and its a shame Xiaomi could not still fix it after many updates. They further made a mess with MIUI 5 v45 by killing the performance still having the heating issue.
After experimenting with the device for about one month, I noticed that hot plugging decreases the battery backup and performance. It consumes more current for low performance. [Tested manually with 3C Cpu Manager and Cpu Temp Apps.] So I concluded Cpu Performance, Battery Performance and Hotplugging should be used optimally to extract the maximum out of this device without any sacrifice.
It is possible to have Good Performance with almost No Heating by enabling the default qualcomm MP decision, Core Control and Thermal Driver and a modified thermal config.
We can fix this in two simple steps [Make sure you have root access]
First Fixing Heating Issue
Download Device Control App from Play Store
Open the app and grant root permissions
1. Go to Extras in the Performance menu and select Thermal Driver and enable Core Control and MSM-Thermal.
2. Now go to Cpu Setting in the menu and enable MPdecision.
3. Goto Preferences >> Reapply on boot and choose Cpu settings and Extras.
4. Close the app and go to Security App >> Permission >> Auto-start management >> Add auto-start apps and choose Device Control
Second Restoring Performance
Go to this Thread by ravinder0003and download either Balanced Config or Gaming Config
Flash it in recovery or extract the thermal-engine-8226.conf file and move to /system/etc manually (Don't forget the permissions).
Now your device can be used at its full potential without any heat issue
This will work almost in every kernel with qualcomm thermal drivers and is found to the most efficient way of fixing Redmi 1s Performance without affecting battery backup.
If the thermal-engine-8226.conf file is deleted once and rebooted in the past then heating issue will occur even after above settings- try after installing the firmware again through recovery.
Other Settings
Go to Extras >> Powersaving >> Power Scheduler >> 2 - Aggressive in Device control App. It forces the tasks into 2 cores and doesn't wake the other two cores for simpler tasks improves battery backup.
Set the CPU Maximum frequency to 1344Mhz using Device Control if you don't want any heat on the device and get maximum battery backup.
If you want to use the device while plugged in to mains while watching movies or use youtube set the CPU Maximum Frequency to 600Mhz or 998Mhz. [Its highly recommended not to use the device while charging via mains].
Click to expand...
Click to collapse
As above thread asked.. Will this work on V50 on latest release of Stable MiUI ???
Sent from my HM 1SW using XDA Free mobile app

It should work fine for all the version. I lost the device and moved to android one. Rooting is required and warranty is not lost if rooted for XIAOMI device. Make a full backup using philz recovery and try it
Sorry for late and incomplete reply.

The Power scheduler which forces apps to use 2 comes always resets after some time to its default configuration. Any fix?
Sent from my HM 1SW using XDA Free mobile app

[Its highly recommended not to use the device while charging via mains
Click to expand...
Click to collapse
Facepalm
So how to navigate in car on 8 hour trip? Phone downlock to 300MHz from 600MHz. I can't even answer phone call (it's hanging)

Suprb..thanx bro

I just want to know that is there any drawbacks of using core control and msm thermal at same time?
Do they conflict?

Related

[GUIDE] [STARTER] (Custom) Kernel Features Explained! - NEW FEATURES [06/30/2013]

This is a simple STARTER GUIDE to kernel features/parameters and everything you need to know about custom kernel goodies before you consider flashing them. I’d be glad if you could help me complete this guide. Thanks to @Shan89 for his fantastic guide which inspired me to collect this.
First of all I’d like to thank all kernel guys who put countless hours into this to bring us the features which I am going to explain soon. Especially: XMister, n3ocort3x, Kozmikkick, Maxwen, Showp1984, faux123, TripNRaVeR, Alex-V.
Overview:
Post 1:
A.: What you want to know about the CPU/GPU of your device
B.: Custom Kernel Features
Post 2:
C.: Built in kernel features with no user control
D.: FAQs (Frequently Asked Questions)
More coming Soon!!!
Post 3:
E. Repacking
F. Useful Tools and Guides out there
More coming Soon!!!
A: What you may want to know about the CPU/GPU of your device:
HOX is powered by nVidia Tegra 3 which is a Quad Core CPU and it is said that have a Core Frequency of 1.5GHz. Also nVidia Tegra 3 comes with ULP Geforce GPU which is at 520MHz in all custom kernels available. You may want to know that your HOX can go up to 1.5GHz of single core and 1.4GHz of 4cores active with Stock kernel (The kernel that comes with your device out of the box). However custom kernels can perform 1.5GHz for all 4 cores.
nVidia Tegra 3 is in fact a 5 core chipset. The Advertising hype was about its 4+1 cores. So what is that one extra core? That core is called LP (Low Power) core. When the phone is in idle (sleep) this core is used. It is a weak core with 475MHz of processing power. It is there to save battery life as when we are in idle we do not need a whole 1.5GHz core to be active.
B.1: CPU/GPU/IO Features which come with Custom Kernels:
•NOTE: Enabling/Disabling these features are explained in the kernel forums. Here is a very simple example to get you up and running so that you don’t feel lost.
In the kernel forum it is said:
To enable S2W:
echo ‘1’ > /sys/android_touch/sweep2wake
So what on the earth does that mean?! It means install a terminal emulator program on your device (Here’s one). And then run it. First type “su” without the quotation marks and hit enter. It will ask for Superuser privileges. Grant it. Now type in the line above echo blah blah blah and hit enter. And bam! There you go, S2W is enabled. Always be advised that ‘1’ means enable and ‘0’ means disable.
Click to expand...
Click to collapse
OC/UC (As for OverClock/UnderClock):
As you may know, CPU or any other processing unit features a clock frequency. Over/Under Clock simply means raising/decreasing the clock frequency of CPU.
Reason: Why would one need to overclock? Because one needs more processing power. For example if you want to experience smoother graphic when playing high-graphic games.
Why would we need underclock? Higher processing power demands more battery. So underclocking helps us, reserve more battery. As for HOX, searching internet and texting don’t need much of processing power. So we can limit the processing power and save battery during low use of our device.
•Note1: OC/UC is not limited to CPU. GPU is also capable of OC/UC. And the interface for that is also available in the custom kernels of HOX.
•Note2: Gamers may not use GPU UC. Limiting GPU processing power impact significantly on your gaming experience.
UV (As for Undervolt):
Every frequency of a processing unit, demands a certain amount of power to be supplied. Undervolting to put it simple means decreasing the voltage of a certain frequency (or all of them).
Reason: The more voltage CPU/GPU gets, more heat will be generated. So mainly we UV to decrease the generated heat of CPU/GPU.
•Note1: One Frequency needs a certain minimum amount of voltage to perform correctly and the system be stable. Undervolting more than a certain amount of voltage will cause system instability.
•Note2: HOX is known for getting hot soon. So UV is a great workaround for your device to be cooler.
•Note3: UV does not impact battery life (or it is not noticeable).
•Note4: For ULTIMATE guide about Undervolting and safe values visit Shan89’s great guide here.
Separate X/Y OC interface:
This probably means that the kernel has separate OC interface (interface to control OC) for operation X and operation Y. To be more exact it means you can OC different values for X and Y.
Audio Min. Freq.:
This specify the minimum frequency of the CPU when Audio is being processed. Default min in custom kernels is normally 51MHz. But Audio needs some more processing power. Anyhow, with this you can change that value.
LP Core OC:
The name explains everything. OC for LP core of T3 chipset.
Reason: LP core uses very little battery. So as long as the phone stays at LP core, more battery will be saved. If LP is OCed, it means it can handle more complex processing tasks and can hold more before letting the device to wake main cores. So battery will be preserved!
•Note: These are work in progress features and mostly in beta releases of Kernels. So using may cause system instability and other issues. So use them if you know what you are doing.
Hotplug Control - NEW:
Hotplugging dynamically activates second CPU core ON on load conditions and turns second core OFF on low load conditions. (From here).
Click to expand...
Click to collapse
- first_level: The number here specifies the amount of load on the cpu for it to turn on all the available cores (4 cores online).
- cores_on_touch: This number specifies the number of cores to come online when you touch the screen. (2 is efficient, 4 for extra smoothness on touch, and so more battery drain.)
- suspend_frequency: When screen is off, you don't expect your device to be smooth (!!!) and snappy! Because mainly nothing important is happening when screen is off. The number here specifies the maximum frequency of the CPU when the screen is off. Screen Off Max CPU can be really a very low number.
CPU Governors:
Frequency scaling is the means by which the Linux kernel dynamically adjusts the CPU frequency based on usage of the device. Governors refer to schemes which dictate to the kernel how it should do these adjustments. (From rootzwiki)
To put it simple, Governors are the way that CPU frequency is adjusted according to the demand of operating system.
Selecting a proper governor for your CPU is crucial to the performance and battery preserving of your device. For example if you are low using your device you may use a more battery friendly governor and if you want to play games you may use a more power consuming performance governor.
•Note: See Shan89’s Great Guide about Governors to be familiar with each one of them and the ones that you should use in different situations here.
I/O Schedulers (As for Input/Output):
Input/output (I/O) scheduling is the method that computer operating systems use to decide which order block I/O operations will be submitted to storage volumes. I/O Scheduling is sometimes called 'disk scheduling'. (From Wikipedia)
To put it simple, Schedulers are the way reading and writing to the SD card is managed.
The same things that is said in the Governors part is applied here, too.
•Note: See Shan89’s Great Guide about Schedulers here.
ReadAhead buffer size:
In terms of reading data from SD card, there is a cache which is used as a buffer. The size of that cache is readAhead buffer size. The size has a direct impact on your reading speed of your SD. So giving it a right amount is crucial.
•Note: Kernel guys believe that 128 is the right amount for that and it is the default in most of the kernels.
File System “X” R/W (As for Read/Write):
Android by default doesn’t support all the File Systems (What are file systems?! See here). So some kernels may add certain file system R/W. The most popular unsupported file system is NTFS.
B.2 Features of Custom Kernels (AKA Goodies!!!):
S2W (Sweep2Wake):
With S2W enabled you can wake/lock your device by sweeping your finger from left to right (or right to left) on the hardware keys of your device (Pretty Cool, hah?).
Reason: Some people just don’t like the hardware power button! Or after some time it will become less responsive. And some will use S2W because it is cool!!!???
•Note1: S2W doesn’t affect battery life that much. It almost does not use even a little bit. But be aware this stands corrected as long as you don’t touch your device. Touching the device would cause in waking the device from deep sleep.
DT2W (Double Tap 2 Wake):
It is something like S2W to wake the device. Double tap on the screen to wake the device.
•Note: The note for S2W applies here, too.
BLN (BackLight button Notification):
With BLN enabled your hardware buttons will blink when you have notifications. It is an/a alternative/support for led notification.
FastCharge:
This feature makes it possible for the phone to ask for more current from USB host. So your device would be charged faster connecting to a USB host (Or USB Battery) Be aware that enabling FastCharge would block the USB access to your Phone Storage.
UMS (USB Mass Storage):
After ICS, google only allows MTP connection to the PC. Back at ICS there was a UMS which make available your Phone Storage as a Mass Storage device in PC. The Mass Storage advantage is that you can manipulate data on it but it cannot be done using MTP. UMS feature returns that feature to your device. A system interface is also needed which is available in ViperX ROM or Lyapota’s mod.
•Note: MTP vs UMS (From here):
MTP:
1. Can copy files over (like APKs) and then access on them on the device without mounting/unmounting.
2. File transfer is available immediately when plugged in without having to mount.
Mass storage:
1. Better security since you have to get past the lock screen to mount.
2. Is actually a real drive in Windows, so you can do all operations normally.
MHL (Mobile HighDefenition Link):
It provides the feature for the miniUSB to HDMI cables to work. To output the device screen using HDMI.
SmartDimmer:
SmartDimmer can intelligently vary the backlight brightness of your device screen to help maximize battery life.
•Note: Haven’t really tried this. You may try it yourself and see how it is.
MultiCore PowerSaving:
This feature try to group up tasks in the least cores possible. To put it simple, it will focus in using least cores for your tasks to be done. This means less cores are active and so more battery life. Also this will decrease performance.
•Note: To enable use TricksterMod app. 0 for disable and 2 for the most aggressive.
Core Control/Max Active CPU Cores:
As the name suggests, this feature allows the user to set the maximum active cores of the CPU. In other words, you can completely shut down some cores. The default value is 4 as we have 4 max active cores. you can reduce this to 3, 2 or 1. But 1 is not really recommended.
Note: Core Control is the feature of ViperX ROM.
B.3 Other Features:
Pocket Protection - NEW:
Using features like S2W and/or D2TW when the phone is in your pocket (with no specific cover) occasionally causes the screen to turn on. (as a result of being close to your skin and almost touching it). This feature is there to prevent such wake ups. It uses proximity sensor to determine if the phone is in a closed position to something. If that is true, the screen won't turn on. :victory:
Swap:
Swap is a space which provides help to RAM in situation of low memory. When you are low in RAM some data will be stored in Swap space (Mostly cache). Swap is a space on Internal (and/or External Memory) so swap is not fast in comparison to RAM, but it helps multitasking, because you could cache more app data to your memory. So the results are less Force closes because of low RAM and faster switching between apps.
Swap is not really used by default, or it is used with very low space. You can boost your Swap, and also know more about this. there's a very nice MOD called Turbo Boost which allows you to add more Swap using your unused space. See this.
zRAM:
In zRAM unnecessary storage resources are compressed and then moved to a reserved area in the fixed RAM (zRAM). So in other words, zRAM is a kind of swap in memory (see swap above). As the data is compressed not much memory needs to be preserved as zRAM. However, the CPU has to work more because compressed data has to be unpacked again when it is needed). The advantage clearly lies in the speed. Since the swap partition in RAM is much faster than this is a swap partition on a hard drive.
In itself a great thing. But Android does not have a swap partition, and therefore brings Android ZRAM under no performance gain as would be the case with a normal PC. (From here with some editing.)
Click to expand...
Click to collapse
What we need to know essentially lies here:
zRAM off = Low use data will be stored the way they are in the memory. This will cause no extra load on CPU, yet need more RAM.
zRAM on = Low use data will be stored compressed in the memory. This will cause extra load in CPU as to store or restore data, yet preserve more Free RAM.
The main use of zRAM is when you are using a heavy ROM that eats up all your RAM. This will allow multitasking to be more functional. On light ROMs, or for those who don't multitask much, this is not necessary.
Init.d Support:
There are some scripts that run every time your device boot up which are located in /etc/init.d Those are called init.d scripts. One of the most popular init.d scirpts that is available for Note 10.1 is this.
DriveDroid Support:
Gives the phone the ability to use DriveDroid.
DriveDroid allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go... without the need to burn different CDs or USB pendrives.
Click to expand...
Click to collapse
Take a look here for more information.
TCP Congestion Control:
The choices in this section, address how the operating system kernel manages flows of information in and out of the kernel, which is at some level the "switchboard operator" of your handset. More info here.
Better to leave this options as is. Cubic as the default of your kernel.
Dynamic FSync:
fsync is a system call in Unix/Linux. "man fsync" says:
fsync() transfers ("flushes") all modified in-core data of (i.e., modified buffer cache pages for) the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even after the system crashed or was rebooted. This includes writing through or flushing a disk cache if present. The call blocks until the device reports that the transfer has completed. It also flushes metadata information associated with the file (see stat(2)).
Click to expand...
Click to collapse
So it's something embedded in programs after a related set of write operations to ensure that all data has been written to the storage device. The bolded part is what makes it interesting for some to disable it - "The call blocks" means the calling program waits until it's finished, and this may create lag. The downside is that if the system crashes, the data on the storage devices may be inconsistent, and you may lose data. (From here).
Dynamic FSync, makes it possible for fsync operation to be asynchronous when the screen is on, and synchronous when the screen is off. And what does asynchronous mean? Means OS issues fsync call, but not necessarily immediately at commit time for each transaction. It delays the FSync call for a certain amount of time. In case of a crash, the transactions not yet sync'ed in the last delay time before the crash may be rolled back, but the state of the data is always consistent. (From here).
Work in progress, will add more info soon.
C. Some built in features with no user control:
Tegra 4 Drivers - NEW:
First you may want to know what a driver is:
A driver is a small piece of software that tells the operating system and other software how to communicate with a piece of hardware.
For example, all printers come accompanied with drivers to install that tell the operating system exactly how to print information on the page. (From here).
Click to expand...
Click to collapse
So kernel guys (Trip to be exact) made it possibe to use some Tegra 4 drivers on Tegra 3 Chip of HOX so that we can enjoy the advantages of new drivers.
MPDecision:
Mpdecision decides when the second core shall be active and sets the idle and screen off freq while the governor decides when the freq should be increased / lowered.
More info at this thread.
CPU Quiet:
It's a dynamic CPU core management. More info here.
D. FAQs (Frequently Asked Questions)
MUST KNOW FACTS:​
The modifications and changing values of kernel parameters will stick until the next reboot. They will be set to default when you reboot your device. So if you want them to stick, you have to do one of the following:
1. Init.d Scripts: Here is a complete guide, how to make one. Also you can use 'CS' app. Which is explained in Useful tools part of this guide (Post 3).
2. Set on Boot: The programs like Trickster Mod, have an option named 'Set on Boot'. If you want the settings you have in Trickster to stick, you have to check that option.
---------------
And a quote from the elite developer that everyone know:
However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance. - Chainfire
Click to expand...
Click to collapse
Q. I'm on Stock. How can I flash a custom kernel?
A. See this complete Tutorial, here.
Q. Is it dangerous to flash a custom kernel?
A. As long as you follow the instructions step by step there shouldn't be any problems. However flashing is always at your own risk.
Q. Why would I need to flash a custom kernel?
A. Because of the goodies I described in post 1.
Q. Which Kernel is more suited for me?
A. That really depends on you. You have to try the kernels and see which one is more suited for you. In Post 3 A little description about the kernels will be provided.
Q. AOSP or Sense???!!!
A. Sense Roms can be identified by their description. Just visit the page of your desired ROM and see what is its base. If it has 'stock' as the base it's sense ROM. If it has AOSP, AOKP, CM or other things then it is an AOSP rom. So identify your base before flashing kernel.
Q. I don't like this fastboot stuff. Why HOX can't flash boot via recovery?
A. That is because something called S-ON (Security-On) by HTC which prevent flashing boot.img via recovery.
Q. Repack?! What on earth is that?
A. Repack will be elaborated in detail in Post 3.
Q. Is repack needed for Kernel X and ROM Y?
A. See Repacking in post 3.
Q. Is there a kernel with OC interface up to 1.6 or 1.7?
A. Yes. Search!
Q. I just want S2W or UMS with Stock kernel, nothing more. Is there a kernel to provide that?
A. Yes, Alex-V Kernel v.0.3 is there for you. See Post 3 when it's ready for more info.
Q. After installing custom kernel I am experiencing battery drain issues. Why is that?
A. The current custom kernels do not have drain issues. Install Better Battery Stats and/or GSam Battery Monitor to figure out what is causing the battery drains.
More Info will be added soon.
E. Repacking:
All Android roms require a boot image to work (normally named boot.img). These files contain the ramdisk necessary to run the rom, as well as the kernel. Occasionally you may want to replace the kernel to add new features or fix bugs, but you must tweak the image to be compatible with your rom (And also as the ramdisk may contain some tweaks, to preserve those tweaks and add them to the kernel of your choice). (From Here).
Click to expand...
Click to collapse
The very main question "Is it really needed?"
Well, you don't really need to repack kernels for Sense/AOSP Roms anymore (Those days are gone!) as they already contain the tweaks and ramdisk to get almost all the ROMs up and running. But sometimes you may encounter some problems like Weak signal/Wifi or such issues. In that case, it is advised to repack your kernel.
How to Repack?
Before you start repacking you need these 2:
1. Ramdisk (boot.img) of the ROM you are using (Or you wish to use). It is usually in the zip file of The ROM which you flashed (or going to flash) via recovery. Just open the zip file and extract boot.img. Some ROMs put the boot.img in their OP (First posts of the respective thread). So if the ramdisk wasn't in the zip file of the ROM, take look at the thread of the ROM.
For preventing the confusion rename the boot.img to the ROM name + ROM version for example Renovate_F4.img
2. Kernel image (boot.img) of the Kernel you wish to use. Some kernels put it for download in their thread. Sometimes modules and image is both in one archive. In that case open the zip file if the kernel and extract boot.img. Make sure you don't replace the other boot.img from step 1. For preventing the confusion rename the boot.img to the kernel name + kernel version + the kernel base(Sense/AOSP) for example XM_305_Sense.img
Click to expand...
Click to collapse
a. Using online repacker:
1. Visit this site: http://nibble.cc/repack/index.php
2. In source kernel image, choose the ramdisk of the ROM. (ex. Renovate_F4.img)
3. In New kernel image, choose the kernel image. (ex. XM_305_Sense.img)
4. Hit 'upload and repack'.
5. Download the repacked kernel.
b. Using One Click Tool:
1. Copy the ramdisk and the kernel image to "kernels" folder which is in the folder of the tool.
2. Connect your device and run the tool.
3. Select "Kernel repack".
4. Select the kernel image in "kernel" section.
5. Select the ramdisk in the "ramdisk" section.
6. Hit "perform action".
7. The repacked kernel is in the "repacked" folder which is the folder of the tool. It's name is a combination of The kernel name and the ramdisk name so that it can be identified easily.
Note: You can also choose to flash the kernel. Just check "Flash repacked kernel". The tool automatically reboots into fastboot and flashes the kernel.
Note: You can choose to repack via PC in the tool. It is much more faster. And also you can repack without connecting your phone if you choose repack via PC (This feature works from version 2.1 or 2.0 I think. Check the thread for more info).
F. Useful Tools and Guides out there:
F.1. Tools:
Trickster Mod:
A little yet powerful program. It is almost the best tool that you can have on your HOX to change certain kernel parameters like UC/OC/Voltage Control of both CPU and GPU. Schedulers, ReadAhead BufferSize, Advanced Governor control. You can change features like S2W and SmartDimmer, too. Also you can set this changes to take effect on boot. Which automatically sets the parameters on device startup (preventing the defaults values to be set, again).
Trickster Mod - Google Play
CS - Custom Settings:
This app is exclusively made for HOX, so it supports most of the features of custom kernels. This app manages to set the values you desire by generating init.d scripts. So there is no set on boot operation by the app but by the scripts.
Custom Settings - XDA
One Click Tool:
This tool is created for One X, and you use it to repack and flash kernels. And by flashing I mean no CMD and other scripting stuff. This tool automates flashing (Though the flashing process via fastboot is not that much of a hard work!).
One Click Tool - XDA
F.2. Guides:
- Battery Life and Gaming Guide + UV/UC and everything explained! by Shan89
- Boosting gaming experience and maximizing performance for gaming by hamdir
More info will be added soon.
Reserved for later reading
Sent from my HTC One X using XDA Premium App
Desaf said:
Reserved for later reading
Sent from my HTC One X using XDA Premium App
Click to expand...
Click to collapse
Yeah, sure!
Sent from my HTC One X using Tapatalk 2
Added recently to the guide:
Post 1:
- ReadAhead buffer size
- Init.d
- TCP CC
Post 2:
- FAQs.
realy helpful
thanks mate for the information.
mandrive said:
thanks mate for the information.
Click to expand...
Click to collapse
Glad to be of help!
Sent from my HTC One X using Tapatalk 2
Recent added to the OP:
- Swap (In appearance of the nice Mod TurboBoost)
- Dynamic FSync (Tricky feature)
Will be added soon:
- Repacking
Nice tut
Sent from my HTC One X using xda app-developers app
Alex-V said:
Nice tut
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, man.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Thanks, man.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Added with credits to my kernel thread..thx again
Sent from my HTC One X using xda app-developers app
Recently added:
Post 2:
- TEGRA 4
Post 3:
- Repacking
Will be added soon:
- Kernels reviews
Huuuuge guide
matt95 said:
Huuuuge guide
Click to expand...
Click to collapse
Just wanted to be a complete guide. Explaining everything.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Just wanted to be a complete guide. Explaining everything.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
You succeeded in it
matt95 said:
You succeeded in it
Click to expand...
Click to collapse
Thanks. Glad I could contribute to the community. :good:
Sent from my GT-N8000 using Tapatalk HD
csec said:
Audio Min. Freq.:
This specify the minimum frequency of the CPU when Audio is being processed. Default min in custom kernels is normally 51MHz. But Audio needs some more processing power. Anyhow, with this you can change that value.
Click to expand...
Click to collapse
Thanks for the guide.
I'm using CyanogenMod right now and I'm having problems with Audio over Bluetooth with the low power core of my endeavoru. I think increasing this frequency might help.
How is this called in kernel-land a.k.a. how do I find instructions regarding this? Asking Master Google was of no help, as I only found custom variants of the CyanogenMod kernel.
lordtillt said:
Thanks for the guide.
I'm using CyanogenMod right now and I'm having problems with Audio over Bluetooth with the low power core of my endeavoru. I think increasing this frequency might help.
How is this called in kernel-land a.k.a. how do I find instructions regarding this? Asking Master Google was of no help, as I only found custom variants of the CyanogenMod kernel.
Click to expand...
Click to collapse
What is your kernel and version?
What governor, what frequency?
What kind of problem are you having with your audio?
csec said:
What is your kernel and version?
What governor, what frequency?
What kind of problem are you having with your audio?
Click to expand...
Click to collapse
I'm running CyanogenMod 10.1 RC2 with the default kernel, which is the 3.1.10-cyanogenmod+inky-ghost kernel, according to About Phone.
Governor is ondemand, and the frequency is untouched - meaning, CyanogenMods defaults (51<f<1500).
The audio sometimes stutters, when I'm using my bluetooth headphones and the screen is locked - I assume, that's due to the low power kernel of the tegra chipset.
Can you help finding that setting, or recommend a good replacement kernel?

Battery/RAM/Speed Optimization Tips for Android Phones

I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THESE TIPS.
I've created a couple threads on the ZTE U950 and LG G2, and one problem is the battery life. The battery cannot come out of these devices and thus we cannot combat this with a bulkier, beefier replacement for heavy usage. Charging constantly is something I try to avoid, so these are a few simple tips that can help optimize your battery life (and that APPLY to ANY PHONE):
TIPS
BATTERY
1a) Buy and download CPU Sleeper (root required). There are two versions, one for dual-cores, and the other for quad-cores. Essentially, when a phone is "sleeping", it is actually still running all its cores, helping drain battery faster. This app turns off all but one core when it is "sleeping" so that your battery is not drained nearly as fast.
BATTERY
1b) To take this step a bit further you can download a free app called Multicore CPU Control. In this app you can control your other cores. You can setup profiles to turn on or off cores, and setup each core with different governors. On my LG G2, I setup a profile to only have one core running at 960MHz (2.2GHz originally) after using the steps from below. If you plan to only run one core, then you do not need to buy CPU Sleeper.
NOTES ON 1b: Multicore CPU Control is the name when installed, it is called CPU Performance Control Free on the Google Play Store (either name will work on Google Play). The program needs to be turned on after each boot. When first setting up a profile save it and edit it in order to manipulate the other cores available. The app does not always apply a profile even if it has already been selected. To turn on a profile, click on the profile desired and go to the CPU Monitor tab to check if it has been applied. If not, repeat the process until it does (it usually takes me about 3 times at most).
BATTERY/RAM
2) Download Greenify (root required), a great free app! Sometimes a user does not have a ROM with a kill all button, so pesky apps just stay on without consent. This app allows a user to turn off any app that may want to run in your background, and even shows you which apps are currently running. Apps like Facebook, Talkatone, etc. can all be stopped even if your "task killer" supposedly took care of them.
BATTERY
3a) Wakelock Detector-Save Battery is a free app that checks for apps that continue to work while the phone is "asleep". While Greenify will display the most troublesome apps, this app will help discover any other apps that are running without consent.
BATTERY/RAM
3b) If Greenify does not show the apps discovered in Wakelock Detector-Save Battery, then download Disable Services (root required). This free app allows a user to disable an entire service, or just parts of a service that are bothersome. Click on a service/app to find out what other services accompany it. Read the accompanying services and discern whether or not the service is needed. A good place to start in this app is to check any service/app that has a blue number next to it.
EXAMPLE 3b: I use the Outlook app a lot, but sometimes it gets annoying with updates for insignificant email. I can open Wakelock Detector-Save Battery and click the Outlook app. I turn off "AppWidgetUpdateService" to disable Outlook email updates. Not all services have obvious names, so be careful on system apps if performing trial-and-error.
BATTERY/RAM
3) Buy and download BetterBatteryStats (CPU Spy Reborn/Plus is FREE and only shows CPU states). This app tells me what CPU States are used the most often and is what I download first before my next step. A user can also determine battery-draining apps and turn those off. If turning off those apps is not possible through Settings>Apps just Greenify them!
BATTERY
4) Underclocking. This is an amazing step for saving battery! If you have ran BetterBatteryStats for at least a day, this will come in handy and is highly recommended. You can use numerous programs like SetCPU or Voltage Control to set the clock of the CPU. The key is to find a point that will still be responsive, yet lower than the maximum.
EXAMPLE 4: For this example I will be using my ZTE U950 and Voltage Control. According to BetterBatteryStats, my most used clock was at 1.2GHz and 860MHz. I left my minimum clock at the lowest possible setting, while my maximum clock I changed to 860MHz. I ran this for a few days and saw a noticeable difference in battery life. Another important part to this if choosing the right I/O Scheduler and CPU Governor. I found the default I/O Schedule ("cfq") to perform the best, despite "noop" being good for sluggish memory. "Powersave" is a good Governor at stock CPU speeds, but it will not get a user the savings of power that a step like this will. I tested with this Governor with this step and got horrible reaction times and would often need to restart the phone. The best results I have are with "ondemand" and "interactive". I am currently using "interactive" with a maximum clock of 475MHz! I arrived at that number after checking my BetterBatteryStats while running at 860MHz and found that to be the next most used clock. Now my battery is lasting about twice as long as it normally did! My phone's response time is a bit slower at this low clock speed, but that can combated...
BATTERY/RAM/SPEED
4b) (IF YOU HAVE INIT.D SKIP TO STEP 4c) My LG G2 is underclocked to 960MHz, as noted in step 1b. I am saving quite a bit of battery, but the UI response can lag a lot at times. The use of boot scripts can be helpful to compensate for this. However, my LG G2 does not have init.d support. There are numerous threads that explain how to get init.d support for a lacking Android phone. The simplest method is to install an app from Google Play. I use one called Init.d-Installer just because it forces the phone to reboot once it has installed; others do not seem to do anything to inform a user if they have received init.d support
BATTERY/RAM/SPEED
4c) Download a script called V6 SuperCharger. The thread may seem daunting, but it is fairly easy to install. Download the newest PDF and change it to TXT. Ensure you have init.d support, BusyBox installed (also in the thread if needed), and SuperSU. Run the script in a free app like SManager with SU permissions and follow the instructions. This script gives the ability to enhance speed and power. I install this in order to ensure my UI stays responsive, and LG G2 runs almost at stock speeds (alongside all my other enhancements)!
BATTERY
5) Undervolting (root required/custom kernel required). This is also a great way to save battery. I decrease the voltage in steps of 25 and test from there. If I find no quirks, I leave it. If I find sluggishness or have random phone reboots, I increase by increments of 25 (or 12.5) until I find something stable.
Most phones will not allow undervolting without a custom kernel. To see whether a phone can undervolt or not download, Sytem Tuner. There is a free and paid (Pro) version of this app, but the free one should be sufficient for what we want to do. After installing, open the app and click on the Voltage settings tile on the left-lower side of the screen. All the phone's CPU MHz steps and the amount of voltage applied to each step can be viewed. At the bottom of the screen are buttons to increase or decrease voltage in 12.5 increments (which will apply to all steps). If the -12.5 button is clicked and the values of all the steps drop, then a phone can undervolt. Additionally, System Tuner allows a phone to manually apply undervolting to each step if wanted.
To test undervolting, just push the decrease button until the phone freezes up. There is no harm to your phone or CPU as neither are being overpowered (just the opposite), and a reboot after freezing will reset the phone to default voltage settings. A - 75MHz drop is normal for a phone while remaining stable; and in a lot of cases -100MHz is achievable.
NOTE: Tips #4 & #5 also can be applied to GPUs.
NOTE 2: One thing that should be mentioned is to be careful about putting more than one app that controls CPU clocks. They can read differently and trump the other when used in combination. Instead, install and use one at a time to get more accurate readings. The same should apply to undervolting apps.
BATTERY/RAM
6) A user can change the Dalvik cache a bit to see if that helps optimize RAM, and possibly battery. I did quite a few tests for these to see how they performed. I think the only reason I noticed any changes immediately is because of how far underclocked my CPU is. Anyways, the best results I was able to get with my ZTE U950 was as follows:
124m - dalvik.vm.heapsize (2nd one, not 1st)
8m - dalvik.vm.heapstartsize
For other phones, these are the items to trial-and-error with:
davilk.vm.heapsize (may be more than one at different values)
davilk.vm.heapstartsize
davilk.vm.heapgrowthlimit (may be more than one at different values)
A user can change these settings by downloading an app like Build.Prop from Google Play. I did notice my battery seemed to drain slower with these changed. The RAM was the best optimized for the self-made tests I performed and was nearly the best in all the tests I had ran. A user may or may not notice any differences unless they multitask a lot.
BATTERY/RAM/SPEED
7) All other well-known methods apply as well:
A. Battery Saver apps/settings
B. Battery Calibration apps
C. Refrain from the use of widgets
D. Automatic Brightness apps/settings
E. Small Screen Times before Screen Sleep
F. Turn Off WiFi and/or Data when not needed
G. Task Killers apps/settings

[Mod/Fix] [No Root] Control Overheating and Performance with Thermal Engine

Hi Everybody,
After v45 update, we all are facing huge drop in performance in our Redmi 1s.
One of my dear provided one patch by modifing some system files.
But that patch will yes revert back the performance BUT IT WILL ALSO BRING BACK THE OVERHEATING ISSUE.
So i am presenting you all with this patch.
It will restore your performance and also will control overheating.
NOTE: THIS MOD ONLY CONTROLS MAX CPU+GPU FREQUENCIES AT HIGHER BATTERY TEMPS. SO IT WONT HARM BATTERY PERFORMANCE AT ALL.
How to do:
NO ROOT IS NEEDED NOW.
JUST FLASH ZIPS EVEN THROUGH STOCK RECOVERY.
How to undo:
Just flash undo zip.
Download:
Updated in attachments as recovery flashable zips.
NOW IT CAN BE FLASHED THROUGH STOCK MIUI RECOVERY.
What have i done:
(1) somebody ask me to remove some of the line from the file but if we remove them our redmi will start overheating as it wont control the cpu.
So i have not removed them but i have set them to frequencies which will neither make phone overheat nor will hang it.
(2) file is patched with little help from my nexus.
(3) in the v45 update the cpu was limited to use less than 1ghz. It hangs the phone. So i changed it.
Now reboot and you device will go easy.
Please comment if you find any issue or suggestions.
A thanks will motivate me.
Also if you want to use my mod in any rom then plz give credits.
Credits:
Ryuinferno : for the wonderful script to sign zip files.
Notepad++
My Nexus
Update (17-11-14)
1. Removed density data from patch. Now only used cpu and gpu to control it.
2. Uploaded Hard Gaming, Power saving and Balanced patch for specific usage.
3. Cleaned and power saving based on original parameters.
What have i done :
Lets have a close look at the original \system\etc\thermal-engine-8226.conf file:
algo_type monitor
sensor batt_temp
sampling 1000
thresholds 380 390 420 500 550
thresholds_clr 370 380 400 450 500
actions cpu+hotplug_2+hotplug_3 cpu+hotplug_3 cpu+hotplug_3 cpu cpu
action_info 998400+1+0 998400+1 787200+1 600000 600000
In above lines, the sensor is batt_temp so here battery temperature is observed.
When the temperature of bettery reaches 380 (i.e. 38*C) then cpu+hotplug_2+hotplug_3 will be performed. Means cpu will clock at 998400 mhz and core2 will be hotpluged. Here your device will start hanging as 1.6 ghz cpu is asked to run at only 0.998 ghz with core2 hotpluged.
Similarly, at 390 (i.e. 39*C) core3 will also hotpluged.
35*C is normal temperature. But you will reach around 39-40*C even at light internet browsing/gaming.
At 42*C your cpu will die with only 0.787 ghz speed. This is less than half of 1.6 ghz.
Now what have i done is i have pushed the limits to little high level.
I have stopped hotplugging of cores and to low down the temp. i have used cpu & gpu both.
algo_type monitor
sensor batt_temp
sampling 1000
thresholds 390 410 420 450 550
thresholds_clr 380 400 410 440 500
actions cpu+gpu cpu+gpu cpu+gpu cpu+gpu cpu+gpu
action_info 1344000+450000000 1344000+320000000 1190400+320000000 787200+200000000 600000+200000000
Here at 39*C the cpu will go to 1.34 ghz but the gpu will remain at max of 450 mhz.
Then at 41*C the cpu will remain at 1.34 ghz but gpu will lower down to 320 mhz.
Likewise, at 420*C the cpu will go to 1.19 ghz and gpu will remain the same.
Above 45*C is too hot so the device is really needed to cool down. So above 45*C both cpu and gpu will lower down a lot for enough cooling.
Again when the temperature with lower down, you will start getting the normal speeds.
All the above information is also observed closely with the help of cpu-z apk.
is it really works ??????
why you didn't just simply configure the ondemand governor to do the same thing? Is more easy and can be done manually or using Trickster mod.
Thanks a ton for the patch but flashable zip file be a lot easier to install. So please make a flashable zip.
pgreed said:
why you didn't just simply configure the ondemand governor to do the same thing? Is more easy and can be done manually or using Trickster mod.
Click to expand...
Click to collapse
Ya but as per me if we have limited something in the thermal config file to behave at a specific battery temp. then we can not use any app or mod to change the cpu frequencies.. I have tried that also..
Also this mod controls cpu+gpu+dencity at specific battery temps...
sumitsrk123 said:
is it really works ??????
Click to expand...
Click to collapse
I also had same questions so me and my friend have tested it with the help of cpu-z app...
Cpu-z app gives you details of your battery temp. and your current cpu clock speeds. Set governor to performance and start playing games like need for speed... Then in between checked the temp of the battery and the cpu clock speed ...
It really works it changes the frequencies as per specific temps...
coolpepe said:
Thanks a ton for the patch but flashable zip file be a lot easier to install. So please make a flashable zip.
Click to expand...
Click to collapse
Yo bro... Signed flashable zips are up... Also added undo zip to revert to stock.
This is what i am using ...
I prefer little more performance over heating...
Nice....now i can use the phone @1.6Ghz without heating !!
Beast Mode Unlocked
Thanks Man for this
In a sense. But you cannot run your cpu at 1.6ghz continuously for a very long time.. Every cpu will get overheat.
Here i have tried to make some balance between the performance and heat.
What miui did.. They just tried to limit us to use at 0.99 ghz when temp is above 38.c so i have pushed that limit to high level with help of other factors like gpu and density etc.
So simple you will not be limited if you go at a high limit of temp.. After that slowly slowly cpu gpu and density will be limited and cpu will cool down...
ravinder0003 said:
In a sense. But you cannot run your cpu at 1.6ghz continuously for a very long time.. Every cpu will get overheat.
Here i have tried to make some balance between the performance and heat.
What miui did.. They just tried to limit us to use at 0.99 ghz when temp is above 38.c so i have pushed that limit to high level with help of other factors like gpu and density etc.
So simple you will not be limited if you go at a high limit of temp.. After that slowly slowly cpu gpu and density will be limited and cpu will cool down...
Click to expand...
Click to collapse
What i meant was this is smarted thermal control and i won't be having to manually underclock any more to prevent heating !
Also i can help my friends who are not aware of rooting and stuffs
No you dont need to do anything... this is balanced version..
If you prefer more power or more battery just tell me i will edit it for you according to ur needs..
ravinder0003 said:
No you dont need to do anything... this is balanced version..
If you prefer more power or more battery just tell me i will edit it for you according to ur needs..
Click to expand...
Click to collapse
Can you make it more reliable for hard gaming & multitasking??? Mod is working perfectly and really increased my battery backup and performance, No heat anymore. Thanks bro keep it up.:beer::thumbup:
Sent from my HM 1SW using XDA Premium 4 mobile app
ravinder0003 said:
Hi Everybody,
After v45 update, we all are facing huge drop in performance in our Redmi 1s.
One of my dear provided one patch by modifing some system files.
But that patch will yes revert back the performance BUT IT WILL ALSO BRING BACK THE OVERHEATING ISSUE.
So i am presenting you all with this patch.
It will restore your performance and also will control overheating.
How to do:
NO ROOT IS NEEDED NOW.
JUST FLASH ZIPS EVEN THROUGH STOCK RECOVERY.
How to undo:
Just flash undo zip.
Download:
Updated in attachments as recovery flashable zips.
NOW IT CAN BE FLASHED THROUGH STOCK MIUI RECOVERY.
What have i done:
(1) somebody ask me to remove some of the line from the file but if we remove them our redmi will start overheating as it wont control the cpu.
So i have not removed them but i have set them to frequencies which will neither make phone overheat nor will hang it.
(2) file is patched with little help from my nexus.
(3) in the v45 update the cpu was limited to use less than 1ghz. It hangs the phone. So i changed it.
Now reboot and you device will go easy.
Please comment if you find any issue or suggestions.
A thanks will motivate me.
Also if you want to use my mod in any rom then plz give credits.
Credits:
Ryuinferno : for the wonderful script to sign zip files.
Notepad++
My Nexus
Click to expand...
Click to collapse
HI Ravindar,
Thanks for your post it is helpful.
I tried it. Given better improvement.
Ram performance better
No heating
But
Battery life poor
Can u rectify
Please
What to do to RAM management with thermal control guys??
It have nothing to do with ram dear its totally cpu+gpu+density hack...
Also, this hack comes into action when you overuse your cpu and it starts heating... But at normal usage it only improves your performance at no extra battery cost...
Simple there is no use of having 1.6 ghz if you are limited to use only 0.988 ghz over 38 degrees... I have extended this limit only... As this limit is manadatory for cooling process...
For hard gaming !!! Will be uploading in some minutes...
Thanks for request...
For hard gaming !!! Will be uploading in some minutes...
Thanks for request...
Mod for hard gaming is up... Plz check the op or attachment...

Some technical help needed in Mokee Lolipop Nightly Version

Dear Friends,
I am using Mokee Lolipop Nightly version in my Redmi 1S.
I need help for the following points :
1) In MKL when i try to disable mpdecision via ADB, nothing is happening and not even by external app like No Frills cpu control I'm able to control max frequency of my cpu.
It is constantly showing 998 MHz only. Earlier in mokee kitkat i was using no frills cpu control and it was working very fine. But not working in lolipop as expected. How to solve that.
2) I have seen in previews and videos that mokee lolipop is having inbuilt super user. But i am unable to see it in my setting menu.
However i am able to get root access via "Privacy Guard" setting in lolipop and that is working well. Comment on that.
Kindly answer me and increase my knowledge on this.
sssaurabh said:
Dear Friends,
I am using Mokee Lolipop Nightly version in my Redmi 1S.
I need help for the following points :
1) In MKL when i try to disable mpdecision via ADB, nothing is happening and not even by external app like No Frills cpu control I'm able to control max frequency of my cpu.
It is constantly showing 998 MHz only. Earlier in mokee kitkat i was using no frills cpu control and it was working very fine. But not working in lolipop as expected. How to solve that.
2) I have seen in previews and videos that mokee lolipop is having inbuilt super user. But i am unable to see it in my setting menu.
However i am able to get root access via "Privacy Guard" setting in lolipop and that is working well. Comment on that.
Kindly answer me and increase my knowledge on this.
Click to expand...
Click to collapse
Use the Release version.
I think it is a thermal script which doesn't allow to do so.
I have noticed that when I have enabled performance option in battery settings(by default it is balanced) I can change the max CPU to 1.6 GHz
However if it is in performance mode but if my CPU temperature is high I cannot change it until the phone cools down.
So I guess if you keep it in performance mode it will automatically set cpu according to your phone's temperature.
Hmm....... May be thermal throttling is responsible

mpdecision for mi max helium

It is reportedly not working on the hydrogen model
Dear Friends i saw online one mod which will be of benefit to all of
Mpdecision is watching the load on your device! When you´re only doing simple stuff like browsing, texting or listening to music, the mpdecision service will completely shutdown single cpu cores to reduce power consumption. When you start games or other heavy processes, mpdecision will bring back online all your cores!
You can download Apps like CPU-Z to monitor your CPU Core Status! With mpdecision Service enabled, you can see that some of the CPU Cores go on- and offline. Without mpdecision all Cores are allways online.
It has been developed by the developers at mi-globe com and you can download the mod there
http://mi-globe.com/index.php/2016/...-mpdecision-for-all-xiaomi-snapdragon-phones/
I am using it on my helium and it is working.
seking said:
Dear Friends i saw online one mod which will be of benefit to all of
Mpdecision is watching the load on your device! When you´re only doing simple stuff like browsing, texting or listening to music, the mpdecision service will completely shutdown single cpu cores to reduce power consumption. When you start games or other heavy processes, mpdecision will bring back online all your cores!
You can download Apps like CPU-Z to monitor your CPU Core Status! With mpdecision Service enabled, you can see that some of the CPU Cores go on- and offline. Without mpdecision all Cores are allways online.
It has been developed by the developers at mi-globe com and you can download the mod there
http://mi-globe.com/index.php/2016/...-mpdecision-for-all-xiaomi-snapdragon-phones/
I am using it on my helium and it is working.
Click to expand...
Click to collapse
Thank you !
Sent from my MI MAX using Tapatalk
seking said:
Dear Friends i saw online one mod which will be of benefit to all of
Mpdecision is watching the load on your device! When you´re only doing simple stuff like browsing, texting or listening to music, the mpdecision service will completely shutdown single cpu cores to reduce power consumption. When you start games or other heavy processes, mpdecision will bring back online all your cores!
You can download Apps like CPU-Z to monitor your CPU Core Status! With mpdecision Service enabled, you can see that some of the CPU Cores go on- and offline. Without mpdecision all Cores are allways online.
It has been developed by the developers at mi-globe com and you can download the mod there
http://mi-globe.com/index.php/2016/...-mpdecision-for-all-xiaomi-snapdragon-phones/
I am using it on my helium and it is working.
Click to expand...
Click to collapse
Can i know are you using GlobeRom for it to work and the same Rom version....does flash this will change anything with the rom...
That I am not sure. I am using the Globe rom and it is inbuilt mod in that rom. I dont know if you flash this mod on other roms. May be you can contact the developers.
Hmm.never heard of this ROM. Is it any good? Like what do they mean by battery tweaks..the info is a little vague...
netusername said:
Hmm.never heard of this ROM. Is it any good? Like what do they mean by battery tweaks..the info is a little vague...
Click to expand...
Click to collapse
If you go the link i have given you will be clear
On a cleanly installed globeROM Helium with nothing else on it except cpu-z, after several minutes, the governor changes suddenly to performance mode and sets all online cores to the highest clock speed and sometimes stays there for good even after several reboots. It shuts down some cores but the over-all cpu load becomes so high that it drains the battery so fast and heats up the phone a little while even idle. If the governor changes to performance mode, the govtuner mod becomes useless and incompatible and can never be run unless governor goes back to interactive mode. I use Kernel Adiutor to control cpu problems a little but I have to check once in a while because it still happens and I have to manually set governor back to interactive mode again through Kernel Adiutor. So it is useless for now. I hope they fix it as mpdecision is dong wonders on other snapdragon 650-652 phones like the Samsung A9 Pro.
seking said:
Dear Friends i saw online one mod which will be of benefit to all of
Mpdecision is watching the load on your device! When you´re only doing simple stuff like browsing, texting or listening to music, the mpdecision service will completely shutdown single cpu cores to reduce power consumption. When you start games or other heavy processes, mpdecision will bring back online all your cores!
You can download Apps like CPU-Z to monitor your CPU Core Status! With mpdecision Service enabled, you can see that some of the CPU Cores go on- and offline. Without mpdecision all Cores are allways online.
It has been developed by the developers at mi-globe com and you can download the mod there
http://mi-globe.com/index.php/2016/...-mpdecision-for-all-xiaomi-snapdragon-phones/
I am using it on my helium and it is working.
Click to expand...
Click to collapse
Not Working on hydrogen ROM:- xiaomi.EU 6.11.17
Help me
See the screenshots
I am attaching some screen shots. Obviously it is working as two cores stopped. As soon as I wake up the device I could see for a brief second all cores stopped and they start as the device is woken up.
aaryan45 said:
Not Working on hydrogen ROM:- xiaomi.EU 6.11.17
Help me
Click to expand...
Click to collapse
confirmed on GlobeROM web that mpdecision is not supported on Hydrogen. Maybe OP can edit the title to avoid confusion and error
alf0 said:
confirmed on GlobeROM web that mpdecision is not supported on Hydrogen. Maybe OP can edit the title to avoid confusion and error
Click to expand...
Click to collapse
So Now?
Guys, I tried it on my helium, but didn't work. If you would turn off 2 cores, you can download ex kernel manager and tap on "esacore mode"
Davide__97 said:
Guys, I tried it on my helium, but didn't work. If you would turn off 2 cores, you can download ex kernel manager and tap on "esacore mode"
Click to expand...
Click to collapse
Click Option on left menu -> CPU -> choose Hexacore mode (Disable CPU6 and CPU7).
That's it!

Categories

Resources