Does latest version support services.jar/odex in Donut-Ion builds? about smali

[JesusFreke]

Comment #1 originally posted by JesusFreke on 2010-01-27T02:54:27.000Z:

When you deodex a framework odex, you also have to deodex everything that depends
on that odex. First, check the contents of the BOOTCLASSPATH environment variable (on
the phone). On my phone (and likely yours), it is:

/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

The later jars depend on the earlier jars. So in this case, since services.jar is the
last entry in the list, you wouldn't have to deodex any of the other 5 jars mentioned
here. BUT, every other jar and apk on the phone will depend on all 6 of these jar
files, so you do have to deodex everything else - all jars and apks in
/system/framework and /system/app - except for the 5 jars that are before it in the
BOOTCLASSPATH.

[JesusFreke]

Comment #2 originally posted by JesusFreke on 2010-01-27T02:59:23.000Z:

Sorry, I had miscounted the jars in the BOOTCLASSPATH. so s/5/4/g and s/6/5/g :)

[JesusFreke]

Comment #3 originally posted by JesusFreke on 2010-01-27T02:59:44.000Z:

<empty>

[JesusFreke]

Comment #4 originally posted by JesusFreke on 2010-01-27T03:15:06.000Z:

Okay thanks.

my /apps directory contains no odex files but as mentioned my /framework directory
contains mostly odex files.

So If I use the same method I used for my services.jar (on all of the other files in
/framework) I should be good?

Thanks again.

[JesusFreke]

Comment #5 originally posted by JesusFreke on 2010-01-27T03:18:35.000Z:

Like I said, you need to deodex everything except the other 4 jars in the
BOOTCLASSPATH :). But it won't hurt to deodex them, while you're at it.

If it still doesn't work, reply back and we can discuss it some more :)

Also: feel free to ping me in #smali on freenode :)