yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Not at the moment. Takes time to analyze and port the hardening features, and I don't really see any "killer feature" of Android 10, which would drive an urgency to switch to LineageOS 17.1.

In the contrary I even see lost features like e.g. the privacy guard or root add-on, the latter factually forcing me to make sure to be always compatible with Magisk.
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
It seems that privilege for 'com.android.vending' is already whitelisted in /etc/permissions. Still getting the wrong signature error while installing the app, nor can I grant the permission (same error as before).

Could you please describe how it's meant to be installed?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
As you put your app into /system/priv-app, which has the package name com.android.vending, you need to also remove the FakeStore apk, which also uses that package name
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
Heads up. Due to a change in FCM (since v20.1.1), new / updated apps won't register with push notifications anymore on MicroG. Signal and Slack for example.

The good news is that there is a pull request waiting to be merged. However, the current development on MicroG can be described as flaky at best (last commit has been a half year ago), so I don't have a lot of hope that it will be merged soon. There is a fork which has merged the PR.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for the hint, appreciated.

I have meanwhile forked the prebuiltapk repo and updated, next to F-Droid and F-Droid privileged extension, also the prebuilt microG GmsCore including this fix. I have used the prebuilt apk from the /e/ project for now. Test looks good so far. Will be part of my next build.
[OnePlus 3 & 3T Cross Device Development] :
Thanx for merging the rest of the nlos commits to your kernel branch. I tried to use it directly without any additional commits. Sadly this branch doesn't boot anymore. It freezes very early while booting the kernel.

I've attached pstore. I'm not 100% sure, but I guess zram is broken (I'm using zram in my builds: https://xdaforums.com/oneplus-3/one...1-20180223-t3754855/post78334059#post78334059 ).

EDIT: my fault: I forgot to merge the bootfix for gcc7... Thanx anyway.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi all,

a new build is available for download and will soon be also offered via OTA update:

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

ASB Security string 2020-07-05

Kernel: Wireguard tag v1.0.20200623 (of course, as every month, kernel is upstreamed from here)

microG: updated prebuilt GmsCore fom /e/ project (fixed FCM registration issues and delay with Signal app)

F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11

Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

Happy flashing, regards M.

P.S.: Meanwhile, there is TWRP 3.4.0 available for our device, I recommend to update it as well (not a requirement, but recommended)
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
For some reason, I get no notifications of SMS messages since using this ROM. I have to open the messages app manually to get them. Is this a known problem?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
No, not really - I use Signal messenger and have set it as SMS app. Signal messages and also regular SMS arrive and are notified in time.

EDIT: I assume you have checked already notification blocking or, if you use a messenger app and not the AOSP SMS app, whether background optimization is enabled etc.?
[OnePlus 3 & 3T Cross Device Development] strangefinder:
moin,

does gcam

https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552

work?

if so which version do u use?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
No idea, I don't use it.

This ROM comes without the genuine Google spy services, and apps from Google usually deeply integrate with them simply for the sake of doing so. So I'd suggest you make a nandroid backup first in TWRP (to be able to restore the previous state in case of major problems) and then you give it a try yourself to find out.

If you would like to report your experience here, you are of course welcome to do so, as this might be interesting for others reading this thread.
[OnePlus 3 & 3T Cross Device Development] $anket:
It's working. I'm using Arnova8G2: GCam_5.200604.2138build-7.3.021 (latest v7.3). And it doesn't require any google services, just download & install apk.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Make sure you don't have Do Not Disturb mode on. By default it suppresses notifications.

Thanks for the new build. Works ok after few days, yet again Aurora Services are giving some pain, Aurora Store only works in root mode now. Otherwise all good.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I normally force close Aurora, if it troubles. Afterwards it normally works again.
[OnePlus 3 & 3T Cross Device Development] J0n4t4n:
Google Device Registration automatically enabled

Hi, I have been using this rom for a couple of months now and I am overall very happy with it.

But with the last update something weird happened, which I am not totally happy with and wanted to give a heads up about: I started receiving push notifications from apps that I wasn't used to getting them from. I checked the MicroG settings and all of the sudden "Google device registration", "Google Cloud Messaging" and "Google SafetyNet" were enabled. I intentionally left them off and they had always been disabled until the last update magically turned them on. Does anyone have an idea why this happened?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
The most recent build contains the prebuilt GmsCore from the /e/ project, as announced before. This was necessary to fix some issues with push messages, because the original microG project does not yet have merged some pull requests dealing with that.

It seems that this version has the stuff enabled by default. I did not notice it during my testing, as I have the GCM stuff enabled.
[OnePlus 3 & 3T Cross Device Development] J0n4t4n:
Ah I see, that makes sense. I thought it was a deliberate decision. Do you happen to know if I'll now have to disable it every update or if microG can save the preferences persistently?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I think from now on it should be fine. (I'll have a look this time and will give a heads-up otherwise)

In fact what I think what happened is that due to replacing that APK (remember: the true signature differs from the previous, but both spoof G* for the other apps - the previous had the original Sig from microG and the one from /e/ was unsigned and got signed with my Build's platform key), the package manager during boot-up has cleaned the app space and thus, the default settings had applied.

So only if I replace that APK again with another prebuilt carrying an own signature and not e.g. only with an updated APK from the /e/ , this might happen again. Maybe then the other way round...
[OnePlus 3 & 3T Cross Device Development] :
Hi.

So I finally flashed a ROM to my OP3T and I was frustrate by the heat and touchlag but it was the kernal choice for battery that caused the problem. I wonder now if I can lock the bootloader and if Im able to install Magisk? Android Pay and Netflix isnt a issue for me. Also can we have a red accent colour, really missing that option.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Hi again,

I'm trying to investigate a bug with a local taxi app which started crashing when invoking com.google.android.gms.maps.model.Polygon.getTag(). I used it two weeks ago on older build and it worked, so now I want to roll back and see if it's really this unmerged patch branch of microG that is causing that.

So my question is: would dirty flashing previous build be ok?

Thanks.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Dirty flashing older build should be OK.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Regarding color accent, I only ship, what comes with LineageOS 16.0 .

Installing Magisk shouldn't be an issue, locking the BL is also possible (install Magisk first!).

However - appreciate feedback from others here as well.
[OnePlus 3 & 3T Cross Device Development] :
A locked bl requires on op3/t an aosp verity key signed boot and recovery partition (other devices may differ). This hardened los rom ships with a signed boot image. Magisk (from 20.3 on) resignes the boot partition after altering if it has been sigend previously. This means: installing magisk on this rom's shipped boot image wil give no problem with a locked bl. If you use a custom kernel (no good idea for many reasons; e.g. sec patch level) which doesn't sign the boot partition, magisk will not resign the now unsigned boot partition.

Order shouldn't matter, because you will be able to update magisk with bl locked.

Official twrp is distributed with a signed recovery partition since 3.3.x-x (at least, don't remember for 3.2.x-x).

Sidenote: I see no advantage in locking bl with this rom, since the tripped verity bit (triggered by an unlocked bl) is droped by this kernel anyway. This may change (or hopefully not change due to kernel level) if safetynet api switches to hardware backed check.

Some more info (reference for reading - not for blindly and unkonwingly flashing!):

https://xdaforums.com/showpost.php?p=78433989&postcount=4

https://xdaforums.com/showpost.php?p=78433987&postcount=3

https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk/
[OnePlus 3 & 3T Cross Device Development] :
Thank you but also...

Because you are so knowledgable, how do I fix the overheating?
[OnePlus 3 & 3T Cross Device Development] :
Why do you quote my complete posting without refering to a signle word of the quoted information?

You need to debug "the overheating", find the cause and remove the cause.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7929484]MSe1969[/MENTION]:

if you want to try a more curtent backport of f2fs in the kernel (including the currently hyped gc fixes) see https://xdaforums.com/showpost.php?p=83132389&postcount=1678 . I think it's better portable for future releases then the merged version of https://github.com/jaegeuk/f2fs-stable. YMMV just to keep you informed.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks, seen the posts in your thread - I'm not at home right now till end of next week, will have a closer look then, and for sure be very grateful to merge/pick, when the feedback in your thread indicates accordingly.

EDIT: And my own (regression) testing, of course.
[OnePlus 3 & 3T Cross Device Development] :
Let's wait and see, we are not in a hurry. I know the cherry-picking is not idle (e.g. for futute updazes of the f2fs backports), but considering you upstream work (which is IMHO more important then the f2fs commits) it's hamdy to have one set of commits fpr cherry-picking. But that's just my thoughts, maybe you find some other procedure more usefull.

Have a good time aboard.
[OnePlus 3 & 3T Cross Device Development] soozie_:
TTS Engine

Hello, I have been using this ROM for somwtimes now without gapps. All is working very fine, the only issue is that I'm not able to find a suitable Text to Speech Engine. What tts engine is everybody using and any recommendations would be great.

Thanks
[OnePlus 3 & 3T Cross Device Development] MSe1969:
That's a good point - I ended up with the below compromise:

Step 1: Download Google TTS via Aurora

Step 2: Within the G* TTS app: Download the needed language files (there is such an option called "install language") to avoid the need of online connectivity

Step 3: In the App settings, Data usage, disallow all kinds of connection (WiFi, mobile data, VPN) for it

Works fine for me, don't like the idea of using a Google app, but as it can't connect to any Google server and still works offline, I can live with it.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Basically what MSe1969 said. I use an old S5 Plus (gapps free) as a remote/music player and I was looking for a Foss TTS engine but also ended up with the same setup as described above.

Sadly there isn't any usable Foss alternative
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
I'm using Flite TTS Engine on fdroid with this ROM.
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
So it seems the development of MicroG has been resumed since early june. Looking into the changelog shows some juicy commits. Let's hope this trend continues!

https://github.com/microg/android_packages_apps_GmsCore
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Hi again,

last time I was trying to investigate local taxi app crashing while trying to render a map. I tried different versions of ROM and different versions of app and it's still crashing. Not sure why it started to crash recently, but switching ROM versions didn't help, so I decided to let it be.

Second problem I have is Aurora Services installations don't work after one of the updates, they just hang forever. I checked the logs and here's what I got:

08-06 10:45:02.162 I/Aurora Store(8779): Aurora Service is installed & available
08-06 10:45:02.166 I/Aurora Service(9206): Checking if package is allowed to access Aurora Services: com.aurora.store
08-06 10:45:02.173 E/Aurora Service(9206): Package is NOT allowed to access Aurora Services

Looking at Aurora Services screenshots on their gitlab/github I see that you need to whitelist Aurora Store in their GUI. However I cannot get to their GUI. I tried invoking the activity listed in Manifest file, but apparently the app removes this activity after first launch(?). So I tried to clear the data for the app, remove it from /system/priv-app and remove the permission whitelist file from /system/etc/permissions/ (it's unrelated as it just gives Aurora Services permissions to install apps, but I was just trying to go clean) and then dirty flash over it, but app still hasn't appeared in the launcher, nor I am able to launch the activity from adb shell.

Any suggestions on either:

1) how to fix the issue?

2) how to remove all of the traces of Aurora Services, so I can go fresh and get access to their GUI?

Thank you.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Normally, AuroraServices has got an own icon to launch. But if you have chosen before in an older version to remove the app icon, it will be tricky. In previous versions, it helped to clear the app data of both apps. Maybe a question to be asked in the Aurora thread?

Important, did you, after removing the services app, reboot the system to let the package manager really clean up? Or did you directly dirty flash after removing the app dir?

What you could also try is purging the Aurora app folder in the Internal Storage, and if that doesn't help, remove both apps and dirty flash after one reboot...
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Thank you, rebooting helped. I assumed since I was removing it on booted system(not from recovery), package manager would already do the job. Removing both apps and dirty flashing after one reboot helped.
[OnePlus 3 & 3T Cross Device Development] geekwithlens:
Hey dev. Thanks for this nice rom. If I lock the bootloader post flashing your rom will I get the benefit of DM-Verity? or that part has been removed by you? Please let me know. Thanks!
[OnePlus 3 & 3T Cross Device Development] :
What benefit do you talk about exactly? I've explained the context of locked bl on the last page - what do you expect?
[OnePlus 3 & 3T Cross Device Development] geekwithlens:
Thanks for replying to me. I saw your post. I am sorry but I didn't understood the part about dm-verity. Is dm-verity disabled in the kernel or just the warning message?

I understand the benefit of locked bootloader is as follow:-

1) Malware cannot gain persistence in system partition.

2) Android Verified Boot will ensure that it only boot with the signed rom.

3) No one will be able to flash anything malicious in my rom via recovery if they get access to it.

My question is simple. If I relock the bootloader with this custom rom - do I get all the same benefits as above? I understand DM-Verity plays an important part in it.
[OnePlus 3 & 3T Cross Device Development] :
This is a hoax spreaded by quite some people for op3/t. I don't know if this is true for other devices but it's not true for op3/t.

Please read my posting from the last page (I don't like explainimg the very same on each page): on op3/t a locked bootloader requires a signed recovery partition amd a signed boot partition. The system partition doesn't need to be signed and can be altered without tripping anything and without failing boot.

Since system is mounted ro a malware needs to gain root previlegs to remount system rw.

Again: read my posting on the previous page: on op3/t a locked bootloader requires a signed recovery partition amd a signed boot partition.

"A signed rom" is really ambigous and doesn't mean anything as long as you don't say what signature you are talking of. See: https://xdaforums.com/showpost.php?p=82568467&postcount=1183

If one has access to your device and therefor to your twrp recovery, everything can be flashed - no matter of bl state.

That's why it's so important to use encryption and secured boot passphrase on data to keep your personal data safe if anybody gets physical access to your device.

As you can see, if you read this posting, my posting from the last page and the referenced posting, this isn't a simple question, if so much misconcepts are part of it.

A locked bootloader just ensures the system partition and the recovery partition are signed with the aosp verity key - not more not less. The benefits you mention are hoax or result of misconcepts.

Even though the answer may be not as easy as you've expected, if you follow all references and the links given in those references it shpuld answer your question.

EDIT:

Just realised this posting is on a new page. "my posting on the previous page" refers to https://xdaforums.com/showpost.php?p=83092591&postcount=134 , of course.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Well your points are pretty valid but you're lacking some pieces

Point 1 is valid

Point 2:

Locking the bootloader enforces secure boot, not verified boot. The kernel will set up dm-verity and verify any partition mounted with verify in fs_mgr_flag options

However something needs to make sure that the kernel and the key are really the kernel and the key that are supposed to be there. Locking the bootloader does that. It verifies the boot and recovery partitions

However since the bootloader only verifies the boot partition it is the responsibility of the boot image to set up dm-verity. If the boot image does not do so the bootloader cannot do anything about this

Point 3 is valid but people's interpretation of what you mean is not. Be it the internet or real life people do not understand or interpret what you tell them. They understand or interpret what they want to and whatever they want to understand it as can be wildly different from what you meant

Locking the bootloader indeed does prevent someone from using the recovery to flash a modified system but not using twrp. You will have to use the recovery that comes with the ROM. Lineageos on user builds has a recovery that doesn't allow flashing anything not signed with a known key
[OnePlus 3 & 3T Cross Device Development] :
Not really: you can still use the default passwd for secured boot - which is not secure.

Read exactly: I stated that the locked bl verifies boot partition and recovery partition needs to be signed with aosp verity keys.

Again, read exactly: the original question is aimed at "this rom". This rom doesn't require system signed.

That's nothing I've missed, but exactly what I explained.

I don't get your point. Maybe you can explain what people understand and how to avoid this misunderstanding.(*)

Again, read exactly: I've expected this, that's why I've mentioned twrp explicitly. It's related to the recovery and not only to the state of bl...

(*)you love to misunderstand, misinterprept and cut down my explanations, arn't you? ;)
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Nowhere have I mentioned you nor did I see your post

Also, when did secure boot have anything to do with encryption? Did you just confuse secure boot and secure startup?

System is signed on all ROMs on op3 that use lineage trees.

It isn't enforced because the commit used to enable signing is broken and will fail boot if enforced

Unless oneplus is violating the spec both boot and recovery only need to be signed with the same key, not AOSP keys. Also I really would like to see a CVE for the system not displaying any warning when booting with a publicly known key
[OnePlus 3 & 3T Cross Device Development] :
Yes, I did. I was confused about you're statement I would have been talking of verified boot, when stating that a locked bl verifies the signature of boot partition and recovery partition.

I've stated tjat the system partition doesn't NEED to be signed, in other words:

You are right, havn't checked specs 'til now, but since twrp and most roms use the aosp verity key (on op3/t) this is quite theorethical...

[MENTION=9655534]geekwithlens[/MENTION]: as you can see, the question wasn't that simple... ;)
[OnePlus 3 & 3T Cross Device Development] geekwithlens:
Thank you [MENTION=4405529]nvertigo67[/MENTION] and [MENTION=5842226]anupritaisno1[/MENTION] . There is a lot for me to learn. :)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with August 2020 ASB patches available

Hi all,

a new build is available for download and will soon be also offered via OTA update:

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

ASB Security string 2020-07-05

Bromite Webview updated to 84.0.4147.113

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

Kernel: Wireguard tag v1.0.20200729

Kernel: qcacld-2.0 merge of CAF tag LA.UM.7.6.r1-07800-89xx.0

Location of the firewall functionality has moved to Network > Data usage in Settings (latest cherry-pick from here)

Happy flashing, regards M.
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
Does this have the latest MicroG build?

EDIT: Nope, it doesn't. Still version 0.2.10.19420-77. Is it possible to update the MicroG part manually, or will it break things?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
As you correctly found out already, it does not. My test to do so ended up in a boot loop, so I decided to postpone it. The current /e/ version contains already the most important fixes, so there is no immediate urgency to do so.

As I don't have much time right now to get into the root cause, better to ship a working build with sec. fixes for now.

If you would like to try, please go ahead - you can't "update", but would have to really replace the /system/priv-app/GmsCore/GmsCore.apk through TWRP.
[OnePlus 3 & 3T Cross Device Development] :
Newer is not always better or more secure: The /e/ version is tested, coded and build for a (security enhanced) los fork and the /e/ microg port is maintained by the same dev as microg. In this very context (hardened los) the /e/ microg port is probably safer and more stable then the original microg port. Apart from the unsolved boot loop issue, it seems quite smart to me to use the /e/ port of microg.