here are the parameters of this upgrade :
I have the same situation. FP3 Stable Android 9 and no update 0.20 → 0.21.
Thank you! They helped me get access to GitLab.
Re: Bluetooth crashing / car audio… it sounds like there’s at least a few reports in the issue tracker. Here’s one: Random bluetooth crashes (#3887) · Issues · e / Backlog · GitLab
This one actually has some logs attached: starlte : Bluetooth crashes on trying to connect to bluetooth car audio. (#4748) · Issues · e / Backlog · GitLab (but it is re: starlte, not star2lte).
Anyway, let me know if there’s more I could do. For example: try to repro, capture logs, screenshots, whatever might help.
Okay, I thought it was such a problem. Now I’ve blacklisted, thanks.
Anyone else have the problem of the switch between cameras?
Hi @meonkeys,
Thank you for your feedback and I have the same camera icon over the zoom slider in the camera App with my S9 (Starlte with V0.21Q)
Can you confirm me if the slow charge mode is working fine on your S9+ ? Mine is not working and I 'd like to know if it is only on the S9. You can find the details in these following Gitlab issues:
Slow charge mde inoperative and some settings reset after reboot.
Thanks,
@Manoj
Hello Manoj,
Like Hermano and Eugene_72 wrote, I also bought my FP3 stable Android 9 in the /e/ shop.
But till now there is unlike what is mentioned at “https:gitlab.e.foundation” no update from 020–> 0.21.
Thanks, Huib43
1 Like
Update of my Murena S9 OTA without any problems. Thank you very much.
I’m awaiting the update to R. 
1 Like
Yep, I’m seeing both of those on my S9+ / star2lte.
Hello all,
I made the S9 OTA Upgrade to Android 10 (incl. encryption during upgrade). (I use the stable version).
I noticed a very strange behavior. During the first hour after the upgrade, my S9 was permanently rebooting every one or two minutes without special activity. Without doing anything, it stopped rebooting, and seems to be now stable. I suspect Android disabled the guilty app or service, but I have no clue what it could be. I guess some logs should be able to tell me more, but I have no clue where to look for. Any help to allow me to understand what went wrong is more than welcome ! As the issue is not understood, I am afraid it could pop up randomly.
Cedric
The stable build for FP3 was released and should be visible on your device. Let me check with the team again and get back
@huib43 which version of the OS are you looking for the FP3 …Q or Pie
1 Like
Dear @Manoj ,
As a few of us told before, we know it was released but we are not getting the update.
Cheers
Looks like they are still on Pie, as being on Q would still require a manual upgrade on an FP3. So it seems they are looking for the 0.21 Pie update which wouldn’t be covered by https://images.ecloud.global/stable/FP3/.
4 Likes
Thanks @AnotherElk
Hi @Hermano @huib43 if you are on the Pie stable builds, then the release has still not gone out. I checked with the team a little while back, and they said they can look into this on Monday…tomorrow
2 Likes
Hello @Manoj
Just like @AnotherElk said I am on the Pie stable build.
Thanks for your attention
Huib
Whilst reading about, and downloading the new updates, please donate to the foundation, to ensure this software keeps being supported.
These people don’t have Apples resources or income stream.
One off or monthly. I have just made another donation.
I know times are hard for many, but think how much you will save by keeping your devices longer!
6 Likes
Is funny, because I have been using dark mode in Oreo without a problem.
On my FP3 that is rooted using Magisk 24.1 and where I have enabled the staging OTA server in the developer options menu, I got offered the following OTA update today:
https://test.ota.ecloud.global//builds/full/dev/FP3/e-0.22-q-20220205161668-dev-FP3.zip
I’ve tried this three times now, both with and without using Magisk to root the freshly flashed image before rebooting, and I reproducibly get the following error upon reboot:
[e logo]
Recovery
Version 0.22 ()
Active slot: bCan’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
- Try again
- Factory data reset
I could fix the error without data loss by not performing a factory data reset, but instead using fastboot --set-active=a to switch back to the old firmware slot, but you might wanna consider retracting that OTA update before it causes problems to more people (even though it’s a staging update).
Regards
Pascal
It’s there for testers. And installing on phones with Magisk installed is not comething I’ve seen on any of the test plans. It would be great if you could raise a gitlab issue, so that this does get tested befor release to non-tester users
Enabling OTA server options is for testers. v0.22 has not been released or QA tested as yet. Pl wait for the tested version to be released or if interested you can join the testing team.
1 Like