yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
If you use the settings search and type Buttons, tab the first hit, expand Advanced and tap on Additional buttons...
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-17-0-oneplus-3-3t-t3990061

Experimental LOS17 now available
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I have a question. It's not really important but I'm interested in the reason why this is happening:

Why is the keyboard disappearing 1 second and then re-appears when starting the device and typing in the pin for decryption?

Can someone explain this? Would be really cool :) . It also occur on OOS.
[OnePlus 3 & 3T Cross Device Development] anavarro8794:
For the past 3 builds I've been trying to clean flash the ROM with just gapps, but I keep getting a boot loop. Should I try something else
[OnePlus 3 & 3T Cross Device Development] Dirk:
Can you link to the gapps package you are trying?
[OnePlus 3 & 3T Cross Device Development] Ysfzone:
I'm on OOS 9.0.5 and i have some issues and i want to switch to LOS 16.. i want to ask you some question..

1- LOS 16 for OP3 stable for daily driver ? i use my phone in my work and i want a good stable rom..

2- Battery backup ?

3- Any major or famous issue in LOS 16 ?
[OnePlus 3 & 3T Cross Device Development] Master_TC:
1- yes

2- good (depends on useage)

3- no
[OnePlus 3 & 3T Cross Device Development] Ysfzone:
Thank You very much..

Can you help me a little to install LOS16 ?

ANY SUGGESTIONS ?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-16-0-oneplus-3-3t-t3866517

https://wiki.lineageos.org/devices/oneplus3/install

https://xdaforums.com/oneplus-3/one.../recovery-official-twrp-oneplus-3-3t-t3543391

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] zadock:
[MENTION=4405529]nvertigo67[/MENTION] has provided you the necessary stuff to flash LOS 16.

In summary, unlock your bootloader if neccesary, flash the lastest version of TWRP recovery, wipe data/factory reset, flash rom, Gapps, and reboot system :good:
[OnePlus 3 & 3T Cross Device Development] Ysfzone:
OK i'm now on LOS16

I have some questions

1- how i can show battery percent on notification bar ?

2- how i can pass safety net (Look attached screenshot) ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
For #2, go to the NLOS ROM thread and read the third post.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Settings>system>status bar>battery style
[OnePlus 3 & 3T Cross Device Development] zadock:
Is camera2 api enabled in this rom?

Is there anyway to run a pay banking app with no root and unlocked bootloader?
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
[MENTION=5091734]dianlujitao[/MENTION]

Last night i turn off the phone as usual. This morning i turned it on and i found that all data was gone, apps were installed but internal storage was completely wiped away. I didn't do anyhing, i only booted the phone like every morning.

It's the first time that i experience this issue with a rom and i can't figure out how it is possible to lost all data on a phone simply by rebooting it. I was running unencrypted ext4.

Thank you for your work, i hope that you have an explanation for this behaviour.
[OnePlus 3 & 3T Cross Device Development] realtos:
use search, both are already answered here
[OnePlus 3 & 3T Cross Device Development] realtos:
hello my good people is there any way to fix these things ( yes they arent flaws but it stands in the way of VISA payment directly from NFC ) or are they associated with the OEM unlocked and cannot be changed cuz the ROM itself makes it look like root when its unlocked? cuz root beer sample detects it as root even its just OEM unlocked

tried to install magisk and set the setting to NO root but doesnt help.

app https://play.google.com/store/apps/details?id=eu.nets.dankort&hl=da
[OnePlus 3 & 3T Cross Device Development] simmeone:
I have run the latest lineageos, but titanium backup doesn't run anymore. Can anyone confirm this or is it a issue of titanium backup? Here is the log file.
[OnePlus 3 & 3T Cross Device Development] :
That's the same for me, after updating titanium backup from 8.3.3 to 8.4 the app FC at/after checking license. Downgrading TB back to 8.3.3 and the app is working fine again. The same behavior also with my OnePlus One. Root with magisk 20.

It looks like it's a TB issue ...

Edited: yes, it's a TB issue. New fixed update is on its way ...

Edited again: https://twitter.com/TitaniumBackup/status/1188488479736500224?s=20

End of off-topic ;)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Deleted
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Confirmed. Same for me, only that the versions are 8.3.3 and 8.4.0 :)

NLOS-16.0, Magisk 20.0

Edit: version 8.4.0.1 fixes the problem and works just fine.
[OnePlus 3 & 3T Cross Device Development] :
Thx for the version hint ;)
[OnePlus 3 & 3T Cross Device Development] simmeone:
The new version doesn't work too
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Does Magisk show that your phone passes SafetyNet? If not then you need to flash this zip to set the correct security patch date: https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post78433987

If your phone does pass SafetyNet and your banking app doesn't work then use the Magisk discussion thread to get help with using Magisk hide: https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[OnePlus 3 & 3T Cross Device Development] adriakus:
This ROM doesn't support "signature spoofing", am I right? I need to install microG, so I need this feature. Is there any way to "activate" signature spoofing without having to flash another ROM?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Use this one https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405
[OnePlus 3 & 3T Cross Device Development] :
Have you really updated to the new 8.4.0.1?
[OnePlus 3 & 3T Cross Device Development] simmeone:
Yes and it is the same error
[OnePlus 3 & 3T Cross Device Development] jj71787:
I have a couple of problems with this rom.

1. I don't see volte

2. Netflix is not on the play store and if I side load an apk it says device not supported
[OnePlus 3 & 3T Cross Device Development] :
Then you should give the TB support team a note
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I went straight from 8.3.3 to 8.4.0.1 and it's working fine.

Have your tried uninstalling/reinstalling TB?
[OnePlus 3 & 3T Cross Device Development] realtos:
volte is in setting :) use it myself and other isnt a question just a statement or?

---------- Post added at 01:07 PM ---------- Previous post was at 12:56 PM ----------

thank you for responding

my phone used to pass everything in magisk up until a month or so ago but i tried to use magisk hide aswell in settings at that time and gave up but i really want to use it to pay directly but it seems hopeless i think

now my phone doesnt pass the first cts and it still dont work obviously, i didnt google the subject and found an old video with a module rootcloak but that was for the old app and video was old so thats out of the question too

i reead somewhere that some bankin apps tries to detect if phone is rooting by lookin for certain apps like the magisk manager app, maybe i should msndowntool the **** back to factory and try again and only flash magisk zip and go direckly into setting and add it to hide but what does that help if cts dont pass, the zip from that site dont work here, both flash as module and trwp. maybe im just cursed
[OnePlus 3 & 3T Cross Device Development] :
Read https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 . For current los16 flash sec-patch-2019-08-01.zip and check if the string was changed. If it hasn't been changed, get a recovery log, if it has changed, reboot to system and check safetynet api again.
[OnePlus 3 & 3T Cross Device Development] :
Which error message do you get if trying to manually installing the apk?

Do you pass safetynet api and is gplay certified?
[OnePlus 3 & 3T Cross Device Development] jj71787:
I get this device is not supported error.

Yes gplay is certified

For safety net. I get cts profile false

Basic integrity true
[OnePlus 3 & 3T Cross Device Development] :
If you get gplay as certified if the cts check fails, it's old data in cache. Wipe cache and data from gplay, force stop and restart gplay to see the real value.

Apart from that, netflix utilizes the safetynet api. That's why netflix isn't supporting the device. Get cts profile (and therefor safetynet api) passing, wipe cache and data on gplay, force stop gplay and on the next gplay start, you can install netflix from gplay again
[OnePlus 3 & 3T Cross Device Development] jj71787:
Oh wait in settings under play protect it says not certified
[OnePlus 3 & 3T Cross Device Development] :
Wait for what? I know your device is not certified if cts profile match check fails. Anyway: this piece of information doesn't change my recommendation on how to get netflix running again...
[OnePlus 3 & 3T Cross Device Development] jj71787:
Cte is fixed and play store is now certified but Netflix app still doesn't appear and of I sideload it it says device not supported by app
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
It will appear. Wait a bit, open a beer, reboot...

It will if CTS is passed and play store is certified.

And if it says by sideload that it's not supported, choose another apk.

There are several version for different apis and so on. Maybe you downloaded the old one for < Android 7
[OnePlus 3 & 3T Cross Device Development] defi231:
same problem here if i use my normal install routine, i have to use the aospkey signer you made to get it working, even with magisk 20 i get bootloops without the aospkey signer.

update: rather than dirty flashing, i did a clean install with factory reset looks like its now working without the signer..still testing
[OnePlus 3 & 3T Cross Device Development] :
Good to know!

I've always assumed it's fixed with https://github.com/topjohnwu/Magisk/commit/085ea6d0a1ba295fa26fd6d06d5b9eac69cf5c47 . Strange.
[OnePlus 3 & 3T Cross Device Development] realtos:
now it worked and magisk say okay now to both but hide in magisk still dont work on Dankort app. see pics. sorry for the last one isnt english, used eng lang though, it say "your device is rooted"

maybe this specific app wont work at all no matter what, i called the number and they said aslong as i can get root by doing some steps and its not part of OEM which dont allow this the app wont work

are there any other hide root apps outthere? the ones i found on google dont exist anymore and the ones i saw guide from isnt avail anymore in magisk

maybe it only works if i relock bootloader as i have everything root disabled but im unsure what happens if I relock it
[OnePlus 3 & 3T Cross Device Development] :
Detecting root and hidimg root is a constant race.

I've never used an app myself, that detects root though it was hidden. Some apps try to detect MagiskManager. There's a setting to repack the Manager app with a differnt name.

If that doesn't help, you can try to help [MENTION=4470081]topjohnwu[/MENTION] to track down the detection of Dankort to get Magisk working with Dankort.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I installed Dankort, hid Magisk Manager, hid Dankort and the app worked (screenshot). I'm using Magisk 20 stable.

If I don't hide Magisk Manager then the app says in rooted.

PS: this is also very helpful https://www.didgeridoohan.com/magisk/MagiskHide

also reading through the Magisk Support thread https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[OnePlus 3 & 3T Cross Device Development] realtos:
omg thanks both of ya. used hide manager and it worked. never though i just could do that. thanks again a million :)

hope this helps out others
[OnePlus 3 & 3T Cross Device Development] defi231:
i checked the magisk log after installing vers.20: "signed with testkey"

if i do a clean install with magisk it is working but after i update the OS i have to sign it again with the AOSP Key or i get bootloops
[OnePlus 3 & 3T Cross Device Development] :
If you still have a copy of the install log, would you please open an issue? Thanx.

https://github.com/topjohnwu/Magisk/issues

For easier reference and to avoid writing the same explanation over and over again, I've created this posting:

https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433989#post78433989
[OnePlus 3 & 3T Cross Device Development] defi231:
JFYI: issue was closed with answer from topjohnwu

"Using Magisk with locked bootloader is not officially supported. Users should expect to sign with their own keys if they want to use locked bootloader. Nobody knows what the bootloader/system expects"
[OnePlus 3 & 3T Cross Device Development] mr-cook:
Had the PIS bug today on 10/30 build. Haven't been following the thread. Don't know of it's supposed to have been fixed yet or not.
[OnePlus 3 & 3T Cross Device Development] Naudiz:
I can't say that I understand everything in the github-discussion, so if anyone could "translate" it for me, it would be highly appreciated. If I understand correctly, some commit was added to Magisk recently so that it will work with locked bootloaders without the need of verified boot patcher?

If this is correct, is this commit already in Magisk 20.1?
[OnePlus 3 & 3T Cross Device Development] :
Yes. No.

It's fixed in the zip I've attached at the end of the github issue conversation (which is patched from canary build 20101 build) and in today's canary build (20102).
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Can anyone else confirm that with the "prevent accidental wake up" option enabled and the proximity sensor covered the device still unlocks as if the sensor doesn't get checked?
[OnePlus 3 & 3T Cross Device Development] anyone23:
"prevent accidental wake up" disables double tap to wake for me when the sensor is covered. It doesn't stop the power button and volume buttons from turning on the screen however.
[OnePlus 3 & 3T Cross Device Development] haelmchen:
That's expected behaviour. It's this way, so your phone doesn't freak out in your pocket and your leg touching the display all the time.
[OnePlus 3 & 3T Cross Device Development] Iceman248:
I've been toying with this ROM on my backup phone and I noticed that after I removed screen lock and even rebooted, that the encrypted status is still "Encrypted". Ever since I moved from OOS to this ROM, the encryption status seemed wonky. In Trust, it told me a screen lock was required for encrypted even though I had one from OOS, but after turning off and back on, it no longer complained, but now with it off apparently my phone is still encrypted. I don't get it. Any help is appreciated. I want to clean flash and use this phone as my primary.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Not sure about trust complaining about the screen lock, but screen lock and encryption are different things, although the screen lock key is what is used as the decryption key as well. Turning off screen lock doesn't remove encryption. I don't think you can remove encryption without formatting data. You don't need to remove encryption to clean flash unless you're having issues decrypting data. I believe the OP3/T uses full disk encryption, and not file-based encryption which is used in newer devices (I have not used that so can't comment on how it's different UI wise).What exactly is your issue right now with encryption? You should be able to use LOS. A clean flash involves just "wiping" data via TWRP, not formatting data.
[OnePlus 3 & 3T Cross Device Development] Iceman248:
Thanks. I noticed the status displaying incorrectly in trust, but was resolved when I removed screen lock and readded, so that made me feel like the encryption was possibly a bit wonky, so I wanted to refresh it, but I'm not an encryption expert, so perhaps it's fine. So encryption stays fine through ROM flashes of different kinds?
[OnePlus 3 & 3T Cross Device Development] knpk13:
I have never experienced that so I cannot comment. I'll let someone else answer that.

Generally, yes, from my experience with OOS and custom ROMs on the OP3/T. There have been hiccups with encryption in the past relating to different OOS firmware updates and custom ROM support, but I'd say Pie is pretty stable now. If you have a screen lock and full disk encryption, you should be asked for your screen lock early during the boot process (well before you reach the homescreen).
[OnePlus 3 & 3T Cross Device Development] :
los has decided to combine lockscreen passphrase with secure boot passphrase: you can set the secure boot passphrase to the same value the lockscreen passphrase, when setting up a new lockscreen passphrase. According to this design decission, trust refers to the combination of secure boot passphrase and lockscreen passphrase as "secure lockscreen". Trust starts complainimg if one of them is not set.

Sidenote: If you want different passphrases for secure boot and lockscreen, use this posting as reference: https://xdaforums.com/showpost.php?p=80390263&postcount=3244

I recommend to search the thread for "encryption" and once again for "default_password" to understand, that a userdata partition can be encrypted and the user is never asked for a passphrase, and how to remove and/or initialize encryption. That's all is explained more then once in this thread.

For the difference of fde and fbe (considering a passphrase is set):

fde encrypts the whole partition - nothing can be read, without decryption on startup.

fbe encrypts single files; that means that single files can be excluded from encryption and can be read at any time no matter if the passphrase was given or not.

Example: poweroff alarm will work on fbe, but not on fde, because the bootprocess stops waiting for the passphrase for fde.
[OnePlus 3 & 3T Cross Device Development] Iceman248:
Thanks for the info. One other thing I noticed that is similar is that in Trust, it also says Root Access is Disabled, which is most definitely is enabled and works, but it says it's disabled. This Trust center doesn't seem very trustworthy itself. It seems to have no idea what's going on with my phone.
[OnePlus 3 & 3T Cross Device Development] :
addonsu or magisk? If the first: your setup is broken (it's definetly shown as rooted if addonsu is enabled in devopts), If the latter: of course not, that's the purpose of magisk.
[OnePlus 3 & 3T Cross Device Development] Iceman248:
Ah, okay. Magisk is what I have.
[OnePlus 3 & 3T Cross Device Development] Peachh:
Every once in a while, for no apparent reason, a particular short sound file, which sounds like 'tinkle', will play. I'm pretty sure it is not notification sound because I have set the notification volume to zero in settings.

Is there a way to find out which App or process plays that sound? This strange thing happened after I installed LineageOS 16. And Apps I installed in LineageOS are restored from OxygenOS by TiBackup.
[OnePlus 3 & 3T Cross Device Development] TNSMANI:
While I have no specific suggestions for your issue, as a general rule, avoid TiBU restores between ROMs and between major versions of the same ROM.
[OnePlus 3 & 3T Cross Device Development] :
I can't emphazise enough, how much issues, time and debugging stress can be avoided by following [MENTION=5656100]TNSMANI[/MENTION]'s advice!

That being said, I'd suggest to check the log, which app is misbehaving. If you can't find it in the log: clean flash and restore apps one by one and see which app introduces the above. IMHO: in the end it will be less time consuming to clean install your apps.
[OnePlus 3 & 3T Cross Device Development] Iqbal Ansari:
So I installed LOS16 on my oneplus 3, everything is working except I cant install latest Gcam port (Tolyan009 Gcam 6.2). As soon as I install it, it says the app is not installed.

I can install Arnova Gcam 5.1 however the picture quality is bad.
[OnePlus 3 & 3T Cross Device Development] Peachh:
Okay. Thank you for your advice.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
[MENTION=10066028]Peachh[/MENTION]

I would like to add that for me it works by installing the apps like usual from Playstore/F-Droid/etc. and then just restore Data with Titanium. (I think that way all the permissions and links can be correctly generated so notifications and stuff should work)

If you run into problems with some app try to clear it's Data and start fresh with it.
[OnePlus 3 & 3T Cross Device Development] Peachh:
Okay. Thanks for replying. I'll try it later. <3
[OnePlus 3 & 3T Cross Device Development] :
Snap: qr and barcode reader

Our shipped cam app "Snap" is build with a qr- and barcode reader:

https://github.com/LineageOS/android_packages_apps_Snap/tree/lineage-16.0/quickReader

How can I use the Snap's build in qrcode reader?

EDIT:

Same question for photosphere and panorama.
[OnePlus 3 & 3T Cross Device Development] Chol:
After upgrading from 20191102 to 20191113, my oneplus3t was stuck on boot logo. Downgrading back to 20191102 fixed it for now.
[OnePlus 3 & 3T Cross Device Development] :
If you look at https://www.lineageoslog.com/16.0/oneplus3 you'll find an earlier 1113 build pulled, perhaps you've been too early with updating and grabed tbe pulled one... Check the checksums to be sure you have the current zip.
[OnePlus 3 & 3T Cross Device Development] Chol:
Thanks for the hint, but the sha256 of the most recent one is the one I installed. I'm on firmware 9.0.5 and TWRP 3.3.1-0.

I will wait for someone else to confirm this version (not) working.
[OnePlus 3 & 3T Cross Device Development] :
...or wait for the next build... Perhaps the build from 8:51 UTC is not the last 1113 build.... ;) Since lineage has moved away from jenkins I don't know how to look at the build logs, so I can't know for sure, but somthing with today's builds (two remobed again) seems wrong.
[OnePlus 3 & 3T Cross Device Development] Chol:
In https://buildkite.com/lineageos/android/builds/6501 you can click on that " bash android/build.sh" box on the bottom to see some log output.
[OnePlus 3 & 3T Cross Device Development] :
Sadly, that's only the initialization, soong- and make-setup, the actual build is missing, and the next is "uploading". I miss jenkins... :(
[OnePlus 3 & 3T Cross Device Development] An68:
Work
[OnePlus 3 & 3T Cross Device Development] Chol:
Going from 20191102 to 20191110 and then to 20191115 worked fine. :)
[OnePlus 3 & 3T Cross Device Development] sfoslino:
Thank you, can confirm the issue. Had the same trouble.

I was on 20191102 too. After upgrading to 20191115 the device was in a bootloop. Back to 20191102 and the device was ok again. Upgrading from 20191102 to 20191110 works and after that the upgrade from 20191110 to 20191115 works too. :good:
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Update from 20191024 to 20191114 went well for me.
[OnePlus 3 & 3T Cross Device Development] DaveHD2:
Hi [MENTION=9837900]slipenbois[/MENTION], I too have the same issue running the latest nightly (lineage-16.0-20191116-nightly-oneplus3-signed.zip) and many before it. Did you ever find a solution? Apologies if there is a solution posted, I have searched and can't seem to find one. Sometimes if I toggle wifi on/off the home & recents start to respond again but not always. The other symptom for me, is that the keyboard no longer appears once in this state, with either the bundled AOSP keyboard or gboard set as default. I have tried the suggested rerun setup wizard and switch from guest user back to myself suggested methods, neither of which have made any difference. I should mention I run on screen nav keys rather than using the hardware buttons. Switching to hardware keys once the issue occurs persists with unresponsive home & recents. If anybody else could offer some insight or suggestions it would be greatly appreciated.