yashsingh1/xdaforums huggingface dataset:
[Android Software Development] TDP95:
Hi,

Today, I attempted to flash the latest LineageOS for microG on my Essential PH-1 (mata). However, when flashing directly using the image, and following the LineageOS installation instructions, the touchscreen was completely non-functional after boot. The flash seemed to go ok with the 20200305 build, and it boots fine. But, upon first boot, I can't progress beyond the first start steps as the touchscreen doesn't work at all. Touches in general aren't registered as touching the screen doesn't prevent the device from sleeping. I also tried the 20200220 build date, and it also has the same issue. The touchscreen also doesn't work in Lineage recovery. I'm wondering though if it's due to the age of the original ROM that was installed. To get TWRP to work, I've had to always flash back to the official Essential ROM from August 2018. Otherwise, the touchscreen doesn't work in TWRP. So, the overall steps I take to flash a custom ROM is, use the Essential fastboot image for August 2018 and run the flashall.bat script from the package to flash it via fastboot. Then, flash TWRP to boot_a. After this, I can finally follow the steps on the LineageOS site to flash the ROM itself from TWRP. The official LineageOS images I have flashed though have never had a touchscreen issue. Could this be caused by the microG fork not including the vendor image that LineageOS ships?

I have though managed to install the microG fork of LineageOS by following the clean installation conversion steps that are on the main website. I follow the same steps as above, but flash the latest LineageOS nightly build for the mata. I don't sideload any gapps, then I follow the steps of wiping Data, System, Dalvik, and the Dalvik cache, and did try to wipe the cache in general. I perform all these wipes via the latest TWRP available for the mata. Then, I flash the microG fork of LineageOS. After the flash, I noticed TWRP said it couldn't find /cache to wipe. I am thinking this might be due to I never booted the fresh official LineageOS ROM I flashed first. But, after rebooting, the PH-1 boots fine, and the touchscreen now works. I was able to setup everything, and the microG setup menu shows all the check boxes ticked after I setup the included location backends.

Lastly, I do have a question regarding one app. That's the 1.1.1.1 app by Cloudflare. I do have a Warp+ subscription through Google Play. I haven't currently enabled any Google Services in the microG settings. However, when I try to accept the terms on the 1.1.1.1 app, it says an unknown error has occurred and cannot proceed. Does anyone know which services I may need to enable for the Warp+ subscription to be activated? I know I'd have to link my Google Account then. But, not sure what may need to be enabled for the app to work.

Any help is appreciated! Thanks!
[Android Software Development] kurtn:
What exactly are you trying to do with warp+ that can't be done with android or apps from f-droid?
[Android Software Development] TDP95:
I guess I liked it was quick amd stable to use as a "VPN" (I know Cloudflare says it isn't) on public wifi, and on the mobile network. But, I just tried the VPN provider I usually use on my desktop/laptop, and it actually works perfectly. I'll probably just stick with this.

Thanks!
[Android Software Development] Hetherington:
Sorry for the misinformation. The problem simply did not show up for some time.

Version 20200309, the problem still remains. Switched location from High accuracy to Device only and SystemUI crashed. But this does not always happen, I still have not figured the pattern and what it depends on.
[Android Software Development] bigsatan:
Same here, it occurs randomly
[Android Software Development] textmarker007:
Hey Shobit Joura,

thanks for your effort for creating this Module. But I read at github it causes bootloops after the 12 August update.

Do you have another recommendation or pathway to install PlayStore?

I tried PlayStore from nanolx via F-Droid but it causes a signature problem.

I also tried the patched playstore from shadow53 but it won't work either.

Thank yo very much!
[Android Software Development] e2vinay:
Bberyllium got official 17.1 from today I guess

Do we get 17.1 based builds going forward for beryllium?

or does it take some time to have 17.1 microG builds? until then will we get 16 based microG builds?

Thanks in advance
[Android Software Development] kurtn:
There is no automatism
[Android Software Development] tshortman:
so now that 17.1 is out this means the QC location services backout is finally upstream no?

does this mean we can hope for an official microg build for guacamole? :angel:
[Android Software Development] kurtn:
17.1 has other problems, like changed location permissions or changed background rules. Quite a bit of work for microG people.
[Android Software Development] tkm89:
Which should be fixed by this pull request, right? Hoping it gets merged soon, but then again the pull request has been open since the beginning of the year.
[Android Software Development] kurtn:
There is a fork with some fixes in http://github.com/nogoolag
[Android Software Development] oF2pks:
I have uploaded all possible MicroG plus privacy LineageOS 17.1 patches, for devs, here https://xdaforums.com/showpost.php?p=82014785&postcount=2 (patches.zip). Working android10 microG apk is also uploaded in post#1, but you can use Omnirom android10 semi-officials build : https://github.com/boulzordev/android_prebuilts_prebuiltapks

It's up to you to chose which ones should be merged at the right place https://github.com/lineageos4microg/docker-lineage-cicd/tree/master/src/signature_spoofing_patches ...

More info: https://gerrit.omnirom.org/q/microg
[Android Software Development] the_Pan:
Is there a chance you could bring those as flashable zip? Right now I'm on Omnirom-microg on raphael. I can't figure out, how to remove fake & aurora store and install patched playstore instead. If I try to use the nanodroid-settings to configure microg before installing, the phone freezes.
[Android Software Development] kubicarobert:
ETA

I'd really like to move to android lineage 17.1 because there are no new security patches for lineage 16 for my phone, but I don't want google. does anyone know when lineageos for micro g in 17.1 version become available, is there any info from mods that they are working on this?

it's been 2 weeks since lineage 17.1 was released so I'm asking myself if it's rather a question of weeks or months when lineageos for microg 17.1 is released
[Android Software Development] githyanki:
Seems that there are still a few issues with microG on Android 10, so may be awhile before it is ready.
[Android Software Development] kurtn:
No ETA. I think we are many months away from lineageOS for microG automated build system for all official 17.1 devices. In the meantime there will be many unofficial or based on lineageOS ROMs with signature spoofing patch. ... Or /e/
[Android Software Development] timmy6:
waiting for lineageos 17.1 :(
[Android Software Development] Tosgaba:
Hi,

Thanks for MicroG builds.

Can we request MicroG Builds for officially supported Samsung Galaxy Note 9 (SM-N960F / DS) crownlte?

Thanks in advance
[Android Software Development] kurtn:
17.1 is only for self-builders at the moment

https://github.com/lineageos4microg/docker-lineage-cicd/issues/68
[Android Software Development] JamesKinds:
Thanks for the update :svetius:
[Android Software Development] vildevilde:
Deleted
[Android Software Development] mitchst2:
Just enquiring about the availability of a build for the OnePlus 6T as this is a device officially supported by Lineage OS. Will it be added at some point in the future?
[Android Software Development] vildevilde:
OnePlus 6T is on LinegeOs17, Android 10 and as long as microG doesn't (official) work on Android 10 there will be no builds.
[Android Software Development] anjarys:
is this compatible with N910H?
[Android Software Development] kurtn:
No
[Android Software Development] Master One:
So that's the reason why there are no more weekly updates for my OnePlus 6 since 24th March.

I already thought that the project has died. Hopefully getting microG to work on LOS 17 will resume anytime soon. I already thought about trying out OmniROM for microG, but my previous experience with OmniROM wasn't that great (borked the phone with a weekly OTA update) and I need a reliable solution to work with.
[Android Software Development] e2vinay:
https://gist.github.com/mar-v-in/c8254168c63361c5094de13a7afea344
[Android Software Development] kurtn:
This is an announcement for microG. It is of limited relevance for the question "will we get automated builds of this lineageOS fork for 17.1”
[Android Software Development] Master One:
Indeed, but I think we can be hopeful because afaik the build system for LOS for microG is pretty much automated, so once microG is compatible with LOS 17, things should start to get rolling again.
[Android Software Development] gadgetguy08:
Is there a known reason there have been no builds since 4/25?
[Android Software Development] e2vinay:
Yes, you can see the reason just in above 3 posts ?

it's due to microG not fully supported officially on android 10
[Android Software Development] gadgetguy08:
I understand that, but there are still official recent updated builds of Lineage 16 that haven't gotten the microG treatment.

Edit: the later 16 builds aren't showing any more on the Lineage site for my device. :eek:
[Android Software Development] yonpi:
Hi there,

why aren't there any OTA updates for gemini (xiaomi mi 5) since 2020.03.24 in LOS 16.0 for microg? Is it no longer supported?
[Android Software Development] kurtn:
Looks like a mistake. That is around the last build date of devices that moved to official lineageOS 17.1 - but Gemini didn't
[Android Software Development] neox95_:
Hey there. Don't know if it is linked to the 17.1 (don't know if my device is concerned) but I don't have any update anymore since 05/24. My device is Asus Zenfone Max Pro M1 (X00TD). Any info about this?
[Android Software Development] kurtn:
Looks like an error in microG build server. In lineageOS the device is still 16.0

https://github.com/LineageOS/hudson/blob/master/lineage-build-targets
[Android Software Development] bege10:
Hi,

I had LineageOS with microG from NanoDroid installer for 1 year and now have LineageOS for microG for another year on my phone (Samsung Galaxy S5 Plus (SM-G901F)). I never had problems with location fixing. Now I noticed that UnifiedNLP doesn't work any more. GPS still works well. Neither with local database nor with Mozilla online plugin I get location fixing by cell location.

I restored both system and data partition backups from a time when I think cell location still worked. But this doesn't work either.

What can be the reason for this problem? Had someone the same problem and found a solution?
[Android Software Development] d1n0x:
For me "UnifiedNLP is registered in system" in MicroG self check randomly gets unticked until I reboot. It doesn't happen often though.

Afaik Lineage for MicroG is still on 16.0, so the problems regarding location permissions that cause issues on Android 10 should not affect it
[Android Software Development] bege10:
Thank you for your answer. In self check everything is checked except the last one saying that UnifiedNLP could not accomplish locating and therefor not test address resolution: Please, check your locating service. Well, all have location permission and are activated as before.

My phone is still on LineageOS for microG 16.0 (2020-05-03) and UnifiedNLP worked some weeks ago when I last used it.
[Android Software Development] yonpi:
Thanks for your answer! Do you think that this mistake with the gemini update will be resolved soon? And do you know who maintaines Gemini LOS for microG?
[Android Software Development] kurtn:
There is no device specific maintenance in microG LineageOS fork. At the moment i see no work done on build server.
[Android Software Development] yonpi:
OK, thanks. Is it possible to take the up-to-date LineageOS build and to reintegrate microG afterwards myself? Or will the build server be fixed in near future anyway?
[Android Software Development] kurtn:
There are custom roms that make it easier to integrate microG. But with some tricks you can microG even on official LineageOS.

No eta for a fix
[Android Software Development] ioctl0:
Samsung Galaxy S9/S9+ (starlte and star2lte) added again in base LineageOS 17.1:

https://wiki.lineageos.org/devices/starlte

https://wiki.lineageos.org/devices/star2lte

And this one also added: https://wiki.lineageos.org/devices/crownlte

Please update LineageOS-MicroG builds.
[Android Software Development] timmy6:
Also poco
[Android Software Development] vikashhero:
I don't suppose there's a statuspage for this project / its build server anywhere on the internet? Been curious as to how things are going since the builds went down some time ago.
[Android Software Development] kurtn:
Official 16.0 devices still get built weekly. There is no build status page. But you can sort downloads by date.
[Android Software Development] vikashhero:
Sorry, I was referring to the build server responsible for the microg fork images. As far as I'm aware, my phone's getting official 17 builds but I can't live without that sweet sweet signature spoofing. Hoping all is well with the project, though I'm thinking I should eventually look into making my own fork of the official images from source and just enabling spoofing and installing microG the manual way.
[Android Software Development] kurtn:
Self-building is the way to get 17.1

https://github.com/lineageos4microg/docker-lineage-cicd/issues/68
[Android Software Development] andy356:
Any update on the Mi 5 situation, though? Still on 16, still no new builds. While the official builds are chugging away.
[Android Software Development] tangmu93:
Tempted to try this instead of official lineage builds... Not sure I actually need to though, as I've transitioned away from apps requiring GMS already. Great option for a lot of folk though, hopefully the project continues to grow!
[Android Software Development] guillermohs9:
Not for all devices apparently. I'll patiently wait for los4microg 17.1, but the 16 branch hasn't seen builds since 20200331
[Android Software Development] vikashhero:
Much appreciated!

I'll follow that repo in the mean time.

Kind regards,
[Android Software Development] luca22:
Hi, just got around lineageos+microg recently.

I already installed before the non official lineagos (no gaaps) on a nubia z17 mini.

Does lineageos+microg cover this phone or only the official ones supported by lineagoos official?

Rgds
[Android Software Development] kurtn:
The device doesn't sound like it could have official lineageOS.
[Android Software Development] dced:
For anyone interested, I managed to get a working Lineage 17.1 build with https://github.com/SolidHal/docker-lineage-cicd/ on the Mi 5. I ran into "error: RPC failed; HTTP 524 curl 22 The requested URL returned error: 524" for the-muppets, so I went ahead and manually cloned and copied the repo over.

Took me 5 hours on a 2600x and >150GB(I estimate it at ~170GB) of space, so do take note if you are looking to build it yourself.

P.S. I was able to adb sideload the .zip over Lineage 16 w/ microg with no issues.
[Android Software Development] Android_Phan:
PIxel 2XL

Hey, guys. I was curious if there is any plans to get support for the Pixel 2XL. I know that I was browsing through the Lineage OS website and I see that the Pixel is supported. I am assuming that the Pixel 2XL might be soon?
[Android Software Development] patrikson:
Hi [MENTION=3049858]dced[/MENTION], where exactly did you put cloned repo? Into src/LINEAGE_17_1/.repo/project-objects/TheMuppets ?

And why did you pick that fork instead of https://github.com/lineageos4microg/docker-lineage-cicd ?
[Android Software Development] dced:
Yes, that's the correct directory, but I believe the folder name was The-Muppets. Can I check if you are also running into the HTTP 524 error?

As for the fork, check out this pull request . This comment is a good step-by-step guide too.
[Android Software Development] kurtn:
From noGooLag telegram channel

LOS for microG 17.1 building tools

In light of problems the official LOS4µG project is facing to build Android Q, ooOOooOoo has created a docker image and automation scripts to patch official LOS sources with sigspoof and integrate the microG with the community's Q fixes.

Project: https://gitlab.com/fremontt/minimal-docker-for-lineageos

Discussion thread: https://redd.it/h8cwpg

#los4µG #microg #los #Q #docker
[Android Software Development] patrikson:
Xiaomi mi mix 2 also working good with 17.1!

I made it for Mi Mix 2 (chiron), same issues with 524 error, same solution.

Source code and build took ~182 GB of space, 20-30 minutes of data download and ~100min of compiling on dedicated vm with 12 server grade vcpus and 16 gigs of ram (no swap).

I managed to adb sideload the zip over clean Lineage 17.1 w/o microg, no data wipe. Phone is working, and aurora store too! Yay! :victory:
[Android Software Development] dced:
Glad that you got it figured out! Sorry for not replying earlier, got caught up with other stuff.
[Android Software Development] ballerd:
Thanks bro
[Android Software Development] patrikson:
I was just wondering if we can somehow help LOS4microg team with our build experiences? Mine "chiron" works like a charm with my build, and I've never seen that good battery performance on my phone. Is there any way to contribute?
[Android Software Development] kurtn:
I think you should share it through the channels other unofficial chiron roms are distributed.
[Android Software Development] 4nndee:
Hi folks,

at first, many thanks to the developers for your efforts. I own an Samsung Galaxy A3 (2016) [A310F] and thanks to you (Lineage and Lineage for microG devs) this device runs like a charm for nearly 4 years now.

There are official Lineage 17.1 builds available for the A310F. I am observing the device list on the LineageOS for microG website since a few weeks, but there are only Lineage 16.0 builds available, yet. Any information on when the new 17.1 builds will be available?
[Android Software Development] Russel's Silverware:
From the FAQ on the LineageOS for microG home page:

LineageOS for microG targets the same device list as regular LineageOS, so you should be complaining to the LineageOS people. However, I believe most devices are supported by community members who volunteer to support that particular device, so just making a request is unlikely to get you anywhere unless they have some sort of voting system where they aim to add support for the most-upvoted models first.

I don't think there's any ETA; I myself am just watching this thread. See the past ~2 pages of the thread for a discussion of the problem and a DIY solution in the meantime.
[Android Software Development] bege10:
Does UnifiedNLP only work with Wifi activated?

Hello,

some time ago I posted that UnifiedNLP (without GPS) doesn't work on my phone any more. Now I found out that it only works if Wifi is activated (no connection required). I don't think that this has always been the case but I am not sure. I have both online and offline backends installed. The online backend of course needs internet access but that usually is mobile data. This is not enough to work on my phone, it additionally needs Wifi activated. Similar with offline backends (database on external SD card): they don't need internet access at all but also only work if Wifi is activated. I also tested a fresh installation, same behavior.

Is this normal? Is this related to the Android version (LineageOS for microG 16 (Android 9))?
[Android Software Development] patrikson:
Thanks, I actually did it. You can find thread here https://xdaforums.com/mi-mix-2/development/rom-lineageos-17-1-microg-mi-mix-2-t4131359 or direct gitlab repo here: https://git.e-science.pl/patbel/los-17_1-unofficial-chiron
[Android Software Development] 4ronie4:
I also have a lot of location problems since months. On my case Mozilla NLP does not work in any situation, but Local GSM works if I use it while driving or outside in the street.

Maybe this problems could be due to Android Pie wifi scaning limitation, which I'm not sure if location backends are avoiding this limitation. Deja Vu backend caused to me the same problems as Mozilla did.
[Android Software Development] cmonty14:
Google device registration, Google account - when is this needed

Hello,

in microG settings I can

enter Google account

activate Google device registration

My question is:

Which services depend on these settings?

Will I "open" my phone for Google services if these settings are enabled?

THX
[Android Software Development] kurtn:
Google device registration is for cloud messaging. No idew with account. Yes, these settings result in communication with Google. But microG is designed to send only minimum information to get the service. For more information see microG.org
[Android Software Development] starbright_:
That sounds weird as you can activate Cloud Messaging without activating Google Registration.
[Android Software Development] kurtn:
True. Should somehow be connected in the settings menu.
[Android Software Development] e2vinay:
microG new update!

https://github.com/microg/android_packages_apps_GmsCore/releases
[Android Software Development] kurtn:
There is a reason, why it's called preview
[Android Software Development] e2vinay:
Agree. I'm not expecting LOS-microG builds to start right away from now. it's a good sign that microG got a new update after long time and hence thought of sharing it here.

Thank you
[Android Software Development] starbright_:
I have patched my LOS with this two patches here to achieve spoofing.

https://gitlab.com/fremontt/minimal-...e/lineage-17.1

This seems to work partially. After installing LOS and microG the selfcheck returns : Phonesky hasn't right signature .

Looking at the app Fakestore it has not requested any permission now. Beside that everything seems to look fine. What did I miss?
[Android Software Development] starbright_:
The answer is (not sure what exactly this is and why this is needed to do manually):

adb shell pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
[Android Software Development] Fluxtrot:
Redmi Note 6 Pro Support

Hi, would you be able to add builds for the Xiaomi Redmi Note 6 Pro? It is officially supported by lineageOS, but I can't find it in the download.lineage.microg.org page.

It's official code name is tulip, but it's called twolip by Lineage because of conflict with a ZTE phone by the same name, I think.

Sorry if I'm missing something or this is the wrong place to ask, I'm a bit unsure.

Thanks
[Android Software Development] kurtn:
This is the right place to ask for. You only missed 17.1 is only for self-builders at the moment.
[Android Software Development] wufuz:
17.1 builds for Crackling

Hello,

Do you know why there are no microG + LineageOS 17.1 builds for Crackling (Wileyfox Swift) available? Plain LineageOS 17.1 builds exist though. What could I do to make them available?

Regards
[Android Software Development] kurtn:
You can build yourself

https://gitlab.com/fremontt/minimal-docker-for-lineageos
[Android Software Development] caphub:
Santoni, which is still on lineageos 16, had the last update on 28 March. Could you restart it's building?
[Android Software Development] wufuz:
Thanks for the response. What can I do to make official crackling builds available?
[Android Software Development] kurtn:
Lineage4microG seems to be stuck in 16.0 - maybe someone has to fork the project for 17.1 support.
[Android Software Development] greenjongreenjon:
Build for XZ2C?

Hi, Xperia XZ2C has an official LineageOS build now, but I don't see a microg build in your downloads section.
[Android Software Development] klaus-hamburg:
microg doesn't official support los 17.1 until now

there are a few manually workarounds for signature spoofing

i patch the builds / servives.jar with linux / adb and/or local

afaik, marvin works on it together with e-foundation
[Android Software Development] kurtn:
So sad