Problem with OTA_URL using the community build image

Using /e/OS Build /e/OS
#1

Hi together,
i cant get my ota running again. I am building with the community docker image and the OTA_URL parameter setted.
After booting, the property lineage.updater.uri is not setted (should that be the case or is this not the “productive place” where it should be configured ?), if I set it manually with
setprop lineage.updater.uri “https://updateserver.de/api/v1/beryllium/unofficial/” it seems to work again.
Without setting it there the requests are made to https://ota.ecloud.global/api/v1/beryllium/unofficial/eng.root.20200524.112605.
Seems like the OTA Url gets to the buildscript. Adding OTA URL overlay is echoed on the build and
the /srv/src/PIE/vendor/lineage/overlay/microg/packages/apps/Updater/res/values/strings.xml contains the valid Ota url also…

Any ideas whats the problem here?

thanks,
Alex

#2

How do you get the property getprop lineage.updater.uri ? This property is empty on my phone, but it does connect to my custom OTA. (I’s a build from 18-1-2020. So maybe something changed…)

1 Like
#3

yep, i get it using getprop. i can see the connection url also in logcat when checking for updates. Okay, thats interesting. I guess the correct url then gets built into the updater app if everything works correctly. So perhabs i have a problem with the overlay stuff?

#4

I now have the same issue, the OTA url is not working. I did an OTA test for leeco s2, after the update OTA points to https://ota.ecloud.global/api/v1/s2/unofficial/eng.root.20200601.134106 So you are right, something changed.

#5

I checked, i was using the wrong script. I never use Docker, but use the same build scripts. So i changed to the correct one and OTA is working again. I have no idea why it is not working for you, since you checked /srv/src/PIE/vendor/lineage/overlay/microg/packages/apps/Updater/res/values/strings.xml
I also checked this file, and the URL was there.

#6

thanks for testing out :slight_smile: i guess you now use the builld-community.sh? Thats the one which should be used in the docker community image according to the CI config.
And yes, the correct value in the strings.xml is really strange…

Perhabs someone who is building with docker can test to ota a recently wiped phone.

#7

Hey @ all, sadly the problem ist still there, even with a complete fresh source and cache. Has anybody made recent builds with a custom ota url and can confirm if its working? especially for beryllium which I’m building for right now.
Thank you!

#8