Is it intended that low level access to Surface Flinger is granted only to components that a part of the system and not to applications developed using the SDK and signed using an arbitrary certificate?
Is it the intention that an Android platform be signed with a certificate unique to an android provider, who if they wished could enable applications to be signed by the same certificate. When an android system is built - where is the certificate that is used for signing the system and does it need to be generated in a particular way (e.g. does it need to be generated by some signing authority). Presumably applications that connect up to surface flinger are routed through something that has the requisite permission. (Or is it that apps in general do not use low-level access?). --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
