Building devices for which Q upgrades failed during the previous weeks
This list will include a few new devices.
The device code names and the OS on which they will be released are
19 Mar
I have been told the release for these devices will happen early next week
FP3 OTA update
There was an issue with the OTA server which was fixed. Pl recheck if you are able to see the OTA update on the Dev channel…
Pl note if you have purchased your FP3 from the eStore you would not be be able to see the update as the stable channel builds have not been released. ETA for stable channel builds is end of week.
22 Mar Update
Apologies for the delay in the release of the stable 0.15 builds. Some device users reported the build was not booting automatically. The team has been asked to check why this is happening. The release of some of the builds which failed during the upgrade was also not done last week.
Hope to clear out this backlog by the start of this week.
22 Mar Update The Stable builds are being rolled out today. Should start showing up for various devices by end of day.
One of them is sailfish (Google Pixel). I’m patiently waiting for the Q-version. Any idea why builds for this particular model seem to fail constantly? Any hope for us waiting?
good news.
Can’t wait to try it out.
Will the update be offered via OTA or will it have to be done via TWRP?
If second option, a quick tutorial would be appreciated.
I see that Bacon is not in the “good list” again. In the “List of issues” I don’t actually get much information. Could you “filter” more details about what’s failing?
Will update once Bacon and the other remaining devices get built. Some of these devices have an issues with limited partition size which means they cannot support the full compliment of /e/ apps. That requires a minimal build to be made for these devices.
Will update if there is any progress.