I gifted myself with a Murena ShiftPhone 8 for Christmas. It’s all going well, but I found that /e/OS is seeing only 256GB of internal storage, although there should be 512GB. The phone is a ShiftPhone 8.1, which got a small hardware update compared to ShiftPhone 8 (not storage related) and for this model there is not even a 256GB option. There is 512Gb written on the sticker under the battery as well. So I’m pretty sure the phone should have 512GB. Is there anything that I could check myself? There is no SD-card in the phone and this issue was there for the initial /e/OS version and then for 3.3 too. I tried to reach support through the contact form already, but I got no answer.
It was my first time with adb, I hope this it what we should look for. What I noticed is that /data and /storage/emulated are both 200-200GB in total, so it looks like the device has more than what it reports. I’m aware that there are some other partitions too that need space and the OS itself is relatively big too, but I would’ve imagined more available space. Is this something that I should go forward somehow?
adb shell df -h give us the volume handled by the system /storage/emulated (internal_storage) is the major part of /data witch is also contain the apps
it could be larger than 200GB as the device have a 512GB emmc
.
to highlight potential usused space, we need aditionnal tool named parted to read the partition table :
open a terminal from the folder were parted have been downloaded,
boot the phone into recovery mode, and in its advanced menu, enable adb,
then run
here we will just watching, no changes will be done
we will use the print free command that is : display the partition table, and available free space
even if the tool is expected to have feature to make change :
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) help
align-check TYPE N check partition N for TYPE(min|opt)
alignment
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkpart PART-TYPE [FS-TYPE] START END make a partition
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resizepart NUMBER END resize partition NUMBER
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
disk_set FLAG STATE change the FLAG on selected device
disk_toggle [FLAG] toggle the state of FLAG on selected
device
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted)
if the factory reset doesn’t help I’d file this with the backlog, but also make a photo of your early fastboot screen (will show flash disk size) to exclude the issue of a wrongly shipped unit.
Partition sizes are handled through BoardConfig.mk in the device repo, but the variable BOARD_USERDATAIMAGE_PARTITION_SIZE isn’t set (removed from most repos), so I guess it’s handled at time of flash but don’t know better.
Sorry for overlooking. After restarting into the “Android” menu, I see Advanced, but that only has the following options:
Enter fastboot
Reboot to bootloader
Reboot to recovery
View recovery logs
Power off
I tried Reboot to recovery, but that brings me back to the same menu. In the main menu, there is Apply update, there I can select Apply from ADB, under that there is ADB Sideload, is that what I should look for? There are no other options for me mentioning ADB anywhere in the menu.
OK, now I’m sure I don’t have the “Enable ADB” under Advanced. Is there any setting anywhere for that?
If nothing’s left, I’ll give it a go, but I read this in this post:
Does this mean anything that I should care about? As long as I know, there is a factory reset through Settings → System → Reset options → Erase all data (factory reset), and another one is under the Recovery menu (or whatever Power+Volume down called).
Again, I’ve run CLI stuff before, but I have no knowledge about adb, nor parted, nothing.
