search

jdrescher2006 / Laufhelden

Sport tracker for Sailfish OS
GNU General Public License v3.0
16 stars 17 forks source link

Status of BLE? #123

Closed thmichel closed 5 years ago

thmichel commented 6 years ago

Hi,

I know Laufhelden does not support BLE devices yet. Would really love to see this implemented, I own a Jabra Sport Headset with Heart Rate and Motion sensor.

Is there a chance that BLE will be supported any time soon? Happy to donate to raise the motivation a bit :-)

My coding skills in C++ are a bit outdated so I am not of much help there but would be happy to test any experimental versions.

Best regards and thanks for this great app!

Thomas.

ncartron commented 6 years ago

Same here, using my Polar HRM which does BLE would be nice. Happy to fund a little :)

jdrescher2006 commented 6 years ago

Hi guys, some time ago I heard that someone is working on a BLE heartrate app for Sailfish. Since it didn't appear yet, maybe it's time to do something about it. There are a lot of ways to start with this, for example take a look at the "Bluetooth Low Energy Heart Rate Game" QT example. The problem is I am quite consumed at the moment and can't really concentrate on developing for SFOS. I hope that will change someday soon.

thmichel commented 6 years ago

Hi,

I did have a look at your code and on the Bluetooth Low Energy scanner example. That looked pretty straigth forward. The difference in connecting to a BLE device seems to be that you need a QBluetoothDeviceInfo object as parameter, in your code you only store the name and MAC address when scanning. So I think first it would be necessary to save a list of the QBluetoothDeviceInfo onbject of all scanned devices so they can be used for connecting. Then depending on the QBluetoothDeviceInfo::LowEnergyCoreConfiguration Flag the correct connection method could be used.

I am not very familiar with github, forking of code etc. but downloaded your code as ZIP file and will try to experiment a bit with this if you don't mind. If I am successfull I could send you the code via mail.

jdrescher2006 commented 6 years ago

You are right, first you need to scan for BLE devices. Then the user chooses the one from the list of found devices. The Bluetooth Low Energy scanner example would be very useful. Do you have the code of it?

thmichel commented 6 years ago

I took the code from the examples for QTCreator. There you find both fthe scanner and heartrate game. I did a lot of copy and paste to create a basic proof of concept. I can connect to a BTLE device and get the heart rate, but it is not very stable at the moment:

So, lot to do to get this working, but at least it seems it is possible to add support for BTLE devices. I will dig some more into this and keep you posted.

jdrescher2006 commented 6 years ago

This sounds very good! To keep it more simple for you, you could do your work in a small separate project. Then I could do the integration work into Laufhelden later.

thmichel commented 6 years ago

Yes, currentlx I am doing it completely offline as I am not very expirienced with forkin on github. If you send me an email to tom [at] michel.ruhr I can send you the code when I am satisfied with it.

@ncartron: I could send you the rpm for testing wiht you Polar device so I can see if it is working with different devices too as I have only one device to test with.

I made some progress already, connection to the device seems to be more stable now - had it running for about 10 minutes yesterday without problems.

ncartron commented 6 years ago

Hi,

Yes please do, i can test it with my Polar HRM.

Thanks! Nico

On Saturday, 24 November 2018, thmichel wrote:

Yes, currentlx I am doing it completely offline as I am not very expirienced with forkin on github. If you send me an email to tom [at] michel.ruhr I can send you the code when I am satisfied with it.

@ncartron: I could send you the rpm for testing wiht you Polar device so I can see if it is working with different devices too as I have only one device to test with.

I made some progress already, connection to the device seems to be more stable now - had it running for about 10 minutes yesterday without problems.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-44135610

-- Sent from my Sailfish device

thmichel commented 6 years ago

Nico,

I have forked the repository, a test version of the BLE support can be found here:

https://github.com/thmichel/Laufhelden/releases/tag/v1.1.3-1

ncartron commented 6 years ago

Hi Tom, just did it!

CHeers, Nico

jdrescher2006 commented 6 years ago

Hello Tom, I have a BLE heart rate belt and did some tests with your software The search finds it (SP-HRM-BLE-200) but when I try to connect there is a problem: `Device::scanServices:139 - Trying to connect to "EF:44:35:C8:10:B9"

Device::scanServices:157 - Device to connect not found!

Device::scanServices:162 - Not a valid device`

Maybe it is not identified as heart rate device?

thmichel commented 6 years ago

Hi,

Looking at the logs it seems that the divice you are trying to connect is not yet discovered. I know this happens if you connect to a device without hitting „Scan for devices“ first. It is something I Need to fix, not sure how yet.

Can you try to scan for devices first? Once the scan is finished, it should appear in the list and you should be able to connect.

You could send me a full console Output if you like, then I could check. Another possibility is that this device is using random addresses (from what I read a kind of privacy fundtion) so the mac address might not be valid any more.

In the device.cpp file this is set to fals in the device Initiator:

Device::Device(): connected(false), controller(0), m_deviceScanState(false), randomAddress(false)

You might try to set this to true, recompile it and test again. If that fixes it, I could try to see if there is a way to automatically detect this.

Regards,

Tom.

Von: Jens Drescher notifications@github.com Gesendet: Monday, November 26, 2018 8:13:46 PM An: jdrescher2006/Laufhelden Cc: Thomas Michel; Author Betreff: Re: [jdrescher2006/Laufhelden] Status of BLE? (#123)

Hello Tom, I have a BLE heart rate belt and did some tests with your software The search finds it (SP-HRM-BLE-200) but when I try to connect there is a problem: Device::scanServices:139 - Trying to connect to "EF:44:35:C8:10:B9" Device::scanServices:157 - Device to connect not found! Device::scanServices:162 - Not a valid device

Maybe it is not identified as heart rate device?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-441760947, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK9Hjl5QorCXRT9N0hZxuEFR7qjDtWiBks5uzD1qgaJpZM4Yu8DK.

jdrescher2006 commented 6 years ago

Hi Tom,

if I scan first and then press the connect button, I get the following:

[D] onStatusChanged:19 - BTPage [D] Device::scanServices:139 - Trying to connect to "EF:44:35:C8:10:B9" [D] Device::scanServices:157 - Device to connect not found! [W] Device::scanServices:162 - Not a valid device [D] Device::startDeviceDiscovery:93 - Scanning for devices ... [D] Device::addDevice:106 - "Last device added: HXM037426" [D] expression for onDeviceFound:46 - 1 [D] Device::addDevice:106 - "Last device added: 4D-9E-BA-FF-12-19" [D] expression for onDeviceFound:46 - 2 [D] Device::addDevice:106 - "Last device added: Pebble 0797" [D] expression for onDeviceFound:46 - 3 [D] Device::addDevice:106 - "Last device added: SP-HRM-BLE-200" [D] expression for onDeviceFound:46 - 4 [D] Device::deviceScanFinished:119 - Scan finished! [W] unknown:207 - file:///usr/share/harbour-laufhelden/qml/pages/BTConnectPage.qml:207: ReferenceError: id_BluetoothData is not defined [D] Device::scanServices:139 - Trying to connect to "EF:44:35:C8:10:B9" [D] Device::scanServices:178 - Trying to connect to "SP-HRM-BLE-200" [D] Device::scanServices:192 - Cannot connect to remote device. QLowEnergyController::Error(UnknownError) [W] unknown:0 - void QBluetoothSocketPrivate::_q_readNotify() 41 error: -1 "Resource temporarily unavailable" [D] Device::scanServices:192 - Cannot connect to remote device. QLowEnergyController::Error(UnknownError) [W] Device::deviceDisconnected:297 - Disconnect from device [D] Device::scanServices:139 - Trying to connect to "EF:44:35:C8:10:B9" [D] Device::scanServices:192 - Cannot connect to remote device. QLowEnergyController::Error(UnknownError) [W] unknown:0 - void QBluetoothSocketPrivate::_q_readNotify() 41 error: -1 "Resource temporarily unavailable" [D] Device::scanServices:192 - Cannot connect to remote device. QLowEnergyController::Error(UnknownError) [W] Device::deviceDisconnected:297 - Disconnect from device

thmichel commented 6 years ago

I checked with my device, I get the same error when I try to connect using random address method to it - so I guess this is the issue. I have published a new rpm that first tries to connect using random address and in case of an error switches to public address. Drawback is that ther is a 30 sec. timeout before it tries to cennect using public addresses. I think some status needs to be shown to the user about what's going on. We now have 3 connection methods: BLE public, BLE random or classic Bluetooth. It's not very nice to have to cycle through this, I need to think on how the could be improved. Probably a setting could be stored for the last used device so that at least this one connects quicker. Sadly I have not yet find a way to find out wich connection method is correct except to try one after the other.

jdrescher2006 commented 6 years ago

Yes, it works now!

[D] Device::startDeviceDiscovery:105 - Scanning for devices ... [D] Device::addDevice:128 - "Last device added: HXM037426" [D] expression for onDeviceFound:52 - 1 [D] Device::addDevice:128 - "Last device added: 4B-A9-49-CA-14-E0" [D] expression for onDeviceFound:52 - 2 [D] Device::addDevice:128 - "Last device added: 50-F4-B8-34-61-43" [D] expression for onDeviceFound:52 - 3

[D] Device::addDevice:128 - "Last device added: 64-DF-8F-D4-2D-E3" [D] expression for onDeviceFound:52 - 4 [D] Device::addDevice:128 - "Last device added: f023c2XO" [D] expression for onDeviceFound:52 - 5 [D] Device::addDevice:128 - "Last device added: Pebble 0797" [D] expression for onDeviceFound:52 - 6 [D] Device::addDevice:128 - "Last device added: SP-HRM-BLE-200" [D] expression for onDeviceFound:52 - 7 [D] onStatusChanged:25 - BTPage [D] Device::deviceScanFinished:141 - Scan finished! [D] Device::scanServices:157 - Trying to connect to "EF:44:35:C8:10:B9" [D] Device::scanServices:185 - Disconnecting from previous device... [D] Device::scanServices:196 - Trying to connect to "SP-HRM-BLE-200" [D] Device::deviceConnected:277 - Device connected - Discovering services...) [D] Device::lowEnergyServiceDiscovered:240 - Service found: "Generic Access" [D] Device::lowEnergyServiceDiscovered:240 - Service found: "Generic Attribute" [D] Device::lowEnergyServiceDiscovered:227 - Heart Rate Monitor Found [D] Device::lowEnergyServiceDiscovered:232 - Battery Level Found [D] Device::lowEnergyServiceDiscovered:240 - Service found: "Device Information" [D] Device::serviceScanDone:247 - Service scan done!) [D] Device::hrmServiceStateChanged:345 - Discovering services... [D] Device::batServiceStateChanged:392 - Discovering services...

[D] Device::subscribeToHRM:380 - Subscribing to HRM Service [D] Device::batServiceStateChanged:396 - Service discovered. [D] Device::batServiceStateChanged:407 - Subscribing to Battery Service [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 46 [D] Device::updateValues:444 - Current Heart Rate 46 [D] Device::updateValues:444 - Current Heart Rate 46 [D] Device::updateValues:444 - Current Heart Rate 46 [D] Device::updateValues:444 - Current Heart Rate 46 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [D] Device::updateValues:444 - Current Heart Rate 45 [W] Device::deviceDisconnected:328 - Disconnect from device

jdrescher2006 commented 6 years ago

The battery service does not seem to work. How can it be fixed?

What we also need is a better integration into Laufhelden. I think the user should be able to choose between "Bluetooth Classic" and "Bluetooth LE". This could be done via a combobox in the BTConnectPage.qml. The Meerun Android App did this exactly like that.

The chosen Bluetooth technology must then be saved as parameter in the settings.

thmichel commented 6 years ago

Yes, it's far from being perfect ;-)

First wanted to get it up and running to see if it works at all. Regarding the combo box, was thinking about this as well. Drawback is that the user needs to know what type of device he has (and I'd rather not rely on that :-) ).

I would like to first experiment with other options, e.g. trying all three connection methods simultaneously (if that's possible at all). I hope I find a way by the end of next week, otherwise the combo box can be used.

Regarding Battery Service: Can't you see a value at all or is it just not changing? It works for my device so it should be possible to fix this, I will add some more debug commands so we can see what's going on. You will see a log entry only when the level changes, not every second like the hart beat. I'll probably remove the heartbeat log now that it works to reduce the output a bit.

jdrescher2006 commented 6 years ago

OK take your time!

I will do a few more tests with the battery service and report back here!

ncartron commented 6 years ago

Hi Tom,

would you mind generating a RPM file for 1.1.4-1? I wanted to test it today but I can only find RPM for 1.1.3-1 on your Github.

Thanks Nico

On 29-Nov-2018 07:40 CET, notifications@github.com wrote:

OK take your time!

I will do a few more tests with the battery service and report back here!

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-442723640

thmichel commented 6 years ago

Hi Nico,

I just double-checked, it can be found here: https://github.com/thmichel/Laufhelden/releases

Regards, Tom.

ncartron commented 6 years ago

Right, so that's the page I was checking, and for some reason it was not here Now I have it, thanks! :)

On 29-Nov-2018 13:35 CET, notifications@github.com wrote:

Hi Nico,

I just double-checked, it can be found here: https://github.com/thmichel/Laufhelden/releases

Regards, Tom.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-442817957

-- Nico

ncartron commented 6 years ago

Now installed, I'll give it a try tomorrow and will let you know Tom!

ncartron commented 6 years ago

Right, so I tried this morning quickly with my Polar HRM, and it seems to work! (see pica) Battery level doesn't work though, but i don't really mind, and I'm not even sure the official Polar app does provide this info anyway. !

20181130083214

thmichel commented 5 years ago

Hi,

I have created a new release on my fork. As parallel connections did not work, I created a corresponding setting on the Bluetooth connection page. I have also re-added the support for "classic" bluetooth devices, but can't test as I don't own one. The BLE stuff seems to be quite stable now (at least for my device).

Please have a look at it and see whether we can push this back to your code.

jdrescher2006 commented 5 years ago

OK, I will check it out. I am looking forward to do this on monday.

jdrescher2006 commented 5 years ago

Did some tests with Bluetooth classic. Does not seem to work anymore. Here is the output: [W] unknown:46 - file:///usr/share/harbour-laufhelden/qml/pages/BTConnectPage.qml:46:5: QML Connections: Cannot assign to non-existent property "onConnecting" [D] Device::startDeviceDiscovery:105 - Scanning for devices ... [D] Device::addDevice:128 - "Last device added: HXM037426" [D] expression for onDeviceFound:55 - 1 [D] Device::addDevice:128 - "Last device added: SP-HRM-BLE-200" [D] expression for onDeviceFound:55 - 2 [D] onStatusChanged:27 - BTPage [D] Device::deviceScanFinished:141 - Scan finished! [D] Device::scanServices:157 - Trying to connect to "00:07:80:0F:AC:95" [D] Device::scanServices:193 - Trying to connect to address "HXM037426" [W] unknown:0 - void QBluetoothSocketPrivate::_q_readNotify() 50 error: -1 "Resource temporarily unavailable" [W] Device::deviceDisconnected:346 - Disconnect from device

jdrescher2006 commented 5 years ago

Maybe we can keep the old implementation as it was in Laufhelden. And if you choose Bluetooth Classic, we would use those old methods. Then if the user chooses BLE (random or public), we would use your new cpp classes. If you like, I can prepare this and add it to Laufhelden. I might find some time for that next week.

thmichel commented 5 years ago

That sure would be an option. I thought it might be easier to have both types in one class (so only one model is needed in the qml page). I published a new release for testing as I set a wrong port in the connectToServie call. I used 0 (NotOpen), you used 1 (ReadOnly). I have corrected this.

Another issue could be that I allowed to connect to the device while still scanning - that works for BLE devices, not sure about others. Maybe you would have to wait until the scan finishes.

Feel free to test again (or switch to two methods).

jdrescher2006 commented 5 years ago

Still doesn't work, scanning was finished: [D] Device::startDeviceDiscovery:105 - Scanning for devices ... [D] Device::addDevice:128 - "Last device added: SP-HRM-BLE-200" [D] expression for onDeviceFound:55 - 1 [D] Device::addDevice:128 - "Last device added: 78-B3-F7-17-3F-22" [D] expression for onDeviceFound:55 - 2

[D] onStatusChanged:27 - BTPage [D] Device::addDevice:128 - "Last device added: f023c2XO" [D] expression for onDeviceFound:55 - 3

[D] Device::addDevice:128 - "Last device added: f022c2YZ" [D] expression for onDeviceFound:55 - 4 [D] Device::addDevice:128 - "Last device added: 45-7F-03-B9-65-E8" [D] expression for onDeviceFound:55 - 5

[D] Device::addDevice:128 - "Last device added: HXM037426" [D] expression for onDeviceFound:55 - 6

[D] Device::addDevice:128 - "Last device added: 5A-4E-DA-62-9A-04" [D] expression for onDeviceFound:55 - 7

[D] Device::addDevice:128 - "Last device added: 7E-F3-98-84-60-57" [D] expression for onDeviceFound:55 - 8

[D] Device::deviceScanFinished:141 - Scan finished! [D] Device::scanServices:157 - Trying to connect to "00:07:80:0F:AC:95" [D] Device::scanServices:185 - Disconnecting from previous random address device... [D] Device::scanServices:193 - Trying to connect to address "HXM037426"

[W] unknown:0 - void QBluetoothSocketPrivate::_q_readNotify() 58 error: -1 "Resource temporarily unavailable" [W] Device::deviceDisconnected:346 - Disconnect from device

thmichel commented 5 years ago

Hi,

I think I've located the issue:

First we see it tries to connect to the correct device: [D] Device::scanServices:157 - Trying to connect to "00:07:80:0F:AC:95" Then it tries to disconnect an existing connection first - This should not happe as we do not have a connection! [D] Device::scanServices:185 - Disconnecting from previous random address device...

Then we try to connect using classic Bluetooth, but with name instead of Address: [D] Device::scanServices:193 - Trying to connect to address "HXM037426"

This fails of course. For a workaround, I commented out the disconnect section, now I can see a correct connection attempt. [D] Device::scanServices:157 - Trying to connect to "08:DF:1F:87:EB:01" [D] Device::connectClassic:225 - Trying to connect to: 08:DF:1F:87:EB:01_1 [D] Device::connectClassic:237 - Connecting... [D] Device::error:316 - Error: "Host is down"

This error is expected - the device is switched off (can't test with HRM device as I don't have one). So it should be fixable. I will look why the disconnect is being tried and will upload a new version tomorrow.

thmichel commented 5 years ago

Think I found it. When loading the Bluetooth settings page, the bluetooth type is not initialized so defaults to BLE Public. Only after switching to a different connection mode and back it works. Adding

id_Device.setBluetoothType(settings.bluetoothType);

in the onCompleted section should fix the error. I will upload a new version now.

jdrescher2006 commented 5 years ago

You got it, it's working now! Battery value with classic Bluetooth is working but not with BLE. Is this working for your BLE device? And can we somehow avoid having 2 BLE entries in the combobox (BLE Public and BLE Random)?

thmichel commented 5 years ago

Hi,

good to hear it's working now. Sadly reducing it down to two items is not a good option (from my point of view). The app does not know if it's public or random type - you cannot detect this during scanning. So the only way would be to try first public, then random - that would cause a 30 seconds connection delay for random devices (or vice versa) and throw an error.

On another thing, I was thinking to put a shortcut to the bluetooth connection page into the main menu (bypassing the step to first go into the settings menu) as this probably is often used when starting the app - what to you think?

If you are happy with the current state, I would create a pull request so it can be merged into your code.

Regarding the battery issue: It works on my BLE device. I can try to add some debugs into the next version. Another option would be trying to actively pull the battery state - currently the device sends updates to the App. Probably that does not work with your device. I'll prepare a test version and will upload it as soon as I can.

jdrescher2006 commented 5 years ago

I wonder how the original bluetooth search of the operating system handles this. It lasts relatively long to detect my HR device so there might also be a 30 seconds delay. I am thinking about if a 30 seconds delay might be OK for us.

Why do you think it is neccessary to open up the bluetooth conection page? Only if bluetooth is deactivated?

Maybe you can prepare a further test version with a fix for the battery issue?

thmichel commented 5 years ago

Hi,

regarding random and public addreses this is what the QT documentation says:

_Note: All other platforms handle this flag transparently and therefore applications can ignore it entirely. On Linux, the address type flag is not directly exposed by BlueZ although some use cases do require this information. The only way to detect the flag is via the Linux kernel's Bluetooth Management API (kernel version 3.4+ required). This API requires CAP_NETADMIN capabilities though.

So it seems we cannot detect which type it is. I would like to avoid the delay as using the correct type lets it connect within 2-3 seconds. It's also no problem to hit the "Connect" button during scan given teh device has already been discovered (which usually happens fast).

The bluetooth connection page I was referring to was teh one from Laufhelden. Idea was to create a shortcut to it bypassing the settings menu to allow quick access to it as it probably is being used each time you start up Laufhelden.

I will create a new version this week where I try to fix the battery level issue - or at least get some better debug output for it.

jdrescher2006 commented 5 years ago

Ok so let's stay with the three choices in the combobox.

Why would it be neccessary to go to the bluetooth page each time you start Laufhelden? I choose the HR device once and that's it. Is it not possible to save the selected bluetooth device to the settings and load it next time the app starts?

thmichel commented 5 years ago

The setting is saved and loaded on app start, but currently there is no automatic connect at startup. So to actually connect to the device, you have to first go to settings, heart rate device which takes you to the Bluetooth settings page where you have to hit "connect". I just wanted to speed that up a bit :-)

Another option would be to automatically try to connect to the saved device, or make that option a setting.

jdrescher2006 commented 5 years ago

It does not make sense to connect o app start, maybe the user only wants to check his last workouts... But there is already a mechanism to connect to the bluetooth device if a workout is started. If the RecordPage is opened there are the lines: if (sHRMAddress !== "" && settings.useHRMdevice && bRecordDialogRequestHRM === false && !settings.useHRMservice) { id_BluetoothData.connect(sHRMAddress, 1); bRecordDialogRequestHRM = true; }

Also check harbour-laufhelden.qml, there are other parts of the mechanism.

thmichel commented 5 years ago

Ah, thanks for pointing that out. That does not work for BLE devices - you need a scan first to discover them, just connecting to a known MAC does not work. So another thing to look at :-)

thmichel commented 5 years ago

OK, I have uploaded a new version that polls battery status every 10 seconds instead of waiting for the device to emit a signal. Please try if it helps. I fixed the issue for connection to HRM at start of workout, tested only with BLE so far.

jdrescher2006 commented 5 years ago

Sounds good, I will test it. Problem is I have currently no access to my BLE HR device (left it at my workplace). So I can only test bluetooth classic.

ncartron commented 5 years ago

Hi Jens and Tom,

I can test that today or tomorrow with my Polar BLE HR device.

Cheers, Nico

On 18-Dec-2018 07:19 CET, notifications@github.com wrote:

Sounds good, I will test it. Problem is I have currently no access to my BLE HR device (left it at my workplace). So I can only test bluetooth classic.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-448109868

DrYak commented 5 years ago

Yay, I'm happy, this fork BLE works with my Connect 3 in 1 HRM (and a quick look on aliexpress seem to show this is a popular chipset found in lots of cheap devices).

Any news when you'd expect the fork to by merged into the main Laufhelden ?

jdrescher2006 commented 5 years ago

@DrYak I hope we can merge it very soon, we just need to sort out a few thinks... I am planning a little christmas release :1st_place_medal:

@ncartron the more testers we have, the better!

@thmichel I made some tests with your current version (bluetooth classic only). Here are the results:

ncartron commented 5 years ago

Right, so I did a quick test by wearing my Polar HRM, and it was well detected and recognized, could see my HR frequency. When launching a new workout, HR frequency is also displayed.

I'll do real tests tomorrow when running and will let you know.

Thanks again! Nico.

On Tuesday, 18 December 2018, Jens Drescher wrote:

@DrYak I hope we can merge it very soon, we just need to sort out a few thinks... I am planning a little christmas release :1st_place_medal:

@ncartron the more testers we have, the better!

@thmichel I made some tests with your current version (bluetooth classic only). Here are the results:

  • scanning starts when dialog opens. This is not good. User wants to choose connection type first and then start scanning manually.
  • when on BTConnectPage.qml, after connecting to a classic HR device and then pressing disconnect button, nothing happens. No disconnect. Also combobox should then be invisible, it can be made visible if disconnection was successful.
  • if dialog is left (BTConnectPage.qml), there is an error: nknown:38 - file:///usr/share/harbour-laufhelden/qml/pages/BTConnectPage.qml:38: TypeError: Property 'disconnect' of object Device(0xab80a8b8) is not a function
  • After a workout, when the RecordPage is left, there is an error. After that the bluetooth device is not disconnected: [W] unknown:91 - file:///usr/share/harbour-laufhelden/qml/pages/PreRecordPage.qml:91: ReferenceError: id_BluetoothData is not defined [D] Device::readData:549 - Entering readData... [D] Device::readData:549 - Entering readData... [D] Device::readData:549 - Entering readData...

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-44829162

-- Sent from my Sailfish device

thmichel commented 5 years ago

Hi, the issues should be fixed; a new version is uploaded. The device disconnects now when the settings pages is closed (as it was before) and reconnects when starting a workout. Currently the combobox in the settings page is always visible, hiding it seemed to disturb the UI feeling for my taste - can change that if you wish.

@ncartron & @DrYak : Do you see the battery status of the device as well?

ncartron commented 5 years ago

Hi Tom.

thanks for the new version, I'll install it for my today's run :)

battery status still do not work for me, i.e. there's "battery status" but no value is displayed.

I don't think this is on your side though, I don't remember seeing this on my Android device with my Polar HRM.

Cheers, Nico

DrYak commented 5 years ago

Battery status shows 100% on a fresh coin cell.

(On the other hand, these are coin cells, they tend to have pretty voltage until almost right at the end of life, so I'm not sure if that peculiar HRM model will ever tell something else beside "100%" and dead)

ncartron commented 5 years ago

Right, so I did run today with Laufhelden and my Polar HRM, and the HRM got disconnected pretty quickly while running, see enclosed picture :(

I'm pretty sure this is not because of the HRM, since it works well when i run with my Suunto watch.

On Tuesday, 18 December 2018, thmichel wrote:

Hi, the issues should be fixed; a new version is uploaded. The device disconnects now when the settings pages is closed (as it was before) and reconnects when starting a workout. Currently the combobox in the settings page is always visible, hiding it seemed to disturb the UI feeling for my taste - can change that if you wish.

@ncartron & @DrYak : Do you see the battery status of the device as well?

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/jdrescher2006/Laufhelden/issues/123#issuecomment-44836453

-- Sent from my Sailfish device

thmichel commented 5 years ago

Can you test with latest version and start laufhelden from a terminal to get the debug output? That would hopefully show the reason why it disconnects.