Reports across the Internet about the Verizon Galaxy Nexus being dropped from AOSP support -- or even worse, no longer being updated by Google -- apparently were a bit premature. Dan Morrill has posted the following to the Android Contributors Google Group:
Hello! This is a quick clarification about support for CDMA devices.For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called "platform" key. However, when an individual creates a custom build from the AOSP source code, they don't use the same signing key as these CDMA flies were signed with. [...]
He goes on to note that the AOSP documentation was simply updated to reflect this fact, and that they will continue to provide as much of the closed-source material as they can.
So what does that mean? Signing keys are tricky things. When we build Android from the available AOSP source, we use a specific set of keys to digitally sign all the binaries. When "official" builds are made by Google or manufacturers, they use a different set of keys. When these keys are mismatched, things can get wonky. Google doesn't want your phone (or tablet) to be wonky. The fellow who built that custom ROM you're using doesn't want things to be wonky. If these changes weren't made and brought to everyone's attention, wonkiness would have resulted, and nobody would have known why without a lot of digging around.
Verizon Galaxy Nexus devices are still Nexus devices. They still have unlockable bootloaders. They still have the Android source available. They just have changed the way they redistribute binaries, because of incompatibilities with the signing keys.
Android developers will just have to change the way they build for the Toro (Verizon Galaxy Nexus), the Stingray (the LTE Xoom), and the Crespo 4G (Nexus S 4G). The sky has not fallen, and they'll figure it out. 
No comments:
Post a Comment