yashsingh1/xdaforums huggingface dataset:
[Android Software Development] heinhuiz:
I asked *you^ to react by PM. Don't know why you did not, but I'll answer publicly and off-topic again.

I did not jump to conclusions until you challenged me to. At first, I was just wondering.

Meanwhile, I appreciate your arguments. You could have explained earlier.

Cheers.
[Android Software Development] HippoMan:
I'm glad that we have gotten closer to a place of mutual understanding.

Thank you, and cheers as well.
[Android Software Development] HippoMan:
Back on topic: I found that I can get "LINE Lite" to work fine under LOS 17.1 microG, and the full-blown "LINE Messenger" hangs at the startup screen under LOS 17.1 microG . LINE Lite and LINE Messenger also show corresponding behavior under the latest e-foundation ROM for my device.

LINE Messenger works fine under non-microG LOS, and therefore, I believe that this is an issue with the full-blown LINE not functioning properly in the absence of gapps.

Given my LINE Web workaround and the fact that I can use LINE Lite under microG, my particular problem is solved ... although for my own edification, I will continue investigate the behavior of the full version of LINE in a microG environment.
[Android Software Development] j_17:
Anyone successfully get [LineageOS for microG] to work on an Essential Phone?

Having troubles...

First, I got regular LineageOS 17 flashed but later learned microG won't work so I am trying to flash LineageOS for microG (lineage-17.1-20210203-microG-mata.zip) but getting error 21 sig ver failure. Only instructions included for sig ver were for prev builds.
[Android Software Development] kurtn:
Did you read lineage.microg.org ? There is a link to

extra

download.lineage.microg.org
[Android Software Development] j_17:
Yes. After I wiped my phone I tried to sideload the migration file first as the directions said to do that before sideloading the zip for the ROM. That's when I ran into the sig ver failure error 21 issue.
[Android Software Development] kurtn:
The migration zip is for not wiping. What did you wipe? Was your previous installation encrypted?

Oops, a/b device. Maybe you should follow the fresh installation guide. From lineageOS wiki.lineageos.org. you can use lineage4microG recovery.
[Android Software Development] Demax55:
Was anyone able to pass Safety Net with lineageos for microG 16.0?

I'm asking because I have an asus zenfone max pro m1 with the latest 16.0 lineageos for microG, but safety net fails attestation even with a certified fingerprint ( changed with magiskhide props config) and safety net universal fix. Maybe I can't pass it because of the ROM?
[Android Software Development] kurtn:
SafetyNet feature of microG is broken a few years now.
[Android Software Development] Demax55:
Yeah but after the release of universal safety net fix people got it passing even with microG. But I can't
[Android Software Development] HippoMan:
Please delete. Thank you. I realize that I should have posted the message in a different thred.
[Android Software Development] voxit:
Does anyone know what is going on with the builds?

All devices included, last one was from 5/02.
[Android Software Development] kurtn:
This is a hobby project. And because of some incompatibility between android versions, the build cycles get manually triggered.
[Android Software Development] matiusuario:
Hi. You should edit the website, it says weekly updates and it's not true. It's more like 6-weeks. (I dont have github so I can't make a pull request).

I hope a new update came out soon. 👍
[Android Software Development] MartiniMoe:
So, is there anything one can do to help getting the ROMs to build again?

I have some experience in building LOS, so maybe, if I knew what the problem is, I could help?
[Android Software Development] Big Dumb Object:
I just received a fresh OTA update on my Polaris (dated March 5), although it is not yet available on the download page.
[Android Software Development] kurtn:
I think you have official lineageOS installed. https://download.lineageos.org/polaris
[Android Software Development] Big Dumb Object:
My bad! I really forgot that I had just recently experimented with a MicroG custom install and left the regular LOS after that. But I was so excited about this OTA notification...
[Android Software Development] SaboraPie:
Is the lineage + microG projet abandon or something?? it takes a long time without any update.

And build it by yourself is very difficult?? to keep keeping it updated. I am on lineage 17.1 version. Thanks!
[Android Software Development] Big Dumb Object:
Just look through the last couple of pages of this thread and you'll get some sort of answer. I don't think a few months of delay can be a symptom of abandonment, since this is not the first time for this project.

Alternatively, you can try other ROMs with MicroG built-in on your Poco F1: OmniRom and eOS.
[Android Software Development] MartiniMoe:
One could also use stock LineageOS and install signature spoofing, microg and f-droid via NanoDroid.

Communication and transparency with this ROM is really bad. Nobody knows how, where or when the build system runs. There is zero communication when builds happen or why they dont happen. Also issues and pull requests dont get any treatment... I'm kinda disappointed and thinking of switching to the mentioned alternative.
[Android Software Development] patroj:
Could be they have their hands full with getting some builds done for R? At least that's what I'm hoping for. 🙏
[Android Software Development] kurtn:
Not really

LineageOS 18.1 support · Issue #139 · lineageos4microg/docker-lineage-cicd

18.1 is upcoming. We might want to adopt the build script and patch to that :-)

github.com
[Android Software Development] kurtn:
Do not update today, if you need signature permission

Signature spoofing permission lost · Issue #47 · lineageos4microg/android_prebuilts_prebuiltapks

March 24 update for a3exlte performed without errors. Only CoronaWarnApp cries: there is no exposure notification framework. Reason see screenshot

github.com

Edit: bug is fixed. Buggy builds are deleted from download server. 17.1 builds started march 26
[Android Software Development] RSkillz:
spotted the update today, thank you!

keep up the great work, love this ROM
[Android Software Development] jay-cp:
Hello,

I have a Moto G6+ (evert) and installed the Lineage for MicroG update from March 27, which seems to have an issue:

In previous versions, I could just touch the fingerprint reader and it would wake and unlock up the device. In this version, it vibrates, but does not wake up. If I use the power button first to turn on the display, then touching the fingerprint sensor does unlock the screen.

Also, in previous versions, while doing a phone call, I could turn the phone and use the keyboard. With this version, I cannot use the keyboard or do anything at all during a phone call. Not even reboot (nothing works), until the call is over.

I'm not sure where to report this.
[Android Software Development] kurtn:
Does not sound like a microG related issue. If you don't find a report in official lineageOS bug tracker, you should try to install official lineageOS. Sadly that process involves clean flashing.

How to submit a bug report | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] jay-cp:
I suppose downgrading to the previous working version would likely break things, right?
[Android Software Development] kurtn:
You can try. But that's no long term solution without reporting.
[Android Software Development] ioctl0:
Hello!

@Simon94, please enable builds for these newly added to upstream devices:

Info about instantnoodle | LineageOS Wiki

wiki.lineageos.org

Info about instantnoodlep | LineageOS Wiki

wiki.lineageos.org

Info about kebab | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] kurtn:
Work

Work in progress

LineageOS 18.1 support · Issue #139 · lineageos4microg/docker-lineage-cicd

18.1 is upcoming. We might want to adopt the build script and patch to that :-)

github.com
[Android Software Development] aldonogueira:
Hi, people

The latest OTA update of lineage+microg (17.1-20210328) for Moto G4 Play (harpia) completely broke sound. No sound is reproduced either through the speakers or using a headphone. Some applications like com.arnaud.metronome crash and others like spotify say they can't reproduce sound. I tried to revert to the previous build, but then I couldn't even unlock the phone because something crashed

Please remove this update from the site until the problem is solved

In the mean time I'm trying to report this bug properly
[Android Software Development] humpty321:
Will an upgrade from 17.1 to 18.1 work on a phone (cheeseburger) where encryption is to be unlocked via PIN?

I'm asking because of what I read in this thread:

https://xdaforums.com/t/recovery-orangefox-r11-0-for-oneplus-5-5t-unofficial-official-soon.4192655/ "That's android 11 problem, A11 doesn't let recoveries decrypt with pin. Only patterns work."
[Android Software Development] kurtn:
That's why wiki.lineageos.org recommends side loading and lineage recovery. No need to decrypt.
[Android Software Development] Samambaia:
My situation:

- REDMI NOTE 7

- "LINEAGE OS recovery 17.1"

- dirty install of ["LINEAGE OS for MICROG 17.1" + migration.zip] on the top of "LINEAGE OS 17.1"

Then, questions:

Will that screw up something if I install "LINEAGE OS for MICROG 17.1 recovery" on the top of my present "LINEAGE OS recovery 17.1" ?

Once dedicated version of 18.1 will appear, shall I update my "recovery" to 18.1 or shall I keep 17.1, in order to install "LINEAGE OS for MICROG 18.1"?

Will that screw up something if installing "LINEAGE OS for MICROG 18.1 recovery" on the top of "LINEAGE OS for MICROG 17.1 recovery" ?

Thanks!
[Android Software Development] kurtn:
Lineage recovery works fine, except ota updates for microG fork. Easiest way to replace it is enabling "update recovery" in updater or developer options. This will screw up nothing.
[Android Software Development] Samambaia:
I look in the different menus and didn't find in 17.1 the "update recovery" menu, neither in the updater neither in the developer's options (only "apply updates at startup" and "show restart option in recovery and bootloader". Can you tell me how to activate the options or if possible from sideload without screwing up everything?
[Android Software Development] kurtn:
You don't have that option?

In that case following the guide

Install LineageOS on lavender | LineageOS Wiki

wiki.lineageos.org
[Android Software Development] Samambaia:
Have a look at my menu (French) under 17.1 with microg. Can you double confirm that "fastboot flash recovery <recovery_filename>.img" with microg version won't screw up and cancel my data when on the top of regular Lineage recovery? :)

Thanks,
[Android Software Development] kurtn:
Confirmed confirmed
[Android Software Development] Bracher:
Hi I have the official LOS 18.1 for gta4xlwifi installed if I now go instead to microG can I use the official LOS Recovery 18.1 or is it necesarry to flash first the microG LOS recovery?
[Android Software Development] humpty321:
I was not aware of that. I assume, the OTA update script does something similar to sideload as it does not ask for the PIN. So OTA updates will continue to work on 18.1 on phones where PIN is used?

Does the version of TWRP make any difference in this respect?
[Android Software Development] kurtn:
You can keep lineage recovery. OTA uptate will not work then.
[Android Software Development] kurtn:
I don't understand the question. Of course, a wrong recovery can break ota update.
[Android Software Development] CoLdIcE42:
Hi,

Im on 17.1 with whyred and im having trouble with phonecalls. Sometimes (especially with Iphone users) I cant hear them and they cant hear me. Ive got the latest firmware but should I update vendor ? Or do I need a complete reinstall for that ?
[Android Software Development] kurtn:
If complete reinstalling is a option, I recommend to go back to miui, and install official lineageOS (18.1 should be available in a few days) and check calling bug. From there you can upgrade to lineage4microG
[Android Software Development] humpty321:
I use Mauronofrio's TWRP, but there is also an official TWRP available for cheeseburger. Then there ist a (no longer maintained) Orangefox -which is to my knolwedge a fork of TWRP- and maybe yet others. So what I tried to ask is, if all the basically working variants of TWRP are unable decrypt via PIN.
[Android Software Development] kurtn:
This is a device specific question and should be answered in your device community. Find it in XDA or on telegram.
[Android Software Development] Samambaia:
It works perfectly out, I just had to place a USB hub on my computer, even it initially recognizes the device in bootloader mode, but hangs in adb. Anyway, it was smooth and I want to thank you.
[Android Software Development] humpty321:
I didn't ask further. Before attempting upgrade I replaced PIN by Pattern. After the upgrade I reverted to PIN. Mauronofrio's TWRP was then able to decrypt with this PIN. Maybe upgrade would have worked even directly with PIN in place. Just in case someone stumbles accross my question here ...
[Android Software Development] pmcmm:
hello guys,

I've been willing to switch to lineage microg for a long time now. However, each time I tried, the location services didn't work and I was unable to use GPS. I've had this in two different phones. So either I'm doing something wrong or there is a problem somewhere in the microg. All the boxes are checked in the microg settings. I'm using the GPS Test app from F-droid, where I can see the satellites, but no connection is established.

What do you think the issue is?

edit: ok it connected to a few satellites, but it still looks rather slow. Do you LOS MG users have no issue with it?
[Android Software Development] kurtn:
Yes, GPS fix is slow in some custom ROMs. What is your benchmark? Stock ROM or lineageOS with GApps? In microG there is a network location module to guess a location from WiFi or cell towers, as long as there is no GPS fix.
[Android Software Development] pmcmm:
The benchmark is LOS with gapps indeed but on a better phone. The difference is drastic. I am aware that first connection with satellites can take longer, so i will keep testing to see how it goes.

What do you mean with GPS fix? I see in microg core services that GPS is part of it
[Android Software Development] kurtn:
This is not gps
[Android Software Development] pmcmm:
That perhaps not, but there is somehow GPS in microg. Here is some evidence, first picture the microg settings showing permission to access GPS and second the phone connecting to the satellites.

edit: @kurtn, you were right all along. The GPS connection to the satellites is made in a first instance but then it seems to cancelled. Reading through the FAQ of the offcial website https://lineage.microg.org/, I finally understood what is going on, GPS is disabled, but one can use the cell towers to get quite an accurate location.
[Android Software Development] pmcmm:
I've spent the last few days testing microg in two devices:

- Redmi Note 4 (mido) LOS 16.0

- Poco F1 (beryllium) LOS 18.1

In the oldest phone, I still couldn't find a single bug. Location works very well, even gps works when using openstreetmap-based apps.

In the Poco F1 however, location is not working that well, I can't seem to get my location detected by google maps. That causes some nuisance as some apps rely on google maps to provide their services.

Considering that it works in one phone and not in other, it can't be a microg limitation. I suspect that it's just a bug that still hasn't been squashed in this fresh releases of android 11. I'm curious what are other people's experiences.

Apart from that, I must say I'm pleasantly surprised on how smoothly everything works in a google-free phone! Thank you microg developers!
[Android Software Development] n76:
crDroid has signature spoofing built in, so all you need to do is follow the microG install instructions.
[Android Software Development] n76:
I suppose it might if I slogged through it all. . . I glanced through the files you posted and did not see anything that was helpful to me. Basically that is capturing a lot of information about every app that recently ran on your phone. A simple logcat at the time of failure would be easier to go through and would have logging from microG in it as well as StadtRad in a time sorted order so that it is easier to follow.
[Android Software Development] Mayank0809:
Can I use google apps on this ROM?

Like Google Dialler, Google Calendar etc.? If not then which ones can/can't be used? I'm really considering moving to this build but this is all that's holding me back!
[Android Software Development] klaus-hamburg:
Many thanks,

unfortunately the usb connector of the device is defect. Is it possible to get a logcat from a app?

Can't find like this until now. I will continue to try to find a solution to this.
[Android Software Development] klaus-hamburg:
so, I got a Catlog log :)

please find attached

thanks for support
[Android Software Development] nguyen4514:
Thanks for all of the great work. I've known about MicroG for a while, but I didn't know about this version of Lineage. I installed it for a couple of my devices and I'm very happy with what your team produced.

There is one device that I have that looks like it is not available for download on your website. Whenever your team has time, do you mind supporting the Samsung Galaxy Tab S 10.5 (chagallwifi)?

Thanks
[Android Software Development] n76:
It looks like the stadtrad app is a bit rough about the edges. I see a number of deprecated actions and other warnings as it starts up. But I don't think that is the reason it is crashing, just an indicator that the code is probably not of the highest quality. Looking at the log, it seems to be crashing because it was given a null object by the microG maps API and it did not handle that well (actually at all):

11-22 19:39:16.076 W/GAv4 (10991): Discarding hit. Missing tracking id parameter: a=1407793146,t=exception,cd=map,exd=java.lang.NullPointerException: Attempt to invoke virtual method 'boolean de.bahn.callabikecore.CABBaseActivity.isMapNormal()' on a null object reference
11-22 19:39:16.076 W/GAv4 (10991):	at de.bahn.callabikecore.fragments.AbstractSearchFragment.changeMapType(AbstractSearchFragment.java:678)
11-22 19:39:16.076 W/GAv4 (10991):	at de.bahn.callabikecore.fragments.AbstractSearchFragment.setupMap(AbstractSearchFragment.java:846)
11-22 19:39:16.076 W/GAv4 (10991):	at de.bahn.callabikecore.fragments.MainSearchFragment.setupMap(MainSearchFragment.java:173)
11-22 19:39:16.076 W/GAv4 (10991):	at de.bahn.callabikecore.fragments.AbstractSearchFragment.onMapReady(AbstractSearchFragment.java:417)
11-22 19:39:16.076 W/GAv4 (10991):	at com.google.android.gms.maps.MapView$zza$1.zza(Unknown Source)
11-22 19:39:16.076 W/GAv4 (10991):	at com.google.android.gms.maps.internal.zzt$zza.onTransact(Unknown Source)
11-22 19:39:16.076 W/GAv4 (10991):	at android.os.Binder.transact(Binder.java:499)
11-22 19:39:16.076 W/GAv4 (10991):	at com.google.android.gms.maps.internal.IOnMapReadyCallback$Stub$Proxy.onMapReady(IOnMapReadyCallback.java:79)
11-22 19:39:16.076 W/GAv4 (10991):	at org.microg.gms.maps.MapViewImpl$1.run(MapViewImpl.java:117)
11-22 19:39:16.076 W/GAv4 (10991):	at android.os.Handler.handleCallback(Handler.java:751)
11-22 19:39:16.076 W/GAv4 (10991):	at android.os.Handler.dispatchMessage(Handler.java:95)
11-22 19:39:16.076 W/GAv4 (10991):	at android.os.Looper.loop(Looper.java:154)
11-22 19:39:16.076 W/GAv4 (10991):	at android.app.ActivityThread.main(ActivityThread.java:6186)
11-22 19:39:16.076 W/GAv4 (10991):	at java.lang.reflect.Method.invoke(Native Method)
11-22 19:39:16.076 W/GAv4 (10991):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
11-22 19:39:16.076 W/GAv4 (10991):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
11-22 19:39:16.076 W/GAv4 (10991): ,tid=,exf=1,aip=1

I can't tell, but suspect that this might be due to some map API calls that are stubs (i.e. not yet implemented) as I see a bunch of warnings about that earlier in the log. For example:

11-22 19:39:15.538 W/GmsMapImpl(10991): Compass not yet supported
11-22 19:39:15.538 W/GmsMapImpl(10991): ZoomControls not yet supported

If I were you, I'd create a bug at https://github.com/microg/android_packages_apps_GmsCore giving a location the app can be obtained and also posting this same logcat file.
[Android Software Development] aphirst:
I'm in agreement with [MENTION=8718591]ubuntiger[/MENTION] - klteduos would be a great addition to the lineup. The S5 itself is a great, well-supported device from the official LOS lineup, and the Duos is basically the dual-SIM variant. I travel a lot so I'm keen to get hold of one of these myself, and "official" microG support would be like an early Christmas present. :)
[Android Software Development] Simon94:
Looks like i just missed one of the posts. The device list is updated, new build started. - Expect new builds during the next 2-3 days - Thats how long the current build takes :)
[Android Software Development] kalehrl:
You didn't miss w5. :D

Thanks Simon.
[Android Software Development] Playoff:
Hey Guys,

At this spirit of Open source issues being waken up around the internet these weeks I'd like to share with you great

open source apps:

Brave browser (adblock,anti tracking,anti fingerprint,https support etc)

VLC media player (plays every music / video)

MuPDF (pdf reader)

SD maid (best real cleaner on android hands down)

L Speed (alot of helpful tweaks to the system)

Open Camera (well known camera alternative)

and a couple of questions to you guys:

1. Do Moovit & Waze apps Work in this microg fork?

2. Would there be CM13 Support (cause there's still no LOS stable/snapshot version)?

THX & :good: , What a great initiative.
[Android Software Development] kurtn:
[MENTION=8740092]Playoff[/MENTION]

1 Waze works. But how about privacy?

2 they are working in 13.0 but I see no progress yet.
[Android Software Development] Playoff:
1. Cause I haven't yet found a proper alternative that functions so well like waze and moovit.

2. You meant "on" instead of "in"?
[Android Software Development] Bill565:
Quick question guys, I made a clean fresh install of LineageOS for microG but I can't find the "microG Settings" app. Do I need to install something extra?

Edit: I also noticed that in the app list google play services are listed as installed, is this normal? I did a factory reset before installing.

2nd edit: Turns out I needed to wipe system as well. Turns out the microg installation instructions are a bit incorrect when saying "If you don't care about losing your current data just reboot into recovery, wipe Data, Cache and Dalvik (perform a "Factory reset") and, without rebooting, install LineageOS for microG." I should note that I came from the latest LineageOS build. Anyway, hope this helps someone else!
[Android Software Development] kurtn:
You've go to delete gapps. Easiest way is wiping system as well before flashing.
[Android Software Development] dnishchhal:
Please compile microG version of lineageos for z008
[Android Software Development] memarama:
Is there a changelog somewhere?
[Android Software Development] Simon94:
Checkout changelog on lineageos page:

https://download.lineageos.org/cheeseburger/changes/ - For cheeseburger you have to type in your device codename. Every change which is merged as of specific device build started is included.
[Android Software Development] osilvab:
Hi guys is there any chance to get the microg working for the Asus ZenPad 8.0 (Z380KL) codename P024 ?
[Android Software Development] elmaos:
Thanks for letting me know!

I actually got it working too. I believe I just installed Droid Guard Helper from F-Droid then moved it from /data/app to /system/priv-app.

How did you do it? Did you just move the apk then install it from within the system partition?
[Android Software Development] kurtn:
You use location and GPS as synonyms. A phone with microG has many sources of location data. Not only GPS. Check your microG settings, go outdoors, install SatStat app and give your phone 10 minutes for location detection.