core.jar (core-pj.jar) patch support about dexpatcher-tool HOT 7 CLOSED

whatever version of android you are using might do a native compile on a maintenance schedule and maybe when charging, so you may need to wait for 2 days while charging at night. but there are also commands you can issue to force an optimize. i don't know much about android, especially recent ones; google and test. thanks!

from dexpatcher-tool.

from dexpatcher-tool.

haystack/patch-fileset:

    if [ "$name" == "core.jar" ] || [ "$name" == "core-libart.jar" ]; then
        error "patching core jars not yet supported by these scripts"
    fi

is what I was looking at. Just realized that I posted in the wrong repo, my apologies.

from dexpatcher-tool.

from dexpatcher-tool.

Haystack works splendidly on Oreo, ODEXed even. I only had to deodex my services.jar and then delete /system/framework/oat/arm64/services.odex
I tried to do the same for core-oj.jar, but it was a lot different:

• no files under /system/framework/oat/arm64, but rather under /system/framework/arm64
• no odex+vdex file, but rather boot-core-oj.oat, boot-core-oj.art and boot-core-oj.vdex (note the prefix)

I managed to deodex the jar using SmaliEx, but after replacing the original and deleting those 3 files under /system/framework/arm64, my phone doesn't boot...

I originally want to patch core.jar, but it seems like it is split in two files in Oreo, thus my attempts to patch core-oj.jar.

Any ideas how I could overcome this? Thank you!

from dexpatcher-tool.

Haystack works splendidly on Oreo

i've heard, but it is unsupported.

I only had to deodex my services.jar
I tried to do the same for core-oj.jar

nope!!! optimizing (odexing, quickening, compiling, whatever you wanna call it) is a global operation. you can't deodex and modify a single file! if you mod services.jar, you need to deodex everything that might depend on it (it will be odexed again on runtime) -ie, the complete android framework-, and reoptimize any apps you might have installed;

from dexpatcher-tool.

It now makes sense why there's a boot.oat file and a bunch of optimized files prefixed with boot-. I deodexed the whole framework and the ROM ran, indeed. Thanks so much for the explanations!
My last question is why is everything so utterly slow? Even after using the phone for an hour, performance is still far from the pre-optimized state. I do not recall such drastic performance issues when running a deodexed ROM.
Thanks!

from dexpatcher-tool.