Device Support Details
| Organization | Device Model | Approx Cost | Device Information | Last Working Build# | Test Date | Tester | Comments |
| UW | Android G1 | still porting | |||||
| Cell-Life | Nokia 2600 Classic | R850($85) Nov 08 | Slow, Low RAM | insufficient memory to run JavaRosa | |||
| Cell-Life | Nokia 2630 | R800($80) Nov 08 | Slow, Low RAM | insufficient memory to run JavaRosa | |||
| Cell-Life | Nokia 3110 Classic | R1100($110) Nov 08 | Great thus far, big keys, lots of RAM | branches/support-celllife | 5/10/08 | widely deployed | |
| Cell-Life | Nokia 3500 | R1500($150) Nov 08 | Excellent device | branches/support-celllife | 5/10/08 | ||
| Dimagi | Nokia 6085 | $120 | Excellent device, 2MB heap | works well | Feb 09 | widely deployed | |
| IRD | Nokia 6131 NFC | ~$200 | This one scans RFID tags | ||||
| Cell-Life | Nokia 6300 | R1800($180) Nov 08 | Excellent device | branches/support-celllife | 5/10/08 | ||
| IRD | Nokia E50-1 | ~$200 | |||||
| Dimagi | Nokia E61 (or maybe 62) | ||||||
| Dimagi | Nokia E70 | ||||||
| Dimagi | Nokia E71 | ||||||
| Cell-Life | Nokia N70-1 | Becoming old, v slow operating system. | |||||
| UW | Nokia N80 | ||||||
| Dimagi | Nokia N800 | ||||||
| Dimagi | Nokia N95 | Phone has gargantuan heap, but limits J2ME apps to only 1MB (!?) | |||||
| Dimagi | Palm Treo 650 | ||||||
| Dimagi | Palm Treo 750 | ||||||
| UW | Sony Ericsson k610i | ||||||
| Dimagi | Sony Ericsson P1i | $400 | Has a touch-screen with stylus, qwerty keyboard (with rocker keys). A promising phone at first glance, but the phone is very slow and the user experience is very poor | works well | Feb 09 | RMS performance is terrible | |
| UCT Spatial Data Management | Nokia 6085 | ||||||
| UCT Spatial Data Management | Nokia 6220c | ||||||
| UCT Spatial Data Management | Nokia 3120c | ||||||
| UCT Spatial Data Management | Nokia 5310 xpress music | ||||||
| UCT Spatial Data Management | Nokia 6120 |
JavaRosa General Device Support
Memory Requirements
JavaRosa requires a reasonably large heap size in its current incarnation to be able to run. In order to run JavaRosa, around 500,000 bytes of memory should be available. To load forms and be fully functional, somewhere around 850,000 bytes of memory is required. To identify the total memory available to phone JVM's, try jbenchmark's numbers. The operative field is "Total Memory" under "JVM general". In our experience, phones with 600KB total JVM heap (such as the Nokia 2600c and 2630) cannot run JavaRosa reliably, even for small forms. Phones with 2MB of heap (such as the Nokia 3110c and 6085) can run JavaRosa comfortably, even for large forms.
In order to test whether a device's memory footprint is sufficient for your particular JavaRosa application, add the parameter "-Xheapsize" with the appropriate value in bytes to the emulator task in the build.xml file, as in the following example. An example should also exist in the current build.xml file.
<emulator wait="true" securityDomain="trusted" enableProfiler="true" enableMemoryMonitor="true" enableNetworkMonitor="false" if="debug"> <parameter name="-Xheapsize" value="850000"/> </emulator>
Samsung Considered Harmful
From http://forum2.mobile-review.com/archive/index.php/t-40430.html :
"It is NOT officially possible to install java MIDlets on samsung handsets (excluding smartphones) via bluetooth, IrDa, USB cable or serial cable. MIDlets can only be downloaded by Over-The-Air (OTA) via a download server."
There does exist a hacky way to do it on some models, but it requires installation of 2 or 3 programs and I think only works on Windows. So for those of us with slow or no GPRS, or without unlimited data plans, Samsung looks thus like a bad idea. Also, the interface on the phone I tried, the e200, is somewhat annoying.
UPDATE: Even more reason to stay away:
http://techype.blogspot.com/2007/04/why-do-south-koreans-hate-developers.html
"Their Java efforts have always been decidedly middling though - many many bugs, documented on the old forums before they were deleted, and very few APIs beyond the basic MIDP and CLDC. Their LCDUI implementations are usually straight out of the WTK, offering no native UI functions and feeling completely alien to the phones."
