Android-based systems are new territory for me. What are the potential compliance requirements for customizing an Android platform with seemingly good compliance status?
1. Hardware and core OS functions would not change. 2. User interface would be customized and a few end user applications pre-loaded which are not part of the OEM factory image. Would there be issues with an additional branding label along the lines of "Widget ABCD powered by XYZ" where XYZ is the platform manufacturer which maintains compliance records. The platform manufacturer's product label wouldn't change and they are agreeable to such additional branding labels, but does the "powerd by XYZ" language affect compliance requirements (Multiple Listee?). Any recommended exploratory testing or required testing based on the new applications and user interface changes? Applications should not have ability to modify low-level functions (memory bus speeds, etc.) - the expectation is that the OEM design remains unchanged, so I/O interfaces (LAN, video, USB, etc.) operate per the OEM's documentation. I've started looking at Android Developer materials but haven't come across compliance-related documentation that I believe are due to Android's HAL architecture for supporting a diverse range of hardware platforms. Searching Android Developer resources with terms such as "compliance," "regulatory," "safety," and so on yields information similar to Windows driver compliance for compatibility requirements and one automobile driving-related "regulations" statement which doesn't apply: https://source.android.com/compatibility/8.1/android-8.1-cdd I would appreciate feedback and/or pointers to reference materials. Cheers, Adam in Atlanta [email protected] - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
