Didn’t you already update to 3.8.0? 
If you switch to stable now, you’ll only receive the next stable release, since you are already on the latest version.
I’m on 3.8.0 beta (even if this is not shown anywhere?). But you were on 3.8.0 beta, too, no?
If you are on 3.8.0 already, switching to stable won’t change anything.
Beta and stable are release channels, if you switch you’ll get updates once they are pushed to the corresponding channel, the actual update is the same.
You generally get releases earlier in beta and stable might skip versions that contained bugs, but you usually don’t get releases that are specific to one channel, the major difference is the timing.
Sounds valid and it seems I missinterpreted the usage of beta and release. I had the idea to get the beta early and switch to stable later ;-). Let’s see if I get 3.9.0 (as I switched to release now). Thanks once more 
.
Regarding this.
I still didn’t find the time to work on a little Magisk module for this.
But for those who want a simple way to have swipe / glide-type in German back, can install this OpenBoard build one created. Release Open Board with Gesture Typing v1.4.4 · erkserkserks/openboard · GitHub
Discussed here in this issue (so not yet integrated as there are some concerns about the source of the library etc … but this would be the same when flashing the library from gapps).
For me it pretty much feels like using ASOP + flashed swipe lib.
For swipe / glide-type in English FlorisBoard works great as well.
1 Like
3.8.0 is running great 
I can’t find the following funktion (source: changelog):
“Settings: Allow user configurable fingerprint wake-and-unlock (for FP4)”
Can anyone give me a hint?
As 3.9.0 is on it’s way: Issues · CalyxOS / calyxos · GitLab
Did you @hirnsushi / @Singulus turn this off?
I did turn it off, but the next release isn’t even marked as beta yet, we still have to wait until it’s actually released.
Sure, just wanted to ask for this setting and express my surprise that the git-issue for 3.9.0 is already there, as we just got 3.8.0. 
I know/understand that there is some time we have to wait until it is beta and or stable.
The end of one release cycle is always the beginning of the next, that’s the ciiiircle of life 
I’m very exited about this part:
Notes: Final 12L build for most if not all devices.
Android 13, here we go 
2 Likes
It felt like there was more time between the builds, at least git-issue-wise.
Saw that as well. 
Will such a change be possible via OTA or does it mean - flash a new factory image - or so?
I hope you are right, because on their news page it sounds a little bit different:
The aim is to get some builds out ASAP for the Google supported Pixels, i.e. Pixel 4 - 6a, and then we will spend some time looking at the Pixel 3, 3a and Fairphone 4, see what is possible and post an update.
I did not turn it off.
Hi,
On Matrix (CalyxOS testers), when someone asked on Tuesday where to download 3.8.0 stable coming from stock ROM, they were answered to wait until the latest factory image and flasher to be on the website. I wanted to install Calyx this week-end, but I don’t mind waiting if I should. The question is: why is it better to wait than to install an earlier version and to upgrade? Would it change something with the security patch level and the bootloader issue?
It makes no difference if you install 3.8.0 and then update to 3.9.0 or if you install 3.9.0 directly. Maybe it’s because they want to get their device flasher released for FP4, you currently still need to install CalyxOS manually.
3 Likes
But they were talking about the 3.8.0 factory images, not the 3.9.0. So instead of flashing an earlier release and upgrade to 3.8.0, they were told to wait until the 3.8.0 factory image and the flasher would be on the website.
As I saw in the meantime that others flashed Calyx anyway, I just wondered why it was considered better to wait. Maybe it is only related to the flasher, as you said.
If you are at least somewhat familiar with the command line, you don’t need to wait for the device flasher to be available. It’s only the install process that gets easier.
Just get the 3.8.0 factory images and go ahead.
If you are thinking about locking the bootloader, please read a bit in the forum about the risks involved.
At least check fastboot flashing get_unlock_ability after the first boot.
Make sure you don’t flash an older patch level (which you aren’t in this case), check Settings → About phone → Android version now and after you flashed.
Maybe the misunderstanding / confusing thing about this
for you (@chrisse ) is, that this beta state and than stable / factory image availability for a new release is not the same as CalyxOS official support for the Fairphone (which would mean an official page with download links etc. … e.g. the same thing the Lineage users wait for).
You always have to search for the factory image (link) on your own or put it together manually (or wait until @hirnsushi is so kind again and post it here). This topic was discussed here: Howto install Calyx OS on FP4 - #39 by Smojo
Thank you for all your answers.
The confusion is actually between the differences read on this forum and on Matrix. I had read everything on this forum and @hirnsushi had already answered my questions. Then when I saw that someone in the same case than I was told to wait on the CalyxOS testers channel, I just wondered if there was something else I didn’t get. I wondered why they weren’t told exactly what you just told me (and which was what I already had understood by the posts on this forum).
Thanks for taking the time to answer me! I will do as you say to flash calyx tomorrow.
2 Likes