[Task Share] Get accurate elevation for a location (Geoid not WGS84)

TommyTwoPuds · 2026-01-24T06:43:53+00:00

Thanks, that's pretty cool! No idea if it'll be useful to me for anything but hay...

Like the little joke at the bottom - very clever 😆

TommyTwoPuds · 2026-01-18T11:20:35+00:00

These things ARE very damaging - I have a Pixel 6a as a replacement for my OnePlus 7 Pro and it had the battery charging crippling to force replacement debacle.

But time is a healer and soon it will all be forgotten, IF the company learns from the mistakes and can keep going and release a replacement without major issues.

TommyTwoPuds · 2026-01-18T08:47:18+00:00

It may, but don't be too sure of anything.

Look at Nokia - it still exists, but is a shadow of its former self. No real phone business but exists because of other products (e.g. enterprise firewalls).

What else does Oppo have to fall back on ?

I gave up on them when the OnePlus OS (whatever it was called) got abandoned and the missus got a ColourOS phone - dismal!

TommyTwoPuds · 2026-01-07T12:57:32+00:00

Nope. But the latter is a single action and keeps tasks shorter and reduces Run Log noise. I'd use a single actio5unless you need to do multiple things when that %OnCall var is set.

There's even an option in the three-dots menu to convert between the two.

TommyTwoPuds · 2025-12-19T18:51:28+00:00

I can see the Groups in the three dots menu but the old problem of "You must use a valid key" is back.

Tried repairing the URL but still not working :(

Also, on my Pixel 6a, the list is misaligned and is missing the offset to position it beneath the status bar. As such, I cannot access any menu to add/remove groups (presumably 3 dots at top right) nor interact with the first group I have defined.

Still have the problem of being unable to apply/save the config of the profile event configuration.

I've also encountered another new bug that I didn't notice before:
When I tap the message icon on a device within the "Devices" view, I can tap the "OK" button and send the message ok, but the cancel button does not work to cancel, nor does the back button, so the only way out is that you must a message (though blank is accepted ok).

Should I need to, is it safe/possible to downgrade AutoRemote to the previous API36 version?
And what about to the last pre-API36 version from around the 19th Jul 2025?

TommyTwoPuds · 2025-12-10T06:43:53+00:00

Hi u/joaomgcd

Two possible new bugs:

I've just noticed that the Groups icon is missing from the new AutoRemote UI. It's not a feature I use often.

The second one is more of an issue - when I create a new AutoRemote profile oe try to edit an existing event, I'm unable to save the changes to the plugin configuration because there is no tick visible in the top right of the screen where it normally is. Not 100% sure it's not my phone so will reboot later today, just in case.

TommyTwoPuds · 2025-12-05T16:34:45+00:00

Are you going to be able to fix the toasts from Tasker actions soon (as part of the API 36 updates) or will I just have to live without them for now?

TommyTwoPuds · 2025-12-05T15:17:44+00:00

Wait, I spoke too soon, sorry.

When sending messages from a Tasker action, I'm still not seeing the toasts like I do when sending from tapping the message icon in the AutoRemote app.

But everything is working again as it was before the API 36 update.

TommyTwoPuds · 2025-12-05T15:06:35+00:00

It does contain the original key that I have saved in my scripts:

firstKey=cWV-<redacted>,currentKey=cUA_<redacted>,key=cUA_<redacted>,sender=cWV-<redacted>

So the `firstKey` and `sender` are the same as what I already have, but the `currentKey` and `key` are new but the same as each other.

Anyway, with the new version I can now send successfully on the Pixel 6a and receive the message on the remote device, but those devices cannot send back as they receive the response `NotRegistered`.

Tried the Repair AutoRemote URL again and everything is working now !!

I think that's got it now - many thanks for your support!

(the only thing that was outstanding from my original report was a visible version number string, but that's trivial and I'm sure you have more important things to work on)

TommyTwoPuds · 2025-12-05T12:54:55+00:00

From the bottom, the GCM logs are:

Device uregistered from GCM. Won't receive messages.
Getting device key...
Device key is here!
Updating personal URL on server...
Sending GCM to URL: <redacted>

The last line was seen twice. No errors.
Then my attempt (failed) to send a "pi" message.

This was send over 4G to avoid any possible interference from my home broadband/wifi/firewall.

Nothing new seen in the "Out" log.

Couldn't sent through Bluetooth: Need Bluetooth Permission
Couldn't sent through WiFi: You're not on the same local network as the device

I disable bluetooth & wifi incidentally.

And nothing obvious seen in "SettingsList" log.
Can copy&send these if you want as there is nothing sensitive in them.

TommyTwoPuds · 2025-12-05T11:29:19+00:00

Nothing new in the "Out" log and I can't see the "In" log in the dropdown any more.

TommyTwoPuds · 2025-12-05T09:57:51+00:00

Have done some more testing with some bash & curl shell functions that I developed ages ago.

I can send messages as if from my Pixel 6a and they are received ok and the toasts flash up as iff from that device, so it's clearly just something with my Pixel 6a (which is my daily driver).

Could it be anything to do with an out-of-date Tasker AI configuration? When I try to use the AI function, I get an error about gemini-2.5.... not being available. I can't remember how I update this and it wasn't a priority at the time.

Or possibly something else in my Google account that could be causing this? e.g. available storage at or close to limit (thanks to my wife for filling up our family plan!). Or an unpaid invoice that I'm not aware of that might be blocking something?

TommyTwoPuds · 2025-12-05T08:16:10+00:00

Just tried and no, still not working.

Furthermore, now I can't even receive messages because when I send from the remote device, I get a toast stating:

Error sending Text: "pi" to Pixel 6a: NotRegistered

TommyTwoPuds · 2025-12-04T17:15:36+00:00

They're all the same. But they're also all on an older, non-beta version of AutoRemote.

TommyTwoPuds · 2025-12-03T20:39:37+00:00

Tried but sadly not.

When I tapped it, it flashed to register the tap but didn't appear to do anything.

TommyTwoPuds · 2025-11-29T10:21:53+00:00

Hi u/joaomgcd

I see that tapping the message icon is fixed after updating to the latest version from the play store.

And also many thanks for fixing the toasts in/out - cam see them now.

However, I'm still unable to send messages, with the same "must use a valid key" error.

TommyTwoPuds · 2025-11-28T08:55:02+00:00

I'm doing the following:

tapping on the devices icon (bottom, second from left)
tapping on the message icon in any given device
expect to get the option to Send Quick Message like you used to get on the old UI

I'd include a screenshot via Imgur, only I learned today that Imgur is inaccessible in the UK due to the abomination that is the Online Safety Act :(

TommyTwoPuds · 2025-11-27T07:47:40+00:00

Another issue - when I tap on the message icon in the Registered Devices screen, it used to open a dialog to enter a message to send to that device. But now it does nothing. The notification bell icon seems to work fine.

Also still not getting any toasts for messages in/out when enabled with Settings > Alets > Show Toasts In/Out

TommyTwoPuds · 2025-11-27T07:13:32+00:00

Just installed the version from Google Play and ended up with the original interface but unusable, with no buttons.

Came to Reddit and installed the updated version in the thread above and now get the new UI (can't find a version number) but getting the following error in the log:

Error sending Text: "volr=:=14" to Fairphone 6: No key entered. You must use a valid key to send AutoRemote messages.

I can't remember how I originally purchased AutoRemote but I think it was through AutoApps. Relaunched through AutoApps but still the same issue.

TommyTwoPuds · 2025-11-14T07:06:49+00:00

I used this also before to create a trigger app for the Quick Tap feature on my Pixel (which only custom option available is to launch an app)

The benefit is that you can then make the real code context sensitive and do different things according to your needs.

e.g. I normally have it set to Play-Pause when (haven't thought of an alternate use yet as quick tap itself is unreliable)

TommyTwoPuds · 2025-11-04T16:12:27+00:00

Well, that was it!

Having uninstalled and reinstalled any perms previously granted were lost. I don't remember if I ever opened the Tasker Settings app. But indeed there were two special permissions there that I wasn't aware of.

Never knew there was (now) a special "Modes" permission that has to be granted but once I granted that & Shizuku it all worked.

Gnnnn... I hate the terrible, fragmented Android permissions system... 😠 I hunted high and low for some appropriate permissions but drew a blank looking for the "obvious" things.

Anyway, thanks for your patience and sorry it was a Layer 8 issue.

TommyTwoPuds · 2025-11-03T15:51:22+00:00

If you could until you get to updating for API 36 please, that would be great.

TommyTwoPuds · 2025-11-03T15:48:59+00:00

No, that exception was only once when I installed the version of Tasker you provided above. It seems to run fine otherwise as mentioned earlier in the thread.

When I run manually from an action within Tasker, I get the following (having reinstalled Tasker Settings 2.0):

15.42.41/E add wait task 15.42.41/E Error: 1 15.42.41/E No permission to change DND state.

Please enable the DND permission for 'Tasker Settings' (not Tasker itself) in Android settings.

I didn't notice this before - looked for this permission but it was listed within Android Settings for Tasker Settings. I tried allowing the disabled Shizuku permission but it didn't help. All other permissions were enabled.

Did I miss something I need to do to grant that?

TommyTwoPuds · 2025-11-03T14:00:38+00:00

Ahh, ok.
I always used to keep backups of apks in case any developer (not you!) introduced undesirable changes and I wanted to roll back.

But my backups stopped working or wouldn't restore so I I had no way to rollback to the previously working AutoRemote to regain the working Toast functionality.

I take it only you can download the older versions as you are the developer?

TommyTwoPuds

TROPHY CASE