SailfishX : MicroSD-card not detected

I'm a bit worried about this. I'm going to buy a 256GB card, which is half the price of the device itself. Maybe I'll be able to recycle it when the Youyota arrives...

So, I tested the 128GB card (SanDisk Ultra) from my Jolla1. This card is BTRFS formatted. The Xperia booted flawlessly and recognized it as BTRFS-card, but did not mount it automatically.

So I wonder if that's a possible option how to do with unbootable combinations: formatting the card as btrfs and mount it later. Can anyone check this?

@Robomike SFOS X does not support BTRFS (it's missing the kernel modules) and in another thread here you can read that it's not easy to add this feature (because the current kernel don't allow modules). That is why your phone detects the card but can't mount it (until you reformat it with another FS). I don't think you suggestion would work since this does not look like an FS issue to me.

@ghling Ah, thanks, missed that info. Sh*t, no BTRFS. The more I know about SailfishX, the more I love my Jolla 1. Some hope remains for the just ordered Samsung ProEvo Plus 256GB.....

KERNEL COMPATIBLITY seems very likely : On Talk Maemo Org, there's a user who consistently can access Samsung EVO+ 128GB under the up-to-date Android 7.1.1 Nougat before upgrade, and loses access after upgrade all devices to Sailfish X (which reuses older kernel - 3.10.84 - and firmware that the Sony's Android 6.0.1 Mashmallow uses).

• his logs : after insertion detection, no card detection but instead only errors.
• my logs : example of how a card detection should have looked.

Regarding BTRFS: currently UDF and F2FS are supported as flash-friendly (and in UDF's case - cross platform) filesystems. BTRFS and everything else could be recompiled (Sony releases the code of their kernels, and the binary firmware are kept separate).

If one wants to know if the 256GB ProEvo+ ("+", not "plus") is running: yes, after external formatting to Ext4. Seems okay at first glance.

Note that the same article mentions that you can use bigger SDXC cards if you format them to ext4 or FAT32 first. Worked for my 64GB card, and I think someone even reported 128GB.

I guess I misinterpreted the article as saying only 32 GB cards are officially supported. Maybe they are just referring to file system limitations when they mention the 32 GB limit. All in all I found the article a bit hard to comprehend.

This worked for me, also for a Sandisk 200GB card. Note, the official specifications describe as 200GB to be the maximum supported (see https://www.sonymobile.com/us/products/phones/xperia-x/#specifications).

It worked for me too !!! Thanks

As far as I know there is no technical reason for a limit of 200GB in the MicroSDXC spec, which allows up to 2TB (that's probably a hard limit related to addressing). I guess Sony just tested the largest card available at the time they wrote that.

I haven't tried yet but I'm reasonably sure 256GB and larger cards will work as there is no technical difference between MicroSDXC cards with different capacities. If anybody tried a memory card larger than 200GB, please report.

Is it this card that works in your Xperia X please? https://www.alza.cz/EN/sandisk-microsdxc-200gb-ultra-android-class-10-a1-uhs-i-sd-adapter-d5169333.htm I have Samsung 128GB evo+ (red+white colour) that I used successfully on Jolla C (and maybe Jolla 1 as well) but SailfishX won't boot with it :/

<rant> These android devices suck big time. I really hate all the proprietary drivers and embedded nonsense or whatever the real reason is why we cannot update the obsolete kernel on our own devices. If they call these locked down devices an "ecosystem" then it is only an ecosystem of planned obsolescence. </rant>

Used a SanDisk Ultra Plus microSDXC UHS-I Card 256 GB. It works fine. :D

Thanks for the answer. I hope that it is fixed in the future. I have 32gb Kingston formatted to FAT32 and not detected by SailfishX. It works great on Jolla 1 & Intex Aqua Fish. With this problem it is impossible to restore a backup to SailfishX from my earlier phones. I'm not yet ready to buy a new MicroSD card because of this. Is there any info available anywhere about Jolla looking into this error?

With Sailfish 3.0.0.8, on Xperia X, the issue is still there. My Kingston 256GB SDCS MicroSD card is not recognized, with "mmc1: mmc_sd_init_card() failure (err = -5)" in dmesg. I formatted it externally with ext4, did not help. A SanDisk 128GB microSD card works without issues. Should have stuck with SanDisk, I guess.

On my Jolla 1, Sailfish 2.2.0.29, the Kingston 256GB is recognized. So, I will try to open a support case for the Sailfish X.

thank you, but this issue depends not on the format.

I was unable to install the rpm package, it said failed :(

Same problem! Phone does not boot with memory card installed. Sony memory card 32GB If I insert it after start Sailfish find it but not able to mount it. Format to ext 4 dosen't seems to work in the phone. Have after that format it in an external PC to ext4 and it doesn't work anyway. Memorycard worked as it should before. Note! When I installed Sailfish I didn't have any SD-card installed.

While fuse-exfat does work most of the time, the phone will randomly stop being able to read it, and Storage reports it having a negative capacity. In my experience, the only way to get a successful re-read is to pop it out and re-insert till it is again recognised in the Storage setting.

I re-formatted my 128 GB SD card with F2FS, and I haven't noticed any of the random dismounting. Unfortunately, the App-->Camera does not allow me to use it as a storage location now even though it recognises it as ready and even shows the remaining capacity. Frustrating.

same problem Sandisk SDHC I 16gb. not detected on Xperia (working on Jolla)

Have you tried re-directing the storage of pictures and videos to the F2FS-formatted SD card? My experience is that it sees the card and shows the free space (within Apps-->Camera) but claims "Selected storage is not available."

I just tried and it works fine.

If your problem is related to mine, I suggest making an F2FS file system but not creating any directories or files outside of Xperia X, i.e. let only the phone write anything to that filesystem. My guess is that there might be some differences in on-disk structures between the old kernel on Xperia X and new Linux kernels on your computer.

My Samsung 128GB EVO+ card formatted with F2FS works fine if I don't write any files or directories directly from another system. If I do, Xperia X shows one top-level directory but no other directories or files. That's not really a problem to me as I'm not planning on switching the memory card in and out of the phone.

Jolla should include f2fs tools, more specifically mkfs.f2fs, so the GUI can format a memory card and we wouldn't have to care about kernel compatibility.

What about IRQ 711 stuff? Any danger? Interrupt does sound nasty as in IMHO in the best case it can influence perceived response, battery or something more nasty. In you case it reads as 86 ms delay of write or something.

I think it relates to the Broadcom wireless driver, possibly about device sleep states, but I'm not too familiar with low-level wireless stuff.

The file manager on Windows laptop (at least Win 10) can show an SD card in Ext4 format (and the contents of it) as long as the card is inserted in Xperia and Xperia is connected to the laptop with USB. Copying data between Windows and the card works both ways.

@jovirkku this is not really the question here, other users have reported that even in ext4, their card is not recognized. Does your comment means that Jolla is not looking at the issue and we need to find another SD card that works?

I can not format it on my Win10 Laptop to Ext4 format (without installing aditional software). It should be as simple as that: Buy any comatible SD-card, plug it in and it works.

Actual Situation: search in Forums to get it work, spend hours with no result, try every workaround, still not working. SailfishOS can do better then that!!! Otherwise there is no chance to get happy customers that could recomend the OS to others to try it out!

I could only make my 64GB memory card function after I formatted it with ext3 and let the phone re-format it to ext4. It just wouldn't mount it, if I pre-formatted it with ext4 using my Linux desktop. Weird...

Oh, this was on Jolla 1, but the software logic was the issue here, and the software functions the same after the memory card has been installed and it gets picked up by the hardware and kernel properly.

Schold that be the way of using an SD card on a Sailfish device? I'm not sure my mother or my sister would get the card to work that way... This is riddiculous!!! And apsolutely NOT userfriendly!

This is ONE WAY to use SD cards - if you dont like this use Android with advertizing and surveilance - SFOS is getting more and more useable. Freedom and Liberty were never "userfriendly". So don`t grumble but thankful - otherwise tell you mother and sister to use pen and paper ...

Lol! please don't take it personal! I hate Android and iOS! I just can not believe it takes so long to make it work! I mean Jolla Has contractors and Partners in Russia, China and Bolivia and this SD-Card situation is so Beta that it hurts! How do they want to conquer the markets when ordinary users have to learn programming to get stuff working? this thread is not even "tracked by Jolla" by the way I Love Sailfish OS and Jolla, and thats why i want it to be userfriendly that even my Family can use it and get to love it!

no matter - i dont take it personal ;) But it`s annyoing that most user expect 100% working Systems.

Especially for linux based systems the hardware settings were sometimes inkompatibel because they are produced for windows systems or consumer devices.

Take a look at the other operatingsystems : Windows is unsave, and MS has the entire control of their OS and demands licence fees - their systems needs a virus scanner and other aditional Software. Most of them is installable via one klick actions.

Linux is licence fee free, and much more saver than windows. But linux needs more manuall configurations, thats the price the user has to pay - work ( Linux ) or money ( Windows ).

Since the upcomming android OS the users became "informatics" when they install apps - they thought. Before the Android Age consumer often consults real informatics to solve simple problems. If SDcard dont work in SFOS consult someone who know how to solve this issue. thats it ;)

Jolla tries to merge these two sections without selling data of their users like google android. Android is compatible to most devices. this extreme compatibility causes an low performance system with a lot of basic issues, like ssh support, networking and others.

SFOS conquers the market , i sure - slow but constantly ;)