In ambient mode, your screen is only updated once a minute or so. If you want to update it more frequently, this will be more complex and you will have to create some service, a "com.example.android.wearable.wear.alwayson.action.AMBIENT_UPDATE" intent and use StartServiceAtExact. I don't know exactly how this would work and this would require some advanced B4A stuff I imagine (probably also some changes in the manifest xml)
Here are some good reads I found but you will have to put the puzzle together yourself:
https://www.b4x.com/android/forum/threads/automatic-foreground-mode.90546
A Java example, here the most interesting part is the comments to find out what the culprits of doing such a thing as you want (like the restarting of the activity stuff looks interesting):
https://github.com/googlesamples/an...roid/wearable/wear/alwayson/MainActivity.java
From what I can get out of it, once an app goes in ambient mode, it can't wake up the processor so you must have a scheduled service that is called at a certain time, and when finished you will have to schedule the next update and so on.
There is probably a reason it isn't easy to do, as such apps can quickly drain the battery of your watch. In my golf app, I have to 'wake up' my watch (by wiggling my hand) to update the screen and see the latest GPS calculations.