Sir,
Most of your builds are for mobiles which are no longer available for sale. If i want to install a eOS on brand new phone, there is hardly any option available. I request you to kindly build ROMs for mobiles which are atleast available in market for buying.
All of the phones listed at the top of this thread are available new according to gsm arena, even the Sony Xperia Z3 Compact which is quite an old phone with it’s 2014 release date! There’s a few listed on ebay uk.
One of the reasons why we still support ‘old’ devices is to avoid e-waste. Not everyone can afford to throw away their phones after a year of use…even those that can afford to do it prefer to retain the old smaller, easy to use handsets. Having said that we do plan to add newer devices to our our list. the problem is to get hold of their source code to port them.
It is greatly appreciated that you recognize the need for supporting older phones.
When you already have an old phone, then it is obviously most sustainable to use that for as long as possible.
If you want to buy a used phone, then important details to watch out for is that it a) is supported by /e/ (or at least supported by LineageOS which should make it more likely to later be supported by /e/ as well), b) has replaceable battery (so it can last much longer).
Samsung Galaxy S3 i9300 fits the above requirements and used to be popular as used phone, also because of its modem isolation The similarly branded and seemingly slightly more popular i9305 is not supported in LineageOS.
Nowadays i9300 and i9305 are disappearing (at least in Denmark where I live), and is also arguably too slow to run the newest releases of Android.
It seems the best option that fits the above requirements nowadays is the Samsung Galaxy S5 Neo.
Please consider adding support for that model in /e/ - it is supported in LineageOS and works fine there.
Please note the ‘Q’ builds have been updated in the table above…more devices are being added to the list. The zip files are tagged ‘dev’ which means testers will not need to manually flash the official builds when they come out later.
Any chance to get the public repos on gitlab updated to reflect the new builds? Specific fatal errors in the public repos make me think that they don’t reflect what got released…
Yes. I did a factory reset first and (just in case) tried to install it via adb sidelload and TWRP install function and it was always the same. The image might have been corrupted during download (I didn’t find a checksum the verify its integrity) but at least during install there was no error.
Did a clean install (format data, wipe etc) eOS Q on Oneplus 3T but it failed.
All steps seemed to go ok through to the bouncing ball for a minute or so (is it only me by the way who sees the e logo with the bouncing ball as the back end of a dog with a bouncing poo? Might be too many failed installs on my other device! ) but did not get as far as “my data is MY data” and rebooted into recovery (twrp).
I tried rebooting recovery again, then system, same result. So it’s powered off for now.
@chrisrg@ff2u all : We have started a new build for all devices with updated vendor source code…that could be the reason these builds are failing
Will update the links to point to the new builds once they are available