Linked by Thom Holwerda on Sun 16th Sep 2012 16:53 UTC
Permalink for comment 535468
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2005-11-10
That, compatibibility layers, is another story. Even Microsoft does not try to prevent e.g. Linux-Distributions or OSX to offer compatibility with Wine, Samba, etc.
The point is more that if you are going to offer a forked Android (and to get this right: all Androids are forks cause they are taken+extended with own stuff and noone ships an Android vanilla) AND if you are member in the OHA and agreed to the compatibility goal then you need to make sure your fork is compatible.
It just does not matter how much extra-things you put in your fork, how much you changed as long as certain criterias are fullfit. Two of them Aliyun failed:
1. Pass the Android compatibility test-suite.
2. Open the sources of your endproduct so all extensions, modifications, drivers are available to all others just like the Android Vanilla (and all the forks of other OHA mabufactors) are too.
All that is assuming Aliyun OS is built on Android. They claim it isn't and just has an Android run time.