yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Try this.

https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763/page130

Migrate is free and can backup app bundles (split apks). Titanium backup is paid (it has a free version too) but I've had issues with it restoring app bundles. There's a few other apps floating around like oandbackup and swift backup for app backups, but I think they have more disadvantages.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
That's a very nice ROM, my daily driver for about two weeks and it's quite solid, thank you!

Love the ability to turn off captive portal, really helps to work with WiFi ODB adapter to diagnose my car, because by default android would switch to 4G if there's no internet connectivity on Wifi!

I did have some troubles getting Google Cloud Messaging to work, but nothing extreme that searching in internet couldn't help(in my case I needed to dial *#*#2432546#*#* after enabling GCM for apps to start registering). I still miss some notifications occasionally, but I'm not so sure if it's ROM's fault or just some specifics of how microg works. And I do have 1 app that shows it's registered but refuses to receive notifications completely. We'll see how/if this resolves.

I have couple of things I'd like to ask though:

1) wireguard kernel support - currently wireguard userspace app eats up about 20% of my battery consistently as I have Always-on VPN, so would be really nice to add kernel support for that, to get rid of the need for user app to constantly wake up and keep the connection alive

2) after recent update Aurora services behave weirdly when I do app updates via Aurora Store: all updates are being downloaded and then all of them show the notification showing "Installing" status, which just hangs there without doing anything. I have to manually go for each app in Aurora store and click "Install" to actually update. When I go go to Aurora store settings -> Installations (give root access) and click a menu item "Aurora Services - Launch Aurora Services" I get "Could not launch services" toast notification. Previous version of ROM updated properly, as far as I remember

Otherwise, great job, thanks a lot!

Cheers!
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi, thanks for the positive feedback.

Regarding microG - not all apps work fine with it, but many do. I include it in my ROM, but I can't give any support, please refer to the respective support thread. One hint I can give in general: Don't use the "ask" feature for the GCM registration, but rather let the app register and if needed, refuse the registration afterwards.

Wireguard is something I am already considering, not highest priority, but chances are good... ;)

The mass update bug in Aurora is an Aurora issue already discussed in the Aurora thread for version 3.2.4, next version 3.2.5 is supposed to have it fixed. Haven't tested yet, will do so soon and update it in next build.

I recommend to choose the AuroraServices installation method, you can in that case refuse Root. The only reason to call the AuroraServices UI is btw to grant the storage permission. If you have chosen within the UI to hide its icon, you can't call it any longer, neither from Aurora settings, but as said, not really necessary.

Also nothing directly related to the ROM, I simply bundle it, together with microG.

Regards, M.
[OnePlus 3 & 3T Cross Device Development] :
If you don't like the compiletime update (I like to have the code that will be compiled ready for review before I start the build and not updated on the fly when the kernel is actually compiled during build) you can use these commits:

https://github.com/nvertigo/android...c83aed8#diff-d6c5855a62cf32a4dadbc2831f0f295f

https://github.com/nvertigo/android...0fa8370#diff-d6c5855a62cf32a4dadbc2831f0f295f

and this adjusted script (pwd should be the kernel dir, script should be placed somwhere, but not in the kernel tree):

https://raw.githubusercontent.com/nvertigo/local_manifest/nlos-16.0/wg_fetch.sh

After running this script net/woreguard is updated to the latest version, but is NOT commited. I commit these changes like this:

https://github.com/nvertigo/android...mmit/8bf9d61d39cbfcf50d1c2e822ede9f01422a9429

but it's not necessary - I lile it fpr documentation and reproducebility. YMMV, though.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with May ASB patches (and other news)

Hi all,

a new build is available for download here and also already offered as OTA update:

ASB Security string 2020-05-05

Telephony: Option to set different ringtones in case of Dual SIM

Kernel: Native Wireguard support

Kernel: Merged CAF tag LA.UM.7.6.r1-07400-89xx.0 (also f. WLAN)

Kernel: Misc. optimizations

Bromite Webview on 81.0.4044.127

AuroraStore updated to 3.2.8

Regards, M.
[OnePlus 3 & 3T Cross Device Development] :
You've merged android-3.18 too early. You've missed 519362305e44^..552e41c10182, which contains https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=ASB-2020-05-05_3.18 (caf/aosp/android-3.18 is identical to google android-3.18, the commit hashes are the very same).

I've cherry picked 519362305e44^..552e41c10182 on top of https://github.com/lin16-microg/android_kernel_oneplus_msm8996/tree/lin-16.0-mse2 in https://github.com/nvertigo/android_kernel_oneplus_msm8996/commits/merge-16.0 .

In https://github.com/nvertigo/android_kernel_oneplus_msm8996/commits/nlos-16.0 I've added some features but mainly apply fixes needed to compile the kernel with gcc 7 on top of https://github.com/nvertigo/android_kernel_oneplus_msm8996/commits/merge-16.0 .
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
There's an interesting app I've seen on fdroid called tracker control. Don't know if that's something for a future consideration for the rom. I couldn't get it working due to the blocked /proc/net. My brief attempt to install as system failed also. Not something I have much experience with but thought it was worth the post. Thanks for the ROM.
[OnePlus 3 & 3T Cross Device Development] Mugenski:
Just wanted to say thanks for the ROM. It has given a new lease on life to my aging device. Impressive battery life.

Only bug I have experienced seems to be failure to wake by fingerprint after the device has gone to sleep. Guessing that's a lineage things. Otherwise it's spot on.

Thanks again.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I could add an exception to the SEPolicy, similarly as I did for the Netguard app - will have a look at that app, I may provide an updated SEPolicy in my next build.
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
Great I'll keep an eye out. Cheers.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Next build will have that exception, just successfully tested it.
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
Awesome thanks for taking a look. Im looking forward to testing myself.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
New build with June 2020 ASB

Hi all,

a new build is available for download - it is also offered already through the updater app as OTA update:

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

ASB Security string 2020-06-05

Kernel: Wireguard tag v1.0.20200520

Bromite Webview on 83.0.4103.101

Sepolicy: Netmonitor exception f. "Tracker Control" app

Note:

This month, no platform patches have been applied (only kernel has been updated with many sec. patches):

The AOSP tag android-9.0.0_r56, which was merged already in May, did already contain all patches, which were pushed again by Google in tag android-9.0.0_r57, which represents the June 2020 ASB.
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
Thanks again for the extra effort. I'm using the tracker control app right now!
[OnePlus 3 & 3T Cross Device Development] $anket:
Hi

My setup is encrypted/locked BL. How can I install this update with my current setup? Dirty flash or OTA?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
If you really have a locked boot loader, I assume you run on Stock OOS ROM (otherwise your BL could not be locked). Then follow the instructions in the OP.

If you have already a Custom ROM on your device, your BL can't be locked. If this Custom ROM is a different one than one of my builds, which this thread is about, also follow the instructions in the OP (I.e. clean install - and carefully read the linked article about firmware).

If you use already one of my Lineage 16.0 builds, you can do OTA or dirty flash, as you like - whether your device is encrypted or not does not matter in this case.
[OnePlus 3 & 3T Cross Device Development] :
You can run custom roms and current twrps with locked bootloader. A locked bl just requires signed boot and recobery partitions. los16, nlos16 (and I guess this rom, too) come with aosp verity key signed boot images. Newer twrp (since 3.3.1-0) recovery images are also signed with aosp verity keys.

For completeness: Magisk since 20.3 resign the boot partition after altering it with aosp verity key.

[MENTION=4487131]$anket[/MENTION]:

Manually updating the rom if data is enctypted is always the safe choice. Updating with automatic flashing on encrypted data sometimes results in a non-booting device (no hazard, just cöean flash again). Using the Update app to download the new build is no problem.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for the info, wasn't aware about that.

Always thought that the locked BL checks for an OEM-specific signature to prevent flashing "non-OEM" stuff...

Does that mean you can simply lock the BL again after e.g. flashing TWRP and/or LineageOS over Stock?
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
I'm running this ROM with locked BL and encrypted data and updated the last few times with OTA with no problems. I've noted however nvertigo67 that manual is recommended in this setup. Cheers.
[OnePlus 3 & 3T Cross Device Development] :
You need to unlock the bl for flashing a signed twrp (unlocked bl is needed for "fastboot flash recovery twrp.img"). After that you can lock the bl again.

As a dev I wouldn't recommend a locked bl, though: "fastboot flash recovery" and "fastboot boot testkernel.img" won't work anymore (the first isn't really important after twrp has been installed once, but the latter is really usefull for testing kernel patches IMHO). I also like the unlocked warning when I wanted to reboot to recobery, but the fat finger has hit system... ;) the warning allows to change the boot target with vol keys... ;)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
For exactly that reason I won't lock my BL (because, also, unlocking again would mean factory reset) - but important to know... :)
[OnePlus 3 & 3T Cross Device Development] :
Just for completeness and to avoid misunderstandings: the issue is triggered by the combination of an encrypted userdata partition amd twrp. It doesn't relate by any means to locked/unlocked bl.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I am not sure I concur with that for two reasons:

1. I use the standard LineageOS updater app - unmodified. The only thing I do is to overlay the download URI (as I obviously can't make use of LineageOS' download server). If there was an issue, it would be an issue for all official LineageOS builds.

2. Technically spoken, the userdata partition is not touched at all during a dirty flash - only system and boot are replaced. The updater app writes the ROM Zip to a specific unencrypted block area to avoid the necessity to decrypt /data, because the download dir obviously is part of /data. TWRP then picks the image in update mode from there.

If you manually flash, you could e.g. also skip decrypt in TWRP and do a sideload.

Therefore I don't think that OTA on encrypted devices is a potential issue .
[OnePlus 3 & 3T Cross Device Development] kHAW17:
Silly question: You aren't planning to port your ROM to xiaomi redmi 9s, are you?

That would be really awesome, but I think the chances are below zero... :laugh:

Nice work.

Greetings

K
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I only build for devices, which I own - very simple.
[OnePlus 3 & 3T Cross Device Development] :
Read the los16 (and los17) thread, the twrp thread and some mentions in the help forums. Unbootable setups after automic flashing updates from Upadater app occurs in about one time out of ten (guessed!) on los16 (and los17) with encrypted userdata partition and boot passphrase set, even if the block map (to access a file for flashing on the encrypted userdata partition, though twrp automatic flashing doesn't ask for passphrase) mechanism is working...

This is a long term known one.

for 1.: I don't think this is the Update app itself, but the automatic flashing in twrp which renders the device unbootable. But even if it's due to some error in the Update app (maybe when generating the block map files - see above), since you use the same app as official los this rom is also effected.

for 2.: The userdata partition IS touched during updates: for reading the zip and after boot to system (first boot after flashing the update) the dalvik (should(*)) for updated system apps should be rebuild - but if this issue occurs this stage is never reached.

The next twrp will have this https://gerrit.twrp.me/c/android_bootable_recovery/+/1664 (hopefully) and get rid of this ugly one out of ten issue.

(*) only works if the app or jar versionmis increased; not always true (e.g. for Snap: often changed without version bumb); that's why I recommend wiping dalvik and caches - which only works on manual updates, ofcourse.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for outlining the background of this and showing the commit in TWRP.

I have made a note in the "Tipps & Tricks section (post #4) about it.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Installed new build, weirdly enough I still have issue of Tracker Control not working after installing it from f-droid. Still says "Device not supported. The OS of your device does not allow for monitoring nd filtering of network communications". Tried looking in logs but see nothing related to that app. How can I troubleshoot?

Another issue I have in last 2 builds is that display doesn't go to sleep, even though it's set to go to sleep after 1 minute of inactivity. It used to randomly refuse to sleep, but now it became more consistent - just doesn't turn off unless I press power button, even if I set shorter period, like 15 seconds. Once again, I'll be happy to troubleshoot.

Otherwise, thanks for your work as always!
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Hi, first of all, thanks for your feedback.

I just downloaded and installed Tracker Control again from F-Droid and I did not get that error, which I got when I initially tested it before updating the SELinux rule accordingly. So I am sure, it works.

An important hint: To assign a user-installed app to a different SELinux context, other than the default "untrusted_app", its package signature has to be added to the rule. For its own app repository (different from linked 3rd party repositories), F-Droid fetches the source, builds the app and uses an own F-Droid signature. This means, the signature is a different one compared to downloading the apk directly from Github. Therefore, " from F-Droid" has to be taken literally, the apk directly downloaded from GH still won't work, only the one installed via F-Droid's main repo through the F-Droid app (not from F-Droid web page either -

I am further also not entirely sure, how F-Droid behaves, if you have linked 3rd party repos and an app is offered by more than one repo...)

In regards to the display - I just tested again on my device, all fine (I definitely would have noticed).

Can you maybe produce a log? Without knowing more, my first "wild guess" would be that there might be an app with a wake-lock active?
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Thanks for your swift reply!

I got more weirdness going on.

1) In regards to Tracker Control: I only use official f-droid repo, still not able to make it run, can I somehow dump the apk signature, so we can verify we have same signature?

2) display stuff: I removed Magisk completely(even though I only had 2 modules: Youtube Vanced + emoji font replacement) and display started to work ok. I'm wondering if one of apps that required root kept waking my phone up...

And to resolve the Tracker Control issue I dirty flashed the latest zip, installed Magisk again on top of that and chose to Clear dalvik and cache in a dialogue after flashing a zip and now I lost all of my userdata. Every app I had installed persisted, but all of my app settings, photos, music etc etc are gone. I'm on TWRP 3.3.1-1. Obviously it's really unpleasant but I guess I'll live, the question is what could've caused it: it's not a data wipe, but user storage wipe. Were there any changes in partition scheme, so that TWRP might've formatted the wrong partition? Any idea, so we can at least warn others?

And yeah, Tracker Control still doesn't work after this "forcefully half-fresh" installation unfortunately

UPDATE: I decided since I have already lost my data I might as well perform a clean install. So I did that. After clicking through initial OS setup screen and updating f-droid app to latest version, I still couldn't get Tracker Control running.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks again for your feedback. Regarding your user storage issue - the "internal memory" in fact is part of the data partition. The physical path is /data/media/0 (0 is the main user, if you have e.g. setup a secondary user, it would be 10 instead of 0); but the mount point for the sdcardfs, which is used by the Android system through all apps and APIs is /storage/emulated/0 - I assume, that this mount point was somehow broken... No idea, why and how, though...

Regarding the Tracker Control app - can you please extract the apk file from your device and upload it somewhere? The signature format used in the SEPolicy mac_permissions.xml file is different from the normal format, I would need to have it calculated by the respective python script first.
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Hi, I just took the latest version from f-droid and uploaded it here: https://send.firefox.com/download/2bb521807ae30a84/#bt2TmASWPUws-jRQGao6wQ

Original filename: net.kollnig.missioncontrol.fdroid_2020052102.apk

MD5: 81b693bc478aa529938c8089d6253a85

SHA1: a1f1cf084fc6430f1b01d0aac3f97c34ca223490
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Thanks for the file - seems I myself have hit that "parallel repo trap" in F-Droid - I have several parallel repo's active in F-Droid and I seem to have downloaded twice the app from the secondary repo (i.e. with its original GH signature) and not the F-Droid one. Wasn't at first aware that in fact I have two versions available to choose from in F-Droid. So if you download the Github release of Tracker control, it'll work.

Please advise, whether this would be ok for you (i.e. no changes in my SEPolicy) or whether you prefer the F-Droid version (which would mean, that I'll push a fix to consider the F-Droid version and you would either have to wait for my next build or you temporarily user the GH version now and when you update my build, you would have to de-install and then re-install Tracker Control again).
[OnePlus 3 & 3T Cross Device Development] soozie_:
Status bar indicator/icon issue

Hi [MENTION=7929484]MSe1969[/MENTION]

Thanks for the awesome work. I have been using the ROM for around a week and its very nice specially from SOT prospective.

I have a minor issue wrt status bar indicators/icons, specifically with network speed indicator. It doesn't get aligned with other indicators and places itself in the middle. So whenever there are many indicators some of them didn't appear properly.

https: //pasteboard.co/JdQ0nGs.png

https: //pasteboard.co/JdQ0VpQ.png
[OnePlus 3 & 3T Cross Device Development] :
Since pie the aosp code base has changed: you can't have real notchless layout anymore. What you really get on a notchless device is a zero pixel notch. The los team doesn't want to chage the aosp default behaviour; meaning adding to the api is ok, but changimg it is unwanted. So they added the possibility to add network traffic XOR clock in the "notch" for notchless devices but doesn't change the presence of the "notch". This way it's possible to add something usefull in the middle of the statusbar for notchless devices without changing the aosp default behaviour.

EDIT:

Somethimg wrong with the pic links; I can't display them (http error 400).
[OnePlus 3 & 3T Cross Device Development] soozie_:
So if understand correctly the network indicator is in the notch part for our device. I'm not an expert in the area, but can something be done so that other icons wrap around the notch and not behind it (this is my assumption of whats happening).

Sorry about that. The site is not allowing me to directly upload pictures and adding a link is also blocked as I'm a new user.

I have added the links with a space after https if your still want to have a look at them.

https ://pasteboard.co/JdQ0VpQ.png

https ://pasteboard.co/JdQ0nGs.png
[OnePlus 3 & 3T Cross Device Development] :
Your screenshots show the intended behaviour. The main drawback in g's api changes is dividing the status bar in two fixed areas. If - like in your screen shots - the area for the status items (right side of notch/network traffic) is full, the overflow dot is shown.

As explained, this can only be undone (one single area) if you change the aosp default api behaviour, which the los team has decided to avoid because of system and app wide impacts (a really good reason!!! IMHO).

BTW:

May I remember the official los 16 thread? For most - if not all - gui/ux related questions the information from the official los 16 thread is valid for this rom, too. status bar chanhes/limitations has been discussed there widely.

DISCLAIMER: I hate notches! Though I have to except these changes and make the best of it. No clock or clock without seconds or clock without secomds on the left or no network traffic but clock without seconds in the center can help alot.
[OnePlus 3 & 3T Cross Device Development] soozie_:
Thanks for detailed explanation and as suggested I will modify clock to make space for other indicators.

Cheers
[OnePlus 3 & 3T Cross Device Development] gonococcus:
Hey, glad to hear we have finally figured it out. As for your question, I think adding f-droid version to signatures makes more sense since you can have automatic updates etc. Or both signatures, why not?

I'm still figuring out how to make it work with wireguard kernel mode always-on VPN, so still not sure if I'm gonna use it constantly. But I definitely like this software so far.

Thanks for your quick response and continuous support of this ROM.
[OnePlus 3 & 3T Cross Device Development] EyUpTeacake:
Morning, just to note I was using the github release of tracker control when I reported it working. Apologies I didn't check fdroid version. I'm not fussed which source as long as I know. If others have a preference then that's cool.

Edit: it does look like the fdroid version is a month old.
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
I can't install Play Store (from Nanolx). Aurorastore doesn't fit my needs. It complains that the previous version has a different signature.

# pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

> Security exception: Permission android.permission.FAKE_PACKAGE_SIGNATURE is not a changeable permission type

Nanolx's patcher says signature spoofing support is already enabled. What's going on?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Signature spoofing perm is flagged "signature|privileged" in my build - so an app in need of it needs to be located in /system/priv-app and also needs permission white listing
[OnePlus 3 & 3T Cross Device Development] WM-Sef:
Thanks! I will give it a spin later today.

Any plans on making a LineageOS 17.1 build of this rom?