On Jul 28, 2016 09:15, "peter enderborg" <[email protected]> wrote: > > What is the point with that?
You could always wrap they aosp never allows in userdebug or eng macros, and be OK with respect to CTS. However, doing so increases the delta between user builds and other variants, which may include breakages that should work when the build flavor is user. Not all engineers at some Android shops test on user builds frequently. For userdebug conflicts on neverallows the guidance I've gotten and advised others is to just use a permissive build, which isn't necessarily the best answer either, as it requires extra steps to either produce the permissive image, or to change the shell into a permissive domain, or modify the kernel command line via a boot shell. > > _______________________________________________ > Seandroid-list mailing list > [email protected] > To unsubscribe, send email to [email protected]. > To get help, send an email containing "help" to [email protected].
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
