05-27-2016, 01:11 AM
(05-27-2016, 12:00 AM)eddyp Wrote:(03-31-2016, 11:15 AM)Andrew2 Wrote: I explained the reason several times in the forums why Android images 'need' Phoenix card (the data partition somewhere inside will be resized to the medium's maximum capacity) and also how the Pine64 folks could deal with: prepare a bunch of dd-able Android images with fixed sizes: 7.5, 15.5, 31.5 and 63.5 GB. Or by expanding the partition on first boot -- that's easy with Linux but maybe not with Android. No idea since I'm not interested in Android at all
It sounds like depending on a Windows host could be easily eliminated. It shouldn't be hard enough to make a shell script that could do the writing of the small image then increase the FS to the needed capacity (or simply make the FS big from the start and loopback mount the partition from the image and rsync the contents from the image to the big FS).
I see you said you're not interested in this, but hasn't anybody tried this yet?
On a related topic, is the format of the Pine64 compatible images documented somewhere? I am thinking of trying other OSes than Linux or Android, so this information would be crucial to be able to do this.
Fixed-sized dd-able Android images are already available via the Pine64 wiki.
