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
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
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.
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.
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
5 matches
Mail list logo
