Nexus S bug forces reboot on phone calls

The Nexus S, Google’s flagship successor to the Nexus One, has barely been out a month and there’s already a major forced reboot bug found in it, which Google was recently forced to admit.

A user reported the problem at the end of December, where they were getting random forced reboots, usually while making a call. Dozens of other people reported the same problem, sometimes when making phone calls over 10 minutes and other times less than five minutes.

The problem appears to be contained to either the Nexus S itself or Android Gingerbread 2.3.1, build GRH78. Since The Nexus S is the only device that currently has the latest Android release it could potentially be a much bigger issue when updates start rolling out for other phones.

A Google employee responded to the difficulty recently, stating: “So we’ve successfully reproduced this issue and are in the process of investigating with Samsung. I’ll provide updates as soon as I have them.”

The problem is that the priority of the problem is marked Medium, much lower than expected for such a severe glitch. While it may not affect all Nexus S owners, the inability to make calls is kind of a deal-breaker for a mobile phone.

The Medium rating is also what was used for an irritating bug that affected Android 2.2, where people’s texts were sent to the wrong person. It took six months for Google to develop a fix for the problem and it still hasn’t been rolled out to everyone. Nexus S owners may have to wait for some time yet.