The chances of the older devices being dropped are high as they are already EOL. The team is facing difficulties in building on latest OS versions for these devices. A final decision on if these devices will be dropped is yet to be taken.
2 Likes
It still does not appear on /e/OS official FP6 download
1 Like
Interesting, I donāt know more then that the update server has it.
Same here.
Iād wait until Monday, even if the wait is annoying.
If the update still isnāt available on Monday, Iād say thereās a problem.
Looking at the details of the 4.1.1 update as it is listed on
https://ota.ecloud.global/api/v1/FP6/official/
I noticed that it says
"is_upgrade_supported": false
which I think means that it will never be listed in an FP6 updater.
I also think that it can be used for a wipe-and-clean install. But I did not (and will not) try.
/e/ has a convention to refer to Android version upgrade as an Upgrade while an update of /e/OS version is an update.
That list is of OTA updates. If and when a release is organised as part of OTA Upgrade (only on an official release) then that line is true.
In that case, Iād say thereās a misunderstanding or a miscommunication.
Either the upgrade to Android 16 has been approved for the FP6, or it will remain on 15.
I also noticed the line with āis_upgrade_supportedā: false and thought it was odd that there was an inconsistency in the information.
These things can happen, but I expect it will be fixed soon.
@Manoj Can you clear this up with the development team plesse.
Notice:
FP6 is still listed here in the Weekly Update as āunder development,ā but in the release notes itās already listed under the upgrade to Android 16.
Surely itās the last A15 version that needs to be shown as upgradable, as indeed v4.0 does. Same as for the FP3 where the last A13 (t) version shows as upgradable, but not the first A15.
I donāt think thereās any need for @manoj to bother the developers here. The release notes show the FP6 being upgraded to A16 in v4.1.1.
All thatās needed here is just a little patience.
2 Likes
The FP6 is kind of a bad example to learn about this because it didnāt need many upgrades yet, but just have a look at e.g. https://ota.ecloud.global/api/v1/FP3/official/ and which builds there are marked as true, and you will clearly see it is as @dave says.
The builds you can upgrade from are marked as true.
2 Likes
The FP6 A16 should be released tomorrow 27 July.
Once it is released will move the device name from āUnder Development and Testingā to āCompletedā section.
5 Likes
For future reference and for understanding the process ā¦
Since https://ota.ecloud.global/api/v1/FP6/official/ is offering the upgrade already, is this not the server consulted by the /e/OS updater on the FP6, or is there some additional blocking in place we canāt see and which then gets removed to āreallyā release a build to the updater?
local transcribe works well enough (vs some details). Thereās no post yet celebrating that, congratulations!
For others: using a multilingual model is a good choice, simplifies the code at some cost to perf, but makes alternating language input possible - the 600mb model is saved at
/data/user/0/foundation.e.stt.offline/files/parakeet-tdt-0.6b-v3-int8
info on the model at nvidia/parakeet-tdt-0.6b-v3 Ā· Hugging Face
3 Likes