Droid 2 Was Dropped, Didn't Explode - Motorola Employee
Earlier this month, we told you the story of a man in north Texas whose exploding Droid 2 sent him to the hospital, resulting in a blood splattered handset and a face full of stitches. — The man, Aron Embry, told the press …
Context & Ripple Effects
The Droid 2 has been Motorola's flagship push since its August 2010 launch at $200 on contract, but the device line has spent the year fighting perception problems, from a botched Android 2.2 rollout to this month's report that a north Texas man, Aron Embry, went to the hospital after his handset allegedly exploded, leaving him stitched up and the phone blood-spattered.
With no syndicated pickup or public reaction recorded yet on the story, the only counterweight so far is a single Motorola employee telling Gearlog the phone was dropped, not exploded — a denial that matters because the claim is circulating under the vendor's own brand name heading into the holiday selling season.
First-order effects
- Motorola is now publicly contesting Embry's injury account, reframing the incident as drop damage rather than a product defect while the story carries the 'exploding' label in press coverage.
- The dispute puts Verizon's flagship Droid 2 marketing message in tension with a hospitalization narrative attached to the same handset.
Second-order effects
- If other Droid 2 owners report similar incidents, pressure shifts to Motorola and Verizon to produce forensic evidence distinguishing impact damage from battery or hardware failure.
- Rival handset makers gain an opening to contrast their own safety records against the 'exploding phone' headlines, regardless of how the dropped-vs-exploded question resolves.
Third-order effects
- Smartphone vendors facing injury claims are learning that the first public statement — even an informal one from an unnamed employee — sets the frame for whether the incident reads as user error or a recall-worthy defect.
- As handsets pack more energy-dense components into slim bodies, single-user incidents become brand-level events that can force formal investigation protocols across the industry.
The trend: Flagship smartphone incidents are being fought first in the press narrative — vendor denials racing user accounts — before any engineering verdict arrives.