I'm using Stock Rom 4.4.2 + Franco Kernel Nightliyes and I can't arribe to 2,5 hours of SOT, with omnirom and the same use i can easily achieve 4,5 hours SOT, this problem starts when i was beggining to use xpossed, any ideas? Recommendations? Thanks in advance
I have same configuration except flashed dalvik and bionic optimized + touch control but having 3.5 hours of SOT and total 19-20 hr of battery. Did you try wiping cache and dalvik cache ? (I did not tried onmirom maybe it is normal )
Xposed and gravitybox usually can't create such drainage problems.
And why you think they are responsible for that?
Can you provide BBS screenshot before ready to charge?
Unleashed by my Nexus 4
Scrye said:
I have same configuration except flashed dalvik and bionic optimized + touch control but having 3.5 hours of SOT and total 19-20 hr of battery. Did you try wiping cache and dalvik cache ? (I did not tried onmirom maybe it is normal )
Click to expand...
Click to collapse
Yesbi did
Enviado desde mi Nexus 4 mediante Tapatalk
Related
Hi everyone,
I got this Rom installed + Glados 2.3 Kernel on my I9023EU.
This combo solved:
-ICS increased battery drain: lazy governor, 100 mhz min freq
-lag in app drawer
Issues:
-font installed not properly displayed
-random reboots (no OC)
any hint?
EDIT:
-WiFi staticIPs not working ... when asked for subnet mask, only the last segment is to be inserted. Then it works..
EDIT 2:
-upgraded to GlaDOS 2.4
NEW ISSUES (not related ti the upgrade, i dare to say):
-BLN BLINKING: if when unlocking, lights are in the off-phase of blinking, the remain off.
-DSP MANAGER 2.0: Equalizer is not working
Thanx a lot
No problem with the ROM NexusBeam 4.1.0, but I didn't change the kernel...
Maybe, if i have any time this weekend, I'll try to install Glados 2.3 Kernel.
I will report issue(s) if I have some.
Try to use the new matr1x kernel
anyone of you heard about wipe cache/dalvik/data
even AFTER having flashed NB4.1. ?
someonedon'trememberwho said this solved some probs..
No problems with Nexus Beam, the best rom at all (imho).
Now i've tryed to use Glados 2.3
Have you wiped data/factory and cache before installing Nexus Beam?
pastikk said:
Have you wiped data/factory and cache before installing Nexus Beam?
Click to expand...
Click to collapse
yep. and someone says also after... what about it?
I encountred some random reboots while making a call with 3G enabled.
Random reboots seem to have disappeared after reinstallation. This time I flashed nb4.1 and glados2.4 at once, without reboot inbetween.
Still short battery life and no correct fontinstall
Sent from my Nexus S using XDA App
Hi,
Can anyone help me with deep sleep? I tried rooms like cm7 from pcfighter, sdsl v1.1, oxygen and now ics rc0 from mike. I don't have deep sleep.
AlarmDump and screens in attachments
radosnyz said:
Hi,
Can anyone help me with deep sleep? I tried rooms like cm7 from pcfighter, sdsl v1.1, oxygen and now ics rc0 from mike. I don't have deep sleep.
AlarmDump and screens in attachments
Click to expand...
Click to collapse
check partial wakeups
Partial wakelokcs:
radosnyz said:
Partial wakelokcs:
Click to expand...
Click to collapse
hmm which apps are you always running ? (active processes )
and what about wi-fi , data connection bluelooth and gps?
Process is only one: "events/0".
Data connection bluelooth and gps are disabled, wifi max 30 min/24h
What is it act=android.intent.action.TIME_TICK?
WiFi really turned off or just disconnected?
If nothing helps clean your ROM:
Factory reset
And dalvik cache clean
Then check if it works.
Reinstall only a few apps and test again and put more apps after the test
Sent from my LG Swift using xda premium
WiFi was turned off. I done factory reset and cleaned dalvik cache. I installed cpu spy, BetterBatteryStats, Root Explorer and waiting for results. I didn't install gaps.
Edit: still don't work :/
Hi guys. I am going to explain my experience and How did I found the solution. It might work for some people but not for others so please try it and see if it works.
Story:-
I was using ARHD 13.0 with siyah kernel 1.6.8 first it was charging very fast as I changed the setting to 1200mAh. but I was keep changing the settings in stweaks and after few days it started to charge very slow. I was putting my phone in charging the whole night and it charged only 30%.
Solution:-
I downloaded the clear data zip from the link below,
http://forum.xda-developers.com/showthread.php?t=1827635
and flashed with CWM. than fter rebooting the phone I RESET the settings in STWEAKS and rebooted in CWM, than clear cache and clear dalvik cache. and now my phone is charging very fast.
I hope this works for you guys too...
your link is dead.
can repost??
Here you go buddy... Sorry for dead link...
http://forum.xda-developers.com/showthread.php?t=1827635
Just updated the latest version of CM 11 nightly on my phone...20140102.. Restarted it was 28 % within 10 min of use it was 17% + the phone back is heating.... This cannot be explained!!! Pls help CM guys.. I'm depending on ure OS.....
Sent from my LG-D802 using Tapatalk
Did you reboot into recovery, wiped cache, dalvik and fix permissions?
Did you try a clean install? (Formatting system and data and dalvik and cache)?
You didn't by any change recovered any apps+data? Best not to.
Also did you check logcat for errors?
Try settings>development (6taps on build in settings>about so see development) then corresponding CPU utilization option, so you can see what's running on CPU most of the time?
All above are best practices m8, goodluck
Hi all,
does anyone know how to fix Sleep of death issue on the oneplus 2 ? im facing this problem for more than 6 months now.
my phone wont wake up from sleep unless i hold the power button for about 10 sec , the phone will reboot and i will lose about 20 % to 40 % from the battery.
this problem happens once every 2 - 3 days
ive tried the following:
*cache and dalvik cache wipe.
* factory reset
* Rooting the phone and installing a custom ROM ( the problem happened on the stock ROM even before i root it or change the ROM to a custom one )
Any solutions ?
thanks in advance
If u face same problem in different rom then i think its hardware problem.
I'll say it's a battery issue
Sent from my ONE A2005 using Tapatalk
i had this issue when i flashed custom kernel over another custom kernel