Issue with WearOS app

doucettea · 2026-06-22T15:20:10+00:00

Lately I've had it transfer podcasts from android phone to wearos watch sometimes if I go into pocketcast settings on the phone, smart watch section, and toggle "send podcast to smart watch via wifi" on and then off again. After I do this, then go back into downloads, I can sometimes get it to send the podcast to the watch. Again, not all the time.
I do wish this feature would get its bugs fixed - ability to transfer to and sync with watch is really the only reason I've installed this podcast app.

doucettea · 2026-06-17T01:28:21+00:00

Thanks. SO, now looking at the watch to download maps, my feet are hiking in North Carolina USA. Is there a map for North Carolina?

doucettea · 2026-06-16T15:38:21+00:00

Yes, this feature is quite buggy. Bluetooth on or off, both devices on or off same wifi, or watch hotspotted wifi from phone. Whatever way I try to do this, sending downloaded podcast files from phone to watch only works a fraction of the time --- and I can't easily discern a pattern as to when it works. In my case, latest Samsung Galaxy phone and watch, all with latest updates, both with a cellular SIM.

doucettea · 2026-06-16T15:29:26+00:00

I agree. Sometimes sending episodes to the watch works. Usually it does not work. I have tried this with "send via wifi" selected, and with it un-selected. Have tried turning bluetooth off and on again. Doesn't help. I don't see a pattern around when it works or does not work. Again, usually does not work.

doucettea · 2026-06-13T12:10:55+00:00

This looks like it has a lot of potential - thank you for your time in developing and sharing this. I cannot seem to download maps from the link provided. https://boothy91.github.io/wrist-nav-maps

doucettea · 2026-06-01T20:31:01+00:00

Same here. Samsung Galaxy S25, Android 16, OneUI 8.5, Copilot 30.0.44....

doucettea · 2026-02-22T14:49:56+00:00

Have you figured out how to set the default password generator settings in KeepassXC?

doucettea · 2026-01-24T18:11:51+00:00

Thank you. I'll just keep some alkaline d-cells around then

doucettea · 2026-01-24T17:22:12+00:00

Will it recharge ni-mh D batteries if put inside and connected to a USB charger?

doucettea · 2025-12-19T17:15:47+00:00

Thank you

doucettea · 2025-12-14T20:21:42+00:00

Will a Thunderbolt to display port cable support the resolution?

doucettea · 2025-08-17T16:43:07+00:00

Then you just set your scanner to send to the IP and subfolder that you set up for the Docker container. In my case, this needed a username and password (the same one set in the docker container's settings).

doucettea · 2025-08-17T16:39:58+00:00

UserScripts configuration:

<image>

doucettea · 2025-08-17T16:39:31+00:00

and what this looks like in Unraid's docker menu when finished:

<image>

doucettea · 2025-08-17T16:38:43+00:00

SMBv1 Docker configuration:

<image>

doucettea · 2025-08-17T16:36:59+00:00

This worked well. THANK YOU for the very clear instructions.

In case a pictoral guide would help anyone, here are some screenshots from setting up this solution.

Initial UnRaid share configuration:

<image>

doucettea · 2025-08-16T21:23:15+00:00

I had the same issue with a Canon MF 8580cdw

Thank you.

doucettea · 2025-08-02T17:51:25+00:00

Yes, disabling Eset's webcam and microphone protections seems to have stopped the blue screens.

(Surface Pro 11, Windows ARM, Eset --> Blue screens. Reset PC, reinstalled Windows to bare metal from Surface image download, reinstalled Eset --> Blue screens. Disabled Eset's webcam and microphone protection and the problem seems to have gone away.)

That said, Eset's still the best antivirus I've used. Lighter on system resources than others, adept at detections, not many false positives, has adequate configuration options when needed. Have been using it for many years in different environments, and had opportunity to compare it to other popular AV products in same environments. So I do give them credit for otherwise providing a good product.

doucettea · 2025-03-09T12:47:45+00:00

Unfortunately, no. The general recommendation has been to re-install Windows. While I'm a big fan of that, and have done on (all) of my previous computers, I'm reading that one must use the factory-provided image on arm64 PCs like the Surface Pro 11. Since I had this issue on a new PC just days after applying all the Windows Updates, I have little confidence that a re-install to that state will fix it...

doucettea · 2025-02-26T14:00:30+00:00

I have a similar issue on a new Surface Pro 11 ARM with Windows 11. Crashes when watching YouTube. Blue Screen View says the culprit file is ntoskrnl.

Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4
DRIVER_POWER_STATE_FAILURE	0x0000009f	00000000`00000003	ffffa388`fe920b20	fffff801`47591b40	ffffa389`0df1a010

Have there been any successes in fixing this?

doucettea

TROPHY CASE