avaescaner
23/10/14, 20:37:18
Muy buenas.
Estaba valorando comprar uno de estos Xiaomi Redmi 1s, pero los problemas de sobrecalentamiento y de batería que leo por todos sitios me echan un poco para atrás.
Buscando he encontrado una posibles solución (en inglés).
Como no me deja poner el enlace, pego el texto. Para ir al original basta con pegar un trozo del texto en google:
Those who are having overheating issues, try this-
Before you start, you must know that this is not for beginners - you need to know and have the confidence to root your phone, do various tweaks that are not exactly beginner level, though what you will be doing will not damage the phone or affect your warranty.
Also note that I have gotten to try this only an hour ago, and as this is not a beginner level task - you are expected to know how to find and do the following steps without someone handholding you. If you need handholding, you should not be doing this at this time. After I am more convinced, and after other advnaced Android users can vouch they have the same result as mine, I shall give a step-by-step.
First make sure your symptom matches what I have:
Root your phone
Install BetterBatteryStats, open it and give it root permissions. Make sure you have set it to start automatically in Security > Permissions
Recharge your phone to 100% (Fully Charged), unplug and use it as normal until the battery is, say 10%. Do not restart the phone for any reason during this test cycle
Open BetterBatteryStats, and choose CPU States in the first drop down - this will give you how much time the CPU was spending in each of its speed steps, and in deep sleep state
If you see a very very high reading for the 1.59 GHz frequency, and only a few seconds or single digit minutes in the other frequency steps, then your symptom is the same and mine.
Now comes the experiment.
Install SuperSU
Install Busybox from XXX - the correct binary for our phone is arm7l - to /system/xbin, symlink and install it to system/bin also
Install Trickster MOD from Google Play
Open Trickster MOD and give it root permissions
Go to the General options (swipe from the left edge), and touch Governor Controls
Change the value for io_is_busy to 0
Change up_threshold to 75
Change up_threshold_any_cpu_load to 75
Change up_threshold_multi_core to 75
Apply the changes (tick mark at the top)
Use the phone for a few hours and make sure everything is fine
Go back to Trickster MOD, swipe from the right edge, and put a tick on Kernel Settings
After doing this, repeat our BetterBatteryStats experiment and see how the pattern is - you should have higher time spent on 300 MHz and 998 MHz, and much lower time spent on 1.59 GHz. And the phone should not heat up like before.
Post your outcomes please.
For rooted users, I have a simpler solution for this. You need to have file explorer that is capable of editing system partitions - like Root Explorer.
Edit the file named /system/etc/init.qcom.post_boot.sh
Look for the section that starts with
case "$target" in "msm8226")
Change the line that reads:
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
to
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
Now, these steps will fix the heating issue, and will ensure the CPU does not sustain at 1.59 GHz most of the time the screen is on. The drawback of this is that the phone will now show lags because the CPU is no longer at its highest frequency. To counter that, change these lines:
echo 50000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
to
echo 30000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
Make sure the init.qcom.post_boot.sh file has 755 (rwxr-xr-x) permissions, reboot.
On a related note, you can add init.d support to your phone by adding this to the last line of the same file:
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Make sure you create the init.d folder under etc with root:shell as the owner and 777 (rwxrwxrwx) permissions, and droop valid init.d scripts in it.
¿Alguien lo ha probado a ver si realmente funciona sin detrimento en las prestaciones?
Gracias!
Estaba valorando comprar uno de estos Xiaomi Redmi 1s, pero los problemas de sobrecalentamiento y de batería que leo por todos sitios me echan un poco para atrás.
Buscando he encontrado una posibles solución (en inglés).
Como no me deja poner el enlace, pego el texto. Para ir al original basta con pegar un trozo del texto en google:
Those who are having overheating issues, try this-
Before you start, you must know that this is not for beginners - you need to know and have the confidence to root your phone, do various tweaks that are not exactly beginner level, though what you will be doing will not damage the phone or affect your warranty.
Also note that I have gotten to try this only an hour ago, and as this is not a beginner level task - you are expected to know how to find and do the following steps without someone handholding you. If you need handholding, you should not be doing this at this time. After I am more convinced, and after other advnaced Android users can vouch they have the same result as mine, I shall give a step-by-step.
First make sure your symptom matches what I have:
Root your phone
Install BetterBatteryStats, open it and give it root permissions. Make sure you have set it to start automatically in Security > Permissions
Recharge your phone to 100% (Fully Charged), unplug and use it as normal until the battery is, say 10%. Do not restart the phone for any reason during this test cycle
Open BetterBatteryStats, and choose CPU States in the first drop down - this will give you how much time the CPU was spending in each of its speed steps, and in deep sleep state
If you see a very very high reading for the 1.59 GHz frequency, and only a few seconds or single digit minutes in the other frequency steps, then your symptom is the same and mine.
Now comes the experiment.
Install SuperSU
Install Busybox from XXX - the correct binary for our phone is arm7l - to /system/xbin, symlink and install it to system/bin also
Install Trickster MOD from Google Play
Open Trickster MOD and give it root permissions
Go to the General options (swipe from the left edge), and touch Governor Controls
Change the value for io_is_busy to 0
Change up_threshold to 75
Change up_threshold_any_cpu_load to 75
Change up_threshold_multi_core to 75
Apply the changes (tick mark at the top)
Use the phone for a few hours and make sure everything is fine
Go back to Trickster MOD, swipe from the right edge, and put a tick on Kernel Settings
After doing this, repeat our BetterBatteryStats experiment and see how the pattern is - you should have higher time spent on 300 MHz and 998 MHz, and much lower time spent on 1.59 GHz. And the phone should not heat up like before.
Post your outcomes please.
For rooted users, I have a simpler solution for this. You need to have file explorer that is capable of editing system partitions - like Root Explorer.
Edit the file named /system/etc/init.qcom.post_boot.sh
Look for the section that starts with
case "$target" in "msm8226")
Change the line that reads:
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
to
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
Now, these steps will fix the heating issue, and will ensure the CPU does not sustain at 1.59 GHz most of the time the screen is on. The drawback of this is that the phone will now show lags because the CPU is no longer at its highest frequency. To counter that, change these lines:
echo 50000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
to
echo 30000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
Make sure the init.qcom.post_boot.sh file has 755 (rwxr-xr-x) permissions, reboot.
On a related note, you can add init.d support to your phone by adding this to the last line of the same file:
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Make sure you create the init.d folder under etc with root:shell as the owner and 777 (rwxrwxrwx) permissions, and droop valid init.d scripts in it.
¿Alguien lo ha probado a ver si realmente funciona sin detrimento en las prestaciones?
Gracias!