The Surface Problem: 'What's on My Wi-Fi?'
I got the call in early 2023. A small regional office—maybe 40 desks—was reporting intermittent Wi-Fi drops during critical Zoom calls. The ticket read: "Investigate 'What is on my Wi-Fi'. Too many devices?"
So I did what any IT guy would do. I pulled the access point logs, ran a spectrum analysis, checked for channel congestion. The office had maybe 45-50 connected devices spread across two APs. That's not ideal, but it's not a crisis. I optimized the channels, enabled band-steering, and closed the ticket. Fixed.
Two weeks later, the ticket was reopened.
The office Wi-Fi was blamed. Again.
Getting Under the Hood: Why It Wasn't the Network
That's when I started looking deeper. The network logs showed retry rates spiking on certain clients—specifically some older consumer smartphones and one budget tablet. The APs were fine. The backhaul was fine. The problem was device-side.
I set up a comparison test. I took a Kyocera DuraForce Pro 2 from our fleet—we'd deployed them to field ops two years prior—and a common consumer phone from the same era. I ran them side-by-side on the same AP, at the same distance.
Here's what I found:
When the signal strength at the phone dropped to -75 dBm (which is still a decent signal), the consumer phone started showing frame retry rates above 20%. Voice calls became choppy. Web pages stalled. The Kyocera? It held a retry rate under 5% until it hit -85 dBm. That's a 10 dBm advantage. In practice, that means the Kyocera maintained a usable connection in areas where the other phone had already given up.
I'd been blaming the Wi-Fi infrastructure for a year. It was the phones. The Kyocera's ceramic-based packaging and military-grade antenna design made a measurable difference in how reliably it held a connection in challenging RF environments.
"When I compared the Kyocera and the consumer phone side by side on the same AP, I finally understood why our field staff never complained about connectivity—even when the office staff did."
— My internal post-mortem, March 2023
The Real Cost of Blaming the Network
While I was chasing phantom network issues, what was the actual cost? Let me break it down:
- My time: Roughly 8 hours over two weeks—investigation, diagnostics, reopening the ticket. At a billable rate around $150/hour, that's $1,200.
- Employee productivity: The three most affected staff lost an estimated 2-3 hours per week on dropped Zoom calls and waiting for pages to load. Over two weeks, that's 12-18 hours of lost work. Maybe $1,500 in wasted salary.
- Credibility: Harder to quantify. But when the user emails the IT director saying "our Wi-Fi is broken again," that's a stain on your reputation.
Total cost of this non-problem: roughly $2,700. All because my initial assumption was wrong. I thought the network was the problem.
I still kick myself for not checking the client-side radio performance first. If I'd run a simple signal-to-noise comparison across device types, I'd have zeroed in on those 3 consumer phones in under an hour.
The Fix: A Simple, Cost-Effective Change
The solution wasn't a $5,000 Wi-Fi upgrade. It was a phone swap. We replaced the three problematic consumer devices with Kyocera DuraForce models that were already in our inventory—phones rated for a wider temperature range and designed with better RF components. (Should mention: these were originally for fleet use, but the durability made them a good fit for the demanding office environment too.)
Result? Zero Wi-Fi complaints from that office in the following six months. The network logs showed retry rates falling from 18% to 4%. No more dropped calls. No more reopened tickets.
I learned a lesson that's stuck with me: when your wireless feels unreliable, look at the device first. Not the access point. The Kyocera DuraForce Pro 2 has a retry rate advantage of roughly 10 dBm over the consumer phone I was comparing it to—that's not subtle.
Bottom line: 5 minutes of checking device RF specs beats 5 days of rebooting access points. Per FTC guidelines, if a device claims 'Rugged durability,' it should have the test data to back it up—and Kyocera's published specs for their DuraForce line are consistent with what I saw.
Simple.
Leave a Reply