Ticket Created
over 4 years ago

CIQQA-381

vivoactive 3 music - not able to get into menu2 settings

I made this question initially on the discussion forums, but since no one knew how to help there and the only suggestion was to open a bug report, I'm here creating this new thread about this.

In the past couple of weeks, I got the same question from more than one user that has a vivoactive 3 music: They can't get to the watch face customization menu. My watch face has the settings menu on the watch itself (Menu2) and not through the phone app, since it only supports models with SDK 3.2 and above anyway. No other user has issues using that Menu2 feature (some don't know how to find it, but it's easy to explain by sending them the link to the user manual). However, the VA3 Music users can't seem to find the menu even after going through the steps of the manual. They say that the default Gamin watch faces allow them to change settings on the watch, but not custom ones.

Can anyone confirm if Menu2 is indeed not supported on VA3 Music or if it's a bug? Not sure why it wouldn't be supported, since all other SDK 3.2 model does. I'm able to access the settings menu through the simulator, but according to them, this is not accessible on the actual watch.

They've sent me pictures showing the same thing: the different options between custom watch faces and the ones developed by Garmin.

Felipe
  • over 4 years ago in reply to flowstate

    I did set the minimum SDK on the Manifest to 3.2, so this should prevent the APAC users from seeing/downloading it, right? Thanks for the tip about how to check the CIQ version on the watch Thumbsup

    Meanwhile, I got an answer from the second user saying that they're in Brazil, so not APAC as well. I've asked them both to check the software version on the watch and will report back as soon as I hear back.

  • over 4 years ago in reply to Felipe

    " However, I didn't know about the different firmware versions for different part numbers, so thanks for clarifying that."

    Sorry, should have mentioned that. However, if you set the minimum SDK version to 3.2 in your project settings, that should prevent any firmware with < 3.2 from even downloading your app.

    "Is there any way that he could still be using the APAC firmware? How can he check that?"

    On my 935, if I open the menu (*), select Settings, Select About, and scroll down a few pages, I can see the CIQ version on one of the pages. I'm guessing the VA3M has a similar page.

    (*) On VA3/M, you open the menu by long-pressing the screen.

  • over 4 years ago in reply to Travis.ConnectIQ

    Hi , thanks once again for the quick reply. I did see that the VA3M seems to support the getSettingsView from SDK3.2 and also tested that on the simulator, so that's why I decided to add support to it on my watch face. However, I didn't know about the different firmware versions for different part numbers, so thanks for clarifying that.

    However, I got in touch with both users and one of them already replied saying that he is in the UK and bought the watch in the same country. Is there any way that he could still be using the APAC firmware? How can he check that? I'm also still waiting for confirmation from the other user about her country, will post back here once I have that.

    Looking at the first picture from my original post, can you confirm if that is indeed the correct place where the getSettingsView should be accessed by the user? That is the only mention to "watch face settings" on the user manual. 

  • over 4 years ago

    Former Member-

    The vivoactive3m does have 3.2 SDK support, and if you do a has check you will see that it does appear to have getSettingsView support.

    Is it possible that the affected users are using APAC (Asia/Pacific) version of the device? The APAC devices typically lag a bit when it comes to firmware. If you look at C:\Users\<UserName>\AppData\Roaming\Garmin\ConnectIQ\Devices\vivoactive3m\compiler.json you will see that there are two part numbers in there... one of them (the WW part) supports 3.2.0 and the other (the APAC part) supports 3.1.6.