Dianne or others, Can someone please point me to any existing documentation that explains steps like those mentioned in this thread needed for shipping an Android device?
1. sign userimage with vendor private keys 2. ensure ro.secure system property set 3. ensure no root consoles left running 4. ensure build phase for generating dexopt files into system image 5. Other? Thanks, Dan On Tue, Aug 11, 2009 at 7:30 PM, Dianne Hackborn <[email protected]>wrote: > When you are creating the user image for your device, you need to sign > everything with your own private keys that nobody else has access to. You > also need to make sure the ro.secure system property is set, and that the > build phase for generating the final dexopt files into the system image is > done (so dexopt doesn't need to be run at boot). > > This is the "mydevice-user" configuration. Generally development will > happen with "mydevice-eng" or "mydevice-userdebug", but the result of these > build configurations is not intended for shipping on a device. > > > On Tue, Aug 11, 2009 at 5:21 AM, cht <[email protected]> wrote: > >> >> The security keys under the directory android\build\target\product >> \security is used to sign the apk for defferent security level. do >> they need to generate some new keys of theirself or do not change it >> for some compatible problems? >> >> thank you >> >> cht >> > > > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > >
