Mi4 Lte Ramdom Reboots [with Logs]


after 18 hours of use , just put in office has restarted all of a sudden , nothing .. the only one that solves this problem and wake lock , a truly hurt kernel
 
I don't post since days, but since i installed Wake Lock app, NO REBOOTS for weeks. Yes, a bit annoying to start always this app, or always in background, but is the only solution i found to Mi4 with Android 5.0...
 
Installing zeurion kernel may be a good alternative. I am testing a simplier thing, as we suspect problem is due to cpu being non active, given the fact that only two cores are active, I REMOVED mpdecision file from /system/bin I well now have 4 cores active on 6.9.15 since yesterday. Phone runs smoother, less heat, better battery. I have a tweaked thermal. Conf also. Currently under test, if someone want to try I can post thermal. Conf here.

Envoyé de mon MI 4W en utilisant Tapatalk
 
Installing zeurion kernel may be a good alternative. I am testing a simplier thing, as we suspect problem is due to cpu being non active, given the fact that only two cores are active, I REMOVED mpdecision file from /system/bin I well now have 4 cores active on 6.9.15 since yesterday. Phone runs smoother, less heat, better battery. I have a tweaked thermal. Conf also. Currently under test, if someone want to try I can post thermal. Conf here.

Envoyé de mon MI 4W en utilisant Tapatalk
I like to try your tweaked themal. Please share too the prosedure for applied the tweaked thermal. This is run on the original kernel right?
 
  • Like
Reactions: jc rey
Installing zeurion kernel may be a good alternative. I am testing a simplier thing, as we suspect problem is due to cpu being non active, given the fact that only two cores are active, I REMOVED mpdecision file from /system/bin I well now have 4 cores active on 6.9.15 since yesterday. Phone runs smoother, less heat, better battery. I have a tweaked thermal. Conf also. Currently under test, if someone want to try I can post thermal. Conf here.

Envoyé de mon MI 4W en utilisant Tapatalk
How do you removed it? I can't do it with ES explorer
If I have Kernel Adiutor, can I switch on the other two cores directly?

Enviado desde mi MI 4LTE mediante Tapatalk
 
@zegio In twrp you have to mount system under mount settings then you can remove copy edit etc. the files in /system. You can also do everything via adb shell too.
 
  • Like
Reactions: jc rey
@zegio In twrp you have to mount system under mount settings then you can remove copy edit etc. the files in /system. You can also do everything via adb shell too.
Agree, all in twrp

Envoyé de mon MI 4W en utilisant Tapatalk
 
Quick update, with KK's mpdecision all 4 cores active/standby, cpu load is good and battery temp is good. I also uploaded KK's thermald-8974.conf file which is not present otherwise in MM. So far phone stable.
 
  • Like
Reactions: jc rey
Quick update, with KK's mpdecision all 4 cores active/standby, cpu load is good and battery temp is good. I also uploaded KK's thermald-8974.conf file which is not present otherwise in MM. So far phone stable.
Verify if my decisions are equal or not but apparently they are not as you see 4 cores active, can you post your thermal conf contents?
 
The KK thermal is the same as MM thermal from what I see but with added battery monitor synthax. But this this was reintroduced back with miui 8. In 7.5 it wasn't there.

KK thermal-engine-8974.conf
Code:
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

[BATTERY_MONITOR]
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

KK thermald-8974.conf
Code:
debug
sampling  5000

[tsens_tz_sensor0]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor1]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor2]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor3]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor4]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor5]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor6]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor7]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor8]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor9]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

[tsens_tz_sensor10]
sampling  1000
thresholds  60  90  95  100  105  110  115  120
thresholds_clr  57  85  90  95  100  105  110  115
actions  cpu  cpu  cpu  cpu  cpu  cpu  cpu  shutdown
action_info  1512000 1188000 918000  756000  648000  540000  486000  5000

I uploaded these 2 along with KK's mpdecision. I guess it's even possible if let's say KK mpdecision has incompatibilities with MM that it's mostly skipped.
 
think this post with the relevant tests made by us should be viewed as xiaomi also to create them a clear idea about the problem , so you think it will be a problem with the cpu that is, that instead of using them all in standby only uses 2 ? But this should not compromise the stability of the system as using only two to manage the cel standby enough. especially as regards fuel consumption , then the cel is unable to handle a reduced consumption of normal ? ..
 
think this post with the relevant tests made by us should be viewed as xiaomi also to create them a clear idea about the problem , so you think it will be a problem with the cpu that is, that instead of using them all in standby only uses 2 ? But this should not compromise the stability of the system as using only two to manage the cel standby enough. especially as regards fuel consumption , then the cel is unable to handle a reduced consumption of normal ? ..
Yes, this is also tested in beta team by few people. Today we remove mpdecision, tests started yesterday with that. In the past I ve got reboots with a suggested one. We need to make sure we are reboot free because in the beta team the discussion was limited to only 2 active cores, problem reported to xiaomi.
With wake lock we can avoid reboots while we still have two cores actives.
The test made with zeurion kernel well demonstrate kernel work can workaround the issue. Also in beta team we need to install every update, we fall short for this test.

Envoyé de mon MI 4W en utilisant Tapatalk
 
think this post with the relevant tests made by us should be viewed as xiaomi also to create them a clear idea about the problem , so you think it will be a problem with the cpu that is, that instead of using them all in standby only uses 2 ? But this should not compromise the stability of the system as using only two to manage the cel standby enough. especially as regards fuel consumption , then the cel is unable to handle a reduced consumption of normal ? ..
Wake lock shows it works with 2

My bat consumption looks better with 4 cores and thermal tweak, phone more responsive. Probably xiaomi want to stay with 2 (pure speculation) and misses a solution to this problem.

Envoyé de mon MI 4W en utilisant Tapatalk
 
Also cpu load is much lower, which in my opinion makes sense that less battery is used. This is nothing new we have been speculating about this many many posts back, just never tried removing or replacing mpdecision.

My best guess would be that they put 2 cores on OnDemand governor (or some other setting) and it causes problems. Unfortunately various cpu info apps usually only show settings for cpu0 so one thinks all 4 cores are set to Interactive for example but they're not.

Personally I'm not savvy enough to go digging through the guts of mpdecision so I'm just guessing at this point. :)
 
Also cpu load is much lower, which in my opinion makes sense that less battery is used. This is nothing new we have been speculating about this many many posts back, just never tried removing or replacing mpdecision.

My best guess would be that they put 2 cores on OnDemand governor (or some other setting) and it causes problems. Unfortunately various cpu info apps usually only show settings for cpu0 so one thinks all 4 cores are set to Interactive for example but they're not.

Personally I'm not savvy enough to go digging through the guts of mpdecision so I'm just guessing at this point. :)
Me too, we can only guess, be sure I ll publish in beta team my numbers to push xiaomi to react.
Also, as zeurion kernel works well, maybe we could get it with sMiui or from here.

Envoyé de mon MI 4W en utilisant Tapatalk
 
Update, had a reboot with KK's mpdecision and thermal, so that's that with this test, unless clearing cache is necessary?

My short experience with sMiui wasn't pleasant to be honest but it is tweaked a lot like all 4 cores active and auto rotation working and other stuff. Maybe I can try sMiui's mpdecision.

@jc rey Did you have any reboots with no mpdecision and your thermal tweak?
 
Update, had a reboot with KK's mpdecision and thermal, so that's that with this test, unless clearing cache is necessary?

My short experience with sMiui wasn't pleasant to be honest but it is tweaked a lot like all 4 cores active and auto rotation working and other stuff. Maybe I can try sMiui's mpdecision.

@jc rey Did you have any reboots with no mpdecision and your thermal tweak?
No reboot removing mp decision+ thermal tweak.
I switched to 6.9.20 rom few minutes ago.
But I am not optimist I see single core active... Weird. If you can continue testing removing mpdecision + th tweak, it was the best experience I had recently.

Envoyé de mon MI 4W en utilisant Tapatalk
 
Only 1 core active with mpdecision removed or with 6.9.20?

I'm going to try removing it tomorrow to see what happens, if reboot happens then I'm going to try sMiui's mpdecision.
 
Only 1 core active with mpdecision removed or with 6.9.20?

I'm going to try removing it tomorrow to see what happens, if reboot happens then I'm going to try sMiui's mpdecision.
1 core active in 6.9.20.


Removing mpdecision 4 cores are active.

Envoyé de mon MI 4W en utilisant Tapatalk
 
No reboot removing mp decision+ thermal tweak.
I switched to 6.9.20 rom few minutes ago.
But I am not optimist I see single core active... Weird. If you can continue testing removing mpdecision + th tweak, it was the best experience I had recently.

Envoyé de mon MI 4W en utilisant Tapatalk
I'm testing the 6.9.15 with mpdecision removed and thermal tweak. No reboots at now.

Enviado desde mi MI 4LTE mediante Tapatalk
 
  • Like
Reactions: jc rey
Usually android kernels have their own cpu regulators and governor settings while mpdecision is for Qualcomm chips and nullifies the kernel's settings, so maybe these two (in Mi4's case) don't exactly get along. Perhaps Miui's MM kernel doesn't "allow" it to function properly, so by removing mpdecision the kernel's settings are "better" for this particular chip.

Or perhaps cpu hotplugging is the culprit and simple tweaks to thermald can solve it.

In any case I guess we will find out if no reboots happen. :) Maybe it's worth a try just by tweaking thermald and leaving mpdecision too.
 
  • Like
Reactions: jc rey