Search results

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.

Very interesting. If that's the only thing they did then what a lazy "fix" :P Makes you wonder why this was removed in the first place.

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...

Great, so from miui 7.x to 8 still reboots..

What bugs me is the randomness of the reboots. Sometimes more sometimes less often. For example my gf's phone didn't reboot for 4 days but today it did. I thought maybe because she doesn't have an alarm active on vacation that this somehow made a difference but no such luck. If it really has...

No there's no such file with MM. Could be that something else is doing the battery monitoring.

It could very well be that all must be "active" and no reboots happen. Perhaps they botched something while setting this stuff in new miui's. @Gingernut says the cores can be activated manually by editing a few configs. Perhaps someone could try this. Maybe a simple cpoy/paste of the settings...

With MM on balance mode only 2 cores are active while 1 is on standy, the cpu usage is extremley high. In performance mode 3 are active, much lower cpu usage. But 1 is always disabled no matter the mode you choose. edit: Oh also 7.1.5.0 is based on developer 6.3.31, no idea why they would call...

I thought so. Fastboot 7.1.2.0 global rom leaves the old partition system by default, while if you had let's say 7.1.1.o and updated via OTA to 7.1.2.0 then you would have gotten merged partitions in preparation for MM. But with fastboot 7.1.2.0 if you manually added flash partiton...

From my research 7.1.2.0 global OTA update merged partitons in preparation for MM which came after with 7.2. This is what I saw in old forums where people where asking what's changed with that update. But fastboot 7.1.2.0 global rom doesn't merge partitions or at least there is no command for...

I guess there could be extra band frequencies enabled for china's version among other things as it's also meant for LTE-CT version too, while global supposedly isn't. Also these versions are the very last before MM came along. I do know they were preparing for MM by merging partitions with those...

Is xiaomi.eu 7.1.5.0 stable based on china KK rom from that period right? I'm wondering what's so different in that rom compared to last KK 7.1.2.0 global stable rom where reboots supposedly don't happen?

I see. Has anyone tried turning proximity sensor off yet?

What exacly is qdhwcomposer unfortunately this is way out of my league. Looks to me like both reboots happen with this. No I don't have Maps installed. Tbh I went with KK cause it doesn't 'kill' 1 core and it's stabler and faster.

Well it looks like I've captured a reboot, at least I hope so. Set it went to sleep and it recorded a few hours. I saw the phone was rebooted in the morning, it's almost on a 24 hour cycle... Tbh I don't know if this log will help at all. Oh and keep in mind this is on custom xiaomi.eu 7.1.5.0...

Alright I'm recording, let's hope a reboot happens soon. From tomorrow on the phone will be roaming on a different network in another country so I guess it's possible that changes things perhaps. Maybe mi4 doesn't like to be idle and likes processes running in the background hence the new...

@Gingernut Any special settings I need to set in logcat extreme for this?

@jc rey I did. I flashed 7.1.2.0 global stable, then xiaomu.eu 7.1.5.0... For 7.1.5.0 (unless you manually strip it down further) you need 7.1.2.0 or higher for merged system partition, because it's too big to fit on ~600mb. This is why I keep wondering if there could possibly be a relation with...

Well my gf is still having reboots on KK too, I've tried disabling just about everything. This phone sux. Maybe someone can look into this: http://forum.xda-developers.com/showpost.php?p=64675180&postcount=11

Good point. But I'm really wondering now why these reboots happen on this particular KK version as well. If I understand correctly they happen with fastboot flashing as well as twrp/cwm/mirecovery flashing correct? So we can rule out the flashing method I guess? Personally I own a mi4c ordered...