Search results

if u have stock mi recovery, follow this http://en.miui.com/a-233.html

On which rom u are now ? which recovery ?

Hm, no problems for me with Whatsapp Web, only after first boot, but after few reboots, works normally .. maybe it is due whatsapp..try uninstall app and install again..with other problems, I have it also :(

For monitoring battery drain,stats etc I am using : 1. Better Battery Stats --> link here http://forum.xda-developers.com/showthread.php?t=1179809 2. Wakelock Detector --> link here https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector&hl=hr 3. CPU Spy Reloaded --> link...

Hi guys, which apps are u using for monitoring battery life and which one for best battery life ? like Greenify etc.. any different setup from default one in kernel and other ? all suggestion and tips are welcome :)

Yeah, that is bug ,look here http://xiaomi.eu/community/threads/mi3-bug-miui-global-6-1-21.29608/

For me seems normal..

Hi, first read this :http://xiaomi.eu/community/threads/how-is-this-different-than-miui-com.18629/ :)

@ingbrzy I noticed little drain in standby, and is it normal big usage from android and android system ? Screenshot here

Haha, I read that too :P

Wow, thanks for tips :)

u are safe ..It is merged :D

Try drained battery to 0% then charge to 100 % and calibrate ,but before charging try wipe cache and dalvik cache :)

In disk info app go to settings, tick all options, then show screenshot about system and modem

I know.. u try again flash latest super su from here http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

wait,that is normal

then try this :If is still bootloop ,press volume button (+) and power button for 20 sec ,in recovery flash rom again, no need to wipe anything

are u followed this : If TWRP offers you to keep /system read-only, indeed keep it read-only. If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things! If is still bootloop ,press volume button (+) and power button for 20 sec ,in recovery...

Try wipe cache and dalvik cache first in recovery ..If it didn't help, than u need clean flash :) btw, clean flash is always best solution, especially if u changing android base ( from 4.4 to 5.0 or 6.0 )