16.0 is Pie, 15.1 Oreo. Just don’t use 17.1.
are the sources synced ?? Do you have your device / kernel / vendor files in srv/e/src/PIE available ??
DEVICE_PATH := device/redmi/curtana is in BoardConfig.mk, so your manifast must store in that dir.
Did you change the manifest back to “redmi”, maybe the “old” lineage-17.1 is still there.
what do you have in device path, it should be redmi.
Are all these sourced in your Oreo folder available?
By he way, the builde.sh script isn’t working anymore on my side. And since all sources are available in e-git you can use this way too [HOWTO] build eOS in old fashioned way with breakfast -- now with interactive script
I prefer using this way.
Starting in OREO folder with
sudo su
source build/envsetup.sh
And I hope, your sources are really 15.1 sources, because the sources you have forked from are all 17.1 sources
Why, I have gotten a Mi Max 3 from factory with android 10. I have first flashed Android pie stock rom and than the e-GSI pie. And it works very good (just typing on than device)
Ok, have a look on xiaomi firmware updater website for android 9 firmware.
If available flash it and than try this way [UNOFFICIAL BUILD] Pi/e/ GSI for Mi MaX3 (nitrogen)
AH, OK, that’s bad. But if you want swap from MIUI there is a LOS17 GSI available
@andrelam am I right, the script isn’t working anymore because of changed docker command / image?
If yes, could you please update the post?
No, script from github works, only OTA is not working. I have a fix for that, but did not push to github.
Where can I find the script on github?
here I’m planning do push an update today to fix OTA url, if you don’t have custom OTA server you can use the script as-is.
Thanks. I’ve pulled the latest version. When I build I get the error reported in this post
Any idea how to fix?
I’ve just seen this commit
I’m running the previous version - is it likely to fail because it doesn’t have the changes? It didn’t seem to mind having export DEVICE... rather than export DEVICE_LIST...
No, they both work. If you don’t use OTA you can use the master branch as well.
as far as I know the ‘latest’ isn’t working anymore. Best using ‘community’
How calls to /e/ OTA server infrastructure should be removed for custom/unofficial builds ?
Is export OTA_URL=’’ in the build script doing it ?
I don’t know what happens when you pass an empty string, i never checked because i use a custom OTA.
@andrelam are you able to show how to set up an ota URL. I have searched without success