JDTP5.1 and JDTPL1 with Custom Pagepools + Controlled Battery Testing Results

[themystx2]

any way to change the pagepool without reflashing?

[deviant.ones]

Originally Posted by themystx2

any way to change the pagepool without reflashing?

Not for the TP yet that I know of, all must be done by flashing.

[blkr00t]

I believe that Active Sync which is auto starting is also draining the battery. I am running JD 5 36 MB Dynamic PP and had my first battery drain tonight. After checking it out, I realized that Navigator was running in addition to Gyrator 2 and Sensorlock. I'm going to do the registry settings now to stop Active Sync from auto starting and monitor my battery usage tomorrow. My wife btw, has the TP with a stock sprint ROM and her battery Suxors.....

[deviant.ones]

Originally Posted by blkr00t

I believe that Active Sync which is auto starting is also draining the battery. I am running JD 5 36 MB Dynamic PP and had my first battery drain tonight. After checking it out, I realized that Navigator was running in addition to Gyrator 2 and Sensorlock. I'm going to do the registry settings now to stop Active Sync from auto starting and monitor my battery usage tomorrow. My wife btw, has the TP with a stock sprint ROM and her battery Suxors.....

Activesync is a killer, go to Settings-Personal-Phone-Services-Time Syncronization and uncheck the auto time sync, that is what seems to open up activesync all the time. I noticed about 5-10% better battery life at the end of a normal day after doing this.

[deviant.ones]

Ok, you all owe me since I actually deprived myself of my phone for over 7 hours to test for you all. So far I have tested JDTP5.1 completely stock except for the 1% battery patch with wifi and bluetooth on and phone in airplane mode at 24, 36, and 48 Dynamic for 2 hours, and actually set a timer, and here are the results.

After 2 hours 24 D Pagepool battery was at 92%
36 D Pagepool battery was at 91%
48 D Pagepool battery was at 92%

To make sure it was as accurate as possible I flashed rom with said pagepool, went through customization, applied 1% increment patch, turned on bluetooth and paired to headset, turned on wifi and connected to home network, turned on airplane mode and returned to clock screen. As soon as I had a solid white lite to show a full charge I unplugged and started 2hr timer. I did this each time so there were no phone calls or texts or unneccesary connections to data or activesync so this is as much controlled as I think i can make it. I was planning on testing the three in static but after seeing these results I don't see how the pagepool could be affecting battery life.

And from an electronics point of view, nomatter where the ram is allocated the chip will always draw the same amount of power. In a pc if you watch the voltage of your ram they are identical between a 512mg chip and a 4gb chip so I would imagine the same would hold true for PPC's.

Regardless I am still going to HEX 24, 36, 48 Dynamic and Static Pagepool versions and upload them since I know there are still probably plenty of people that will swear its different even though there not willing to do a truly controlled test.

[sirdevinster]

Originally Posted by deviant.ones

Ok, you all owe me since I actually deprived myself of my phone for over 7 hours to test for you all. So far I have tested JDTP5.1 completely stock except for the 1% battery patch with wifi and bluetooth on and phone in airplane mode at 24, 36, and 48 Dynamic for 2 hours, and actually set a timer, and here are the results.

After 2 hours 24 D Pagepool battery was at 92%
36 D Pagepool battery was at 91%
48 D Pagepool battery was at 92%

To make sure it was as accurate as possible I flashed rom with said pagepool, went through customization, applied 1% increment patch, turned on bluetooth and paired to headset, turned on wifi and connected to home network, turned on airplane mode and returned to clock screen. As soon as I had a solid white lite to show a full charge I unplugged and started 2hr timer. I did this each time so there were no phone calls or texts or unneccesary connections to data or activesync so this is as much controlled as I think i can make it. I was planning on testing the three in static but after seeing these results I don't see how the pagepool could be affecting battery life.

And from an electronics point of view, nomatter where the ram is allocated the chip will always draw the same amount of power. In a pc if you watch the voltage of your ram they are identical between a 512mg chip and a 4gb chip so I would imagine the same would hold true for PPC's.

Regardless I am still going to HEX 24, 36, 48 Dynamic and Static Pagepool versions and upload them since I know there are still probably plenty of people that will swear its different even though there not willing to do a truly controlled test.

Thanks for doing this!

I just reflashed to JDTP5.1 with 24mb static pp. I will use it normally as I would with any given day and post results later. Just a reminder, I had JDTP 5.1 with 48mb dynamic pp prior to this flash where it gave me bad battery life.

[deviant.ones]

Originally Posted by sirdevinster

Thanks for doing this!

I just reflashed to JDTP5.1 with 24mb static pp. I will use it normally as I would with any given day and post results later. Just a reminder, I had JDTP 5.1 with 48mb dynamic pp prior to this flash where it gave me bad battery life.

Well, just remember that "using it normal" is nowhere near a controlled test. Any random data connection that dosn't close properly or activesync that is constantly searching for a connection can kill battery life, unless your willing to do like I did and pretty much give up half a day to make your phone stay in identical environments then your results will never be accurate.

[sirdevinster]

Originally Posted by deviant.ones

Well, just remember that "using it normal" is nowhere near a controlled test. Any random data connection that dosn't close properly or activesync that is constantly searching for a connection can kill battery life, unless your willing to do like I did and pretty much give up half a day to make your phone stay in identical environments then your results will never be accurate.

True...well, thanks again for taking the time to test and post the different results. You saved a lot of folks time by sacrificing yours!

I just don't understand why it went from full charge to no charge in less than 4 hours. I made a few calls, no YouTube, no surfing the net, had ActiveSync communicate with my Exchange Server but that's normal as I always have that running!

I'm lost at this point...lets see what results I'll get from this flash!

[Yay 4 Juggs]

Originally Posted by deviant.ones

Well, just remember that "using it normal" is nowhere near a controlled test. Any random data connection that dosn't close properly or activesync that is constantly searching for a connection can kill battery life, unless your willing to do like I did and pretty much give up half a day to make your phone stay in identical environments then your results will never be accurate.

how does one kill activesync...ive tried!!! i hardly use as anyways

[Merdinh]

Originally Posted by deviant.ones

Well, just remember that "using it normal" is nowhere near a controlled test. Any random data connection that dosn't close properly or activesync that is constantly searching for a connection can kill battery life, unless your willing to do like I did and pretty much give up half a day to make your phone stay in identical environments then your results will never be accurate.

Its the large pagepool thats killing the battery life, and many of us have confirmed this.