I have e (version .13-xxx, osprey) installed on a MotoG3. Storage shows 4.29 GB of 7.45 GB used. Yet the phone is a 32 GB phone. Any idea why I don’t have the full storage space on the phone.
My Nexus 5 (.13.xx hammerhead) shows 4.15 GB of 29.8 GB used. I know hammerhead is a smaller built but I don’t think the MotoG3 should have so little space left.
Yes, the df command will output sizes for all mounted filesystems.
Si it’s a good start to diagnose your problem
The most interesting will be something with “data” or “sdcard” in mount path.
Please post back the entire output.
I am not at home but when I first configured the phone yes there was something I did with an SD card… must have done something wrong. I was trying to use SD card as phone internal not external if I recall.
Unfortunately, as I expected the filesystem of your data partition (in mmcblk0p42) is clearly undersized
But there is hope : partition size may still be okay, so it could just be the filesystem inside not using all the space …
If you’re willing to dig further, here is a method to check partition size (it’s safe if you follow instructions carefully, please let us know if you need more details) :
make sure you have a working TWRP on phone, and a working adb on PC (should be, as you installed /e/ )
reboot your device to TWRP recovery, plug it to PC using a good USB cable
on PC, go to adb folder within a shell, launch adb devices (should answer with random ID and “recovery” keyword)
put partition tools on phone using (replace <path to tool> with it’s full path where you extracted it, for example c:\adb\tools\fdisk, keep the “” ) :
adb push "<path to fdisk>" /sbin
adb push "<path to gdisk>" /sbin
adb push "<path to parted>" /sbin
issue an adb shell command, prompt will change as you are now executing commands on your phone
issue
fdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
parted /dev/block/mmcblk0 print
exit adb shell with … exit
get your phone back to duty using adb reboot system, don’t close your PC shell
copy and post back the outputs of commands (hint : use “Preformatted text” style, symbol </> above)
Note 1 : partition tools won’t stay on your phone, you’ll have to push them at every boot in TWRP
Note 2 : it’s okay if you find that too complicated, hopefully others will come with a easier way
Can I just re-install e fresh making sure I properly format existing disk space before I install e?
If not I will attempt the above method. In the above method at note 1, does that mean I need to keep the partition tool on the phone to maintain the space?
This phone is my back up so I have no problem starting over.
The purpose of the tools in previous post is just to gather intel, they won’t modify anything if used as instructed
It’s not an easy way, but you can try it safely if you wish.
The note #1 was just informational, in case you’ll have to restart.
The goal was to verify that the partition (see it as a container) is big enough, so we could try to resize the filesystem in it.
Anyway if you can start over with installing, I suggest you first blindly try the “Resize” TWRP option, and the “Format” if the “Resize” does nothing.
I’m not aware of MotoG3, but if your phone is encrypted I suggest the following steps before re-install :
of course, remove any SDCard
disable screen lock or pattern, remove fingerprint, reboot once to system
before installing, regardless of above Resize result, format (not wipe) the data partition using TWRP
I owe you an apology, I have been a bit embarrassed. The phone is actually 8GB not 32GB, sorry for being careless and wasting your time. In future I will be more careful. I had confused the 32GB SD card I used in it at one point.
Not a problem, sometime the best engineers make mistakes too
I’m afraid we can’t do anything for your phone, but it was not a waste of time as this thread could help others !
If this device is still a backup, we could also build an /e/ image with reduced apps set.
See “build options” here.
Unfortunately this will disable the OTA update.