Starting late last month, users of the Samsung Nexus S have made myriad complaints on the Web about the Android OS 2.3-based smartphone, citing issues that include forced bootups during voice calling, balkiness during Bluetooth streaming, and a continuation of SMS messaging troubles.
One user, who calls himself WestIndiesKing, seemed to suggest that a recent OTA update from Google to Android 2.3.1/GRH78 might be to blame for his problems during voice calls.
“Since the update I have been experiencing random reboots at least once every two days. It’s driving me nuts,” he wrote, in Google’s Mobile Help Forum. “Anyone else having this issue?”
Google: ‘Getting Close to Root Cause’ of Reboots During Calls
“Hey everyone, Thanks for your many useful reports. We are getting close to tracking down the root cause of the reboots during calls and are currently testing a fix to resolve the issue. I’ll come back to keep you informed once we know more,” responded a Google employee named Ry Guy.
It’s unclear at this point whether the forced bootups are the fault of the Android OS software or the Samsung-built phone hardware, but the Nexus S is the only model running Google’s OS 2.3, and it’s the only one having most of these issues.
Problems with Bluetooth Streaming, too
Indications of other possible bugs, related to Bluetooth audio streaming, also started surfacing after the OTA OS update on December 23.
“It seems like I can only get about 10 to 15 minutes streaming audio before the phone becomes completely unresponsive, won’t power on or anything,” said krohnjw, in a post in the XDA Developers Forum.
Answered coco 135, another user: “You should be thankful…I can’t get more then 10 sec without it being cut off and play again…for…10 sec.”
SMS Texting Mishaps Keep Going On
All the problems aren’t related to Android OS 2.2; Users of the Nexus S have also been encountering the same issues with SMS texting — involving transmission of messages to the wrong contacts — that have also plagued users of other smartphones running Android OS 2.2.
By now, many users are plenty perturbed that Google hasn’t yet fixed the texting glitch.
“Very worried about this. I wonder why the big [smartphone] providers do not make much noise here,” wrote michi in Google’s Code Forum. “Will they pay damages when the SMS went to the very wrong person?!?”
Predicted another user, cheungsz, “This [is] gonna be even more disastrous than the iPhone 4 faulty alarm clock episode. Leave it untouched if you want Android to be as notorious as iPhone.”
Bugs Get ‘Medium’ Priority from Google
Presumably, Google and other producers of Android OS phones are going to be under intensified pressure to offer bug-free user environments now that Verizon Wireless has unveiled its own version of the iPhone.
Google, however, has reportedly assigned a priority of only “medium” to both the random bootup and text messaging bugs. It’s unknown whether Google will remedy those problems prior to Android 2.4 (aka Ice Cream), a release currently rumored to be set for availability as early as May or June.