Originally Posted by nikoola

Damn, 0.9 is faaaaaaaast.
Good job.

BUT... I have problem when i click on on red button and turn off display. I press buttons but display sometimes wan't turn on.
When I go home I will make .avi with this problem.

I know exactly what you're talking about...
It is definitely the fastest ROM I have put together! This one is running at 658MHz, which is not good for your phone! That's why it's freezing. Please flash the older 0.8 version back right away!
I will have this fixed soon!

Originally Posted by cursordroid

I know exactly what you're talking about...
It is definitely the fastest ROM I have put together! This one is running at 658MHz, which is not good for your phone! That's why it's freezing. Please flash the older 0.8 version back right away!
I will have this fixed soon!

Damn i got to try this 658MHz rom
Keep up the great work cursor, are there any speed improvements from 0.7 to 0.8 ?

Thanks

Originally Posted by kassy_ok

Damn i got to try this 658MHz rom
Keep up the great work cursor, are there any speed improvements from 0.7 to 0.8 ?

Thanks

I hope you're not serious... Do not flash the 0.9 ROM!
The clock speed could damage your phone.

Again, to everyone... sorry about this HUGE mistake...

Originally Posted by cursordroid

I know exactly what you're talking about...
It is definitely the fastest ROM I have put together! This one is running at 658MHz, which is not good for your phone! That's why it's freezing. Please flash the older 0.8 version back right away!
I will have this fixed soon!

Thank you verry much.
I will downgrade right now.

What is CPU speed on 0.8? 528MHz or?

I should change the title of my post to read "WAY TOO FAST!"

Processor	: ARMv6-compatible processor rev 2 (v6l)
BogoMIPS	: 657.81
Features	: swp half thumb fastmult edsp java 
CPU implementer	: 0x41
CPU architecture: 6TEJ
CPU variant	: 0x1
CPU part	: 0xb36
CPU revision	: 2
Cache type	: write-back
Cache clean	: cp15 c7 ops
Cache lockdown	: format C
Cache format	: Harvard
I size		: 32768
I assoc		: 4
I line length	: 32
I sets		: 256
D size		: 32768
D assoc		: 4
D line length	: 32
D sets		: 256

Hardware	: sapphire
Revision	: 0080
Serial		: 0000000000000000

Well, you are reading this value from the bogomips field...
Not sure how this is calculated on the armv6l though.

AFAIK, you get the maximum frequency by reading:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

BTW, nicely done, keep up the good work!

Originally Posted by alex___

Well, you are reading this value from the bogomips field...
Not sure how this is calculated on the armv6l though.

AFAIK, you get the maximum frequency by reading:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

BTW, nicely done, keep up the good work!

The bogomips field is an approximation of the CPU speed, which is also used by the Overclock widget and the SetCPU program to determine current clock speed.
I know it's not 100% accurate, but it seems to be causing some problems on the ROM that's for sure.

the bogomips has no relation at all with the CPU speed. It is just an internal delay loop. It is also NO measurement of performance.

See the cpuinfo of my laptop cpu:

jos@roxy ATMH[amh-2.0]$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz
stepping	: 6
cpu MHz		: 800.000
cache size	: 6144 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi flexpriority
bogomips	: 4986.77
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

Originally Posted by cursordroid

The bogomips field is an approximation of the CPU speed, which is also used by the Overclock widget and the SetCPU program to determine current clock speed.
I know it's not 100% accurate, but it seems to be causing some problems on the ROM that's for sure.

If developers are using the bogomips field to get the CPU speed, they have no clue at all about what they're doing, and I would suggest staying away from apps like that mess with kernel settings by devs that have no clue.

Originally Posted by cursordroid

The bogomips field is an approximation of the CPU speed, which is also used by the Overclock widget and the SetCPU program to determine current clock speed.
I know it's not 100% accurate, but it seems to be causing some problems on the ROM that's for sure.

If developers are using the bogomips field to get the CPU speed, they have no clue at all about what they're doing, and I would suggest staying away from apps that mess with kernel settings by devs that have no clue.