[android-porting] /vendor/manifest

[Harish N]

Hi All,

We have android platform Image and N number of products are derived from it
with different product specific features supported.
VTS test cases fails since we have single manifest entry for all features
but devices will not support all feature.

How to address this problem Runtime loading of manifest

[Satish Patel]

Post by Harish N
Hi All,
We have android platform Image and N number of products are derived from
it with different product specific features supported.
VTS test cases fails since we have single manifest entry for all features
but devices will not support all feature.

​generally structure to be followed as
device/<vendor>/product1
device/<vendor>/product2
etc...

The common to vendor specific can go to
vendor/<vendor>/common.mk
and product specific will go to /device/<vendor>/product1..N (in your case
product specific manifest.xml)

So each product can have separate build and separate product specific
configuration with common vendor features.

​

Post by Harish N
How to address this problem Runtime loading of manifest
--
--
website: http://groups.google.com/group/android-porting
---
You received this message because you are subscribed to the Google Groups
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

--
Regards,
satish patel

[Satish Patel]

Satish I can have multiple manifests for different products but I have
single build supporting N number of products with different hw support.how
should I go ahead.
Eg. One product support GPS one does not

​In that case one need to tweak vts tools code. But that is not recommended
as Android Team will not take compile VTS on tweak code, if product goes
for certification (if required)

For local validation you can explore tweaking of the code
http://androidxref.com/8.1.0_r33/xref/test/vts/utils/python/controllers/android_device.py

Or change vendor/manifest.xml or system/manifest.xml on target before
running vts tool
​

Post by Satish Patel

Post by Harish N
Hi All,
We have android platform Image and N number of products are derived from
it with different product specific features supported.
VTS test cases fails since we have single manifest entry for all
features but devices will not support all feature.

​generally structure to be followed as
device/<vendor>/product1
device/<vendor>/product2
etc...
The common to vendor specific can go to
vendor/<vendor>/common.mk
and product specific will go to /device/<vendor>/product1..N (in your
case product specific manifest.xml)
So each product can have separate build and separate product specific
configuration with common vendor features.
​

Post by Harish N
How to address this problem Runtime loading of manifest
--
--
website: http://groups.google.com/group/android-porting
---
You received this message because you are subscribed to the Google
Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.

--
Regards,
satish patel

--
Regards,
satish patel