Search results

Try a clean install. Magisk 20.1 works fine on my MIUI 11 stable.

That's global INDIA schedule, where Mi 9 isn't available officially. The China stable release is early November (Phase 2) for Mi 9.

Yes, that's the last one available from MIUI EU as their tool no longer supports 10.2 and Mi 9 will jump straight to MIUI 11 based on Android Q instead of having another 10.X update. The global stable is still being updated, though. The same 10.2 but with more features and bug fixes (new camera...

I just did this. Apparently I can't wait for the MIUI 11 EU. Without system wide dark mode, the battery life doesn't meet my expectations. I barely get 5 hours SoT in 24 hours per charge. With system wide dark mode in global, the SoT increases by 2 hours more. I install magisk then adaway...

I only miss "OK, Google" and probably the dedicated macro mode in stock camera app from current EU stable, which can be overcomed by the dedicated assistant button. Knowing that it may jump straight to MIUI 11 in less than a month, I think I can live with it.

https://github.com/GreatApo/MiNote3-Camera2API-fix Don't forget to mount system partition before flashing the zip

Just dirty update my Mi Note 3 10.3.1.0 to 10.4.1.0, all working good so far and I found working camera2 API enabler for *no-support-for-this-app-on-this-forum*. Thanks for the update!

It doesn't exist then. Goodbye.

Rather than coming back to this useless debate again, how about generating that logcat? No logcat, no bug. It's a common rule in custom ROM world, by the way, if you haven't known already. Go check xda-developers custom ROM threads. You haven't even tried, how do you it won't show anything? I...

If you guys are really really desperate with the issue, and none of developers can reproduce given the steps (of course it's possible to happen, it doesn't happen to me as well), then give them a logcat containing logs when this issue happens. Otherwise, it's a valid move for the developers to...

Looks like it changes partition layout or something, therefore the full wipe is mandatory. I even lose my fingerprint data, so when I restore my twrp backup I can't get in. It also wipes out /sdcard, something that's normally not done during normal wipe. Now I have to extract it from my twrp backup.

Your TWRP is old, update it. That first line checks whether the device is correct so you don't mistakenly flash the ROM on the wrong device. Might not be so lucky next time if the updater script uses something else that only newer TWRP has.

Selfies are definitely a lot better, main camera is more useful in low light when you use night sight, but as the HDR+ (since it uses the same basic algorithm), it requires certain lighitng conditions to be fulfilled if you don't want to end up in greenish black. A more equally lit scene is more...

OK, this is weird, a clean reinstall still has the same problem. I wonder if it has anything to do with magisk. I'll try another reinstall without magisk. EDIT 1: Seems true, clean reinstallation without magisk only makes the CPU awake for a little while and then completely goes into deep...

All CPU cores are prevented from entering deep sleep, all clusters are stuck at 1.4GHz, draining the battery significantly. Unfortunately, the app that's suspected is part of Android system, so it's unclear which service does it. Other thing that can be verified is that Compass app keeps asking...

Read OP: https://forum.xda-developers.com/mi-note-3/how-to/google-camera-how-to-mi-note-3-t3757049

Working nicely, thanks.

Glad to hear it still works even with hacks. Please attach the files here or host somewhere easily accessible, telegram is too noisy for me.

Ah, damn. Why do they have to do such a thing... front camera with Pixel3Mod is so much better than MIUI camera. I hope EU can integrate this modded blob. I can live without OIS/EIS as I have proper gimbal lying around, but I can't live with subpar image quality.

The two devices are not in the same class. If you have the budget, go with newer device, always.