Performance Question

[Guest Richard T]

Hi all,

I am running the stock Samsung rom that came with my O2, PDA version i8000XXII9, and have noticed something odd.

If I have the performance profile set to auto, the start menu and titanium run smoothly, however the Task Switch and Cube interface has a noticable judder to it. Changing the profile to Low or Normal and you can see the frame rate drop on Titanium however the Task Switcher runs perfectly (as does Cube in the Normal profile), which does not make much sense to me. The only way to get both to run smoothly is setting the CPU to High, which kills the battery.

Does anyone else notice this, and is it something that is fixed in later roms. Although I have a standard rom, I have disabled quite a lot of the Samsung stuff, and have ~60mb ram free.

Ta

Rich

[Guest Richard T]

Just me then I guess :) lol

[Guest bluhound]

You're not the only one. I have the same problem too so what I did was setting performance to high, run FPU Enabler and overclock CPU to 920Mhz (higher than that and I get random crashes).

Average battery lifespan for me is 1 1/2 days per charge, not a major concern as I charge my phone battery every evening.

[Guest Tylwith]

Hi all,

I am running the stock Samsung rom that came with my O2, PDA version i8000XXII9, and have noticed something odd.

If I have the performance profile set to auto, the start menu and titanium run smoothly, however the Task Switch and Cube interface has a noticable judder to it. Changing the profile to Low or Normal and you can see the frame rate drop on Titanium however the Task Switcher runs perfectly (as does Cube in the Normal profile), which does not make much sense to me. The only way to get both to run smoothly is setting the CPU to High, which kills the battery.

Does anyone else notice this, and is it something that is fixed in later roms. Although I have a standard rom, I have disabled quite a lot of the Samsung stuff, and have ~60mb ram free.

Ta

Rich

task switcher and cude are opengles 2 .titanium is a normal program.

so when you use the 3d one you are not using the same part of the processor.

[Guest Richard T]

task switcher and cude are opengles 2 .titanium is a normal program.

so when you use the 3d one you are not using the same part of the processor.

So the results that I am getting almost suggest that setting the performance profile between auto and normal affects how 3d apps are processed maybe - auto running them via cpu and any other profile kicking the 3d processor into action?

I am thinking it is more just a quirk of the setup on mine though, as surely that would not be the case?

[Guest Ender Psp]

The judder you mention might be due to the cpu freq switching. If the cpu senses it needs more power it will switch to a higher frequency (and lower complement). I imagine this switching is done on-the-fly and some apps might not take it very well.

[Guest bluhound]

task switcher and cude are opengles 2 .titanium is a normal program.

so when you use the 3d one you are not using the same part of the processor.

The judder you mention might be due to the cpu freq switching. If the cpu senses it needs more power it will switch to a higher frequency (and lower complement). I imagine this switching is done on-the-fly and some apps might not take it very well.

That makes sense...... :)

[Guest dwallersv]

The judder you mention might be due to the cpu freq switching. If the cpu senses it needs more power it will switch to a higher frequency (and lower complement). I imagine this switching is done on-the-fly and some apps might not take it very well.

It's a nice theory, but unfortunately completely wrong.

Frequency changes in controllable CPUs do not cause any blips, pauses, or interruption of program execution that is detectable at all.