Device Support Details
| Organization | Device Model | Approx Cost | Device Information | Last Working Build# | Test Date | Tester | Comments |
| Dimagi | Palm Treo 650 | ||||||
| Dimagi | Palm Treo 750 | This is Jon's phone | |||||
| Dimagi | Nokia N800 | ||||||
| Dimagi | Nokia E61 (or maybe 62) | ||||||
| Dimagi | Nokia 6680 | ||||||
| Dimagi | Nokia E70 | ||||||
| Dimagi | Nokia N95 | This is Cory's phone. | |||||
| Dimagi | Sony Ericsson P1i | ||||||
| Cell-Life | Nokia 2600 Classic | R850($85) Nov 08 | Slow, Low RAM | none | |||
| Cell-Life | Nokia 2630 | R800($80) Nov 08 | Slow, Low RAM | none | |||
| Cell-Life | Nokia 6300 | R1800($180) Nov 08 | Excellent device | branches/support-celllife | 5/10/08 | ||
| Cell-Life | Nokia 3110 Classic Classic | R1100($110) Nov 08 | Great thus far, big keys, lots of RAM, used in field | branches/support-celllife | 5/10/08 | ||
| Cell-Life | Nokia N70-1 | Becoming old, v slow operating system. | |||||
| UW | Nokia N95 | ||||||
| UW | Nokia N80 | ||||||
| UW | Sony Ericsson k610i | ||||||
| TechEndeavour | Nokia 2865 | Avi M's cell. Good example of series 40 phone. | |||||
| TechEndeavour | Nokia 6085 | ||||||
| TechEndeavour | Nokia 6600 | ||||||
| TechEndeavour | Nokia 5610 | ||||||
| TechEndeavour | Sony Ericsson 810i | ||||||
| TechEndeavour | Sony Ericsson 580i | ||||||
| TechEndeavour | Motorola V3i | ||||||
| TechEndeavour | Motorola V8312 | ||||||
| TechEndeavour | BlackBerry 8310 | Smart phone, OS version: v4.2.2.163 | |||||
| TechEndeavour | BlackBerry 8100 | Perl, OS version: v4.2.0.61 | |||||
| TechEndeavour | BlackBerry 8700 | Wireless Handheld, OS version: v4.2.1.91 | |||||
| TechEndeavour | O2 XDA atom | Win mobile 5.0 | |||||
| TechEndeavour | Imate SP5 | Win mobile 5.0 | |||||
| TechEndeavour | HP - iPAQ (PocketPC) | Win mobile 5.0 | |||||
| TechEndeavour | HP - iPAQ | Win mobile 5.0 | |||||
| TechEndeavour | O2 XDA-II | Win mobile 2003 | |||||
| IRD | Nokia 6131 NFC | ~$200 | This one scans RFID tags | ||||
| IRD | Nokia E50-1 | ~$200 |
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 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."
