• Replies 7 replies
  • Subscribers 18 subscribers
  • Views 1532 views
  • Users 0 members are here
Options
Related

Vibration patterns not working on ForeRunner 235

geniuswrist
Hi Guys,

I just got a 235 and I noticed that it does not execute the vive profiles correctly as stated in the documentation
I updated the device and it's running the latest firmware.

Module: Toybox::Attention
(Object) vibrate(vibe)
use the vibe motor
Parameters:
vibe (Array) — Array of VibeProfile objects to play in sequence. Maximum of 8 supported.

In vivoactive and fenix the vibe patterns I defined work correctly but in 235 doesnt matter what I send in the profile Array, I get only the same single vibe as result.
The same result should be expected on 230 and 630?

Am I missing something?

Cheers
  • Shannon - That's probably something to note in the doc, as right now, under VibeProfile, the only note for "Supported Devices" is "All non-Edge devices".
  • Thanks Shannon. I use vibrate on the 23x/630, but my patterns are all just the same level so I never noticed :)
  • Just to be sure about the particulars of the Toybox.Attention

    Shannon, when you say forerunner series it includes the 920XT?

    And another one. The new vivoactive HR has sound capabilities?

    Thanks Guys.
  • Hello,

    I´ve got some reviews to my app, saying that the watch is constantly vibrating.
    Today I received the information that it is related to Forerunners, only. That´s how i found this thread.
    So far, so good!

    The documentation has been updated to this:
    Note: Forerunner devices do not support vibration patterns. Vibration may still be used, but the vibration will always run at the same duty cycle.

    This is not really helpful to know how vibrating works without "patterns". Profiles as a parameter are mandatory.

    Does it mean, one profile is allright, sending several in a row might cause one of them to be the "last" with vibrating on?

    OK?
    var vibrateData = [new Att.VibeProfile( 50, 150 )];
    Att.vibrate(vibrateData);

    Not OK?
    var vibrateData = [new Att.VibeProfile( 50, 150 ),
    new Att.VibeProfile( 100, 200 ),
    new Att.VibeProfile( 50, 100 )];
  • The documentation probably needs to be worded a little differently, but I believe some devices essentially ignore the duty cycle value and will always vibrate at the same "frequency", but they will still respect the length parameter. You should still be able to send multiple profiles, like in your second example, but I think it will manifest as a single 4.5 second vibe instead of three distinct vibes since they're all going to be at the same duty cycle. That's basically what the docs mean when it states that vibration "patterns" don't work in some cases.