Comments on: A small guide…to J2me benchmark/test midlets http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets/ Technology, wireless, games...and more..... Wed, 19 Nov 2008 11:37:24 +0000 http://wordpress.org/?v=2.5 By: TomSoft » MobileZoo: the definitive museum for mobile diversity http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets/#comment-9527 TomSoft » MobileZoo: the definitive museum for mobile diversity Thu, 05 Oct 2006 20:38:57 +0000 http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets#comment-9527 [...] One of the initial idea (I am just over simplifiying, as there are many ideas in the air here!) was the following: instead of creating specific benchmark to provide information about handsets, or to create your own code to gather this information and store it on your server, why not provide a service for this? The ideas is to create a small library (less than 8kb) that can be easily embedded on most (if not all) J2me application. The library than gather the maximum of information about the handset and send them to a server. This server then maintains a database about handset capacities, supported JSR, configuration, etc…. There are multiple benefits on this approach: [...] […] One of the initial idea (I am just over simplifiying, as there are many ideas in the air here!) was the following: instead of creating specific benchmark to provide information about handsets, or to create your own code to gather this information and store it on your server, why not provide a service for this? The ideas is to create a small library (less than 8kb) that can be easily embedded on most (if not all) J2me application. The library than gather the maximum of information about the handset and send them to a server. This server then maintains a database about handset capacities, supported JSR, configuration, etc…. There are multiple benefits on this approach: […]

]]> By: Davide http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets/#comment-8378 Davide Tue, 12 Sep 2006 14:28:05 +0000 http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets#comment-8378 FPC Bench is not focused on speed only. FPC Bench is a java benchmark to test and compare the performance of a phone with others phones. Differently from other benchmarks, FPC Bench results are not influenced from the screen resolution; this is a good way to get more reliable results. FPC Bench is a complete test tool to test performance and features. - CPU/Memory benchmark - Check for total heap memory size - Check for free heap memory size - Check for full screen's maximum resolution in a Java canvas - Check for double buffering - Check for RMS size - Check for RMS speed - Check for available profile/configuration - Check for the latest APIs: JSR 75: File System access API. JSR 82: Bluetooth/OBEX API. JSR 118: Mobile Information Device Profile API. JSR 120: Wireless Messaging API (WMA 1.1). JSR 135: Multimedia API (MMAPI) JSR 139: Connected Limited Device Configuration 1.1 JSR 172: Wev service specification. JSR 177: Security and Truste Services API. JSR 179: Location API. JSR 180: SIP API. JSR 184: Mobile 3D Graphics. JSR 185: Java Tech for Wireless Industry API. JSR 205: Wireless Messaging API (WMA 2.0). JSR 209: Advanced graphics and user interface. JSR 211: Content Handler API. JSR 226: Scalable 2D vector graphics for JavaME. JSR 229: Payment API. JSR 234: Advanced Multimedia API. JSR 238: Mobile internationalization API. JSR 239: Java binding for OpenGL ES. JSR 257: Contactless communication API. I think that is much more than a speed benchmark. FPC Bench is not focused on speed only.

FPC Bench is a java benchmark to test and compare the performance of a phone with others phones. Differently from other benchmarks, FPC Bench results are not influenced from the screen resolution; this is a good way to get more reliable results.

FPC Bench is a complete test tool to test performance and features.

- CPU/Memory benchmark
- Check for total heap memory size
- Check for free heap memory size
- Check for full screen’s maximum resolution in a Java canvas
- Check for double buffering
- Check for RMS size
- Check for RMS speed
- Check for available profile/configuration
- Check for the latest APIs:
JSR 75: File System access API.
JSR 82: Bluetooth/OBEX API.
JSR 118: Mobile Information Device Profile API.
JSR 120: Wireless Messaging API (WMA 1.1).
JSR 135: Multimedia API (MMAPI)
JSR 139: Connected Limited Device Configuration 1.1
JSR 172: Wev service specification.
JSR 177: Security and Truste Services API.
JSR 179: Location API.
JSR 180: SIP API.
JSR 184: Mobile 3D Graphics.
JSR 185: Java Tech for Wireless Industry API.
JSR 205: Wireless Messaging API (WMA 2.0).
JSR 209: Advanced graphics and user interface.
JSR 211: Content Handler API.
JSR 226: Scalable 2D vector graphics for JavaME.
JSR 229: Payment API.
JSR 234: Advanced Multimedia API.
JSR 238: Mobile internationalization API.
JSR 239: Java binding for OpenGL ES.
JSR 257: Contactless communication API.

I think that is much more than a speed benchmark.

]]> By: Wendong http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets/#comment-6726 Wendong Wed, 02 Aug 2006 04:15:24 +0000 http://blog.landspurg.net/a-small-guideto-j2me-benchmarktest-midlets#comment-6726 I believe j2mepolish actually offers a Java ME client which covers testing like keycode, jsr, screen etc. MicroCode project also collects a rich set of J2ME attributes in text files: http://j2me-device-db.sourceforge.net I believe j2mepolish actually offers a Java ME client which covers testing like keycode, jsr, screen etc.

MicroCode project also collects a rich set of J2ME attributes in text files:
http://j2me-device-db.sourceforge.net

]]>