I feel that this was more happening on TJC than here, probably because those impatient people left the boat since then (or maybe it’s because I don’t follow this forum as much as during the initial TJC years)
I do want to join that discussion 
, because that’s why personally I have kind of the same feeling than @diegoc. The 4.0 indeed brought a few regressions on (I think) some core features of a smartphone:
- Call recording doesn’t work anymore, it needs to be re-enabled with terminal
- Call recording only works after reboot
- Bluetooth can only be enabled after reboot
Just about the Bluetooth issue, the thing is that it was reported during the Early Access, but the 4.0 was released anyway without any comment from a Sailor. I understand they can’t spend all their day on this forum, but the release threads are generally important to discover major issues.
After hitting those issues myself and digging here, I actually discovered that they might not be related specifically to the 4.0, as the bug reports I’ve linked above are for the 3.4. So probably, those bugs are not easily reproducible and hit only a few of us? ← this is where I would love to see Sailors proactively jumping in:
I would like to have proper statements for such issues:
- Hey, we’ve seen that a few of you have this/that major issue but we can’t reproduce consistently on Sailfish X. We advise you to reflash
- Hey, this is indeed a major regression and we have a fix but it’s too costly to release a patch for it, bear with us until 4.1!
I can’t imagine that Jolla’s clients can accept a broken Bluetooth or call recording, so currently I’m left wondering if I’m one of the few unlucky that need to reflash or if 4.1 will improve things, and in the meantime, I need to run scripts to restart things when I need them. If I need to reflash no problem, I’ll be sad to still not be able to recommend Sailfish but that’s it!
Personally that’s this uncertainty that makes me feel a bit forgotten.