When old iPhones get a lifeline: iOS 12.5.8 keeps iMessage and FaceTime alive

A small update can feel like a minor miracle when it suddenly makes an ancient phone useful again. On January 26, 2026, Apple quietly pushed iOS 12.5.8 to a handful of legacy devices — an unexpected but welcome move that ensures iMessage, FaceTime and device activation keep working on models that can’t run modern iOS releases.

Why this matters more than it sounds

• Many people still rely on older phones as spare devices, handed-down hardware, or phones for kids and elders.
• Some core services — iMessage, FaceTime and device activation — depend on security certificates that can expire. When that happens, even a perfectly functional battery and screen can’t redeem a device that can’t authenticate with Apple’s services.
• Apple’s 12.5.8 update renews those certificates so these services continue to work past the original expiration window (Apple’s release notes say this extends functionality beyond January 2027).

That’s not a flashy feature update — no redesign, no new widgets — but it’s practical maintenance that keeps devices online and useful for everyday communication.

Which devices are covered

• iPhone 5s
• iPhone 6 and iPhone 6 Plus
• iPad Air (original)
• iPad mini 2 and iPad mini 3
• iPod touch (6th generation)

If you own (or inherit) any of these models and still rely on Messages or FaceTime, installing iOS 12.5.8 is the simple way to avoid service interruption.

A little context: Apple’s approach to legacy support

• Apple has a reputation for longer OS support than many Android vendors. This update extends the lifespan of devices launched in 2013–2014 — a 12–13 year span for the iPhone 5s and iPhone 6.
• Historically, Apple issues focused security patches and certificate renewals for legacy OS branches (like iOS 12) when a backend change would otherwise break key functionality.
• This particular update appears targeted and intentional: it replaces an expiring certificate rather than modernizing the platform.

What to do if you have one of these older devices

• Back up the device first (iCloud or a local backup) in case anything goes wrong.
• Check Settings > General > Software Update and install iOS 12.5.8 when it appears.
• After updating, verify iMessage and FaceTime activation by sending a message or placing a FaceTime call.
• Remember that app compatibility, security protections, and modern features remain limited on these devices — this update preserves core Apple services, not modern app support.

Why Apple might care about keeping old devices working

• User experience: Broken messaging or activation is an outsized annoyance for users who otherwise have functioning hardware.
• Device activation matters for transfer, resale, repairs and emergency calls — so certificate renewals protect many downstream scenarios.
• Environmental and social impact: Extending useful life reduces e-waste and helps people who can’t or don’t want to upgrade frequently.
• Brand consistency: Apple benefits when its services remain reliable across generations, even if hardware is dated.

A few caveats

• This update does not make old hardware secure in the same way a modern iPhone is. Newer iOS releases get deeper security architecture upgrades and broader app compatibility.
• Apple has also briefly stopped signing a few recently released updates (reported January 28, 2026), which can affect the availability of specific builds. If an update doesn’t appear or seems blocked, check Apple’s official notes and retry later.

Quick takeaways

• iOS 12.5.8 (released January 26, 2026) extends the certificates that let iMessage, FaceTime and device activation continue to work on older Apple devices.
• The update is small and targeted but meaningful: it keeps legacy hardware useful for communication and activation tasks.
• If you use an iPhone 5s, iPhone 6, original iPad Air, older iPad mini, or iPod touch (6th gen), install the update after backing up.

My take

This is the kind of practical, unspectacular move that quietly matters to real users. It’s not about headlines or feature lists; it’s about keeping connections alive. For people holding onto older devices for budget, sentimental, or environmental reasons, Apple’s certificate renewal is a small mercy — one that nudges the device’s useful life forward without pretending it’s modern. Companies don’t always prioritize these low-glamour fixes, so when they do, it’s worth noticing.

Sources

• Apple Support — About the security content of iOS 12.
  https://support.apple.com/en-us/103695

• MacRumors — iPhone 5s Gets New Software Update 13 Years After Launch (January 26, 2026).
  https://www.macrumors.com/2026/01/26/iphone-5s-software-update/

Steam finally goes fully 64‑bit on Windows — and it actually matters

A small, quiet change rolled out in December 2025 that will make a surprising number of problems less annoying over time: Valve has converted the Windows Steam client to a native 64‑bit application. If that sounds like a nerdy footnote, stick with me — this is the kind of technical housekeeping that unlocks better stability, simpler development, and fewer edge-case crashes for millions of PC gamers.

What to know right away

• The Steam desktop client for Windows 10 (64‑bit) and Windows 11 is now a native 64‑bit application (stable rollout in December 2025).
• Valve will continue delivering a 32‑bit build only to systems that require it until January 1, 2026; after that date 32‑bit Windows installs will no longer receive updates or support.
• The update also bundled several quality‑of‑life fixes and controller/input improvements (friends/chat reporting tweaks, recording/export fixes, better controller support, Big Picture/Remote Play bug fixes).

Why this upgrade matters

Upgrading an app from 32‑bit to 64‑bit is more than a checkbox for developers. For Steam, the switch brings practical benefits:

• Better memory handling. A 64‑bit client can address far more memory, which makes it harder for leaks or memory‑hogging bugs to bring the whole Steam client (and sometimes the running game) to its knees.
• Cleaner toolchain and testing. Valve no longer has to maintain two separate native builds for modern Windows installs, which reduces platform complexity and frees engineering time.
• Compatibility with modern platform pieces. Many modern libraries, browser engines, and drivers are optimized for 64‑bit Windows — moving the client to 64‑bit aligns Steam with that ecosystem and avoids fragile edge cases.
• A path for future features. Removing a legacy constraint lets Valve adopt newer subsystems or optimizations that assume 64‑bit execution.

Put simply: this is an investment in long‑term stability and fewer weird failures for the vast majority of Steam users.

What else shipped with the December update

Valve didn’t stop at the binary switch. The release notes and coverage show a batch of smaller but tangible fixes and additions:

• Friends & Chat: new reporting options for suspicious or harassing messages inside group chats (right‑click to report and optionally block/unfriend).
• Game recording: fixes for exporting H.265 videos and clipboard issues on certain NVIDIA 50xx GPUs.
• Steam Input: expanded controller support — including Nintendo Switch 2 controllers over USB, improved GameCube adapter behavior in Wii U mode (with rumble), and pairing improvements for high‑end controllers like DualSense Edge and Xbox Elite.
• Big Picture / Remote Play: stability and usability fixes (fewer in‑game purchase failures for some titles, Remote Play mouse movement fixes across multiple monitors when using touch).
• Miscellaneous stability fixes: for the embedded browser helper and other components that could occasionally spawn stray windows.

These are the small wins that make day‑to‑day Steam use more pleasant.

Who’s affected (and who isn’t)

• Practically everyone on modern Windows is unaffected in a painful way — if you’re on Windows 10 64‑bit or Windows 11 you get the 64‑bit client automatically.
• A vanishingly small group of users on 32‑bit Windows 10 (Valve’s telemetry puts this at around 0.01% of the user base) will still be able to run Steam for a short while, but their client will stop receiving updates and security fixes after January 1, 2026. If you’re in that group, upgrading to a 64‑bit OS is the practical recommendation.
• 32‑bit games remain supported. This change affects the Steam client binary and support lifecycle for 32‑bit Windows OSes — it doesn’t mean Valve is suddenly dropping older games.

The broader context

The move fits a larger trend across the industry: operating systems and large platform apps are shedding 32‑bit legacy support. Microsoft’s push and the natural hardware turnover means most PCs now run 64‑bit Windows, and browser engines and middleware are drifting away from 32‑bit compatibility. For Valve, consolidating around 64‑bit simplifies interactions with anti‑cheat vendors, browser components, and controller vendors — all of which tend to favor 64‑bit builds.

It’s also a subtle signal about priorities: Valve is choosing engineering simplicity and future readiness over maintaining obscure legacy setups. For a platform serving hundreds of millions of users, that pragmatism makes sense.

My take

This isn’t flashy, but it’s the kind of under‑the‑hood improvement that compounds. You won’t see a headline getting you excited about a new feature, but you will notice fewer random crashes, smoother controller behavior, and a slightly cleaner Steam client experience over time. For power users and developers, it removes a constraint that used to complicate troubleshooting and testing. For the tiny fraction still on 32‑bit Windows, the deadline of January 1, 2026 makes upgrading unavoidable if you want continued support.

Sources

• Steam’s December update finally brings a fully 64‑bit client to Windows, Windows Central — https://www.windowscentral.com/gaming/pc-gaming/steams-december-update-finally-brings-a-fully-64-bit-client-to-windows-modernizing-the-platform-after-years-of-partial-support
• Valve will drop support for the last 32‑bit Windows systems in January 2026, Ars Technica — https://arstechnica.com/gaming/2025/09/steam-will-drop-support-for-the-last-32-bit-windows-systems-in-january-2026/
• Steam announces end of support for 32‑bit Windows 10, PC Gamer — https://www.pcgamer.com/gaming-industry/steam-announces-end-of-support-for-windows-10-32-bit-saying-only-0-01-percent-of-pcs-are-still-running-it/

A key in your pocket: Rivian Digital Key brings Gen 2 cars into your phone wallet

There’s a tiny moment of delight when you walk up to your car, your phone in your hand (or not), and the vehicle simply knows you’re there. Rivian just made that moment more seamless. On December 18, 2025, Rivian began rolling out Rivian Digital Key for Gen 2 R1T and R1S vehicles — a native digital-wallet car key experience for iPhone, Apple Watch, Google Pixel, and Samsung devices that lets owners unlock, share, and start their Rivian without the dedicated fob or the Rivian app’s Bluetooth-only workflow.

This isn’t just another “app feature” patch. It marks a bigger shift toward platform-level convenience, tighter hardware integration (Ultra-Wideband and NFC), and the standardization of car access across ecosystems.

Why this matters now

• Smartphones have increasingly replaced physical items (boarding passes, credit cards, transit passes). Car keys are the next obvious candidate — but only when the integration is reliable and secure.
• Rivian’s Gen 2 cars were built with newer connectivity and UWB hardware that make native wallet keys practical in ways first-gen Bluetooth approaches weren’t.
• By supporting Apple Wallet, Google Wallet, and Samsung Wallet, Rivian avoids locking users into a single OS and taps into the “works-as-you-expect” experience people now expect from modern devices.

What Rivian Digital Key does

• Native wallet integration: Add your Rivian Gen 2 car key to Apple Wallet (iPhone & Apple Watch), Google Wallet (Pixel), and Samsung Wallet.
• Multiple unlocking modes: Ultra-Wideband (UWB) for precise hands-free proximity; NFC fallback that can work even when the phone is in power-reserve (Rivian notes up to ~5 hours on supported devices).
• Key sharing: Send digital keys to family and friends instantly — no physical handoffs.
• Broader device support: Works across major smartphone ecosystems to maximize owner convenience.
• Requirements and flow: The feature arrives with Rivian’s 2025.46 OTA and Rivian Mobile App update (3.8.0); some Android implementations require recent OS versions (Android 15 / One UI 7.0 mentions in reporting).

(Technical specifics and exact device compatibility can vary; check your vehicle’s OTA status and the latest Rivian app release notes before expecting the feature on your car.)

How this compares to the old way

• Old: Rivian’s earlier digital key used the Rivian app and Bluetooth Low Energy. It worked, but could be slower, less precise, and was app-dependent.
• New: Keys live at the OS level (Wallet apps), enabling Express/Power Reserve, tighter proximity detection through UWB, native watch support, and a fallback NFC path if the battery is depleted. In short: faster, more reliable, and more integrated.

The broader context

• Rivian is part of a broader industry trend: automakers are adopting the Car Connectivity Consortium (CCC) standards and integrating with phone wallet ecosystems. Apple Car Key and similar Android standards have been rolling out across several manufacturers in recent years.
• This update arrives alongside other notable 2025.46 features (Universal Hands-Free driving modes and other Gen 2 improvements), signaling Rivian’s push to refine both autonomy and convenience features in tandem.
• The move also reflects product lifecycle strategy: many automakers concentrate new platform-level integrations on newer vehicle generations, which can leave earlier owners waiting or requiring hardware retrofits.

Opportunities and caveats

• Opportunities:

  • Simpler sharing: temporary or permanent digital keys can replace lending physical fobs.
  • Reduced lockout worry: Express/Power Reserve offers peace-of-mind if your phone dies.
  • Cross-platform parity: support for iOS and major Android ecosystems lowers friction for households with mixed devices.

• Caveats:

  • Compatibility: older phones or Gen 1 vehicles may not gain the same functionality.
  • Security and privacy: while wallet-based keys typically have strong device-level protections, owners should follow best practices (device passcodes, biometric locks, OS updates).
  • Reliance on hardware: UWB and NFC behaviors depend on device and vehicle hardware; real-world performance can vary by device model and environmental conditions.

What this means for owners and would-be buyers

• Gen 2 Rivian owners should look for the 2025.46 OTA and update the Rivian app (3.8.0+), then follow the wallet setup flow to add the car key.
• If you’re evaluating Rivian vs. other EVs, consider how important native wallet integration is to your daily routine. For many buyers, the convenience of wallet-based keys will be a useful tie-breaker.
• If you own a Gen 1 R1 and hoped for parity, note that many of these features rely on Gen 2 hardware and may not be fully transferable without retrofits.

A few practical tips for setup

• Update the Rivian mobile app to the version that mentions wallet support (3.8.0 or later) and ensure your vehicle has received the 2025.46 OTA.
• For iPhone owners: confirm iOS 17.4.1+ and Wallet readiness; for Apple Watch, make sure NFC works and watchOS is up to date.
• For Android owners: check Google Wallet or Samsung Wallet compatibility and any OS version requirements (reporting has referenced Android 15 / One UI 7.0 for some features).
• Keep your device OS updated and enable device-level protections (Face ID/Touch ID, PIN/passcode) for security.

My take

Rivian Digital Key is one of those “small” features that changes daily life more than you’d expect — especially once you get used to your phone being the primary interface for everything. By moving car access into native wallets and leveraging UWB/NFC, Rivian has reduced friction and added resilience (power reserve) against common real-world annoyances. It’s also a vote of confidence in cross-platform standards: owners shouldn’t need to swap ecosystems to get convenience parity.

That said, manufacturers must balance excitement with clarity: clear communication about device and vehicle compatibility will be crucial to avoid confusion, particularly between Gen 1 and Gen 2 owners. If Rivian keeps this momentum — and continues to make ownership feel like a continuous software upgrade — these moments of polish could become a meaningful competitive advantage.

Final thoughts

Digital keys are a practical example of how cars are becoming platforms rather than standalone devices. When automakers, OS vendors, and standards groups converge on simple, secure experiences like this, the payoff is everyday delight: fewer fumbling moments at the door, easier sharing with family, and one less physical item to misplace. Rivian’s rollout for Gen 2 is a smart step in that direction — now it’s about execution, clarity, and getting the experience right for every owner and device.

Sources

• New Software: Rivian Digital Key — Rivian Stories. https://stories.rivian.com/ (December 18, 2025).
• Rivian on the App Store — What’s New (Rivian App 3.8.0). https://apps.apple.com/us/app/rivian/id1570215232.
• Rivian to add Apple Wallet car keys with R1T and R1S OS update — 9to5Mac. https://9to5mac.com/2025/12/04/rivian-apple-wallet-car-keys-support-r1t-r1s-software-update/.
• Rivian rolls out software update 2025.46, including Universal Hands-Free driving and digital key — Electrek. https://electrek.co/2025/12/18/rivian-rolls-out-software-update-2025-46-including-universal-hands-free-driving-and-digital-key-for-apple-and-android-users/.
• Rivian rolls out new ‘Universal Hands-Free’ driving feature — TechCrunch. https://techcrunch.com/2025/12/18/rivian-rolls-out-new-universal-hands-free-driving-feature/.

A faithful throwback: ModRetro’s M64 and the return of the N64 controller

The image of an original Nintendo 64 controller — that odd three-pronged trident, a chunky thumbstick centered like an awkward crown — still sparks a weird, affectionate debate. Is it genius or relic? ModRetro may have just answered that question by leaning into nostalgia. The company unveiled the design for its upcoming M64 console and, yes, recreated the classic N64 controller almost perfectly. But the reveal leaves the bigger, juicier questions — performance, features, and real-world polish — tantalizingly unanswered.

Why this matters beyond nostalgia

It’s easy to shrug this off as another retro-lite product for collectors. But the M64 sits at an interesting crossroads in retro gaming hardware:

• It’s an FPGA-based system, which means it’s aiming for hardware-accurate reproduction of the original N64 experience rather than the software emulation most people are used to.
• The M64 arrives in a moment when multiple companies (Analogue being the most notable) are chasing faithful N64 remakes, and each choice — from controller design to FPGA selection — signals what “authentic” will mean for a new generation of retro consoles.
• The controller decision matters. Analogue partnered with 8BitDo to modernize the N64 pad; ModRetro chose authenticity. That’s a deliberate statement about the market they’re courting.

What ModRetro revealed

• Design: Translucent console shells in green, purple, and white that echo N64 colorways while peeking at internal hardware.
• Physical features: Top-mounted cartridge slot, four front controller ports, HDMI, multiple USB-C ports, and a microSD slot. A large power button and a dial labeled “Menu” are visible but not yet fully explained.
• Controller: A near-identical recreation of the original three-pronged N64 controller — central thumbstick, trigger layout, and the familiar silhouette — color-matched to the console.
• Price signaling: Introductory pricing reportedly set at $199, a cheeky nod to the original N64’s 1996 launch price. Availability details initially favored a waitlist, then expanded.

(Source coverage emphasized the design reveal more than performance specs.) (theverge.com)

The technical elephant in the room

Design and nostalgia sell photos. But for serious retro fans, the crucial question is: how well does it play?

• FPGA promise: ModRetro is positioning the M64 as FPGA-driven, meaning the goal is cycle-accurate recreation of the N64’s hardware behavior rather than pure software emulation. That’s the same philosophy behind Analogue’s work and the MiSTer community — and when done right, it makes classic games feel and respond like the originals. (theverge.com)
• Unknowns that matter:
  • Which FPGA and memory architecture are used? Those choices strongly influence how accurately the system can reproduce complex N64 graphics and timing.
  • Which N64 core or implementation is running on the hardware? Some recent reporting suggests ModRetro has ties to existing MiSTer N64 cores and contributors, which could be promising for fidelity. (timeextension.com)
  • Latency, upscaling, and compatibility (especially for tricky titles like Mario 64 or games that used specific cartridge expansion hardware) are still unproven.

The controller debate: authenticity vs. ergonomics

• Choosing authenticity: The recreated trident controller is a love letter to purists. For collectors and players who grew up on the original hardware, a faithful pad is comforting and — for some games — essential for the right feel.
• The ergonomic trade-off: The original design is polarizing. Modern reinterpretations (like Analogue’s 8BitDo collab or third-party controllers) try to keep the layout while improving sticks and shoulder inputs. ModRetro’s decision suggests they prioritize historical fidelity over ergonomic modernization. For competitive or long-session play, that could be a downside for some buyers. (theverge.com)

Market context and why ModRetro’s move is interesting

• Competition: Analogue’s 3D project and a slew of emulation-based solutions create a crowded field. Each approach — software emulation, FPGA, or hybrid — attracts different buyers. ModRetro is positioning the M64 as a lower-cost, authentic option in that space. (androidauthority.com)
• Community ties: Early signs indicate ModRetro is engaging with the MiSTer/FPGA community and possibly integrating proven N64 cores. If they contribute back or collaborate, that could elevate the platform’s credibility among enthusiasts. (timeextension.com)
• Brand context: ModRetro’s founder, Palmer Luckey, is a visible and polarizing figure; that shapes public reaction and coverage even when the product itself is broadly appealing to retro fans. Expect PR noise to mingle with product discussion.

What to look for next

• Detailed spec sheet: FPGA model, RAM configuration, video pipeline, and exact I/O functionality (what that Menu dial actually does).
• Compatibility list: Which cartridges work out of the box, and how the system handles edge cases and expansion carts.
• Controller feel tests: Stick drift prevention, deadzone behavior, and whether the recreated controller uses modern sensors or vintage-style potentiometers.
• Public demos and hands-on reviews: Playable showings (like retro expos) or early review units will reveal whether the M64’s claims match reality. (androidauthority.com)

Quick highlights for skimmers

• The M64 is an FPGA-based N64 tribute with a nearly identical recreation of the original trident controller.
• ModRetro favors authenticity over modernized ergonomics.
• Important technical and performance details remain unconfirmed; community FPGA cores may be part of the plan.
• Intro pricing at $199 echoes the original N64 launch cost.

My take

Seeing the M64’s translucent shell and faithful controller design gives me nostalgia goosebumps — it’s a crisp visual promise. But hardware nostalgia is only worth so much on Instagram shots and product renders. The real story will be whether ModRetro’s engineering choices deliver a low-latency, high-compatibility experience that respects the weird quirks of N64 hardware. If they pull that off at the reported price, the M64 could be a delightful, more affordable competitor in a market that’s been hungry for faithful N64 hardware for years.

Sources

• ModRetro recreated the N64 controller for its M64 console — The Verge
  https://www.theverge.com/news/831498/modretro-m64-console-4k-fpga-nintendo-64-clone

• ModRetro's N64 Tribute Console Has A Price, Launches Later This Year — GameSpot
  https://www.gamespot.com/articles/modretros-n64-tribute-console-has-a-price-launches-later-this-year/1100-6533380/

• ModRetro's N64 clone is fully playable and ready for the spotlight — Android Authority
  https://www.androidauthority.com/modretro-nintendo-64-fpga-m64-pricing-3580094/

• ModRetro's FPGA N64 Uses FPGAzumSpass's MiSTer N64 Core — Time Extension
  https://www.timeextension.com/news/2025/08/modretros-fpga-n64-uses-fpgazumspasss-mister-n64-core