Transcript (auto-generated, may contain errors). Hosts are AI-generated. Stories curated by Synaptic Plunge.

Quick note before we start, we're AI-generated hosts, and today's stories were curated by the Synaptic Plunge team. Welcome to the Daily Plunge. What should you update or check today? It's a great question, and we actually have a lot to cover. We really do. I mean, just imagine your PC is quietly shredding its own hard drive, right? Like, riding up to 13 terabytes of junk data a month, all while you're just staring at an idle desktop.

Yeah, that is, well, it's the ultimate digital silent killer. And it's just one of the things we need to audit, today. Exactly. So today, we're gonna find out if your computer is one of them. We're doing a full digital triage for this deep dive.

I like that word, triage. All right, our mission is to basically sort through your devices and figure out what needs your immediate attention and what can absolutely wait. Makes sense.

So we have five specific targets today. For Pixel owners, a massive Android update just arrived a whole month early. Out of nowhere really. Yeah. Then for the Samsung crowd, we need to talk about the Android 17 One UI 9 rollout. Which is pretty messy frankly. Very messy. Then for PC users, we are digging into that runaway

Radeon driver bug I just mentioned that's well chewing through SSDs. That one is urgent. For sure. Fourth, for Apple users, there is a fundamental privacy change coming to public iCloud links. And finally for the desktop creators out there, Blender 5.3 just made 3D scanning native. It's a dense list, I know. But the overarching theme here is really just routine maintenance.

Right. Like we have a few action items but nothing that should cause widespread panic. We are just doing a little digital housekeeping today. Just a little sweep up. So let's jump right into the phone updates. Starting with the clean, straight shot, Google's pixel lineup.

All it updates? Usually, yeah. If you are rocking a Pixel 6a through the 11 or the Fold or the tablet, this applies directly to you. Android 17 QPR 2 dropped stable on November 10th, and it was bundled right into the November Pixel drop. Which honestly caught a lot of developers off guard. Oh really?

Oh yeah. I mean, the QPRs, the quarterly platform releases, they are usually pretty rigid in their timing, you know? QPR 2 was universally expected in December. Oh, gotcha. So pushing it out in early November means Google, they accelerated their testing pipeline significantly. Well the feature everyone is posting screenshots of is the new

custom system colors. You finally get a full rainbow hue slider. Yeah, people love the customization. They really do. And you can apply these four intensity styles now. So there's neutral, soft, bright and bold. Right. And it fundamentally changes the dynamic theming engine. How so?

Well, previously Android just extrapolated a very limited palette from your wallpaper. Right? Right. Now the OS is doing real-time color math. It shifts those custom hues seamlessly between light and dark modes You know depending on the time of day. That's super cool But I am gonna push back on the hype a little bit here. Fair enough. The colors are great I can't eat. I mean I love them, but the real story the reason you actually need to install this update today is the security patch Oh, absolutely

We are talking about 232 Android vulnerabilities across two patch levels plus 166 pixel specific fixes. You are absolutely right to highlight that patch volume of that size Usually indicates they've closed a significant framework loophole like a structural thing exactly when you see hundreds of vulnerabilities patched Simultaneously it often means a core library like something that handles memory management or media processing had a fundamental flaw Wow Yeah, a flaw if it cascaded into dozens of smaller exploits, so closing those doors is critical.

Makes total sense. It also squashes some annoying daily bugs, like that scroll stutter and background battery drain people were seeing on the Pixel 11. Finally. Right. But there is a new feature that genuinely changes how we use Bluetooth. It's called AuraCast Voice Broadcast.

This is a major leap forward for localized audio. I'm so glad they included this. Let me make sure I understand the mechanics of this though because it sounds almost too simple. Go for it. Say I'm running a small community event in a room with terrible acoustics. Sure. Instead of shouting, I toggle ORACAST in my quick settings through a QR code on the

projector and people just scan it to hear my microphone feed through their own earbuds. That is exactly how it works. That's wild. Under the hood, ORACAST utilizes Bluetooth low-energy audio, but it breaks the traditional Bluetooth rule. Which is the pairing thing? Right. Normally Bluetooth requires a one-to-one paired handshake. ORACAST turns your phone into an FM radio station. Oh, I like that analogy.

Yeah, it doesn't care how many people are listening, it just broadcasts the audio packets outward in a localized bubble. So anyone can just tune in. Exactly. As long as the receiving device, whether that's high-end earbuds or a modern hearing aid, which is huge for accessibility, understands the protocol, rounds It just tunes into the frequency. You know, the producers behind the glass at the Synaptic Plunge team

were actually just talking about this in our prep meeting. Oh, yeah. Yeah, they produce a lot of YouTube channels, and they were thinking ORACAST could be an incredible way to share a live voice track with a crew in a room during production. That's a brilliant use case.

Right. The only bottleneck they noted is that everyone needs compatible LE audio gear, which is, you know, still catching on. True, but it will be ubiquitous soon enough. Now, looking at the sentiment online, the tech press is thrilled. But actual users are dealing with the reality of Google's stage rollouts, which are always painful

Oh totally over on X Android central was hyping the rollout on November 11th But the replies are just a wall of impatience You have users like Joseph Spurner asking if literally anyone has actually received it yet I even saw some friction in the custom ROM community to unsurprising Yeah, the folks over at Graphene OS posted that the update is is indefinitely delayed for their users

because Google hasn't pushed the open source code for QPR2, as promised. Stage rollouts always breed frustration. And we are seeing a few scattered reports of UI lag returning with users like Mellaburn21 complaining that the choppy experience

from the early Android 17 days is back. But overall, I mean, it's a staple release. OK, so to answer our title question for this segment, this is a definitive update answer. If you have a Pixel, dig into your settings and check for Android 17 QPR2 today. The interface colors are fun, but patching 232 vulnerabilities is why you actually hit

download. Let's widen the lens a bit though. If Pixel is the clean, straight shot, the Samsung ecosystem is a sprawling metropolis. That is a very polite way of saying it's everywhere. Exactly. For anyone running a Samsung Galaxy phone or tablet, Android 17 is wrapped inside

One UI 9 and this rollout is wildly fragmented It really is it started hitting the Galaxy S26 series back in September and it is just slowly making its way down to the S23 family the fold the flips and even budget devices like the a34 Well, the fragmentation happens because Samsung isn't just updating an OS, you know They're reading it with carrier requirements regional regulations and hardware specific features like galaxy AI It's a lot of moving parts. It is. A great heuristic for navigating One UI 9

comes from the tech community actually. If you see a new feature nested under the Google tab in your settings, it's core Android 17. Okay. If it requires a Samsung account to function, that's Samsung leveraging their proprietary ecosystem. The feature I really want to focus on here is the blue dot location indicator. No, that's a good one. Right., you're just swiping through your phone and suddenly a little blue dot appears at the very top of your

screen. That means an app is actively pulling your GPS coordinates at that exact millisecond. It takes the abstraction out of background processing. You can see it happening. Can I kill the apps access right there on the spot? Or is this just like a friendly FYI from Samsung?

Oh, you can absolutely act on it. Nice. Tapping the notification,- acts as a deep link directly into that app's permission manager. So no digging through, settings menus., kind of actionable transparency really appreciate that direction

they've also integrated deep system alerts that will physically block unknown malicious at the一下 from launching until you explicitly bypass the warning or delete the application

I love that one of the for Galaxy owners. This is an update but maybe- wait answer. I agree one UI 9 is fantastic actionable privacy tools but giving it a day or two for the early adopters to report any system breaking bugs on your specific carrier model is a very smart move. Definitely. Alright let's transition from, phone software to a

literal hardware emergency. Yeah this one is rough. If you are on a Windows PC running an AMD Radeon graphics card. Pay close attention. This is not a phone story. Right. We are talking about the AMD External Events utility. The process name you'll see in Windows is ATIECLX.exe. Catchy. Very. It installs silently alongside your Radeon graphics drivers. And

its primary job is supposed to be listening for hotkeys and managing display detection when you plug in a new monitor. But it has gone rogue. Totally rogue. AMD has confirmed a bug where this utility gets stuck in a loop and continuously writes data to the SSD even when the PC is completely idle.

And we are seeing reports of it writing anywhere from 0.3 to 1.5 megabytes per second with spikes up to 5 megabytes a second. Which sounds small but over time? The math on that is alarming. If a background process is writing 5 megabytes a second constantly, that translates to roughly 432 gigabytes of writes per day.

Good grief. Over a month, you are looking at nearly 13 terabytes of useless data being churned through your solid state drive. I really want to clarify the stakes here. I've seen people compare this to a dripping tap under a sink.

But I think a better analogy is leaving your car idling in the driveway with a brick resting on the gas pedal. Ouch. Yeah, that's accurate. Sure, modern SSDs are incredibly resilient, but they still have a finite lifespan measured in TBW terabytes written.

You are burning through your hardier's mileage for absolutely zero reason. The runaway logging loop is what's causing it. The utility is generating error or debug. Logs faster than the system can parse them Right. And you're right about the TBW limits.

Modern drives use wear leveling algorithms to distribute rights evenly across the memory cells. So, you know, this bug won't kill a brand new drive in a week. Okay, but it's somewhat comforting. But if you have an older drive or a smaller capacity drive where the wear, where the wear leveling has less surface area to work with.

13 terabytes a month is a significant degradation of your hardware's lifespan. So how do we check for the brick on the gas pedal? It takes less than 30 seconds. Hit the Windows key and R, type Resmon to open the resource monitor, click on the disk tab and look at the processes with disk activity list. And what am I looking for? If that ATIE CLXX process is sitting at the top,

turning away at your drive while you aren't doing anything, you have the bug. You know, for our Synaptic Plunge team who are constantly rendering out massive video files and generating AI music tracks through Suno, their main drives are already taking a beating. Exactly. They can't afford this bug. Right. Running this quick 30-second check is just cheap insurance against premature dry failure. The tech community on X is definitely treating it as a priority audit.

user Mike Taps admitted he thought the whole thing was overblown until he actually measured his own rig and found the process going crazy. See. And Chad W. Tech and Zack Schutt were both urging folks to just run the 32nd check. That is exactly why we verify. I saw a great point from a developer on X2, harmzog5.

What did they say? They said that if a software's logging function can literally wear out physical hardware it needs to be an opt-in toggle with a built-in bite counter. I completely agree. It's a fundamental failure of software design. AMD has acknowledged the issue, thankfully, and States of Fix is coming in the adrenaline 26.11.1 driver update later this month. So answering our title question for this one, this is a mandatory check answer. Go check it right now.

If you have a Radeon card, open resource monitor today. If the utility is writing, don't go blindly deleting system files or tweaking your registry, just monitor it and install that adrenaline update the second it drops. That's the best advice. It is fascinating though. We spend all this time worrying about a software bug

wearing out our physical hard drives, but Apple users are currently facing a completely different kind of storage anxiety. Oh, this is a big one. Yeah, what happens to your data after it leaves your local drive and hits the cloud?

This is a major philosophical shift for Apple's ecosystem. Okay. And it centers entirely around how iCloud sharing operates. Let's define the current we talk about the change just to be clear. Good idea. Right now you have two ways to share a file. You can share it with people you choose, which requires you to invite specific Apple IDs, or you can generate a public URL by selecting anyone with the link.

Right. Starting in 27.3, if you choose that anyone with the link option, Apple has stated they will begin scanning those specific files for what they classify as harmful content. And the technical reality of that scan is what's causing the uproar, right? Exactly. Because Apple's own support documentation now explicitly states that when you generate a public link, that file is no longer end-to-end

encrypted. Well, while Apple hasn't released the exact white paper on this specific implementation yet, historically this kind of scanning relies on server-side hash matching. Hash matching. Yeah, they take the file, generate a cryptographic fingerprint, a hash, and compare it against a database of known harmful content.

Let me ground this in a real-world example. Please do. Say you take a video of your kids at the park and want to send it to your grandma. If you generate an anyone with the link URL and text it to her, Apple servers will hash and scan that video. Correct.

But if you use people you choose and specifically invite your grandma's apple ID by name, the end-to-end encryption remains perfectly intact and apple can't see a thing. That's the crucial difference. It's the exact same video, going to the the person, but tapping a different menu option completely changes your privacy footprint. It does. Now, it is crucial to be impartial here and look at both sides of the friction

this is causing. Right, because there's a big debate. There is. Apple's position is standard for cloud providers if you are using their servers to host a publicly accessible link. They have a legal and ethical obligation to ensure their network isn't being used to distribute illegal or harmful material. Which makes sense, from an infrastructure standpoint. Exactly. The critics, however, are

pushing back hard because Aval is not provided a rigid legal definition of harmful content. The gray area. Right. The fear is that an undefined term creates a slippery slope, potentially turning iCloud into a surveillance tool. Depending on who is defining the word harmful on any given day. It's a massive gray area. You know, the Synaptic Plunge team distributes digital downloads like their plug-in plan sheets using various share links. They do, yeah. This news was a stark reminder for the production team that any share link

set to anyone is fundamentally public infrastructure. You surrender a layer of privacy you make a link open to the web, whether you are using Apple, Google, or Dropbox. Let's draw across the board. The reaction on X is incredibly polarized as you'd expect. I can imagine. User Beezys saloon asked the exact question driving the debate, Who determines harmful content? Valid question.

Meanwhile, users like JustRus03 are trying to de-escalate the panic, pointing out that a lot of tech blogs are misrepresenting the the scope of the scan. It only applies to public links, not your private camera roll. I did see a rather opportunistic post from a privacy company called Sigeia. Oh, what did I say? They were loudly pointing out that Apple's fine print admits the encryption is broken

on public links. Even with advanced data protection, it's totally a sales pitch, but well, the underlying technical fact is correct. It is. So our dashboard takeaway for Apple users is essentially a think before you share kind of an answer.

Yeah. In version 27.3 right now, anyone with, anyone with the link means Apple is running a hash check. And if you want true end to end encryption for personal files, you must intentionally use the quote people you choose unquote setting. Right. All right. Yeah.

All right. Let's move from managing our data to a completely new way of generating it. This is the fun stuff. Definitely. So our final target today is for the desktop creators on Windows Mac or Linux. This is not a phone story. This is a desktop story. The Blender team just dropped Blender 5.3 and Gaussian Splatting is finally native. Yeah, I mean and for those for those working in spatial capture

This is this is a real this is a watershed moment. Okay Gaussian splatting is now rapidly overtaking traditional photogrammetry. Okay, I want to make sure I understand the distinction here because they sound similar to me Sure Traditional photogrammetry is when you take a bunch of photos of an object and the software tries to build a solid 3d mesh out of polygons, right? Exactly. And it often ends up looking a bit melted or warped if it can't figure out the complex

geometry. Precisely. Photogrammetry struggles with reflections, transparency and complex geometry, like the leaves on a tree. But a Gaussian splat doesn't build a mesh at all. It creates a radiance field.

Sounds like sci-fi. It kind of is. The software analyzes the video or photos and generates millions of tiny fuzzy colored points in 3D space. points. Yeah. Each splat is essentially a mathematical equation describing how light and color behave at that exact coordinate from any viewing angle.

It feels like absolute magic. It really does. You can just walk a circle around a statue in a park while filming on your phone. You run that video through a processor to create the splats. Import that file directly into Blender 5.3 and suddenly you have a photo realistic environment. Right on your desktop. You can set up a virtual camera and render a sweeping cinematic drone fly through of that statue and you never actually own a drone.

It completely democratizes highly advanced visual effects. However, we should be clear, 5.3 is very much a first step. What are the limitations? Currently you can import splat formats, specifically PLY and SPZ files. SPZ is particularly important because it's a highly compressed format designed to hold those millions of data points without instantly melting your computer's RAM.

That's helpful. But while you can import and view them, Blender 5.3 does not yet support exporting splats back out. Ah, and there are definitely some early adopter bugs too. Yeah, quite a few. Users are finding that the splats sometimes default to this weird emissive glowing state

which ruins the lighting setup of whatever 3D scene you drop them into. Yeah, that requires some manual tweaking in the shader editor to fix. Still, the fact that this professional grade tech is landing in a free open-source tool is incredible. Our producers were already scheming about how to use this. I bet.

If the Synaptic Plunge team wants to build a photorealistic 3D channel intro, or a trippy music visualizer for a sueno song, or even drop their 3D mock-ups of the plug-and-plan sheets into a real-world scanned office environment. The possibilities are endless. Exactly. Blender 5.3 makes the only real cost their time, not a massive software budget.

The 3D community on X is showing a very sober, practical kind of excitement about it. How so? Well, they love that the foundation is there, but they know it's a work in progress. Part 3D posted a great tip warning users not to expect too much just yet. They advise cleaning up the point cloud in an external tool called SuperSplat before importing the compressed SVZ file into Blender.

Smart workflow. Yeah. IndieTooling.com also pointed out that while the splats are viewable in real time in the viewport, The promised texture layers didn't make the final 5.3 cut. A bit of a bummer, but expected. But as user Rosamatsu perfectly summarized...

No export yet. Still free. That is the ultimate trump card for Blender. User Bogoth Progee really captured the macro view. Photoscans and AI generated worlds just became something every Blender user can open. So our final dashboard answer is a resounding try it. Blender 5.3 puts cutting edge spatial capture inside a free tool.

But treat it as experimental tech and be prepared to troubleshoot some rough edges. Definitely a weekend project. OK, we have covered a massive amount of digital ground today. You really have. Let's do a rapid fire recap of your targets. Pixel-oners, dig into your settings and update to Android 17 QPR2 today

to lock down those 232 vulnerabilities. Samsung owners 1 UI 9 offers great privacy tools, but waiting 48 hours for carrier bug reports is completely fine PC owners with Radeon cars and 30 seconds checking resource monitor right now To ensure the external events utility isn't silently chewing through your SSDs lifespan Apple users remember that in version 27.3 anyone with the link invites an Apple server hash scan So use people you choose for true encryption

description. Desktop creators, go download Blender 5.3 and start playing with Gaussian splats, but keep your expectations in check. Perfect recap. To give you a direct, actionable answer to today's title question. One second SSD check if you have a Radeon PC immediately.

Install the Pixel update today. Know exactly which iCloud sharing mechanism you are tapping. And treat the Samsung rollout and the Blender software as nice to try weekend projects. That is the perfect way to schedule it. Just knock out the security patch and the hardware check right now. Yep.

Before we wrap up though, I want to leave you with a final thought to mull over. Ooh, let's hear it. When we look at everything we discussed today, running resource monitors to prevent hardware degradation, auditing our cloud links to maintain encryption, understanding the nuances of system updates,

it highlights a profound shift. In what way? We are no longer just users of technology. Because these systems are so deeply integrated into our daily lives and honestly so incredibly complex, we are being forced to act as caretakers. Caretakers?

Mm-hmm. Wow. I really like that framing. It changes the relationship, right? It totally does. It brings us right back to the digital triage we started with.

It's not just about reacting when an emergency life flashes. It's about taking ownership of the system, doing the routine maintenance, and making and your lying mechanics are actually serving you safely. Exactly. Just like taking care of a physical home. That's today's Daily Plunge. Thanks for listening to the Daily Plunge

from the Synaptic Plunge team.