[ROM][GINGERBREAD] CyanogenMOD 7 Nightly Builds.

I hear what you're saying. It's so cliche but I'm such a minimalist that I did uninstall all non-system apps and still couldn't figure it out. I thought there was a program called Spare Parts or something that would make troubleshooting this a breeze? Not going to try a full wipe again unless I have too.
 
I hear what you're saying. It's so cliche but I'm such a minimalist that I did uninstall all non-system apps and still couldn't figure it out. I thought there was a program called Spare Parts or something that would make troubleshooting this a breeze? Not going to try a full wipe again unless I have too.
Hopefully somebody else has a better way.. I had similar problem and thats what I did. It worked for me. Great battery life.
 
I hear what you're saying. It's so cliche but I'm such a minimalist that I did uninstall all non-system apps and still couldn't figure it out. I thought there was a program called Spare Parts or something that would make troubleshooting this a breeze? Not going to try a full wipe again unless I have too.
Ok heres something you can compare to mine. See attached screenshots. Use Spare parts and Battery Usage Statistics. Hope this helps. Compare times and what not
 
  • Like
Reactions: wkupike2000
just tried to dl 173 and it said couldn't complete because there was not enough space on phone. I don't have that much stuff on the phone any ideas
 
Ok heres something you can compare to mine. See attached screenshots. Use Spare parts and Battery Usage Statistics. Hope this helps. Compare times and what not
Got Spare Parts, thanks for the screenshots. That helped me know what to look for. ADW is my biggest culprit except for Google Reader. ADW is in the 600k's but Google Reader is in the 2 millions ms.

How do I know what is a good or normal number of ms? Maybe I have a weird Google Reader setting
 
Got Spare Parts, thanks for the screenshots. That helped me know what to look for. ADW is my biggest culprit except for Google Reader. ADW is in the 600k's but Google Reader is in the 2 millions ms.

How do I know what is a good or normal number of ms? Maybe I have a weird Google Reader setting
I would compare to good acting apps, and then consider usage vs time. High time with low usage would indicate its using the battery in the background. Usage is something you determine.. subjective. Exampls: Don't use hulu app that much..why is time so high?? Check settings, etc.
 
  • Like
Reactions: wkupike2000
About to flash new radio then 166, on 80 or 90-something now. Hopefully that might help my issue some.

But I need to know how to determine what is DEVOURING my battery. I have the Seido Innocell 1750 & hardly ever download any apps so there's only so much that could be draining it. I turn it off at night so that it gets the full bump charge yet my gf's Incredible 2 kills mine in battery life.

Ex: Sat we both take off charger at 10 am. She texts,talks, and plays games the majority of a 2 hour car ride. I check a couple texts and an email, that's it. By noon I have 75% she has 90%. She continues to use hers a ton and I only check my texts a couple times per hour. Yet by 5 pm I'm needing a charge at 14% and she's still at 69%. Could it be my ROM or how can I investigate this?

Thanks!

The DInc2 does get better battery life than the OG DInc out of the box, so it's tough to do a real comparison between the two. Newer chips, less hardware drain.

In addition t the kernel and checking your sync frequencies, be a Radio Fascist. Make sure BT, GPS, WiFi are off when not needed. Are you syncing Facebook - that's always a good place to look for a battery suck.
 
The DInc2 does get better battery life than the OG DInc out of the box, so it's tough to do a real comparison between the two. Newer chips, less hardware drain.

In addition t the kernel and checking your sync frequencies, be a Radio Fascist. Make sure BT, GPS, WiFi are off when not needed. Are you syncing Facebook - that's always a good place to look for a battery suck.

This is how Pville got advisor status, and he's correct. Make sure all additional functions are turned off if not being used. If you use Facebook, Twitter, Google+, etc., set the synch time to either maximum or manual. Make sure you use auto brightness and set screen timeout to a minute. Also, background colors will also eat battery when the screen is on. It seems that a darker wallpaper will use less juice than a bright one.
 
  • Like
Reactions: PvilleComp
While I'm thinking about it, any known issues with 168? That was my last update mainly because I don't like recustomizing my phone, but since 168, my phone has randomly rebooted twice so far. Once today and once over the weekend.
 
I didn't have any problems with 168 other than the Blue tooth issue that is still haunting me on 164 - I'm going to test with 151 and see if BT works correctly again. If not I guess I'm Full Wipe City :(
 
Last edited:
Everyone seems to be having problems right now. (OK, probably not EVERYONE, but a lot). I flashed 170 and everything seems to be working fine, although, I don't use bluetooth, so I can't say anything about that.

Glad I made the switch to CM7. Noone was lying about battery life, customization, etc. Daily ROM now.
 
  • Like
Reactions: mldiroff
This is how Pville got advisor status, and he's correct. Make sure all additional functions are turned off if not being used. If you use Facebook, Twitter, Google+, etc., set the synch time to either maximum or manual. Make sure you use auto brightness and set screen timeout to a minute. Also, background colors will also eat battery when the screen is on. It seems that a darker wallpaper will use less juice than a bright one.

I agree he's the best! And so are all you others that have offered assistance. It makes absolutely no sense as nothing is showing abnormal in Spare Parts, I turn Wifi off anytime I'm not using it, and I don't use GPS or Bluetooth. My Facebook updates are set to max interval so I'm just baffled. Even without comparing the Dinc2, I used to get a full day just a few months ago and now I'm charging by 5 p.m. I'll keep fighting the good fight though!!
 
  • Like
Reactions: PvilleComp
I agree he's the best! And so are all you others that have offered assistance. It makes absolutely no sense as nothing is showing abnormal in Spare Parts, I turn Wifi off anytime I'm not using it, and I don't use GPS or Bluetooth. My Facebook updates are set to max interval so I'm just baffled. Even without comparing the Dinc2, I used to get a full day just a few months ago and now I'm charging by 5 p.m. I'll keep fighting the good fight though!!

My apologies if I missed this, but for grins and giggles, have you tried another battery?
 
Downloading 173 now. Although I've only had 2 reboots in the past 2 weeks, one was during a phone call and I missed a great photo op because of the other. :-( Ah well, still proud to be a contributing member of the AOSP!!!

EDIT: Just flashed 173. Will advise of any random reboots.
 
Last edited:
I finally got my !@#@$#@! Bluetooth problem fixed. After 3 downgrade flashes, it went into Boot loop Hades and so I restored my last nandroid of #151 and it works again.

My problem with Bluetooth was that after connecting to BT and then disconnecting, I could not make or receive calls. Data was fine and notifications worked fine, but no calls. A reboot would fix it. Since I spend a lot of time driving this is no good. :(

Hopefully once Cyanogen gets settled, there will be more approvals to the builds and this can get fixed.
 
I agree he's the best! And so are all you others that have offered assistance. It makes absolutely no sense as nothing is showing abnormal in Spare Parts, I turn Wifi off anytime I'm not using it, and I don't use GPS or Bluetooth. My Facebook updates are set to max interval so I'm just baffled. Even without comparing the Dinc2, I used to get a full day just a few months ago and now I'm charging by 5 p.m. I'll keep fighting the good fight though!!

You may not use BT or GPS, but check to see if they are on. Even when not in use they will "ping" or search for signal on a periodic basis looking for a connection.
 
I finally got my !@#@$#@! Bluetooth problem fixed. After 3 downgrade flashes, it went into Boot loop Hades and so I restored my last nandroid of #151 and it works again.

My problem with Bluetooth was that after connecting to BT and then disconnecting, I could not make or receive calls. Data was fine and notifications worked fine, but no calls. A reboot would fix it. Since I spend a lot of time driving this is no good. :(

Hopefully once Cyanogen gets settled, there will be more approvals to the builds and this can get fixed.

Glad you got it working again. I wanted the convenience of a bt without a bt headset. I ended up getting a cassette adapter and connecting it to my phone so I can listed to XM while in the car. Now when my phone rings in the car, it plays through the radio speakers. It works for me. :D
 
My apologies if I missed this, but for grins and giggles, have you tried another battery?

Honestly no and maybe I should. I have my original OEM battery and could try that instead of the Seido extended battery. You think that actually might be it?
 
Honestly no and maybe I should. I have my original OEM battery and could try that instead of the Seido extended battery. You think that actually might be it?

It couldn't hurt to try. It may not be the battery, but at least you can say you tried another one.
 

Trending Posts

Members online

Forum statistics

Threads
956,907
Messages
6,970,556
Members
3,163,648
Latest member
crayzeefoo