[android-developers] Re: Dalvik and BOOTCLASSPATH
Ahh, I see. Thanks for the heads up on that documentation. I had looked at the dexopt source and it looked like that libraries in the boot class path were restricted to being in dependency order... so that basically shoots down my idea of overriding class loading. On Nov 16, 10:26 pm, fadden [EMAIL PROTECTED] wrote: On Nov 14, 1:37 pm, Koush [EMAIL PROTECTED] wrote: From adb shell on the emulator, I am prepend theBOOTCLASSPATHto include a jar that contains an implementation of android.widget.EditText. This won't work. Generally speaking, it's not a good idea to try to change the bootstrap class path. For a full explanation, see dalvik/docs/dexopt.html in the open source tree. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Dalvik and BOOTCLASSPATH
Also, I've tried just pushing a vanilla framework.jar and framework- apk.jar (as built from the source) to the emulator. This didn't work at first. I found that it was looking for EGLImpl, and then pushed lib/ libandroid_runtime.so to the phone to fix it, and though it worked, most of the applications would continue crashing? Any reason that updating all or any of the files on the emulator would keep it from running properly? I've also tried running the emulator off the resultant system.img, but that image is doesn't seem to have internet access. On Nov 16, 10:26 pm, fadden [EMAIL PROTECTED] wrote: On Nov 14, 1:37 pm, Koush [EMAIL PROTECTED] wrote: From adb shell on the emulator, I am prepend theBOOTCLASSPATHto include a jar that contains an implementation of android.widget.EditText. This won't work. Generally speaking, it's not a good idea to try to change the bootstrap class path. For a full explanation, see dalvik/docs/dexopt.html in the open source tree. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Dalvik and BOOTCLASSPATH
The issue of internet access on the emulator built from the open-source tree was resolved a while back, but you need to do a clean build and wipe data for it to stick. JBQ PS: this discussion is falling on the side where it should probably continue on one of the open-source lists (e.g. android-framework) instead of using an SDK list. On Tue, Nov 25, 2008 at 11:48 AM, Koush [EMAIL PROTECTED] wrote: Also, I've tried just pushing a vanilla framework.jar and framework- apk.jar (as built from the source) to the emulator. This didn't work at first. I found that it was looking for EGLImpl, and then pushed lib/ libandroid_runtime.so to the phone to fix it, and though it worked, most of the applications would continue crashing? Any reason that updating all or any of the files on the emulator would keep it from running properly? I've also tried running the emulator off the resultant system.img, but that image is doesn't seem to have internet access. On Nov 16, 10:26 pm, fadden [EMAIL PROTECTED] wrote: On Nov 14, 1:37 pm, Koush [EMAIL PROTECTED] wrote: From adb shell on the emulator, I am prepend theBOOTCLASSPATHto include a jar that contains an implementation of android.widget.EditText. This won't work. Generally speaking, it's not a good idea to try to change the bootstrap class path. For a full explanation, see dalvik/docs/dexopt.html in the open source tree. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Dalvik and BOOTCLASSPATH
On Nov 14, 1:37 pm, Koush [EMAIL PROTECTED] wrote: From adb shell on the emulator, I am prepend the BOOTCLASSPATH to include a jar that contains an implementation of android.widget.EditText. This won't work. Generally speaking, it's not a good idea to try to change the bootstrap class path. For a full explanation, see dalvik/docs/dexopt.html in the open source tree. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Dalvik and BOOTCLASSPATH
I don't know about the BOOTCLASSPATH, but did actually run the jar through dx --dex etc? On Nov 14, 1:37 pm, Koush [EMAIL PROTECTED] wrote: From adb shell on the emulator, I am prepend the BOOTCLASSPATH to include a jar that contains an implementation of android.widget.EditText. Then from ADB, I launch an activity using the am tool. However, am is failing to launch at all with the following errors in logcat. Any ideas on how to successfully tweak the BOOTCLASSPATH in Dalvik/Android? D/AndroidRuntime( 186): AndroidRuntime START D/AndroidRuntime( 186): CheckJNI is ON W/dalvikvm( 186): DexOpt: incorrect opt magic number (0xff ff ff ff) D/dalvikvm( 186): Stale deps in cache file; removing and retrying D/dalvikvm( 186): DexOpt: --- BEGIN 'koushikdutta.testboot.jar' (bootstrap=1) - -- E/dalvikvm( 187): Too many exceptions during init (failed on 'Ljava/ lang/NoClas sDefFoundError;' 'java.lang.NoClassDefFoundError') E/dalvikvm( 187): VM aborting I/DEBUG ( 21): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** * --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
