Now that there are no more security updates for AOSP 13 are there any initiatives to move the Murena Two to a higher version? I see that other older devices support versions above 13. I think that it is a bit strange that I need to say goodbye to an official Murena device after just 2 years because of this while other brands get more support.
The lists mentioned only the community builds. All official builds devices are candidates for upgrade to A16 where possible. The only issue is the ETAs are to be decided when the A16 official builds will be available. Unlike community builds official require OTA OS upgrade features which require more development and testing efforts.
I have been a Murena Two & /e/OS user for almost two years now and wear my supporter t-shirt proudly, talk about /e/ as much as I am given the opportunity.
With the recent 3.6 update, when I looked at the release notes I saw that scary bit:
Security patches are no longer available for AOSP 13.
I have created a support case, and received the answer saying that maybe an upgrade will be available without guarantee.
I would like to understand my options, I understand there are community builds but have never taken the time to look seriously into it. I was hoping that Murena would continue to provide security updates for at least 2 years.
If anyone has ideas, I would be willing to follow. I only have that phone and do not like the idea that its OS is end of support.
Do you have an idea as to approximately how long this could take? this is just to have an idea… I work in cybersecurity and feel bad to know I cannot apply security fixes, so keeping my fingers crossed for no vulnerability to be published on AOSP13.
Also, I would be willing to help, early tester or whatever so don’t hesitate to ask
No ETAs available as yet. There is a lot of development activity in progress on getting the OTA OS upgrades working.
The OTA OS upgrade on official builds requires the OS to update all the app data seamlessly across OS versions. This is slightly tedious development. The easy way out would be to ask users to take backup and then flash first the upgrade build and reinstall all the apps. That is the not the user experience we would want for our official builds.
Will share ETAs once I get them from the development teams.