# Is there a way to boost the RAM for Android, aliendalvik?

asked 2019-02-07 22:41:53 +0300

Seems the limt of RAM for Aliendalvik is still something around 500 MB.

With JP 1 I didn't complain, but with the XA2 it's very painfull.

Especially the young future SFOS user are hard to convince to change their OS when they have a look in the native App-stores. They start to get really interested when I mention the Android support. But open several or RAM-intense Android apps (Photo-/Videoeditors, games, etc.) makes flickering or slow impressions and the feeling of going backwards 5 years ago. :(

Is there a way to get rid of that limit? Why is it there anyway?

edit retag close delete

## Comments

Mine doesn't even start due to hitting a 256MB limit, so any info on this would be very welcome.

( 2019-02-07 23:11:37 +0300 )edit

I 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

( 2019-02-08 11:26:22 +0300 )edit
1

hopefully, this is essentiell

( 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

( 2019-02-08 21:14:51 +0300 )edit

I don't experience this with Photoshop/Lightroom for instance. Do you have a Google account added on your XA2? (not in dalvik)

( 2019-02-09 11:41:23 +0300 )edit

## 1 Answer

Sort by » oldest newest most voted

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.

more

## Comments

Do you know if there's a way to achieve the same thing with the Jolla Tablet?

( 2019-05-11 05:37:07 +0300 )edit

No idea. I don't have the tablet. Does the tablet even have alien dalvik? If so, it should be the same steps. You may not even have to recreate the system.img in case the files are just in a directory (this was the case for the jolla 1 phone iirc). Either way, the build.prop file is an android thing, so technically, no matter HOW you run android apps it should work. Even on real android OS.

( 2019-05-11 16:57:20 +0300 )edit

@mynameisnotimportant The tablet for sure uses Alien Dalvik, as in Android 4.4.4. There are actually three build.prop files to be found in the folder structures, I've edited the one in "system_jolla" (= 256 MB limit, 896 MB size, like above), and it got my tablet into a boot loop after a restart, so I had to do a hard reset in the end, because I couldn't access the files through Recovery Mode anymore. Do you have a clue why such a small change ended in a non-starting device?

( 2019-05-12 03:13:40 +0300 )edit

I've been able to modify the build.prop in opt/alien/system now (256m limit, 512m size), without causing a bootloop, unfortunately Fennec 59.0.2 still crashes a lot despite the change. Anyway, thanks for the instructions above!

( 2019-05-13 01:06:22 +0300 )edit
1

No problem, glad it works for you. I am not sure about system_jolla, never heard of that before. It's probably unrelated, maybe some folders are related to libhybris? Not sure, at this point I am just wildly guessing. In any case, the /opt/alien/system/build.prop file is the correct one. As for boot loops, if I had to guess it's due to assigning too much RAM? I'd just play around with it. You should be able to just simply restart the service instead of rebooting the device to try the values systemctl restart aliendalvik.service.

As for Fennec, also no idea. However you should try reinstalling it (uninstall then reinstall, not just updating). That's what I had to do after installing microg.

( 2019-05-13 18:44:50 +0300 )edit

## Stats

Asked: 2019-02-07 22:41:53 +0300

Seen: 433 times

Last updated: Apr 30