Java/Bluetooth

Impronto Developer Kit for Linux for Non Commercial use Release Notes

Introduction

The Impronto Developer Kit provides Java developers with a Bluetooth environment to build and deploy Bluetooth applications. The Impronto Development Kit for Linux for Non Commercial Use implements the standard JABWT (Java APIs for Bluetooth Wireless Technologies) developed by the JSR- 82 expert group.

Support for JABWT Java APIs
Provides full support for RFCOMM, L2CAP, SDP, OBEX, Bluetooth Control Centre (BCC)
Supports the official Linux Bluetooth stack BlueZ
Support for JSR-82 IrDA connectors
Lightweight remote object invocation (PRMI)
Demonstration Applications [Tic-Tac-Toe, Service Browser]

Prerequisites

The hardware requirements (for the installer for x86 and Zaurus editions) are as follows:
At least a Pentium CPU 200+ MHz recommended
At least 128MB RAM
5MB free disk space
Bluetooth Hardware
Sharp Zaurus SL-5500 or C-760 with USB cradle (Zaurus edition only)

The software requirements for the x86 edition are as follows:
Fedora Core 2 or later (e.g. Mandrake 10.0 or later)
Any 2.4-series kernel later than 2.4.20 or 2.6-series kernel later than 2.6.5.
Apache ANT build tool [1.5.4] or later
Java SDK [1.4.2] or later

The software requirements for the Sharp Zaurus edition development machine are as follows:
RedHat Linux distribution
Apache ANT build tool [1.5.4] or later (available here: http://ant.apache.org/bindownload.cgi)
Java SDK [1.4.2] (available here: http://java.sun.com/downloads/)

Required version of BlueZ packages are:
BlueZ-SDP 1.2 or later
BlueZ-Utils 2.3 or later
BlueZ-Libs 2.4 or later

For x86:
bluez-libs-2.4-1.i386.rpm (or later)
bluez-sdp-1.2-1.i386.rpm (or later)
bluez-utils-2.3-1.i386.rpm (or later)

For Sharp Zaurus:
bluez-kernel-2.4.18-mh14_arm.ipk (or later)
bluez-libs-2.7_arm.ipk (or later)
bluez-utils-2.7_arm.ipk (or later)

Target Environments

Impronto Development Kit for Linux for Non Commercial use currently supports the following hardware devices:
Linux x86 computer with BlueZ compatible Bluetooth device. Linux kernel 2.4.20 or later
Sharp Zaurus SL-5500 or C-760 with BlueZ compatible Bluetooth device. Zaurus ROM version 3.10 kernel version 2.4.18-embedix, or ROM version 2.39 kernel version 2.4.16-embedix
Check http://www.holtmann.org/linux/bluetooth/devices.html for a list of BlueZ compatible devices

Documentation and Resources

The JABWT spec: http://www.jcp.org/jsr/detail/82.jsp
JABWT.com, http://www.jabwt.com

To Install the x86 edition

As root user type;

# rpm -vh impronto-1.3-7.i386.rpm

The installer creates the following files:
/usr/share/doc/impronto-1.3/user_guide.pdf This directory also contains the Javadoc and examples.
/usr/share/java/idev_bluez.jar - Impronto Java archive.
/usr/lib/libimpronto.so The x86 native library.

To Install the Sharp Zaurus Edition

On your desktop development environment as root user type;

# rpm -ivh impronto-1.3-7.noarch.rpm

This will install Impronto Developer Kit for the Sharp Zaurus. If installing both the x86 version and the Sharp Zaurus version use the --force flag.

The installer creates the following files:

/usr/share/doc/impronto-1.3/user_guide.pdf
/usr/share/java/idev_bluez.jar - Impronto java files
/usr/share/java/impronto_1.3_arm.ipk - Package to place onto the Zaurus

Place impronto_1.3_arm.ipk onto the Zaurus and install from a terminal on the Zaurus with the following:

# ipkg install impronto_1.3_arm.ipk

The following files are installed onto the Zaurus:

/usr/lib/libimpronto.so - The ARM native library
/usr/share/prmirt.jar - The PRMI runtime library
/usr/share/idev_bluez.jar - The Impronto runtime library

Licensing

The Impronto Developer Kit must be licensed before use. Please contact sales@rococosoft.com if you have not yet received your license. The LinuxLicence.txt you receive must be placed on your classpath at runtime.

Known Issues

The table below contains details of all known product issues.

Rococo Identifier Details
345 Very large data-elements in SDP service records can overflow the buffer (64k) allocated by BlueZ's SDP library.
338 InterruptedIOException not thrown on thread blocked in read
314 Reception of empty L2CAP packet indistinguishable from EOF. This results in a JSR-82 specification non-compliance, but can easily be avoided.
344 Removed service attributes are still returned from SDP server. This is a problem with the BlueZ SDP implementation.
496 Server-specified security fails for RFCOMM. Security settings for RFCOMM servers fail due to a problem within BlueZ.

Support

To report any technical problems with Impronto Developer Kit for Linux 1.3, please use the web form at http://www.rococosoft.com/support.html

Alternatively, email the following information to support@rococosoft.com:

Short Description of the problem.
Operating System version and any service packs applied.
JDK Version and any patches applied.
Severity of this bug. This rating should reflect the impact of this issue on your evaluation.
Detailed Description of the incident with any diagnostic information which may be available, for example Simulator log files or Java stack traces.
Test Case: Where appropriate a Java test case which illustrates the issue must be provided. The test case will help the support team to quickly diagnose the error.

We are very interested to hear your feedback on any aspect of the program. Please email comments to support@rococosoft.com.