I have no way of knowing customer environment settings at apk build time so SharedPreferences as you described is out. If the customer (possibly with an accompanying utility) could unzip the apk, adjust the settings file, and then deploy it, but I ran into signing issues with both raw resources and directly reading the apk as a zip.
On Aug 3, 8:42 am, TreKing <treking...@gmail.com> wrote: > On Mon, Aug 2, 2010 at 9:28 AM, droidbm <droi...@gmail.com> wrote: > > *Raw Resource: If I unzip the apk and change the settings file, it becomes > > invalid as I need to resign the apk. > > Why are you unzipping the APK to change the settings file? > You can have several raw resources, one for each configuration, and on first > run read the one that's appropriate and use it to set up your app, applying > the settings to, say, a SharedPreferences object. Done. What's the problem? > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
