Mine is 250-1000 for almost a year and running perfectly.

I don't use smartreflex, it doesn't seem to do any good, so I left it off after a couple days of testing.

When idle the CPU goes to 0MHz. My personal setting is 250-805 with SR. I use the starving voltage profile with some VIDs turned up a notch or two just for stability. I have a lot of freqs disabled.

0-->250-->600-->805.

In addition to this I have upthreshold at 93. This means that the phone never goes above 250 unless I am actually using it. i.e. when playing music in my pocket it never goes up to 600.

Only a total noob locks their phone at one constant frequency. It is a dumb as riding a fixed gear bike.

U mad bro? talk about 1/3 extra batterylife!

Nope.

If I don't use 3G data, my battery can run solidly up to 48h.

Even when I HEAVILY use the phone, FM TX, WIFI, GPS and more. I use my phone for everything. WIth or without smartreflex this doesn't matter, at all.


The problem lies with 3G data. If I let my device connected, for example, on MSN, AIM, Skype and DO NOT USE IT, it can run my battery from full to dry in less than 5 hours. Just being connected to 3G data makes my battery die in less than 5hours. If I'm activelly using the phone during this time it will run out about an hour faster.

I don't know why 3G data connection power manager is so bad, but it is. I miss my old E71 whose battery could last for 3 days of HEAVY USE.

well i have no idea about smart reflex, i do feel the already powerful processor is good enough to handle 30 apps at once, i have done that, no issues... but if i wanna install android on it, i want it to be stable, no heat up issues or anything, so what's an idea, and SAFE power for the processor ?

Here everything goes fine with vdd 1 and 2 enabled and:
0,30,180 - 250,30,180 - 500,38,360 - 750,45,430
and:
Ignoring nice load, up threshold=98 and sampling rate=500000 and powersave bias=15(the scalling goveror will have a bias towards making it slower 15 out of 1000 in average)
If it is idle it can stay on for 3 days. If it is working heavily it works for about 3,5 hours. If I put max 500 and minimum light it can stretch to 5.

I also can put it to 750-900 profile with vdd1 and 2 off with sampling at 300000, bias 0 and threshold 75 while I'm out for extra speed.
750,50,430 - 900,58,500.
This way it can work up to 2,5hours.

I tested a lot of configs with different speed combinations and voltages, and the 250-500(low voltages), 250-500-750(low voltages), 250-500-750-900(slightly bigger voltages), 750-900(slightly bigger voltages) were the ones that never failed me. But this is MY phone - particular. It can handle almost starving configs up to 750, but after that it needs more power. LOTS of.

There was just one time that I forced my n900 for 6 straight hours on 750-900 playing mupen64plus, and then it got strange for a week (clumsy - I don't know how to explain), but as phones are not used to self heal, I think that I must have done something else that did the strangeness that I forgot about.

While I'm at it, I have enable vsync at all times. Some phones seem to hang with it, till now my n900 is holding very well. Now even with a lot of things in the desktop, I can still run almost as if nothing was.

Mine's been running at 850mhz ideal for a year now.

No issues at all

Ideal would be 500-1.15Ghz

Smartreflex doesn't do any good, if You tweak Your voltage @ each frequency with care. Guy working in TI already explained everything in SmartReflex thread - it's mostly thing that do good to TI (less chips trashed during Quality Testing), not users. Actually, it can do some good if You're using popular profiles NOT customized for Your device (like titans's predefinied profiles, which I don't reccomend at all), but as well it can do more harm than good by slowly corrupting Your filesystem via undervoltage results. Also, please don'*t spread FUD about 805 not being overclocking at all - even stock 600 mhz run little overvoltaged with Nokia stock voltage settings, in comparision to manufacturer specification.

In summary, SR can do little good or more harm, but NEVER is, was, or will be better, than tweaking voltage for every used CPU frequency and (important!) testing it very extensively. Also, remember to never run on lowest stable edge voltage - battery/proc saving is neglible, but You may fail @ different ambient condition (yea, undervoltage toleration can vary with temperature, humidity, and whatsnot). Personally, I use quite much higher voltage settings that my "discovered" minimal, cause real-life battery runtime doesn't change, and I'm sure that processor runs hapilly on enough energy to never create undervoltage errors.

Said that, i use 500-900 limits. Why 500 lower limit? Cause using that, idle tasks are done 2x faster, than on 250, so i get more 0 mhz time during every second. On 0 mhz, power leakage in transistors is also 0, which You can't said about 250 mhz. Power leakage is derivered from function containing mhz and voltage as basic multipliers, so getting more idle time is always powersaving/ CPU saving win. On the other hand, 900 mhz generates more heat and overall "stress", so I don't want it to run only on two steps of 0 mhz -> 900 mhz, even for idle tasks. Then, 500 mhz isn't overclocking even by strict TI specifications. This way I have 900 mhz when need it, and all steps including 500 for other cases.

I run 950 on ideal as that seems to be best on battery. I've got 1150 on lv for when its needed (desktop icon to toggle)

I used to run 1150mhz as a daily without problems for about 1 year, dropped it for better battery.

i can't enable Smartreflex witjh ideal setting.

restart before load :/ .p

thats mean 250-850 limit.

just with VD1 it restarts, any help? should i got to 805mhz? or maybe its something with voltage?