Mi4 Lte Ramdom Reboots [with Logs]
- Thread starter jesuslg123
- Start date
zegio
Members
- Jun 8, 2016
- 76
- 30
6.8.4 xiaomi.eu
Full wipe, cache, dalvik and data.
No backup restore.
In first place I flashed the room and wipe cache and dalvik, and had a reboot after 6 hr of intense use (but, while charging)
Enviado desde mi MI 4LTE mediante Tapatalk
I was wondering this too. If updater script is the only navigator for flashing then I'd say not everything gets flashed. Surest way imo would be to fastboot flash the corresponding official rom version then flash .eu based on same version afterwards.
Anyway I flashed my gf's phone with .eu 7.5.3.0 (with some minor customization) over china stable 7.5.6.0 and 2 days no reboots yet. But auto rotate screen isn't working lame.
Anyway I flashed my gf's phone with .eu 7.5.3.0 (with some minor customization) over china stable 7.5.6.0 and 2 days no reboots yet. But auto rotate screen isn't working lame.
In 6.8.4 they have re-added the battery monitoring stuff to the cpu thermal config.
giobooo
Members
- Jul 9, 2016
- 73
- 30
I think they just didn't fix it in this release. Even if they tried as suggested by the First changelog, the results are not there. Maybe next week... It should be the last dev before the actual release of the stable Miui 8...
Inviato dal mio MI 4LTE utilizzando Tapatalk
Very interesting. If that's the only thing they did then what a lazy "fix" 
Makes you wonder why this was removed in the first place.
Makes you wonder why this was removed in the first place.
giobooo
Members
- Jul 9, 2016
- 73
- 30
Got another reboot on 6.8.4 after 20 hrs of uptime. The problem is real, still I don't understand how hard could it be for devs to Get to the bottom of it considering how many phones are affected...
With 6.8.4 2nd & 3rd cpu core are permanately off no matter which profile you choose, balanced/performance.
Performance profile puts 4th core to max freq while the 1st stays more or less idle.
Don't know what they are doing but by the looks of it they think these reboots have to do with heat, I don't agree at all as they nearly alwasy only happen while phone is idle and not under heavy stress.
On a side note we should get better battery life on this build at the expense of performance.
Performance profile puts 4th core to max freq while the 1st stays more or less idle.
Don't know what they are doing but by the looks of it they think these reboots have to do with heat, I don't agree at all as they nearly alwasy only happen while phone is idle and not under heavy stress.
On a side note we should get better battery life on this build at the expense of performance.
Not convinced about frequency/voltage problem but a bug in kernel that is not being found for some reason, something that kicks in when idle like trim or something.
Mine has rebooted before while uninstalling or installing an app from the play store so maybe the assumption of the partition merge problem is correct or atñeast along the lines of a storage/memory bug.
I know it's been said before but it's strange how Cyanomodgen is also affected when they have most code updated to recent releases from AOSP/Qualcomm/Codeaurora.
Last edited:
Could be a cache problem as it's constantly in use and it had to be chnged quite a bit for MM. Which kind of brings us back to partitions.
I'm inclining for partitions also but I've also been reading up on other devices that have had random reboot issues in the past like the OnePlus One, they had like four guys debugging and serching for the issue for a few weeks then they issued a radio driver update, also there was a problem when the OnePlus was first released and that the user partition was getting corupt.
Users were also getting logs from their phones live adb logging all the time, you have to leave your phone connected to a computer the whole time waiting for a reboot.
Possibly partition coruption is our problem and comes from the way the different parts of the rom gets written to each partition or maybe just an incompatible app for Marshmallow we have installed, I did see in my log alot of errors due to Poweramp so I have uninstalled it.
Another thing is the time our device has been on the market, more than likely Xiaomi has only one engineer working on it now which slows down debugging this stuff alot.
Has anybody tried installing a fastboot rom in emergency download mode (EDL)?
AFAIK the files are included in the fastboot image.
AFAIK the files are included in the fastboot image.
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
I cannot leak it as per agreement sorry.JC Rey knows but can't tell us
But I still do not reboot on xiaomi.eu 6.8.4 installed over 6.8.2 global rom.
Envoyé de mon MI 4W en utilisant Tapatalk
jc rey
Members
- Feb 15, 2016
- 1,538
- 142
I know, they'll kick you off the team.
I haven't had a reboot on 6.8.4 either since restoring a backup and updating but I did check and they have capped cpu performance hard.
