From month now, my Samsung A5 2017 (a5y17lte) are stuck to the version e-1.8.1-20230206257879-a5y17lte.
What can I do?
I bought two (quite) similar devices, and I was happy to flash them and use them with /e/OS. But since some month now, there is no more updates.
What happens?
I suspect a lack of testers for this device, but not sure. Something else?
If it is a lack of tester, is there something I can do? These devices are for a day to day use, I cannot flash them with an unstable system. Should I buy an other device to run tests on it? But if so, does it worth the price? If buying an other device perhaps should I chose a more recent and supported one.
Any other way to add confidence for the dev versions of /e/OS?
Find thousands of reconditioned Galaxy a5 (2017), convince the e-Corporation managers to put such “old” models in their sales catalog, and find thousands customers to buy them…
(in my opinion, the last point should be the easier)
So far so good.
I test a bunch of apps/ connections to mostly stuff I run on my home server.
Account syncing with murena and two nextcloud instances.
Camera, audio, calling worked too, but only test them briefly.
I should look for the /e checklist and really tick things off
@eloi.rivard I did not have any show stoper, but I don’t make a lot of calls, so this is untested on my side. My daily driver ist still a Galaxy S5, with a 2nd S7 on a custom T-build from @ronnz98
