You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understood, mounts2sd uses a partition (or two if swap is enabled) based on convention and fails quiet silently if it doesn't find it. Has there been discussion about specifying the partition to use with a path to a block device or a UUID (I don't know if Android has /dev/by-uuid/ mapping). This would not only allow to use specific partitions (rather than "the largest"), but also to get an immediate feedback when setting the partition in the settings dialog whether it can be used or not (and in this case of course why :)). This would also cover issues like #26.
The text was updated successfully, but these errors were encountered:
It's especially a problem on shoddily-designed products like the Nabi2. The Nabi2 uses /sdcard2 as a link to one of it's own internal partitions. A lot of apps will presume the highest-numbered sdcard# is the external, while that is not the case with the Nabi2 (which puts external storage at /sdcard1). Desperately trying to find a way to make this kids tablet usable for something other than the shoddy built-in apps.
As far as I understood, mounts2sd uses a partition (or two if swap is enabled) based on convention and fails quiet silently if it doesn't find it. Has there been discussion about specifying the partition to use with a path to a block device or a UUID (I don't know if Android has /dev/by-uuid/ mapping). This would not only allow to use specific partitions (rather than "the largest"), but also to get an immediate feedback when setting the partition in the settings dialog whether it can be used or not (and in this case of course why :)). This would also cover issues like #26.
The text was updated successfully, but these errors were encountered: