03-08-2017, 05:00 AM
It may take a couple iterations for us to get things working on your device. The major problem is that your device isn't reporting the removable SD card correctly. That screws up a lot of code that normally relies on being able to get that information. For example, on most devices, if you select a read-only directory on a removable SD card, my app is going to recognize that in the file browser and prompt you to select the SD-card, at which point access is granted. With your device, I have no way of detecting if the selected directory was on a removable SD card, because your device is saying there isn't one! So I just fall back to saying it's read-only. You did the correct thing by selecting the "Set SD Card" option in the overflow menu, as I added that for devices like yours that don't operate the normal way.
I'm going to need you to work with me to see if we can get this all working correctly. If you want to install beta versions for me, I'll be able to get things working much faster than if you just wait for regular releases where I won't know for certain if it's fixed. If you want to do this, send an email to mike@zubersoft.com so I can provide information about how we will go about doing this.
A couple of notes:
1) You shouldn't need to select the /mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files directory with my latest changes. Once the SD card is set, you should be able to pick whatever folder you want.
2) As you noted, the restore from local MSB file to the removable SD card is going to be very slow. The new interface that Google added for this is so much slower than direct file access - there is absolutely nothing I can do about this. If you want to use a removable SD card on a device that doesn't properly support the /mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files path, the only way my app will have access is through that very slow interface. The good news is that I should be able to read files at normal speeds, so in theory this should only affect writing operations (i.e. importing new files that have to be copied to the storage location, restoring backups, exporting songs, etc).
3) Expose database file will not work on a removable SD card unless the application data directory is used (/mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files). It will not work on your device at all due to it not correctly handling the removable SD card. There is nothing we can do about that - you will have to leave that disabled.
4) Restore via companion worked for me when I tested it, but there may be some issues on your device to the way the SD card is handled
5) I really don't think you should try storing the database on the removable SD card. It sounds like it sort of worked in your last bullet, but I can't guarantee there won't be problems
6) It's true that your PC may not be granted access to files and folders created through the new SD card API - I'm not sure how Google handles this.
So I think the next step is for me to add some additional code so that you can pick a different folder on the removable SD card, and it won't say it's read-only. That way the rest of my code will work the way it's supposed to. It sounds like you found some ways to work around that, but I don't believe the code is working correctly if the normal process doesn't complete through the file browser. Just to verify - did it still say the path was read-only after you used the "Set SD Card" option, or did it work after that?
I'm also confused about one thing - in the last bullet, you made it sound like everything did work, albeit very slowly. If you had left the original storage location, and didn't try to put the database on the SD card, did everything work properly? That's the real test I want you to run.
Thanks,
Mike
I'm going to need you to work with me to see if we can get this all working correctly. If you want to install beta versions for me, I'll be able to get things working much faster than if you just wait for regular releases where I won't know for certain if it's fixed. If you want to do this, send an email to mike@zubersoft.com so I can provide information about how we will go about doing this.
A couple of notes:
1) You shouldn't need to select the /mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files directory with my latest changes. Once the SD card is set, you should be able to pick whatever folder you want.
2) As you noted, the restore from local MSB file to the removable SD card is going to be very slow. The new interface that Google added for this is so much slower than direct file access - there is absolutely nothing I can do about this. If you want to use a removable SD card on a device that doesn't properly support the /mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files path, the only way my app will have access is through that very slow interface. The good news is that I should be able to read files at normal speeds, so in theory this should only affect writing operations (i.e. importing new files that have to be copied to the storage location, restoring backups, exporting songs, etc).
3) Expose database file will not work on a removable SD card unless the application data directory is used (/mnt/external_sd/Android/data/com.zubersoft.mobilesheetspro/files). It will not work on your device at all due to it not correctly handling the removable SD card. There is nothing we can do about that - you will have to leave that disabled.
4) Restore via companion worked for me when I tested it, but there may be some issues on your device to the way the SD card is handled
5) I really don't think you should try storing the database on the removable SD card. It sounds like it sort of worked in your last bullet, but I can't guarantee there won't be problems
6) It's true that your PC may not be granted access to files and folders created through the new SD card API - I'm not sure how Google handles this.
So I think the next step is for me to add some additional code so that you can pick a different folder on the removable SD card, and it won't say it's read-only. That way the rest of my code will work the way it's supposed to. It sounds like you found some ways to work around that, but I don't believe the code is working correctly if the normal process doesn't complete through the file browser. Just to verify - did it still say the path was read-only after you used the "Set SD Card" option, or did it work after that?
I'm also confused about one thing - in the last bullet, you made it sound like everything did work, albeit very slowly. If you had left the original storage location, and didn't try to put the database on the SD card, did everything work properly? That's the real test I want you to run.
Thanks,
Mike