Thanks for this info. Sharing this with the team to check and resolve ASAP. No need for a bug ticket.
1 Like
Android Auto Update:
I just got a report from the QA team members who tested Android Auto on the v3.6 build. The testing was done using FP5 and the build is the 3.6-a15-20260312593772-official-FP5
The issue is reported here in gitlab.
You may not be able to read the QA comments as he marked it the response as internal. The summary is that Android Auto is working in their tests on v3.6.
Suggest you share your issue details on the same bug ticket in gitlab. They may need as much detail as possible.
2 Likes
I’m a little confused. Will there be A16 for the Oneplus 5 (“cheeseburger”) or not? The lists are not clear in this regard.
The list of devices was the first set. We will be adding more devices to the A16 list in the coming releases.
1 Like
Yes, the certificate has been renewed. FOSS Warn can successfully (re-)subscribe. The UP example app does not work, but this may be a temporary problem.
Hi ,
Could you please share some info about issues on avicii , I could not find info on gitlab or test channel
it’s a great affordable official device we’d like to be upgraded to 3.6 , either on A14 or better
Right now only A14 is 3.1.1 which is a real problem
Can you confirm that both upgrade paths will be supported when the OTA upgrade issues are resolved ?
A12→A16
A14→A16
Or we ‘d better stop installing A14 if it’ will be a dead branch ?
3 Likes
Thank you very much @Manoj for this information. When you said all Fairphone can upgrade to A16 or on another, it’ for the few days or few weeks or more time ? I search a solution to protect my FP3 with A13 and if the OTA will arrive so fast, it’s ok, but in other case, I search a other solution.
Thanks for the e/os work !
Update from the QA team:
We have tested both, but the approved path is A12 to A16. Which will be OTA
- Those on A14 will have to sideload the build when it is released.
- Known issue: Icons/Folders on the launcher will get reset when upgrading from A12 to A16.
- In both the cases, a full backup of the device data must be taken before proceeding.
The testing team is still working on the builds. Unless we get their go ahead the official builds will not be released. No major issues detected but we are waiting for further inputs from the testing community.
3 Likes
Thank you note for delivering A16 just 5 months after A15, qnd for keeping devices alive and private.
Keep up the amazing job 
4 Likes
Hello,
I’ve just upgrade my Avicii OnePlus Nord from A14 unofficial to latest A16 unofficial successfully, many thanks to the TEAM for releasing so quickly 
. I’ve upgrade with sideload method and all went smooth without errors.
However, Wifi Display is broken since A16, could you tell me please where should i report this issue ?
Thanks
Most likely here:
Might wanna search if there’s a similar report already.
2 Likes
You can report issues on Gitlab
2 Likes
Hello @Manoj are there any news on availability of documentation regarding Unified Push (push.murena.com) used by integrated foundation.e.ntfy and maybe even providing status-information on eg https://status.e.foundation/?
3 Likes
Will pass the suggestion to the team.
2 Likes
This topic was automatically closed after 7 days. New replies are no longer allowed.