The deployment to Nextcloud 30 (v30.0.14.11 ) was successful, bringing better performance, numerous fixes, and exciting upgrades.
You can view the full changelog here
7 Likes
The FP4 vendor updates will come along with v3.2 release. The changes have been made in the code. Expect v3.2 to come out by mid October 
3 Likes
The following devices will not be receiving the A15 builds in v3.1.4 release. The reason as mentioned earlier are upstream changes which came after the code freeze. We will target release of A15 build for these device along with the v3.2 release .
| Vendor | Device Name | CodeName |
|---|---|---|
| ASUS | ZenFone 8 | sake |
| Essential | Essential PH-1 | mata |
| F(x)tec | ProĀ¹ | pro1 |
| Fairphone | FP3/3+ | FP3 |
| Fairphone | FP4 | FP4 |
| Pixel 4a 5G | bramble | |
| Pixel 4a | sunfish | |
| Pixel 8a | akita | |
| Pixel 5a | barbet | |
| Pixel 3 | blueline | |
| Pixel 3a XL | bonito | |
| Pixel 9 Pro Fold | comet | |
| Pixel 4 XL | coral | |
| Pixel 3 XL | crosshatch | |
| Pixel XL | marlin | |
| Pixel 5 | redfin | |
| Pixel 3a | sargo | |
| Lenovo | Z5 Pro GT | heart |
| Lenovo | Z6 Pro | zippo |
| LG | G7 ThinQ | g710ulm |
| Motorola | Moto G7 | river |
| Motorola | edge 40 pro | rtwo |
| Motorola | moto g84 5G | bangkk |
| Motorola | Moto Z3 Play | beckham |
| Motorola | edge 20 | berlin |
| Motorola | edge 2021 | berlna |
| Motorola | moto g power 2021 | borneo |
| Motorola | moto g10 | capri |
| Motorola | moto g30 | caprip |
| Motorola | moto g9 power | cebu |
| Motorola | moto g32 | devon |
| Motorola | edge 30 | dubai |
| Motorola | Moto G6 Plus | evert |
| Motorola | moto g 5G - 2024 | fogo |
| Motorola | moto g34 5G | fogos |
| Motorola | moto e7 plus | guam |
| Motorola | moto g9 | guamp |
| Motorola | moto g42 | hawao |
| Motorola | Moto G 5G / Motorola One 5G Ace | kiev |
| Motorola | Moto G7 Plus | lake |
| Motorola | moto z3 | messi |
| Motorola | edge 30 neo | miami |
| Motorola | Moto G 5G Plus / Motorola One 5G | nairo |
| Motorola | Moto Z2 Force | nash |
| Motorola | Edge S / Moto G100 | nio |
| Motorola | Moto X4 | payton |
| Motorola | edge 20 pro | pstar |
| Motorola | moto g52 | rhode |
| Motorola | moto g82 5G | rhodep |
| Motorola | moto g200 5G | xpeng |
| Nubia | Mini 5G | TP1803 |
| OnePlus | 7 | guacamoleb |
| OnePlus | 7T | hotdogb |
| OnePlus | 9 | lemonade |
| OnePlus | 9 Pro | lemonadep |
| OnePlus | Nord N200 | dre |
| OnePlus | 5T | dumpling |
| OnePlus | 7 Pro | guacamole |
| OnePlus | 7T Pro | hotdog |
| OnePlus | 8 | instantnoodle |
| OnePlus | 8 Pro | instantnoodlep |
| OnePlus | 8T | kebab |
| OnePlus | 9R | lemonades |
| OnePlus | 9RT | martini |
| OnePlus | 11 5G | salami |
| Razer | Phone 2 | aura |
| Realme | 10 Pro 5G | luigi |
| Realme | 9 Pro 5G | oscar |
| Samsung | Galaxy A52 4G | a52q |
| Samsung | Galaxy S10 5G | beyondx |
| Samsung | Galaxy Tab S5e | gts4lv |
| Samsung | Galaxy Tab S7 | gts7lwifi |
| SHIFT | SHIFT6mq | axolotl |
| Sony | Xperia XA2 Ultra | discovery |
| Sony | Xperia 10 | kirin |
| Sony | Xperia 10 Plus | mermaid |
| Sony | Xperia 1 II | pdx203 |
| Sony | Xperia 5 II | pdx206 |
| Sony | Xperia 5 III | pdx214 |
| Sony | Xperia 1 III | pdx215 |
| Sony | Xperia 1 V | pdx234 |
| Sony | Xperia XA2 | pioneer |
| Sony | Xperia XA2 Plus | voyager |
| Xiaomi | Poco F1 | beryllium |
| Xiaomi | Mi 6 | sagit |
| Xiaomi | POCO F3 / Redmi K40 / Mi 11X | alioth |
| Xiaomi | Mi 10T / Mi 10T Pro / Redmi K30S Ultra | apollon |
| Xiaomi | Mi MIX 2 | chiron |
| Xiaomi | Redmi K20 / Mi 9T | davinci |
| Xiaomi | Mi 8 | dipper |
| Xiaomi | Mi 8 Pro | equuleus |
| Xiaomi | Redmi Note 8 / 8T | ginkgo |
| Xiaomi | Redmi 7A / 8 / 8A / 8A Dual | Mi439 |
| Xiaomi | Redmi 4A / 5A / [Note 5A / Y1 - Lite] | Mi8917 |
| Xiaomi | Redmi 3S | Mi8937 |
| Xiaomi | Mi A3 | laurel_sprout |
| Xiaomi | Mi MIX 3 | perseus |
| Xiaomi | Mi MIX 2S | polaris |
| Xiaomi | Redmi Note 10 Pro | sweet |
| Xiaomi | Mi 8 Explorer Edition | ursa |
| Xiaomi | Redmi Note 7 Pro | violet |
3 Likes
Some bad news for users of these devices.
- They would not be getting the v3.1.4 build on A14.
- The devices are also failing builds as their system partition size limitations is not allowing us to build for them.
- We will be making another attempt to build for them with v3.2 if that fails we may unfortunately have to drop these devices.
| Vendor | DeviceName | CodeName |
|---|---|---|
| Motorola | Moto G6 Plus | evert |
| Motorola | Moto G7 Power | ocean |
| Pixel XL 2 | taimen | |
| Pixel 2 | walleye | |
| Motorola | Moto One Action | troika |
1 Like
Still waiting for v3.1.4 for FP5 (official) - or any info at all if or where the build has been stuckā¦
Is there a location to see as a user if your build has failed?
āThe reason as mentioned earlier are upstream changes which came after the code freezeā - do your devs not see these changes before trying a build? It would be fantastic if you find a good way to avoid this situation happen again and again / possibly throw out these āupstream changes after code freezeā or something like this.
1 Like
official builds are released towards the end of the release cycle.
1 Like
You can try to adopt from here what I wrote to almost the same comment above
Throwing out the upstream changes is definitely not a good solution. There is active development and debugging ongoing on the A15 device trees. A working build is anytime better than a non working buggy release.It is good in that bugs and issues are being fixed. While we are trying to work out a code freeze timeline which works the challenge is the large number of devices we support.
1 Like
OnePlus Nord is in testing phase for OTA update from A12 to A14 since many months nowā¦ what are the issues??
any page with something related? thanks
1 Like
I got the official 3.1.4 for FP5 right now.
1 Like
Would that be the official or the community release Manoj?
It should be for both.
Ah, thanks, I wasnāt sure :).
I see others already getting the fp5 build hours ago but it doesnt show up for me yet. Guessing it will show up later today or tomorrow?
1 Like
Welcome ! There are a lot of nuances between every release. After about a year of following these topics, I think I finally understand a little.
The move from Android 14 (A14) to A15 is going to happen at a later time for the OTA update method. If Iām correct, this was planned for October or November when 3.2 or 3.3 arrives.
No, this is only true for the Android T release, not the a14 one. As given by the initial post, the upgrade from a14 to a15 should have been with the 3.1.1 release.
I was also surprised that my phone didnāt upgrade to a15 with the 3.1.1 update and the updater instead only chose 3.1.1-a14.
So I also would like to know whether my 3.1.1-a14 version can update via the updater to 3.1.4-a15 because my phone does not find the update as well. Should we just wait (and search for the update manually via the updater), or was 3.1.1 the only upgradeable build and now were kind of stuck for the moment?
Maybe @Manoj can give us insight into that?
1 Like
Hit the refresh button in the updater atleast 5 times to āforceā it. But also be aware of being one of the first
Doesnt work for me 
Checking on this with the team. Will update.
Update: QA testing for the official FP5 upgrade from A14 to A15 OTA OS upgrade is in progress. Release has been pushed to v3.2 : ETA mid October
4 Likes