exFAT filesystem is not supported currently, I think. All 64 GB SDXC-memory cards are preformatted to have exFAT. Reformatting them to ext4 in some Linux PC may work. Later, exFAT-support could come to jPhone also.

I'd say you are wrong. Android has good multitasking. In specific ways it is better and more clever than the normal UNIX multitasking. Activities, processes which interact with a user, are not suppose to run when process is not on the foreground, there is no reason to waste battery life then.
If a process needs some code to run in the background, a Service or IntentService is created.

I use multitasking in Android daily, successfully.

Recent high end Android devices with bigger screens, like Samsung Note 3 and Note 10.1 have multiwindow multitasking, when many applications run in the foreground and they all can interact with a user at the same time.

There were some discussion about Android's process life-cycle's (see picture) Pause-state. Pause-state is when the Activity is no longer in the foreground, but may be partly visible still (or not). The Activity's process may run in the background also in the Pause-state (Android 3.x and later) and only when going to Stop-state, it needs quickly to save all needed session data, if nice user-friendly Resume is needed. On the Stop-state, the Android system may kill the Activity in low memory conditions or for some other reasons.

I'd hope, also native apps for Jolla, would have trapped SIGHUP and SIGINT signals and behave like Android apps when they go to Stopped-state. So if kernel needs to OOM-kill the process, it would have session data saved to persistent memory and when a user restarts the app, it returns to the same state it was before the OOM-kill. That is one lesson which would be good to learn from the Android system for all (mobile) apps.

But also many (lazy) Android-developers do not just care if their app go to Stopped-state. They just assume a user would always run their app in the foreground and then quit it when a user is done with it. It then gets frustrating if a user goes back to the app and expects it to be in the same state where (s)he left it.

If you mean a rpm-file which you have locally on the filesystem or on a sd-card? With zypper:
http://remind-nix.blogspot.fi/2008/0...kages-for.html
http://forums.opensuse.org/english/g...le-zypper.html
I do not know if zypper is found in Jolla as a CLI program.

With a rpm-program:
rpm --install /tmp/coolnewsoftware.armv7hl.rpm

Btw, are native app and software rpm-files signed with a GPG-key to prevent MITM-attacks?