Just had it happen to me for the first time. I starred the issue;; but notice there's only 32 stars on it.
The bug report has been declined at ... so it doesn't look like they think it's a gingerbread problem.
Although the Nexus One and Nexus S run pure Android, this issue tracker is not the place to report bugs for these devices. I am going to continue posting updates to this issue on the Google Mobile forum.
Hey all,
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.
-Ry Guy
I find if difficult to distinguish a bug in the Android software and a bug in software running on a "Pure Android experience device". Aren't they the same thing?
That's not exactly true. The close comment said:
In the Google Mobile forum mentioned an official Google employee posted:
So it seems there is a real problem. Google has confirmed and reproduced it, but have yet to confirm if it's software or hardware. However, by the number of people returning their devices and having the same problem again makes me think its a software issue.
On a personal note, I find if difficult to distinguish a bug in the Android software and a bug in software running on a "Pure Android experience device". Aren't they the same thing?
One thing that I read there, all bug reports are using Android 2.3.1 ...
Anyone has this bug on 2.3?
One thing that I read there, all bug reports are using Android 2.3.1 ...
Anyone has this bug on 2.3?
Hi all. Last night I called 02 a few times and the call was dropped and the phone restarted three times, each time a while (~10 - 15 minutes) into the call. The phone rebooted and operated fine after (although, like i say, repeated this behaviour a second ten third time).
No problems before or since to do with anything else.
Anyone experience the same? Any clues or diagnostic tips?
ta