OTA done… Easy peasy. 
Many thanks to the devs!
1 Like
OTA also done. Everything works fine !
Thanks a lot
Here’s the latest build from /e/ e-0.22-q-20220225166118-dev-lilac.zip
It should also be available OTA
Release notes:
3 Likes
OTA done. Thanks a lot
Hi there,
I had a weird stuff going on today with my mobile data. It turns out that /e/ drive used 2Go of sync in a very short time. I have a notification to tell me when I’m using too much data so I found out quite quickly and turn off every synchronisation of /e/ drive I could.
I read some same stuff in the french channel on telegram, and there is a backlog of this specific issue. eDrive consumes a lot of internet traffic (#4853) · Issues · e / Backlog · GitLab
I just wondered if you had the same problem since the new update ?
I’m not using this build - I use my Custom build which is still on 0.21, as I haven’t had time to make a v0.22 build yet. So I’m sorry, but I can’t help.
1 Like
Here’s a new version built by /e/ from the v0-23-q tag
Release notes for v0-23-q
I don’t see it as being available OTA, so you may have to install it manually. Please let me know if it is offered to you OTA, then I can try and find out why I am not seeing it 
Good luck
1 Like
I seeeeeeee the OTA.
(RE “seeeeeeee” - my new 20-character workaround!)
EDIT: OTA completed. No issues.
1 Like
Thanks. I’ll try to work out why I can’t seeeeeeeeeee it
1 Like
Hi there,
I had to make it search for the OTA but it found it and it worked also.
Thanks
2 Likes
Here’s an unofficial Q / lineage-17. build of lineageos4microg
It runs, and the main functions seem to work. You’ll probably need to format the data partition if you’re installing on a device currently running /e/OS.
Unlike my /e/OS builds, this is build from the upstream repos rather than /e/'s forks. I made it to test the work I’ve been doing to get upstream changes (in device, kernel and vendor repos) into /e/, and I decided to share it in case anyone else is interested.
Of course you’re better off using /e/OS though 
2 Likes
If anyone is using the test channel to pick up the latest test build OTA updates, you may see a new update /e/OS 1.0 dated 10 May 2022
DO NOT INSTALL THIS UPDATE
The build is broken and will not boot. If you have already installed it, and you have a TWRP backup of your existing data, you should be able to get your device working as follows.
- If your phone is stuck at the e boot animation, ‘hard power off’ (by pressing and holding volume up and power keys, until the phone vibrates three times in quick succession)
- boot into TWRP (press volume down and power keys)
- format data partition
- reinstall the
v0.23-qbuild linked above - reboot the system
- complete the first time setup wizard, making sure to set the same screen lock (PIN or pattern)
- power off
- boot into TWRP
- restore your backed up data
If you don’t have a TWRP backup fo your data partition, then you probably should not be installing test builds You may be able to create a backup by hard powering off then booting into TWRP as described above, and backing up the data partition.
Please remember that these test builds are not intended for daily use and there is always a risk that
- they may not work
- they may fail in such a way that it is not possible to restore your user-installed apps and settings, and you may have to start again from scratch
2 Likes
e-1.0 has been released for this device.
It will show up as an OTA update, dated 27th May. I have tested the OTA update and it works fine
If you are not currently running a dev ROM, and you don’t see the update, I have uploaded it to AndroidFileHost
I can’t find any release notes for the v1.0 releases. I’ve asked, and I will post details if I hear anything.
Enjoy version 1.0!
1 Like
Hi, thank you again. I don’t see it in OTA, I thought I would because my ROM is dev-keys,dev-release.
But I don’t really know what it means. I’ll try to do it the old way
I couldn’t do it. I got a message (on the terminal) saying that I’m not in the plugdev group, but I’m not sure I should change that.
Do you have any idea why it didn’t say that before ?
Hi, @Xyguma, I do not know the device or why this happened to you, but I stay in the plugdev group without downsides. One place it is described (in a different context) is here : Run apps on a hardware device | Android Developers.
I know no downside to doing this temporarily (as long as you know how to undo it! – or follow better guidance !)
sudo usermod -aG plugdev $LOGNAME
Thanks a lot, but today the OTA appeared so I did it that way.
Everything seems to work. I’m happy to be on v1.0
Thanks again
Hey, thanks for doing this! I would like to test it but Android File Host always errors:
OOPS!
no mirrors found.
Thanks for letting me know.
Here’s the re-uploaded version
Hi petefoth,
A new version /e/OS 1.1 (29 june) appeared on my phone this morning.
Did you make it ?
Do you know if it’s working ?