View Single Post
Old 08-12-2014, 06:00 PM   #327
embryo
Fanatic
embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.embryo calls his or her ebook reader Vera.
 
embryo's Avatar
 
Posts: 529
Karma: 64554
Join Date: Aug 2013
Device: Kobo Glo, GloHD
Recently I changed my 'Android only' setup to a 'Dual Boot' one, and I was really happy about it until I discover that the Android part could not recognize unicode characters in the file names.
Instead of the characters I see question marks.
I tried different file managers with no luck.
Even changing the System Language did not help.

Knowing that the original image could recognize the filenames correctly, the culprit could be one of the following two:
- The files of the patches that make the reader Dual Boot capable or
- The files I copy to the image to make it able to run from the SD card.

If someone with some knowledge of the Android internals could find which file is responsible for this problem, would be really appreciated.

UPDATE: As I was suspecting, the problem comes from the way the FAT32 partitions are mounted before starting Android.

A workaround is to remount the Fat32 partitions.
I can do that from the settings for the mnt/sdcard/extsd/ but not for the mnt/sdcard/

With the terminal, if I try to umount/mnt/sdcard I get I failed response.
Its the same if I first try umount/mnt/sdcard/.android_secure
Mounting the system to the PC and unmounting it, fixes the problem.

Last edited by embryo; 08-13-2014 at 05:09 AM.
embryo is offline   Reply With Quote