yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
The same question:

How can I, staying on this ROM, update the microG app?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
There are three options - each of them has their own advantages and disadvantages, depending on the specific situation and setup (

the 1st step of all actions should be a nandroid backup of your current setup!

):

1. TWRP: Backup - Flash - Copy - Restore - Replace

- Reboot to TWRP

- Make a full nandroid backup of your current 16.0 setup

- (Clean) Flash the most recent LineageOS 17.1 ROM

- Copy the file /system/priv-app/GmsCore/GmsCore.apk to your Internal memory

- Restore your nandroid backup

- Replace the file /system/priv-app/GmsCore/GmsCore.apk with the previously taken copy

- Restore ownership and file permissions, if needed (root:root 644)

- Reboot to LineageOS

2. Extract the GmsCore.apk from my LineageOS 17.1 ROM zip

This was the question from @gonococcus - you need Linux on your PC for this.

The basic approach is described here, the LineageOS 17.1 ROM zip for the OP3T is 'block-based'. We need the system.img file mounted (obviously, we don't want to "extract vendor blobs"), once mounted, you can copy the file /system/priv-app/GmsCore/GmsCore.apk.

Reboot to TWRP and replace that file and make sure, ownership and permissions are set (root:root 644)

3. Go back to the "original" microG

You could also download the original microG file from here and replace the file accordingly in TWRP (details see above).

However - replacing an apk file with another one having a different signature is like uninstalling the app and installing from scratch!

WARNING: If you do so, the following will happen:

- Your GCM registrations will be gone

- If you use a Covid tracing app, the bluetooth token database is empty again

You would need to re-enable the device registration and the cloud messaging and check, whether your apps will re-register. It may happen, that some of your apps can't re-register. If *#*#CHECKIN#*#* from the Dialer app plus reboot does not solve that issue, you would need to uninstall and re-install those apps, which may also require to find out about backing up and restoring the affected app's data . . .

Hence, this approach may (or may not) end up in a lot of follow-on issues.

Regards, M.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Thanks for good news. As for your question: extract the FS image and mount it, then grab APK - just like you answered to @zhenev .

BTW, regarding microG. I was under impression that you merge quite a lot of patches when you build microg and also that official microg is not being built very often to reflect the changes commited. So the question is: how much does your build differ from official build? Did they start to build more often since project /e/ started submitting the patches? A bit in the dark here about microG current situation. I'd rather keep up with your build extracted from 17.1, not that big of a deal to extract it from time to time. but also wondering if they've sped up their release cycle.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I don't know more than you. When you look at their tags (see my link from previous post), it seems that the frequency has improved a lot. I usually look, what is available, when I build the next version to be included in my monthly builds.

When you look at the last three tags, it seems a 3-week cycle meanwhile, at least a decent update frequency. Before, it hasn't been that way, and at the time, when I wanted to publish my monthly builds, there were important commits available, which I did not want to miss.
[OnePlus 3 & 3T Cross Device Development] guywitht679:
hi all, great thanks to mse for developing and maintaining this rom. been using since late december, havent been able to get gps working tho. location is On, permissions have been granted (OsmAnd~; SatStat; several others); nothing can find me. A-GPS data has been repeatedly downloaded but seems to never work. have tried it outside, while driving, same thing. tried FasterGPS, no effect (reverted now). SatStat and GPSTest once picked up a glonass fwiw. im rooted. have checked forums for these different programs to no avail, so im hoping im not wasting your time with this question.

i just dirty flashed the newest 16.0, but it hasnt affected the problem (phone recognizes that the wifi network it's connected to has internet now tho, yay). many thanks for any guidance; gps is very crucial for my job.

EDIT: vendor image out of date, will have to check into it tomorrow. would delete this reply if i could to read into that first.
[OnePlus 3 & 3T Cross Device Development] new_zhenev:
You need turn on location modules in microG settings, if I've understood your problem correctly.
[OnePlus 3 & 3T Cross Device Development] guywitht679:
not sure what changed since last night thru this morning, but it works now lol. thanks for the response though! :)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Heading towards EOL

Hi all,

as already explained in various previous posts, I have created a LineageOS 17.1 Successor thread for this ROM, where I have recently published a new ROM version containing the February 2021 ASB patches. I have also explained, how to migrate and that I have

stopped

providing the LineageOS 16.0 builds.

Based on the received feedback, I have also explained, how to extract microG updates from my 17.1 builds to apply them to the 16.0 builds for people, who do not want yet to migrate to 17.1, which of course is everybody's individual decision. Nevertheless, I recommend to migrate to 17.1.

I have updated the OP to indicate the EOL of this thread. I'll keep it still open for some time, as announced already.

Thanks for your interest and contributions to this thread, looking forward to seeing you in my LineageOS 17.1 thread.

Cheers, M.
[OnePlus 3 & 3T Cross Device Development] Stephen:
Moderator Information,

Thread closed as per OP's request
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Fixed build

Hi [MENTION=10538061]0xC0ncord[/MENTION] [MENTION=10552377]AjikanRB[/MENTION] ,

applying this kernel fix, which I found thanks to [MENTION=10552377]AjikanRB[/MENTION] 's hint, has fixed the crash for me.

Would you mind downloading and flashing this test build and report back to me, whether this solves your issues? (The only difference between the test buld and my build dated February 7th is the mentioned kernel fix)

Once you confirm it is fine, I'll make it available as OTA update for everyone.

Thanks in advance, M.
[OnePlus 3 & 3T Cross Device Development] 0xC0ncord:
Just tried it by dirty flashing on top of my device as-is, and I can confirm it has fixed it for me as well. VoIP calling works perfectly over both Linphone and the native SIP dialer. Thank you!
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Okay, new interim release available with the previously mentioned kernel patch:

Linked in OP (download link updated) and also being offered as OTA update.
[OnePlus 3 & 3T Cross Device Development] AjikanRB:
Hi [MENTION=7929484]MSe1969[/MENTION],

after installing the OTA update this morning, all VoIP issues seem fixed on my device as well. Every WebRTC-related app I throw at it (Riot, NextCloud-Talk, also Whatsapp) now works perfectly.

Thanks for the quick update, and for all the excellent work you've been doing so far :good::).
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with March ASB

Hi all,

a new build with March 2020 security patches is available for download:

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

It is already being offered for OTA update through the updater app and contains the following changes:

Security string 2020-03-05

Bromite System Webview 80.0.3987.118

AuroraStore 3.2.0

Added Netguard app (F-Droid) to SELinux domain allowing /proc/net

Regards, M.
[OnePlus 3 & 3T Cross Device Development] LaCereb:
That Rom sound interesting. Since RR is basically dead for my 3T im tempted to switch to this one.

Dear MSe1969, for how long can we expect you to keep this build alive and support it?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
If you look at my other threads (and also this one, which is the successor thread of my LineageOS 15.1 thread for the same device), you will be able to judge yourself - I usually maintain my devices quite long and normally close a thread by offering a successor thread and upgrade instructions.

The OP3T is my daily driver, so IMHO not too bad to consider... :)
[OnePlus 3 & 3T Cross Device Development] LaCereb:
I need something that lasts till the end of the year since my 3t is giving up *hardcore sad emotion*. I'm lurking with the new 8 Series of one plus. But I do love my 3T really much so I would like to keep at live with my hardest try ^^

But the rear camera gave up and the power button is a 50/50 change of signal detection from it.

Does your Rom have that double tap feature at lockscreen? And does it have the ability to double tap status bar to lock the screen?

I'm so out of LOS and it's feature. Used it way back when it still was CM :D
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Yes, those features are present. Up to you then to give it a try...
[OnePlus 3 & 3T Cross Device Development] :
For enhanced security you may want to consider: https://xdaforums.com/oneplus-3/how-to/guide-deblob-alipay-ifaa-tencent-soter-t4064893
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Many thanks for the hint! Saw also your comment in that thread. Will you do something individually for your builds?

EDIT: No on my PC now, but I think I will have a closer look at your repositories...
[OnePlus 3 & 3T Cross Device Development] :
I'm still in the process of considering. It's either removing the ifaa stuff from the build and providing a zip to clean out the fw (much less time consuming and "cleaner", but the ifaa stuff is gone and there is no user choice any more), or making the zip I've suggested (more generic and leaves it to the user to use ifaa stuff or not - but more time consuming). Currently I'm running the first version on my device, to check for unwanted side effects.
[OnePlus 3 & 3T Cross Device Development] :
Could you already share your zip?

I tried the same but ended with a rom which was much slower as mentioned in the link above. Probably the environment.rc issue (luisrom btw, so based on Lineage 17)
[OnePlus 3 & 3T Cross Device Development] :
To avoid hijacking this thread with convesartion on other roms: https://xdaforums.com/showpost.php?p=81991323&postcount=3
[OnePlus 3 & 3T Cross Device Development] :
After a night of sleep, these are my current thoughts: https://xdaforums.com/showpost.php?p=81995047&postcount=1494
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I definitely would like to apply this also in my build.

If I can help by testing something (preferably by applying it directly to my build), please let me know. I understand that the solution (assuming the straight approach to just remove and not caring whether somebody would still use this stuff) is to strip the firmware and to apply those two commits f. device and vendor.

Question:

I have seen your commits for the device and vendor repo and noticed, that some binary files were changed (not deleted), did you replace them? And can I simply pick that?
[OnePlus 3 & 3T Cross Device Development] :
Basically yes. The device commit strips ifaa manager and all ifaa, soter and alipay related stuff such as boot jar entries, compatibility and manifest entries, sepolicy objects and finally the list of proprietary files (used to generate a vendor repo).

This makes sure, that the next (clean) build is build without references to ifaa, soter, alipay stuff.

Editing the blobs file list has no effect at this point, but...

...instead of editing the makefiles and deleting the blobs from the vendor repo manually, I run the extract-files.sh script (I have a local git with all unpacked oos versions on my local disk). This way I can update the vendor repo to changes in proprietary-files.txt and ensure the changed proprietary-files.txt generates what I think it should generate... (yeah, I'm a bit paranoid...)

Some of the blobs need to be decompiled from the boot*.{vdex|oat} files with baksmali and recompiled for our use with smali. This always changes the date inside the resulting blob. I should have them reset in the repo, but in the end I'm too lazy... ;)

For testing you can just use the no-alipay branch of the vendor repo, apply the device commit and regenerate your own vendor repo, or apply the vendor repo patch (which will need some manual resolving based on themuppets).

Later today (or tomorrow or so) I'll supply a patched 9.0.6 fw with soter and alipay removed (quite some fws: op3 and op3t each with 9.0.6 bootloader and 5.0.8 bootloader... if oneplus decides to come up with 9.0.7 (very unlikely) I need to assamble 8 fw packages...).
[OnePlus 3 & 3T Cross Device Development] MSe1969:
That explains, thanks - just to be sure (I prefer to ask a maybe obvious question rather than messing up things):

I use right now the "original" Muppets. If I take your vendor commit as .patch file and remove all binary changes from that patch file, then apply it, afterwards manually delete the files shown as deleted in your commit and ignore the binary files shown as modified, I should be fine - correct?

(That's the point in time to fork those repositories obviously)

Looking forward to your new version of the fw, really grateful that you're doing this!
[OnePlus 3 & 3T Cross Device Development] :
Go to the directory of vendor/oneplus, then fetch my branch and cherry-pick the no-aliplay commit. Something like:

git fetch https://github.com/nvertigo/android_device_oneplus_oneplus3t no-alipay
git cherry-pick FETCH_HEAD
#this will throw some collisions, look at them:
git status
#resolve the conflicts, then finish the cherry-pick
git cherry-pick --continue

git supports binary patching; the patch command doesn't. Even though binaries are only deleted since there will be conflicts in the binaries, patching may result in unwanted rejects.

Available at https://github.com/nvertigo/firmware-3t/tree/master/archive sorted by op3 and op3t. Look fpr the filenames containing -no-alipay. Only available as 9.0.6.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION]; what will happen if we just use your modified firmware without further modifications in rom?
[OnePlus 3 & 3T Cross Device Development] :
Honestly I've no idea - maybe nothing.

I'll push a alipay/wechatpay-free nlos build later today.
[OnePlus 3 & 3T Cross Device Development] :
Unfortunately still based on Lineage 16, otherwise I would definitely would give it a try.

Will stop spamming the forum for today. Thanks for your input ;)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Interim build - debloated

Hi all,

based on the latest discussions, this thread and thanks to [MENTION=4405529]nvertigo67[/MENTION] - I have created a new interim build:

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

Debloated from Alipay, WeChatpay, Soter and IFAA

Brought vendor blobs up to OOS 9.0.6

I haven't yet pushed it into the OTA update process - if you simply flash it, it should work. However, I recommend to flash the debloated firmware before flashing the update.

See the OP of this thread, last section "Alipay, WeChatpay, Soter and IFAA".

Within the April ASB update, I will again push the next build into the OTA process, so enough time to update the firmware as well. As said, not absolutely necessary, but recommended.

Regards, M.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with April 2020 ASB

Hi all,

a new build is ready and will be soon offered via the OTA updater app:

Download here:

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

ASB Security string 2020-04-05

Fix for CVE-2020-8597 (external/ppp)

Kernel: CVE-2019-10638 siphash 128bit for IP generation *

Bromite Webview on 81.0.4044.76

AuroraStore updated to 3.2.4

_______________________________________

* Kernel is frequently updated every month, but I found this patch worth noting, as it has not been down-ported from the 4.4 and above kernels into 3.18

Please also note my comments in the previous post about the firmware. I recommend to upgrade the firmware.

Regards, M.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Is this for oneplus 3?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Yes, ROM is for Oneplus 3 and 3T - if you upgrade firmware, make sure to use the right version for the respective device.
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
Signed up just to say thanks for your efforts. Installed March a few days ago with locked bootloader. Just now updated to April.
[OnePlus 3 & 3T Cross Device Development] pawlik79:
How is the battery life on this ROM?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
It's my daily driver and I don't have reasons to complain (or, to be more precise, because I build it: No urgent needs to search for solutions to improve the battery behavior)
[OnePlus 3 & 3T Cross Device Development] $anket:
Does this rom support encryption?
[OnePlus 3 & 3T Cross Device Development] :
Yes, of course. It ships with all los-16 features plus what's mention in posting #1 and #3.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Yes, It does! No known limitations.

However - please be aware about the below two items, which are also referred to in the OP:

Use a current recovery (a current TWRP is recommended), so upgrade recovery, if applicable. This is recommended in general, not only because of encryption.

Read the linked thread about firmware upgrade from 5.x to 9.x on encrypted devices; carefully decide your next steps accordingly.
[OnePlus 3 & 3T Cross Device Development] $anket:
Thanks for the quick reply. Yeah I'll use latest recovery. I'm on stock rom 9.0.6 no root, locked BL, so I'll only have to flash that alipay 9.0.6 firmware before Installing the rom, right?

I mean this firmware: https://github.com/nvertigo/firmware-3t/blob/master/archive/op3t/oxygenos-9.0.6-no-alipay-firmware-3T.zip
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Short answer: Yes

Longer answer: I better let [MENTION=4405529]nvertigo67[/MENTION] step in as well. As far as I know, the debloated FW has the 5.x bootloader. So in your case you have the choice between original FW or debloated FW with BL downgrade, which however is no real issue
[OnePlus 3 & 3T Cross Device Development] :
Since he is already on oos 9.0.6 he is using the unmodified fw - the one he's suggested should be ok based on this information.
[OnePlus 3 & 3T Cross Device Development] kHAW17:
Hi,

since about a month my bluetooth headset isn't playing audio from almost any app except for the telephone app. In telephone app I can hear the other person and I can talk to them.

Can you give me a hint why this happens?

Many thanks in advance.

Greetings

Karsten
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi,

the fact that you can use your BT headset for phone calls indicates, that the pairing and BT connectivity as such works.

I don't have a BT headset, but I have no issue at all with playing songs using car BT and as far as I know, car BT also uses the profile of a "BT headset" (I may be wrong here).

I had however in my treble build for a different device a (not so) funny issue with AudioFX and a physical plugged in headset, which was solved by disabling AudioFX, when headset connected. Maybe that could be worth a look?

Regards, M.
[OnePlus 3 & 3T Cross Device Development] kHAW17:
No, that didn't help. And uninstall wasn't possible. Do you know anything else?

Regards

Karsten
[OnePlus 3 & 3T Cross Device Development] :
You can always delete it from twrp. Mount system, start the twrp terminal:

rm -r /system/priv-app/AudioFX

Don't forget to check the output of the above command (e.g. if you forget to mount system, there will be something like "no such file or directory").
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Not really - just to make sure: When you say "since about a month" this isn't directly related to e.g. "since the March update of my build", so it must be something you did (unknowingly) with your device like installing something, changing some settings somewhere, etc. - correct?

So you could e.g. try to isolate the problem by e.g. making a nandroid backup with TWRP and doing a factory reset and see, whether it works again...
[OnePlus 3 & 3T Cross Device Development] kHAW17:
Factory reset doesn't work somehow... I can't see anything resetted.

Additionally I flashed the noAlipay zip. It suddenly reboots and nothing is set back. I mean resetted. Sure this is not normal, is it?

Regards

K
[OnePlus 3 & 3T Cross Device Development] :
Boot twrp, factory reset and without reboot reflash the no-alipay fw. Now (without reboot) get the recovery log (MainPage->Advanced->Copy log - no need for kernel log).
[OnePlus 3 & 3T Cross Device Development] kHAW17:
OK,you might call me blid, but I didn't find an option to factory reset in twrp. Maybe I need little training. ...

I already did a nandroid backup that said something wasn't backed up. So I tried to back up as much as possible from my most important data until I was unlusty.

Can you please tell me, if the work was useless and where the option to factory reset is in twrp?

Regards

Karsten
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi,

1. Factory reset in TWRP: Button "Wipe" and the bottom shows "Swipe to Factory Reset" - that's what you do.

(Löschen - Werkseinstellungen herstellen)

2. A meaningful backup is to choose Boot, Data, System, nothing else

3. A factory reset does not purge your "Internal Memory" (at least not in TWRP, Stock ROM is a different story)

The backup therefore also does not take the contents of your Internal Memory, whivh is ok.

Regards, M.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7929484]MSe1969[/MENTION]:

Wow, you are jaw-dropping tough, my friend - I'm still too appalled to answer that question.
[OnePlus 3 & 3T Cross Device Development] kHAW17:
OK, I die all that stuff, imediately installed New pipe to see if my headset works and it works. What would be the next step?

---------- Post added at 10:04 AM ---------- Previous post was at 10:04 AM ----------

OK, I die all that stuff, imediately installed New pipe to see if my headset works and it works.

Then I installed Your Rom and it still works.

What would be the next step?

Regards

K
[OnePlus 3 & 3T Cross Device Development] MSe1969:
OK, that means it is not directly related to the ROM or your Hardware (what I thought already).

You have now three options on how to proceed:

1. You can live with a fresh install and manually get your stuff back one by one. Then just go that path. In fact that is what I recommend.

2. You restore your nandroid backup, which brings back the previous situation. You could now try to delete the data of certain apps (e.g. Bluetooth) and see, whether it fixes the issue - that will be most probably frustrating, I tell you.

3. After restore, you can partially backup stuff (e.g. your contacts, if they aren't synch'ed already) or you use an app like Titanium backup for that, so you backup the stuff you don't want to lose (but be very strict, there isn't really a lot besides contacts or calendar entries, as most apps store the user-specific data on Internal memory, which is still there), do a factory reset again, manually install all the apps you need, and finally restore your "partial" backups.
[OnePlus 3 & 3T Cross Device Development] kHAW17:
I decided for option one. Now everything works. But it's hard to remind all settings I made and all apps I installed. You mentioned an app, to backup things, it's no free software, is it? You have to pay for it I guess, correct?

Regards

K