• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [BETA]Cyanogen!! Landed!!! :) Go get it![Updated 7/12/2011]

Just read on the CM site. AOSP does not support the powered down charge. That is something that is created on the manufacturer side. Since AOSP was born this way, I will be OK with it. Thanks for the replies.

No problem :)

Just remember the beauty of AOSP...
ANYTHING is possible and can be brought to the table.
I'm sure someone will program and implement this into CM4DX.
It would definitely be a welcomed new feature :D
 
Upvote 0
Is anyone else having some weird battery issues still? Running Nightly 10 and here's what I got:

4 hours and 17 minutes on battery, yet only 70% battery left. Almost all of that time I wasn't even using my phone.


30% Display
24% Phone idle
20% Cell standby
7% Android System
6% ADW.Launcher
5% Android OS
5% Messaging
2% Dialer
2% Swype
2% Voice calls

And when I check out all the running services, I get this:

17MB Settings (1 process)
5.8MB Maps (1 process and 1 service)
4.7MB Market (1 process and 1 service)
8.3MB Google Services (1 process and 1 service)
2.8MB DSPManager (1 process and 1 service)
11MB Swype (1 process and 1 service)

Then there is a whole bunch of stuff being cached in the background like Music, CMStats, and apparently Youtube and Netflix.

121MB of my RAM is being used though, I wonder if that is the cause?

Well given that 30% of the battery use was from the screen, perhaps you used it more than you think.

Also, that isn't terrible battery life. You should have gotten at least 12 hours of battery at that rate. We also don't know exactly how much battery was really used. It could be that it had just dropped to 70% on the display which really means it had closer to 75% left, but the battery display isn't that refined.

You don't have to worry about applications cached in RAM. They don't consume power in that state and being cached in RAM will actually make them use less power when you use the app again because it doesn't have to load from scratch.

You running services look normal (even fewer than I have running). No obvious batter drain there.
 
Upvote 0
Is anyone else having some weird battery issues still? Running Nightly 10 and here's what I got:

4 hours and 17 minutes on battery, yet only 70% battery left. Almost all of that time I wasn't even using my phone.


30% Display
24% Phone idle
20% Cell standby
7% Android System
6% ADW.Launcher
5% Android OS
5% Messaging
2% Dialer
2% Swype
2% Voice calls

And when I check out all the running services, I get this:

17MB Settings (1 process)
5.8MB Maps (1 process and 1 service)
4.7MB Market (1 process and 1 service)
8.3MB Google Services (1 process and 1 service)
2.8MB DSPManager (1 process and 1 service)
11MB Swype (1 process and 1 service)

Then there is a whole bunch of stuff being cached in the background like Music, CMStats, and apparently Youtube and Netflix.

121MB of my RAM is being used though, I wonder if that is the cause?

After 2 hours of no use on my phone (running Nightly 10 as well), I had about 60% left and standby was using about 20% of that.
 
Upvote 0
After 2 hours of no use on my phone (running Nightly 10 as well), I had about 60% left and standby was using about 20% of that.

OK that is a battery issue. I would recommend doing these two things in order:

1) If you have any overclock program installed (even if you are not using it), I would remove the app (or freeze) and wait a couple of days to see if battery life improves.

2) If that doesn't work, or if you don't have a overclock program installed, the I would recommend a SBF back to 2.3.34 and going through the process of installing CM again. In that case, something is messed up and a totally new start will most likely fix the problem. Are you on radio .07 or .12? It should definitely be .07.
 
Upvote 0
OK that is a battery issue. I would recommend doing these two things in order:

1) If you have any overclock program installed (even if you are not using it), I would remove the app (or freeze) and wait a couple of days to see if battery life improves.

2) If that doesn't work, or if you don't have a overclock program installed, the I would recommend a SBF back to 2.3.34 and going through the process of installing CM again. In that case, something is messed up and a totally new start will most likely fix the problem. Are you on radio .07 or .12? It should definitely be .07.

I agree with this....
I was getting only about 8 to 10 hours of battery life when I first flashed CM7, I uninstalled Droid Overclocking and a day later I was getting 16+ hours, which is what I expect to get because that will get me though the day. I have been using quickclock to undervolt my phone (have not seen a reason or need to overclock yet) and this has not hurt my battery in anyway.

Another idea if you are seeing weird results in your battery usage (good battery life, status just look wrong) would be to fully charge, reboot in to recovery, wipe battery stats and then use Battery Calibration.
 
Upvote 0
At the end of my baseband version it says: 12P

Assuming that is my radio, is there a way to get back to .07 ? And what exactly is the benefit in doing so? :thinking: Another words, is it really necessary?
It's not necessary, I actually updated mine to 12P the other day as I read it can help with the 3G signal dropping out, I haven't had any issues at all.
 
  • Like
Reactions: LaZeR
Upvote 0
OK that is a battery issue. I would recommend doing these two things in order:

1) If you have any overclock program installed (even if you are not using it), I would remove the app (or freeze) and wait a couple of days to see if battery life improves.

2) If that doesn't work, or if you don't have a overclock program installed, the I would recommend a SBF back to 2.3.34 and going through the process of installing CM again. In that case, something is messed up and a totally new start will most likely fix the problem. Are you on radio .07 or .12? It should definitely be .07.

This was before I installed Droid overclock and after doing so, my battery life has improved back to where I normally was, about 16-18 hours on heavy use.

How do I check the radio version? For future reference.
 
Upvote 0
I can say that my battery life is much better since freezing the app. I'm not 100% sure that it was the culprit, but I went from getting about 9-10 hours before it ran out of a battery and needed to be recharged to getting 15+ hours and still having battery power left before I go to bed. I typically charge over night and I've never come close to using 100% battery since freezing the app. I think my worst day so far was yesterday (Saturday). I was up at 8am for a swim meet, I listened to Pandora while I did yard work for over an hour on top of my regular phone usage and I still had 30% battery power left when I went to bed at 11:30pm. My overall usage has stayed about the same and freezing the app is really the only change.

I wasn't even using the app to overclock or underclock and decided to freeze it when I noticed that it was a running service all the time (something that is normal I believe). I figured I didn't need it running if I wasn't using it. The next day was the first day I had incredible battery life and it has continued everyday since then.

I see. I guess I'll give it the phone a shot without the app. Thanks for your explanation.
 
Upvote 0
What's the best way to get on the latest nightly from .596 (Apex)?

Flash the CM RC0 MONSTER zip (boot up, then reboot and flash it again?) and then flash the latest nightly over it?

I was on vacation last week and didn't keep up with the multi-hundred page threads that popped up while I was away.

Yup, that should work, don't forget the camera and mms zip fixes afterward.
 
  • Like
Reactions: Scooter70
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones