yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with November 2020 ASB fixes available

Hi all,

a new build is available for download and will soon be available via OTA updates:

https://sourceforge.net/projects/li...NOFFICIAL-microG-signed-oneplus3.zip/download

ASB Security string 2020-11-05

Kernel: Upstreamed to tag ASB-2020-11-05_3.18

Kernel: Fix of bug causing crashes with Wireguard in native mode

Fix of AOSP E-Mail widget

Fix for CVE-2020-15999

Bromite Webview on 86.0.4240.181

Updated microG with fixes in GCM and EN API

Replaced weak F-Droid signatures with ROM's V2 signatures (see note below)

Please note:

The F-Droid and F-Droid privileged extension have been re-signed with this ROM's signing key. F-Droid keeps compatibility also to older Android versions, which however results in the necessity to use weak V1 signatures. In addition, they don't use V2/V3 signatures. To overcome this issue, the F-Droid apps have been built from source and V2-signed with the ROM's signing key.

You therefore need to de-install any updates, if you have made any - do do so, simply deactivate F-Droid and F-Droid privileged extension and activate them again. In case there were any updates, they will be de-installed and you will have as a result the delivered re-signed apps in their newest version.

(Alternatively, connect to the phone via adb and enter the command adb shell pm uninstall-system-updates)

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] soozie_:
Thanks for the update.

This may be apparent to others, but just wanted to know if I this step of de-installing the updates is to be done after or before updating (over OTA).

( In case it matters, I'm on Sept build)

Thanks
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I recommend to connect the phone via adb to your PC and run the command 'pm uninstall-system-updates' before updating.
[OnePlus 3 & 3T Cross Device Development] parlaphone:
Hello MSe1969,

Thank you for all of your work, it is greatly appreciated.

Is Spotify on the iptables exception list? With Net Monitor I can see Spotify is still connecting to a Facebook edge location.

I checked the thread for the LineageOS 15 version of your rom but couldn't discern how to edit the hosts file.

Thanks again for your help
[OnePlus 3 & 3T Cross Device Development] MSe1969:
No, it is not - which location is it connecting to?
[OnePlus 3 & 3T Cross Device Development] parlaphone:
31.13.93.19

edge-star-shv-02-dfw5.facebook.com

I'm not able to connect to Facebook via browser but this IP continues to show in Net Monitor when opening Spotify.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with December 2020 ASB patches available

Hi all,

a new build with December ASB fixes is available for download and already offered as OTA via updater app:

https://sourceforge.net/projects/lin16-microg/files/oneplus3/lineage-16.0-20201211-UNOFFICIAL-microG-signed-oneplus3.zip/download

ASB Security string 2020-12-05

Kernel: Upstreamed to tag ASB-2020-12-05_3.18

Bromite Webview on 87.0.4280.106

Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)

Updated F-Droid to 1.10-alpha1-114

Please note:

I have meanwhile worked on bringing this build to LineageOS 17.1 and use since a week the LineageOS 17.1 build as my daily driver on my own device. I will shortly post a link to this build, to obtain also feedback from you guys, before officially shipping it. More to come, stay tuned.

Happy flashing!

Cheers, M.
[OnePlus 3 & 3T Cross Device Development] :
Hi everyone, does this ROM have Galileo GNSS support?
[OnePlus 3 & 3T Cross Device Development] soozie_:
A quick google search showed that it should be enabled in device chipset and oneplus 3T is not one of them.

Edit

Thanks for pointing out nvertigo67.

SD 820/21 is among the supported ones

Link
[OnePlus 3 & 3T Cross Device Development] :
Both socs (sd820/1) support galileo. I've explained in several threads, if somebody can point me to a sd820/1 equipped device with an android 9 based manufacture shipped rom supporting galileo, there's a good chance to get it working on los 16 based roms.
[OnePlus 3 & 3T Cross Device Development] :
Lenova Zuk Edge(Oreo) and Samsung Galaxy Tab S3 LTE(PIE) I posted to but you forgot, I know you are very bussy so no worries.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Thanks, flashed a new build, so far no problems.

Regarding 17.1: does this mean your LOS16 build is gonna be deprecated? If so, I'd like to share my concern about missing Privacy Guard, new permission hub is not a proper replacement, as it doesn't allow to spoof permissions, like Privacy Guard or XPrivacy. Also, in my very personal opinion, newer Android versions don't bring much new stuff to the table, so in my, again, personal case, I don't see any benefit of losing Privacy Guard to get some new minor features.
[OnePlus 3 & 3T Cross Device Development] :
I havn't forgotten to look at those, but I probably forgot to give feedback: I can't get the zuk blobs working on 16.0 (interestingly the custom roms for zuk doesn't use the gps blobs, but kang them from some other device without galileo support), the sammy blobs break booting (sammy is always different, maybe die to different bootloader design, though I don't understand the impact of the bl on gnss).
[OnePlus 3 & 3T Cross Device Development] :
Thx for the reply. So where does this take us? I have found a third device, the Sharp Aquos P1 Im not sure if it would help with another obscure phone, it has even a worse situation then the Zuk.

How did Oneplus work on GNSS?
[OnePlus 3 & 3T Cross Device Development] :
I can't find a download: https://www.sharpconsumer.com/support/gave me

Search results for: Sharp Aquos P1

Nothing found
[OnePlus 3 & 3T Cross Device Development] MSe1969:
LineageOS 17.1 Test build

Hi all,

here is my LineageOS 17.1 Test build - feedback welcome:

https://sourceforge.net/projects/lin17-microg/files/oneplus3/lineage-17.1-20201211-UNOFFICIAL-microG-signed-oneplus3.zip/download

You can "dirty-flash" it over my 16.0 build (but don't forget to make a backup in TWRP to be able to get back to 16.0). I have worked on taking over the features of my 16.0 build as much as applicable/possible:

Patch level:

ASB Security string 2020-12-05

Kernel: Upstreamed to tag ASB-2020-12-05_3.18

Bromite Webview on 87.0.4280.106

microG 0.2.14.204215-15 (picked until 720b089)

Ported features:

Pre-installed microG and F-Droid same as the LineageOS for microG project

Pre-installed AuroraStore

eSpeak TTS engine (FOSS TTS solution)

Additional security hardening features listed below:

Cloudflare as default fallback DNS (instead of Google)

Privacy-preferred default settings

Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)

Optional disable captive portal detection

Increased max. password length of 64

No submission of IMSI/phone number to Google when GPS is in use

Default hosts file with many blocked ad/tracking sites

Privacy-enhanced Bromite SystemWebView

Firewall (control internet access per app - under Trust)

Constified JNI method tables

(Note: Access restrictions to /proc/net are now implemented by default in Android 10)

New features:

Bromite as default browser

Set different captive portal detection URLs (default is GrapheneOS and not Google; Settings - Network & Internet)

Extra control of sensor access for additionally installed user apps (Special access under app permissions)

Hardened memory allocator lib (see GrapheneOS)

Seedvault backup app (this is shipped by standard LineageOS, but I wanted to still mention it)

Lost/abandoned features:

Privacy Guard (abandoned in LineageOS 17.1)

Native WireGuard support

LineageOS Root AddOn

LockClock app *

In an extra post, I will write some comments about the lost features.

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] :
I only found a 4PDA link on the Sharp phone and not on XDA

Sharp AQUOS P1 - Обсуждение - 4PDA

Sharp AQUOS P1 - Обсуждение, Смартфон, 5.3"

4pda.ru

I mean yeah its a dead end on 820/821 phones and tablets, some say Lenovo ZUK Z2 Pro has Galileo but after watching reviews its not true. Treble would be the cause SD835 got Galileo. Hypothesis, after the SD820/821 series got replaced by the SD835, where the 820/821 architecture downgraded to the SD6XX series chipset? Would the solution be found there?

Edit: What about open sourced implementation of GNSS?
[OnePlus 3 & 3T Cross Device Development] :
Hi gotto ask, what does Sony have to do with Location service for the Oneplus 3/T?
[OnePlus 3 & 3T Cross Device Development] gonococcus:
That's as sad as it is inevitable

Yes, PG is known to be glitchy sometimes and there are ways to work around it for app devs(thank Google for the whole zoo of different-but-the-same APIs). The blessing was is that LOS is not nearly as popular as stock ROMs, so no one would bother.

It was also mostly abandoned by LOS devs, so instead of fixing it to work in a more reliable way, they just killed it, which is still a big regression, in my view.

Kudos for your attempt to port it, but even if you've succeeded, it would probably too much to ask you to maintain it to keep it working in future builds.

That one I actually didn't see coming. Because the deal is that if you have root, you can use kernel support, if you don't have root, you just use userspace implementation. I don't see how it would hurt to ship kernel support for those users who want it, as it doesn't take anything away from non-rooted users - Google has even included wireguard kernel support starting from Android 12. However, it also depends if it's pain in the ass for you to maintain it: as far as I've heard patches are pretty simple to apply, but you also use other patchsets, so your mileage may vary, of course.

That said, I'll probably stay on 16 as long as possible(until there's a new RCE vulnerability or smth). Not only because I will miss Privacy Guard(XPrivacyLUA is a potential solution here, but needs xposed), but also because I don't really see what benefits 17.1 brings.

I do believe hardening makes things potentially more secure, but from my experience in the field the biggest attack vector is human factor, so additional hardening is not the main feature of this ROM for me, but microg, privacy features and removing Google crap like captive portal and DNS - those have much more value for me. So yeah, in the end, I don't feel it's worth updating for me.

As always, thank you for your work!
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for notifying me, that was a copy/paste glitch from a post in the amami thread, which I have fixed. Of course, no Sony here.
[OnePlus 3 & 3T Cross Device Development] soozie_:
I'm not that savvy in terms of android development but move to 17.1 does looks exciting. Apart from security and privacy (enhancements), there are some good UI changes as well that I'm looking forward to.
[OnePlus 3 & 3T Cross Device Development] :
The used opensource part of the gnss stack isupporting galileo, as far as I understand the sources:

android_device_oneplus_oneplus3/gps/core/LocApiBase.cpp at lineage-16.0 · lin16-microg/android_device_oneplus_oneplus3

Contribute to lin16-microg/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com

EDIT: Enter sended again instead of inserting a linefeed, seems to haapen only after paste...

android_device_oneplus_oneplus3/gps/gnss/GnssAdapter.cpp at lineage-16.0 · lin16-microg/android_device_oneplus_oneplus3

Contribute to lin16-microg/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com

android_device_oneplus_oneplus3/gps/location/LocationAPI.h at lineage-16.0 · lin16-microg/android_device_oneplus_oneplus3

Contribute to lin16-microg/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com

That's why I hope for sd821 galileo supporting blobs. Early (oos 3x) there has been a statement in the oneplus forum, that galileo will be supported in future updates, butit has never been implemenzed by oneplus.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Unless I receive feedback about severe issues, I plan to start a thread with my current test build as initial build and provide a final 16.0 build in this thread in January.

As I have also a "Treble" thread for the Huawei P9, I will continue keeping the sources of Lineage 16.0 up to date.

So building the 16.0 ROM yourself could maybe be an option for you (you would have to migrate the ROM's signature, of course)?

I had at first a similar impression of unwillingness on LineageOS side, that is why I started to try on my own. As indicated, I have changed my point of view and definitely see the issues - the major overhaul of the AppOps API by Google and the major overhaul of certain system services, which are heavily used by the PG "ask mode" has made it most probably impossible to port PG, without entirely re-designing it - at least the "ask mode" part, which is the true core-feature of PG.

Of course, I am by far not a skilled (Android) Java programmer, so my judgement could simply be based on my own limitations (in fact I have almost no experience in Java, but I do have profound programming experience in general, which has enabled me to also do Java stuff for Android). But I do respect now their decision to abandon it.

Well, the inclusion indeed

is

easy, almost trivial. And there is not much to do with additional tags, as it seems that the WG development for that sub-project has been finished, so only small bugfixes are added each month. From that point of view, you would be right and it should be a no-brainer. I also see your point in suggesting to simply leave it in.

However, each feature shipped is also expected to be supported - @nvertigo67 and I have spent hours in finding the one bad commit, when applying the kernel upstream fixes last time. And that is, where my decision comes from and what causes the p.i.t.a. - ok, could be, that this was a one-off exception and will never happen again, who knows? But I consider it more honest to stop shipping a "courtesy/favor" feature (in which I am at least right now not fundamentally intrerested myself) and annouce it, rather than continuing it and - when the next major issue comes - simply state "hey guys, tough luck - I confirm it's an issue, but I am not in the mood to fix it". And also, my stated argument persists, that it does not make sense to me to ship a feature, which can only be activated, if a root solution will be flashed.
[OnePlus 3 & 3T Cross Device Development] :
Oneplus like many others didnt add support. Maybe cost because Qualcomm is greedy or there needsto be extra hardware. we dont know. Maybe GnssStatus.getCarrierFrequencyHz() is missing or some other API. Did you enable full GNSS measurments in developer options? I was able to get a EU SBAS in my radar.

The dev behind GPStest just started to collect data on devices GNSS tech. There where many classifications. I think all 820/821 phones intercept the raw GNSS but cant decode QZSS ,Galileo, NavIC, GAGAN signal. As of now there are no other phones with possible blobs to experiment with then the Edge and S3. Question would CAF software help?
[OnePlus 3 & 3T Cross Device Development] :
The source of the opensoirce based part of the gnss stack is actually caf:

History for gps - lin16-microg/android_device_oneplus_oneplus3

Contribute to lin16-microg/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com
[OnePlus 3 & 3T Cross Device Development] :
All right now I know. One thing I found out is that many budget LG devices since 2017,2018,2019 have been released with the 821 but has no Galileo.Same with the 820A for cars and 820E for single board computers since 2019. Also Idk what Oneplus did but I remember that there where many GPS "fix updates ", no idea what they fixed, could be updates for the A-GPS,A-Glonass. I dont think Oneplus unoffically added Galileo support without the certification, I looked up every satallite number I collected from GNSSlogger and I saw no Gallileo in the report.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi,

first of all, thanks for your feedback and your positive opinion about my 16.0 build!

I am going to comment on the technical aspects on the 16.0 => 17.1 ROM switch further below.

To your other comments - I am - like you - not really a "Google fanboy" (you have stated it less diplomatically than me, but you're right) - otherwise I would not have tried to create a ROM, which I could at least use to an extent, I am able to tolerate.

The firewall commits haven't been merged by LineageOS, yet. This is in fact "version 1", in 16.0, there was a "version 2" moving it to network/data, which hasn't been picked into 17.1 yet. In 17.1, there is also a newer patch set, but my first attempt to pick that wasn't functional. We'll see...

As indicated, I am using now since two weeks the 17.1 build on my device and I don't have these issues. I am however not using any alternative launcher. Could you please try uninstalling Lawnchair to see whether that fixes? Maybe it would be required to first uninstall any alternative launcher, then dirty-flash and then install any alternative launcher?

I can't reproduce this behavior on my own device at all. Anyhow, all I do it to compile F-Droid from source "as is" for the sake of giving it a different signature. So any issues, the F-Droid app has, should be looked up on F-Droid's issue tracker.

As indicated before, I can't reporduce the behavior - however, in my November update (16.0 build), I have explained, that any updates of the F-Droid app need to be uninstalled. Did you dirty-flash from a pre-November build to 17.1 w/o uninstalling system app updates first, maybe?

Did you simply install and set lawnchair as 2nd launcher, or did you also explicitly do a "pm uninstall --user 0" via adb for Trebuchet? Maybe the latter is the issue?

Maybe the advices given before could solve your issue?

Thanks - that'll be documented accordingly.

The reason for that was explained already in one of my previous posts (PG ask mode not available any longer) - Magisk is the way forward for those wanting root.

Hope that helps, regards - M.
[OnePlus 3 & 3T Cross Device Development] EinsteinXXL:
Where can I find the firewall UI?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
In the regular LineageOS 16.0 build: Settings - Network & Internet - Data usage - Manage data restrictions

In the LineageOS 17.1 Test build: Settings - Privacy - Firewall
[OnePlus 3 & 3T Cross Device Development] EinsteinXXL:
Thanks for your fast answer. (y)

Now to another little problem that I have with your Linage build. I understand your concept of a hardened and google free ROM, but it is unfortunately not 100% possible to use FOSS apps. For example, I use cryptowallets and apps from various exchanges and they often include trackers. Recently I was still using Android 6 with xprivacy, which is no longer possible with Android 8+. Now I am looking for a way to continue to manage different internet connections of an app. Netguard offers this function, but unfortunately not with your hardened version. Netguard is unable to filter network traffic, only fw on/off per app is possible. Is there any workaround to fix this?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
The Netguard app,

if dowloadeed from F-Droid (hence having the F-Droid signature)

is added to the SEPolicy exceptions and thus should be able to work.
[OnePlus 3 & 3T Cross Device Development] EinsteinXXL:
Are there any problems with LineageOS 16 and GPS?? I am unable to get a gps fix.

I got this error msgs in logcat after gps was enabled:

12-21 01:59:22.768: E/GnssLocationProvider(1387): Unable to initialize GNSS Xtra interface

12-21 01:59:22.769: E/GnssHal_GnssGeofencing(547): setCallback]: mApi is NOT nullptr

12-21 01:59:22.770: E/LocSvc_APIClientBase(547): onCtrlCollectiveResponseCb:189] ERROR: 3 ID: 232

12-21 11:21:28.631: W/LocationHelper(2705): java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.

12-21 11:21:28.632: W/LocationHelper(2705): java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.

12-21 11:21:28.632: W/LocationHelper(2705): java.lang.SecurityException: "network" location provider requires ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION permission.

Update: Problem solved. Made clean flash again and it works.
[OnePlus 3 & 3T Cross Device Development] EinsteinXXL:
I am a fan of your privacy friendly LinageOS. Now I have recently switched to a Oneplus 7T Pro. Are there any plans to make a Treble version?
[OnePlus 3 & 3T Cross Device Development] ajash:
Safety net pass Out Of The Box ?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
No.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
@MSe1969

Using your rom for over 2 weeks now in replacement of my own LOS4microg 17.1 build.

So far, super good experience. Thanks a lot!!
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
@MSe1969

Not asking for any ETA nor anything, but just out of curiosity, but do you have any plan for a hardened LOS 17.1 or LOS 18?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I will this weekend start a new thread with the lineage 17.1 successor of this build and publish a final build here.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
LineageOS 17.1 successor thread and final 16.0 build with January 2021 ASB patches

Hi all,

a new build with January 2021 ASB patches is available for download and will soon be offered as OTA update:

https://sourceforge.net/projects/lin16-microg/files/oneplus3/lineage-16.0-20210112-UNOFFICIAL-microG-signed-oneplus3.zip/download

ASB Security string 2021-01-05

Bromite Webview on 87.0.4280.131

Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)

Updated F-Droid to 1.10-alpha1-212

Please note, that this build is the

final

LineageOS 16.0 build. - As announced and as some of you may already have seen, I have opened a new thread for the LineageOS 17.1 successor build of this hardened microG ROM:

https://xdaforums.com/t/rom-unoffic...hardened-lineageos-17-1-oneplus-3-3t.4219383/

You can simply "dirty-flash" the "microG" LineageOS 17.1 build over the "microG" build of this thread. I recommend to go this path in the near future.

Of course, I will keep this thread open for a while and answer topics related to this 16.0 build and how to migrate to the 17.1 successor build. I would like to take the opportunity to thank you for your interest in this build and look forward to seeing you in my new 17.1 successor thread.

Happy flashing, cheers - M.
[OnePlus 3 & 3T Cross Device Development] Fallon9111:
Cheers MSe1969 for keeping this rom going, and I appreciate the great communication you've provided in the forums. I've been using your rom for half a year now, and it works as well as any stock ROM I've used, with lots of added bonuses.

Keeping my 4 year old phone running a modern OS & degoogled is brilliant.

Thanks :)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
You seem to be lucky ;) - I have indeed bought myself a used 7T Pro beginning of this month, so there will soon be a respective thread (this a/b partition thing enforced by G* to all devices initially shipping with 10 is really a p.i.t.a.) . . .

EDIT: https://xdaforums.com/t/rom-unoffic...rdened-lineageos-17-1-oneplus-7t-pro.4222945/
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
Does this mean that in a near future the builds for OnePlus 3(T) will get abandoned in favor of the OnePlus 7 Pro?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
No. I will continue providing builds for the 3(T)
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Thanks as always, I'll be flashing that build soon.

My question is: are microg for 16 and 17.1 compatible? What I'm really asking: would it be possible for me to extract microg apk from your 17.1 and manually drop it into 16.0 to update it?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Yes, that is possible - no issues.

But if your goal is to keep on 16.0 and just update microG, how do you want to easily extract it from the 17.1 zip w/o first flashing it?