FORUMS

XDA Picks: Best Apps of the Week (June 27 – July 4)

Apps are at the front and center of any smartphone experience, and with over a … more

HTC One M9 Developer Edition Android 5.1 OTA

The Developer Edition of the HTC One M9 is receiving an over-the-air update to Android 5.1. … more

Index Project For XDA Device Subforums

Another ambitious project from the collaborative efforts of Recognized Contributors and Forum … more

The Atlas of XDA

A few weeks ago, we asked you “How Does Your Location Affect Your Life As A Power User?”. In the days that … more

Need development help: DexOpt mismatch signature

659 posts
Thanks Meter: 726
 
By shaftenberg, Senior Member on 11th February 2014, 04:00 AM
Post Reply Subscribe to Thread Email Thread
13th February 2014, 08:54 PM |#11  
Q9Nap's Avatar
Senior Member
Thanks Meter: 872
 
Donate to Me
More
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
 
More
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
 
More
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