[closed] SD Path Relocation and Installation Bugs
Posted: Thu Jun 27, 2013 12:27 pm
One thing that I find particularly annoying about Android is that, unlike Windows Mobile 6, the app installers do not let you choose the target storage device for the installation. I got caught out by this in AQ and discovered a few bugs…
On my new Note 10.1, I installed AQ before receiving my microSD card. Obviously, with no choice, Android picked mnt\SdCard0 for the installation, which is fair enough. I was not worried about this as I had previously noted a setting in AQ for redefining the data path.
So, having installed a microSD into the Note, I set about copying the alpinequest folder from mnt/SdCard0 to mnt/extSdCard. I then opened AQ and reset the data path to mnt/extSdCard/alpinequest. After restarting AQ, I then imported my set of GPX landmarks, but was surprised to note that none of my custom icons were displaying, even though they were present in the mnt/extSdCard/alpinequest/icons folder.
I then removed the original mnt/SdCard0/alpinequest folder and restarted AQ. It reported an error at first (maybe significant?), but then appeared to start properly. However, my custom icons were still not being displayed, or listed in the landmark explorer.
My next step was to de-install AQ and reinstall it from Google Play. I was very surprised to find that it re-installed into mnt/extSdCard/alpinequest/alpinequest!!! So I de-installed AQ again, renamed my folder to mnt/extSdCard/xxx-alpinequest and re-installed. I have no idea where it installed on this occasion – I could not find a new alpinequest folder anywhere!
Finally I renamed my folder to mnt/extSdCard/xxx, de-installed and re-installed AQ. This time it installed correctly into mnt/extSdCard/alpinequest. Once I had copied in the stuff from the xxx folder, AQ correctly displayed my custom icons.
Some subtle bugs there which I will leave to you to figure out
One suggestion…
It would be helpful if the SD folder location setting invoked a folder picker, rather than relying on the user to work out the path syntax. I also think that it should move (or copy) all of the data across from the previous folder location automatically, including the map cache.
On my new Note 10.1, I installed AQ before receiving my microSD card. Obviously, with no choice, Android picked mnt\SdCard0 for the installation, which is fair enough. I was not worried about this as I had previously noted a setting in AQ for redefining the data path.
So, having installed a microSD into the Note, I set about copying the alpinequest folder from mnt/SdCard0 to mnt/extSdCard. I then opened AQ and reset the data path to mnt/extSdCard/alpinequest. After restarting AQ, I then imported my set of GPX landmarks, but was surprised to note that none of my custom icons were displaying, even though they were present in the mnt/extSdCard/alpinequest/icons folder.
I then removed the original mnt/SdCard0/alpinequest folder and restarted AQ. It reported an error at first (maybe significant?), but then appeared to start properly. However, my custom icons were still not being displayed, or listed in the landmark explorer.
My next step was to de-install AQ and reinstall it from Google Play. I was very surprised to find that it re-installed into mnt/extSdCard/alpinequest/alpinequest!!! So I de-installed AQ again, renamed my folder to mnt/extSdCard/xxx-alpinequest and re-installed. I have no idea where it installed on this occasion – I could not find a new alpinequest folder anywhere!
Finally I renamed my folder to mnt/extSdCard/xxx, de-installed and re-installed AQ. This time it installed correctly into mnt/extSdCard/alpinequest. Once I had copied in the stuff from the xxx folder, AQ correctly displayed my custom icons.
Some subtle bugs there which I will leave to you to figure out
One suggestion…
It would be helpful if the SD folder location setting invoked a folder picker, rather than relying on the user to work out the path syntax. I also think that it should move (or copy) all of the data across from the previous folder location automatically, including the map cache.