3 ms·
This reminds me of how a recent Android version (12?) suddenly made certain characters (e.g. ?:<>) illegal in file names[0], probably because to increase compat
by codethief 4y ago
This reminds me of how a recent Android version (12?) suddenly made certain characters (e.g. ?:<>) illegal in file names[0], probably because to increase compatibility with NTFS. Wtf, Google. Nowhere was this breaking change announced.
Not only does my notes app, which has worked flawlessly for years, now crash when I accidentally use one of those characters in a file name / note title. (Unfortunately, the app no longer receives updates.) But suddenly my entire ebook library (which follows the name format "first author & second author: title (year)") no longer synchronizes with my phone (running AOSP / GrapheneOS), either. Fantastic.
[0]: https://android.googlesource.com/platform/packages/providers/MediaProvider/+/6b7baf4b9722dd75bfb5d64acadf48223226cde6%5E%21/#F0 https://android.googlesource.com/platform/packages/providers...
- dpkirchner 4y agoMakes you wonder what issue they were mitigating. Passing file names as part of a concatenated string to bash? Ala 'bash -c "ls $filename"'?
- kps 4y agoWindows. /** * Sanitizes given name by mutating the file name to make it valid for a FAT filesystem. */ https://cs.android.com/android/platform/superproject/+/master:packages/providers/MediaProvider/src/com/android/providers/media/util/FileUtils.java;drc=master;l=1461 https://cs.android.com/android/platform/superproject/+/maste...
- codethief 4y agoAh, good point. So it was not NTFS but FAT compatibility they were aiming for.
- mikepavone 4y agoOh, I was wondering my new phone didn't like some of the music files I was trying to copy over using MTP even though the old one handled them fine. I had assumed the phone manufacturer did something dumb, but apparently it was Google all along.