iWork8 Air partitions

iWork8 Air partitions

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #46126
    Riccardo
    Participant
    • Posts: 39

    Just out of curiosity, what all the partitions I see on my iWork8 Air tablet are for?

    I mean, obviously on the one named “Windows” I’ll find Windows O.S. and on the one named “Android” I’ll find Android O.S., but I see a partition named “Recovery” and many unnamed others (100mb in size for each or so): are all of them necessary?

    #47093
    Riccardo
    Participant
    • Posts: 39

    No one?

    I see 12 partitions:

    • 100 mb
    • 30 mb
    • 30 mb
    • 1 mb
    • 16 mb
    • 2,50 gb
    • 1,46 gb
    • 8,00 gb
    • 1 mb
    • 8 mb
    • 100 mb
    • C:\ 16,64 gb

    I assume the partition with 8 Gb is the one with Android O.S. and, obviously, the one with 16 gb is the one with Windows; but what the other partitions are for?

    In particular, the one with 2,50 gb and the one with 1,46 gb could give us a lot of space, if deleted and merged with the Windows partition.

    All the partitions, except for the Windows one, were made by the initial flash of Android but Android use only 8 gb of space, so what is their purpose?

     

    #47114
    Konsta
    Participant
    • Posts: 27

    root@CHT_CR_MRD:/dev/block/by-name # ls -l
    lrwxrwxrwx root root 2016-05-25 17:12 Basic_data_partition -> /dev/block/mmcblk0p14
    lrwxrwxrwx root root 2016-05-25 17:12 EFI_system_partition -> /dev/block/mmcblk0p12
    lrwxrwxrwx root root 2016-05-25 17:12 Microsoft_reserved_partition -> /dev/block/mmcblk0p13
    lrwxrwxrwx root root 2016-05-25 17:12 android_boot -> /dev/block/mmcblk0p3
    lrwxrwxrwx root root 2016-05-25 17:12 android_bootloader -> /dev/block/mmcblk0p2
    lrwxrwxrwx root root 2016-05-25 17:12 android_bootloader2 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root root 2016-05-25 17:12 android_cache -> /dev/block/mmcblk0p8
    lrwxrwxrwx root root 2016-05-25 17:12 android_config -> /dev/block/mmcblk0p11
    lrwxrwxrwx root root 2016-05-25 17:12 android_data -> /dev/block/mmcblk0p9
    lrwxrwxrwx root root 2016-05-25 17:12 android_metadata -> /dev/block/mmcblk0p6
    lrwxrwxrwx root root 2016-05-25 17:12 android_misc -> /dev/block/mmcblk0p5
    lrwxrwxrwx root root 2016-05-25 17:12 android_persistent -> /dev/block/mmcblk0p10
    lrwxrwxrwx root root 2016-05-25 17:12 android_recovery -> /dev/block/mmcblk0p4
    lrwxrwxrwx root root 2016-05-25 17:12 android_system -> /dev/block/mmcblk0p7

    shell@CHT_CR_MRD:/ $ cat /proc/partitions
    major minor #blocks name

    254 0 102400 zram0
    179 0 30310400 mmcblk0
    179 1 102400 mmcblk0p1
    179 2 102400 mmcblk0p2
    179 3 30720 mmcblk0p3
    179 4 30720 mmcblk0p4
    179 5 1024 mmcblk0p5
    179 6 16384 mmcblk0p6
    179 7 2621440 mmcblk0p7
    179 8 1536000 mmcblk0p8
    179 9 8388608 mmcblk0p9
    179 10 1024 mmcblk0p10
    179 11 8192 mmcblk0p11
    179 12 102400 mmcblk0p12
    179 13 16384 mmcblk0p13
    179 14 16531456 mmcblk0p14
    179 15 819200 mmcblk0p15
    179 48 4096 mmcblk0rpmb
    179 32 4096 mmcblk0boot1
    179 16 4096 mmcblk0boot0
    253 0 2600764 dm-0
    253 1 8388608 dm-1

    Basic_data_partition = Windows
    EFI_system_partition = Windows EFI bootloader (ESP)
    Microsoft_reserved_partition = Windows ???
    android_boot = Android boot image – Linux kernel + initramfs – can replaced with a custom image (custom kernel, etc)
    android_bootloader = Android bootloader – pressing volume down key and selecting Android in dual-boot menu boots device here
    android_bootloader2 = Android bootloader backup
    android_cache = Android cache – used to store recovery logs, etc
    android_config = Android persistent data – wifi/bt MAC address, etc
    android_data = Android user data – user apps, app data, settings, dalvik cache, etc – doing a factory reset wipes this partition
    android_metadata = used to store decryption key for /data encryption
    android_misc = not sure if used
    android_persistent = used for Android’s FRP (factory reset protection) feature
    android_recovery = Android recovery image – selecting ‘recovery’ option in bootloader boots device here – can replaced with a custom image (e.g. TWRP)
    android_system = Android OS itself – can by replaced with a custom image (e.g. CyanogenMod, Remix OS, etc)

    #47136
    Riccardo
    Participant
    • Posts: 39

    Thank you for the explanation.

    So, nothing could be done to give some more space to Windows O.S. since all the partitions seems to be absolutely necessary…

    #49225
    Eric Dunn
    Participant
    • Posts: 11

    I have also asked this question. Would it be possible to decrease the Android OS partition size without damaging it? On my phone, there are 3 main “drives” I assume they are partitioned accordingly. There’s a device root (represented in ES as “/) where I’ve learned not to tinker. This contains the android OS, drivers, etc. But then the onboard SD card, I can wipe in a recovery without problems. The android OS appears to be appropriately allocated in its normal partitioned environment on the iWork8 AIR. So my question is, Is the 8 GB partition volatile? As in, if we used Windows Disk management, we could essentially delete this partition, build a new Fat32 partition, and then use the Expand utility in Windows 10 to expand it over into the unpartitioned space. Would this way of thinking be correct?

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.

Lost Password

Skip to toolbar