Openness > Open source
Merely providing source of the OS doesn't make the phone an open phone. The more important issue is total control to customers over what really runs on the phone - not just at application level or source code level, but at machine code level and OS level. For this level of control, you need to have
1. A mechanism for booting the phone with whatever kernel (not just Linux) you want it to boot.
2. Programming documentation of the hardware used by the phone down to machine level.
SDK for development and source code of the OS are insufficient substitutes for machine-level documentation. There is no assurance whatsoever from google that the android phone will be 100% documented.
Only open documentation can prevent vendor lock-in and ensure fair competition between OSs. Not open source. What's the use of the source-code when there is no exhaustive programming documentation? Your freedom to tinker with the source-code will be limited to a few areas which don't require hardware documentation.
But google says it will be 100% opensource when released
1. A mechanism for booting the phone with whatever kernel (not just Linux) you want it to boot.
2. Programming documentation of the hardware used by the phone down to machine level.
SDK for development and source code of the OS are insufficient substitutes for machine-level documentation. There is no assurance whatsoever from google that the android phone will be 100% documented.
Only open documentation can prevent vendor lock-in and ensure fair competition between OSs. Not open source. What's the use of the source-code when there is no exhaustive programming documentation? Your freedom to tinker with the source-code will be limited to a few areas which don't require hardware documentation.
Comment