Take our customer survey to evaluate your visit.
It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.
2017-06-17 08:43 PM
There are plenty of strange things, but I think you're doing progress in a systematic investigation! I agree that the permissions looks good so that wasn't it. Then the file manager can access external card, that's a bit unexpected. New apps working, but those you already had installed doesn't?
> relates to "this phone", "the new card name", "the backup content" separately
Thanks for breaking it down for me. You concluded that "backup" seems to be irrelevant. For "new card name" I thought that there might be references to the old name in the backup, but that is then also irrelevant. With "this phone" I didn't specifically mean HW problems, but something stored in the phone, settings or so. Something that was not there from the beginning. If you were able to try the card in another phone it could bring evidence to "the phone" theory. Seeing that the other theories are probably irrelevant, this is still the best current idea. Trying the card again after a factory reset is the next best thing after trying another phone. :-)
The mount list shows that there is something that is belived to be encrypted. It could be something Spotify does to protect their cache (being precious music data I guess) and possibly nothing wrong in itself. It didn't happen when I tried Spotify briefly, but may be I didn't do exactly like you.
Let us know if you get more insight.
2017-06-17 11:36 PM
Ok, now I understand what you meant by "the phone". And after this weekend, I have proof that you were right with the "the phone" theory. But let's look at it step by step:
Well theories aside, I took a look at dmesg output yesterday. Here are some entries I found strange:
Hmm, invalid supeblock and some filesystem inconsistencies - not what I wanted to see...
Don't know what to think about the ecrytfs entries. SD card should not be encrypted!
And here some more "avc: denied" messages and ecryptfs messages:
2017-06-17 11:52 PM
With the logs from my last entry, my current theory is the following: My initial attempt to encrypt the card was around the reboot issues I had (the beginning of this thread). As a result, the information on the internal storage got corrupted somehow and the system still thinks, that parts of the SD card are encrypted and parts of the SD card file access permissions got corrupted as well.
So I did a software repair with the Xperia Companion to get a complete new install (and not just a factory reset). I did this with the SD card in place (and intentionally not reformatting it). Before I made a backup of the system (everything available) with the "Backup & Restore" app of the phone (target: SD card). After the software repair I let Google Play reinstall all my apps and restored everything available with "Backup & Restore".
Now everything is back to normal again and I can access the SD card from all apps (Spotify, MAPS.ME, etc.) without problems.
I will follow up on this topic when I find the time to look at the logs - please give me some days :-)
Just for reference and maybe it will help someone in a similar situation.
2017-06-18 12:38 AM
Addendum part I:
[ 6.872765] e2fsck: /system/bin/e2fsck: Bad magic number in super-block while trying to open /dev/block/bootdevice /by-name/userdata [ 6.905012] e2fsck: /dev/block/bootdevice/by-name/appslog: 40/1024 files (5.0% non-contiguous), 1159/4096 blocks [ 6.918033] e2fsck: /dev/block/bootdevice/by-name/diag: 51/2048 files (2.0% non-contiguous), 1270/8192 blocks
2017-06-18 04:53 PM - edited 2017-06-19 06:55 PM
Final post in this thread - maybe ;-)
I want to thank the Sony support team and especially JensG for the great support during this error tracking session. Without the help of Jens, I wouldn't have gotten this far and I learned a lot while debugging this issue. Thank you very much!