For me batterylife isn't really a problem, I easily get one to one and a half day before I need to recharge.Does anybody test battery life?
If I'm not using my phone (calls, browse, games, GPS ....) I expect the battery to works about 5 days. Don't ask me why I did my phone to work so long, I will answer "Because I like that"
The people are different, you know!
If I'm not using my phone (calls, browse, games, GPS ....) I expect the battery to works about 5 days. Don't ask me why I did my phone to work so long, I will answer "Because I like that"
The people are different, you know!
My Xiaomi Mi2 last for 5 days )
Of course I've did some tricky stuff.
I'm using Tasker, and I have all powerful consummation sensors off, if I do not need them. I have sync task with the net on each hour. (mail, messenger, weather).
I'm putting my phone in airplane mode during the night. So its possible your phone to last for 5 even for 6 days in some cases
Most of the people do not need that, but I'm a lazy man and I even forget to put my phone on power supply, so battery life for me is very important
I think you can reach that with any ROM available for our M2/S, just doing that kind of tricks Tutmos has said
Sent from my MI 2S using Tapatalk 4
I agree with you that the use is of major importance, but the ROM also plays a vital role. I've tested several ROMs in the 9 months I own this phone, without changing the way I use it (and I can say I make a quite moderate use, no gaming, no auto-syncing and only few calling) and I can say that from the one ROM to the other I've seen from little to big differences, with the most efficient being JLB14 (3-4 days without external apps for energy saving).Yes, but the bigger differences in terms of battery consumption, comes from the use of the phone. The ROM may be responsible for, let's say, 20% of the differences.
And 5 days is reachable with any ROM I think.
And sometimes apps like tasker, Llama, Greenify... can save you a lot of battery. Much more than the little they consume. While they do their things in the background, you'll need to turn on the screen to do it manually, and then it will cost more battery, for example.
Sent from my MI 2S using Tapatalk 4
Edit system/usr/keylayouts/Generic.kl with Root Explorer, change binding for 257 code
"257 BUTTON_2" to "257 HEADSETHOOK"
Save, make sure file permissions are still rw-r--r-- and reboot.
First of all thanks for answering. I've tried this, but nothing changed.
Plus I messed up everything and long story short now I have a really old backup that works and a newer backup corrupted.
Now I can''t find how to fix the backup because all the solutions in internet are erasing the md5 checksum and that's not what I need.
Is there a way to - given a backup plus the md5 checksum - try to fix it? It piss me off doing a complete backup and discovering when I need it that it's ****ed up!
Hell yes!
Thank you very much, now it works like it is supposed to do.
Summary: edit the /system/usr/keylayouts/Generic.kl file assigning HEADSETHOOK to key 256 - plus removing key 226
Same thing. There's no ringtone nor vibration.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation