LineageOS for microG

Search This thread
By:
Advanced…
J

JamesKinds

Senior Member
Nov 30, 2007
237
97
n76 said:
Darned the XDA app for Android cutting off all of my reply that started after the accented Deja Vu. I will try to recreate my lost post with out the accents. . .

<snip>

Source for above: I am the author of those back ends.
Click to expand...
Click to collapse

Thanks you for the detailed post. I truly appreciate you taking the time to write up those details. I've searched for details in the past but never found anything as succinct as your write up.

It's good to k ow and I will certainly use the NLP is the future if my situation warrants it. At the moment I am very lucky that my current phone (Pocophone F1) has a very speedy GPS lock and that works for most of my needs.

However I will look forward to using the NLP providers you mentioned in the future as needed.

Keep up the great work. Your contributions are helping tons of people.

Thanks again
 
  • Like
Reactions: lichtblitz
L

la0pe0Ue

Senior Member
Jan 9, 2018
58
33
kurtn said:
It sounds like @Setialpha can build a patch for that issue in nanodroid. Or he has already? Can you flash nanodroid and test?
Click to expand...
Click to collapse

After googling, it seems to me that introducing Qualcomm Location poses a significant risk to privacy since it will implicitly collect user data, including geolocation, tower, WiFi and IP address. It is very difficult for me to understand the official position of Lineage OS Team on this. Therefore it is not only a technical issue, much more serious.
 
Last edited:
  • Like
Reactions: Exabyter, SGH-i200, selfishjelly and 1 other person
G

githyanki

Senior Member
Mar 11, 2009
1,662
879
Edmonton
la0pe0Ue said:
After googling, it seems to me that introducing Qualcomm Location poses a significant risk to privacy since it will implicitly collect user data, including geolocation, tower, WiFi and IP address. It is very difficult for me to understand the official position of Lineage OS Team on this. Therefore it is not only a technical issue, much more serious.
Click to expand...
Click to collapse
I can tell you Lineage's official position on this subject. "We told you so! Now go install Google package as your supposed to and stop using that insecure microG project."
Lineage does not allow signature spoofing on official builds, that's why this is a separate project. Also, this project defaults to the Mozilla location backend,, if your wondering their position.....
 
Last edited:
  • Like
Reactions: Exabyter and SGH-i200
L

la0pe0Ue

Senior Member
Jan 9, 2018
58
33
githyanki said:
I can tell you Lineage's official position on this subject. "We told you so! Now go install Google package as your supposed to and stop using that insecure microG project."
Lineage does not allow signature spoofing on official builds, that's why this is a separate project. Also, this project defaults to the Mozilla location backend,, if your wondering their position.....
Click to expand...
Click to collapse

I am not aware of the current situation, but before we could install UnifiedNlp as a location provider without the whole microG, which does not require signature spoofing. I don't think that signature spoofing is a good thing: it is used to fight against a worse thing: Google makes the Google service almost necessary in the Android ecosystem.

Anyway, Lineage OS does not per se contain Google's proprietary blobs of Google services. It is us, users need that kind of service to run apps. However, the introduction of Qualcomm Location is of a quite different nature: it is a proprietary blob inserted into key apps in the OS (as a priv-app). This should be at least questioned because Lineage OS is supposed to be free and open source, so at least should not contain proprietary blobs unless it is strictly necessary.
 
  • Like
Reactions: SGH-i200, lichtblitz, guest4711 and 2 others
W

Wintonson

New member
Jan 21, 2016
2
0
33
Dickinson
Issues Updating

I am having issues updating. When using twrp to install, I get boot loop. Using lineageos recovery install works through adb sideload but cannot get it to update. How are you guys updating the rom on your phones?
 
kurtn

kurtn

Senior Member
Jan 28, 2017
5,220
2,379
Small town in Bavaria
POCO M2 Pro
OnePlus Nord N10 5G
Wintonson said:
I am having issues updating. When using twrp to install, I get boot loop. Using lineageos recovery install works through adb sideload but cannot get it to update. How are you guys updating the rom on your phones?
Click to expand...
Click to collapse
Bootloop is usually no ROM problem, but your addons. What zips did you flash after last wipe of system?
Update path is through settings / system / advanced
 
M

marconxda

Member
Jan 22, 2017
9
5
This commit MUST be reverted!

It effectively destroys the free choice of NLP providers and imposes severe privacy issues by collecting mentioned data using a unique id. I do not understand, how this commit could ever be accepted. At least users should be asked and have the option to take part in this data dealing game...

Anyway, if one wants to compile from source by oneself, how this could be effectively reverted? (I'm not completedly new to this, have compiled Lineage for microg before, but without any changes and others systems like libreelec, openwrt ... too). But here, I'm confused.

In config.xml in .../frameworks/base/core/res/res/values both variables do have the right values. I suspect that the settings in overlay/frameworks/base/core/res/res/values overrule these.
So, how to change this behaviour? I even don't see any overlay/... in the Lineage source tree... :confused:

Could somebody please kindly explain or give a step by step, where to make the appropriate changes and then how to compile?
 
  • Like
Reactions: SGH-i200
kurtn

kurtn

Senior Member
Jan 28, 2017
5,220
2,379
Small town in Bavaria
POCO M2 Pro
OnePlus Nord N10 5G
marconxda said:
This commit MUST be reverted!

It effectively destroys the free choice of NLP providers and imposes severe privacy issues by collecting mentioned data using a unique id. I do not understand, how this commit could ever be accepted. At least users should be asked and have the option to take part in this data dealing game...

Anyway, if one wants to compile from source by oneself, how this could be effectively reverted? (I'm not completedly new to this, have compiled Lineage for microg before, but without any changes and others systems like libreelec, openwrt ... too). But here, I'm confused.

In config.xml in .../frameworks/base/core/res/res/values both variables do have the right values. I suspect that the settings in overlay/frameworks/base/core/res/res/values overrule these.
So, how to change this behaviour? I even don't see any overlay/... in the Lineage source tree... :confused:

Could somebody please kindly explain or give a step by step, where to make the appropriate changes and then how to compile?
Click to expand...
Click to collapse
You talk about a new kind of Qualcomm network location "feature"? Does it come with a proprietary blob?
 
L

la0pe0Ue

Senior Member
Jan 9, 2018
58
33
marconxda said:
This commit MUST be reverted!

It effectively destroys the free choice of NLP providers and imposes severe privacy issues by collecting mentioned data using a unique id. I do not understand, how this commit could ever be accepted. At least users should be asked and have the option to take part in this data dealing game...

Anyway, if one wants to compile from source by oneself, how this could be effectively reverted? (I'm not completedly new to this, have compiled Lineage for microg before, but without any changes and others systems like libreelec, openwrt ... too). But here, I'm confused.

In config.xml in .../frameworks/base/core/res/res/values both variables do have the right values. I suspect that the settings in overlay/frameworks/base/core/res/res/values overrule these.
So, how to change this behaviour? I even don't see any overlay/... in the Lineage source tree... :confused:

Could somebody please kindly explain or give a step by step, where to make the appropriate changes and then how to compile?
Click to expand...
Click to collapse

I encourage you to complain at https://gitlab.com/LineageOS/issues/android/issues/1270 and somewhere else where LineageOS Team frequently looks at (maybe reddit?), since there is little affect to just reply here. I would like to stress again that LineageOS is advertised to be free and open-source, therefore the introduction of unnecessary proprietary blobs should always be at least questioned. Plus the privacy issue - this is important but not as striking as "free and open-source" at the homepage of LineageOS.
 
  • Like
Reactions: SGH-i200
M

marconxda

Member
Jan 22, 2017
9
5
Googleing, Qualcomming and the way out

kurtn said:
You talk about a new kind of Qualcomm network location "feature"? Does it come with a proprietary blob?
Click to expand...
Click to collapse

Yes, at least that's how I understand la0pe0Ue.

Some automatisms on my phone depend on the results of UnifiedNLP. They ceased to work because UnifiedNLP doesn't work any longer, because of the above mentioned commit that blocks alternative location providers and pushes data to Qualcomm. So users' phones are effectively crippled to support a company's data collection behaviour!


There are 3 possible solutions to this:

1. LineageOS reverts it (best one, all users of Lineage and its descendants will profit)

2. Lineage for microG reverts it (that's why I posted in this forum: it doesn't make any sense to take the burden of creating and distributing a system, that substitutes Google by Qualcomm, when they play the same game)

3. Users reverts it by themselves (highest effort but rewarding from an intellectual standpoint ;))


I successfully compiled Lineage for microG using the Docker image on github.

But I don't know where to interrupt the building process to stop overlay/frameworks/base/core/res/res/values/config.xml from interfering with the standard values of config_enableNetworkLocationOverlay and config_enableFusedLocationOverlay.

Would be glad to get any suggestions!
 
Last edited:
  • Like
Reactions: lichtblitz, SGH-i200 and kurtn
bege10

bege10

Senior Member
May 26, 2018
247
69
Germany
Reboot after turning on mobile data

For about a month I have a new issue on Samsung Galaxy S5 Plus (SM-G901F), LineageOS for microG 16 (Android 9):
If I turn on mobile data for the first time after the phone has booted it immediately reboots most times. It is not a complete reboot but rather a reboot of the system UI: Black display for a short moment, no Samsung boot screen, no LineageOS boot screen, no SIM card unlock code. The phone is locked, after unlocking the display boot operations like scanning the external SD card run. The status bar shows both the SIM provider name and SIM card not available. Calling is not possible. I have to reboot the phone completely. As mobile data is turned on then the problem does not occur again until the next boot.
Following activations of mobile data do not trigger that issue.
Can someone confirm this or have an idea what the reason may be?
 
Last edited:
You must log in or register to reply here.

Similar threads

Phil3759
[2015.10.09]CWM 6.0.5.1 - PhilZ Touch 6.59.0 (libtouch_gui 1.42)
Replies
6K
Views
4M
A
aminelove
jajb
[GAPPS][2015-04-04] Google Apps Minimal Edition for Android 5.0.x & 5.1.x
Replies
1K
Views
1M
thiago_727
thiago_727
M
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Replies
7K
Views
2M
landry314
landry314
iBotPeaches
[UTIL][JAN 20, 2024] Apktool - Tool for reverse engineering apk files
Replies
6K
Views
2M
Z
Zhelkek
madmack
[APP][ROOT] FolderMount - Link folders from internal SD to external to free space
Replies
4K
Views
1M
ArmagedFoxer
ArmagedFoxer

Top Liked Posts

24 Hours 30 Days All time
  • 1
    kurtn
    kurtn
    ToughDBlue said:
    Does LOS for microG support locking of the bootloader for a Pixel 7?
    Click to expand...
    Click to collapse
    No. Use calyxos or divestOS
    View
    1
    P
    petefoth
    ToughDBlue said:
    Does LOS for microG support locking of the bootloader for a Pixel 7?
    Click to expand...
    Click to collapse
    For device-specific information like this, best to look in the LOS Device Wiki pages for your device

    The default for most devices re-locking bootloader is not possible. If it is possible for a specific device it will be mentioned in the device's LOS Wiki pages. Nothing mentioned there for this devices so it seems it's not possible
    View
  • 2
    P
    petefoth
    Some more information on why the March QPRS update caused the 21.0 builds to fail: https://www.reddit.com/r/LineageOS/comments/1bp83tb/_/kwvut4m
    kurtn said:
    The 18.1 branch still has security patches. They don't get merged. So you have to pick them
    https://review.lineageos.org/q/topic:"R_asb_2024-03"
    Click to expand...
    Click to collapse

    Thanks, but from my (very limited) understanding of Gerrit, those changes have been implemented, but not been verified or code reviewed. So they are not, and will not be, merged to the main `lineage-18.1` branch, and LineageOS won't be making and publishing builds which include the changes.

    Our project scope is to build for the same devices as LineageOS build for, so the changes aren't a lot of use to us. I don't know how we would go about 'picking' them for our builds, even if a: we had the resources to do so and b: we are happy to make builds including unverified, unreviewed code, which we don't
    View
    2
    O
    Oelmuvun
    petefoth said:
    Keep an eye on the matrix room to see when the build finishes
    Click to expand...
    Click to collapse
    Just wanted to say thanks for running the nio build. After a couple months of crashing in standby and then the delays related to the recent build issues, I was getting ready to nuke&pave with vanilla lineage until I came across this thread. Started watching the matrix room with bated breath when I saw a nio build begin last night!

    I have been hearing a lot of positive things about recent Lineage 21 builds for the nio, so fingers crossed that this stays stable. Thanks again.
    View
    2
    P
    petefoth
    2faraway2 said:
    Hi guys, it seems that we have to say goodbye the mozilla location service (MLS), it will be retired soon ..
    Imho that meens, that shipping the mozilla location location service will be no longer necessary.

    The question is, which version of microG should be included in the upcoming builds ?
    More about mar-v-in's future plans here
    <snip>

    @petefoth : Do you already have an idea how and when integrate a new microG version ?
    Click to expand...
    Click to collapse
    At the moment, our builds include the latest `stable` Microg components from https://microg.org/download.html (currently GmsCore is `0.2.27.223616`). We also include the microG F-Droid repo pre-configured, so that users can receive updates. Users can choose to allow beta updates of microG, allowing them to pick up the latest beta versions. This is what I do, so I'm running `0.3.1.240913` on my daily driver device.

    I see no reason to change this approach at the moment. I guess mar-v-in will start by shipping his new versions as betas, which users will be able to try out if they wish. Eventually, with luck, the changes will become stable, and we will then include them in our build for all users. Until that happens, users will have to accept that MLS will stop / has stopped working, and live with the reduced performance: the fix is going to come from mar-v-in, and we will include it as normal.
    View
    2
    P
    petefoth
    All the 20.0 builds are complete. Let's hope that 21.0 upstream builds are fixed in time for next month's build run.

    The final 18.1 builds have been moved to https://download.lineage.microg.org/archive/
    View
    1
    P
    petefoth
    heinhuiz said:
    Are there any problems with that device?
    Click to expand...
    Click to collapse
    Yes - there was an error while building the kernel.Probably caused by a change made in the kernel code repo during the build run. With luck it will get built in the next build run - see below
    heinhuiz said:
    Also, the latest build overall is almost a week ago.
    Click to expand...
    Click to collapse
    Yes, we run builds once per month. The next build run will start at 00:01 on 1st April. There will probably only be 20.0 builds because
    • upstream 18.1 builds have stopped and the 18.1 branch has reached 'end-of-life'
    • 19.1 devices were all promoted to 20.0 a couple of months ago
    • 21.0 builds are broken upstream
    View
  • 168
    S
    Simon94
    Android 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-28
    View
    24
    S
    Simon94
    Just 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
    Simon
    View
    15
    S
    Simon94
    Current 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,Z00L
    View
    15
    S
    Simon94
    Hey 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.
    View
    13
    N
    ncorna
    baxxter106 said:
    today i got my weekly(?) update with november security patches via ota notification.
    thanks for that!
    Click to expand...
    Click to collapse

    vildevilde said:
    Yes they are rolling out new builds again :) Thank you everyone who is contributing to this :good:
    Click to expand...
    Click to collapse

    kurtn said:
    Oops. They only build Oreo right now.
    Click to expand...
    Click to collapse

    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.
    View

New posts