yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] nadastry:
May I ask 2 questions about this ROM?

1)

Call Recording was removed by Google and Call Recording apps like Cube ACR warn that only partial recording is working, means only one side could be recorded because only the external microphone could be accessed. Has this changed? Is proper and good call recording possible of both sides on this ROM?

2)

Does Snoopsnitch work? The App needs the Qualcomm DIAG driver to do network tests and recognize IMSI catchers or silent sms.
[OnePlus 3 & 3T Cross Device Development] :
You can check yourself:

---EDIT--- (Fixed the link)

https://github.com/lin17-microG/and...ch/arm64/configs/lineageos_oneplus3_defconfig

No CONFIG_DIAG_CHAR.

---END OF EDIT---

But even with that driver it's still not working because of unfixed error in the apps initializing code. You need to use the (slightly) outdated and not updated patched app from here: https://xdaforums.com/t/app-patch-snoopsnitch-oneplus-compatibility-patch.4154491/

Or you need to build the app with patch yourself from the git mentioned in the that thread.

Callrecording works for regions, where allowed:

android_packages_apps_Dialer/java/com/android/dialer/callrecord/res/xml/call_record_states.xml at lineage-17.1 · LineageOS/android_packages_apps_Dialer

Contribute to LineageOS/android_packages_apps_Dialer development by creating an account on GitHub.

github.com
[OnePlus 3 & 3T Cross Device Development] ledpepper:
Not sure if this was mentioned or not so I thought I'd share: (Oct 2020)

Google adds WireGuard VPN to Android 12’s Linux Kernel

Update 1 (10/26/2020 @ 06:11 PM ET):

I'm neutral on the matter but for anyone else: yay for more info!
[OnePlus 3 & 3T Cross Device Development] :
@ledpepper:

When can we test your custom kernel with 4.9 or - better - 5.4 port for op3/t? ;) (SCNR)
[OnePlus 3 & 3T Cross Device Development] ledpepper:
haha. Sure, as soon as the money-fairy visits and showers me with cash and Pixels
[OnePlus 3 & 3T Cross Device Development] MSe1969:
My final comment to the Wireguard topic, I will afterwards not react anymore to any "arguments", why I should add it:

Let's ignore for now, that we have a 3.18 kernel for the OP3(T), which normally is already the 100% explanation, why this info is irrelevant for the OP3(T) device.

Let's look at below

Quote

:

though it remains to be seen whether or not Google will add APIs to interface with the kernel module in time for the stable release of Android 12

As long as there is no API available to properly trigger the WG VPN service, root is needed to use native WG support in the kernel!

And I have explained my stance already in a previous post.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
@MSe1969 Seems like the Aurora store version bundled with your rom doesn't manage to create the Google API anymore.

There was a recent update on f-droid that can't be installed due to signature mismatch.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
In my next build, the current version (right now 4.0.2) will be bundled together with the most current version of AuroraServices and will thus upgrade the current version.

As a work around until then, you can install the latest nightly build of AuroraStore (has a different package name) next to AuroraStore 3.2.9
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
Funny thing. I took the latest build from AuroraOSS Telegram channel and installed it. It completely replaced your version.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
You're right - I bundle the pre-signed AuroraStore from here - and that is the same signature, so it works. F-Droid signs with their own signature, that is why.

Make sure to also update AuroraServices, or you will have to enable unknown sources.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build available with April Security patches

Hi all,

a new build is available for download and already offered via Updater app:

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

ASB Security string 2021-04-01

Kernel upstreamed to tag ASB-2021-04-05_3.18

Bromite System Webview and Browser updated to 90.0.4430.59

F-Droid updated to 1.12

Update: AuroraStore 4.0.4 with AuroraServices 1.1.0

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
Moving to a Pixel 3a. Juste wanted to thank you for your work on our beloved OP3.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build available with May Security patches

Hi all,

a new build is available for download and already offered via Updater app:

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

ASB Security string 2021-05-01

Kernel upstreamed to tag ASB-2021-05-05_3.18

Bromite System Webview and Browser updated to 90.0.4430.204

microG upstreamed (no version change)

Update: AuroraServices 1.1.1

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] mister_monster:
Hello, I've been using this ROM as a daily for 9 days as a daily driver, and it has a couple of issues that I have noticed.

Kernel Version: 3.18.140-g2c5b28d06424 #1 Sun May 9 12:54:41 CEST 2021

Build Date: 2021-05-09

oxygenos-9.0.6-no-alipay-firmware-3T.zip from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3t as per instructions.

The link in your post to the logs you want is a dead link apparently.

First issue, the network speed indicator shows extremely inflated values for down speed randomly, it is more common on mobile data, I think it occurs most frequently when switching from WiFi to mobile data. I have a very limited and unreliable bandwidth connection, that could be triggering it, but it is definitely a bug in this ROM.

Second, I cannot change the charging disconnect sound to "none" (so as to leave vibration on but have no sound).

Third issue, and this is a big one, while charging sometimes for some reason the system glitches out for a while and crashes, and then the phone is frozen with a black screen and must be rebooted. This has happened to me while charging 4 out of the 8 nights I have left it charging while asleep. Once I was charging it while using it and it started acting really weird, and I unplugged it and it stopped acting up. Something fatal is happening while charging. This issue makes the device unreliable as an alarm clock, a core use of a phone.

Fourth, another big deal, attempting encryption just soft reboots the system.

Finally, this isn't an issue, but are there any plans to add wireguard support in kernel? This is a great security focused ROM and it just seems like something that fits right in with the goal of it.

Thanks for maintaining this ROM, and if I notice any more issues later I'll report them to you, and if you release an update to the last build to resolve issues I will use it and let you know.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for reporting, but I've just tested the link in my OP and it works.

I am not sure, what exactly you mean - which "network speed indicator" are you talking about? You mean the signal strength indicator?

In general, I use most of the LineageOS sources and device config, only with minor adjustments. This statement is valid for all aspects/issues, you mention. I have e.g. not altered any device configuration or functionality in regards to charging or sound settings.

I'll look closer tomorrow, however - assuming this is same behavior like official LineageOS f. OP3T, I can't do anything about it.

EDIT: There is an explicit Option to disable/enable the charging sound (Settings - Sound) and that works fine on my device, so no issue for me.

I can't see that behavior on my own device - anybody else having that issue?

My OP3T is regularly encrypted w/o issues. When I find the time, I'll make a backup, format the /data partition and encrypt again to see, whether there is an issue. Same as previous section - can anybody else feedback on this?

WG support isn't built-in on purpose - please scroll back, there has already been a discussion about this topic in this thread.

See here and the following posts.

So far, as indicated, I don't really see any issue. Anyway, some logs would be helpful! Of course, if it turns out that there is an issue and I am able to fix it, I will of course publish an update. I'll do some further testing and feedback here. Nevertheless, appreciate the feedback.
[OnePlus 3 & 3T Cross Device Development] mister_monster:
Regarding the charging sound, if you turn off charging sound as you say, you get no sound, but then you have no option to enable vibration. If you turn the sound on so as to enable vibration, but then you select "none" from the drop down of sounds to select, it still plays the default sound regardless. There is no way to have only vibration and no sound.

As far as the network speed indicator, it's actually called "Network Traffic Monitor" in status bar settings, and frequently shows inflated down speed in Mbps that I am not getting, particularly on mobile data and when switching from WiFi to mobile data.

I'm curious of the data encryption problem is the result of magisk being on my device. You say you don't use it, and that might be the difference, as I had this same problem with my previous ROM, NLOS 15.1.

I'll try to get you some logs.
[OnePlus 3 & 3T Cross Device Development] :
Sounds like you've formated data with a broken twrp (don't remember the exact broken twrp version, but it has been published in nlos-15.1 times), which doesn't reserve space for the encryption footer. This has been widely discussed. I.e.: https://xdaforums.com/t/eol-rom-sdc...mode-nlos-15-1-20190208.3754855/post-78326684 , but it's also in the twrp thread as well as in other rom's threads.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
The charging sound can be enabled or disabled - independently from other sound settings - and it seems you would like to make the phone vibrate only, if the cable is connected or disconnected. This seems to me a not foreseen feature in LineageOS or Android; for sure, nothing which I am going to tamper with (and also in my eyes not really a "deal-breaker").

OK, now I got it (wasn't even aware about that feature). Well also here, not a feature, which I have modified. This feature behaves same also in official LineageOS, I guess. Since it seems to update in "intervals", I am not sure, how accurate this really is - you describe it as inaccurate, which could very well be the case. But also here, I don't see, how I could improve this, so I simply won't!

In regards to encryption, the answer given to you by @nvertigo67 really seems to be the explanation.

Please update your TWRP, if not yet done, make a full backup via TWRP, don't forget to save the internal memory separately, and - most important - make sure to copy your backup files afterwards to your PC. Format the /data partition afterwards and then do the encryption. To save time, I recommend to first boot into your empty OS, do the encryption and afterwards, if all OK, restore copy back your backup files and the Internal memory contents to your phone and do a restore .
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build available with June Security patches

Hi all,

a new build is available for download and will later today be offered via Updater app:

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

ASB Security string 2021-06-05

Kernel upstreamed to tag ASB-2021-06-05_3.18

Kernel WLAN driver (qcacld-2.0) patched to include mitigations against "Frag" vuln.

Bromite System Webview and Browser updated to 91.0.4472.102

microG 0.2.19211515-9

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] Cashmeousside:
Amazing work!

This ROM has finally convinced me to ditch root.

I was wondering if it would be possible to allow certain apps that depend on Facebook (read:WhatsApp) like how you can change whitelist specific google dependant apps.

Many thanks!
[OnePlus 3 & 3T Cross Device Development] Cashmeousside:
That was well explained.

So as I understand it, if you've let one fb botnet app through, you've essentially let them all through.

Unfortunately I cannot let go of WhatsApp since I have work related stuff on it.

Sorry for trying to cause feature creeps, but is a separate toggle for google and Facebook blocking possible so I can try to block as much as possible.

Again, many thanks
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Maybe you should consider one of the two below options:

- Use of the app "Shelter" (F-Droid), in which you "jail" the spyware (see doc. it in fact uses a work profile for that)

- If it is not necessary to be "always online" in WA and receive notifications, but it would suffice, if you e.g. check for news twice a day or every now and then, you could create a secondary user and install WA only there. You would switch to that user, check WA and switch back to your main user. The secondary user of course would only have a very small phone book, disabled location and, as you will see, no access to ANY of the primary user's data, even Internal memory...
[OnePlus 3 & 3T Cross Device Development] eightfiveseven:
I used WA with previous version of this ROM (LOS 16) and it worked all the way except when someone sent a picture or video. They wouldnt load until I disabled iptables blocking script. After loading the picture/video I enabled blocking script.

I also didnt allow any permissions to WA and I used "Open in Whatsapp" app from Fdroid to add new numbers to WA. Its a little bit struggle to find which number is which of my friends but it never bothered me. (profile picture)

I have moved to Pixel 4a and CalyxOS and I dont have WA app in my new phone. Though I still have my 1+3T and I am planning to update old LOS 16 to 17 and have it as backup phone.

Btw thanks M for this excellent ROM and your effort to it!

EDIT

Oh I forgot I also had whatsapp related hosts blocked by AdAway:

g.whatsapp.net , mmg.whatsapp.net , pps.whatsapp.net , privatestats.whatsapp.net , static.whatsapp.net
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build available with July Security patches

Hi all,

a new build is available for download and already offered via Updater app:

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

ASB Security string 2021-07-05

Kernel upstreamed to tag ASB-2021-07-05_3.18

Bromite System Webview and Browser updated to 91.0.4472.146

microG 0.2.21.212158-2

AuroraStore 4.0.7

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] mike_lo:
Does anybody know how to install EdXposed in this firmware? I tried a lot of versions Riru, Riru-Edxposed and Edxposed Manager. Every time manager says - EdXposed Framework not installed. I tried original versions of LineageOS and LineageOS+microG, and there EdXposed works fine. But I want this firmware. Is it real install EdXposed, or it will never work becouse of sign spoof in this firmware?!
[OnePlus 3 & 3T Cross Device Development] :
Exposing compile time framework defaults to userspace on a hardened, security enhancing rom is like securing your home with the latest locks and alarm devices and putting your money in a shoebox in the frontgarden. If that is, wjat you want, you need to use a non-hardened base, as plain los.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build available with August Security patches

Hi all,

a new build is available for download and already offered via Updater app:

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

ASB Security string 2021-08-05

Kernel upstreamed to tag ASB-2021-08-05_3.18

Bromite System Webview and Browser updated to 92.0.4515.134

F-Droid updated to 1.13

Fix in WiFi randomization

Happy flashing!

Regards, M.
[OnePlus 3 & 3T Cross Device Development] mike_lo:
Answer me wider please. So is it possible to consider that Xposed is a hole in security? And because of this, author disabled opportunity to install Xposed in this firmware?
[OnePlus 3 & 3T Cross Device Development] :
Exposing framework's settings and private data and methods to userspece is a security hazard. And yes "If that is, what you want, you need to use a non-hardened base, as plain los." means it's not possible on this rom - but it's not firmware (prebuild closed source basic blobs like radio, bootloader etc.) related.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
@nvertigo67 has already perfectly explained this, also in his recent response.

Just to add to this:

I did not actively disable stuff by means of "yeah, let's block feature 'xyz' " (unless I have put an option in the Settings leaving the user a choice), but I knowingly decided to include many hardening features from the GrapheneOS project into my ROM; which puts a significantly stricter limitation in place in regards of what the OS core components are allowed versus non-core components and 3rd party stuff ("user space"). The aim is to reduce the attack surface of especially yet unknown potential attacks.

The fact that Xposed, Gapps and other stuff cannot be flashed and/or do not work properly because of that is neither surprising, nor unwanted.
[OnePlus 3 & 3T Cross Device Development] :
*lol* Bro, you made my day. That's humble. I'd call these effects "proof of concept" or "proof of hardening in place" - "neither surprising, nor unwanted" is an awesome phrase in this context! Still laughing... :) :) :)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
LineageOS 18.1

Hi all,

a LineageOS 18.1 test build is available here:

https://sourceforge.net/projects/lin18-microg/files/oneplus3/lineage-18.1-20210818-UNOFFICIAL-microG-signed-oneplus3.zip/download

It has the same features, as described in the OP for this 17.1 build, with the following additions:

- AuroraDroid app replaces F-Droid app to access F-Droid repositories

- Option to only use fingerprint unlock for apps and not for the device

- Optional timeout for Bluetooth and WLAN connections

- Some more hardening features ported from GrapheneOS

- Kernel is based on the upstreamed kernel of this build (with many necessary adaptations for 18.1, of course)

- Sec. string 2021-08-05

Right now, this is still a

test build

, this means:

I truly appreciate any feedback (especially, if things don't work as expected). And there definitely will be an update for 17.1 with ASB patches for September. It is possible to "dirty-flash" over this 17.1 build, but make a backup in TWRP before, to be able to get back.

Feedback appreciated - Thanks & regards, M.

EDIT:

Kernel source: https://github.com/lin18-microG/android_kernel_oneplus_msm8996/tree/lin-18.1-mse2

Build Manifest: https://github.com/lin18-microG/local_manifests/tree/lin-18.1-hmalloc

EDIT2 (2021-08-22):

Seems the kernel needs more rework: on my device, it always crashes after a while. If you use the "original" LineageOS kernel (e.g. extract and flash boot.IMG from an official LineageOS ROM Zip), it will work.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
LineageOS 18.1 - 2nd Test build

I have chosen a different approach for now with the kernel and created a 2nd test build here, which seems to run well:

https://sourceforge.net/projects/lin18-microg/files/oneplus3/lineage-18.1-20210830-UNOFFICIAL-microG-signed-oneplus3.zip/download

Kernel source: https://github.com/lin18-microG/android_kernel_oneplus_msm8996/tree/lin-18.1-mse3

Build Manifest: https://github.com/lin18-microG/local_manifests/tree/lin-18.1-hmalloc

Please test and provide feedback!

Assuming this build runs smoothly and stable, I plan to provide a last time a 17.1 build with September ASB and afterwards LineageOS 18.1 builds.

Regarding Kernel:

I haven't yet abandoned the idea of a fully upstreamed kernel, which I used to provide so far for my 16.0 and 17.1 builds.

However, right now I am struggling to find the root cause of the kernel panics in my upstreamed kernel (branch 'lin-18.1-mse2').

Main reason is, that pstore doesn't work either right now, which makes it impossible to get proper logs. Any help appreciated!

For the time being, the working kernel used is the official Lineage 18.1 kernel with the missing official ASB patching plus further patches - taken from the updater script of Divest-OS (and a lot of manual work to get the proper commit history).
[OnePlus 3 & 3T Cross Device Development] Cashmeousside:
Hey!

I've been using this test build mk2 for nearly a day. And its very good. Kudos!

The issue that I've come across is that using the touchscreen gestures on screen off causes the device to reboot.

I apologise for no logs as my phone can only charge through the USB port (hardware issue)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for the feedback, I can confirm your observation:

09-01 22:32:40.306 2784 3296 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 3296 (InputReader), pid 2784 (system_server)
09-01 22:32:40.492 2784 3297 I HidlSensorManager: hidl_ssvc_poll: spurious wake up, back to work
09-01 22:32:40.495 7016 7016 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-01 22:32:40.496 2229 2229 I tombstoned: received crash request for pid 3296
09-01 22:32:40.501 7016 7016 I crash_dump64: performing dump of process 2784 (target tid = 3296)
09-01 22:32:40.564 7016 7016 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-01 22:32:40.565 7016 7016 F DEBUG : LineageOS Version: '18.1-20210830-UNOFFICIAL-microG-signed-oneplus3'
09-01 22:32:40.565 7016 7016 F DEBUG : Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:8.0.0/OPR1.170623.032/02281230:user/release-keys'
09-01 22:32:40.565 7016 7016 F DEBUG : Revision: '0'
09-01 22:32:40.565 7016 7016 F DEBUG : ABI: 'arm64'
09-01 22:32:40.566 7016 7016 F DEBUG : Timestamp: 2021-09-01 22:32:40+0200
09-01 22:32:40.566 7016 7016 F DEBUG : pid: 2784, tid: 3296, name: InputReader >>> system_server <<<
09-01 22:32:40.566 7016 7016 F DEBUG : uid: 1000
09-01 22:32:40.566 7016 7016 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
09-01 22:32:40.566 7016 7016 F DEBUG : Abort message: 'Inlined method resolution crossed dex file boundary: from android.view.KeyEvent org.lineageos.lineageparts.gestures.KeyHandler.handleKeyEvent(android.view.KeyEvent) in /system/priv-app/LineageParts/LineageParts.apk/0x31659ec220 to int lineageos.providers.LineageSettings$System.getInt(android.content.ContentResolver, java.lang.String, int) in /system/framework/org.lineageos.platform.jar/0x3165918b60. This must be due to duplicate classes or playing wrongly with class loaders. The runtime is in an unsafe state.'

Have already an idea how to avoid this...
[OnePlus 3 & 3T Cross Device Development] MSe1969:
LineageOS 18.1 - 3rd Test build

Fixed the Keyhandler crash from previous post (this is the commit for those interested):

https://sourceforge.net/projects/lin18-microg/files/oneplus3/lineage-18.1-20210901-UNOFFICIAL-microG-signed-oneplus3.zip/download
[OnePlus 3 & 3T Cross Device Development] NWD:
I tried Divest-OS earlier today, since it stated I might be able to lock the bootloader, it worked, but still gave a message about a dodgy ROM when it booted...

I tried flashing your ROM using the same method (thanks to this tip

https://www.reddit.com/r/OnePlus3T/comments/hubb7r
) it seems to be working fine...

Locked BootLoader (no messages during reboots)

Encrypted with Boot Password and LockScreen Password

Thanks for the hard work you put in to keep this hardware working :)