GPS Data Logger Software - BT747

+1

BT747 for Android would kick.

Tried running the J2ME.jar using netmite but had no luck.  The midlet would run and scan for bluetooth devices but would not find the 747.

Sorry, I know nothing about programming, otherwise I would be happy to help with the development.  Best.

-H.

Hi

Apparently it is possible to create a package on the site directly which is what I did - I put it at http://soft.bt747.org/BT_J2ME.apk .

I've tried this in the emulator provided by google and the 'Live Android CD' in an emulator.

I learned that:

1. A J2ME runner has to be installed from netmite:  On http://www.netmite.com/android/ , I selected the latest version to date: http://www.netmite.com/android/old/1.7.0.2/andme_signed_1.7.0.2.apk 
2. Running in the Android SDK emulator starts the app which starts looking for devices.  It stays there indefinitively and there is no response to the keys (in principle the left button should make the application go to the main menu but there is no response on the keys).  That may be because the emulator does not support bluetooth and BT_J2ME does not capture that exception correctly (which is what I see in the 'logcat' log).
3. In the Android Live CD setup running in Sun Virtual Box the 'apk' files can not even be installed - Android reports an issue with the packages.

So, I can not do much in the emulator for the moment.

To understand what is happening on the device, one would need to get the 'logcat' from the device.  I am not sure how to do that on a device.  Throught the emulator functionality (adb), I can do a 'logcat' and see messages like these:

BT747's log file setup (but apparently failing:)

W/System.err(  571): [Info] Setup up console to file

V/@@@ERR  (  571): [Thread-10]:Connector.open(file:///root1/BT747Console.log,3,false

V/@@@ERR  (  571): [Thread-10]:Connector.open(file:///root1/BT747Console.log,3,false

V/@@@ERR  (  571): [Thread-10]:Connector.open(file:///root1/BT747Console.log,2,false

W/System.err(  571): [Info] Setup up console to file

W/System.err(  571): [Info] Basedir set to:/root1

Bluetooth can not be loaded:

D/dalvikvm(  571): Trying to load lib /data/data/com.netmite.andme/libbluecove-2.1.0.51-1607.so 0x43b7c2b8

I/dalvikvm(  571): Unable to dlopen(/data/data/com.netmite.andme/libbluecove-2.1.0.51-1607.so): Cannot load library: link_image[1721]:    30 could not load needed library 'libbluetooth.so' for 'libbluecove-2.1.0.51-1607.so' (load_library[1051]: Library 'libbluetooth.so' not found)

BT_J2ME detects issue in bluetooth discovery and cancels it (which is normal) (messages [Info] and [Error] are from BT_J2ME):

W/System.err(  571): [Error] Problem with Bluetooth device discovery.

W/System.err(  571): [Info] Canceling Bluetooth device discovery.

Stack overflow happens somewhere and this unexpected exception is not really handled in BT_J2ME:

I/dalvikvm(  571): Stack overflow, expanding (0x42700200 to 0x42700000)

I/dalvikvm(  571): Shrank stack (to 0x42700200, curFrame is 0x42700344)

W/System.err(  571): [Warn] Unhandled exception in hideNotify() of Finding GPS...

And that latter issue seems to be the main reason why BT747 'blocks'.  However, it is not clear if that is the raised exception in Java.  

That is for the emulator, so it would be interesting to see what happens on the device.

Hi rt

An unhandled exception has been reproduced on a regular J2ME platform and I finally managed to get an unhandled in an emulator too after solving an issue in the GUI library I am using.  I am not sure the issue is the same, but the exception is an out of memory error.  Currently I am still puzzled why that consistently appears after solving the other library issue, but at least it is consistent now.

The netmite server is up again and I was able to convert the application.

Bluetooth will not work yet because of a general issue, but the application now runs normally on Android.

You can install from http://soft.bt747.org/J2ME (select the 'apk' file) and you'll need to have netmite installed as mentionned earlier.

In the netmite configuration you need to disable the 'Auto detect Game Canvas' (Menu/=System Menu=/=Settings= ).

Now I am going to fix this general bluetooth connection issue (also on normal J2ME platforms).

Hi Mario,

I leave for a couple of days and look at the progress.  Sorry about the delayed response.  Your .apk seems to be working in my device, minus the bluetooth connection.  All of this is way over my head and your efforts are much more productive than mine were when I was running the .jar directly in netmite (ver: 1.7.0.2) without creating the .apk.

I understand that Android has some inherent issues with its bluetooth stack and I have not been able to find an application which allows NMEA data to be utilized from an external device.  I was looking into a project being worked on at 'http://code.google.com/p/android-bluetooth/' which I believe would allow serial connections over bluetooth in Android.  Although, again, way over my head.  

I appreciate your work and expertise and I'd be happy to help within my capabilities.  I am using an HTC Hero running Android 1.5.  Let me know if I can be of help.

Cheers,  -H.

Thanks Mario,

Pasted application log below:

[Info] Setup up console to file

[Info] Basedir set to:/sdcard

[Info] Version 0.3.61

[Info] Before main.show

[Info] Discovering Bluetooth devices.

[Error] Problem with Bluetooth device discovery.

(javax.bluetooth.BluetoothStateException: Bluetooth Device is not available)

[Info] Returning Discovery Error

[Info] Discovering Bluetooth devices.

[Error] Problem with Bluetooth device discovery.

(javax.bluetooth.BluetoothStateException: Bluetooth Device is not available)

[Info] Returning Discovery Error

[Info] Setup up console to file

[Debug] Screen switched to Log

[Debug] MainScreen showNotify

[Debug] MainScreen setupScreen

[Debug] Screen switched to MTK Logger Control V0.3.61

[Debug] Screen switched to Log

[Debug] Screen switched to Connection

[Info] Discovering Bluetooth devices.

[Debug] Screen switched to Finding GPS...

[Debug] Starting Bluetooth device discovery

[Error] Problem with Bluetooth device discovery.

(javax.bluetooth.BluetoothStateException: Bluetooth Device is not available)

[Info] Returning Discovery Error

[Debug] Screen switched to Discovery Error

[Debug] MainScreen showNotify

[Debug] MainScreen setupScreen

[Debug] Screen switched to MTK Logger Control V0.3.61

[Debug] Screen switched to Log

[Debug] Screen switched to Logger

[Debug] Screen switched to Log

[Debug] Screen switched to App Settings

[Debug] Screen switched to Log

[Debug] MainScreen showNotify

[Debug] MainScreen setupScreen

[Debug] Screen switched to MTK Logger Control V0.3.61

Not sure how I check permission settings on those files, I'll do a little research and find out.  I do have root access on my device as well as a terminal emulator application, I just do know the commands.  Working on it.  Anything else?Cheers.  -H.

Hi

Ok, it seems that the problem may be with the driver.  To know more about it we need the logcat information regarding this error.  I've looked around again and found a program that will allow you to see it on the device.  I added the link to the apk on http://soft.bt747.org/J2ME .  You can look at the system log on the device and save it to a file (you can not choose the path, hopefully you have some means to retrieve it).

When you have the log, try attaching it (Webfm below the comment entry window) rather than paste it - thanks.

You should look for something like this in the error log:

error Problem with Bluetooth device discovery.

(javax.bluetooth.BluetoothStateException: BlueCove libraries not available)

 c.a.b.b.a(null:-1)

error MIDlet caught javax.bluetooth.BluetoothStateException: BlueCove libraries not available

 c.a.b.b.a(null:-1)

javax.bluetooth.BluetoothStateException: BlueCove libraries not available

at com.intel.bluetooth.BlueCoveImpl.createDetectorOnWindows(BlueCoveImpl.java:896)

at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:439)

at com.intel.bluetooth.BlueCoveImpl.access$500(BlueCoveImpl.java:65)

at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:1020)

at java.security.AccessController.doPrivileged(Native Method)

at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:1018)

at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:1011)

at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:75)

at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:95)

at net.sf.bt747.j4me.app.b.g.a(Unknown Source)

at net.sf.bt747.j4me.app.b.a.a(Unknown Source)

at net.sf.bt747.j4me.app.b.a.g(Unknown Source)

at net.sf.bt747.j4me.app.a.b.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

at org.microemu.app.util.MIDletThread.run(MIDletThread.java:99)

error [Info] 

 c.a.b.b.a(null:-1)

error Returning Discovery Error

 c.a.b.b.a(null:-1)

error [Info] 

If you have a rights problem on the bluetooth devices in /dev/socket , the way to become root is apparently to use the Android SDK.

So, you need to:

1. Get the SDK.  This is basically downloading an archive and extracting it from http://developer.android.com/sdk/index.html .
2. Then you need to connect your device using the USB cable and launch
   adb shell
3. Inside that shell, do:
   su root
   cd /dev/socket
   chmod 777 bluetooth
   chmod 777 dbus_bluetooth
   ls -l
   exit
   
   The above will (a) make you root, (b) put you in the socke directory, (c,d) change the rights, (e) show the directory content so that you can verify those rights, (f) exit the shell.
4. When you are root, you can also use logcat ;-), but that is easier when doing that directly from adb:
   adb logcat -d > logfile.txt
   
   That will put the 'logcat' content in a file on your desktop that is called logfile.txt .

That is 'it'.

I compiled the log.  I'm not seeing the WebFM link.  Log file at <http://dl.dropbox.com/u/4706302/logfile.txt> 

Keep me posted.

-H.

Bluetooth is on and idle.  I checked the bluetooth and dbus_bluetooth file permissions several times, they look good.  

Thanks for the follow up.  I'm still happy to participate in any way that I can. Let me know.

Cheers.  -H.

Yes, I've paired my iblue 747 to my android device. 

I've been trying out other applications in netmite which utilize the bluetooth connection and I'm not having any luck with those either.  I keep getting an error asking me to turn my bluetooth radio on, or telling me that a bluetooth device is not available, etc.  This appears to be a configuration issue and not an issue with the bt747 apk.  I shot an email to the Netmite dev.  Perhaps there's something else that I'm not doing right.  -H.

Hi

I had a look at netmite again and I saw that a new version is out, so I reconverted BT747.  As a reminder, the links to get the BT747 apk is at http://soft.bt747.org/J2ME/ .  There is also a link to get netmite itself from their page.

'rt', I guess that you tried the correct flavor of BT747 by installing a BT_J2ME.jar file.

From what you write, I have little info to go on - I know it is a specific Samsung model with Android but I am not sure what "it does not work" means.

Does the application at least start (Netmite, native J2ME?);
What does the log say ?.

J2ME is a headache regarding credentials.  Make sure that you accept the security exceptions and/or that these are configured for BT_J2ME.

Actually, the J2ME version runs in microemu on the desktop for demonstration purposes. There is a link (jnlp) on the following page that also has the other J2ME links:

http://soft.bt747.org/J2ME/

I looked for android and microemu on the web and stumbled on this page again:

http://microemu.blogspot.com/2008/11/running-java-me-applications-on-and...

That is about a port of microemu to Android.  When I looked a long time ago, it looked liked this project was dead, but recent entries show that it is alive, including a google group:

http://groups.google.com/group/microemulator-support

So, that could be another way of doing it.  I currently can't investigate that path though.

As for running it with Netmite, it simply FCs -- "The application Java J2ME Runner (process com.netmite.andme) has stopped unexpectedly. Please try again. [Force close]".

As for logs, the following part looks most interesting:

V/@ERR@   ( 2668): Problem with Bluetooth device discovery.
V/@ERR@   ( 2668): (javax.bluetooth.BluetoothStateException: Bluetooth Device is not available)
V/@ERR@   ( 2668): javax.bluetooth.BluetoothStateException: Bluetooth Device is not available
V/@ERR@   ( 2668):     at com.intel.bluetooth.BluetoothStackBlueZ.nativeGetDeviceID(Native Method)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BluetoothStackBlueZ.initialize(Unknown Source)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl.setBluetoothStack(Unknown Source)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl.detectStack(Unknown Source)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl.access$500(Unknown Source)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl$1.run(Unknown Source)
V/@ERR@   ( 2668):     at java.security.AccessController.doPrivilegedImpl(AccessController.java:205)
V/@ERR@   ( 2668):     at java.security.AccessController.doPrivileged(AccessController.java:178)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(Unknown Source)
V/@ERR@   ( 2668):     at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(Unknown Source)
V/@ERR@   ( 2668):     at javax.bluetooth.LocalDevice.x_a(Unknown Source)
V/@ERR@   ( 2668):     at javax.bluetooth.LocalDevice.getLocalDevice(Unknown Source)
V/@ERR@   ( 2668):     at dy.a(Unknown Source)
V/@ERR@   ( 2668):     at cq.a(Unknown Source)
V/@ERR@   ( 2668):     at cq.b_(Unknown Source)
V/@ERR@   ( 2668):     at dv.run(Unknown Source)
V/@ERR@   ( 2668):     at java.lang.Thread.run(Thread.java:1096)
V/@ERR@   ( 2668):     at com.netmite.andme.MIDletThread.run(Unknown Source)
I/ActivityManager( 1940): Process com.netmite.andme.launcher.bt_j2me_midlet_suite (pid 2662) has died.

and maybe:
E/dalvikvm-heap( 2668): 499200-byte external allocation too large for this process.
E/        ( 2668): VM won't let us allocate 499200 bytes
D/AndroidRuntime( 2668): Shutting down VM
W/dalvikvm( 2668): threadid=3: thread exiting with uncaught exception (group=0x4001b180)
E/AndroidRuntime( 2668): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 2668): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
E/AndroidRuntime( 2668):     at android.graphics.Bitmap.nativeCreate(Native Method)
E/AndroidRuntime( 2668):     at android.graphics.Bitmap.createBitmap(Bitmap.java:468)
E/AndroidRuntime( 2668):     at com.netmite.andme.lcdui.CanvasBufferingView.<init>(Unknown Source)
E/AndroidRuntime( 2668):     at com.netmite.andme.lcdui.x_x_bc.run(Unknown Source)
E/AndroidRuntime( 2668):     at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 2668):     at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 2668):     at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 2668):     at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 2668):     at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2668):     at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 2668):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 2668):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 2668):     at dalvik.system.NativeStart.main(Native Method)