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

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

I know it's a little early to be reporting battery life but....

screenshot-1325293280127.png


Only 2% use after one and a half hours.. and that's WITH 40% time without a signal!
My drainage before has NEVER been less than 4% per hour.

Mantera, Whyzor you guys are awesome!! It's so nice that you are are both working together to produce a killer ROM. Thank you!

Big thanks to Tickerguy and Issac for laying the groundwork.

Needless to say, the phone does enter deep sleep now and my battery life is unprecedented.
Can't wait to see how many hours this charge is going to last!! :)

PS: Accelerometer is still functioning normally, but I'll need to wait at least twenty fours before I can report if the fix is successful. So far, so good.

EDIT: 2hrs 11mins and 97% left. So that's 1.5% per hour.
 
ziggy46 said:
the only thing i noticed bad about this rom is low in call volume... on regular cm7 the volume is normal :D
Click to expand...

I think I've had the same problem but wondered if it was my imagination.

I'm not saying DSP Manager is bad. MANY people like it.. but I've found the app "Volume+" available on the Market to do a very good job at increasing call volume as well as headset volume. Very effective.

I may just not be using DSP Manager correctly, but I can't get it to perform as well as I would like.
 
britton1981 said:
I think I've had the same problem but wondered if it was my imagination.

I'm not saying DSP Manager is bad. MANY people like it.. but I've found the app "Volume+" available on the Market to do a very good job at increasing call volume as well as headset volume. Very effective.

I may just not be using DSP Manager correctly, but I can't get it to perform as well as I would like.
Click to expand...
1. DSP Manager is a equalizer, enough said....
2. Thanks for the reference, Volume+ IS AWSOME TO THE MAX ESPECIALLY THE PAID VERSION
3. I have download every sound boosting app that works(5), i'm happy now
 
idbl_fanatic said:
So, the 12/30 release seems to have fixed the sensor issue that I was having, thanks!!
Click to expand...

Good to hear.

About the volume issue, it could be DSPmanager messing with things since it comes default with CM7 ROMs. I normally remove a lot of junk when I install a ROM, and DSPManager is one of them, haven't noticed any problems with call volume.
 
@britton1981,
I registered just now so I could ask you, WHAT are your current settings on your phone?? I'm getting horrendous battery life on this ROM! I've got a constant 100% TWS (Which I'm very sure that this is the main reason).

Could you please reply with your details?
PRL:
CPU Gov:
CPU Min:
CPU Max:

I'd like to see if I could get close to your battery life
 
britton1981 said:
I know it's a little early to be reporting battery life but....

screenshot-1325293280127.png


Only 2% use after one and a half hours.. and that's WITH 40% time without a signal!
My drainage before has NEVER been less than 4% per hour.

Mantera, Whyzor you guys are awesome!! It's so nice that you are are both working together to produce a killer ROM. Thank you!

Big thanks to Tickerguy and Issac for laying the groundwork.

Needless to say, the phone does enter deep sleep now and my battery life is unprecedented.
Can't wait to see how many hours this charge is going to last!! :)

PS: Accelerometer is still functioning normally, but I'll need to wait at least twenty fours before I can report if the fix is successful. So far, so good.

EDIT: 2hrs 11mins and 97% left. So that's 1.5% per hour.
Click to expand...

What is your cpu settings and are u using 3g or wifi?
 
APag96 said:
@britton1981,
I registered just now so I could ask you, WHAT are your current settings on your phone?? I'm getting horrendous battery life on this ROM! I've got a constant 100% TWS (Which I'm very sure that this is the main reason).

Could you please reply with your details?
PRL:
CPU Gov:
CPU Min:
CPU Max:

I'd like to see if I could get close to your battery life
Click to expand...

djboi2011 said:
What is your cpu settings and are u using 3g or wifi?
Click to expand...

Here are some other battery saving tips:

http://androidforums.com/triumph-all-things-root/473481-discussion-ways-you-save-battery.html

http://androidforums.com/motorola-triumph/461571-guide-triumphant-battery-tips.html
 
Whyzor said:
Here are some other battery saving tips:

http://androidforums.com/triumph-all-things-root/473481-discussion-ways-you-save-battery.html

http://androidforums.com/motorola-triumph/461571-guide-triumphant-battery-tips.html
Click to expand...

Believe me, I've read through every guide there is about battery saving on Android phones (including those two). I've never managed to have a charge throughout the entire day.

I'm running JuiceDefender, and only use 3G. No GPS or WiFi. I'm also not overclocking at all.

I would just really like to know your personal settings on you phone, if you don't mind posting them (which I don't see why you would) :)
 
APag96 said:
Believe me, I've read through every guide there is about battery saving on Android phones (including those two). I've never managed to have a charge throughout the entire day.

I'm running JuiceDefender, and only use 3G. No GPS or WiFi. I'm also not overclocking at all.

I would just really like to know your personal settings on you phone, if you don't mind posting them (which I don't see why you would) :)
Click to expand...

PRL: default VM
Min: 61 (same when I had 122 & 245 Mhz)
Max: 1024
Governor: interactive

These settings won't make much of a difference to explain the kind of battery life you're getting. The 100% TWS is probably it, meaning the phone can't get a signal and has to keep sending at max power frequently to try to get one. Either you're in a bad area, or there's a problem with the phone's radio.
 
Whyzor said:
PRL: default VM
Min: 61 (same when I had 122 & 245 Mhz)
Max: 1024
Governor: interactive

These settings won't make much of a difference to explain the kind of battery life you're getting. The 100% TWS is probably it, meaning the phone can't get a signal and has to keep sending at max power frequently to try to get one. Either you're in a bad area, or there's a problem with the phone's radio.
Click to expand...


Thank you very much! The weird thing is that my phone usually has at least 1 bar of signal. Sooo, 100% TWS is abnormal.
 
I am still on the same charge as yesterday (about 24 hours now) and I just hit the 50% mark :D

Also want to report that after almost 24 hours without reboot, the accelerometer fix looks effective! Thanks, Whyzor!!

My following post probably belongs in a battery life thread so please forgive me:

These are my opinions, so please share yours if they happen to differ with mine. I'm always eager to learn from others experiences.
I used to be a fan of the conservative cpu governor as default thinking it would save battery life but I realized that it just made the processor work harder and longer to complete a task rather than ramping to the speed necessary and get it over with.
I use ondemand governor with 95% up threshold overclocked to 1401mHz and undervolted according to mantera's "more aggressive" tables listed here: http://androidforums.com/triumph-al...kernel-mt-isaac-tg-based-cm7.html#post3426876
I do have a screen off profile of conservative governor min61/max1024.

I have tested both governors thoroughly and I found that conservative governor drained the phone slightly more than ondemand by about 3%. I'm no saying ondemand is the best, but it's certainly better than conservative especially in terms of performance (which is obvious). Alot of people prefer interactive or smartass but I personally find both of those to stay at higher frequencies a bit longer than ondemand. Ondemand seems to ramp up and immediately ramp down to minimum.

One thing to do if you haven't already: LOSE YOUR AUTO TASK KILLER. They were helpful before Froyo but now they only make your phone work harder by immediately restarting tasks that were killed and create a constant cycle of CPU activity which only drains your battery faster. You can tweak your phones internal memory management system and there is absolutely no benefit to using Auto Task Killer, although some may disagree with me.

I am using the stock PRL. Swapping PRL's does not make a difference and may actually have a negative effect.
Here's why:

  1. PRLs are not a list of towers. They are a list of SIDs - geographic regions. As long as your phone knows about a given SID, it will automatically find new towers within that SID. AFAIK, Sprint has not added a new SID for years. BatonRougeBroadband.Info - Home Have a look and see how there are no lists of towers, only SIDs, carriers, priorities, and frequencies.
  2. Roaming, in the context of a PRL, means leaving your home SID, not roaming to another carrier. Therefore, VM phones need a PRL to know what to do when you leave your home area.
  3. I haven't looked at the PRLs for the latest VM phones, but they used to use standard Sprint PRLs, and disallow roaming to other carriers in firmware.
  4. Even if you managed to hack your phone to allow roaming to other carriers, you still couldn't authenticate to those carriers. In other words, doing all that work would only result in a message to "Call 611 to establish service", or something similar.
  5. Carriers that allow roaming to other carriers are constantly updating their PRLs to reflect changes in agreements with other carriers. Carriers get added and dropped, and roaming priorities get changed. That is why Sprint postpaid users (for example) are always on the lookout for new PRLs. And updating a PRL is sometimes a step backwards. You may get worse service, not better.
  6. Anyone seeing an "improvement in reception" after hacking their PRL is more likely seeing an artifact of cellular breathing.
 
Also, if you are using Auto Task Killer, a better alternative is an app like "Watchdog" which monitors your background CPU activity and alerts you of an "out of control" or "rogue" app. Your biggest battery drain is most definitely the "time without a signal" percentage, but you may also want to see if you have an app that is draining your battery in the background. It has helped me on occasion.

As for the abnormal "Time Without a Signal" check out this thread: http://forum.xda-developers.com/showthread.php?t=1228629
 
APag96 said:
Thank you very much! The weird thing is that my phone usually has at least 1 bar of signal. Sooo, 100% TWS is abnormal.
Click to expand...
I have no idea if this is remotely correct, but I've found that my TWS gets higher when I have bad signal. I rarely have no signal but often have bad signal, which seems to be considered "no signal."
 
JokaLo said:
Do I need to reflash before the boot tho it said "same process"
Click to expand...

If you are coming from stock then it is the "same process" to install as Tickerguys Final CM7.

If you are updating from Tickerguy's CM7 just simply flash the ROM and reboot. No need to flash gapps unless you perform a factory reset (which you don't need to do but just wipe cache and dalvik cache)
 
A couple of questions before I decide to flash this:

1) Does Go Launcher work well with it? It has been very good on the TG CM7 so just checking.

2) I have never flashed another ROM besides the TG CM7: when I do will everything have to be set up again (app reinstall etc) or will that not occur because I won't be doing the factory reset?
 
wigginst said:
A couple of questions before I decide to flash this:

1) Does Go Launcher work well with it? It has been very good on the TG CM7 so just checking.

2) I have never flashed another ROM besides the TG CM7: when I do will everything have to be set up again (app reinstall etc) or will that not occur because I won't be doing the factory reset?
Click to expand...
1) Go Launcher works fine for me
2) This is basically just an updated version of TG's CM7, so no, as long as you don't factory reset, just clear cache/dalvik and flash it.
 
So I flashed the Rom after clearing cache and davlik cache but the phone keeps rebooting after being up for a few minutes. Thoughts?
 
On the performance setting. Would that cause it?

Just recleared the cache settings and reflashed. We'll see how it goes!
 
You must log in or register to reply here.
Back
Top Bottom