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

vivoactive 4 Series (all versions) SW 4.70 is now live

This update can be downloaded with Garmin Express or automatically with Garmin Connect Mobile (pending rollout).

Change log:

  • Fixed an issue with debug logging
  • gone since update 4.70. For me sleep tracking and breath rate also stopped working :-(

  • I don't know why you have those problems. For me with 4.6 I had drain battery problems which are solved with that update. Also body battery and also pulse ox recording as usual! The 4.7 update worked fine for me..

  • So far so good...after my full reset yesterday, sleep tracking/stress tracking/body battery appears to be working well again. But this is just 24 hours. 

    One caveat: when I reset it somehow lost my step count up for that day (which is weird since it was synced on my phone...all the other data continued after the reset).

  • Former Member
    0 Former Member over 5 years ago in reply to Negated

    Well for me, it’s been 3 days since I upgraded to 4.70, and just like it happened on4.60, body battery no longer works. I’m definitely not gonna be resetting my watch every 3 days. At this point I might just have to downgrade back to 4.53 beta or just dump the watch. It no longer makes sense to be getting worthless firmware updates that address nothing but introduce new bugs, and even when we complain, garmin does nothing.

    im so sick of this.

  • Former Member
    0 Former Member over 5 years ago

    Hi, after this up date and the previous one, I have notice two problems:

    1. Dramatic battery draining. I only achieve 3 day with only two activities with GPS, with 100% pulse mesure and with oxy. Befere I achieve 5 or 6 days...
    2. Alarm message is not translate into Spanish. It is not a huge problem, but for your information.

    We have had since the launch of this VA4 problems with the battery. I can not understand how others models from the competitors can achieve much more battery life even with AMOLED display... It is very annoying to have this problem with a Garmin watch with this screen that we suppose that have a longer battery life... 

    Thank you very much for your support and to give to your clients a correct battery life.... Thanks

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    So, I get up and go for a quick 3km morning run. I live on the first floor in an apartment building, so naturally I climb down one flight of steps and waIt for GPS to register, Once that happens I get a notification that I’ve hit my stairs climb goal (7 flights daily). At the end of the run, I climb same flight up to my apartment and boom another notification that I’ve surpassed my daily goal 2x. I check and it says I’ve climbed up 14 flights of stairs and 0 flights down.

    Also, since 4.70 my v02 max has gone up 10 points; of course I wouldn’t mind that much progress, but the other flaws make it obvious that I can’t rely on any metrics or data from the watch. I dunno if the Garmin staff get to read this thread, but if they do..., you’re loosing a lot of customers, it’s like the firmwares released don’t address the vast complaints of users but instead, introduce new nightmarish bugs. I left Fitbit cos they refused to enable sp02 on the watches even thought the devices had the required hardware, coupled with the google buy-out a lot of ppl dumped Fitbit cos they never listened to their customers and had poor communication. I see the same thing happening here. I will not settle for factory resetting my watch every 3 days.

    I see no reason why a general release firmware will have this many bugs. Aren’t they being tested before release? Or are we the beta testers? I’m open to test firmwares, but let me know I’m dealing with a beta so what ever I experience, I know it’s beta. But this is tooooo bad guys, it’s really bad

  • Battery usage is 1%/h since update while it was 0.5% on. 4.60 firmware. Numerous restarts and power off/on did not help.

  • I've reviewed the language transalations v02.40 in the ./TEXT-directory and found numerous missing translations.

    Dutch language has the most 2056 translations using as it reference

    summary:

    brazillia: Missing ebbef246
    danish: Missing ebbef246
    finnish: Missing ebbef246, fb557388
    french: Missing ebbef246, 27afed22, 6bd8e38e, db84aa58, fb557388
    german: Missing d86bca8f, b2cf6cf9
    italian: Missing ebbef246, b5a8081b
    norwegia:Missing ebbef246, fb557388
    portugue: Missing ebbef246, 9038fec5, a8d85200
    spanish: Missing ebbef246, 94dd960a, 05c4ea4d
    swedish: Missing fb557388

    Missing transalations:

    ebbef246: Dutch "Auto Rust" isnt it the same as "Auto Pause" (708f6e9a Auto Pause) -> possible duplicate code?
    fb557388: Dutch "Overzicht" / "Overview"
    27afed22 Batterij te leeg om muziek te synchr. Sluit aan op oplader. / "Battery too low to sync music. Connect to charger."
    6bd8e38e Locatie ophalen / "Pickup location"/"Find location"?
    db84aa58 Tijd v houding /"Time for position"
    d86bca8f Voer maximale cadans in / "Enter maximum cadence"
    b2cf6cf9 Voer minimale cadans in / "Enter minimum cadence"
    b5a8081b Nauwk. hs-meting aan pols kan afwijken bij zwemmen. / "Accuracy to hr measurement on wrist may differ when swimming"
    9038fec5 Houd bvn knop ingedr v opsl activ of druk op ond knop v verw. / "Press top button for save or bottom button for delete"
    8d85200 P2 slagen / "P2 beat"
    94dd960a T 500M LR (datafield text)
    05c4ea4d Ren/Loop / "Run/Walk"

    [henning@satellite TEXT]$ ls -l
    totalt 600
    drwxrwxr-x 2 henning henning 4096 mai 27 08:27 backup
    -rwxr----- 1 henning henning 54212 mai 23 08:54 brazilia.ln4
    -rwxr----- 1 henning henning 50377 mai 23 10:39 danish.ln4
    -rwxr----- 1 henning henning 50990 mai 23 08:54 dutch.ln4
    -rwxr----- 1 henning henning 52215 mai 23 08:54 finnish.ln4
    -rwxr----- 1 henning henning 55724 mai 23 08:54 french.ln4
    -rwxr----- 1 henning henning 53251 mai 23 08:54 german.ln4
    drwxrwxr-x 2 henning henning 4096 mai 27 08:39 id
    -rwxr----- 1 henning henning 52393 mai 23 08:54 italian.ln4
    -rwxr----- 1 henning henning 51199 mai 23 11:33 norwegia.ln4
    -rwxr----- 1 henning henning 54672 mai 23 08:54 portugue.ln4
    -rwxr----- 1 henning henning 55109 mai 23 08:54 spanish.ln4
    -rwxr----- 1 henning henning 50597 mai 23 08:54 swedish.ln4

    [henning@satellite TEXT]$ wc -l *.ln4
    2055 brazilia.ln4
    2055 danish.ln4
    2056 dutch.ln4
    2054 finnish.ln4
    2051 french.ln4
    2054 german.ln4
    2054 italian.ln4
    2054 norwegia.ln4
    2053 portugue.ln4
    2053 spanish.ln4
    2055 swedish.ln4
    22594 totalt

    details: using diff tool

    [henning@satellite id]$ diff dutch-id.ln4 brazilia-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-18|v02.40
    132d131
    < ebbef246

    Missing ebbef246

    danish:

    [henning@satellite id]$ diff dutch-id.ln4 danish-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-00|v02.40
    132d131
    < ebbef246

    Missing ebbef246

    finnish:

    [henning@satellite id]$ diff dutch-id.ln4 finnish-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-02|v02.40
    132d131
    < ebbef246
    1752d1750
    < fb557388

    Missing ebbef246 and fb557388

    french:

    [henning@satellite id]$ diff dutch-id.ln4 french-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-03|v02.40
    132d131
    < ebbef246
    241d239
    < 27afed22
    330d327
    < 6bd8e38e
    1462d1458
    < db84aa58
    1752d1747
    < fb557388

    Missing ebbef246, 27afed22, 6bd8e38e, db84aa58, fb557388

    german:

    [henning@satellite id]$ diff dutch-id.ln4 german-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-04|v02.40
    950d949
    < d86bca8f
    956d954
    < b2cf6cf9

    Missing d86bca8f, b2cf6cf9

    italian:

    [henning@satellite id]$ diff dutch-id.ln4 italian-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-05|v02.40
    132d131
    < ebbef246
    2032d2030
    < b5a8081b

    Missing ebbef246, b5a8081b

    norwegia:

    [henning@satellite id]$ diff dutch-id.ln4 norwegia-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-06|v02.40
    132d131
    < ebbef246
    1752d1750
    < fb557388

    Missing ebbef246, fb557388

    portugue:

    [henning@satellite id]$ diff dutch-id.ln4 portugue-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-07|v02.40
    132d131
    < ebbef246
    1220d1218
    < 9038fec5
    1428d1425
    < a8d85200

    Missing: ebbef246, 9038fec5, a8d85200

    spanish:

    [henning@satellite id]$ diff dutch-id.ln4 spanish-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-08|v02.40
    132d131
    < ebbef246
    787d785
    < 94dd960a
    1539d1536
    < 05c4ea4d

    Missing ebbef246, 94dd960a, 05c4ea4d

    swedish:

    henning@satellite id]$ diff dutch-id.ln4 swedish-id.ln4
    1c1
    < 006-D7905-01|v02.40
    ---
    > 006-D7905-09|v02.40
    1752d1751
    < fb557388

    Missing: fb557388

  • Former Member
    0 Former Member over 5 years ago

    With this update i notice huge battery drain! I hope they fix it ASAP!!

  • Same happened to me: 90% Battery drain in 10h(overnight).

    And GPS fix takes much longer