why are there different images based on sd card size?
#1
I'm new to this, but have been exploring and experimenting with my new pine64 and also a rpi3 (just ordered a ODROID-C2 to play with as well)

I haven't seen this practice elsewhere. for other distros I have tried there is a single img file and, once you have it flashed, you expand the file system to free up the rest of the card.

Just curious what the advantage is here.

thanks
#2
(07-28-2016, 06:42 AM)checktravis Wrote: I'm new to this, but have been exploring and experimenting with my new pine64 and also a rpi3 (just ordered a ODROID-C2 to play with as well)

I haven't seen this practice elsewhere. for other distros I have tried there is a single img file and, once you have it flashed, you expand the file system to free up the rest of the card.

Just curious what the advantage is here.

thanks

Expanding the file system utilised by the Android image is apparently trickier than your standard Linux image. The PhoenixCard version of the image expands readily enough, but not everyone gets on well with the PhoenixCard software, so there are also offered DD images, which can be burned using the dd command, or with software such as Win32DiskImager, ApplePi Baker or Etcher, depending on the computer you are using to burn the image.

See also this thread: Empty space.

Ideally I suppose the DD Android images would come with a built-in script that automatically expands the filesystem to fill the microSD card. Then only a single minimally-sized image would be needed.
#3
Theoretically the /data partition on the dd images can be expanded since it is behind all the other ones. Practically the partition layout has overlapping definitions as I pointed out in http://forum.pine64.org/showthread.php?tid=1834 . I managed to resize the /data partition to the full size, but you have to use low-level tools like sfdisk since all the more user-friendly ones don't operate on partition tables with overlapping partitions. Maybe this can be somehow fixed in the build config of the Android SDK?

The Phoenixcard images are expanded on the fly to the full card size, but they require a tool that basically runs only on Windows and doesn't always work for everyone...
Come have a chat in the Pine IRC channel >>


Possibly Related Threads…
Thread Author Replies Views Last Post
  Maximum size of boot MicroSD for RockPro64 and Pinebook Pro commiecam 0 315 08-07-2022, 10:47 AM
Last Post: commiecam
  I just got to find phone in my sd card won't read Tyro 5 3,891 11-15-2021, 01:11 AM
Last Post: alexenwaston
  My PinePhone does not read SD card asasani 4 2,414 11-09-2021, 03:24 AM
Last Post: asasani
Question Differences in Jumpdrive images. jpaulbiss 2 1,883 09-16-2021, 06:30 PM
Last Post: jpaulbiss
  How to boot from SD card on pinebook pro linux123 3 4,218 12-02-2020, 10:29 AM
Last Post: linux123
  SD Card boot - trying out OS Baconomics 1 3,398 06-19-2020, 06:58 AM
Last Post: tophneal
  SD Card locked icemeister 5 7,782 05-13-2020, 11:59 PM
Last Post: alexenwaston
  How to boot from the SD card and install to eMMC? ravanh 2 5,103 03-18-2020, 09:42 AM
Last Post: tophneal
  recommended micro sd card ? mronhb 91 179,162 03-03-2020, 11:34 PM
Last Post: siyatalerja
  eMMC card on adapter Malmgren 8 8,264 03-20-2018, 11:14 AM
Last Post: Malmgren

Forum Jump:


Users browsing this thread: 1 Guest(s)