Thank you @SuzieQ, but I would like to have microG installed correctly by default (LineageOS for microG is not yet released, and may be never… but the master developer now works for the /e/ team)
Hi @lakano, is this a verifiable statement? Where did you get this interesting information from?
By the way: LineageOS 17.1 ROM for starlte was just an idea to shorten the waiting time for /e/OS Android Q.
I myself use the ROM ASOP Android 10 Havoc-OS v3.8 Official for ‘starlte’. I like it a lot because it is also open for Micro-G support (Signature Spoofing ready). MicroG can easily be installed via the official F-Droid repository.
Until you can use e/OS Android Q halfway, there will still be a lot of water of the Seine flowing from Paris to Le Havre.
So, stay healthy and confident. So long
Martin Wißfeld is since this summer directly sponsorised per /e/ foundation, to help to supervise microG integration inside /e/ ( in french: https://www.toolinux.com/?e-OS-participe-au-developpement-de-microG )
1 Like
I’m trying to manually build for river and hit the following issue:
error: system/extras/boot_control_copy/Android.bp:3:1: "bootctrl.copy" depends on undefined module "libbootloader_message"
What I’m really trying to do is get an unofficial build for pixel3a, the river build is just to make sure I can build something… When I put stuff together for sargo (pixel3a) I get the same error.
An additional/alternate question I have is where do the device-specific repo manifests get pulled in in the official e CI builds? I’ve looked through the docker scripts and don’t see it. If someone could point me to the right place I’d really appreciate!
Thanks!
(NB: please don’t suggest I try e-pie, then I rather stay on LineageOS 17.1 and wait)
2 Likes
Yes @lakano, yes @LEPT, I am familiar with M. W. (see here). I read the term “master developer” in a different context.
However, I don’t see a more intensive cooperation between M. W. and /e/ as a guarantor that /e/OS Android Q for for Samsung Galaxy S9 ‘starlte’ [and Galaxy S9+ ‘star2lte’] will become operational faster. The cooperation is rather an indication that there will be no /e/ OS without pre-installed MicroG for the time being. We will see how the numerous /e/ plans develop in the near future.
Very nice. Q is on the road! 
1 Like
I’m now trying the docker build (docker-lineage-cicd) and I see an error early on, but so far it continues… Trying to build river:
> docker run --rm -v /xtra/e-q-docker/src:/srv/src -v /xtra/e-q-docker/zips:/srv/zips -v /xtra/e-q-d
ocker/logs:/srv/logs -v /xtra/e-q-docker/ccache:/srv/ccache -e BRANCH_NAME=v1-q -e DEVICE=river
-e CLEAN_AFTER_BUILD=false -e REPO=https://gitlab.e.foundation/e/os/releases.git build-e
...
[Thu Aug 27 23:52:01 UTC 2020] Starting build for river, v1-q branch
...
+ build/soong/soong_ui.bash --dumpvar-mode TARGET_DEVICE
23:52:35 Build sandboxing disabled due to nsjail error.
build/make/core/product_config.mk:223: error: Can not locate config makefile for product "lineage_ri
ver".
23:52:35 dumpvars failed with: exit status 1
Should this be posted as an issue at https://gitlab.e.foundation/e/backlog/-/issues ?
We had got a couple of issues to be fixed on the build side for Q. Hope to get the team to resolve them by next week.
1 Like
Sir,
Most of your builds are for mobiles which are no longer available for sale. If i want to install a eOS on brand new phone, there is hardly any option available. I request you to kindly build ROMs for mobiles which are atleast available in market for buying.
Regards,
1 Like
hi @ankit221215, welcome to the /e/community.
we are numerous who like to use second hand-devices for morals, ecologicals, politicals and economicals reasons.
we are users more than customers
i could advise you the Samsung Galaxy A5(2017) with 3GoRAM that i would buy if i have enough money, awaiting for the A10e in about 3years
Edit : some Xiaomi and the Oneplus have powerfull hardware
2 Likes
All of the phones listed at the top of this thread are available new according to gsm arena, even the Sony Xperia Z3 Compact which is quite an old phone with it’s 2014 release date! There’s a few listed on ebay uk.
One of the reasons why we still support ‘old’ devices is to avoid e-waste. Not everyone can afford to throw away their phones after a year of use…even those that can afford to do it prefer to retain the old smaller, easy to use handsets. Having said that we do plan to add newer devices to our our list. the problem is to get hold of their source code to port them.
3 Likes
LineageOS for microG has recently switched to ASOP Android 10 (Q). Here the second build lineage-17.1-20200826-microG-starlte.
1 Like
It is greatly appreciated that you recognize the need for supporting older phones.
When you already have an old phone, then it is obviously most sustainable to use that for as long as possible.
If you want to buy a used phone, then important details to watch out for is that it a) is supported by /e/ (or at least supported by LineageOS which should make it more likely to later be supported by /e/ as well), b) has replaceable battery (so it can last much longer).
Samsung Galaxy S3 i9300 fits the above requirements and used to be popular as used phone, also because of its modem isolation The similarly branded and seemingly slightly more popular i9305 is not supported in LineageOS.
Nowadays i9300 and i9305 are disappearing (at least in Denmark where I live), and is also arguably too slow to run the newest releases of Android.
It seems the best option that fits the above requirements nowadays is the Samsung Galaxy S5 Neo.
Please consider adding support for that model in /e/ - it is supported in LineageOS and works fine there.
Please note the ‘Q’ builds have been updated in the table above…more devices are being added to the list. The zip files are tagged ‘dev’ which means testers will not need to manually flash the official builds when they come out later.
3 Likes
Ah, FP2 is on the list, I am impatient to try it on FP3 
Yessss! I was waiting to try this on my 6T, just saw this on the list now!!! Gotta backup everything then GO!
Think this made my day, THANK YOU TEAM
2 Likes
Any chance to get the public repos on gitlab updated to reflect the new builds? Specific fatal errors in the public repos make me think that they don’t reflect what got released…
Yes, that’s great. But on my FP2 it doesn’t boot. It’s trying to start but after some time booting it restarts to recovery.