yashsingh1/xdaforums huggingface dataset:
[Magisk] rignfool:
Hmm...

Ok... Let's dig deep...

We will try to avoid a data wipe... But I think your game data is corrupt...

Reflash your boot.img... and double-check with twrp file manager that /data/dalvik-cache is totally empty or does not exist... And try to run your game

Also... Too lazy to look back... Which game is it?

---------- Post added at 07:38 AM ---------- Previous post was at 07:38 AM ----------

TRAITOR!

?
[Magisk] veez21:
:D:D

SuperSU all the way... (ﾉ･ω･)ﾉﾞ
[Magisk] :
Idolm@ster starlight stage, my game data runs fine after restoring though. Don't bother anyway, I gave up on this module. No sense squeezing my brains out about this.
[Magisk] infernus38:
Bug - after setting any compiler filter and rebooting dalvik-cache did not fully generating, just with 0-byte files. Android is starting, but shows "internal storage running out" message (over 4 gigs are free in /system and /data), apps are starting but cant install any new app.

Disabling module and wiping dalvik didnt do anything with that:\
[Magisk] veez21:
Try deleting the files in /data/property/ and then wipe dalvik-cache
[Magisk] infernus38:
Same, dalvik-cache generetes just 0-byte files, deleting module from magisk also wont help.

I forgot to mention rom - AOSP 5.02
[Magisk] veez21:
You have any important stuff in there? Try doing a clean rom install.
[Magisk] Sachiru:
Running this module on LineageOS 7.1 for the Zenfone 2 (x86) causes a bootloop. What's the best way to capture logs to submit to the author to help them fix this?
[Magisk] veez21:
First, try rebooting a couple of times after flashing...

If that doesn't work, try re-wiping dalvik-cache.

If that also doesn't work try uninstalling the module
[Magisk] Sachiru:
Thanks for the response, but wouldn't it be better if I am somehow able to capture logs and submit them for further analysis?
[Magisk] veez21:
I couldn't really do much on logs in this matter. The values of this module is very simple and the reason of the bootloop is pretty obvious. So looking for the most probable solution related to the changes made by this module will likely help you more with the problem ;)
[Magisk] ebrijesh:
Thanks.

Just one more question.

I have dirty flashed rom update yesterday.

Do I need to re apply all settings of module.

I checked on terminal emulator and it shown my last compiler setting before rom update.

Using magisk with RR on bacon.
[Magisk] veez21:
You don't have to reapply, the last update fixes that particular magisk limitation :cool:
[Magisk] Anonymus1725:
Can I FLash with FlashFire??

I have a S7 and I dont have a TWRP.

I have Xposed not Magisc
[Magisk] veez21:
You can flash it in flashfire, but this needs magisk. It won't work if you don't have it
[Magisk] ala_mo:
budum tss
[Magisk] veez21:
NON-MAGISK VERSION

Basically the same funtionality, but no UI and if you want to change the compiler filter, you need to edit the file (There are instructions in it ;))

How to use:

- just extract the .sh file inside and the put it either in /system/su.d, /su/su.d or /system/etc/init (not preferred)

- you can change the compiler filter by changing the value of filter variable by editing the file

## You can edit the 'filter' variable if you like ;)
## More information in the XDA thread
[B]filter=[/B]<compiler filter>
## More information in the XDA thread

- set permissions to 700 (rwx)

- then reboot to recovery and wipe dalvik-cache

Download
[Magisk] k2065183s:
After these steps,go to TWRP and wipe dalvik/art cache? Or just reboot?
[Magisk] veez21:
Oh yeah, forgot bout that...

You've to wipe dalvik-cache

Thanks :highfive:
[Magisk] k2065183s:
Thank you for reply.

I've just done,but I have no idea it's working or not...

I am using S7 with Towchwiz&Facebook Messenger.

After wipe&reboot,everything is fine,no problems.

Is there any way to know the optimization is taking effect or not?

Sorry for my bad English.
[Magisk] veez21:
try doing this command​ in terminal emulator:

getprop | grep dalvik

and see if it lists the build props on the OP ;)

If it does then it's working ?
[Magisk] k2065183s:
Screen shot attached.

Not every props on the OP showed here.

Is it working?
[Magisk] veez21:
Sorry, I actually made a mistake. Fix coming up soon

EDIT:

Fixed, pls check this out

https://xdaforums.com/showpost.php?p=72184915&postcount=239
[Magisk] k2065183s:
Screen shot attached.

It seems that it's working right?

Thank you very much.
[Magisk] KaMyKaSii:
Thanks, I'm still going to test this but I have a question. I think the "set_prop dalvik.vm.dex2oat-filter speed" part should be "set_prop dalvik.vm.dex2oat-filter $filter", or am I wrong?
[Magisk] veez21:
I don't know, the info I got says to only change the other one, you could try and tell me and then I'll add it if it goes well ?
[Magisk] realmin04:
Sorry for the late quote

Tried it, still didn't work: it hangs everytime i install this module with SuperSU...

i don't know why, maybe i'll try the non-magisk version then :confused:
[Magisk] justjr:
Sounds like a x64 conflict, what plataform is your phone? Go to magisk forum ask for support if the problem is with magisk, they'll be able to help you.

You can try non magisk if you want anyway.
[Magisk] realmin04:
it's arm64 mate.

this module is fine with magisksu but it won't get along with supersu unless i'm using a non-magisk of this module :confused:

by the way i'll try to ask later, need some sleep :highfive:
[Magisk] rex900:
just set in build prop
[Magisk] justjr:
I don't use, or see the need for supersu, so I can't help you there. And quite frankly, if your problem is with magisk and/or supersu you should ask on their forums.
[Magisk] veez21:
UPDATE TO v0.7.5!

Changelog:

added dalvik.vm.dex2oat-thread_count which will "supposedly" make app installation faster

Download here or at Magisk Manager ** install in recovery
[Magisk] justjr:
This is too much technical for me to know what this will change, hahaha, care to explain a little? TY.
[Magisk] veez21:
Not that much technical ;)

Just added a build property that will "supposedly" make app installation faster :good:
[Magisk] justjr:
It does apply and delete caches on it's own? Cause I restarted after updating thought magisk and android is optimizing apps. Didn't runned it on terminal.
[Magisk] veez21:
What do you mean? The options you saved in art_magisk? Also,, you need to install it in recovery to have it the same as you saved it :good:
[Magisk] realmin04:
0.7.5 zip not working, updater process ended with error: 1, maybe can you fix it? :confused:
[Magisk] justjr:
Lol, I also didn't get what you said, I always install it from magisk, I can't?

I mean I just updated it on magisk, restarted to recovery (flashed the new arise module) and it started to optimize apps on start, as if I had cleaned cache when I didn't.

On the getprop thread is marked as [4], and the option I had chosen before (speed).
[Magisk] veez21:
Try downloading zip from magisk manager and then flash in recovery
[Magisk] veez21:
Ok then :good:

Seems like there's no prob
[Magisk] realmin04:
thanks, that works ;)

recently i always encountered a "process error" for some reason i tried to dl modules

fixed it by restarting somehow :confused:
[Magisk] utjduo:
After installing this through Magisk I can not any longer open some apps, no root-apps at all and my phone freezes after a while. As I can't open Magisk as it's a root-app, how can I uninstall this module?
[Magisk] realmin04:
Uninstall and reinstall Magisk, and don't flash SuperSU, you have the same problem as me
[Magisk] Ubimo:
How can I measure this "Android Runtime Optimization" objectively?

SSD benchmark? Time it takes to install an app? Time it takes to open an app?

Edit:

I cannot flash 0.7.5 in TWRP. It says" Error installing the zip file... ERROR: 1"

I have a Samsung Galaxy S7 edge and use latest TWRP 3.1.0-1

I re-downloaded the file several times with several methodes (PC, phone, different browser) and several androidfilehost-mirror.
[Magisk] cafe-creme:
Already the optimization is visible with regard to the storage of the applications (300mo)

At startup there is a small gain faster, so do not expect 40 seconds either :)

A very good result and module in my case.
[Magisk] rignfool:
CleanMaster is never worth installing...

The malware it comes with slows your phone to a crawl... The task killer destroys battery... And it send all your info to servers in China...
[Magisk] cafe-creme:
Only China ? Damage ...

Connected = information anyway.

The subject is this module rather than SmartManager by Samsung :p
[Magisk] gps3dx:
I Install SuperSU as systemless ( i.e after Magisk was auto-installed by my rom) -> wiped Dalvik -> reboot.

system is loading file, but don't got root at all.

I don't understand how to uninstall thus ART_OPT module...

I Don't have /magisk folder at all under root while in TWRP.

which files should I wipe using TWRP ?

also, if this module CAN work with superSU ( systemless ) - what steps should I take ?

Is only the non-magisk version of ART_OPT works with SuperSU ( systemless ) ?
[Magisk] Didgeridoohan:
If you want SuperSU you'll need to flash that before installing Magisk. If your ROM comes prerooted with MagiskSU you'll first have to uninstall Magisk and start from scratch.

To uninstall a module from TWRP, flash the Mount Magisk script from the Collection of Magisk modules and the use the file manager to navigate to /magisk.
[Magisk] realmin04:
SuperSU first then Magisk

basically (if your arch is arm64) if you activate this module, it would make your device unresponsive, the non-magisk version of this mod or removing supersu for magisksu is your option...

Here's the hang bug (for me) :

--------- beginning of crash
[ 05-08 01:14:39.981 7837: 7837 F/libc ]
CANNOT LINK EXECUTABLE "/system/bin/dex2oat": "/system/lib64/libsigchain.so" is 64-bit instead of 32-bit

[ 05-08 01:14:39.981 7837: 7837 F/libc ]
Fatal signal 6 (SIGABRT), code -6 in tid 7837 (dex2oat)

[ 05-08 01:14:40.047 7839: 7839 F/DEBUG ]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
LineageOS Version: 'unknown'

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys'

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
Revision: '0'

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
ABI: 'arm'

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
pid: 7837, tid: 7837, name: dex2oat >>> /system/bin/dex2oat <<<

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
r0 00000000 r1 00001e9d r2 00000006 r3 00000008

[ 05-08 01:14:40.048 7839: 7839 F/DEBUG ]
r4 f776158c r5 00000006 r6 f7761534 r7 0000010c

[ 05-08 01:14:40.049 7839: 7839 F/DEBUG ]
r8 f76ef010 r9 f76ef18d sl 00000009 fp fffc35f8

[ 05-08 01:14:40.049 7839: 7839 F/DEBUG ]
ip 00000002 sp fffc3568 lr f7741bbb pc f7742604 cpsr 600f0010

[ 05-08 01:14:40.052 7839: 7839 F/DEBUG ]

backtrace:

[ 05-08 01:14:40.053 7839: 7839 F/DEBUG ]
#00 pc 0004a604 /system/bin/linker (__dl_tgkill+12)

[ 05-08 01:14:40.053 7839: 7839 F/DEBUG ]
#01 pc 00049bb7 /system/bin/linker (__dl_pthread_kill+34)

[ 05-08 01:14:40.053 7839: 7839 F/DEBUG ]
#02 pc 00041ff7 /system/bin/linker (__dl_raise+10)

[ 05-08 01:14:40.053 7839: 7839 F/DEBUG ]
#03 pc 00040abb /system/bin/linker (__dl___libc_android_abort+34)

[ 05-08 01:14:40.054 7839: 7839 F/DEBUG ]
#04 pc 0003f88c /system/bin/linker (__dl_abort+4)

[ 05-08 01:14:40.054 7839: 7839 F/DEBUG ]
#05 pc 00041acb /system/bin/linker (__dl___libc_fatal+22)

[ 05-08 01:14:40.054 7839: 7839 F/DEBUG ]
#06 pc 0000a0ed /system/bin/linker (__dl__ZL29__linker_init_post_relocationR19KernelArgumentBlockj+3336)

[ 05-08 01:14:40.054 7839: 7839 F/DEBUG ]
#07 pc 0000934d /system/bin/linker (__dl___linker_init+356)

[ 05-08 01:14:40.054 7839: 7839 F/DEBUG ]
#08 pc 00002960 /system/bin/linker (_start+4)
[Magisk] realmin04:
art optimization non-magisk version 0.7.5 (for those who wants it, not tested yet - only extract)

just trying to contribute :highfive:
[Magisk] justjr:
First, I will ask if SuperSU was working before installing this module

Then I have to say that this module have nothing to do with root, it only need modules part of magisk, not the root. You should ask on SuperSU forums about SuperSU​.

To see Magisk folder on TWRP you need to flash a module that will mount it for you, that you will find on Magisk forum, same place this topic is.

Enviado de meu MotoG3 usando Tapatalk
[Magisk] gps3dx:
Thank you both - I managed to wipe the module after rebooting my system, then magik folder appears.

I guess the same will happen with the "mount script" you told me.

Only in retrospect I noticed that my rom was already pre-configured with same 'speed' options as this module can set.

just for the record, yes, I has superSU working 100% OK before installing this module.

so after its installation ( & reboot-> dalvik wipe -> reboot to system .. ) no root was available at all, no matter which app request it.

Lastly, A question... did anyone perform benchmarks and compared the results of using various flags ?

What interest me the most is: 'speed' VS 'all' VS 'interpret-only' in terms of boot time ( with dalvik wiped prior to boot ) and typical app launch like google-play etc...

P.S - thanks for the assist.:o

---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------

only change VS orig script is:

set_prop dalvik.vm.dex2oat-thread_count=4

isn't that more device limited command ?

i.e AFAIK, it should be NOT good for old devices with less the 4 threads....

---------- Post added at 04:22 PM ---------- Previous post was at 04:14 PM ----------
[Magisk] arythion:
hello everyone!

I installed this app via recovery (after downloading via magisk and having errors in installation). I got terminal emulator, rebooted once, went back to recovery, wiped art/dalvik cache rebooted again- Seems quite fast, I am on Alxndr's rom for n910f (note 4). For some reason it broke xposed, since it shows as inactive. Both this module and xposed were installed systemless-ly with compatible modules. So now i tried uninstalling xposed, to reinstall later. rioght now it is optimizing apps again. after reinstalling xposed i might run this module on terminal again to apply the everythign filter and see if xposed breaks again.....

Does this make sense? or is there something i am not doing right?
[Magisk] Techie Android:
Trying today on my Oneplus One running Marshmallow and it's been putting me in a bootloop. I'm not sure I know how to remove it without being inside the OS. It also kept spitting out error 1 messages in TWRP before I just flashed from source. I need to know quick because this is my only phone and daily driver, I hope I don't have to clean wipe my phone to fix this. Thanks.

Correction: I am not even bootlooping, It's just displaying the bootloader image, it hasn't even started the bootanimation.

Still waiting on some info and help. Please let me know when you've fixed it.
[Magisk] veez21:
Mount Magisk in twrp and then delete /magisk/runtime-optimization folder
[Magisk] veez21:
Seems to have problems with xposed for others. Mine is completely fine :confused:

Anyways, you can just uninstall it if you really need xposed ;)
[Magisk] Shen Ron:
Version 0.7.5. Caused xposed framework to stop work.
[Magisk] veez21:
Well, I have an old device running magisk and is completely fine with it :good:
[Magisk] veez21:
QUICK FIX v0.7.5-fix

Fix for installation error when downloading from AFH.

(though I haven't tried it yet, but this should fix the error)

Download
[Magisk] realmin04:
first answer: ask the OP, idk :confused:

second: my device is Redmi Note 3, with custom ROM (RR 5.7.3).

it's definitely an architecture error for the script, who knows? :fingers-crossed:
[Magisk] veez21:
So, this only happens when supersu is used with magisk?

Since you've been pretty active in this thread, I assume you're using this with magisksu. So any issues with it?
[Magisk] k2065183s:
I've tried to set the "set_prop dalvik.vm.dex2oat-filter speed" part to "set_prop dalvik.vm.dex2oat-filter $filter" in the version 0.7.5.

And everything goes well,no problems.
[Magisk] Techie Android:
Is there anyway to uninstall it without having magisk already on the device after flashing it and it not being able to boot into the OS?

I'm familiar with all of TWRPs features is there a file or folder I can navigate to and edit or remove?
[Magisk] veez21:
Mount magisk in twrp, (should be here) then delete the folder /magisk/runtime-optimization
[Magisk] gps3dx:
[MENTION=7296895]veez21[/MENTION]...

I wonder... the magisk module's update-binary contains checks for 'ARCH' and 'IS64BIT' - but AFAIK, beside finding the right answer per device the module is installed on - you don't use these variables AT ALL to install whatever it is ( arch based installation ).

so why checking ARCH type at all ?

I think you forgot to implement arch-based installation in your update-binary, and I can only guess that currently the module supports only ARM, not ARM64/x86 etc..

that's why might [MENTION=6577007]realmin04[/MENTION] got this lib error throw in logcat.

is there any ARCH based specific action/bin/command switch involved with your module installation procedure ?
[Magisk] 24imelqui:
7.5 take longer time to boot than 7.0. It will stay at asus logo for about a minute before it will show RR N boot animation.
[Magisk] lenin1928:
HTC 10 Venom rom latest nougat , elemental x, with latest firmware. Installed this module and stalls at boot screen.
[Magisk] veez21:
I never really thought that this was a arch based property. Cause it's from google (nexus 6p and so on is arm64). Anyways, thanks for the conclusion. But I'll investigate on this issue more. If there's any issues with Magisksu or is it only with supersu
[Magisk] realmin04:
Nothing, if i use magisksu, but as soon as i flash supersu and magisk on a clean/fresh rom and enable this mod, my phone freezes within a minute or two... :confused:
[Magisk] justjr:
Try not to use SuperSU if you want this. All roms I tested, even stock, got no problems, never used SuperSU. Probably that's the problem from the looks of it, but it need deeper investigation.
[Magisk] ala_mo:
im on a arm64 device with supersu and magisk both installed this works just fine
[Magisk] rignfool:
Thought:

Maybe you should put up a warning about using OEM ROMs and this mod...

Specifically samsuck and their inability to leave ART alone
[Magisk] veez21:
Thanks for confirming, less weight in my shoulders :)

Okay, I'll add it ;)
[Magisk] asusm930:
I have this tweak applied via build.prop Running MIUI8 Android 6.0 Rooted via Systemless SuperSU (not using magisk) WITH XPOSED and its running fine at the moment.

what I did:

1. Edit build.prop file

2. Reboot to recovery and wipe dalvik cache and cache via TWRP

3. Reboot

One app did forceclose at 1st boot though but that app is running fine

I did set it to balanced though

I just need to confirm one thing; Does this make apps launch faster, on top supposedly faster dalvik/art cache build during 1st boot? Thanks
[Magisk] veez21:
Well, depends. Setting to balanced is good since it'll save you space and still retaining app performance
[Magisk] asusm930:
lets say i want to go full retard and i want to test the fastest setting (that speeds up app launch speed-honestly dont know if im making sense) the best setting to use would be everything right?

Thanks (and sorry if my questions sound dumb lol)
[Magisk] veez21:
Yes. When you try it tell me if there's something wrong with xposed with everything ;)
[Magisk] asusm930:
Aight I just set it to everything and now its building the art cache after wipe and reboot :good:

---------- Post added at 12:18 AM ---------- Previous post was at 12:12 AM ----------

GOAT DAMN!!!!!! WITH IT SET TO EVERYTHING APPS ARE CONSIDERABLY FASTER TO LAUNCH (TWITTER, INSTAGRAM, CHROME) AND IM RUNNING XPOSED, TOO

Thanks so MUCH OP

REDMI NOTE 4 MTK MIUI8 ANDROID 6.0 SYSTEMLESS SUPERSU XPOSED WITHOUT MAGISK
[Magisk] veez21:
Good man :good:

Seems that there's no prob with xposed :good:
[Magisk] justjr:
I've being using this module with xposed and stock rom for weeks. Just now changed to DU.
[Magisk] jmmigo:
Are you set to everything like this?
[Magisk] veez21:
No, there should be a like this

filter=speed

edit it after the "=" sign ;)
[Magisk] jmmigo:
One question again sir, I've read two words with "$filter". So, "$filter=speed"? Or must I delete "$" symbols? Sorry for noob questions. Thanks before
[Magisk] veez21:
No, you only have to edit this
[Magisk] jmmigo:
Thank you sir
[Magisk] veez21:
UPDATE TO v0.8!

** I ACTUALLY MADE A MISTAKE IN LOGGING AND SETTING A FEW PROPERTIES IN THIS VERSION. THAT PROBLEM SHOULD BE FIXED AFTER THIS EDIT HAS BEEN SAVED :o

REDOWNLOAD AS YOU READ THIS JUST TO BE SURE

Changelog:

added dalvik.vm.heaptargetutilization (another improvement, i'll not get into the details)

Added logging. You should see logs from this module in Magisk Manager

Download at the OP or Magisk Manager

Non-Magisk Download Link (instructions on how to install non-magisk version:

here
[Magisk] nan0s7:
Question. Would it be possible to have a different compiler filter for each app? Instead of or as well as having the global setting?
[Magisk] veez21:
No, unless you run dex2oat yourself
[Magisk] Ubimo:
How do I completely uninstall this? And undo settings.
[Magisk] veez21:
QUICK UPDATE/FIX TO v0.8.1!

QUICK UPDATE/FIX TO v0.8.2!

Logging and setting properties were messed up in v0.8

Update to v0.8.1 for the fix

Update to v0.8.2 to fix a few extra malfunctions

DOWNLOAD AT THE OP OR MAGISK MANAGER
[Magisk] k2065183s:
Even non-magisk version 0.8 should reinstall?
[Magisk] veez21:
Nope, non-magisk is okay :good:
[Magisk] jordirpz:
Hi, non-magisk version need update to 0.81, or 0.80 is good?

Thank you sir
[Magisk] veez21:
v0.8 non-magisk is good. No problems on that side :good:
[Magisk] edoardotavecchio:
With 0.8 and 0.8.2 my phone becomes unable to read SIM card :eek: which log do you need for it?

(P.s.: could someone upload the working zip for 0.7.5 version? that's the latest one working fine)
[Magisk] shadowstep:
Thanks for the update, [MENTION=7296895]veez21[/MENTION]! I like modifying my build.prop directly and just to confirm, please let me know if the following is what the module adds to build.prop at the moment:

dalvik.vm.image-dex2oat-filter=everything/speed/balanced/space/interpret-only/verify-none, user configurable
dalvik.vm.dex2oat-filter=speed
dalvik.vm.check-dex-sum=false
dalvik.vm.checkjni=false
dalvik.vm.execution-mode=int:jit
pm.dexopt.bg-dexopt=everything/speed/balanced/space/interpret-only/verify-none, user configurable
dalvik.vm.dex2oat-thread_count=4
dalvik.vm.dex2oat-swap=true for a low memory device, false otherwise
dalvik.vm.heaptargetutilization=0.75, if the value for the above^ is false or 0.9, if the value above^ is true

Thanks a lot!
[Magisk] veez21:
Yeah ?
[Magisk] edoardotavecchio:
this isn't working either ?
[Magisk] cafe-creme:
Copy this zip to your folder Magisk of course, otherwise it will not actually install in recovery !
[Magisk] edoardotavecchio:
oh, I didn't know that the location was an important part of the magisk module flashes. Thanks. Anyway, I've solved the problem. This module was interfering with AudioModLib from ahrion, so I deleted it and now everything works fine
[Magisk] veez21:
UPDATE TO v0.8.5!

You have to update in this version!

Changelog:

Code Optimizations

Moved dalvik.vm.heaptargetutilization to be used on Android 5.0+

Fixed logging

Download at Magisk Manager

No Update for Non-Magisk (no need in this version)

Uninstaller linked in the OP!
[Magisk] Shen Ron:
The previous versions of the 0.8 causes my phone to be stuck in bootloop just after the screen goes dark and about to enter the system ui which results in having to go back and uninstall magisk then reflash all the modules i saved including 0.7.5. I hope this version won cause the same thing g to happen
[Magisk] veez21:
try and tell me if it works