Skip to main content

Review: Sony Noise Cancelling Headphones WHCH710N



Having multiple pairs of headphones and earbuds are important to me. I still use my Galaxy Buds on walks or at the gym, but I prefer wired, over ear for at home, and it was time to get a new pair, moving to Sony.

These replace my Sennheisers from about 2017 -- While they were uncomfortable for a long period of time, the sound quality was unmatched. I couldn't find a pair that looked comfortable and were hovering around 120$. One of the ear cups has broken off, and I can't super glue and rubber-band it back forever 😥 (Maybe I could use sugru? It's held up my car windows for 5 years. #NotAnAd)

 I had 5 criteria for a new set of wired over the ear headphones;

  • Colorful
  • Wired
  • Reasonable sound quality
  • Under 100$
  • Made in the past 3 years (No earlier than 2019)


I managed to get 4.5/5 -- The headphones are a nice blue (albeit darker than I'd like -- A lot of my furniture is dark, and I have lost tech for days because my cases are also dark.), they have both wired and Bluetooth capability with a microphone, we'll get back to the sound quality, they were 64$ on Black Friday, and they were first available in 2020!



The ear cups are much more comfortable -- They are over-ear as opposed to on-ear, and the cushion is flexible enough to not press the ear directly against the hardware or my glasses. No complaints.


The fact that these have several options is interesting -- Wired, Bluetooth, and even NFC, which I have never seen as a connection option. My familiarity with NFCs is through Amiibo and Amiibo cards to use with my Switch. 

I wonder if I could listen to a card. What would it sound like....I digress.

These do need to be charged for Bluetooth use -- The PDF guide says something akin to 24 hours for a full charge, and 10 minutes gets you 1 hours of playback -- but I wonder how it would work. Traditionally, headphones are powered through that cable that also gives us the audio, and better sound quality often comes from a wired connection instead of Bluetooth.

Update: 1/25 -- It has to be charged to even use the cable. That's...why I bought a set of headphones with a cable. So I didn't have to charge it and it could be powered through the cable, like past headphones.

 Interesting choice! And by interesting I mean odd and slightly annoying. To its credit, I've had these for a year (this is a 2/17/2023 edit), I have only had to charge it about twice.

Sound Quality

 Want to follow along with your own sound tests? Use the videos that I did:

Audio (No Vocals):

 Audio (Vocals):

Audio (Spoken Word):
* Use your own discretion, may involve language unsuitable for work. We're all adults here.

So my goal is to use these wired -- My initial connection was to my phone (Because it still has a headphone jack, ha ha!). It sounded oddly muffled. Then I attached it to my laptop to the same thing. 

Wondering if I would have to get out the superglue again, I decided to look at the PDF guide and reset the settings by holding the power button -- Sounds clearer, though not as much as the Sennheisers.

There is a noise cancelling button on the right earcup, but I'm not sure what it does, if anything, after pressing when wired. When Bluetooth-connected, it works well enough. It also seems to suck the battery fairly quickly.


With the variety of connectivity options is admirable, I'm not sure if some of the lesser-used options like NFC were necessary. Could that effort have been used to improve sound quality?

Also, needing almost a full day to charge completely hinders a quick wireless pickup and go.  Samsung Buds are better for that. These, in 2022, retailed for more than the Sennheisers in about 2017, but the sound quality is worse. However, Sennheiser seems to no longer make headphones that came out within the past 3 years around the 100$ range.

 These are around the same price as the Sony headphones, albeit currently on sale for $149 - A dollar more than the Sony ones. I'd spring the extra pocket change and get those.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory