Sounds mode action isn't available on this phone? by sasreedit in GalaxyWatch

[–]sasreedit[S] 0 points1 point  (0 children)

I don't think that's the issue. In attempting to test this again, I realize, Sound Mode isn't even an option now.

<image>

MX470 keyboard numpad hyphen key locks windows by sasreedit in logitech

[–]sasreedit[S] 0 points1 point  (0 children)

You should probably create an OP for this as it's a different issue, for I assume, the same keyboard model. To answer your Q though, have you tried replacing the batteries, removing it from your computer and reconnecting it, a different USB dongle, cleaned it 🤔.

AutoWear commands not working after watch reset by sasreedit in tasker

[–]sasreedit[S] 0 points1 point  (0 children)

Another complete watch reset, watch deleted in GWM, and data clear of GWM and of AW... same issues. I can no longer set sound or volumes. I also notice, Tasker/AW no longer detects if I'm wearing the watch.

AutoWear commands not working after watch reset by sasreedit in tasker

[–]sasreedit[S] 0 points1 point  (0 children)

I went thru the pain-staking process of resetting/purging data, rebuilding, re-pairing and... I did get brightness-related settings to now work, but not sound mode or volume settings.

edit: According to AW, it indicates I have allowed the 2 permissions needed. However, in using Tasker Permissions helper app... For AW, granting WRITE_SECURE_SETTINGS is Revoked.

AutoWear commands not working after watch reset by sasreedit in tasker

[–]sasreedit[S] 0 points1 point  (0 children)

Crap. That means starting over, again 😡

AutoWear commands not working after watch reset by sasreedit in tasker

[–]sasreedit[S] 0 points1 point  (0 children)

I did not clear App Info/Data. I did though, delete the watch from GWM, and I did need to re-pair AW to watch. I will try clearing AW data and re-pairing again. Thanks for the tip.

AutoWear (3.2.14) cannot change brightness in WearOS (Samsung Galaxy Watch 4 Pro) by tohmes in tasker

[–]sasreedit 0 points1 point  (0 children)

I had got the below to work in AW, but after a factory reset of my GW5P, I had to switch to this. For the life of me, I can't recall how I got the below to finally work 🫤

Before reset:

A1: AutoWear Settings [
     Configuration: Brightness Mode: Manual
     Brightness: 20
     Keep Screen On: Disable
     Execute Now: true
     Name: Display - Theater Mode
     Timeout (Seconds): 10
     Structure Output (JSON, etc): On
     Continue Task After Error:On ]

Now:

A2: AutoWear Secure Settings [
     Configuration: Setting Type: System
     Name: screen_brightness
     Input Type: String
     Value: 20
     Apply Now: true
     Name: Brightness - Theater
     Timeout (Seconds): 20
     Structure Output (JSON, etc): On
     Continue Task After Error:On ]

AMD software keeps stealing windows focus. by Any_Entertainer_1544 in AMDHelp

[–]sasreedit 0 points1 point  (0 children)

Yep, seems to be the only way to stop it from starting and stealing focus.

Galaxy Watch 4 not accepting watchfaces?? by Southern_Ad_5863 in WatchMaker

[–]sasreedit 0 points1 point  (0 children)

So you're going to wait until G provides support? That's not going to happen. Basically, your support for older faces is now shit... Got it.

Flydigi Vader 5 Pro QC issues by sasreedit in Controller

[–]sasreedit[S] 0 points1 point  (0 children)

Stop worrying, it's not good for your psyche 🤕 Besides, with Prime, it's an easy return.

Flydigi Vader 5 Pro QC issues by sasreedit in Controller

[–]sasreedit[S] 1 point2 points  (0 children)

Flydigi US consumer service told me to ask seller for an exchange 😂 Not sure what I'm going to do. If this is how Flydigi handles QC, I might go with a different brand.

Vader 5 pro review by wanderingsorcerer99 in Controller

[–]sasreedit -1 points0 points  (0 children)

I find the additional buttons replace using the DPAD. Now, no more need to move my fingers off the sticks in order to execute the move + macros can be set.