androids apps are really killed very often :/

Installed Sailfish 2.1.3.7 and then updated to 2.1.4.13 and I was amazed how it was improved since I tried the first release, very fast, androids apps works almost perfect (except for the stupid bug of online status for Whatsapp). Installed again Android as the stupid bug for me is important as I use for work, hope in the next dalvik (or probably ART) release that will be fixed. Very happy with the progress of Sailfish

Greetings from Paraguay!

Enviado desde mi F5121 mediante Tapatalk

Have anyone managed to get a SDXC 256gb card working on the xperia?

I got an Samsung Evo 256 working in my x, don't know if its SDXC.

Yes, Samsung Evo Plus Micro SDXC 256GB (Model MB-MC256GA/EU ) works fine (FAT32 formatted).

I tried the 256GB SDXC from my Android phone today. Unfortunately the card is using exFAT and as I swap between devices very often I kept the file system.

Downloaded olebr's fuse exfat, and exfat utils , as well as ferlanero's auto mount exfat on Sailfish X

I found auto mount does not work, so I tried manually with mount /dev/mmcblk1p1 /media/sdcard , but terminal says unknown file system type "exfat"

Seems fuse exfat isn't recognised by the system? But olebr's version should be specifically built for Sailfish X. Very strange... Any hints?

Many thanks

Depends on the technology of the card itself.
I've personally been using Transcend Ultimate 633x 64GB card on my Jolla1, and it handles swap pretty well.

- it uses dynamic wear leveling, to spread the writes accross more erase groups, delying the dying.
- it uses static wear leveling to also occasionally re-write old data to avoid it decaying over time (remember Samsung's non-pro 840 SSD, back with the old firmware ?)
- has ECC and is much more resilient.

I second that, but only on some high quality microSD card that can survive the load.

Out of curiosity, what problems are you experiencing ?

Currently, we're stuck with Alien-Dalvik. We won't see anything at least not before Sailfish 3.

According to some threads on TJC, some cards aren't even physically recognized by the kernel's mmc driver.
(Someboy had problem with a Saumsung EVO (non plus) 128GB)
Apparently, it's a known kernel problem (should be eventually solved in some future upgrade).

That's in addition of you needing to either reformat from exFAT into something slightly more cross platform (e.g.: FAT32), or installing exFAT fuse drivers.

Before getting to the exFAT problem, as mentionned above, check that the kernel at least sees the MMC device itself :

after loading the card holder in the phone, do you see a "/dev/mmcblk1" device appearing (external slot) ? or do you only see "/dev/mmblk0p??" devices (internal flash).

What does "blkid /dev/mmcblk1p1" say ? (run as root with "devel-su" ?)

Try: "mount.exfat-fuse /dev/mmcblk1p1 /media/sdcard"

To force your system to use the correct FUSE helper.

There is indeed mmcblk1, so the hardware recognises external SD

blkid recognises Label, UUID and Type correctly. Tried with mount.exfat-fuse this time worked correctly! Thanks a lot!

On every reboot I need to manually mount again. But doesn't matter.

When you're using Whatsapp or Telegram, or any IM app that shows online status, after you close, press android back button, or your swipe to go to another app, the online status persist



Enviado desde mi F5121 mediante Tapatalk

I have the same issue.