Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??
Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??
I haven't noticed any difference. I still have 64 percent after having wifi on all day and moderate use. I AM using Auto Memory Manager and Juice Defender so maybe those are helping.
Has anyone else notice significant reduction in battery life in 6.3.13? I went from a full day to about 5 hours after flashing. I wonder if the multi-tasking has some task sucking up the juice??
Since this new build, I have not been able to get my phone to apply my voltage settings in my init.d file. It was working before the update, but now it always reverts back to default. Normally, this would only happen if the voltages were unstable and cause a force reboot. Now the phone goes straight to the default voltages when the phone first starts.
I am wondering if init.d is broken again. Anyone have any problems setting configurations with init.d after flashing this updated rom?
Thanx.
Is anyone using this rom with the navigation bar enabled?
If you are, have you noticed if you still get the occasional non-responsive back soft key?
I've been playing with this all day and I happened to have the navigation bar enabled testing some stuff out and I haven't had the soft keys become non-responsive yet, so just wondering if anyone else noticed the same thing or if it is just coincidence.
I've been using the Navigation Bar all day (preparing for my move to the Gnexus...lol) and haven't had a problem. I recommend a battery pull, and waiting 1 minute, then booting up again.
Whoops, sorry man, it was directed towards you.<br />Originally Posted by FrenchToast<br />
I've been using the Navigation Bar all day (preparing for my move to the Gnexus...lol) and haven't had a problem. I recommend a battery pull, and waiting 1 minute, then booting up again.
<br />
To whom are you directing your comment?
Whoops, sorry man, it was directed towards you.
Whoops, sorry man, it was directed towards you.
I wanted to add my 2 cents about the battery. It has been draining within about 8 hours over the past few days. I always try to kill tasks that are running before I go to bed. So I am not sure why its not going to sleep.
Also, does anyone else lose service when they turn on wifi? I think its just this stupid replacement phone, but I figured I would throw it out there. I should be receiving a new phone (againx4) today, so I am hoping that that issue is corrected.
No loss of service here when I turn wifi on.
I wanted to add my 2 cents about the battery. It has been draining within about 8 hours over the past few days. I always try to kill tasks that are running before I go to bed. So I am not sure why its not going to sleep.
Also, does anyone else lose service when they turn on wifi? I think its just this stupid replacement phone, but I figured I would throw it out there. I should be receiving a new phone (againx4) today, so I am hoping that that issue is corrected.
I still see the memory settings in the 99memory script in the init.d folder being applied so I don't think that it's broken--at least on my phone.
I think I tracked down the source of the problem. The performance settings in this update seem to be locked. When I try to change the min or max frequences, it always reverts back to 268 min and 1024 max.
Because my init.d file fails to make the cpu changes, it probably skips all settings changes. Or else the same thing that is causing the frequencies to stay locked is locking the voltages too.
I assume that you're using a 3rd party app to oc? Since using the built in performance settings work fine. However, I've actually updated the init.d calls in the next build so it might work better for you.