[5/16] Speed test Silence9 vs SilenceX vs Mighty5 vs SSK2.0 vs STOCK vs Others!

[silence12782]

Originally Posted by larry haben

as far as roms i have a verizon touch pro and i can say i tried all of them the most reliable and stable are from ssk scott. downloaded 2.0 may not be fancy but it is the most stable and reliable

Try the one I just posted you wont be sorry..

[XxXViRuSXxX]

I would like to see the new DB rom on here !!!!!!!

[tsperez]

+1 He just upgraded from 21222 to 21231 (HTC builds).

tsp

Originally Posted by Jboot

I would like to see the new DB rom on here !!!!!!!

[blkr00t]

Originally Posted by scrosler

Thanks!

Thats a very popular quesiton for me these days. I dont have the files anymore nor the phone. Sorry. I did however transfer rights to the ROM to a fellow on XDA who is still supporting the product. I cant remember the chaps name but its a large thread over there.

I found the thread Scott...thanks a bunch...

[silence12782]

Im sure both my new medium and lite will be faster and much better in performance than sr9..

[oldman]

Originally Posted by larry haben

as far as roms i have a verizon touch pro and i can say i tried all of them the most reliable and stable are from ssk scott. downloaded 2.0 may not be fancy but it is the most stable and reliable

I agree with you. It may not be fancy, but that makes it easier for you to "embellish" it with your own personalizations and you can change them as your "whims" desire.

Bob

[Big D5]

Moved to Main TP Forum

[sc00b4s7eve]

Thanks for the benchmarks!
btw, this could be an additional test if you think it's useful:
http://forum.xda-developers.com/show...64#post3723064
For example:
Juicy7 - 090512

Results
--------------------------------
alpha texture (128x256 rgba)
25917 kPixels/s

torus (3k triangles) one light
5536 kPixels/s

color blending
28044 kPixels/s

sub texture (128x128 15x15)
10563 kPixels/s

OpengGL ES info
--------------------------------
Vendor
QUALCOMM, Inc.

Version
OpenGL ES-CM 1.0

Renderer
Q3Dimension MSM7500W 01.02.03 0 5.1.2

Extensions
GL_OES_byte_coordinates
GL_OES_read_format
GL_OES_fixed_point
GL_OES_single_precision_commands
GL_OES_compressed_paletted_texture
GL_OES_matrix_palette
GL_OES_point_sprite
GL_OES_point_size_array
GL_ARB_vertex_buffer_object
GL_ARB_texture_env_combine
GL_ARB_texture_env_dot3
GL_ARB_texture_env_crossbar
GL_ARB_texture_mirrored_repeat
GL_EXT_stencil_wrap
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_blend_func_separate
GL_EXT_blend_equation_separate
GL_ATI_texture_compression_atitc
GL_ATI_extended_texture_coordinate_data_formats
GL_OES_draw_texture

That's all the output info... not that you would need all of it. But it could be interesting to see if the chef's have different drivers/options enabled.

Lastly, the comment about Juicy's pagepool being large with no benefit is not my experience.
FYI - I use alot of additional programs so I set my pagepool at 32Mb. Now, after a few hours of use my RAM settles at about 65% used instead of 70-75% used with the 16Mb pp.

[selytch]

Please help me testing the new ROMs - contribute to PPCGeeks community!

Prerequisites:
1. CorePlayer 1.3.0 (bult 6213) http://badikoff.com/coreplayer130.cab
2. Divx test clip http://badikoff.com/test_clip.divx
3. Stopwatch/timer
put both files on SD card.

Detailed procedure:
1. Install ROM of your choice (I use SD card since its faster)
2. First boot
- Start timer when you press reset button (or when screen goes blank)
- Stop timer when "Tap screen to begin" appears
- Record this time, go through screen calibration
3. Customization time
- Start timer when "Your device will customize in 3 seconds" _disappears_
- Stop timer when screen goes blank
- Note the time and start timer again right away
4. Second boot to start menu
- Timer should be running at this point
- Stop timer when start menu icon appears
5. Note today version (Chome/TF3D/TF3Dv2) - TF3Dv2 has built in calendar
- (if CHome) Settings - Today - Items - Select TF3D
- install core player (from file explorer)
6. Opera speed test
- open Opera, wait for default home to load
- enter "http://www.ibm.com/us/en"
- start timer when you press "go" button or hit enter
- stop timer when progress bar disappears (it may reappear for a second but ignore that)
- type "opera:about" in the address bar and note Opera version
- opera - settngs - privacy - clear cache/cookies/history
7. Third boot
- start timer when pressing reset button
- stop timer when TF3D clock flips to current time
8. Record ROM data
- Settings - System - About (Rom version)
- Settings - System - Memory (Free RAM)
9. CorePlayer test
- Open coreplayer, open the test clip, pause it
- Position playhead at 0:00, Tools - Benchmark and let it run
- note the % from the first line
- exit CorePlayer
10. Repeat opera test and take the best time. Make sure cache/cookies were cleared.
11. Repeat Third boot time and record the best time.

PM me with your results. Your name will be listed as the ROM tester.
Thanks for your help again!

[selytch]

Originally Posted by sc00b4s7eve

Thanks for the benchmarks!
btw, this could be an additional test if you think it's useful:
http://forum.xda-developers.com/show...64#post3723064
For example:
Juicy7 - 090512
[CODE]Results
--------------------------------
alpha texture (128x256 rgba)
25917 kPixels/s

torus (3k triangles) one light
5536 kPixels/s

color blending
28044 kPixels/s

sub texture (128x128 15x15)
10563 kPixels/s

OpengGL ES info
--------------------------------
Vendor
QUALCOMM, Inc.

Version
OpenGL ES-CM 1.0

Renderer
Q3Dimension MSM7500W 01.02.03 0 5.1.2
...
That's all the output info... not that you would need all of it. But it could be interesting to see if the chef's have different drivers/options enabled.

Lastly, the comment about Juicy's pagepool being large with no benefit is not my experience.
FYI - I use alot of additional programs so I set my pagepool at 32Mb. Now, after a few hours of use my RAM settles at about 65% used instead of 70-75% used with the 16Mb pp.

Thanks for the info! Let's see if I can make a standard test out of it...