Thanks for helping out with the testing @Rik I just restarted the build. Once it is done will let you know and you can test if the OTA is working now.
Update: @Rik Pl can you check if the OTA builds are showing up on your tablet and phone. The builds are complete and show as published on the OTA server.
Thanks for testing out the Asus phones was worried as there was no feedback on some phones. Pl can you share the TWRP version used if any.
The issues you have shared are generic and most have bugs raised in gitlab for them. So they would be there in most devices and the fix here possible will also come for all devices.
Thanks for replying. I have 2 android devices - Moto G4 (athene) and ASUS Zenfone Max Pro M2 (X01BD), among which athene was already supported for a long time now and was the first device for me to try out this awesome /e/ System. I wish I had more devices to test out /e/ on but for now I have X01BD.
I would like to thank you guys for creating and maintaining /e/ for so many new and old devices, /e/ is the best if not the only option to get security patches and version upgrades on years old devices which is one of the major drawbacks of android vendors. So I am glad to help anyway I can. I really want to see this ASUS Device to get official support.
I am looking through gitlab now for possible workarounds for the mentioned bugs. One thing I noticed last night is that not only /e/Drive is not working but Notes are also not syncing anymore although it was working the day before yesterday. I managed to take a screenshot of the error toast message.
On same version of rom, so I am guessing it has something to do with the cloud, maybe it’s temporary server issue? Let me know if you figure out anything.
Ok, looks like I finally figured out what’s going on with the eDrive sync. So while adding /e/ account in Account Manager it automatically sets the server to https://e.email instead of https://ecloud.global causing to Drive not syncing. This is still just a guess as I know we can access /e/ Nextcloud services from https://e.email as well. But after manually changing the server to https://ecloud.global Drive is working as expected.
A more interesting find is that Photos and Videos captured in android device were automatically uploaded to the cloud without any issues, it just was not downloading anything to the device. Package List and Application Settings in Devices folder were also syncing accurately. Anyway it’s working now with https://ecloud.global set as server.
Would a tablet Samsung SM-T719 suitable for eOS ? And most of all, would be useful for the community? I’m going to buy one and I would like to make the right choice.
I’m new to gitlab, so a little lost where to post about it. Can you link me the exact page where I can submit the issue? I am seeing 12 branches of eDrive project but none of them seems to be the version shipped with the test builds.
Hi Julien,
If LOS officially starts support for a device in 17.1 then it is easy for us to build the ROM as the ‘hard’ part of the porting is already done. I can add these new devices to the list and make a test build for them.
For now I am working to ensure that the first set of test builds we released in this thread can get OTA updates. There was an issue with the OTA server which we need to resolve.
The whole point of these test builds was to give users a chance to use Pie on their device and update the test builds seamlessly OTA while we add them to the official list.