Samsung Galaxy Unpacked: No Peeking! - Waveform: The MKBHD Podcast Recap
Podcast: Waveform: The MKBHD Podcast
Published: 2026-02-27
Duration: 1 hr 15 min
Summary
In this episode, the hosts discuss the recent Samsung Galaxy S26 unveil and the Nothing Phone 4A launch, while also sharing insights from their past live podcast at South by Southwest. They dive into some tech frustrations, particularly with WhatsApp voice messages on Pixel devices.
What Happened
The episode kicks off with Marquez, Andrew, and David welcoming listeners back and sharing their excitement about returning to South by Southwest for another live podcast. They reminisce about their first live event last year and encourage listeners to join them on March 13th at 10 a.m. on the Vox stage, hinting at an engaging Q&A format similar to last year’s event. The hosts reflect on the fun atmosphere and the lively interactions they had with the audience, setting the stage for an even better experience this time around.
Transitioning into the tech discussions, the hosts dive into the unveiling of the Samsung Galaxy S26 and the partial reveal of the Nothing Phone 4A. They express their thoughts and excitement about the new features and designs showcased during the event. A particular focus is placed on discussing the challenges they face with technology, especially the glitches experienced with WhatsApp voice messages on Pixel devices. David shares an anecdote about how his voice messages would pause unexpectedly, leading him to suspect a bug within the Pixel rather than the app itself. This leads to a broader conversation about app accountability and user frustration when tech doesn’t work as expected.
Key Insights
- The hosts are returning to South by Southwest for a live podcast event, encouraging audience participation.
- The Samsung Galaxy S26 and Nothing Phone 4A were major topics of discussion, highlighting their new features.
- David shares a personal tech frustration with WhatsApp voice messages on Pixel devices, suspecting a bug specific to the phone.
- The conversation touches on how users typically assign blame in tech issues, often towards app developers.