Be advised that their available storage size is limiting the size of /e/ builds.
Therefore, on those devices, starting from today, we have to remove some default apps (LibreOffice Viewer, MuPDF and Signal) to be able to release an installable image.
Regarding Signal, you will be able to install it manually to continue using it.
For Motorola Moto E (condor) and Motorola Moto G (falcon), we also had to remove Telegram. You are still able to install it manually, and you will recover your data by sign in to the app.
each device has a specific amount of internal space set aside for the build. The latest /e/ builds has exceeded the size. This throws an error during the build process. The reason why we did not have this issue with build size earlier is that we have added a number of application that are doing the same function for example QSMS and Signal. This was done to give users an opportunity to migrate their contacts and text messages from one app to the other. As we move towards the release version these āduplicateā apps will be removed and we will only have a small set of default apps. Future version of the /e/ ROM are also going to have the feature of allowing users the ability to uninstall system apps and install apps of their choice.
Not having read āimportant messageā before ordering a 2nd-and Moto G I realise that I may have a truncated version of the āfalconā version of /e/ when I attempt to sideload it using heimdall. But as it has 8 Gb of memory I canāt quite see how this is a limiting factor as I have installed /e/ on my old Galaxy Note2 and even with a fair bit of personal uploads it still only takes up less than 500 Mb of 1.7 Gb available on the internal sdcard. I hope it will be possible to install the missing apps - particularly Telegram, which I use a lot, and also Signal. And that this will not slow up the device which has a gigabyte of RAM according to the specs. I chose this phone partly for financial reasons but also because it has a smaller 4.5" screen. Since I would like to offer it to a lady friend who doesnāt like the big phones of today, I saw this as the only currently available choice with an /e/ build.
Hi @Grendel the space constraint mentioned is an issue which come up during the build process. By default the each device allocates only a specific portion of its internal space for the OS. When the /e/ ROM started to exceed this space we got errors and builds failed. This issue is only with certain slightly āolderā device models. As a solution we removed a few default apps to bring down the ROM size. You can install these applications later in case required.
Hello @Manoj thanks for the info about the moto G Iām still awaiting. The bootloader unlock instructions on the Motorola site look a bit complicated and itās not clear if they still support giving the key but I suppose as you list the phone and have an /e/ build for it, this must be possible. Fingers crossed Iāll manage it by myself!
Hi @Manoj. Iām using the Moto G Titan with /e/ with no constraints so far. It has like a 8GB (if I remember well) for storage and I added a 2GB microSD as an internal storage.
Iāve just installed yesterdayās system update and so far, so good. I have some 9.10GB total space and 7.64GB used.
I donāt have files like music, videos and docs storaged. I am using my own cloud for that with Nextcloud app; when I need a file, I download it and erase it afterwards.
Iām also using ES File Explorer to explore the files and alert me when Iām out of space.
I was considering changing the microSD to a larger one, like 16GB or 32GB. You believe it would be enough?
Anyway, congrats to the great work you and the rest of the team are doing.
Good to hear it Anonyme!
Iām still learning about phones and stuff related. My confort zone is with servers, Linux and I really donāt understand, yet!, how things go with phones and Android.
Thanks for your reply and sorry for taking so long to answer it.