Mi4 Lte Ramdom Reboots [with Logs]


What's interesting to me is how many people have long periods without reboot then all of a sudden more than one in a short period. Same thing happened to me. Now gf reports to me many consecutive reboots and almost getting worse, even 3 per day.

So what exactly could be happening, what happens with prolonged phone usage? Cache gets filled a lot for example, what else? And why doesn't a reboot help basically..
 
  • Like
Reactions: Gingernut and jc rey
zegio said:
No

89a7b5b343e342eda1155eb1b4414248.jpg


Enviado desde mi MI 4LTE mediante Tapatalk
Click to expand...

Nice, keep on going, if you get a reboot please tell us.
I hope not!
Have you flashed the last official fastboot file before xiaomi.eu 8.0.2? Developer or stable?
 
  • Like
Reactions: jc rey
Pedro Tavares said:
Nice, keep on going, if you get a reboot please tell us.
I hope not!
Have you flashed the last official fastboot file before xiaomi.eu 8.0.2? Developer or stable?
Click to expand...
No, from 6.8.18 via twrp

6.8.11 with all wipes (include data), no backup restore (configured it as a new phone) --> after a week, 6.8.18 --> and few days later 8.0.2

Enviado desde mi MI 4LTE mediante Tapatalk
 
buzdo said:
What's interesting to me is how many people have long periods without reboot then all of a sudden more than one in a short period. Same thing happened to me. Now gf reports to me many consecutive reboots and almost getting worse, even 3 per day.

So what exactly could be happening, what happens with prolonged phone usage? Cache gets filled a lot for example, what else? And why doesn't a reboot help basically..
Click to expand...

Possibly something to do with bad flash blocks?

Data tries to get written to a bad block, but can't and panics, but this would surely be reflected in a kernel log output.

Flash chip garbage collection (trim)?

Kicks in every XX days but only in standby and causes a reboot stuck on a bad block, after the reboot it repeats the process again and again untill it fails and moves on?
 
Gingernut said:
Possibly something to do with bad flash blocks?

Data tries to get written to a bad block, but can't and panics, but this would surely be reflected in a kernel log output.

Flash chip garbage collection (trim)?

Kicks in every XX days but only in standby and causes a reboot stuck on a bad block, after the reboot it repeats the process again and again untill it fails and moves on?
Click to expand...
but bro, why kitkat 7.1 have no reboot issue?
 
Ivan rom after 3 weeks:
Just 1 reboot two weeks ago, it could be for many reason, so i consider this rom free of the ramdon reboot issue.

Enviado desde mi MI 4LTE mediante Tapatalk
 
  • Like
Reactions: jc rey
manlysixpacks said:
but bro, why kitkat 7.1 have no reboot issue?
Click to expand...

Before the Mi4 had two system partitions. They had to get merged together so future updates could fit, this happen just before the Android 6 update.

I'm just guessing but when the two partitons became just one I suppose other kernel/system code configs need to be ajusted for this change and haven't.

Users state that with ZeurionX kernel they don't get reboots, has this been tested?
 
Gingernut said:
Before the Mi4 had two system partitions. They had to get merged together so future updates could fit, this happen just before the Android 6 update.

I'm just guessing but when the two partitons became just one I suppose other kernel/system code configs need to be ajusted for this change and haven't.

Users state that with ZeurionX kernel they don't get reboots, has this been tested?
Click to expand...
bro im using 7.1.5 china stable with one-merged-system-parition and no reboot issue happened. so weird.
 
Gingernut said:
There are users that downgraded to 7.1.5 and one system partition and have reboots.

Have you had android 6 on our phone?
Click to expand...
Also the fact that with wake lock app no reboot so far. So it is also possible that the problem is there in kk also but not toggled due to different power savings.

Envoyé de mon MI 4W en utilisant Tapatalk
 
Gingernut said:
Possibly something to do with bad flash blocks?

Data tries to get written to a bad block, but can't and panics, but this would surely be reflected in a kernel log output.

Flash chip garbage collection (trim)?

Kicks in every XX days but only in standby and causes a reboot stuck on a bad block, after the reboot it repeats the process again and again untill it fails and moves on?
Click to expand...
Yeah my initial suspicions were something to this effect as well, something wants to get written/dumped and fails then tries again until it can skip it.

jc rey said:
Also the fact that with wake lock app no reboot so far. So it is also possible that the problem is there in kk also but not toggled due to different power savings.

Envoyé de mon MI 4W en utilisant Tapatalk
Click to expand...
This is so interesting, we kind of never considered that maybe the same problem exists in KK too but due to such a different power management in MM it never manifests itself as a reboot.

Anyway my next test will be to manually erase everything with fastboot sort of a reverse flashall.bat but I'll include partition, persist, etc. and do a reboot then a blank flash via emergency mode but also manually.
 
  • Like
Reactions: Gingernut
buzdo said:
Yeah my initial suspicions were something to this effect as well, something wants to get written/dumped and fails then tries again until it can skip it.


This is so interesting, we kind of never considered that maybe the same problem exists in KK too but due to such a different power management in MM it never manifests itself as a reboot.

Anyway my next test will be to manually erase everything with fastboot sort of a reverse flashall.bat but I'll include partition, persist, etc. and do a reboot then a blank flash via emergency mode but also manually.
Click to expand...

Did you try ZeurionX kernel?
 
Hi,
I'm using 7.5.3, and ever since I installed "wake lock app" (144h), had no reboots.
The longest period with no reboots in a few months!
 
  • Like
Reactions: jc rey
Hey...
I'm using miui.eu 8.0.2.0, and since I installed "wake lock app", had no reboots for 114h. Before i'm using the "wake lock app“, only 48h and my mi4 got reboot.
 
  • Like
Reactions: jc rey
jc rey said:
Ok, I will try the kernel, hope other users will still append progress with wake lock app in the meantime.

Envoyé de mon MI 4W en utilisant Tapatalk
Click to expand...
How install it?

Enviado desde mi MI 4LTE mediante Tapatalk
 
zegio said:
How install it?

Enviado desde mi MI 4LTE mediante Tapatalk
Click to expand...
Root... Flashify.. Save current... Generate twrp to flash new... And go. Visible after on about phone.
Then I used kernel adaptor to disable wake double tap as recommended. No reboot since 30 minutes

Envoyé de mon MI 4W en utilisant Tapatalk
 
You must log in or register to reply here.

Similar threads

Igor Eisberg
  • Locked
Known Issues (Weekly ROM)
Replies
2K
Views
2M
Bugs
Oscopoldo
O
Namaless
[kernel] Miui Speed Mod
Replies
43
Views
24K
Redmi Note 2
Oelschlegel
O
manohar
Smartisan OS v0.5.0 13-10-15 for Mi2/2S
Replies
106
Views
46K
Xiaomi Mi 2 / Mi 2S
Vivek Burse
Vivek Burse
Top Bottom
Back