ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Myth of "Exploding Droid X Phone" Busted: why battery and capacitor did NOT explode next to ear! It wasn't the speaker!

Updated on March 3, 2015

Really? Phone Exploded?

On December 3rd, 2010, news spread that a man in Texas, Aron Embry, was wounded by an exploding Droid 2. Quoting the news from the Daily Mail...

Aron Embry, 30, from Texas, said he was getting in his car to travel to work when he decided to make a call.

In the middle of his conversation the phone 'burst outward' injuring the side of his face, he claimed.

Should you return your Motorola smart phone immediately? No. Let me explain why.

Droid 2 that allegedly exploded, but did it?
Droid 2 that allegedly exploded, but did it? | Source

The Impossibility of Physics

Only two items can explode inside a phone: the battery, and any capacitors on the circuit board. Those are the only items that STORE energy, and thus, have any potential to explode.

So are there any capacitors inside near the top? Fortunately, someone had disassembled a Droid 2 on iFixit, and there are NO capacitors in or near that location based on the disassembly. The only thing at that area is the speaker. Look at step 10 and 19.

So could it be the battery? If you look back at step 5, you will find that the battery is in the BOTTOM of the phone. (The camera is on top, and the phone's being held upside down). So it can't be the battery either. (I have the original Droid, I would know) And the damage... is on the TOP.

Thus, the damage shown in the picture CANNOT be produced from within the phone. The picture shows NO bursting of any sort from the phone.

Further check of the story confirms the facts: the man FINISHED the call. If any capacitor or battery had actually ruptured, the phone would have stopped working immediately. To quote again:

'I just heard a pop. At first I didn't know what to think', Mr Embry said adding that he then noticed blood trickling down his neck and saw broken glass on the phone's speaker.

Although the phone itself was left intact, the screen was ruined.

Also, look at the photo of the alleged damage: it is right around the hole in the glass, the weak area.

Finally, consider the following facts... when is the phone most likely to have the most energy? When it is at FULL POWER, after it's being charged. THAT is when it is most likely to "explode". NOT when it is being used and the power is being used up.

Thus, the phone could NOT have exploded.

So What Really Happened?

There are two possibilities that I see:

1) Mr. Embry had dropped the phone earlier, which had weakened the glass around that weak spot in the glass. When a loud noise or pressure was applied, the glass cracked, and he sliced his ear on the broken glass.

Indeed, this is the unofficial explanation leaked by Motorola as given to Gearlog.

2) Mr. Embry made up the whole story, like the "Balloon Boy" dad. The fact that he drove to his wife's work place instead of to a hospital is in itself, very suspicious. From the article linked earlier...

Mr Embry said he started to panic and drove himself to a local elementary school where his wife work so she could take pictures of his injuries.

There is not sufficient evidence to go either way at this time.


    0 of 8192 characters used
    Post Comment

    • H P Roychoudhury profile image

      H P Roychoudhury 

      7 years ago from Guwahati, India

      This is what is called the syndrome of Terrorism.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)