[ROM | 4.4.4][ | WIUI | ][ 4.8.29 - FiNAL ] - MULTiLanguage | v5 | AROMA |
- Thread starter Wajk
- Start date
josedb
Members
- Nov 5, 2013
- 219
- 52
greenify was already installed, and it doesnt change anything..
well, wipe, clear caches, and reinstall for third time, nothing installed, just rom, and rilj wakelock is still there, iam fed up, i've been asking for this a lot of times, and developer didn't respond, so, i move to other rom.
EDIT: please, check this wakelock detector instead WDL , as its not detecting all wakelocks:
http://forum.xda-developers.com/showthread.php?t=1179809
Last edited:
Hello guys, I've been away for some time cause my phone crashed and I've just replaced my screen. I'm looking for the most stable release of this rom. Battery life is the most important factor for me. Which one do you suggest?
kamakasnh
Members
- Aug 23, 2013
- 317
- 67
i tested a lot of roms last month and i found mokee the most battery friendly.
Sent from my MI 2S using Tapatalk
orlanddon
Members
- Sep 2, 2014
- 20
- 13
Could you please explain what exactly does that mean? And is it possible to raise frame rate from 22.25 fps to at least 25 fps in normal (non HDR) mode? And is it possible to make recording of sound in Camera from both microphones (true stereo)?
DjBrie
Members
- Nov 7, 2013
- 43
- 20
I've found that freezing 'weather provider' using titanium backup reduces rilj wakelocks. This does however remove the weather from the clock widget.
kamakasnh
Members
- Aug 23, 2013
- 317
- 67
barbuti17
Members
- Mar 9, 2014
- 266
- 67
Interactive and Cfq as scheduler with Normal cpu power.
Inviato dal mio Mi2S con Tapatalk.
kamakasnh
Members
- Aug 23, 2013
- 317
- 67
barbuti17
Members
- Mar 9, 2014
- 266
- 67
It is not clear what'd you need to know anyway "Interactive" is the Cpu governor, "Cfq" is the I/O scheduler, "Normal" is the Cpu profile. It is the better solution for my usual usage.
Inviato dal mio Mi2S con Tapatalk.
paulrlz
Members
- Nov 23, 2013
- 584
- 82
Yes I have the same problem on 4.8.29.!
Did you fix it by removing the /etc/init.d/99_retention file?
Last edited:
oile
Members
- Jul 15, 2013
- 285
- 67
Sadly no. I had to switch back to CM11. The notification problem seems to be a "feature" of MIUI to save battery (wtf?). Rounding time seems to be more or less 5 minutes (at least with alarm time fix xposed module). It is not Wajk fault, maybe Ivan's.
Cyanogenmod doesn't have this issue. Retention and power collapse doesn't ruin app wakeups.
It is the only reason why I abandoned Miui (until v6 only if and only if it fixes this issue) in favour of a custom rom.
Sad but true.
Cyanogenmod doesn't have this issue. Retention and power collapse doesn't ruin app wakeups.
It is the only reason why I abandoned Miui (until v6 only if and only if it fixes this issue) in favour of a custom rom.
Sad but true.
paulrlz
Members
- Nov 23, 2013
- 584
- 82
https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer&hl=it
Try this, worked with nexus 4
Try this, worked with nexus 4
Hmm what a shame. I didn't have the problem with last weeks official MIUI rom. It's probably caused by ivan's KK then I suppose.
Thanks anyway!
The delayment is only with text messages. The screen goes on but sound and vibration are mostly a minute or more later. Does the app also fix that?
In the last days I faced this issue.
When I did a call the screen went off and the phone didn't react to the pressure of any button or touches on the screen. The screen became active again, and the phone responded to pressure of buttons and touches on the screen, only after the phone call terminated by the other part.
The problem was that when the call was anwsered by an asnwering machine it was not possible to have the phone reactive again because the other part didn't terminate the call. I had to pull the battery out of the phone.
When I did a call the screen went off and the phone didn't react to the pressure of any button or touches on the screen. The screen became active again, and the phone responded to pressure of buttons and touches on the screen, only after the phone call terminated by the other part.
The problem was that when the call was anwsered by an asnwering machine it was not possible to have the phone reactive again because the other part didn't terminate the call. I had to pull the battery out of the phone.
Maarva
Members
- Feb 16, 2013
- 34
- 28
An easy way is to deactivate the proximity sensor from dialer's menu.
I had the same problem and I solved it through this video
