AsteroidOS/asteroid

Option to Vibrate multiple times on incoming calls

Closed this issue · 11 comments

Hi,
I have an LG Urbane (bass). Would really like to have multiple vibrations when there is an incoming call.
Thanks!

This could be nice :)
Maybe one could add a new notification type to AsteroidOSSync https://github.com/AsteroidOS/AsteroidOSSync/blob/8092ce6e93921ab911328f6c3425c655d4e5b353/app/src/main/java/org/asteroidos/sync/NotificationPreferences.java#L21
And asteroid-btsyncd https://github.com/AsteroidOS/asteroid-btsyncd/blob/master/notificationservice.cpp#L60
That would use the "ringtone" vibration pattern of ngfd-plugin-droid-vibrator https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-nemomobile/ngfd/ngfd-plugin-droid-vibrator/50-droid-vibrator.ini#L28

And then the user could select this vibration pattern for notifications coming from the phone app. We could also default standard phone apps to this

@FlorentRevest So this already implemented on the watch side? If yes I would look into it on the AsteroidOSSync side of things.

There should already be ngfd profiles for that.
However, this would need two more lines of code in asteroid-btsyncd's notification profile.

Based on this commit (AsteroidOS/asteroid-btsyncd@01146a0) I'm assuming that we don't need to check if the updated btsyncd is present on the watch e.g. via AsteroidOS version. Correct?

Correct

so does this mean its now been implemented in current build if I update my asteroidOS image on the watch?
Sorry Im new to github and these sort of things.. I dont know where to find any changelog for this product with versionnumbers either..

@GitJamz I don't think so, the merged PR was for the companion app. AsteroidOSSync now supports the rigtone pattern. I don't think it is already implemented in asteroidos. AsteroidOS has most of the required functionality already in there. If I recall correctly there are only one or two files that need to be adapted (e.g. pass the pattern correctly to the handler)

@jrtberlin So what you are saying is, no progress on this request. Correct? I mean for me as a end user this is not implemented and there is no need for me to update my image on the watch?

Maybe this is relevant for telescope @StefWe

Thank you @jrtberlin
Would be cool to have this in telescope. Sadly I don't have any free time at the moment.

Closing since the main feature is implemented on the watch side.
Tested working now again using the Android sync client.
Feel free to open new issues in the sync clients repos regarding usage of the feature.