Hey, hoping someone on here may possibly know a definite answer to this. (goto last paragraph for my actual questions)
Since I got the Xperia L little over a year ago as a secondary phone, I started flashing and manipulating my (then) two devices, and I also use a lot more apps now than I did two years ago as my "need" to be mobile and stay available and connected has lately increased. Overall, I'm not too satisfied of the whole Android and apps concepts but, so far, I've appreciated the Xperia L as a versatile and unobtrusive device.
When its "internal storage" (or /data, basically) recently got a little cramped, I moved a few apps to SD via Android's native method, and when some apps wouldn't like to be moved or even stopped working after they got moved, I created an sd-ext partition in the external SD card and moved a few apps there, via symlinks first then via Mounts2SD - certain apps still seem to prefer to remain on the internal storage for some reason and some apps seem to act up (or lose settings etc), especially when /data/data is saved to sd-ext, or they wouldn't even run correctly, stop responding or crash (user apps only).
The "internal SD" is 4 GB in size and I barely need it for anything, other than saving ROM files, Gapps and aromafm when flashing without the external SD card present, which is 32 GB (and I have two of these) so I don't really see the point of saving work files and media on just another partition. I see how there may be a point in terms of speed, e.g. for taking pictures, since writing to the external SD card seems significantly slower (at most around 11 MB/s for larger files), and when saving apps to sd-ext, the internal storage provides enough space for a couple of photos anyway.
Now, my questions are if it's possible to use the internal SD partition as a mount point for sd-ext by whatever means, maybe swap certain /dev/blocks somehow, though I don't know which ones that would be and how I'd have to do that so Android doesn't give me the bird..?
And, considering the Linux way of "partitions" and mounts, is it even expedient practice to force apps "outside" the root/data structure..?
Is there a completely reliable (compatible and transparent) way to do this, so no apps ever complain about it, and then save/load their stuff (on either the internal or external SD), or would it generally be the better choice to remain with unchanged partitions..?
I take it there's no feasible way to actually re-partition the internal memory, so the whole /data thing would increase from 1.57 GB now to, say, 3.5 GB or more, leaving 1-2 GB for sdcard0 (enough for my purposes)..? (without an external input of sorts, however they initially put the partitions on the clean 8 GB memory)
Since I got the Xperia L little over a year ago as a secondary phone, I started flashing and manipulating my (then) two devices, and I also use a lot more apps now than I did two years ago as my "need" to be mobile and stay available and connected has lately increased. Overall, I'm not too satisfied of the whole Android and apps concepts but, so far, I've appreciated the Xperia L as a versatile and unobtrusive device.
When its "internal storage" (or /data, basically) recently got a little cramped, I moved a few apps to SD via Android's native method, and when some apps wouldn't like to be moved or even stopped working after they got moved, I created an sd-ext partition in the external SD card and moved a few apps there, via symlinks first then via Mounts2SD - certain apps still seem to prefer to remain on the internal storage for some reason and some apps seem to act up (or lose settings etc), especially when /data/data is saved to sd-ext, or they wouldn't even run correctly, stop responding or crash (user apps only).
The "internal SD" is 4 GB in size and I barely need it for anything, other than saving ROM files, Gapps and aromafm when flashing without the external SD card present, which is 32 GB (and I have two of these) so I don't really see the point of saving work files and media on just another partition. I see how there may be a point in terms of speed, e.g. for taking pictures, since writing to the external SD card seems significantly slower (at most around 11 MB/s for larger files), and when saving apps to sd-ext, the internal storage provides enough space for a couple of photos anyway.
Now, my questions are if it's possible to use the internal SD partition as a mount point for sd-ext by whatever means, maybe swap certain /dev/blocks somehow, though I don't know which ones that would be and how I'd have to do that so Android doesn't give me the bird..?
And, considering the Linux way of "partitions" and mounts, is it even expedient practice to force apps "outside" the root/data structure..?
Is there a completely reliable (compatible and transparent) way to do this, so no apps ever complain about it, and then save/load their stuff (on either the internal or external SD), or would it generally be the better choice to remain with unchanged partitions..?
I take it there's no feasible way to actually re-partition the internal memory, so the whole /data thing would increase from 1.57 GB now to, say, 3.5 GB or more, leaving 1-2 GB for sdcard0 (enough for my purposes)..? (without an external input of sorts, however they initially put the partitions on the clean 8 GB memory)
Aucun commentaire:
Enregistrer un commentaire