LineageOS for microG
- Thread starter Simon94
- Start date
Could you please add avicii (OnePlus Nord) to the build roster for LOS for microG 20? New maintainers took over and it's officially supported again by lineage.
download.lineageos.org
LineageOS Downloads
Hi all. I have just clean-installed "LineageOS for microG" on my OnePlus 5T and it seems to be working perfectly except for one thing. I want to use "GMaps WV" with my location provided by my GPS. I have given "Location Access" to GMaps WV, and after having tried to locate myself using my GPS, GMaps WV correctly appears in the list of apps that have made "recent location requests". I have also checked whether my GPS is working by installing and running SatStat, and SatStat is working 100% correctly (it shows me that I am locked to 6/21 satellites, my current latitude and longitude are displayed, and my "Last fix obtained" updates every second.) But whenever I click on the "My Location" button in GMaps WV, the spinner (inside the button) just spins forever and the app never finds my location.
The microG Settings applet "Location modules" shows that I have 0 backends configured, but I assume that this is correct as I want to use neither "Network-based geolocation modules" (such as Mozilla Location Service) nor do I want to use "Address lookup modules" (such as Nominatim) - I just want to use my GPS.
I have not yet logged a bug against GMaps WV in case I have not set this up correctly. Does anyone here know whether this should work or not? If I have only clean-installed "LineageOS for microG" and the GMaps WV app (via fdroid), should I be able to use my GPS to find my location? Thank you for your help!
(FWIW, the versions are "LineageOS for microG" 18.1 20220516 and GMaps WV v1.8)
The microG Settings applet "Location modules" shows that I have 0 backends configured, but I assume that this is correct as I want to use neither "Network-based geolocation modules" (such as Mozilla Location Service) nor do I want to use "Address lookup modules" (such as Nominatim) - I just want to use my GPS.
I have not yet logged a bug against GMaps WV in case I have not set this up correctly. Does anyone here know whether this should work or not? If I have only clean-installed "LineageOS for microG" and the GMaps WV app (via fdroid), should I be able to use my GPS to find my location? Thank you for your help!
(FWIW, the versions are "LineageOS for microG" 18.1 20220516 and GMaps WV v1.8)
Edit: I stand corrected. See below.
Last edited:
kurtn
Senior Member
Tried on several devices. Nominatim is not needed. But a short signal from a location backend. After that the gmaps wv app can work with satellite location. If you don't want to share your location with mozilla, install déjà vu
I've just tried this using déjà vu and it "works". I still think that this is a bug, however, so I'll submit a bug report to the gmaps wv issue tracker. Thank you for the workaround - I will include this info in the bug report.
I clean-flash my chosen rom (*) onto my Oneplus 5T and then boot into system to make sure that everything is good. I then attempt to upgrade Services Core (from the included 0.2.24 to the current 0.2.27) : I reboot into TWRP, copy the latest Services Core apk over
What am I doing wrong? (I thought that over-writing the relevant apk with a later version was an acceptable way of upgrading microg.
) Also, if I should open a bug report, does anyone know the best place to do so?
(*) Yes, I know this is an old version, but that's the one I want.
/system_root/system/product/priv-app/GmsCore/GmsCore.apk and reboot into system, but the phone does not complete its boot. After about a minute of boot animation, the phone reboots itself back into recovery (I think this is called the Android Rescue Party!)What am I doing wrong? (I thought that over-writing the relevant apk with a later version was an acceptable way of upgrading microg.
) Also, if I should open a bug report, does anyone know the best place to do so?(*) Yes, I know this is an old version, but that's the one I want.
You can update it by simply installing the apk inside Android.I clean-flash my chosen rom (*) onto my Oneplus 5T and then boot into system to make sure that everything is good. I then attempt to upgrade Services Core (from the included 0.2.24 to the current 0.2.27) : I reboot into TWRP, copy the latest Services Core apk over/system_root/system/product/priv-app/GmsCore/GmsCore.apkand reboot into system, but the phone does not complete its boot. After about a minute of boot animation, the phone reboots itself back into recovery (I think this is called the Android Rescue Party!)
What am I doing wrong? (I thought that over-writing the relevant apk with a later version was an acceptable way of upgrading microg.
(*) Yes, I know this is an old version, but that's the one I want.
If you really want to manually replace the apk in the system partitions you also have to edit the relevant xml for privileged permissions (and if needed also update the relevant extracted libraries).
Hi,
I'm at loss as to where to report what could be bugs on LOS MigroG. Hopefully this is the right place. On my main phone (a Fairphone 3) that was on LOS 19 microG, I dirty flashed LOS 20 microG that went out about 4 or 5 days ago (https://download.lineage.microg.org/builds/full/FP3/lineage-20.0-20230403-microG-FP3.zip). The reboot went smoothly. However, the install of updated apps through Aurora would fail.
Thinking a reboot might solve this, I went for it, and alas, I get a bootloop (the animated LOS logo stays for a long time, eventually leading to a reboot). Reapplying the LOS4MG upgrade doesn’t fix anything. And today I realise that the build was withdrawn, and no other LOS4MG v20 is available yet (https://download.lineage.microg.org/FP3/). Is that withdrawal related to my issue? Any idea of what could be wrong? Is there any way to revert to a functioning phone (I fear that dirty flashing the latest LOS4MG 19.1 image would make things worse)?
I'm at loss as to where to report what could be bugs on LOS MigroG. Hopefully this is the right place. On my main phone (a Fairphone 3) that was on LOS 19 microG, I dirty flashed LOS 20 microG that went out about 4 or 5 days ago (https://download.lineage.microg.org/builds/full/FP3/lineage-20.0-20230403-microG-FP3.zip). The reboot went smoothly. However, the install of updated apps through Aurora would fail.
Thinking a reboot might solve this, I went for it, and alas, I get a bootloop (the animated LOS logo stays for a long time, eventually leading to a reboot). Reapplying the LOS4MG upgrade doesn’t fix anything. And today I realise that the build was withdrawn, and no other LOS4MG v20 is available yet (https://download.lineage.microg.org/FP3/). Is that withdrawal related to my issue? Any idea of what could be wrong? Is there any way to revert to a functioning phone (I fear that dirty flashing the latest LOS4MG 19.1 image would make things worse)?
I am also wondering why the latest build - for p7 [panther] in my case - has been withdrawn. Updated via ota and no issues so far other than an irregular high idle drain (~1%/h). Is it safe to use it going forward or should I revert? Any advice would be helpful. Thanks a lot in advance.
The latest builds have been withdrawn because if problems with F-Droid: see here for details. New builds should be along soon
So, https://download.lineage.microg.org/FP3/lineage-20.0-20230410-microG-FP3.zip is out, but I still bootloop.
Any clue as to get out of it without wiping + reflashing?
I see https://download.lineage.microg.org/FP3/lineage-20.0-20230407-microG-FP3-boot.img just got published, could it be of any use?
Sorry, I don't quite understand. Now I have LineageOS 20, in guide installation need migration from LineageOS - LineageOS + microGaps. For this I just need boot in preinstall LineageOS recovery (not LIneageOS+microGapps recovery), factory reset and clear all Data, and then turn on ADB mode and install the LIneageOS+microGapps rom? Why then do the developers post the lineage-20.0-20230407-microG-kebab-boot.img and
lineage-20.0-20230407-microG-kebab-recovery.img?
Do they also need to be pre-installed before flashing lineage-20.0-20230412-microG-kebab.zip rom?
lineage-20.0-20230407-microG-kebab-recovery.img?
Do they also need to be pre-installed before flashing lineage-20.0-20230412-microG-kebab.zip rom?
kurtn
Senior Member
You have lineageOS or lineageOS with GApps? And dont say "mictoGaps" microG is no GApps.
I simply sideloaded lineage4microG like a normal update on official lineageOS without GApps.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1Not dead.
So, it seems Lineage4MicroG is dead, right?
No updates after may 3 and some builds just disappeared
1 -
161Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)
This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..
You can find us on https://lineage.microg.org
XDA:DevDB Information
LineageOS for microG, ROM for all devices (see above for details)
Contributors
Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
Source Code: https://github.com/lineageos4microg
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-11-06
Last Updated 2020-08-2824Just to give a small heads up. As you may noticed some of the project members the priorities have shifted to other projects.
I was and am still willing to take over some of the tasks, but as microG lacked some bugfixes and support for LineageOS 17.1 i was not sure whether its worth it to spend more time into LineageOS for microG. Once marvin released the new microG update, we still had to check with our team, how we'll proceed.
For now i've taken over the responsibility of the Android Build process, merged some of the fixes and integrated LineageOS 17.1 support. New builds are on their way, both LineageOS 16 and 17.1 based.
Best
Simon15Hey guys. You are right with your findings. We were testing yesterday LineageOS 15.1. But we rolled it back. Now we have almost everything ready for Lineage 15.1 - In fact there is one minor change outstanding before we're going to release. After release we'll start building the complete LineageOS weekly build roster again.14Current device list which will be built tomorrow:
Code:a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855, deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100, i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme, serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L13
Yes they are rolling out new builds again Thank you everyone who is contributing to this :good:
We have decided to build every device weekly (like before), as we don't have the capacity to build for ~75 devices daily and nightlies are quite useless to the end users. We will build for all the ~200 devices, ~30 devices per day, from top to bottom of the usual hudson devices list (which means that 15.1 builds will appear in the first part of the week and 14.1 in the second one).
As usual, new devices will be automatically added to the build list, no need to ask for them, just wait some days.
