Beep sounds wrong

I get that this might be a pain to fix, and might not be worth it.

However, if time is taken for each Garmin device, to attempt to make the simulator emulate that device... then maybe someone wants to add BEEP TONE emulation to the implementaiton punch list.

For example, of the 18 different BEEP TONES, only a few that the simulator generates matches what the Edge 1030 device actually produces.
  • I just wrote a simple app that lets you step up through the tones. FR/Fenix (630, 935, F5+) devices all nearly identical. Edge devices nearly identical (520, 1030). But several differences between the watches and bike comps.

    The following ones aren't at all similar

    #4, 5, 12, 13, 17 - basic just beeps on the Edge devices, various more involved sounds on the watches

    4: ALERT_HI
    5: ALERT_LO
    12: TIME_ALERT
    13: DISTANCE_ALERT
    17: LOW_BATTERY
  • Thanks! That was an interesting experiment. It is good to know that within a device family there is consistency.

    Did you happen to run that same test in the simulator? Did the simulator generate tones that tracked with the watches? I was testing on the Edge devices and the sim does not.
  • All but the following are nearly identical between the F5+ and the simulator

    8, 10, 12,13: quite different
  • Awesome. So it sounds like if we stick to these Tones, they are essentially the same on the simulator, the Fenix watches, and the Edge cycling computers.
    1, 2, 3, 6, 7, 9, 11, 14, 15, 16, 18

    These tones are problematic in attempting to understand the user experience from the simulator or consistency from watch to Edge:
    4, 5, 8, 10, 12, 13, 17

    I got lucky and use 1, 2, 3, 9, 14, and 15 in my code! Thanks!!
  • I've added a project, ToneMaker, to my GITHUB CIQTest repository. Just a simple app that uses next/previous page to cycle through the tones.

    https://github.com/ekutter/CIQTest.git

    It should be public. Let me know if you have any issues accessing it.