issue deodexing uiautomator.odex (android 4.1.1)

[GoogleCodeExporter]

What seems to be the problem?
Can't deodex uiautomator.odex

What is the exact smali/baksmali command that you ran?
java -Xmx1024m -jar baksmali.jar -a 16 -d bootclassdir -x uiautomator.odex
also tried passing the BOOTCLASSPATH but without success.

What version of smali/baksmali are you using? What rom are you working from?
-baksmali 1.3.3
-Samsung Galaxy Nexus stock ROM Android 4.1.1 (build JRO03C)

What is the airspeed velocity of an unladen swallow?
11 meters per second, or 24 miles per hour? :D

Log attached.
Thanks!

Original issue reported on code.google.com by rygel...@gmail.com on 13 Jul 2012 at 11:40

Attachments:

• log.txt

[GoogleCodeExporter]

You need to add the junit jar to the classpath

-c :core-junit.jar

Original comment by jesusfreke@jesusfreke.com on 14 Jul 2012 at 1:35

• Changed state: Done

[GoogleCodeExporter]

as I wrote I already tried to do that.

with: -c :core-junit.jar

and also with the BOOTCLASSPATH: -c 
:core.jar:core-junit.jar:bouncycastle.jar:ext.jar:framework.jar:android.policy.j
ar:services.jar:apache-xml.jar

Original comment by rygel...@gmail.com on 14 Jul 2012 at 5:25

[GoogleCodeExporter]

FYI, I just compiled v1.3.4-dev taken from git and now works fine.
something is broken in v1.3.3.

Original comment by rygel...@gmail.com on 15 Jul 2012 at 1:40

[GoogleCodeExporter]

Well, you didn't mention *what* classpath you used originally :)

In any case, I was going to suggest you try 1.3.4. I don't think 1.3.3 is 
broken, but deodexing will be greatly simplified in the next version (you 
shouldn't ever have to specify a manual classpath for deodexing)

Original comment by jesusfreke@jesusfreke.com on 15 Jul 2012 at 8:23