How do I change To dexopt in data/dalvik-cache instead of cache/dalvik-cache. I'm porting a rom and it chooses cache/dalvik-cache to dexopt so it won't boot. Also if I add cache dalvic . Internal memory becomes full and cannot write anymore.
hi i have lg g pro lite wiith android 4.4.3, in developer options i don't have a runtime option.
So i have tried to change it manually, i modified /data/property/persist.sys.dalvik.vm.lib and to build.prop i add this:
Code:
persist.sys.dalvik.vm.lib=libart.so
dalvik.vm.dexopt-data-only=1
After that i reboot my device, it take more than usually but dalvik cache is still exists....so i have a trouble....after reboot the /data/property/persist.sys.dalvik.vm.lib file contains again libdvm.so...?!?
Anyone can help me?
Port Dot os 1.2 karatep+hyper n upstream kernel+fix cam+fix audio rom=7.1.2
First from advanced cleaning system+ data +dalvik cache +cache+internal Storgae
Picture= https://i.hizliresim.com/9ada3r.png
sonra rom+hypern kernel
Picture= https://i.hizliresim.com/MVvVb2.png
missing contexts as you see in the picture after
Please check as the picture will be complete click
flash fix cam
then check the contexts again like in the picture complete click
flash audio fix
then flash the gaaps
root with optional magisk
Preview
https://i.hizliresim.com/XMXME3.png
https://i.hizliresim.com/5aQaGz.png
https://i.hizliresim.com/dvGv7D.png
https://i.hizliresim.com/bVGVLZ.png
https://i.hizliresim.com/ADkDyv.png
https://i.hizliresim.com/0RBRGZ.png
I need to disable the scroll cache, but I lose a lot of performance on android, I did some research and they said that this can cause performance delay due to GC, is there any way to solve this? or is there another method to disable without losing performance?
Obs: I do the deactivation with the following command "persist.sys.scrollingcache=4 ( or 3, the 2 lose performance )
Wondering what sense it makes to disable Android's scroll cache ( basically a drawing cache - a bitmap ) because using a drawing cache makes an animation smooth compared to redrawing the view at every frame?
BTW:
persist.sys.scrollingcache=1 -> cache on always
persist.sys.scrollingcache=2 -> cache on certain times
persist.sys.scrollingcache=3 -> cache off certain times
persist.sys.scrollingcache=4 -> cache off always
Good day , I have a general question about these and hope someone could explain me what exactly happens there:
So , I played around with some props values ( also looked a bit into the aosp code / dev docu ) and set these values with magisk as system.prop
dalvik.vm.isa.arm64.features=Default
dalvik.vm.isa.arm.variant=cortex-a76
dalvik.vm.isa.arm.features=Default
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.5
dalvik.vm.heapminfree=8m
dalvik.vm.heapmaxfree=32m
dalvik.vm.dex2oat64.enabled=True
dalvik.vm.dex2oat-flags=--debuggable
dalvik.vm.dex2oat-filter=everything
dalvik.vm.image-dex2oat-flags=--debuggable
dalvik.vm.image-dex2oat-filter=everything
dalvik.vm.dex2oat-Xms=16m
dalvik.vm.dex2oat-Xmx=512m
persist.dalvik.vm.dex2oat-threads=8
dalvik.vm.dex2oat-threads=8
dalvik.vm.image-dex2oat-threads=8
dalvik.vm.boot-dex2oat-threads=8
dalvik.vm.jitmaxsize=128m
#extrem values ! Default would be 10000
dalvik.vm.jitthreshold=2500
dalvik.vm.jittransitionweight=333
dalvik.vm.jitprithreadweight=333
pm.dexopt.install=speed
pm.dexopt.bg-dexopt=speed
Note here that I used first dalvik.vm.dex2oat-Xmx=256m instead of 512m , after a Dalvik clean up and rebuild I had 248m of Dalvik cache , no noticable performance impacts etc , I though It would be better to raise the value. In the same reboot process to enable the changes I also did an update , now my Dalvik cache is empty and can't be rebuilt , the interesting part is that my system is now quicker ? Especially in games I can notice a significant boost in startup time and menu transitions , but firefox (the only app atm) doesn't like this but can be used normaly after 3 "crashes-to-launcher"
Side Note: I don't need answers how to repair anything , I'm curious what's going on
So my questions is first how can it be faster if it presumably uses the default java JiT in memory instead of creating Dalvik cache + odex files
And what happend that Dalvik etc can't be normaly initiated ? Does it not like the settings and simply crash , or is this the right behavior for my settings and I have simply no idea what I'm doing ?
Thank you for reading and any helpfull response
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
jwoegerbauer said:
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
Click to expand...
Click to collapse
Right it would probably good to know my setup , I use the Mi 9T with Miui 12.3 on android 11 , ram is 6gb , cpu/gpu is SDM730
Thank you for the first clarification , so does this mean the JiT is on newer OSs ineffektiv ? Or just a backup technique