[Optimus One, P500 Original Android Development] Hanny:
@voyager

well i guess making performance gov simply forces the cpu to run max even in idle so its abit similar to constant stress test, but i choose stress test cause it can probably test out those "smartass2 ****ing errors" because it allows the governor to work on itself ;)

also just move apps to FAT as few as possible (for me less than 10) and u will be all good lol :p app/dalvik to EXT is already a large memory release for O1's **** internel, dont be greedy or it will really cause bootloops of no reason haha :p

@franco

TIME FOR A FULL REPORT!! :) (sorry if my format is not clear/easy to read enough because ive tried my best to type on my phone)

argh... im sorry franco when i am writing this report cause my results seems not so happy :o

after a whole day of testing, i would like to first make a brief comparison between ur two testing builds on my phone...

[key: ST=setcpu constant Stress Test]

version: 11112011 on the left | 12112011 on the right

-----freq as .32 stable-----

freq: 729mhz | 729mhz

governor: smartass2 | smartass2

time until panic: 20min ST fail | 1h10m ST fail

sub conclusion: improved stability

freq: 729mhz | 729mhz

governor: conservative | conservative

time until fail: 2h ST no error + 10h normal usage | 55m ST fail

sub conclusion: worsened stability

-----1 step down-----

freq: 710mhz | 710mhz

governor: smartass2 | smartass2

time until fail: 1h ST no error + 5h normal usage | 2h50m ST fail

sub conclusion: improved stability

freq: 710mhz | 710mhz

governor: conservative | conservative

time until fail: 1h ST no errors + untested | 2h ST fail

(but refer to the above, 11112011's conservative729 runs 2h ST no error + 10h normal usage before panic, but 12112011's conservative710 runs 2h ST and fail)

sub conclusion: worsened stability

(yes i double checked, i didnt reverse any of them)

BIG conclusion:

(key)12112011 - NEW

(key)11112011 - OLD

- in new one, smartass2 has improved stability, maybe it is because of the lowering values of FSB/BUS tweak.

- however, smartass2 still gives panic/reboots even the freq is 1 step down my .32 stable freq

- in new one, conservative has worsened its stability, however i dont know why because i am not sure of its working principle

- same as above, conservative still gives panics/reboots even the freq is 1 step down my .32 stable freq

- in new one, although it is said that the FSB/BUS tweak has lowered its value, i dont think there is much difference in performance based on my normal usage experience (i dont trust benchs :D)

- but of course both are much more stabler than 02102011

Questions/comments:

- does FSB/BUS tweak affect the working principle of Smartass2? if not, i guess i wont waste time on testing this buggy governor until you fix it :) rather i will focus on other gov such as ur conservative

- i think activating FSB/BUS tweak is the main instability cause of the kernel, it is not activated in .32 right?

- i personally think O1 is quite **** and maybe it cannot handle rocket tweaks which Nexus S can handle :o

- if the tweak is totally disabled, will there be really a serious decrease in performance? eg. back to similar speed as .32?

- if not that serious, i think we can try disabling it because i completely agree stability is important than speed (when we OC we wont choose a fast but unstable freq right :D)

- i really dont care the frames down in comparison to stability, because our phone were supposed to have 40fps and now u nearly double it... lol

- i agree with voyager, and we may disable vsync to compensate the speed loss of decreasing/disabling FSB/BUS

- franco thank you really really really very seriously super damn ****ting holy praying adoring jumping dancing flying much -- for your great developing skills and ur continous + active support on kernels of our **** phone, hope this will finally be stable and i will try my best to test and report to you!! :);):);):)