I have no problem ditching my AirPods for these earbuds - especially at this price
Briefly

I have no problem ditching my AirPods for these earbuds - especially at this price
"The CMF Buds 2 Plus feature a similar square-ish case to the Bud Pro 2. While the dial is still present, it isn't functional and is only present as a signature CMF design element. The absence of the Smart Dial feature doesn't bother me since I seldom used it on the Pro model. The overall case build has a textured but slightly slippery finish."
"The buds themselves are light and fit me well. They have a small touch control area that recognizes taps. You can double-tap, triple-tap, tap-and-hold, and double-tap-and-hold to control the music playback, volume, and ANC. Also: Google just gave Android Auto its most significant update yet - and we tested it on the road While I find swipe gestures to be more intuitive, the controls on CMF Buds 2 Plus earbuds work well... unless you're a side sleeper."
"They fit well, and there's not much to fault at that $79 price point, and even less to complain about when they're often discounted to $55. Soon after launch, I shifted to the CMF Buds 2 Plus as my daily driver for music and calls. Also: 100+ best Black Friday deals from Amazon, Walmart, & more still live Apart from one minor annoyance, there's a lot to like. These might be my new go-to recommendation for budget earbuds."
CMF Buds 2 Plus deliver strong value through frequent discounts, often priced at $55 during sales, while offering sound and call performance competitive with higher-tier models. The case resembles the Bud Pro 2 with a nonfunctional Smart Dial as a design element and a textured yet slightly slippery finish. The lightweight earbuds fit comfortably and provide tap-based controls for playback, volume, and ANC. The touch sensors can falsely trigger from clothing or pillow covers, causing ANC on/off pings when lying on a side. Overall performance and price make them a strong budget-earbud recommendation despite the touch-sensitivity issue.
Read at ZDNET
Unable to calculate read time
[
|
]