This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

3.50 doesn't fix my phone connectivity issue. Is Garmin working on a new release?

I'm on 3.50 and my 830 won't find/connect to the phone via BLE.  The only way I found that will allow a BLE connection is to bring up GC that's running in the background.  If I don't bring GC to the foreground the 830 won't connect to the phone automatically.  Very frustrating.  My 520 has no such issue.  Would like Garmin to acknowledge that this is a bug.

  • I have this exact same issue on my 530. Connect fine to the phone but only when GC is running. If I dont have GC open it wont connect.

  • Thank you.  I'm glad I'm not the only one with this problem.  Matthew from Garmin has opened a new topic on the 530 forum.  He's seeking user input with this issue.  Please post your experience there to help Garmin troubleshoot the issue.  Thanks so much.  Here's the link to the topic:  https://forums.garmin.com/sports-fitness/cycling/f/edge-530/166691/ride-upload-issue-while-connected-to-wifi-and-bluetooth-after-updating-to-sw-3-50

  • I have this exact issue. 98% of the time I have to open Garmin Connect Mobile to get the edge 830 to connect to my phone.

    Just did a bunch of testing here.

    If my phone is in range of the Edge while I turn the Edge on, it will connect to the phone 100% of the time. 

    If my phone is not in range of the Edge when I turn the Edge on I need to open GCM to get the Edge to connect to the phone.

    If I turn the Edge on then come into range with the phone the Edge unit just continually says "searching or connecting" but it never connects.

    Whether I have GCM open or not it doesn't matter. If you turn the Edge on while the phone is out of bluetooth range it doesn't like to connect.

  • I have also done extensive testing and my experiences differ from yours.  With my phone within range and with GC running in the background, turning the Edge on it won't automatically connect until I bring GC to the foreground.  The next part is interesting.  With the 830 connected to the phone, I leave the phone in the garage and leaves for a three-hour ride.  Upon returning home once the 830 is within range of the phone it will automatically connect without me touching the phone.  But if I leave the house without having the 830 connected to the phone to start my ride, then upon returning and coming within range of the phone the 830 will never connect unless I bring GC to the foreground.  The last test is also interesting.  If I make the 830 connect to the phone and then turn off the 830, upon powering up the 830 immediately it will find/connect to the phone.  It will work like this until the very next morning when I power up the 830 and it won't find/connect to the phone.  It almost seems like the 830 (or the GC) has some short-term memory and the phone connectivity is tied to that short-term memory.  If I leave the 830 off for more than 6 hours then power it up it won't find/connect to the phone.  I hope Matthew at Garmin will take our notes to the Engineering team.

  • Did some more testing. Contradicts my first test. My phone was within 5 feet of the Edge and it did not connect when powering on the Edge. Testing the other day it was consistently connecting. On my commute this morning I had to open GCM to get a bluetooth connection.

  • I'm having the same connection issues with my iPhone and the 830. It will connect on it's own maybe 20% of the time. I have to open GC before it will establish a mobile connect to the 830 in most cases. 

  • Today om my ride for an hour after about 20 minutes the connection lost with my phone and then after 2 minutes or so the connection came back. This was no problem with the previous software.

  • Yes.  That's been my experience as well.  Having the phone within BT range doesn't guarantee a connection when turning on the Edge.  It's a hit and miss.  But opening up GC will guarantee a connection when the Edge is already turned on.  As I stated earlier my 520 doesn't need GC to be in the foreground to connect, so I consider this as a bug on the 830.  If Garmin can fix this then the 830 becomes a great computer.  This is the only issue I have with the 830.  I haven't experienced a single sensor drop nor a freeze.

  • Thanks for the feedback.  This is a diff. problem than mine since I don't carry my phone when I ride, but I could possibly have the same issue.  Do you have trouble connecting to the phone when you first turn on the Edge?  Or do you need to bring GC to the foreground to connect via BT?

  • the bluetooth connection has been my only issue. I had an 810, 820 and now 830. The 830 has been amazing so far.