Search results

7.1.2 was the first one that merged partitions?

In system info tap on kernel version a few times and it should take you to a test menu, in the test menu select the first option.

I think so but not sure what's changed

Sorry but no idea here, I've had reboots on every rom so far based on Android 6 under different scenarios. Yesterday I had two after uninstalling/installing apps. I've contacted Patrick at Miui, seems he's a forum admin, and asked him for any news on the reboot issue.

Did a TWRP backup of Global Beta 6.7.29 and downgraded to Xiaomi.eu KitKat 7.1.5 to test, wish it was a least Lollipop though. First off the thermal-engine-8974.conf has some extra battery tempreature code at the end to scale CPU speed vs battery temp, basically it down clocks or shuts down CPU...

One core gets killed because Miui have configured it in the thermal-engine-8974.conf, but you can change it easily with root. qdhwcomposer looks to be part of the graphics chip driver.

Rebooted and caught a log. In the process of sending it to Miui.

Thank you for the log, been glancing over it but nothing jumps out at me. I've change, in the log app setting, the priority level from Info to Debug so more information is logged. I'm sure the devs will say your phone is on an obsolete version. But why not update to Marshmallow if you have...

I don't think so, just press record and wait for a reboot. That's what I'm doing but since I installed it I've had a totally stable phone.

Most incompatibility problems can be patched in kernel code, driver updates etc but by the looks of it they don't have a clue as why this is happening.

This has to be a kernel issue for sure, and as you say some Mi4's probably need different config due to different hardware. Have we tested locking mobile networks to 2g/3g only? Edit: Just read that some already tested this and still get reboots. Your unaffected Mi4 is 3g only, correct?

Why don't you capture a log so we can post it on the MIUI forum? As stated above it would have to be logging before the actual reboot occurs. This is the only way to get this stuff fixed and as the devs say " No log cat, then it didn't happen".

It means that the kernel has changes made and has been recompiled but we don't know what the devs have modified. Hopefully something to stop these reboot problems. If you go to phone information and press 5 times on kernel version you go into a test menu and it tells you there.

Supposedly if you reboot a few times, after the initial CM 13 install, sensors work properly except the IR sensor.

Updated to 6.7.29 Global beta: Kernel has been recompiled with todays date stamp so hopefully the devs are trying to solve this bug but who knows what they've changed. Same baseband/modem as before. -------------------------------------------------------------------------- I'm trying to...

It's a China stable without gapps so no go for me but could be another test we could try without Google services installed just in case.

That's it

I've got it disabled also and haven't noticed worse battery. The strange thing is that since yesterday I'm live logging to a file in memory permanently to try and catch the reboot message and I've been getting even better battery life than before, go figure.

Now I'm being asked for more information by the Mini forum moderators. I'm going to try and get a logcat just before the reboot happens saving periodically to internal storage. But by the looks of it this isn't going to get solved anytime soon.

No flashing method solves this. My Mi4 is going to get sold second hand by the looks of it.