Thank you for the inputs. On Thu, Sep 1, 2011 at 12:28 AM, freakingtux <[email protected]>wrote:
> Hello, > > > > On Wednesday, August 31, 2011 2:46:36 AM UTC+2, Pratik Prajapati wrote: >> >> Hi, >> >> For production of the device, android APKs needs to be signed. I have >> created keystore as explained in http://developer.android.com/** >> guide/publishing/app-signing.**html<http://developer.android.com/guide/publishing/app-signing.html>and >> signed my APKs with that keystore. >> >> I am doing it for eclair. >> >> I need to know following things. >> >> (1) Do I need to sign the andoird framework build as well, apart from APKs >> that I'll provide in my production device? the older guidelines say it. >> http://www.kandroid.org/**online-pdk/guide/release_keys.**html<http://www.kandroid.org/online-pdk/guide/release_keys.html> >> > I don't know the glory details yet but I think I can say the following. If > you plan on releasing a device you should really replace the default > certificates with newly generated one and create a release build. The guide > you followed is intended for application developers and does not describe > the procedure to create a new device. > > Look in build/target/product/security it contains the keys used for signing > the platform packages and README describing how to regenerate new keys. > Using a strong password on the key store is certainly advisable > > Greetings > -- Kind Regards, Pratik Prajapati -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
