mobile

I am running CyanogenMod (CM) 12 on my 1st generation Moto G. In the root directory as shown via the file manager, I created a "notes" folder, where I store text files. Files that I copy over from Windows 7 seem fine.

As an *aside*, the only proviso is that the native CM text editor uses Unix line endings (LF only, not CR+LF). So if the text files were DOS to begin with, any new lines of text added on the handset will have only LF, while old lines will have CR+LF. The CM text editor handles this well, seemingly treating both line endings in the same way.

I have a problem with any *new* text files created on the handset. I am not sure whether the problem is somehow related to the line endings. On the handset, I created a file tmp.txt of length 160 bytes (it contains 160 characters). When I view the text file from Windows 7 using the MTP interface, windows explorer shows the file as having 0 bytes. When I drag the file over to a Windows folder on the laptop, it is basically an empty file. Very bad.

I can use adb to pull the file over, and then it's fine (it's not empty). As a side note, the source path as seen in the handset file manager must be prefixed with storage/emulated/legacy/ when using adb pull.

I do not want to use adb pull to copy over a whole bunch of files. The klag in that process would make it a real headache. I will be regularly mirroring these text files between the laptop and the handset.

Can anyone suggest a reason why a file created on the handset looks so bizzarely empty when viewed over the MTP USB interface? Can anyone suggest a hopefully elegant workaround that doesn't involve too much geeking out? Geeking out is all fun and that, but the handset was really meant to save me time rather than become a project in itself.

Thanks.