Mi4 Lte Ramdom Reboots [with Logs]
- Thread starter jesuslg123
- Start date
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
Was fine 165h with tweaks. No reboot. Important thing is that I see 6.9.29 rom fixes the cores disabling issue, I am testing it for reboots without tweaks.
Envoyé de mon MI 4W en utilisant Tapatalk
Envoyé de mon MI 4W en utilisant Tapatalk
manlysixpacks
Members
- Jan 20, 2016
- 89
- 20
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
72h with 6.9.29, no random reboot for now....
Envoyé de mon MI 4W en utilisant Tapatalk
Envoyé de mon MI 4W en utilisant Tapatalk
manlysixpacks
Members
- Jan 20, 2016
- 89
- 20
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
Wondering if a clean miflash of a fastboot rom would not solve your RR....
Envoyé de mon MI 4W en utilisant Tapatalk
zegio
Members
- Jun 8, 2016
- 76
- 30
+155h. 6.9.15 xiaomi.eu
Enviado desde mi MI 4LTE mediante Tapatalk
Could you post the battery graph also? You are with the 3GB RAM model?
jockjoint
Members
- Dec 18, 2014
- 11
- 15
Guys, try that
"Its not hardware problem. When the temperature increases, the OS is toggling down the CPU frequency to monitor the temperature. What is weird is, I haven't noticed any of those issues on my phone, even though my phone reaches 45-48 C. But battery temp and processor temp are different. Battery will not be as hot as the processor.
Anyway, if that is the issue you are facing;
according to the thread, do this:
You need a root explorer, like solid explorer, or equivalent
Navigate to /system > /etc > find the file thermal-engine-8974.conf
Open that file.
You should find the contents as shown in that thread.
Now delete the stuff highlighted in RED in that thread.
Save , exit, reboot.
Done.
sampling 5000
[CPU0_MONITOR]
algo_type monitor
sensor cpu0
sampling 1000
thresholds 55000 60000 65000 70000 85000 105000 115000
thresholds_clr 50000 55000 60000 66000 80000 90000 110000
actions cpu cpu cpu cpu cpu cpu shutdown
action_info 1728000 1497600 1190400 1036800 960000 6528000 0
[CPU1_MONITOR]
algo_type monitor
sensor cpu1
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU2_MONITOR]
algo_type monitor
sensor cpu2
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU3_MONITOR]
algo_type monitor
sensor cpu3
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
algo_type monitor
sensor batt_temp
sampling 1000
thresholds 380 395 500 550
thresholds_clr 370 385 450 500
actions cpu+hotplug_2+hotplug_3 cpu+hotplug_3 cpu cpu
action_info 1190400+1+0 1190400+1 1036800 960000
This may not be the ideal way to do it, have to actually do it using ADB, if you plan on doing it, reply here, I will post how to do it!
Your device must be rooted to do any of these.
EDIT: found that file. Even I have it, but have not noticed anything of the sort stated here. The method above should work."
And replace mpdecision file to /system/bin with permission 755, owner 0-root, group 2000-shell.
"Its not hardware problem. When the temperature increases, the OS is toggling down the CPU frequency to monitor the temperature. What is weird is, I haven't noticed any of those issues on my phone, even though my phone reaches 45-48 C. But battery temp and processor temp are different. Battery will not be as hot as the processor.
Anyway, if that is the issue you are facing;
according to the thread, do this:
You need a root explorer, like solid explorer, or equivalent
Navigate to /system > /etc > find the file thermal-engine-8974.conf
Open that file.
You should find the contents as shown in that thread.
Now delete the stuff highlighted in RED in that thread.
Save , exit, reboot.
Done.
sampling 5000
[CPU0_MONITOR]
algo_type monitor
sensor cpu0
sampling 1000
thresholds 55000 60000 65000 70000 85000 105000 115000
thresholds_clr 50000 55000 60000 66000 80000 90000 110000
actions cpu cpu cpu cpu cpu cpu shutdown
action_info 1728000 1497600 1190400 1036800 960000 6528000 0
[CPU1_MONITOR]
algo_type monitor
sensor cpu1
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU2_MONITOR]
algo_type monitor
sensor cpu2
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU3_MONITOR]
algo_type monitor
sensor cpu3
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
algo_type monitor
sensor batt_temp
sampling 1000
thresholds 380 395 500 550
thresholds_clr 370 385 450 500
actions cpu+hotplug_2+hotplug_3 cpu+hotplug_3 cpu cpu
action_info 1190400+1+0 1190400+1 1036800 960000
This may not be the ideal way to do it, have to actually do it using ADB, if you plan on doing it, reply here, I will post how to do it!
Your device must be rooted to do any of these.
EDIT: found that file. Even I have it, but have not noticed anything of the sort stated here. The method above should work."
And replace mpdecision file to /system/bin with permission 755, owner 0-root, group 2000-shell.
It should be that when a phone is on standby, screen of sitting on a shelf, the cpu should be hardly in use at all, and this is the tipical reboot scenario, not while your playing a game which puts heavy load on cpu+gpu.
zegio
Members
- Jun 8, 2016
- 76
- 30
2Gb model. I'm insurance agent and my graphic battery looks like russian mountains. I'll post a screen next weekend.
Enviado desde mi MI 4LTE mediante Tapatalk
manlysixpacks
Members
- Jan 20, 2016
- 89
- 20
This solution does not work properly bro, my fone has juz reboot right now with this tweak :'(. Back to wake lock now, drainin' a little bit of battery but no rebooting.
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
Yes, saw the same, only one core remain after a while no way to wake up the others until you reboot. Mee too I removed mpdecision after a random reboot.
Envoyé de mon MI 5 en utilisant Tapatalk
Rıdvan
Members
- Sep 17, 2016
- 30
- 20
Also I saw this in global rom too.
I flashed Zx kernel but seems the battery isn't that good. Do you think flashing any older version will fix this? I really got bored with this ridiculous things.
Q&A live session today on Mi4, whoever's interested.
http://en.miui.com/forum.php?mod=viewthread&tid=373938&extra=&page=1&mobile=2
http://en.miui.com/forum.php?mod=viewthread&tid=373938&extra=&page=1&mobile=2
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
Rıdvan
Members
- Sep 17, 2016
- 30
- 20
I only got one reboot on 7.5.3.0 eu and never got another rr on Miui 8. Sometimes I just have problems with the cores and frequency but everything's fine in Zx kernel.
It's so weird how totally random these reboots are for different people. For example I get quite a lot of them while others get very little and after many hours of uptime. Makes you wonder what causes them from which apps are installed/running to different network types and frequencies, since there's no confirmed reboot without sim card I'm thinking this is a high possibility.
I'm now trying different build.prop settings, compared to old KK's build.prop there are quite a few differences. I'm systematically turning stuff on and off in build.prop one by one to see if anything makes a difference. But so far unsuccessful. :/
I did notice that after wiping cache and dalvik cache it takes longer for a reboot to happen so I'm still not ruling out the possibility that it could be cache partition related.
I'm now trying different build.prop settings, compared to old KK's build.prop there are quite a few differences. I'm systematically turning stuff on and off in build.prop one by one to see if anything makes a difference. But so far unsuccessful. :/
I did notice that after wiping cache and dalvik cache it takes longer for a reboot to happen so I'm still not ruling out the possibility that it could be cache partition related.
