AutoWear complication not working with Samsung Watch One UI 5

[Yoan]

Hi everyone,

I have a Galaxy Watch 5 Pro. I was using AutoWear to make a complication (text and icon) and was working fine.

My watch recently got updated with One UI 5. Since, the complication tasks is not working anymore. When the complication task is done in Tasker, it returns:

Funny thing, if I reboot my watch, the complication is actually updated with the new value.

How to fix the error and make the complication being updated (without rebooting the watch)? 

Thank you for your help :)

[João Dias]

If you open the main AutoWear app and try to edit AutoWear elements there, does it work?

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Yoan]

Thank you João for your answer.

In AutoWear app itself, I have 2 different behaviors:

1. If I update the complication setting and then validate, there is a "Please wait" during around 1min, then error (see screenshots).
    
   
2. If I select "Apply now", I get an OK message "Complication shown", however the complication is not updated.

Note that my watch is seen and selected in "Wear device" menu

Logs are available here

Hope you can find the issue

Thank you

[João Dias]

Thanks. Do other types of AutoWear elements (like screens for example) work normally?

[Yoan]

Screens and floating icon are working yes

[João Dias]

Ok, and what if you try different types of complications? Do none of those work?

[Tasker]

Correct. Same behaviour with all Complications.

But if I select another complication on the watchface, and select again my previous complication, the content is actually updated.

It looks like the complication is actually updated, but the display doesn't refresh. Is there kind of refresh command sent by AutoWear? It seems that this refresh is timing out.

[João Dias]

I do send out the request to refresh :( Seems like a bug on the device itself to me, sorry... It works well on all the devices I tested it on.

[Luke Lo Presti]

Also broken on Galaxy Watch 4 after today's One UI 5 update.

[Tasker]

I have the same complication problem with my GW5pro updated to OneUI5 / WearOS 4. Like i mentionned in comment in my post, it seems the watch lost the ADB wifi. The workaround for non-rooted phone (adb tcpip 5555) to do after each & every reboot to enable ADB wifi on the phone work too with the watch (just replace 5555 for 7272). But it just bother me now i have to do it on the watch & phone now lol 

[Tasker]

Thank you both for your feedback.

Can you please give more details of the workaround.

I have to do a "adb tcpip 5555" on my phone? 

What about the "adb tcpip 7272"? To do on the phone or the watch?

Thank you

[Jean Fellipe]

Hello.

It seems no one found the solution yet...

My temporary workaround it to use WatchMaker faces.

So I can set a variable in Tasker and load it in WM (just like a complication would).

[joaomgcd]

Ok, I was able to fix this, but because of the fix I had to change a bunch of stuff in the background that might have broken other stuff. If you want to give it a try you can install both APKs (on your phone and on your watch) and give it a go:

https://drive.google.com/file/d/1LPKGsu82B5jiVgG6ayy7bUfLQ4TuV3sr/view?usp=sharing
https://drive.google.com/file/d/0B8G77eDgeMdwYmN2czAtWjhFQ3c/view?usp=sharing

Let me know if it works if you're willing to try. :)

[Luke Lo Presti]

Thanks Joao.

Happy to give it a go.

I've was able to download the phone apk but the watch apk asks me to request access?

[Yoan]

Thanks you so much Joao, you're an amazing developper!

I will try it next week

[Google User]

I also have a galaxy watch 5 with One UI 5 and some problems.

Permissions for security settings are set via ADB.

But I can not turn the screen on (via input command e.g). And if I turn on/off the AOD the setting only take effect, when I manually wake up the screen.

Additional I am not able to turn my watch into vibrate only mode.

(this should be global security setting mode_ringer with string value 1).

I am glad to read, that there will be an update, but I am not able to download the app for the watch :(

would you be so kind and let me test this one too :))

thank u !!

[joaomgcd]

Sorry about that! I just gave you access :) Could you please try it now? Thank you!

[Eugen Schwanda]

Thank you so much for your respond and care of your tasker fans :)

i try to get the apk for my watch at
https://drive.google.com/file/d/0B8G77eDgeMdwYmN2czAtWjhFQ3c/view?usp=sharing
but still needs to be authorised.

The first link for the phone apk works normal.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/kdG4nUsGERM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/c26e95c4-43aa-4ac2-9c48-b995d7ef59d4n%40googlegroups.com.

[João Dias]

Sorry about that. Can you please try this link instead? 

https://drive.google.com/file/d/0B8G77eDgeMdwYmN2czAtWjhFQ3c/view?usp=sharing&resourcekey=0-dLHdgXsU5XbyDdazepn8pw

Thanks!

[Luke Lo Presti]

Thanks for the fix!

The AutoWear APKs seemed to have solved the issue. I am now able to update complication text via tasker. 

But there are a few issues with the "Text and Icon" complication.

1. The icon no longer shows on the complication

2. Tapping the complication no longer sends the command that is set

I tested a few other complications and they show as expected and send the command on tap, ex: "Single Colour Icon"

Let me know if there is any other info I can provide! Thanks!

[João Dias]

Thank you very much! :) Ok, I think I fixed those now!

Can you please try this version? https://drive.google.com/open?id=0B8G77eDgeMdwYmN2czAtWjhFQ3c&resourcekey=0-dLHdgXsU5XbyDdazepn8pw&usp=drive_fs

[Luke Lo Presti]

Thanks heaps Joao! Everything working as expected with that latest APK!

[Eugen Schwanda]

Hmm...

maybe I am doing something wrong.

1) I deinstalled autowear on my phone and on my watch.

then I restart both devices.

2) after that I downloaded the Device.apk from the first working Link

https://drive.google.com/file/d/1LPKGsu82B5jiVgG6ayy7bUfLQ4TuV3sr/view?usp=sharing

and installed it on the phone.

ALL possible permissions grand.

3) Then I downloaded the latest Watch.apk with my Laptop from

https://drive.google.com/open?id=0B8G77eDgeMdwYmN2czAtWjhFQ3c&resourcekey=0-dLHdgXsU5XbyDdazepn8pw&usp=drive_fs

4) After that I deactivated Bluetooth on my Galaxy Watch 5 (One  UI 5), and activate ADB Debugging via WiFi.

I ADB connect my watch with Laptop and successfully install the Watch.apk on my Watch using this command:

adb -e install path/to/Watch.apk

5) And after that I successfully use these both commands (without errors) on my Laptop

adb shell pm grant com.joaomgcd.autowear android.permission.WRITE_SECURE_SETTINGS

adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS

(I think autotool is not necessary, but I did it anyway...)

6) Now i reactivate Bluetooth and opened the fresh installed  AutoWear Watch.apk on my watch and allow ALL possible permissions.

7) Message told me to deactivate ADB Debugging via WiFi (leave only Bluetooth activated)

********

But still the same problems exist:

i can not use security settings to set my watch to "mode_ringer" value 1

i can not use input command to turn screen on.

changing AOD via autowear works fine, but the new toggled AOD setting only take effect when I manually turn on the screen.

:(

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/kdG4nUsGERM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/c3395076-9b26-45ce-9532-39b30aac6082n%40googlegroups.com.

[joaomgcd]

Thanks for the feedback! When you open the "AutoWear Settings" app on your watch, does it ask you to grant some permissions there?

[Eugen Schwanda]

I think at the very first app opening on the watch I was asked something for grant permissions... but I think this there was a short error and I did set permissions for writing secure settings via adb AFTER that.

anyway, I got some error now on my watch, which I should show the developer ;-)

maybe this helps?

********************

com.joaomgcd.autowear version 3.1.1

 Source com.google.android.packageinstaller

 OS Build TP1A.220624.014.G985FXXSIHWHI

 OS Code 33

 Device SM-G985F

 Manufacturer samsung

 Product y2seea

m6.f: The exception could not be delivered to the consumer because it has already canceled/disposed the flow or the exception has nowhere to go to begin with. Further reading: https://github.com/ReactiveX/RxJava/wiki/What's-different-in-2.0#error-handling | y5.a

 at a7.a.r(SourceFile:21)

 at q6.g.onSuccess(SourceFile:16)

 at io.reactivex.internal.operators.single.k$a.run(SourceFile:15)

 at i6.o$a.run(SourceFile:10)

 at w6.k.run(SourceFile:14)

 at w6.k.call(Unknown Source:0)

 at java.util.concurrent.FutureTask.run(FutureTask.java:264)

 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)

 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)

 at java.lang.Thread.run(Thread.java:1012)

Caused by: y5.a

 at com.joaomgcd.reactive.rx.util.DialogRx.W(Unknown Source:2)

 at com.joaomgcd.reactive.rx.util.DialogRx.V(SourceFile:7)

 at com.joaomgcd.reactive.rx.util.DialogRx.H0(SourceFile:7)

 at com.joaomgcd.reactive.rx.util.DialogRx.w(Unknown Source:0)

 at a6.c0.run(Unknown Source:4)

 at m5.j$b.e(Unknown Source:3)

 at m5.j$b.a(Unknown Source:0)

 at m5.l.onCancel(Unknown Source:2)

 at android.app.Dialog$ListenersHandler.handleMessage(Dialog.java:1913)

 at android.os.Handler.dispatchMessage(Handler.java:106)

 at android.os.Looper.loopOnce(Looper.java:226)

 at android.os.Looper.loop(Looper.java:313)

 at android.app.ActivityThread.main(ActivityThread.java:8762)

 at java.lang.reflect.Method.invoke(Native Method)

 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)

 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

********************

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/5860d737-be9c-448d-b8c4-23d4708fe7d0n%40googlegroups.com.

[Yoan]

I have installed the new version you provided. Complication is now working :D Thank you so much Joao! This is why we love Tasker

I will continue to test in the coming days and will let you know

[Jean Fellipe]

Hello. Complications are working again in my GW5pro updated.
Secure Settings are also fine, after the painful wifi adb with paring mode using a PC.

Issues found:

- Voice Screen (simply doesnt show);
- List Screen doesnt accept HTML and freezes after the timeout.

[Google User]

Great that it worked for some of you :-)
i am still with the same problems, but looking forward for an update
(no hurry - i will be happy whenever it will be... ^^).

[João Dias]

Hi everyone. Could you please try with the latest beta on Google Play and report back? :) Thanks in advance!

[Yoan]

Hi Joaomgcd.

I have the version 3.1.2 on my watch. Is that the latest beta version?

I currently don't have update available, not sure if it has been automatically updated from Play or not

[João Dias]

The latest version is 3.2.4-beta. Can you please check if there's an update on Google Play available now? :)

[Luke Lo Presti]

I've just downloaded the beta version on my phone 3.2.4-beta but the Google Play store on my watch only has 3.1.1 which has the original bug. Do I need to do something special to get the beta in my watch?

Google Play region is Australia if that matters?

[Yoan]

I have checked again, and I can see version 3.2.4-beta on my phone. I have installed the update

However on my watch I have only 3.1.1 proposed

[João Dias]

Ok, I figured out that the problem is that Google is not releasing the watch beta right due to some issues... 😭

Are you able to install the APKs directly from here?

[Luke Lo Presti]

Installed beta APK on my watch from the Reddit link. All working as expected. :)

[Yoan]

3.2.4-beta installed on my watch. Complication seems working fine. Will test in the coming days and give you feedback

Thanks again fro your amazing support

[joaomgcd]

Thank you very much for testing! Glad it's working well with the new APK!

[Chris G]

I've got a new pixel watch 2 and I used adb to install 3.2.7-beta on both my device and watch. I am able to change the global settings like ambient_tilt_to_wake (and see that tilt to wake toggles) but attempting to change mode_ringer & zen_mode_ringer_level does not toggle the watch silent/ringer modes.

I've read in previous posts/threads that occasionally the OEM of devices may not respect various settings changes, is this just the case where I'm SOL because google doesnt respect the value of those variables? Its so strange because when I manually toggle on the watch, I can see those two values change with adb shell settings list global but it seems like the watch doesnt respect if it changes from outside the toggle.

All I want to do is toggle watch sound notifications from a task.

Any advice?

[Yoan]

For me no issue to toggle sleep mode (global setting setting_bedime_mode_running_state) and theater mode (with Secure setting action).

Also (I don't know if it was already here before the beta version), I just figured out the new Tile feature. I love it, and works fine.

Complication (icon and text) also works fine. 
So no bug to report 👍 thanks again for your support Joao

[João Dias]

The way it works is, when you toggle the setting in the UI, that action will change the system setting in the background. When you use AutoWear to change the system setting in the background, nothing happens because the system is not actively listening to the change, so it doesn't do anything with it. The system is probably only "listening" to the tap on the UI element that toggles the setting. Makes sense? :)

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/7c0d5d03-ec64-4386-9683-0c4c721a89f4n%40googlegroups.com.

[João Dias]

It will, as soon as I can. Google isn't letting it go through though right now :(

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[YT]

Hi Joao, is there an activity intent that we can send via ADB Wifi that would force Autowear to refresh the complication on AOD? Some of my complications (long_text) work fine, but single_icon and small_image always have a long lag (up to 1min when AOD updates its own time) before updating the complication. Thanks!

On Tuesday, September 19, 2023 at 6:01:16 PM UTC+8 joaomgcd wrote:

I do send out the request to refresh :( Seems like a bug on the device itself to me, sorry... It works well on all the devices I tested it on.

[João Dias]

Not that I know of, sorry :( It's probably just the OS not allowing it to refresh that often.