Jump to content

ROM for performance


Guest david_dawkins
 Share

Recommended Posts

Guest david_dawkins

My Pulse is either:

1. out of battery

or

2. too slow to be useful

I'm running 2.2.1 with CyanogenMod-6.1.0-RC0-Pulse.

I've got JuiceDefender installed, got the SetCPU o/c cranked. I leave data off all the time now.

The 2.x bling is nice, but not at the expense of a usable handset. Does anyone have 2.x installed and have a useful phone, or did you go back to 1.5? Any tips or links to articles that tune our beloved Pulses?

Thanks

Dave

PS By "useful" I mean "no lag". I haven't got time to wait for the phone to wake up and decide to let me text, phone, take pics..

EDIT: Found this thread with some good advice in it. Thanks for reading. http://android.modaco.com/content/t-mobile...attery-problem/

Edited by david_dawkins
Link to comment
Share on other sites

Guest Daz555

1.5 was horrific, would never go back to that shambles.

2.1 custom ROMS with swap have been excellent imo - as fast as can be expected but more importantly, reliable. Swap was important in that it improved speed and killed off the SMS bug which originally came with official 2.1 releases.

My sig has my current setup.

Edited by Daz555
Link to comment
Share on other sites

Guest jimmie32

I think the phone does lag a bit sometimes because when its in sleep it is on 122MHz (setting it this low does result in *some* delay in SMS and calls), and when you wake it up, it has to step the CPU up from 122MHz all the way up to [your max frequency].

The CPU has to be stepped up in small increments; according to the frequency stats, its 122/245/320/480/528/576/595/614/633/652/672/691/710, so as you can see, if you overclock it, it will take longer to step all the way up to 710.4MHz from 122.88MHz, so it will result in a little lag as the CPU scales. In non-overclocked versions, its 122->245->320->480->528 (stock pulse's maximum CPU speed), so as you can see, it takes significantly less steppings than going from 122 to 710, so it might be a little faster <citation needed>

I got a huge 2400mAh battery (a 3rd party one) for my pulse, which is about 900mAh (60% more) more than the stock pulse's battery, so I leave the CPU on 672/710, so when it wakes up it is only two steppings away from the maximum performance - I have a huge battery so it doesn't matter - and it holds up roughly 4 days (including standby and I turn it off at night) on a full charge.

(With more active usage its about 2.5 days though - I got used to making the pulse hit the charger as soon as I get home now)

So, this solves the slow problem. As for the battery, you can just underclock the CPU, CM6 is pretty fast on 528MHz last time I tried... not as fast as 710 but still fast.

Going back to 1.5 makes no difference for me - though I can't even go back to 1.5, there's no 1.5 fallback for my device (hell, I forgot to nandroid it...) - I remember that it held up as long as my current CM6 install. So... not worth it. But you could try.

Resumed: Happy 2.2 CM6 user here. No battery issues (though not using stock battery). :D

Link to comment
Share on other sites

Guest hunk74

I have Tom G's 2.2 with DarkTremors a2sd, cache2sd (aka swap) enabled.

This little trick solves the low/out of memory problems the Pulse seems to be encountering with OS versions 2.1 and up.

The device is stable as a rock and UI is fast too.

Highly recommended to add to your custom rom setup especially for a lowmem/minimum spec. device like the Pulse.

Edited by hunk74
Link to comment
Share on other sites

Guest Casterina

Cyanogen Pulse Plus is very good... i recommend you use that MOD.. I'm waiting til the fixes for Gingerbread Pulse are done.

Link to comment
Share on other sites

Guest eckengucker1
I think the phone does lag a bit sometimes because when its in sleep it is on 122MHz (setting it this low does result in *some* delay in SMS and calls), and when you wake it up, it has to step the CPU up from 122MHz all the way up to [your max frequency].

The CPU has to be stepped up in small increments; according to the frequency stats, its 122/245/320/480/528/576/595/614/633/652/672/691/710, so as you can see, if you overclock it, it will take longer to step all the way up to 710.4MHz from 122.88MHz, so it will result in a little lag as the CPU scales. In non-overclocked versions, its 122->245->320->480->528 (stock pulse's maximum CPU speed), so as you can see, it takes significantly less steppings than going from 122 to 710, so it might be a little faster <citation needed>

I got a huge 2400mAh battery (a 3rd party one) for my pulse, which is about 900mAh (60% more) more than the stock pulse's battery, so I leave the CPU on 672/710, so when it wakes up it is only two steppings away from the maximum performance - I have a huge battery so it doesn't matter - and it holds up roughly 4 days (including standby and I turn it off at night) on a full charge.

(With more active usage its about 2.5 days though - I got used to making the pulse hit the charger as soon as I get home now)

So, this solves the slow problem. As for the battery, you can just underclock the CPU, CM6 is pretty fast on 528MHz last time I tried... not as fast as 710 but still fast.

Going back to 1.5 makes no difference for me - though I can't even go back to 1.5, there's no 1.5 fallback for my device (hell, I forgot to nandroid it...) - I remember that it held up as long as my current CM6 install. So... not worth it. But you could try.

Resumed: Happy 2.2 CM6 user here. No battery issues (though not using stock battery). :D

Any ebay links for the battery? Sounds really interesting!

Link to comment
Share on other sites

Guest Madail
I think the phone does lag a bit sometimes because when its in sleep it is on 122MHz (setting it this low does result in *some* delay in SMS and calls), and when you wake it up, it has to step the CPU up from 122MHz all the way up to [your max frequency].

The CPU has to be stepped up in small increments; according to the frequency stats, its 122/245/320/480/528/576/595/614/633/652/672/691/710, so as you can see, if you overclock it, it will take longer to step all the way up to 710.4MHz from 122.88MHz, so it will result in a little lag as the CPU scales. In non-overclocked versions, its 122->245->320->480->528 (stock pulse's maximum CPU speed), so as you can see, it takes significantly less steppings than going from 122 to 710, so it might be a little faster <citation needed>

I got a huge 2400mAh battery (a 3rd party one) for my pulse, which is about 900mAh (60% more) more than the stock pulse's battery, so I leave the CPU on 672/710, so when it wakes up it is only two steppings away from the maximum performance - I have a huge battery so it doesn't matter - and it holds up roughly 4 days (including standby and I turn it off at night) on a full charge.

(With more active usage its about 2.5 days though - I got used to making the pulse hit the charger as soon as I get home now)

So, this solves the slow problem. As for the battery, you can just underclock the CPU, CM6 is pretty fast on 528MHz last time I tried... not as fast as 710 but still fast.

Going back to 1.5 makes no difference for me - though I can't even go back to 1.5, there's no 1.5 fallback for my device (hell, I forgot to nandroid it...) - I remember that it held up as long as my current CM6 install. So... not worth it. But you could try.

Resumed: Happy 2.2 CM6 user here. No battery issues (though not using stock battery). :D

Where do you get that battery?

Link to comment
Share on other sites

Guest jimmie32

Well, there's a huge electronics city here in Beijing, China. Got the battery there.

You could try checking out eBay for batteries compatible with HB4F1 (model no. printed on the back of your pulse's battery). Or, just check the size, and the voltage (3.7V idle, 4.2V on charge) and you might find one. :)

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.