As far as the chords not being put on different lines, I'm willing to bet that's because of a difference in line endings (\r\n on Windows, \n on Android). I will run some tests to see if I can reproduce that issue and get it fixed for the next update.
As far as the text issue with the chords, I have found that all the unicode characters that you add through the insertion dropdown will not scale properly between devices (and this not something I can fix). This is a problem whether you go from Android to Android or Android to Windows 10 (or vice versa). I'm going to remove the ability to add those symbols in text annotations as soon as I've reworked the stamps to use a music font. My hope is that the music font will scale properly between the devices unlike those special unicode characters. In the meantime, if you need to move your library between devices, you can't rely on those unicode characters. You will have to instead insert stamps or use b for flat and # for sharp.
Mike
As far as the text issue with the chords, I have found that all the unicode characters that you add through the insertion dropdown will not scale properly between devices (and this not something I can fix). This is a problem whether you go from Android to Android or Android to Windows 10 (or vice versa). I'm going to remove the ability to add those symbols in text annotations as soon as I've reworked the stamps to use a music font. My hope is that the music font will scale properly between the devices unlike those special unicode characters. In the meantime, if you need to move your library between devices, you can't rely on those unicode characters. You will have to instead insert stamps or use b for flat and # for sharp.
Mike