PocketMatrix

We would like for Pocket Matrix to host a database of properties for devices that would include information such as GAPI properties, hardware specs, OS version, etc.

What is needed is a diagnostic program that will dump the info to a file which can then easily be uploaded to the site. Digby, does your GAPI properties program output to file, and if so, do you feel like distributing it? If not then I will write a program myself.

The next thing needed is volunteers to run the diagnostic program on all the types of Pocket PCs known.

What we need up-front are suggestions for what information should be collected beyond just the GAPI properties. I would like to record the type and number of storage cards supported, the physical dimensions of the display, the type of display and backlighting, a table relating the physical location of the hardware buttons to the GAPI key properties, processor type and speed, OS version, etc. Obviously some properties can not be reported by a diagnostic program and will have to be provided by the tester.

Any other suggestions?

Dan East

hmm:
1.key test if you can press few keys at a time and to check how they work (not sure if it's needed, but some time ago phantom noticed that on some? devices a button press generates two keydown communicates?)
2.sound support (mono/stereo/any?)
3.mb of mem?
4.exact bpp for display (ie if it's either 16bpp cut down to 12bpp like on some devices or true 16bpp display)

hope some of this makes sense:)

has anyone tried this (the Spy program),I'm not a programmer so I don't know if this is useful.

I found the link on the NetStubler site.

http://www21.brinkster.com/samsstuff/

One thing is to have a gamma part in it. Where the screen displays a very dark square or something, and they change the gamma until they can see it.

We should also have a benchmarking part of it. Like memoryspeed and processor etc. Doesn't need to be very advanced. Just some memory writes/reads (both random and sequentially) and then doing some fixed point and floating point calculations and see how long time it takes to make x amount of them.

Would also be nice to have the REAL GAPI values in the list, not just the ones GAPI returns, but also the ones the new iPAQ uses internally. I could supply those to the DB if needed. Think I also have the physical address to Casio EM-500:s video memory (untested).