OnePlus DR-1 Quadcopter Drone Available for Purchase

OnePlus has been teasing a new product for a while now, hailing it as a … more

KDZ of Android 5.0.1 Captured for T-Mobile LG G3

T-Mobile US is yet to release the 20B Lollipop build for the LG G3. Luckily enough, you … more

Build Custom Stock Kernel with Linaro GCC 4.9.1

With this guide for Sony devices, you will learn how to build a kernel using the Linaro … more

What’s Your Biggest Reason for Not Owning an iPhone?

With XDA being a community of Android enthusiasts, it is not uncommon to see … more
Post Reply Subscribe to Thread Email Thread

Need development help: DexOpt mismatch signature

13th February 2014, 08:54 PM |#11  
Q9Nap's Avatar
Senior Member
Thanks Meter: 666
 
644 posts
Join Date:Joined: Feb 2009
Donate to Me
Quote:
Originally Posted by shaftenberg

Whoa, this was very helpful indeed, that explains almost everything...
Just a side note: I didn't know that, so I deodexed my system the standard way and I don't have any FCs.

Modding framework-res.apk worked though, even with creating new arsc and dex.

[edit] sure it works. framework is already deodexed in stock systems.

yeah kinda crazy, just realized that late last night and redumped the system.img to be sure i wasn't tripping lol.
20th October 2014, 08:17 AM |#12  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2014
DEXOPT Invocation Test
Quote:
Originally Posted by shaftenberg

Hi there,
I deodexed stock 4.4.2 for XT1052 successfully and wanted to mod android.policy.jar for the skip music with volume button mod. I did this several times for Jelly Bean ROMs and even for the Nexus 5 running on KitKat 4.4.0

baksmali and smali the classes.dex works fine with no errors but after pushing the file to /system/framework I got stuck in a black screen.
Logcat says DexOpt: mismatch dep signature for android.policy.jar - I googled but didn't find a solution.

Any dev here who can help? Is this a 4.4.2 or even MotoX issue?

''ANY CHANGES TO THE DEVICE COULD RESULT IN UNDESIRABLE USE. AND MAY HAVE CONSEQUENCE. AND MAY VOID WARRANTY. USE IS USERS SOLE RESPONSIBILITY''
You may want to try a test of dexopt.
I came across something, (while surfing the web for midget love making) That you may find useful.. this will test and show you the dexopt conditions of your installation.
netmite.com/android/mydroid/build/tools/dexpreopt/dexopt-wrapper/DexOptWrapper.cpp

P.S. just a thought CmeL8r
Last edited by TERRY72763; 20th October 2014 at 08:25 AM. Reason: forgotten link. forget to wait 5 min...fnNoobs
20th October 2014, 10:17 PM |#13  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2014
DEXOPT mismatches...
environmental variables can be overridden with explicit assignment.
Then you can use command line makefile assignment:
$ make showcommands WITH_DEXPREOPT=false
ANY CHANGES TO THE DEVICE COULD VOID WARRANTY.
AND MAY CAUSE UNDESIRABLE CONSEQUENCE OF SYSTEM.
USE IS USERS SOLE DISCRETION, RESPONSIBILITY.
Hope this helps you to call up current files, with variables allocating instructions for device to, Stop Driving You CRAZY....
Just a thought CmeL8r
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes