answered
2019-04-30 07:25:22 +0300
I think there might be something we can do, though I am not sure of the long term effects. If you edit the build.prop
you can change the following values:
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
I set the limit to 512, and the size to 768 myself in an attempt to make Azur Lane run smoother, and it seems to definitely have some effect I think (although it may just be placebo, I doubt it). If I understand correctly, these values should be low-ish for multitasking (more apps that don't do much themselves) and higher for games).
To change them, you'll have to copy the /opt/alien/system.img
to a computer, then run unsquashfs system.img
as root, edit the squashfs-root/system/build.prop
file, then re-create the image with mksquashfs /path/to/squashfs-root system.img.new -comp lz4 -Xhc -noappend -no-exports -no-duplicates -no-fragments
. Then just replace the old system.img with the new one you just made (make sure to back up the old one!).
Personally I would just set them as high as possible, but lower then the max available memory (SFOS itself also needs resources as do native apps). Also, the normal limit applies to 'normal' apps while the overall heap size limit applies to 'big apps' if I understand this correctly. Games _should_ use the normal heap size.
I have only just started messing around with these values, so I am not sure what the best values are. I think I will try 1537 for the heapsize next....
EDIT: Values over 1GB prevented aliendalvik.service from starting. In the end I used 256 for the limit and 896 for the size, and that seems to work somewhat well.
Mine doesn't even start due to hitting a 256MB limit, so any info on this would be very welcome.
attah ( 2019-02-07 23:11:37 +0300 )editI think this issue is due to the non-optimization of aliendalvik. I think they're going to make it more robust in the future updates
Sakke ( 2019-02-08 11:26:22 +0300 )edithopefully, this is essentiell
Bavarian ( 2019-02-08 21:10:03 +0300 )edit@Sakke What you mean with non-optimization of aliendalvik?
"I think they're going to make it more robust in the future updates"
If "they" means the Jolla Sailors and "future" means during the lifetime of XA2, please share your method to get so optimistic! :-D
1984 ( 2019-02-08 21:14:51 +0300 )editI don't experience this with Photoshop/Lightroom for instance. Do you have a Google account added on your XA2? (not in dalvik)
Bundyo ( 2019-02-09 11:41:23 +0300 )editI do, yes, so i tried with disabling it and there was a difference, but in the end the result was very similar.
attah ( 2019-02-09 11:49:13 +0300 )editDisabling doesn't work - you'll have to delete it. My dalvik was unusable - huge memory leak and crashed every 2 minutes. After deleting my Google account from the phone - dalvik flies and no problems in sight.
Bundyo ( 2019-02-09 13:33:29 +0300 )edit