Related
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

Firmware 5.04 Beta feedback

Former Member
Former Member over 8 years ago
Hi

I will note some of my experience with Firmware ver 5.04 Beta
1. Installation – No issues
2. Cosmetically (watch face, screens) same
3. Whatsapps notification – (text inverted)Fixed from ver 4.70 and 5.03 Beta
4. Heart rate monitor lock (time it takes the watch to lock onto your heart rate, any screen. I was seated)
– Did about 20 test and average lock time is 25 sec. Much better than ver 4.70
* Update 07 July - went on my first run today, couldn't get a HR lock after 2 min of waiting on the Run HR screen. A Quick reboot and 20sec HR lock.
5. Cadence lock
* Update 07 July - went on my first run today, no cadence lock detected.Although my HR and cadence values was not close. e.g HR 140 vs Cadence 167 spm. Maybe getting the values close would be a good test.
6. GPS Fix – within 5~10 Sec - same as always..pretty quick
7. Watch speed between menu – minimal improvement detected
8. Battery life – Not fully tested
* Update 07 July - At what percentage does the "Low Battery" alert get displayed?
9. Sync with phone – Working as it should…not fully test

5.04 Beta
http://www8.garmin.com/support/downl...s.jsp?id=10451

Changes made from version 5.03 to 5.04:
Several Connect IQ 1.3.0 improvements.
Known Issue: Some text on some Connect IQ watch faces may not display correctly.

5.03 Beta
Cant find the link to download.

Changes made from version 4.70 to 5.03:
Added Connect IQ 1.3.0 SDK support. See the Connect IQ 1.3.0 SDK for a list of new features.
Various bug fixes and stability improvements.

Things are looking positive!
  • Former Member
    0 Former Member over 8 years ago
    The Connect/GCM teams are still working on correcting the disconnects that are seen between daily and 7 day average RHR. Currently the the RHR values that are on the watch are not being displayed as expected in GC/GCM.

    We continue to provide updates to the teams based on the discussions that are going on regarding RHR in the forums. As always thank you for the discussion and feedback.
  • Former Member
    0 Former Member over 8 years ago
    Garmin seems to have recently changed the definition of RHR.


    Well that's one way to fix an issue.
  • 0 over 8 years ago
    Well that's one way to fix an issue.


    On a related note, they also changed the definition of "calorie".
  • 0 over 8 years ago
    Definitions?

    On a related note, they also changed the definition of "calorie".


    Huh, and I was going to say that they changed the definition of "Smart notifications." Or perhaps the definition of "Support."

    Still annoyed that my marshmallow nexus 7 disconnects in under an hour and I need to use an older, insecure, unupgraded device. Email support was a joke; after 4 back and forths I still didn't get the impression that anyone actually read what I wrote. Settings were right in that I could get gmail/hangouts notifications. But when the 235 is disconnected (I have the alert indicate when this happens), but the GCM still thinks it's connected it doesn't try to reconnect so there's no notifications.

    I'm really afraid to try a different firmware on my watch given what I've been reading behavior regressions.
  • 0 over 8 years ago
    Huh, and I was going to say that they changed the definition of "Smart notifications." Or perhaps the definition of "Support."

    Still annoyed that my marshmallow nexus 7 disconnects in under an hour and I need to use an older, insecure, unupgraded device. Email support was a joke; after 4 back and forths I still didn't get the impression that anyone actually read what I wrote. Settings were right in that I could get gmail/hangouts notifications. But when the 235 is disconnected (I have the alert indicate when this happens), but the GCM still thinks it's connected it doesn't try to reconnect so there's no notifications.

    I'm really afraid to try a different firmware on my watch given what I've been reading behavior regressions.


    Apologies if I'm stating the obvious, but given that Garmin support probably haven't mentioned it or even know about it, have you tried the bluetooth connection aid option buried right at the bottom of the settings page on the android version. I dont really know what it does, but it may help. My Z5 on latest android works fine.
  • Former Member
    0 Former Member over 8 years ago
    Fairly sure it's beta-related, but I used the "Hike" app to track a walk earlier today - when trying to save the activity, my watch rebooted. When it came back up, it had the activity paused but under "run".

    It synced the activity as a run but I could change it after to a walk. It kept the data from the activity and that synced, but when all was said and done none of the data stuck on the watch, or in connect - no steps, no HR, no extra calories burned from it.
  • 0 over 8 years ago
    Hummmmm.. The crash you describe in hike is back with 5.04 on the 235 :( I've only heard of it on the 235 in the past, and not on the 230 (I test with a 230).

    It's very likely an "out of memory" condition, as when the the "resume/save/discard" menu is display, the FW grabs a bunch of memory to do that. I'll see what I can do in the code....
  • Former Member
    0 Former Member over 8 years ago
    Links not working!

    Both the links are not working! I am not able to download the beta firmware.
  • Former Member
    0 Former Member over 8 years ago
    Both the links are not working! I am not able to download the beta firmware.


    Fixed!
  • 0 over 8 years ago
    bluetooth silent disconnection

    Apologies if I'm stating the obvious, but given that Garmin support probably haven't mentioned it or even know about it, have you tried the bluetooth connection aid option buried right at the bottom of the settings page on the android version. I dont really know what it does, but it may help. My Z5 on latest android works fine.


    I was pretty sure that I had tried that, but I wasn't 100% so I tried that this morning. Unfortunately same result. I even tried a full power cycle of my nexus 7 after enabling it. Within about an hour of the initial connection, I don't see/hear my watch give the alert that the phone is disconnected, and GCM on my N7 thinks the device is connected. However a sync initiated by my watch, or N7 will fail. Additionally, notifications don't show up.

    I find it ... unsatisfying that in the Device Sync Audit the failed attempts to sync don't actually show up. I tried 3 times, with 144 being the last entry. Turned off bluetooth, force killed GCM, turned on bluetooth and waited for reconnection. Notification on watch face then properly indicated 1 notification, and with the next sync attempt it incremented to 145.

    GCM 3.6.0.1 and firmware 4.60 on my FR235.