Android 2.3 code hits the net
Even though Nexus S is designed to be suitable for AOSP work, there are some caveats. I very strongly recommend against trying to use Nexus S for anything related to AOSP at the moment. Trying to unlock or use your Nexus S for AOSP work could easily turn it into a Nexus B (where B means 'brick'); I have two of those, they're not very useful."
Posted Dec 18, 2010 0:29 UTC (Sat)
by me@jasonclinton.com (subscriber, #52701)
[Link]
Kernel.org is already under a lot of load: http://twitter.com/#!/warty9/status/15892347757789184
Posted Dec 18, 2010 1:28 UTC (Sat)
by karim (subscriber, #114)
[Link]
Posted Dec 18, 2010 4:10 UTC (Sat)
by davide.del.vento (guest, #59196)
[Link] (1 responses)
Posted Dec 19, 2010 3:48 UTC (Sun)
by swetland (guest, #63414)
[Link]
JBQ's use of "brick" was unfortunate here -- the main issue is that the original factory system images are not available for download yet, so if you flash a custom build that doesn't work there's not a trivial way to restore to the original build.
We'll be getting this resolved soon.
Posted Dec 18, 2010 17:37 UTC (Sat)
by busterb (subscriber, #560)
[Link] (2 responses)
Posted Dec 18, 2010 18:07 UTC (Sat)
by karim (subscriber, #114)
[Link]
Posted Dec 20, 2010 22:54 UTC (Mon)
by ldo (guest, #40946)
[Link]
Android 2.3 code hits the net
Android 2.3 code hits the net
Android 2.3 code hits the net
http://googlemobile.blogspot.com/2010/12/wait-is-over-ann...
Android 2.3 code hits the net
The Cyanogen port appears to have wasted no time updating to 2.3
The Cyanogen port appears to have wasted no time updating to 2.3
Gingerbeard