Google acknowledges Nexus S failure during longer calls

Google acknowledges Nexus S failure during longer calls
Nexus S users have been complaining about their phone rebooting mid-call mostly during calls longer than 3 minutes, but up until recently Google did not admit the issue publicly. Well, it has now been successfully reproduced by a Google employee and hopefully a fix will come out soon.

The phone has been reported to restart with no apparent reason in various circumstances, but most often during longer calls. Some users reported that their phone would restart even during a shorter conversation and this definitely qualifies as a dead serious issue. It is not yet clear whether it is a software malfunction or if the problem is in the hardware. With Best Buy's two-week return policy running out for many soon, hopefully some information will appear soon that will shed some light on the issue.

While we hope that this is not ahardware problem, a Gingerbread-related problem would also be a misfortune for Google as they chose the Nexus S as the showcase handset for their latest version of Android. Have you experienced the same frustrating issue on the Nexus S?

source: Google Mobile Forum via IntoMobile



1. Distortedloop unregistered

Happened to me once, last week, after about 10 minutes into a call. I've been unable to duplicate it on my phone since. I've had the phone since December 17th, so it's not a frequent issue at all for me, but some claim it's happening to them every phone call in the forums I read.

10. Wardski unregistered

The Galaxy S had the exact same problem in the early firmwares. Good ole Samsung. Their motto should be "We don't learn from our mistakes - we like to re-create them instead.."

12. XxVerbalxX unregistered

Samsung: wait for the software update they have been like this for at least the last 6 years. they never get it right the first time around. once they do fix issues i do love their phones. they are turning into the new motorola (the bad motorola, pre droids)

2. fraankie unregistered

I would say the blame should fall on Samsung. XDA developers I9000 forum is full of dead internal SD fails, bricking the phone. I personally am on my 3rd mainboard because of this. And the nexus S is a galaxy S update.

3. Seylan unregistered

This is as big a deal as the antenegate problem with the Iphone 4! Unaccepectable! Stories like this make me feel proud to own a Nokia N8.

5. protozeloz

Posts: 5396; Member since: Sep 16, 2010

one difference... the antenagate could not be solved with an update, this one can

13. XxVerbalxX unregistered

bigger honestly. if u held the iphone "right" at least it worked... i slammed the iphone for the issue, to not slam samsung for this jus makes me a sad apple hater.

4. 530gemini

Posts: 2198; Member since: Sep 09, 2010

This is not a big deal. But if this happened to the iphone4, it would be :)

6. protozeloz

Posts: 5396; Member since: Sep 16, 2010

I guess you are right, an error coming from a company that makes around 10 smartphones a year should no be considered that big compared to an error made by a company that makes one phone once a year and that claims to have perfection

7. bucky

Posts: 3795; Member since: Sep 30, 2009

its a samsung.

8. metric152 unregistered

I wonder how widespread this issue is. I've had a problem with my phone rebooting but it was because a poorly written live wall paper. Since removing it I haven't had any problems.

9. hs78 unregistered

i have had this phone for few weeks.. i still haven't faced this issue.. strangely..not that i am complaining..:)

11. Tino unregistered

I have it since 20th of December and I experienced no dropped calls with my Nexus S...

14. mortac88 unregistered

Samsung Galaxy phones are garbage. I don't know why they have this reputation as being so great.

15. ARQJAV1 unregistered

I have the same booting issue but with my Motorola Milestone,I have changed the SBF file many times whit different ones and the problem persist have install cynogean mod and the G.O.T mod two an is the same problem, and now that I see this happeing to the Nexus S, I must say has to be a problem with Android.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.
FCC OKs Cingular's purchase of AT&T Wireless