I use old Moto E condor phones to test and play with /e/OS because I have several of them we used to use at work. A few months ago my latest best friend didn’t start anymore while it was running great before.
This week I found another Moto E and I immediately unlocked it, installed TWRP and downloaded the ‘latest’ rom. I was surprised to see that the latest rom was from november 2019 while other models have roms like e-0.9-n-2020051554230-dev-osprey.zip.
I built a Nougat ROM for Condor a couple of days ago, to check out my build setup. I’m quite happy to make another one if it’s any help? I can make sure it runs - I have a spare device here - but it would be an unoffical build, and at your own risk.
Pete
I would like a have a ROM for my condor MotoE.
It’s nice to honor the MotoE some more before it (they; I have a number of them) goes to charity where it will be recycled.
First it was my work phone somewhere in 2015. Then it became my loyal /e/ phone (I made a few bricks of it too). And now it wil become my pete phone. And after that may it rest in peace.
Same problem with Moto E 2015 Surnia, still with unofficial /e/nougat by Unknown… Lovely compact and works fine, but no matter to test last improvements of /e/ ROM… (I can’t build by myself, lack of memory and RAM in my Dell).
Hi trefix
Building a new unofficial ROM for surnia is on my To Do list, because my wife has one of these devices. It’ll be a few days before I do it though
Hope they aren’t failing at 99% with not enough space error or at around 85 % with java error regarding apps.
The out of space error is a bug which is reported long time ago on github and the other seems to be new
I’m building using Docker, so I have no idea how to go about changing the source.
Do I have to go digging around inside the docker image before I call docker run
(Sorry for the dumb questions: I’ve not worked with docker before)