Havoc 4.x is not beta for long time. Latest is 4.4 or 4.3 depends from device...However some device might be drop out from further development...Check it for Havoc-OS website or Telegram group for latest version for your device.I'm still on 3.12 due to havoc os 4 being labeled as beta still.
Anyway I just tested tested out some different values for dalvik vm in build.prop
These are the current AOSP defaults for devices with 6gb of RAM
Havoc OS uses:
dalvik.vm.heaptargetutilization 0.75 dalvik.vm.heapminfree 4m dalvik.vm.heapmaxfree 8m
dalvik.vm.heaptargetutilization 0.5 dalvik.vm.heapminfree 8m dalvik.vm.heapmaxfree 32m
the other 3 values are the same
of course there are Oneplus 3 devices with less RAM, but my 3T has 6GB RAM so I gave them a test and I feel like they improved performance on my device
My guess why they improve performance:
it might not be as efficient since the heap can be up to 50% larger than necessary but the vm doesn't have to increase/decrease heap size as often.
Also the VM doesn't have to free RAM as often to have exactly 4-8m free.
Other ROMs have 2-8m or 8-16m but there is more memory to play with than just 4m
heapminfree/heapmaxfree is used to avoid kernel calls afaik and therefore delay (reduce latency).
Values for havoc OS in the github repo seem to differ again, but in a different way:
I would prefer 16m heapstartsize still
android_device_oneplus_oneplus3/device.mk at 662d12f7f7f0e81b8244945761807ed5e27c7c66 · Havoc-Devices/android_device_oneplus_oneplus3Contribute to Havoc-Devices/android_device_oneplus_oneplus3 development by creating an account on GitHub.github.com