OK, but what if the device is not present in the AOSP tree?
On Apr 8, 2015 9:28 AM, Rodney Dawes rodney.da...@canonical.com wrote:
Ports are based on AOSP, and not CM. You shouldn't use CM at all, but
AOSP, and the AOSP device support tree provided by the manufacturer.
On Wed, 2015-04-08 at
Ports are based on AOSP, and not CM. You shouldn't use CM at all, but
AOSP, and the AOSP device support tree provided by the manufacturer.
On Wed, 2015-04-08 at 13:04 +, Nkansah Rexford wrote:
I think that should be CM 11 because the porting requires android
4.4.2 and cm 11 is 4.4
Does
Hello,
For ports, based on CyanogenMod, which CyanogenMod version should be used?
Thanks,
Vladislav
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help :
I think that should be CM 11 because the porting requires android 4.4.2 and
cm 11 is 4.4
Does the '.2' at the end of 4.4.2 strictly matters for the porting to work?
Rexford
khophi.co
On Apr 8, 2015 1:00 PM, Vladislav Evgeniev v.evgen...@gmail.com wrote:
Hello,
For ports, based on CyanogenMod,
On miércoles 8 de abril de 2015 14h'20:01 ART, Vladislav Evgeniev wrote:
OK, but what if the device is not present in the AOSP tree?
You can use CM, just make sure the component api's match the ones from AOSP
so porting is not as complicated; e.g.; hybris is tied to specific android
source
5 matches
Mail list logo
