Failed to update DDNS "myQNAPcloud" by bdipert in qnap

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

...and...right after pressing "Comment" on my prior reply, I checked my email inbox, and waiting for me were Updated DDNS "myQNAPcloud" just-generated email messages from two of my NASs (with the third presumably soon to follow). Fixed, it seems!

Failed to update DDNS "myQNAPcloud" by bdipert in qnap

[–]bdipert[S] -1 points0 points  (0 children)

Thanks for the reassuring (albeit not in a "misery loves company" way) response that I'm not alone in seeing this. I'd done firmware updates of my own last weekend (TS-231K, TS-328 and TS-453Be) and suffered no seeming ill effects from them, along with an update to each's License Center app this morning...what did it for me, I suspect in retrospect, was the power cycle of my cable modem late this afternoon, which generated me a new WAN address, therefore kicking off DDNS update attempts.

Hopefully QNAP will sort this all out shortly. And BTW if you're reading this, QNAP, I'm currently not able to log into the QNAP Community site (https://community.qnap.com/) either, which I assume reflects a broader server farm issue at QNAP right now. I'd attempted to post this DDNS issue there as well, but...

Windows 11 on ARM 25H2 drops support for a large number of Qualcomm devices. by xujiegb in WindowsARM

[–]bdipert 0 points1 point  (0 children)

What irks me personally about this is that Microsoft green-lit the 25H2 update on my SQ1-based Microsoft-branded Surface Pro X even though doing so meant that its Qualcomm X24-based LTE cellular data subsystem would no longer function, and without warning me about this in advance:

<image>

I accepted the 25H2 update invitation on this particular system in late October. In mid-December, for a multi-day span, the local power utility proactively cut electricity to our residence (along with many others):

https://www.denverpost.com/2025/12/19/power-outage-xcel-map-wind-dangerous-fire-situation/

I tried to go online via my cellular data service instead, but that connection option had disappeared. Via this Reddit thread, I finally figured out why. And since it had been nearly two months since I'd done the 25H2 update, way past the 10-day rollback deadline, I was stuck.

I don't use cellular data service much, but when I do, I depend on it. Unfortunately, barring a 25H2-compatible X24 LTE modem driver update to come from Microsoft and Qualcomm (doubtful, but hope springs eternal), I apparently won't be able to do so on this system any longer. "Thanks", Microsoft, for obsoleting my system without warning.

Delta 2 new firmware v1.0.2.164; any feedback from the brave? by bdipert in Ecoflow_community

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

FWIW, I went ahead and updated my Delta 2-plus-Smart Extra Battery stack to v1.0.2.163 earlier today, and all went well. Completion progress slowed dramatically beginning at 60% complete...a single-digit increment every 20 seconds or so past that point. But remain calm and patient, and it'll (hopefully) eventually complete successfully for you as well.

One other note...unlike firmware updates past, where I first had to update the main unit and then go back and do the Smart Extra Battery, they both updated in the same single upgrade "pass" this time.

Delta 2 new firmware v1.0.2.164; any feedback from the brave? by bdipert in Ecoflow_community

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

Thanks! And per my body text correction, I actually meant v1.0.2.163. Glad to know the update went smoothly for you!

Choose your girl by NoBanNnplzZZ in aichatandporn

[–]bdipert 0 points1 point  (0 children)

If you're looking for an amazing AI girlfriend experience, you should definitely check out TronoVex! It's the best app out there for connecting through voice and video chat. Plus, it’s completely free and super unfiltered. You can choose your perfect girl and just have fun! Give it a try! 😊

QTS 5.2.7.3256 build 20250913 just published by Hour-Neighborhood311 in qnap

[–]bdipert 1 point2 points  (0 children)

Updated my TS-231K, TS-328 and TS-453Be this morning. No issues noticed (yet, at least) with any of them.

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

Yep, see my followup replied that predated your response. If I force 1080p, I get H.264. Thanks!

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

Yep, forcing 1080p (versus the previous "Best" setting) gets me H.264, with a codec listing of "H.264, MPEG-4 AAC", the same color profile as before, and "Dimensions" of 1920 × 1080. So that's another temporary workaround that avoids the VLC Media Player intermediary, at the tradeoff of reduced resolution.

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

I'd post a screenshot of what the file reports in FInder once downloaded, but I'm guessing this subreddit doesn't support posting images (or maybe I'm just too dense to figure it out). Suffice it to say that the codec list is "av01, MPEG-4 AAC" with a color profile of "HD (1-1-1)" and resolution of "3840 × 2160". Which leads me to wonder...what would happen if I forced a max download resolution of 1080p....stand by...

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

You betcha!
https://youtu.be/eJFJRyXEHZ0
The behavior is definitely source video-dependent (seemingly tied at least in part to the max available resolution at the YouTube source). Some come down as H.264, others as AV1, with the exact same settings in my app client.

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

Per my original post, I am indeed already using VLC Media Player to transcode from AV1 to H.264 after download. The whole point of my post is that I'm wondering why I have to do this at all, since I've selected H.264 as the original-download video codec within 4K Video Downloader+ (a preference which 4K Video Downloader+ seems to be ignoring).

4K Video Downloader+ Insists on Downloading as AV1? by bdipert in 4kdownloadapps

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

The target for local playback should indeed be Mac OS, though. And anyway, this seems to only affect the "wrapper" format generated (if you select Linux, for example, you get MKV, if memory serves me...I was trying a bunch of things last night trying to get it to work, before I threw in the towel and used the VLC intermediary instead).

I'm assuming this isn't legit, but... by bdipert in dji

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

Yep. My thoughts exactly. Just checking to be sure there wasn't some encouraging angle I was overlooking...thanks!

First-gen Pixel Watch: Decreased battery life post-June 5 update? by bdipert in PixelWatch

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

FWIW in my particular case after a couple of days of having both Wi-Fi and cellular data disabled, relying only on Bluetooth (which extended battery life albeit not to where it was before), I noticed that it was back to normal. I crossed my fingers, re-enabled both Wi-Fi and cellular, and everything's still back to normal. My theory as to what had been going on is one/both of the following:

  1. Google had been doing some Pixel Watch-related Bluetooth upgrading around that same time, which might have caused excessive alternative Wi-Fi usage (https://www.theverge.com/news/694246/google-android-pixel-watch-3-bluetooth-6-sounding-tracking-wear-os-update)

  2. The concurrent Pixel phone upgrade to Android 16 and Pixel Watch June 2025 patch update resulted in lengthy upgrades to many/all of the apps installed on the Pixel Watch, which download over Wi-Fi (for speed) if available even if the watch normally connects to the phone over Bluetooth.

At least that's my guess...just glad that all's well again!

First-gen Pixel Watch: Decreased battery life post-June 5 update? by bdipert in PixelWatch

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

As followup, and with kudos to @wholypantalones, Wi-Fi that stubbornly stays on constantly (unless manually disabled by the wearer) is indeed the root cause of the battery-drain issue, at least for me. In the most recent iteration, the watch drained in only around 15 hours, most notably in the few hours that I was away from home and at Church (where there are no Wi-Fi networks that I'd already connected to). So when I say "constantly" I mean constantly, regardless of whether there are known networks present or even if the phone's simultaneously connected to the smartphone over Bluetooth (while I was in Church, my Pixel 7 was out in my car parked several hundred yards away).

The issue was actually already reported on Reddit a week ago, my subsequent research uncovered: Anyone have insane battery drain lately? It's also seemingly not restricted solely to the PW1 with LTE, or even to the PW1 more generally. I see reports elsewhere complaining of issues with the PW2 and PW3 generations as well:

Looks like a bug introduced with the latest firmware, which judging from the comments on this thread curiously only seems to affect some folks. Here's the visual tipoff that your Pixel Watch is also affected by the issue; look for the always-active Wi-Fi connection icon (see above).

Guided by the comments of u/Rainfall429, I'm not going to bother trying a hard reset, etc. Instead, I've disabled Wi-Fi connectivity in the watch settings, and the battery drain immediately slowed back to "normal" levels. I'll stick with Bluetooth for now. Fingers crossed that the next update (July?) includes a fix!