Locus for Wear: "out of route" notification
Gathering feedback
Hello Locus Team,
How could we get out of route notifications on Wear?
Would it be possible to add this event to Locus Wear?If not it would help to add this event to Locus API, but I am not sure if I could establish a 2nd connection to android wear if locus maps does already communicate over bluetooth.
In the worst case I have to re-implement out of route notification based on current position and known track points.
I like this idea 
Normally android wear should vibrate on every smartphone notification. Would it be possible to add "vibrate" or "notification" to Locus Maps? Maybe it is enough to implement notification on Locus Maps because it gets automatically synchronized with android wear?
Normally android wear should vibrate on every smartphone notification. Would it be possible to add "vibrate" or "notification" to Locus Maps? Maybe it is enough to implement notification on Locus Maps because it gets automatically synchronized with android wear?
Hello,
thank for noticing this. It is true that these Locus notifications seem not to be propagated further to the Wear OS wearable. This could actually work independently from the add-on, I would have to look into it further to say how this could be implemented, cannot promise you anything at the moment though.
Best regards
Milan
Hello,
thank for noticing this. It is true that these Locus notifications seem not to be propagated further to the Wear OS wearable. This could actually work independently from the add-on, I would have to look into it further to say how this could be implemented, cannot promise you anything at the moment though.
Best regards
Milan
Thank you.
If you find a solution it would be nice if you could enable all notification settings to be compatible with android wear.
I did already check workarround like: create an app which does listen for sound or listen for vibration to translate them into app notifications. But you can't listen for vibration or sound on android framework. I guess the most easy solution would be "notification" as 3rd option in locus maps because "sound" and "vibration" are not send to wear.
A more advance solution would be sending custom events direct to locus wear instead of relying on android notification syncronisation.
Thank you.
If you find a solution it would be nice if you could enable all notification settings to be compatible with android wear.
I did already check workarround like: create an app which does listen for sound or listen for vibration to translate them into app notifications. But you can't listen for vibration or sound on android framework. I guess the most easy solution would be "notification" as 3rd option in locus maps because "sound" and "vibration" are not send to wear.
A more advance solution would be sending custom events direct to locus wear instead of relying on android notification syncronisation.
Thank you for the detailed description. You are right, triggering system notification, if that could be configured, would definitely solve it. That could also be interesting for navigation "commands" as this would also get synchronized to other wearables, not just Wear OS.
A custom solution would probably be also doable by targeting a remote intent to the connected node with the add-on.
Thanks, I will think about it.
Thank you for the detailed description. You are right, triggering system notification, if that could be configured, would definitely solve it. That could also be interesting for navigation "commands" as this would also get synchronized to other wearables, not just Wear OS.
A custom solution would probably be also doable by targeting a remote intent to the connected node with the add-on.
Thanks, I will think about it.
I guess this idea has very low priority. Would it make sense to rebuild this over api? Or is there an easy way to fire anything which could be processed by other apps to handle this idea over api? If broadcasts are more easy for you, I would like to listen to them.
Would be cool to get access to all notification-like locus events over api. I guess they are cheep enoght to fire them allways and we don't even need an UI to disable them.
I guess this idea has very low priority. Would it make sense to rebuild this over api? Or is there an easy way to fire anything which could be processed by other apps to handle this idea over api? If broadcasts are more easy for you, I would like to listen to them.
Would be cool to get access to all notification-like locus events over api. I guess they are cheep enoght to fire them allways and we don't even need an UI to disable them.
Hello Falco,
to be honest, Wear add-on really has kind of a low priority at the moment. I have sent link to this idea to Menion to consider but we will probably continue to keep all the Locus state information in the UpdateContainer to be read through periodic updates and then parsed meaningfully by the client application consuming the data.
Hello Falco,
to be honest, Wear add-on really has kind of a low priority at the moment. I have sent link to this idea to Menion to consider but we will probably continue to keep all the Locus state information in the UpdateContainer to be read through periodic updates and then parsed meaningfully by the client application consuming the data.
Are there any news on the discussed functionality to receive auto notifications / Vibrations on wear os app of Locus?
Are there any news on the discussed functionality to receive auto notifications / Vibrations on wear os app of Locus?
Replies have been locked on this page!