Hi AppCoder, Thanks for the response. That worked well.
I was going to try to another approach primarily for learning, to sign the app with the system certificate (after the build is done from Eclipse) and also specify the signatureOrSystem permission. GL. On Aug 3, 7:53 am, AppCoder <[email protected]> wrote: > Give your developers a rom that has /system/app write enabled > (or a way to remount it write enabled) and have them use > adb push to put the .apk on the ROM. > > Note if they use their own native libraries (jni) they will > need to be able to write /system/lib (or some lib that the > dynamic linker finds) and do adb push of the .so to /system/lib > as well. > > On Aug 2, 10:24 pm, GL <[email protected]> wrote: > > > > > > > > > We are building a device, therefore, we build the entire ROM image > > here and all the APKs included in the ROM image get the system flag > > and therefore additional privileges. However, we find that developing > > (compiling/downloading) with Eclipse is quite efficient. That way our > > developers don't have to rebuild the entire ROM image while debugging > > an app. That said, Eclipse downloaded APKs don't get the system app > > privileges and we need that privilege for some of our apps. What is > > the best way to work around this issue? > > > Thank you, > > > GL. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
