DrYak | # 2331 | 2018-02-28, 12:19 | Report

Had a quick look around.

The package you've downloaded, "usb-stick-utils-automount-exfat-support",
is a different script ("mount-usbstick.sh") that gets triggered (see "90-mount-usbstick.rules") whenever a USB stick is inserted (either a microUSB stick directly into the USB OTG port, or a regular USB stick into a USB HUB conencted to the OTG post).

It does support exfat, but does not react to SD cards.

the built-in script that gets called is "mount-sd.sh".
If you have a look into it, it doesn't handle the FUSE exFAT module.
(compare the 2 "case ${TYPE}" switch blocks in the middle of both scripts).

Together with TJC member "V1olat0r" we had bounced back and forth a few more advanced scripts (handlind NTRFS, Swap, etc.)

I think you should be able to get SD card automounting by transfering the vfat/exfat/ntfs case block from "/usr/sbin/mount-usbstick.sh" to "/usr/sbin/mount-sd.sh".

DrYak | # 2332 | 2018-02-28, 12:31 | Report

Two different thing to notice :

- WhatsApp relies on a background daemon "com.whatsapp" running to handle the messages. You are technically online as long as this daemon is running, and there's no official way to kill it from the WhatsApp interface.
(According to the rationale from some WhatsApp FAQ is that they want to mimmick the "always on" feature of SMS. You can't switch SMS online, therefor you shouldn't be able to shut down WhatsApp either).

If you want WhatsApp to stop processing messages, you need to kill the background daemon.

If you only close the app (kill the card, press "back", etc.) you're merely closing the interface, not shutting down WhatsApp.

The fact that it suddenly doesn't show online anymore on Android is probably some side effect of how that peculiar version of Android (or some addittional tools) handle rogue processes / ressource conservation. But that's not the normal expected WhatsApp behaviour according to their docs.


- Sailfish OS is a true multi tasking OS. All the open cards are always running (unless grayed out). But most 4.4 Kitkat era applications (=the API level exposed by aliendalvik) don't have a concept of application "still running but not in focus".
Thus nearly no android app knows that you swiped to switch to another app, and WhatsApp is among them.
Because it's interface is still working, it's still believing to be infocus.

The only useful tip that I can give is to get out of any message screen back to the main contacts/list-of-chats screen, before switching to another card.
At least WhatsApp won't be thinking that you read a message while the chat is open and won't mark as double-blue tacks (read) in the senders' app, but only as double-gray tacks (delivered).

wrm | # 2333 | 2018-03-01, 04:59 | Report

Facebook messenger background service keeps crashing time to time. Anything can be done on that?

suicidal_orange | # 2334 | 2018-03-01, 12:50 | Report

My X dual sim has just arrived and I see in the January update SFOS 2.2 will be out in 'a couple of months' adding official support - any thoughts on whether I should wait or will it be a smooth upgrade if I mod the current version?

I'm thinking the new kernel won't arrive until SFOS3 so it should be OK but this is .2 rather than the usual .1.x so must be more significant...

lantern | # 2335 | 2018-03-01, 13:17 | Report

no need to wait

mariusmssj | # 2336 | 2018-03-01, 13:25 | Report

I feel that dual xperia X is not yet ready to be daily driver. Too many things rely on mods. Thanks for Lantern I got mine working but it's not reliable enough for me just yet. Thus I am waiting for 2.2 update in few months time.

suicidal_orange | # 2337 | 2018-03-01, 13:57 | Report

I'm only going to use one sim and WiFi, got a great condition dual for not much more than the single and the extra space could be useful.

What makes it not ready for daily use?

datman | # 2338 | 2018-03-02, 01:43 | Report

Hi, I am sure I posted this but I cant find it. Is the F5122 ok to use with the standard install without any tweeks? I only need the 1 sim. Thanks

suicidal_orange | # 2339 | 2018-03-02, 08:41 | Report

You also posted in the community build thread - similar names so it gets confusing!

As I understand it sometimes the dual works and sometimes it doesn't without these tweaks, with them it works:

You also need to resize the partitions to use the full 64gb.

Might want to wait for lantern to confirm nothing's changed

---

Last edited by suicidal_orange; 2018-03-02 at 09:56. Reason: Strike resizing as inaccurate

lantern | # 2340 | 2018-03-02, 08:48 | Report

Nothing's changed.
Also, you don't need to resize partitions, you'll have full 64 gb automagically.