Sedagive? and I picked up our Samsung Galaxy Nexus Android smartphones last Thursday at Costco. Since the Galaxy Nexus came out in the UK and other parts of the world earlier, we felt pretty good about being “early adopters” in the United States.
Overall the phone is a sweet piece of kit, and the Ice Cream Sandwich version of the operating system is pretty good. I have mixed feelings about it, but that’s for another post. I’ve enjoyed exploring mine. However, Sedagive’s? phone ran into a problem that we hope to never see again.
Her phone shut off unexpectedly while we were at IKEA Saturday night, just two days after getting our phones. She tried powering the phone on again, but nothing happened. We pulled the battery and tried again. The phone booted this time, but became stuck at the loading animation screen. The boot screen animation looped over and over again. We pulled the battery again and went home instead of trying to troubleshoot it in the car.
I tried the following to fix the phone:
- Removed and reinstalled the SIM card.
- Removed the SIM card and powered up the phone without the SIM installed.
- Put the battery from my working Galaxy Nexus into her phone.
- Put the SIM card from my working Galaxy Nexus into her phone.
- Tried to boot with Sedagive’s battery installed, yet running from the wall charger.
- Some US Galaxy Nexus owners were reporting boot loop problems when going from a WiFi area to another network type (3G or LTE). This was apparently fixed in the latest over the air update, but you know how things go. Some owners were able to get their phones working again by doing a factory reset and then disabling either WiFi or 3G/LTE. I tried to do a factory reset by holding down the volume up button and the power button while the phone was off.
The phone didn’t respond to that key combination, and continued to get stuck in the boot animation loop.
- We called Verizon Wireless from my Galaxy Nexus. “Becky,” the customer service representative, sounded genuinely concerned that Sedagive’s phone was dead. After all, it had only been out in the market for two days. I told her what I’d done, and she said that was her troubleshooting script as well. There was nothing we could do except exchange the phone.
Costco only had five Galaxy Nexus phones on launch day. By the time Sedagive? got hers they were down to two, with another customer apparently coming in. This was all before 3PM on Thursday, so we were concerned they were going to be sold out.
- We had to go to Costco on Sunday anyway, so I attached the phone to the wall charger and just let it run. After about 90 minutes the phone chirped — Sedagive? had an email notification. Apparently the phone was fine.
So far so good — although she didn’t trust the phone and wanted to exchange it anyway at Costco.
We were in luck, and they had several Galaxy Nexus phones in stock on Sunday. The lady tried to tell us that phones use battery power when going from WiFi to other networks and back again, and that sometimes the battery runs low. Sedagive? gave her the best “you are a dumb whore” look I’ve seen in awhile and then dropped knowledge on her about what was going on. We finished up our rundown with “and Verizon suggested we return the phone to you,” and that was that. New phone on the way.
The staff attempted to do a factory reset on Sedagive?’s phone but it got stuck in a loop again. I’m not sure how long it took for the phone to sort itself out, but I did all of my shopping at Costco in the meantime. I’d say it was at least twenty minutes. I was able to verify that the phone was eventually returned to the factory setup.
Between the screwy booting loop, our inability to get the phone to recognize the factory reset key combination while the phone was wonky, and the troubled reset at Costco, I am very glad that Sedagive? exchanged her phone. The new handset appears to be fine, and she mentioned that the screen orientation seems to be faster than on the last Galaxy Nexus. Perhaps that’s another symptom of a bad phone, but it’s too soon to tell.
I am afraid that more people may have these problems before we hear more about it, but I hope that ours is just an isolated case of a droid with a bad motivator.