GPS-Sport ForenRun.GPS HardwareZephyr HxM and Android 2.1 problem
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
kawasakai 03.08.2010 22:48:08 UTC geändert am 03.08.2010 22:48:16 UTC

Android Zephyr™ HxM Samsung Galaxy S (i9000)

Also bei dir hat sich das Problem mit einem Update auf die 2.1 erledigt?


Ich habe ein i9000 mit 2.1 und es ist nicht möglich sinnvolle Daten vom HxM zu bekommen. Das Gerät ist aber in Ordnung wenn ich es mit meinen WinMobile-PDA benutzte.

Siehe http://www.gps-sport.net/trainings/running_358981
Nach einer Weile 1-2 min kommt dass die Verbindung vom Herzfrequenzmesser schlecht wäre und das Herzsymbol bleibt lila und ist "zerbrochen". Der Puls bleibt ab diesen Moment unverändert die par Änderungen welche zu sehen sind kommen davon das ich die Verbindung manuell unterbrochen und wieder hergestellt habe.
cfarrell 20.05.2010 12:18:43 UTC

Problem solved by updating the Spica firmware

When I updated the phone firmware to the latest version available from samsung-firmwares.com (May 2010), the HxM worked out of the box.
cfarrell 25.04.2010 21:48:52 UTC

See also http://www.gps-sport.net/forums/thread/1532-0/Keine-Sprachausgabe-auf-HTC-Desire

Cross posting this entry from the software category. The thread over there deals with the Zephyr HxM as a secondary issue - meaning it mightn't be easy to find...

http://www.gps-sport.net/forums/thread/1532-0/Keine-Sprachausgabe-auf-HTC-Desire

24.04.2010 16:47:05 UTC geändert am 24.04.2010 17:03:03 UTC

A fix to the bluetooth connection problem

Hi

If this problem still is not resolved, the code below describes how to make the connection work with Android 2.1 (Tested on HTC Desire). Just replace "00:07:80:89:EE:EB" with the MAC of your HXM to make it connect. After the connection is successful, a regular method with input = socket.getInputStream() can be used.

BluetoothDevice hxm = BluetoothAdapter.getDefaultAdapter().getRemoteDevice("00:07:80:89:EE:EB");
Method m = hxm.getClass().getMethod("createRfcommSocket", new Class[]{int.class});
socket = (BluetoothSocket)m.invoke(hxm, Integer.valueOf(1));
socket.connect();

Hope the fix will be out very soon =)

Best regards
Espen S. Nygaard
cfarrell 19.04.2010 14:28:12 UTC

more info from stackoverflow.com

I did some more logging and posted the output to stackoverflow. It may be helpful
http://is.gd/bzegq

Glad to help in any way I can. Would love to get the HxM working :-)
admin 19.04.2010 13:49:42 UTC



Thanks for the detailed logs!

We're currently working on this issue.



cfarrell 16.04.2010 11:45:18 UTC

logcat output on Samsung Spica using adb

cfarrell@paddy:/home/cfarrell/android-sdk-linux_86/tools> ./adb logcat | grep Run.GPS
D/WYNEX> (11551): Excute :: Run.GPS Trainer UV, (null)
E/Run.GPS (11997): Cannot connect to BT device
E/Run.GPS (11997): java.io.IOException: Service discovery failed
E/Run.GPS (11997): at android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:374)
E/Run.GPS (11997): at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:184)
E/Run.GPS (11997): at ju.a(Unknown Source)
E/Run.GPS (11997): at qk.j(Unknown Source)
E/Run.GPS (11997): at fs.c(Unknown Source)
E/Run.GPS (11997): at le.a(Unknown Source)
E/Run.GPS (11997): at s.b(Unknown Source)
E/Run.GPS (11997): at pb.a(Unknown Source)
E/Run.GPS (11997): at as.a(Unknown Source)
E/Run.GPS (11997): at am.b(Unknown Source)
E/Run.GPS (11997): at gf.onTouchEvent(Unknown Source)
E/Run.GPS (11997): at android.view.View.dispatchTouchEvent(View.java:3709)
E/Run.GPS (11997): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884)
E/Run.GPS (11997): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884)
E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1665)
E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1107)
E/Run.GPS (11997): at android.app.Activity.dispatchTouchEvent(Activity.java:2061)
E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1649)
E/Run.GPS (11997): at android.view.ViewRoot.handleMessage(ViewRoot.java:1694)
E/Run.GPS (11997): at android.os.Handler.dispatchMessage(Handler.java:99)
E/Run.GPS (11997): at android.os.Looper.loop(Looper.java:123)
E/Run.GPS (11997): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/Run.GPS (11997): at java.lang.reflect.Method.invokeNative(Native Method)
E/Run.GPS (11997): at java.lang.reflect.Method.invoke(Method.java:521)
E/Run.GPS (11997): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/Run.GPS (11997): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/Run.GPS (11997): at dalvik.system.NativeStart.main(Native Method)
E/Run.GPS (11997): Cannot connect to BT device
E/Run.GPS (11997): java.io.IOException: Service discovery failed
cfarrell 16.04.2010 11:27:10 UTC

dmesg output while trying to connect

<4>[74726.239833] select 11691 (.serviceModeApp), adj 15, size 3205, to kill
<4>[74726.240741] select 11739 (com.wssnps), adj 15, size 3207, to kill
<4>[74726.246870] select 11750 (id.partnersetup), adj 15, size 3219, to kill
<4>[74726.253390] select 11857 (p.bluetoothicon), adj 15, size 3299, to kill
<4>[74726.259879] select 13131 (ndroid.settings), adj 15, size 4586, to kill
<4>[74726.266372] send sigkill to 13131 (ndroid.settings), adj 15, size 4586
<7>[74733.945097] [BT] GPIO_BT_WAKE = 1
<7>[74733.945121] [BT] wake_lock(bt_wake_lock)
<7>[74733.951799] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74733.951822] [BT] wake_lock timeout = 5 sec
<7>[74735.890196] [BT] GPIO_BT_HOST_WAKE = 0
<7>[74736.150987] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74736.151009] [BT] wake_lock timeout = 5 sec
<7>[74737.490185] [BT] GPIO_BT_HOST_WAKE = 0
<7>[74740.073913] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74740.073948] [BT] wake_lock timeout = 5 sec
<7>[74741.315336] [BT] GPIO_BT_HOST_WAKE = 0
<7>[74743.249747] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74743.249768] [BT] wake_lock timeout = 5 sec
<7>[74744.865099] [BT] GPIO_BT_HOST_WAKE = 0
<7>[74745.154487] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74745.154509] [BT] wake_lock timeout = 5 sec
<7>[74748.852534] [BT] GPIO_BT_HOST_WAKE = 0
<7>[74749.156256] [BT] GPIO_BT_HOST_WAKE = 1
<7>[74749.156278] [BT] wake_lock timeout = 5 sec
<7>[74750.490018] [BT] GPIO_BT_HOST_WAKE = 0
<4>[74754.230424] select 11691 (.serviceModeApp), adj 15, size 3191, to kill
<4>[74754.231326] select 11739 (com.wssnps), adj 15, size 3193, to kill
<4>[74754.237473] select 11750 (id.partnersetup), adj 15, size 3205, to kill
<4>[74754.243950] select 11857 (p.bluetoothicon), adj 15, size 3283, to kill
<4>[74754.250452] select 13140 (com.svox.pico), adj 15, size 3465, to kill
<4>[74754.256787] send sigkill to 13140 (com.svox.pico), adj 15, size 3465
cfarrell 16.04.2010 10:14:14 UTC

Got it working with HTC and Windows Mobile

With a HTC Windows Mobile smartphone I was able to get the heartrate monitor working. At first, it didn't look as though it was going to work. The pairing was quite dodgy (the HxM device was always shown as being 'disconnected' in the Windows Mobile bluetooth settings). In run.gps, under 'Settings -> Heartrate Monitor' there are many more options available than on run.gps for Android. The baud rate can be changed, as can the COM port.

When I changed the COM port to COM1, it worked.

On Android, I guess a COM port is known as /dev/tty or something like that. I don't know how to change this - run.gps doesn't give me any options.

Is there anyone who has successfully got the heartrate monitor working with Android and if so, how.
cfarrell 14.04.2010 23:37:47 UTC



Here's my phone information - it's using the Eclair codebase

Samsung (Spica) i5700
Firmware 2.1-update1
Kernel 2.6.29

The problem is that run.gps will not connect the Zephyr bluetooth transmitter. In the Android phone's settings, I already paired the HxM device (using 1234 as indicated in the run.gps manual) and the pairing was successful. At that stage, Android told me that the device was 'paired but not connected'.

When I went to run.gps -> Configuration -> Heart Rate Monitor the Zephyr was preselected, so I clicked on the 'connect' button. After a while, I got the 'could not connect' message - looks like it timed out.

I made sure that there was no other bluetooth paired device present. Is there anything else I can do to debug this? I'd like to connect to the Zephyr somehow - perhaps hcidump or something like that. Are there any tips/advice?
Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung