Develop Bugs

Temperature hacks on the Tab (battery, and the other sensor)

First of all, I needed SetCPU to detect the battery temperature on my overclocked Galaxy Tab (to switch profile when overheating), so I modified my home-brewed kernel with this small patch:
http://forum.xda-developers.com/showthread.php?p=11454036#post11454036
This is fine, but on my JMI ROM (even with the correct /system/lib/hw/sensors.default.so library), applications like "SensorTest" were not displaying the temperature from the AK8973B sensor. I found a way to fix this.
Basically, I compiled this open-source driver (or alternatively, this one), which provides a custom sensors.default.so library and akmd service executable. The former is actually not needed, only the latter needs to be run on the Tab (because the standard /dev/akm8973_daemon device node is used, via ioctl to update the /dev/input values for compass, etc.).
First, I stopped the default /system/bin/akmd2 service. I then launched the custom akm daemon, which showed wrongly-calibrated values for the compass and orientation sensors (because I entered random digital and analog gain values), but the correct temperature was displayed (actually higher than the battery one !). I then stopped akmd, and re-launched akmd2...and magic: the temperature is now picked-up correctly !
Note that the gyroscope and accelerometer sensors are *not* affected these AKM modifications (they are effectively different hardware, with different drivers). The ambient light and proximity sensors are also different hardware (the latter isn't enabled on the Tab, by the way...I suspect we need to compile/install a driver for it).
I will do more testing with akmd and akmd2, and I will probably modify my init.rc to launch the service accordingly (in my custom initramfs).
I hope this helps.
Cheers, Dan
--- EDIT ---
Mhmmm, here's an interesting update:
There is no need to compile the open-source AKM daemon ! Instead, you just need to kill the /system/bin/akmd2 process, and restart it.
Well, actually it's not that simple: it only really works when the temperature sensor is polled (for example, when the SensorTest or Elixir app is displaying current values). Oh, and the temperature sensor only spits-out results when the compass sensor is also polled at the same time ! (Elixir is useful to test this, because sensors can be selectively activated)
I tried to reverse-engineer the values coming out of /dev/input/event4 (which corresponds to the compass sensor, as shown by the getevent command). I used shell commands similar to that (note the automatic conversion from hexadecimal to decimal values):
Code:
getevent | grep "/dev/input/event4:" | sed 's/ffffff//g' | awk '{print $2 " " $3 " " ("0x"$4)+0 ">" $4}'
Unfortunately my time ran out before I could make sense out the stream of values.
By the way, here is the script I used to stop+restart the AKM daemon in init.d/ :
Code:
get_akmd_pid()
{
ps -w | grep akmd2 | grep -v grep | awk '{print $1}'
}
pid=`get_akmd_pid`
echo "Killing /system/bin/akmd2 (PID: ${pid}) ..."
kill -9 $pid
pid=`get_akmd_pid`
echo "Checking that /system/bin/akmd2 process has been terminated: now PID = [${pid}] (should be empty)"
echo "Restarting /system/bin/akmd2..."
/system/bin/akmd2 &
pid=`get_akmd_pid`
echo "Checking that /system/bin/akmd2 process has been restarted: now PID = [${pid}] (should NOT be empty)"

What temperature do you consider too hot on your tab? I currently have my set to underclock from 1.4 ghz to 800 mhz whenever it reaches 90 degrees Fahrenheit (I am a worry-wart), but it reaches that a lot, so I was wondering what you have the maximum temperature set to before you bring the clock speed down.
Thanks

caveman999 said:
What temperature do you consider too hot on your tab?
Click to expand...
Click to collapse
I'm not sure yet. The battery temperature is lower than the one indicated by the AK8973 sensor. As it stands, SetCPU switches profiles based on the battery temperature, so personally I use conservative values (at the moment, 35 degrees Celcius).
By the way, the original post has been updated to reflect new findings.
Cheers, Daniel

my temp sensor is stuck at 30 c after flashing a kernel how do i get it to work. what you posted did not work. im actually stuck in a boot loop

nev310 said:
my temp sensor is stuck at 30 c after flashing a kernel how do i get it to work. what you posted did not work. im actually stuck in a boot loop
Click to expand...
Click to collapse
Same here, stuck on 30 degrees C. Any fix would be appreciated.

Any updates on this

PesasusQ governor here

Hi everyone,
i'm not quite sure about governor information , it's for this cause i'm asking here
My main answer is:
Is really pegasusQ governor the better multi-core governor?
start from begin.
pegasusQ is a ondemand governor which also controls hotplugging of cores.
i know, every core has run queue with different thread, but for now our 2core work in synchronous core speed, when core0 ( first core ) is underload tells cpudriver to raise cpufreq ( both core ) , also core1 ( second core ) get high clock that it need.
if i'm not wrong,
pegasusQ work in a-synchronous mode, each core has different clock, if core0 is underload, governor will increase only core0 clock and not core1
can be better this for battery and lag-kill right?
Gokhanmoral modified pegasusq (originally authored by Samsung for quad core devices) in Siyah kernel to be dual core friendly, with good results ( he make default governor in his kernel ) ,
why we dont have a kernel ( or famous kernel like franco, fugu,air, trinity or same ) doesn't include this?
with this value ( mixed driodphile relaxed settings and franco ondemand settings ) can we get a better battery and better speed?
Code:
echo "98" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold_at_min_freq
echo "30000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
echo "5" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
echo "4" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_step
echo "384000" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_for_responsiveness
echo "15" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "15" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "729000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "384000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "350" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "200" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/ignore_nice_load
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/io_is_busy
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/max_cpu_lock
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
thanks for answer and i hope to myself understand of this governor, thanks

Hope some one can explain >_< Curious to know :good:

[SCRIPT] [v3.3] G3 SPEED [APP] [v2.3] VELOCITY 1/3/15

TWO MODS ARE LISTED IN THIS OP. ONE SCRIPT AND ONE APP. PLEASE STATE WHICH ONE YOU ARE REFERRING TO WHEN RESPONDING TO THIS THREAD!
THESE MODS WORK ON MOST ROOTED LG G3 ROMS.
TESTED ONLY ON D851. (I CAN'T TEST EVERY CARRIER SO LET US ALL KNOW IF IT WORKS FOR YOU)
USE THIS AT YOUR OWN RISK!
SPECIAL THANKS TO...
@KingOfDope - For providing us with an awesome icon and UI design for Velocity
*THE SCRIPT*
G3 SPEED SCRIPT VERSION 3.3
This script is strictly designed for the G3 and will give you a decent boost in performance without any gimmicks. This can also be used with other basic scripts in the general section of XDA without issues.
Script may be heavy on battery usage.
THE G3 SPEED SCRIPT
#razz1
#G3SPEEDV3.3
echo 1024 > /sys/class/bdi/0:19/read_ahead_kb
echo 1024 > /sys/class/bdi/0:21/read_ahead_kb
echo 1024 > /sys/class/bdi/179:0/read_ahead_kb
echo 1024 > /sys/class/bdi/179:32/read_ahead_kb
echo 1024 > /sys/class/bdi/1:0/read_ahead_kb
echo 1024 > /sys/class/bdi/1:1/read_ahead_kb
echo 1024 > /sys/class/bdi/1:10/read_ahead_kb
echo 1024 > /sys/class/bdi/1:11/read_ahead_kb
echo 1024 > /sys/class/bdi/1:12/read_ahead_kb
echo 1024 > /sys/class/bdi/1:13/read_ahead_kb
echo 1024 > /sys/class/bdi/1:14/read_ahead_kb
echo 1024 > /sys/class/bdi/1:15/read_ahead_kb
echo 1024 > /sys/class/bdi/1:2/read_ahead_kb
echo 1024 > /sys/class/bdi/1:3/read_ahead_kb
echo 1024 > /sys/class/bdi/1:4/read_ahead_kb
echo 1024 > /sys/class/bdi/1:5/read_ahead_kb
echo 1024 > /sys/class/bdi/1:6/read_ahead_kb
echo 1024 > /sys/class/bdi/1:7/read_ahead_kb
echo 1024 > /sys/class/bdi/1:8/read_ahead_kb
echo 1024 > /sys/class/bdi/1:9/read_ahead_kb
echo 1024 > /sys/cl30s/bdi/253:0/read_ahead_kb
echo 1024 > /sys/class/bdi/254:0/read_ahead_kb
echo 1024 > /sys/class/bdi/254:1/read_ahead_kb
echo 1024 > /sys/class/bdi/254:2/read_ahead_kb
echo 1024 > /sys/class/bdi/254:3/read_ahead_kb
echo 1024 > /sys/class/bdi/254:4/read_ahead_kb
echo 1024 > /sys/class/bdi/254:5/read_ahead_kb
echo 1024 > /sys/class/bdi/254:6/read_ahead_kb
echo 1024 > /sys/class/bdi/254:7/read_ahead_kb
echo 1024 > /sys/class/bdi/7:0/read_ahead_kb
echo 1024 > /sys/class/bdi/7:1/read_ahead_kb
echo 1024 > /sys/class/bdi/7:2/read_ahead_kb
echo 1024 > /sys/class/bdi/7:3/read_ahead_kb
echo 1024 > /sys/class/bdi/7:4/read_ahead_kb
echo 1024 > /sys/class/bdi/7:5/read_ahead_kb
echo 1024 > /sys/class/bdi/7:6/read_ahead_kb
echo 1024 > /sys/class/bdi/7:7/read_ahead_kb
echo 1024 > /sys/class/bdi/default/read_ahead_kb
echo 0 > /sys/module/smem_log/parameters/log_enable
echo 0 > /d/mmc0/clk_delay
echo 0 > /d/mmc1/clk_delay
echo 0 > /d/mmc2/clk_delay
echo 5 > /sys/class/mmc_host/mmc0/clk_scaling/up_threshold
echo 75 > /sys/class/mmc_host/mmc0/clk_scaling/down_threshold
echo 5 > /sys/class/mmc_host/mmc1/clk_scaling/up_threshold
echo 75 > /sys/class/mmc_host/mmc1/clk_scaling/up_threshold
echo 5 > /sys/class/mmc_host/mmc2/clk_scaling/up_threshold
echo 75 > /sys/class/mmc_host/mmc2/clk_scaling/down_threshold
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/log_level_cmd
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/log_level_ctxt
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/log_level_drv
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/log_level_mem
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/log_level_pwr
echo performance > /sys/class/devfreq/qcom,cpubw.41/governor
echo 10000000 > /sys/class/kgsl/kgsl-3d0/idle_timer
echo 10000 > /sys/class/firmware/timeout
setprop debug.egl.hw 1
setprop debug.performance.tuning 1
setprop debug.egl.profiler 1
setprop debug.gr.swapinterval 0
setprop dev.pm.dyn_samplingrate 1
setprop dev.pm.gpu_samplingrate 2
setprop dev.pm.c2d_samplingrate 2
setprop dev.pm.mdp_samplingrate 2
setprop logcat.live disable
setprop persist.sys.use_dithering 0
setprop profiler.force_disable_err_rpt 1
setprop profiler.force_disable_ulog 1
fstrim -v /data
fstrim -v /cache
fstrim -v /system
RUN/INSTALL THIS SCRIPT.
1. Make sure you have your ROM backed up!
2. Download G3 SPEED zip and flash in recovery.
3. Reboot
REMOVE THIS SCRIPT.
1. Download G3 SPEED UNINSTALL zip and flash in recovery.
The uninstaller will also replace those files that were originally deleted by early versions of G3 SPEED.
DOWNLOADS FOR G3 SPEED SCRIPT.
Version 3.3
http://d-h.st/kLQ
Mirror
https://www.androidfilehost.com/?fid=95916177934540403
Uninstall
http://d-h.st/D7p
Mirror
https://www.androidfilehost.com/?fid=95916177934540404
Version 3.2.1
http://d-h.st/50g
Version 3.1
http://d-h.st/vT6
Version 3
http://d-h.st/orX
Version 2
http://d-h.st/oyi
*THE APP*
VELOCITY APPLICATION!
THIS APP MAY HAVE THE POTENTIAL TO CAUSE DAMAGE TO YOUR DEVICE.
YOU'VE BEEN WARNED!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PERFORMANCE- Realtime screenshot of Velocity being used on the Quadrant benchmark application.
I labeled this originally as a "graphics" app but in further research it does much more than that. It will speed up your entire system a considerable amount.
This is a completely seperate MOD from the script above and may be used in conjunction with that script or any other script.
Expect much higher framerates, smoother graphics and higher overall system performance.
Essentially you are overclocking your device with this app.
Use it CAREFULLY! Choose wisely!
THINGS TO KNOW.
This does NOT overclock your CPU or GPU. It adjusts multiple internal clock settings in your device. These clock settings will be raised by this application and could cause instability and "Blue Screens"
HOW VELOCITY OPERATES.
When you set "on boot" Velocity will save your values. When you reboot your phone it will restore your values after 10 seconds has elapsed.
If you open the app before those said times have elapsed, all values are at default and the app will say "standby". After the time has elapsed Velocity will restore your previous values and now show these values instead of "standby".
REQUIREMENTS FOR VELOCITY
- Latest version of SuperSU.
-"Mount namespace separation" must be enabled in SuperSU.
VELOCITY APPLICATION DOWNLOAD.
VERSION 2.3 - ALL ROMS
http://d-h.st/H8WL
Mirror
https://www.androidfilehost.com/?fid=95916177934537668
VELOCITY v2.1 - ALL ROMS
http://d-h.st/Jn5
VELOCITY v2.0 OFFICIAL RELEASE.
STOCK BASED 4.4.2 ROMS
http://d-h.st/2zO
AOSP/CM BASED 5.0L ROMS
http://d-h.st/mGJR
Beta v1.5
http://d-h.st/Fyv
Beta v1.4
FUBAR
Beta v1.3
http://d-h.st/1pO
Beta v1.2
http://d-h.st/Cq6i
Beta v1.1
http://d-h.st/yuK
Beta v1.0
http://d-h.st/mag
CHANGELOG FOR VELOCITY APPLICATION
VERSION 2.3
-Removed "boost" option.
-Changed theme.
-Added safety option.
-Added information page.
-Added G3 Speed script trial. New Version 3.4(script is heavy on battery)
-Fixed D855 bugs and BSOD.
VERSION 2.2
-Test build.
VERSION 2.1
-Bug fixes.
VERSION 2.0
-Rewrite application from ground up for efficiency and proper execution.
-Bug fixes.
BETA VERSON 1.5
-Added 'Boost" button to OC additional clocks in the device.
-Added "Set On Boot' option.
-All clocks are set to default when the screen is off.
BETA VERSION 1.4
-FUBAR
BETA VERSION 1.3
-Velocity is now the official name.
-New fresh material design.
-Value now WON'T hold after reboot for safety.
-Added more frequencies for finer adjustments
BETA VERSION 1.2
-Added more frequencies in a new selector.
BETA VERSION 1.1
-Changed Level 4 "max" to a lower value. It was crazy high IMO.
-Added "shake to default" in case you get into trouble.
-Values now stick after screen toggle!
-Values set to default after reboot.
CHANGELOG FOR G3 SPEED SCRIPT
VERSION 3.3
-Removed net settings.
-Adjust emmc gov settings.
-Disabled logging in kgsl.
-Adjusted kgsl and firmware timing.
-Removed adreno config file for now.
VERSION 3.2.1
-Add 30sec delay to script launch.
VERSION 3.1
-Removed parts of the script that deleted files from the system.(QOS & logcat)
-Added build properties to the system.
-Removed any clocking that was initially in the script. These are now added to Velocity.
-Greatly improved Adreno.
VERSION 3
-Add fstrim back
-Add delay before script executes
VERSION 2
Remove fstrim.
Remove drop caches.
Adjust mmc clock delay.
Change devfreq governors.
Adjust byte clocks.
Added adreno config file to remove adreno logging.
THANKS ENJOY![emoji2]

This working good for anybody? I have more coming on this. This is really just the beginning. This will be a flashable zip after I'm done with a few more goodies.

razz1 said:
This working good for anybody? I have more coming on this. This is really just the beginning. This will be a flashable zip after I'm done with a few more goodies.
Click to expand...
Click to collapse
I've been running scripts with a lot of your tweaks already in it and it's been running great for me. The only thing that I noticed that wasn't in the scripts that I'm running was the lines to remove the qosmgr stuff so I just added your lines into one of the the files in my init.d folder. I also just added the new line that you posted up in the International thread to try and increase FPS rate so we'll see how that goes.
Thanks for your work. I look forward to seeing what you come up with for your next flashable zip.
Here's the mods/scripts I've been using for awhile now even when I had my S4 just so you know what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=2226373

bofiana said:
I've been running scripts with a lot of your tweaks already in it and it's been running great for me. The only thing that I noticed that wasn't in the scripts that I'm running was the lines to remove the qosmgr stuff so I just added your lines into one of the the files in my init.d folder. I also just added the new line that you posted up in the International thread to try and increase FPS rate so we'll see how that goes.
Thanks for your work. I look forward to seeing what you come up with for your next flashable zip.
Here's the mods/scripts I've been using for awhile now even when I had my S4 just so you know what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=2226373
Click to expand...
Click to collapse
Good. Thanks man. Yea you should hit some high frame rates with that. Better than I've seen on any phone I've had.

Just ran this on Zom ROM. So far so good. Thanks!
Sent from my LG-D851 using XDA Free mobile app

Do I need to run this every time I reboot?
Wow. Sorry for the the newb question. I read the OP. Thanks.
Sent from my LG-D851 using XDA Free mobile app

showbo said:
Do I need to run this every time I reboot?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. I am making a flashable zip to make it run on boot though. Will have it done soon.

I finished with a very BETA app for boosting the graphics on the G3.
It looks like crap but functions as intended. I will make it look nice/ad features later.
Essentially you are overclocking your device with this app.
Use it CAREFULLY! Their hasn't been extensive testing yet but I don't forsee any issues.
If at any time the screen is turned off on your device, your settings will revert to default to avoid any blue screens.
Enjoy!
http://d-h.st/mag

Have a flashable zip here. This is version 2 and should be even quicker! I will post a changelog in a bit.
Flash in recovery.
Reboot twice after install!!!
G3 SPEED V2
http://d-h.st/oyi
Uninstall version 2
http://d-h.st/D7p

Will this application work with aosp? I know the script won't.

mastibeta said:
Will this application work with aosp? I know the script won't.
Click to expand...
Click to collapse
I would also like to no the answer this?

mastibeta said:
Will this application work with aosp? I know the script won't.
Click to expand...
Click to collapse
Are you sure the script won't? Did you try it out? I haven't played with it much on aosp yet.
bbobarino said:
I would also like to no the answer this?
Click to expand...
Click to collapse
The app is very beta. Right now the app is supposed to bring the setting back to default when you toggle the screen off. It has a hard time doing this on an aosp rom right now. Otherwise it works the way its supposed to. You can try it but make sure you hit the default button before turning your screen off or when you turn the screen back on you will end up with a blue screen. At that point you will need to pull the battery.
The app will give you a significant increase in performance overall. Not just in graphics.
I am working hard at perfecting the other operations of this app but just need a little time.
Thanks guys!

So if you have used the graphics application you probably realize this app makes the entire device faster. Not just the graphics. I labeled it "graphics" because it was so obvious great things were happening there but good things are happening elsewhere in the system too.
NEW Beta version 1.1
-Changed Level 4 "max" to a lower value. It was crazy high IMO.
-Added "shake to default" in case you get into trouble.
-Values now stick after screen toggle!
-Values set to default after reboot.
Let me know how it performs for you.
Thanks guys!
[emoji12]
Download
http://d-h.st/yuK

Tried out the graphics app beta 1.1 on my D850 (ATT) and on level 2 my screen when almost fully blue and was tweaking out. It happened to fix itself, Thank God. Is the reason why this happened because I'm on the Att variant?

theshow4life said:
Tried out the graphics app beta 1.1 on my D850 (ATT) and on level 2 my screen when almost fully blue and was tweaking out. It happened to fix itself, Thank God. Is the reason why this happened because I'm on the Att variant?
Click to expand...
Click to collapse
No. It's not an issue with variants. However, every phone is different. Just like some people can overclock their phones really high but others with the same device can't go that high without issues. It's the same thing here. Some devices can handle more than others.
If you run into an issue again just shake the phone or toggle your screen off and on. Either one of these will trigger the app to revert to a lower default setting.
Are you overclocking your CPU? Just wondering if that could cause a blue screen at only level 1.

I am not overclocking anything stock phone rooted with bumped bootloader. Level 2 is there i had problems. Ill give it another go thank you for the support!

theshow4life said:
I am not overclocking anything stock phone rooted with bumped bootloader. Level 2 is there i had problems. Ill give it another go thank you for the support!
Click to expand...
Click to collapse
Yea. Not everyone's phone can reach all levels. This adjusts other behind the scenes clock settings. You won't see your GPU or CPU overclocking. This is app does something entirely different.
I haven't updated the op here yet but if you go to the G3 international thread their is newer versions posted.
http://forum.xda-developers.com/showthread.php?t=2929212
[script] [v2] g3 speed [app] g3 graphics

razz1 said:
Yea. Not everyone's phone can reach all levels. This adjusts other behind the scenes clock settings. You won't see your GPU or CPU overclocking. This is app does something entirely different.
I haven't updated the op here yet but if you go to the G3 international thread their is newer versions posted.
http://forum.xda-developers.com/showthread.php?t=2929212
[script] [v2] g3 speed [app] g3 graphics
Click to expand...
Click to collapse
The new beta works way better for me no blue screen .
Thank you very much!!!

VELOCITY v1.3b
Been working on the app most of the day to bring you version 1.3 of the app.
The app really needed an official name so it's now called Velocity. It now has a new look based mostly on @KingOfDope design so thank him.
-New fresh material design.
-Value now WON'T hold after reboot for safety but will add "OnBoot" soon.
-Added more frequencies for finer adjustments
NOTE.. I wouldn't hit the insane speed button.
DOWNLOAD
http://d-h.st/1pO

UPDATES IN THE OP
New Velocity.
New G3 Speed script.

Fix for heating issue without performance drop [Root Required]

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?

Help me to Improve Interactive CPU Governor tunnings

I'm currently running following script for interactive governor on stock oxygen os 3.2.0.
It's running great but I know there is lot of room to make it even great.
So help is needed to make it great
====
#!/system/bin/sh
# configure governor settings for little cluster
echo 20000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
echo 95 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
echo 20000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate
echo 307200 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
echo 90 480000:25 652800:30 844800:45 960000:60 1036800:65 1113600:70 1190400:80 1228800:90 1324800:95 1593600:100> /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
echo 40000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis
echo -1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack
----------------
# configure governor settings for big cluster
echo 20000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/above_hispeed_delay
echo 90 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/go_hispeed_load
echo 30000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_rate
echo 307200 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/hispeed_freq
echo 40 403200:15 480000:20 556800:25 652800:30 729600:40 806400:47 883200:55 940800:60 1036800:65 1248000:72 1324800:60 1401600:65 1478400:70 1555200:90 1632000:70 1785600:93 1824000:95 1920000:90 1996800:97 2150400:100 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads
echo 20000 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/min_sample_time
echo 0 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/max_freq_hysteresis
echo -1 > /sys/devices/system/cpu/cpu2/cpufreq/interactive/timer_slack
-------------
# input boost frequency
busybox echo 0:1036800 1:0 2:1036800 3:0 > /sys/module/cpu_boost/parameters/input_boost_freq

Hey Jumboman,
Have you made any progress with your settings? Coming from a brief time with a 6P, I've been trying to reduce the noticeable touch lag / latency on the OP3 and I'd love to see if anybody has made any progress.
Thanks!

brooksilg said:
Hey Jumboman,
Have you made any progress with your settings? Coming from a brief time with a 6P, I've been trying to reduce the noticeable touch lag / latency on the OP3 and I'd love to see if anybody has made any progress.
Thanks!
Click to expand...
Click to collapse
Actually I posted this to get help from some experienced users.
I am now using stock values because as per @flar2 there are lot of system processess trying to change cpu parameters and also he suggested to use stock values for both performance , stability and battery life.