Knowledge Base & Community Forums/Community Forums/Android OS Technical Discussion

Answered

Updated: Bluetooth Low Energy support in Strava for Android?

Chris Paton
asked this on July 27, 2013, 5:23 PM

Hello there,

The good news finally came this week that Android 4.3 will have full Bluetooth Low Energy support!
https://developer.android.com/guide/topics/connectivity/bluetooth-le.html

So, are there plans afoot to add support for Bluetooth LE heart rate and cadence monitors to Strava for Android? It would be awesome to see this done in order to bring Strava for Android up to speed with the iOS equivalent.

Thanks!
Chris Paton

Support edit: 

Since version 4.1.1 of Strava for Android was released in June, this Strava app now supports supports heart rate, cadence and power sensors that connect with Bluetooth LE.  It also features integration with Samsung Gear devices. 

 

Comments latest first

User photo
Elle Anderson
Community Support

Hello Android folks! 

For any of you who tried our Early Access or Labs version of the Strava app, we have a new Beta program we'd like you to know about. Please see the link below for more info and instructions on how to sign up.

Thanks for your help!

https://strava.zendesk.com/entries/49220360-Strava-Android-Beta-pro...

July 15, 2014, 1:10 PM
User photo
Elle Anderson
Community Support
Check Answer

Hi folks - 4.1.1 of Strava for Android was released a few days ago, and this version now supports supports heart rate, cadence and power sensors that connect with Bluetooth LE.  It also features integration with Samsung Gear devices.

Since this forum's purpose (and the original question asked) is now resolved/answered, I'm closing this discussion in favor of starting a new feedback channel here:

https://strava.zendesk.com/entries/46073310-Feedback-for-Strava-v4-...

Please check out the new forum and post your comments and feedback. Thanks! 

June 23, 2014, 2:00 PM
User photo
Elle Anderson
Community Support

Davide - there is another user with the same problem here: https://strava.zendesk.com/entries/44521944-Scanning-for-BTLE-4-0-H...

Perhaps you could compare notes and help us find the issue here? 

June 17, 2014, 1:15 PM
User photo
Davide Scalzo

@Byron: Sorry for the delay getting back to you.

When I look for my heart rate monitor the app gets stuck on "Searching...", both with the Lab build and the new production build. Other apps find it quite quickly.

  • Android HTC One 4.4.2
  • Not rooted
  • Viiiiva 4iiii
  • Using BTLE (obviously).
June 17, 2014, 5:09 AM
User photo
Joey da Silva

I posted back in May when I was kindly assisted to get my Motorolla Moto G running Android 4.4.2 working with my Polar H7 HR monitor using the Lab 265 build, which I have not knowingly updated, and which has been working perfectly till now.

I had a strange occurrence yesterday, as you can see on this activity: http://www.strava.com/activities/154354029 with it having worked perfectly the day before: http://www.strava.com/activities/153953199

I did pause the app (which I had done briefly on a test before) while I waited for our run club 5km to start (for about 15mins after running 2km to get there), but I see the HR flatlined well before this. The app is now not seeing the HR monitor at all, even after reboot and disabling bluetooth so the app triggered it switching on again, a day later. I have used my old Polar wristwatch which is showing the HR monitor and reflecting seemingly accurate HR's.

Appreciate any input to get this working again as I am running a half on Sunday and really hoped to track my HR!

June 17, 2014, 4:41 AM
User photo
Armand Crutzen

I had also issues when PAUZED. I had a flat tire and pauzed Strava. After fixing the tire I continued. After unpauzing Strava did not show any heartbeat. (ICardio which was running simultaniously did have actual HR!!)

Checking the ride at home it shows a flat steady line @ 119BPM for about 7 minutes. After that it apparently picked up the signal again.

http://www.strava.com/activities/150879772/analysis

 

Nexus 5 4.4.3; Strava 4.1.0 (changed to official Strava instead of Labs version)

June 10, 2014, 9:19 AM
User photo
Joseph Gaffney

Something seems to be odd with pausing.  I took a light ride this morning with my wife, paused when we took a break, and definitely unpaused when we started riding back.  Even showed as running when we got home, but only the first half up until I paused actually went through:

http://www.strava.com/activities/151806583/overview

June 10, 2014, 7:57 AM
User photo
Mattias E.

I returned my Runtastic Heart sensor before I had the chance to do any additional testing with different pockets. I have now bought a Polar H7 heart rate monitor instead, and even though they actually state that carrying the phone in a back pocket is not supported, it works very well. I now have two rides around an hour that were recorded without any problems, carrying my phone in my left back pocket (since that the best one according to previous comments). So the Polar H7 is definitely the better heart rate monitor of the two for biking.

One thing I notice with both heart rate monitors, is that Strava seems to be slower than other apps to find the monitor and when things get flaky (I guess to the bluetooth stack in android) Strava seems to have a worse time than Runtastic and Polar native apps. So there seems to be some difference in finding the heart rate monitor. Do you always scan, where the others maybe only go for the already known and paired devices?

June 9, 2014, 2:39 PM
User photo
Piotr Bilik

I see all the talk about BLE but how about ANT+?

June 6, 2014, 8:30 PM
User photo
Tommi V.

Hi,

I've been using official Strava Android app 4.1 for some time now, and I've now got multiple times an issue that heart rate recording works just fine, but next time for next training session when I start Strava app, it says "Heart Rate sensor detected" but does not get heart rate after that. All I can do in this situation is reboot my phone and start Strava again, and then heart rate monitoring works fine. When I get into this "stuck mode" with the phone, also other apps (Endomondo and Polar Beat) cannot read heart rate, but also find the sensor just fine. Before Starav 4.1 release I was using Endomondo to track my heart rate, and I had never before experienced this kind of situation. My phone is Samsung Galaxy S3 (GT-I9300) and I'm using Polar H7 heart rate strap if that matters.

June 6, 2014, 5:10 AM
User photo
Mark V.

Hi Byron,

My issue with mileage being dropped at the end of my routes is resolved. Turns out I needed to have time set to get time from network.

Updated to latest build and all working perfectly...Thanks!

June 4, 2014, 1:44 PM
User photo
Yuji Horimoto

Bryon,

Today's ride worked well today (aside from forgetting to unpause the app at one point).  However, the max Cadence doesn't look right.  I think the max rpm i got was 86? http://www.strava.com/activities/148221452/analysis

June 1, 2014, 10:58 AM
User photo
Joseph Gaffney

@Byron, I tried with my body in between the phone and sensor various times, and it seems to be reconnecting ok.  It is less, 6 to 6 1/2 feet (I didn't bring my tape with me, forgot) is about the limit.  The data still seems off though, with random dips and relatively long flat  periods.

Still using Labs 265, Nexus 4, 4.4.2 rooted, Mio Link HRM, and Wahoo SC cadence sensor.

June 1, 2014, 7:42 AM
User photo
Jason Rafanan

nexus 5 / 4.4.2 / wahoo ble hrm / jarv SPD/cadance / build 265

 

cadence seems wonky.... 

 

http://www.strava.com/activities/147148918/analysis

May 29, 2014, 11:58 PM
User photo
Joseph Gaffney

@Byron: That was unobstructed.  I'll play around a bit with my body inbetween, see what I can make happen.  I just got home from my weekend away (and unfortunately didn't have a bike rack so I could take my bike with me until this morning), but weather permitting, I'll play with this tomorrow. And 2.4ghz is bad with dense material, so that makes sense.  I'll see what I can come up with, try to replicate the disconnect, see what happens.

May 27, 2014, 5:58 PM
User photo
Byron Hood

Hi all,

The team published Strava 4.1.0 today, which includes, among several other awesome features, support for BLE heart rate monitors. I want to thank everyone here who helped to test the Labs app - your feedback was valuable in finding and fixing things I'd missed.

Unfortunately, cycling cadence (including speed+cadence) and power sensors are not yet supported in this release. We decided this on the basis of some of the issues people here were experiencing with maintaining connections to cadence or speed+cadence sensors, as well as the results of our internal testing.

As you have seen in the Labs build, the functionality to connect to power, cadence, and speed+cadence sensors already exists, and I hope that we will be able to release it very soon. I purchased a Stages power meter not too long ago, so I'm personally invested in this feature.

I am leaving Labs build 265 up so that you can still record with power and/or cadence sensors if you like. You can find it at:
https://rink.hockeyapp.net/apps/dbbeadd6c63647932675c38d41247606

-Byron

May 27, 2014, 2:59 PM
User photo
Ravshan Kosimov

Hi!

I've bought today Polar H7 to use it with my LG G2.

It is in the PAIRED DEVICES list. It works with Endomondo and Polar Beat, with no problems, but Strava doesn't see it.

Android 4.4.2

Strava 4.0.2

I see that many people wrote that they using Strava 4.1.0, where I can get it?

May 27, 2014, 7:26 AM
User photo
Byron Hood

@Matthias: before you return the HRM, could you try each of your jersey back pockets separately? A number of my colleagues have noticed that the center jersey pocket (if you have one) tends to be the most problematic in terms of signal (for all three sensor types), but that the left side is best, and even the right side is better than the center.

I have no personal experience with either, but several colleagues have Wahoo HRMs, and there have been a good number of success stories on this forum as well.

May 25, 2014, 2:20 PM
User photo
Byron Hood

@Chad: I'm sorry to hear that the app crashed. Could you be more specific about which build you were running, and precisely on what screen or button press the crash happened? Did you have a previous Labs version on your phone before installing the version currently installed? If you go back to the record screen, are you prompted to save the activity?

If you're looking for a more stable experience, I'd suggest sticking with the store app (or at least recording with both simultaneously). Labs builds are necessarily buggier and unfinished, because they are prototypes - a midpoint in our development process, not a finished product.

May 25, 2014, 2:10 PM
User photo
Mattias E.

@Byron I just figured out what the problems with the Runtastic Heart Rate Monitor. It worked fine when I was running, but always failed when I was out riding MTB. The cause for this is, that when I ride I have my phone in my pocket on my back, and then the connections fails. I reproduced this by just holding my phone in front of me, verifying that the pulse readings are ok, then I held it behind my back for 10 seconds and when I looked at it again the connection was dropped.

I just contacted the seller of this heart rate monitor to return it...  I notice that Strava sells the Wahoo btle heart rate monitor, does that work even when the phone is in the jersey back pocket?

May 25, 2014, 2:00 PM
User photo
Byron Hood

@Ethan, @Boyd, @Oscar: good to hear! thanks for helping to test the app.

May 25, 2014, 1:57 PM
User photo
Byron Hood

@Davide: is this an issue with both the record screen and the settings screen?

When the phone is scanning on the settings screen, what does the subtitle under "Heart Rate" say?

May 25, 2014, 1:51 PM
User photo
Byron Hood

@Matthias thanks for the clarification. I'll keep an eye out for this.

May 25, 2014, 1:40 PM
User photo
Byron Hood
@Joseph: was that 15' unobstructed? I've been able to reproduce some connectivity issues when standing about 1.2m/4' from the phone and positioning my body between the sensor and the phone. The connection always came back for me within a few seconds, but it wasn't exactly a real-life test either. I've been told that the underlying issue has to do with the frequency band that Bluetooth uses - apparently it's one of the frequencies absorbed by water. It's a bit silly, as nearly every BLE sensor I can think of - especially cadence, power, and HR sensors - tend to be placed in such a way that the body obstructs communication to the phone.
May 25, 2014, 1:39 PM
User photo
Oscar Víquez

Hello,

Just reporting, My morning ride was tracked with no problems whatsoever.

 

Sensor: Polar H7

Phone: Galaxy S4

OS: 4.4.2

Ridehttp://www.strava.com/activities/144954358/overview

May 24, 2014, 11:55 AM
User photo
Chad Reece

I agree with Tony 100%.  I to have been doing the lab updates and quite frankly it seems to be getting worse instead of better.  I updated the labs version last week and it has crashed twice already.  Today was the final straw.  Lost an entire ride when the app crashed during the upload after the ride.   There is no record of it.  vanished into thin air!  yes....i'm pissed.  I pay for a premium account and right now i can get better and more reliable service from a FREEBIE on the play store.

 

May 24, 2014, 10:37 AM
User photo
Tony Solon
What is the planned release date for a stable version supporting btle?

I've been receiving updates on testing results from this thread for almost a year. Have yet to see any update indicating a completion date. It seems obsurd that it has taken so long already! Could we have a best guess ETA please?

I work in software dev and have dev'ed with the BT stack alot. At no time on any project I've been involved in would this "speed" of execution been accepted. Am I being impatient here, or are my thoughts reflected in others?
May 22, 2014, 11:25 PM
User photo
Boyd Kelly

@joseph @bryon

Thanks Joseph for the tip.  

I also tweaked the cadence sensor, and didn't have any issues yesterday.  Looks good!  Can't wait till the app comes out in general availability!

http://www.strava.com/activities/144081736/analysis

Boyd

 

May 22, 2014, 2:49 PM
User photo
Ethan Henry

Hey Mateo,

I downloaded Labs build 265 and it worked great with my Nexus 4 and my Polar C7. Great work!

May 21, 2014, 9:29 AM
User photo
Davide Scalzo

@Byron, yes it works fine with other applications, at the moment I am recording with another app and then export the TCX to Strava.

It just seem to not sync, at all.

May 21, 2014, 3:29 AM
User photo
Mattias E.

@Byron I used the pebble on all my tests to watch the sports progress, I just didn't use it for pausing in Test 1 and my Intervals. So being connected to multiple btle doesn't seem to be the problem either. If I were you I'd keep my eyes open for more random failures, if that happens add some debug to see if it is the connection that gets dropped, or some problem in the thread reading or if it is the storage that fails.

Anyway, thanks for a great job on implementing this!

May 20, 2014, 10:24 PM
User photo
Joseph Gaffney

@Boyd, I have noticed that after you've connected in settings, it doesn't stay connected when you exit, and will reconnect.  Tap on the bike icon, it will show connected devices there.  You should see an announcement that the cadence sensor was detected, and in that drop down from the bike, it will say 1 BLE sensor connected.

May 20, 2014, 7:35 PM
User photo
Boyd Kelly

@Byron:  I'm using a Moto G, and a Wahoo Blue SC.  I just got the cadence sensor, so I can't confirm that it was working with anything else.   However I verified before recording that the sensor was recognized as connected in the settings.  I took off and did not touch anything till the end of the ride.  I'll give another go at it tomorrow.

 

May 20, 2014, 7:31 PM
User photo
Joseph Gaffney

@Byron: I gave the connection a quick test over distance.  Still stable at 15', with a low signal.  So I'm not entirely certain the issue is distance, I don't think I got more than 6' away when I got up to take pictures.

May 20, 2014, 7:17 PM
User photo
Byron Hood

@Boyd: what phone and cadence sensor are you using? It looks like the phone was having trouble connecting to the sensor and was only able to get two readings (1rpm and 15rpm). Did you happen to turn the screen on at some point during the ride besides the beginning and end?

May 20, 2014, 6:53 PM
User photo
Byron Hood

@Hans: I'm glad to hear that it worked, thanks for testing the app!

While sensors should be capable of handling multiple simultaneous connections, the client-server architecture of Bluetooth can make it harder on the sensor to record in multiple apps simultaneously. The Strava app doesn't try to monopolize or "steal" the sensor data, but it's possible that the sensor only supports up to one connection to the phone at a time.

May 20, 2014, 6:50 PM
User photo
Byron Hood

@Davide: were you able to detect the HRM in any other BLE-enabled app?

May 20, 2014, 6:26 PM
User photo
Byron Hood

@Matthias: thanks for the detailed testing! For a reason I'm unable to identify, the first recording with BLE seems to have more issues than later ones. The app doesn't treat first-time recordings any differently than later ones, so I imagine it has something to do with the stability the underlying first-time BLE connection versus a well-established connection.

As you guessed, pausing/resuming shouldn't impact BLE connections. The same should be true with a Pebble, but since both the sensor and the Pebble use Bluetooth (sensor is BLE, the Pebble is Bluetooth Classic) it's possible that some devices may have trouble handling both. Android documentation states that the system can handle multiple simultaneous connections on different Bluetooth protocols, but the hardware in older phones might still get confused. If you have trouble whenever you use the Pebble, and success without, that might be the issue. Otherwise, I wouldn't worry about it.

May 20, 2014, 6:25 PM
User photo
Byron Hood

@Joseph: thanks - I'll see if I can reproduce that and try to make the app respond a bit better in those situations. I'm guessing that the distance from your cadence sensor to the phone is nearing the limit of the sensor's signal range to begin with (and this wouldn't be helped by body parts getting in the way), and when you get off to take a photo, the sensor and phone completely lose contact.

May 20, 2014, 5:52 PM
User photo
Boyd Kelly

Hi,

I am having no issues with the Wahoo HRM, but the cadence sensor is not working.  Here it shows 1 and the 15 rpm for my entire ride home.  I checked that the magnets seem to be adjusted correctly, but I'll fiddle some more.  

http://www.strava.com/activities/143684631?ref=1MT1yaWRlX3NoYXJlOzI... 

Thanks!

Boyd

May 20, 2014, 5:34 PM
User photo
Joseph Gaffney

Riding today, without pausing or taking pictures, and the cadence sensor worked fine the entire time.  The issue seems to be whenever I switch out to take a picture with instagram or to pause the ride, the cadence sensor disconnects and does not reconnect.

May 20, 2014, 12:21 PM
User photo
Mattias E.

I did some short intervals today and used my runtastic heart rate monitor with my Nexus 4 and Strava labs 265, and it worked perfectly. http://www.strava.com/activities/143561471

I guess there were some other issue causing my first ride to malfunction, my conclusion is that runtastic heart rate monitor is working as expected.

May 20, 2014, 12:12 PM
User photo
Hans Kwakkel

as promised here are the results of the sony xperia T from The Netherlands :)

http://www.strava.com/activities/143488258/analysis

worked flawlessly during the ride, but it did take some time to upload the results. at first it said that the results couldnt be uploaded because of a disconnecting WIFI, but i could get online perfectly so clearly that wasnt the real problem.

 

in hte end it did upload the results as shown in above link.

 

during the ride i had the app on at all time. Because the strava app used the HRM-output, appearantly, my other app wasnt able to make use of the same data (Fietstijden.nl) not a biggie, but maybe it is something to take into consideration.

 

All-in-all im happy the device connected and performed as hoped/expected :)

 

Keep up the good work, and get it in a release as soon as feasible :)

May 20, 2014, 11:19 AM
User photo
Hans Kwakkel

hey guys, i just bought a Polar H7 HRM yesterday and will try to get the .265 version on my experia T before i'll ride back home. (didnt see any test results for a sony device while scanning the topic)

ill post the specifics as soon as ill get home:

Mobile: Sony Experia T (LT30P)

Android: 4.3 

May 20, 2014, 12:10 AM
User photo
Mattias E.

I just realize it might be interesting to know what other hardware I'm running. The combination I used in my tests above is a Nexus 4 with Android 4.4.2 and the Runtastic Heart Rate Combo Monitor.

May 19, 2014, 11:50 PM
User photo
Davide Scalzo
Hi all. I tried the latest lab version with HTC one running 4.4.2 unrooted with a Viiiiva HRM.

No luck in detecting the device :(
May 19, 2014, 1:03 PM
User photo
Mattias E.

Just got a runtastic btle heart rate monitor and tested it with strava labs 265. It finds the heart rate monitor and displays the pulse correctly on the recording screen so the basic functionality seems to be there. However the recording of my first ride seems to be quite weird even though I verified that it showed correct heart rate before starting the session.

http://www.strava.com/activities/143126971/analysis

After the ride I checked the app and it displayed my current pulse correctly, so I don't understand why the recording is wrong. Since I used a Pebble smart watch I started the session then paused immediately to put away the phone, put on my gloves aso. then resumed the ride when we actually started. I also ended the ride by pausing on my pebble then stopping on the phone. My initial thought was that this might be causing problem. But in my tests later (se below) pause resume doesn't seem to affect the heart rate recording.

 

When I got home I tested again by just walking and jogging around the block (I guess these are within my privacy zone, so you have to either friend me or as a developer access the data using some privileged access).

http://www.strava.com/activities/143160370 - Simple test where I waited for the recording page to show heart rate, then started a session walked/jogged and stopped the recording.

http://www.strava.com/activities/143161519  - Test with pauses where I started, paused, resumed walked/jogged paused/resumed some more. Note that this pausing/resuming was NOT done through the pebble, but I don't see how that could affect things.

Both these tests seems to work fine, so I'm quite confused why it didn't work for the ride.

May 19, 2014, 12:10 PM
User photo
Joseph Gaffney

@Byron, another ride, same configuration, the HRM worked perfectly, and once again, Strava dropped the cadence sensor.  I checked the positioning when I got home, as well as whether or not there was communication with my Nexus, and with the Wahoo Fitness app, it worked.  So it seems communication with the Wahoo SC is a bit erratic on build 265.

May 19, 2014, 10:14 AM
User photo
Alec McEachran

Any update on a ship date for this? Jelly Bean has been out for a while and this thread is getting close to a year old. I can't install unverified apps on my (corp) Android device, so have to wait for the official update.

May 19, 2014, 8:08 AM
User photo
Byron Hood
@Guil: that's great to hear! Thanks for helping to test the app.
May 18, 2014, 10:22 PM
User photo
Byron Hood
@Mark: let me know if there's any improvement. Could you perhaps record the same trip on both the Play Store build and the Labs build, and post both activities? That way I can analyze the difference between the two uploads and potentially spot the difference faster.
May 18, 2014, 10:21 PM
User photo
Byron Hood
@Joseph, @Yuji: it looks like your cadence sensors got disconnected midway through the ride, and the app wasn't able to reconnect. I'll try to replicate something like that and see if I can't get the app to respond a bit better.
May 18, 2014, 10:16 PM
User photo
Yuji Horimoto

Speed seemed to be good.  HRM was weird at beginning but seemed to straighten out.  Not sure what happened with the cadence portion though.  http://www.strava.com/activities/142728470/analysis

May 18, 2014, 5:38 PM
User photo
Yuji Horimoto

Bryon,  my bad!

It seems that my HRM battery died because the sensor was still attached to the band which causes it to still report via bluetooth.  I had to replace the battery and now it's working and was able to use  while riding Citibike. http://www.strava.com/activities/142424893/analysis

 

I'm going for a ride in an hour so i'll report the results with cadence and HRM at the same time.  Thanks for the hard work Bryon!

May 18, 2014, 5:59 AM
User photo
Thomas Viteau
May 18, 2014, 4:35 AM
User photo
Jacob Broido

Hey, I just received a MIO link HR monitor, would be interested in testing it on labs build of strava - how can I get it.

Thanks

May 18, 2014, 4:19 AM
User photo
Guilherme Moura
Hi my name is Guil . I used the latest version of Strava Labs (4.1.0) today and it worked flawlessly.

Ride Link : Check out my 19.8 mi Ride on Strava: http://app.strava.com/activities/142241099

Phone : Nexus 5

OS - 4.4.2 Kitkat

Sensor - Polar H7
May 17, 2014, 11:18 PM
User photo
Joseph Gaffney

@Byron, Mio Link is still working well, but I had something really odd happen with my Wahoo SC cadence sensor.  I stopped to take a picture, and cadence got stuck at 21 rpm for the entirety of the ride there on out: http://www.strava.com/activities/142279517/analysis

May 17, 2014, 12:12 PM
User photo
Mark V.

Hi Byron,

 

It only seems to drop Km's off the end of my rides, however I did not see this issue on my rides home last night (below), Let me continue testing next week and feedback.

 

http://www.strava.com/activities/141460957

http://www.strava.com/activities/141503991

May 16, 2014, 3:46 AM
User photo
Byron Hood

@Paul: there are a few possibilities here, but my first guess would be bad GPS reception. Were you inside when you were testing the app?

To get around that problem, you can use an app like Location Spoofer to fake the device's GPS location. That way you can rest assured of continuous location updates even when inside or in an area with poor GPS reception.

May 15, 2014, 8:22 PM
User photo
Byron Hood

@Neil: it's great to hear that it worked for you, and thanks for your help testing the app!

May 15, 2014, 8:17 PM
User photo
Byron Hood

@Joseph: I'm glad to hear that the MIO worked out for you! It had given me a lot of trouble in a previous iteration of the BLE implementation, late last year.

Thanks for the suggestion. I'll take it into account, but I can't promise anything in terms of delivery - I'm already stretched thin between this and other projects on our Android app!

May 15, 2014, 8:16 PM
User photo
Byron Hood

@Mark: while I'm not particularly an expert on GPS data, it appears (if I recall your previous post correctly) that about 1km is being taken off the end of each of your rides. Is that the case, or is some being taken off the beginning as well? Has this never occurred with the Play Store build?

May 15, 2014, 8:13 PM
User photo
Byron Hood

@Yuji: do you have any other apps (e.g. Wahoo Fitness) on your phone with which you can test the HR sensor? If Strava is saying "searching" that indicates to me that there's a problem in the scanning/identification phase, and the heart rate monitor is either not responding to the Bluetooth scan, or is being misidentified as a different sensor type.

May 15, 2014, 8:08 PM
User photo
Paul Tiplady

@Byron - Is it a separate issue that there were only 3 GPS points in a 5+ minute recording? Or is that expected if I'm not moving around much?

Cheers,

Paul

May 15, 2014, 3:14 PM
User photo
Paul Tiplady

@Byron - Is it a separate issue that there were only 3 GPS points in a 5+ minute recording? Or is that expected if I'm not moving around much?

Cheers,

Paul

May 15, 2014, 3:14 PM
User photo
Neil McEachran

Moto G, Stock 4.4.2

Strava Labs build 265

Wahoo Blue HR

http://www.strava.com/activities/141366167 - This all worked perfectly for me with Wahoo Blue HR.  No issues at all.  Thanks for all the good work on this build.

May 15, 2014, 6:25 AM
User photo
Joseph Gaffney

Nexus 4; Rooted stock 4.4.2, build KOT49H, using modified radio, .98 + LTE.

Strava Labs 4.1.0 build 264

Mio Link came in, so I tested that out.  It connects immediately in both the Mio GO software and in Strava, no issues whatsoever.  Which says to me that the oddly longer connection time of the Wahoo SC in Strava but not in Wahoo Fitness is unrelated to how Strava is handling BLE connections, or at the very least, its more specific to the cadence sensor connection.

I do think that something more than a check box, like a connection/settings window would be good, to see the device connections and their signal strength for each, something like that would go a long way.

May 15, 2014, 5:56 AM
User photo
Mark V.

Hi Byron,

I have updated with latest build and restarted my Samsung 4 however still seeing issues with GPS being dropped on both my rides this morning.

http://www.strava.com/activities/141299045

http://www.strava.com/activities/141316850

 

May 15, 2014, 2:48 AM
User photo
Yuji Horimoto

or rather, searching.

May 14, 2014, 7:21 PM
User photo
Jason Rafanan

@byron: both times it said sensors were detected 

May 14, 2014, 7:15 PM
User photo
Yuji Horimoto

Nope.  It said connecting.  

May 14, 2014, 7:11 PM
User photo
Byron Hood

@Yuji: can you connect to the HRM at all via the settings?

May 14, 2014, 6:43 PM
User photo
Byron Hood

@Jason: I'm not sure why it worked this time, but not last time. Did you see the "cadence sensor connected" message when you recorded the ride that had errors?

May 14, 2014, 6:42 PM
User photo
Byron Hood

@Thomas & Paul: I'm glad to hear that it worked, thanks for helping to test the app!

Paul: this is a known issue with how sensor data points are processed. The server tries to match each sensor data point to a GPS point; since there are only 3 GPS points in your activity, there can only be 3 heart rate points. I'm working on getting someone to fix this, but it's a bit of a complicated process.

May 14, 2014, 6:39 PM
User photo
Yuji Horimoto

Byron,

Here's my last ride.  Cadence and speed looks good.  Still no go with HRM.  

http://app.strava.com/activities/140835828/analysis

May 14, 2014, 6:16 PM
User photo
Jason Rafanan

Check out my 29.3 mi Ride on Strava: http://app.strava.com/activities/141133858

cleared everything

nexus 5 / 4.4.2 / wahoo ble hrm / jarv SPD/cadance / build 265

May 14, 2014, 2:32 PM
User photo
Paul Tiplady

Just tried build 256 on my Nexus 5, with a Polar H7 BLE strap.

The monitor sync'd, and seemed to be producing readings. However, when I left the app running it seems to have failed to take repeated readings; the gpx only has 3 data points, with a 5-min gap between 2 and 3.

http://www.strava.com/activities/141165238

May 14, 2014, 1:18 PM
User photo
Thomas Viteau

Xcover 2 with cyanogenmod + mio link

No problèmes to record HR

http://app.strava.com/activities/140898319

May 14, 2014, 2:37 AM
User photo
Jason Rafanan

@byron: i have strava labs running in the background. i always wait until both heart rate and cadence sensors are detected then switch to wahoo. i use wahoo as my cyclometer since strava doesnt display mph or cadance in real time (free acct cant speak for premium) and had both heart rate and cadence displayed on wahoo during my last ride. ive been running like this the past 3 builds that haver been posted. before i would have strava (google play version) in the background with wahoo. im going on a ride tomorrow AM... ill clear all the data before my ride and hope for the best.

 

@Jason: did you happen to turn on the record screen around the time that the app finally managed to connect to your HRM?

May 12, 2014 01:17 PM
May 13, 2014, 10:01 PM
User photo
Byron Hood

@Michael: I'm glad to hear that the HR data was in line with what you're seeing in other apps. Thanks for helping to test the app!

As Yuji noted, there are a few unexpected GPS-related experimental features in build 264, but they have been removed in build 265 as well as the upcoming official release.

May 13, 2014, 11:23 AM
User photo
Byron Hood

@Yuji: let me know how it goes. Sometimes it also helps to reset the sensor by removing the battery for a few seconds.

May 13, 2014, 11:03 AM
User photo
Yuji Horimoto

Michael,  check build 265.  

May 13, 2014, 8:52 AM
User photo
Michael Muljana

Galaxy S3, on official 4.3, SMART helmet

264 build appears to work well,.

HR is a little wacky, but is the same HR as Endomondo, ,so do not think its on Strava end, both my last two rides also had some minor GPS issues that have not been issues before with this phone (Prior on Samsung Captivate, they were an issue)

http://www.strava.com/activities/139520409

http://www.strava.com/activities/137552371

 

No cadence nor power meter here, so unable to test those

May 12, 2014, 9:34 PM
User photo
Yuji Horimoto

Ah ok.  I did not see "Heart rate sensor detected".  When looking at settings, cadence sensor immediately comes up but HRM still remains at searching.  I'll play around more with the cadence sensor positioning.  

May 12, 2014, 9:14 PM
User photo
Joseph Gaffney

@Byron, it wasn't phone position, but the sensor on the frame relative to the magnet on the crank arm - so not a Strava issue there, user error.

May 12, 2014, 4:55 PM
User photo
Byron Hood

@Joseph: that's great to hear! Could you describe in more detail what you did to fix the sensor and/or phone placement? I'd love to pass those on to our support team when the time comes.

May 12, 2014, 4:24 PM
User photo
Byron Hood

@Yuji: sorry, I was referring to the previous ride you posted (one titled "afternoon ride cut short by rain"). For the other one - yes, it appears no connection ever occurred. Did see you see the "Heart rate sensor detected" message on that ride?

For cadence data, is it possible that the sensor or phone placement has changed? I haven't found anything amiss yet on my end, and that seemed to fix things for Joseph.

May 12, 2014, 4:22 PM
User photo
Joseph Gaffney

@Byron, did some experimenting tonight between Wahoo and Strava after I once again saw 0rpm.  Wahoo was off, but still had some occasional readings, so I readjusted the sensor position.  Looks like that did the trick.  The latest showed data, and I wasn't paying enough attention to say that its right, but its definitely working!

Mio Link comes in on Wednesday 

May 12, 2014, 3:58 PM
User photo
Yuji Horimoto

Here ya go.  I'm going out for a short ride in a few minutes and going to clear data just in case.  WIll post that log too.  

May 12, 2014, 2:49 PM
User photo
Joseph Gaffney

Looks like the log shows the same, 0's straight down.

May 12, 2014, 2:13 PM
User photo
Byron Hood

@Joseph, @Yuji, @Jason: there should be a file called "ble.log" in the Strava directory on your SD card. Would you mind posting with that file attached?

May 12, 2014, 2:07 PM
User photo
Yuji Horimoto

Byron, I don't think the HRM ever detected connection in the first place.  Whenever I do resume my rides, I'm always at the Record Activity pages as that's where the pause/unpause button is anyways.  

May 12, 2014, 2:04 PM
User photo
Byron Hood

@Joseph: looks like cadence data was uploaded, but was all zeroes. I'm am investigating what might be causing the issue.

May 12, 2014, 1:34 PM
User photo
Joseph Gaffney

@Byron, certainly:

http://www.strava.com/activities/139311569

http://www.strava.com/activities/139464487

No cadence data present, and only the one sensor to connect to right now (and showed as connected).  

May 12, 2014, 1:20 PM
User photo
Byron Hood

@Joey: I'm glad to hear that it worked! Thanks for helping the test the app.

May 12, 2014, 1:17 PM
User photo
Byron Hood

@Jason: did you happen to turn on the record screen around the time that the app finally managed to connect to your HRM?

May 12, 2014, 1:17 PM
User photo
Byron Hood

@Yuji: With a break that long, I'm guessing that your heart rate monitor may have gone into some kind of "sleep" mode and reset the connection to the device. The app should be able to recover from that, but you can give it a helpful nudge by going back to the record screen (this causes the app to rescan for sensors).

May 12, 2014, 1:14 PM
User photo
Byron Hood

@Joseph, Yuji, Jason: I'll look into the issues with cadence recording.

Joseph, could you post an activity link (private is fine) to either of those rides?

 

May 12, 2014, 1:11 PM
User photo
Yuji Horimoto

I just went on another bike ride today.  Speed/Cadence seemed to sync up.  HRM didn't .  Looking at the Speed Analysis, speed seems to be fine but cadence not quite sure.  Looking at the Time Analysis, it seems that the pause doesn't pause the timer and the non-ride time is counted into the analysis.  Is that supposed to happen?

http://www.strava.com/activities/140090118/analysis

May 11, 2014, 3:47 PM
Topic is closed for comments