yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, clearly an error in the coding. It applies also to unlocking.
[OnePlus 3 & 3T Cross Device Development] Xydia:
Hooray it worked!

I've found two issues:

- Encryption - it doesn't work. In the UI I select it but get back a locked screen. UPDATE: I managed to fix this by "TWRP > Format Data".

- Enabling SELinux - your link suggests reflashing the modded firmware... it didn't fix it

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
You are mixing different topics:

Encryption is working. It is breaking, if you change the unlocked bl from 5.x to 9.x. For details read (not blindly flash): https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164. If you want to relock the bl, it's mandatory to relock BEFORE updating tne bl, of course. If you boot your bl 5.x encrypted data partition with an unlocked 9.x updated bl once, your encryption is broken and a reformat is mandatory, as explained in tbe mentioned posting:

If you've updated to 9.x bl and expirience selinux is permissive and flashing the 5.x bl again, you need to start from scratch. In doubt (e.g. flashed different fws together with different gapps and magisk can create a chaotic status) use an unbrick tool.

If you update the fw - especially if updating the bl as part of fw) - order is very important (as well as for changing bl's status). Rebboting is absolutly mandatory before formating if you've decided to update the bl in an unlocked state.
[OnePlus 3 & 3T Cross Device Development] generalprobe:
Thank You for your reply. Sorry that I respond so late, but I wanted to wait till I got the battery replaced by Oneplus.

Sadly this did not help much. Maybe a few hours ...

I will back my stuff up again and go with a fresh installation for testing purposes.
[OnePlus 3 & 3T Cross Device Development] Oswald Boelcke:
[MENTION=7364990]slev!n[/MENTION] [MENTION=7134312]knpk13[/MENTION] [MENTION=4405529]nvertigo67[/MENTION] [MENTION=5616867]150208[/MENTION] [MENTION=4405529]nvertigo67[/MENTION]

I just want to let you know that I've deleted a few of your posts regarding the latest "balck screen" discussion, and I apologise for that. Please continue/follow the discussion here: https://xdaforums.com/oneplus-3/help/emmc-error-suddenly-black-screen-t4075449/

Initially, I intended to move your post to that thread but I realised it wouldn't work due to the timestamps as [MENTION=7364990]slev!n[/MENTION] had created the new thread after his post here.

EDIT: I played a bit, and all of your posts have now been moved to the thread I've linked above i.e. nothing of your valuable contributions got lost.
[OnePlus 3 & 3T Cross Device Development] unimke:
Hi everyone,

Anyone know why this is happening?
[OnePlus 3 & 3T Cross Device Development] unimke:
The negative storage that is...
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
See your vendor patch level, still questions?

Cheers

Kurt
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
So yes the OP3/3T are in for a treat! [emoji16]

https://lineageos.org/Changelog-24/
[OnePlus 3 & 3T Cross Device Development] RKS96:
Will there still be los 16 builds? I would like to move to 17 but op3t is my only and main phone.
[OnePlus 3 & 3T Cross Device Development] :
According to https://github.com/LineageOS/hudson...d2c4b1cfb37a02862f01157/lineage-build-targets 16.0 is completely droped for oneplus3.

I'm planing to continue nlos 16.0 builds: https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
hello everybody.

i was happy to receive lineage os 17.1,AMAZING.

THANK YOU.

a small question please:

i read the lineage wiki on the subject,that 3party root solutions can be used,and looked for an answer here on this device.......

i can use magisk without a problem right?:confused:

i used to have magisk on twrp

i am asking if someone tried magisk on linage os 17.1 with lineage recovery?

i saw that the recovery is different and my device already tripped in the transition.....but it was probably my mistake.....

i am happy with the upgrade no matter the answer

TNX:)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Go to the official LOS17.1 thread for OnePlus 3/3T and you will find the answers to your questions ... Hope so ... ;)

https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-17-0-oneplus-3-3t-t3990061

Alternatives to stay with LOS 16:

- Build for yourself LOS 16 ... https://wiki.lineageos.org/devices/oneplus3/build

- [MENTION=4244522]pitrus-[/MENTION]'s builds ... https://lineageos.wickenberg.nu/oneplus3/

- NLOS 16 ... https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
i will look it up thank you very much.

:)
[OnePlus 3 & 3T Cross Device Development] ZeroVirus:
how to solve this?
[OnePlus 3 & 3T Cross Device Development] :
Fix your selinux policy. If you'd have put the build log in an adequate manner, I'd point you to the exact line. It's about sysfs_fps_attr. It seems you've added a rule with that object, which isn't defined. Look at https://github.com/LineageOS/androi...e-16.0/sepolicy/hal_fingerprint_default.te#L6 and send a link to your (changed) repo.

Before you ask:

brunch oneplus3 2>&1 | tee brunch.log
[OnePlus 3 & 3T Cross Device Development] :
https://www.reddit.com/r/LineageOS/comments/g325ex/how_to_use_quickreader_in_snap/

I've also asked on the los irc channel (via discord) and got - surprise - no answer.

I'm trying to solve this since 18 months. I'm not only completely clueless what's going wrong (it's definetly compiled into Snap), but really sad no los dev including the device maintainer has ever answred. Out of helplessness, desperation, frustation and anger I've done this lately: https://review.lineageos.org/c/LineageOS/android_packages_apps_Snap/+/272554 This was bad manner and I know better - I apologize for that. Sorry, Micheal!

Since I don't know if this is a really a bug, I havent created an issue on gitlab.

Please help me: if you have hands on another los (16 or 17) running device with the new Snap ui, check for quickReader. If you have access to one of the los devs, ask her or him. If you know of any other resource, that can help solving this mystery... Please help... Thank you in advance!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I'm aware of that and I don't understand it either... and I read Michael's not very pleasant answer... but expected.

About "my" devices on LOS 16:

- qR on a3xelte and a5xelte

- no qR on a5y17lte and mako
[OnePlus 3 & 3T Cross Device Development] :
Don't blame Micheal - blame me. He is right! It was a "what the heck should quickreader do harmfull, when it's just not there"-type reaction; and it wasn't ok.

Will comparr the device trees the next days. Thanx.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI, qR on OnePlus 5T (official LOS 16.0) .... !
[OnePlus 3 & 3T Cross Device Development] pat_kylie:
Anyone with problem of casting with Lineage 16.0 ? It just not responding.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
https://status.lineageos.org/issues/5eae596b4a0ebd114676545f
[OnePlus 3 & 3T Cross Device Development] !ndeXpl!cat!on:
various issues around audio

hello everyone, im currently running a one plus 3 with LOS 16 (march 25th build) and twrp 3.3.1-1 recovery,

im plagued by various issues around audio for quite some time now.

-plugging out headphones or disconnecting from bluetooth speakers doesnt stop playback. the playback just continues from internal speaker

-when music is paused for a while, the eleven player seems to crash in the background, making the widget not able to start playback again, even opening the player directly sometimes doesnt help. i have to kill the app to get it working again.

i can force the behavior by opening the app stop playback and then kill the app by the running app view, the widget isnt able to start playback again.

-i asume this is more a problem with my car audio but when having bluetooth hd audio enabled, the initial connection with my car doesnt produce output, ive got to either disable and enable hd audio again or reconnecting.

i have tried:

-cleaninstall of LOS16

-clearing cache of eleven app

-clearing dalvik-/cache in recovery

-LOS17

im out of ideas what i could do and hope i can get some help here

logcat here: https://paste.gg/p/anonymous/17ff7889d88b48109081587020f676eb

which hopefully include the necessary data for point 1 and 2.

around 22:02 i plugged the the headphones in and out, and killed the app rendering the widget not able to start playback again
[OnePlus 3 & 3T Cross Device Development] :
Thanx for your posting! After seeing so many moronic postings without versions, detailed description nor logs, this posting really stands out. It's a pleasure to read!

First of all: official los 16 isn't build anymore. Currently I know of two still maintained and updated unofficial los 16 builds:

https://xdaforums.com/oneplus-3/one...m-hardened-lineageos-16-0-oneplus-3t-t4034869

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405

I highly recommend using one of these.

If you want current fixes and/or current security patches it's mamdatory to use one of this builds - official los 16 is still maintained source code wise (https://review.lineageos.org/q/branch:%5E.*lineage-16.0.* ), but op3/t has moved to 17.1 and no new los 16 official builds profiting from current commits are done.

This is a well known one. The fix is a build including https://review.lineageos.org/c/LineageOS/android_packages_apps_Eleven/+/268138 . I know for sure it's included in nlos. If it's not included in the hardened los 16 build, I'm pretty sure [MENTION=7929484]MSe1969[/MENTION] is open towards including it.

I've never used the widgets of eleven (I'm using mostly off screen gestures or the notification) and need some days to investigate. Maybe related to battery optimization.

Maybe you are right. The bt implementations out in the wild disagree on sbc hd widely and the car's implementations arn't the most up to date bt sinks...

What's always worth a try is deleting AudioFX when audio issues show up, though AudioFX should be fixed since quite some time.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
It is already included in my build; I have - due to my other car BT issue with Eleven (song title not being displayed) also included further 17.1 commits (there is an ongoing attempt to rework Eleven), but that didn't help for me - Besides, the Eleven from my build works fine. I meanwhile use VLC and all fine, given up on fixing Eleven/BT.
[OnePlus 3 & 3T Cross Device Development] !ndeXpl!cat!on:
thank you very much for the quick response

as a softwaredev(nothing android related though) myself, i know of the struggle having to deal with bugreports without any details. i try do as much research and be as cooperative as possible before/while filing any reports.

i am aware of it, but i usually give new api versions a bit of time before going with it as my daily driver. also as mentioned already, this problem is present for some time now.

i read that audiofx was the cause for some audiorelated issues some time ago, and that it was fixed in the meantime, so i didnt gave it much thought except tryign it with disabled equilzersettings.

i gave it a go now nonetheless.

disabled audiofx via adb shell pm disable-user --user 0 org.lineageos.audiofx

didnt help though

in the meantime i also did a cleaninstall of the hardened LOS build

https://xdaforums.com/oneplus-3/one...m-hardened-lineageos-16-0-oneplus-3t-t4034869

the problem of the continuing playing music after disconnecting headphones is gone. this was my biggest problem and im happy that it works accordingly now. thank you very much [MENTION=4405529]nvertigo67[/MENTION] & [MENTION=7929484]MSe1969[/MENTION]

sadly, the problem with the widget persists.

i had disabled the gesture for playing/pausing music because i sometimes activated it accidently.

after trying it with gestures i can say that when the widget doesnt work, the gestures do still work. seems i will have to stick with it for a while.

EDIT: noticing https://review.lineageos.org/c/LineageOS/android_packages_apps_Eleven/+/268249 was already merged april 17th in the op3 build of LOS 17. the changelog page of LOS lists that commit for the earliest build of LOS17

hmm i know of the outage of the buildserver and that some recent builds have been deleted, if older builds werent deleted as well i should have had a build that had that commit included, when i tried LOS 17...
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=3157481]!ndeXpl!cat!on[/MENTION]:

Fpr the Eleven widget issue: did you try to disable battery optimization for eleven? Since I've disabled it, I can't reproduce the issue any more - even after the eleven notification has gone.
[OnePlus 3 & 3T Cross Device Development] !ndeXpl!cat!on:
can confirm, on a quick testing this seems to be the solution, will test over the next days and will inform you if the issue still appears under different circumstances.

thank you very much again
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
phone shuts down and empty over night

Hello,

I'm using the last official build LOS 16.1 from april.

Since 3 days (or nights) I've a strange issue:

I set up an alarm clock for the morning, and switch the phone to airplane mode.

In the morning, the phone is empty. Phone just buzzers, as it tries to boot for the clock.. Pluging in the cable: "Battery is empty, please charge".

It's really total empty. And it's not because of a drain from the battery, I attached the battery statistic. It's just like a "hard cut" and baam: phone off & empty

The battery level in the evening wasn't that low: 40%, 25% and 75%

I din't change anything on the software - only play store updates, as they're installed automatically.

Maybe a g-services update could cause it?

I've no clue why it's happening, does anybody else have this issue?

Edit: I also described it (in German) in the OP forum: https://forums.oneplus.com/threads/oneplus-one-schaltet-sich-von-alleine-aus.283295/#post-21633109

Another user also reported that problem this morning...

It seems it only happens with an activated clock?

EDIT: I switched to LOS 17.1 and it disappeared. Cannot say what was the reason for this and I hope it'll never appear again...
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Hi - is there anywhere I can still access these builds? I'm running 20200325 but want to know if there are any more recent nightlies on 16.0.
[OnePlus 3 & 3T Cross Device Development] :
As you can see in https://github.com/LineageOS/hudson/blob/master/lineage-build-targets 16.0 isn't build anymore for oneplus3.

You may want to have a look at

https://xdaforums.com/oneplus-3/one...m-hardened-lineageos-16-0-oneplus-3t-t4034869 (by [MENTION=7929484]MSe1969[/MENTION] ) or

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=4244522]pitrus-[/MENTION] is still hosting Los 16 and 17 builds: https://lineageos.wickenberg.nu/oneplus3
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Ah that's awesome - do you know if these are just built straight from the source or if there's anything else that's touched up on them?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
As far as I know they are straight from sources.
[OnePlus 3 & 3T Cross Device Development] getzze:
@dmukhin

Sorry to pull back this old issue, but I have this problem with a 3T and LOS18.1 (screen sometimes doesn't switch on when pressing power button).

Can you explain in more details what you did to solve it so it can be adapted to los18.1 ?

Do you have to build LOS from source to solve it?

Thanks a lot
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I'll assume you have abandoned the custom ROM scene for some time now or just read an old guide. SuperSU has been dead for a while and not even developed by its founder. Magisk is the boss of rooting now and is currently being actively developer for latest Android OS versions. Latest version of magisk is 18.0.
[OnePlus 3 & 3T Cross Device Development] 666biker:
magisk works fine, thanks
[OnePlus 3 & 3T Cross Device Development] fashion_live:
i have installed this rom but PC does not recognize the phone. Why?

RESOLVED
[OnePlus 3 & 3T Cross Device Development] 666biker:
just one small question. what about Tasker and Mobile Data toggling? ToggleData not works in LineageOS 16, is something which works in Tasker and LineageOS 16 for MobileData toggling (on/off)

EDIT: WORKS via Tasker/Net/MobileData on/off

Has this build issue to connect to hidden wifi SSID?

I am able to connect only when it is not hidden.
[OnePlus 3 & 3T Cross Device Development] fashion_live:
Google Map dont work.

Open app but i dont see the maps. Why?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Maybe if you would have taken logs, someone could tell you the answer to they why. How the heck anybody is supposed to know why it doesn't open for you?
[OnePlus 3 & 3T Cross Device Development] berliozz:
I want to update on this ROM from official Lineage 15.1, but have some questions:

1. Does TRUST works in this ROM

2. Does it ROM have OTA update or need to download last version manually?
[OnePlus 3 & 3T Cross Device Development] realtos:
your problem asshat

have some respect arrogant prick, search and keep your cold lame WHY **** to yourself. posting that everywhere is pathetic
[OnePlus 3 & 3T Cross Device Development] fashion_live:
It happens sometimes that the phone hangs for a few seconds, goes alone in the lock screen and after a few seconds return to work. This same problem happens to me with Havoc and Nitrogen Roms.

Does it happen to you?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
For everyone planning to come from official 15.1: you'd better wait for official 16.0 to avoid wipe data if it's a serious issue for you

And of course OTA is not a thing on my unofficial builds
[OnePlus 3 & 3T Cross Device Development] KUPOinyourWINDOW:
[MENTION=5091734]dianlujitao[/MENTION]

Could you please consider giving us the ability to theme quick settings light or dark independent of device theme? I love the cleanness of Lineage OS but ever since oreo I haven't been able to use it, because I have the dock on my home screen transparent black, and when I pull down the quick settings it's white and it clashes and doesn't look good. This is especially true with Android Pie.

It also happens in the settings app, if I pull down quick settings it's white on white.

Regardless, thanks for your hard work, this is really coming along well! I had extreme lag in YouTube with clean flash a few builds ago, tried out the newest build and that isn't a problem anymore. It's actually really smooth overall now.
[OnePlus 3 & 3T Cross Device Development] 666biker:
hello, has someone some practice advice, how to control ringer volume with volume keys like in Android 8.1?

Is there some easy way in Lineage OS 16 or in general? thanks
[OnePlus 3 & 3T Cross Device Development] helderfp:
[MENTION=5091734]dianlujitao[/MENTION] another bug report
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Please describe in detail or at least tell me what happened, instead of throw out a bugreport and be gone.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
No I can't, you should go to somewhere else for a feature request
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Navbar does not work when typing in split screen with aosp keyboard. As in it became a useless black bar.

No issues when using 3rd party keyboard (google pinyin)

Here's a log that's hopefully useful (no idea what I should look for…)
[OnePlus 3 & 3T Cross Device Development] helderfp:
Using the phone, and system automátic give a bug report, dont know wy.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Random crash? That's interesting
[OnePlus 3 & 3T Cross Device Development] knpk13:
[MENTION=4839377]helderfp[/MENTION]

I sometimes accidentally press the power and volume keys together and it triggers a bug report. I believe it's a key shortcut to create a report? Though I can't get it to trigger consistently on Pie for some reason. If that's the case, I think it's not a bug but just the report because of accidental keypresses.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Exactly there's a key combination for bugreport iirc
[OnePlus 3 & 3T Cross Device Development] abhibnl:
IMO, Oreo encryption to Pie ROM jjump won't be supported unless oneplus releases their Pie sources. I believe this should be added into the OP as well as flashing Pie right now, at least on all other Pie ROMs, requires a decrypted storage.
[OnePlus 3 & 3T Cross Device Development] bjo81:
10/11/18 works fine here. But https://nyyu.tk/jenkins/job/lineage16_oneplus3/ only use the merged sources, not the sources from dianlujitao's own repo.
[OnePlus 3 & 3T Cross Device Development] atoyu:
+1
[OnePlus 3 & 3T Cross Device Development] caryle:
Not 4.x.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Decryption itself works, but some framework stuff crashes. will be fixed in the next build
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=5091734]dianlujitao[/MENTION] and all LOS devs

First a big thank you for bringing the taste of Pie to the OP3!:good:

According to the OP it's to early for me to smell the Pie , as I need and use my OP3 (my only device) as daily driver.

I'm fine atm with LOS15.1, runs smooth and stable .

I will follow this thread and will switch to LOS16 when it becomes more stable and encryption working.

First thing. when I received my OP3 in June 2016 was flashing CM13, then CM14 and LOS15.1,

never used OOS.
[OnePlus 3 & 3T Cross Device Development] bjo81:
I'm using LOS 16 (the Jenkins builds) as a daily driver and they work fine. You could do a twrp backup and try it.
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=5437807]bjo81[/MENTION] Encryption working?
[OnePlus 3 & 3T Cross Device Development] Playa82:
Huh ? dianlujitao's builds are on jenkins already ?
[OnePlus 3 & 3T Cross Device Development] bjo81:
The builds on https://nyyu.tk/builds are built by jenkins from the usual LOS repos, and dianlujitao also maintains the OP3 in these repos. You can see this if you search for oneplus3 on https://www.lineageoslog.com/16.0
[OnePlus 3 & 3T Cross Device Development] :
Look at the post 3 before yours, it's already answered by the dev
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=2044343]accuphase[/MENTION]

I know. but [MENTION=5437807]bjo81[/MENTION] suggested to test the Jenkins builds as daily driver - maybe he didn't noticed that I will switch to LOS16 when encryption works!
[OnePlus 3 & 3T Cross Device Development] realtos:
dont change his reply, still has been answered all over the place about encryption.
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=9554680]realtos[/MENTION]. I haven't. changed any reply - I wrote clearly in my first post that I will switch to. LOS16 WHEN ENCRYPTION WORKS....:confused:
[OnePlus 3 & 3T Cross Device Development] mk_1996:
encryption works in pie. just not from oreo to pie. because pie has a software based encryption. only sources from oneplus would fix this which should be coming soon as they're working on op3 on a private branch(as seen on github)
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=5437807]bjo81[/MENTION] [MENTION=2044343]accuphase[/MENTION] [MENTION=9554680]realtos[/MENTION] [MENTION=7554367]mk_1996[/MENTION]

could you all please stop this annoying discussion 'bout LOS16 encryption?

As I stated in my first reply in this thread I'm still fine with LOS15.1 atm, I'm aware that the sources from OnePlus are needed to fix the encryption and will switch to LOS16 when it becomes more stable with encryption working - I didn't started this discussion......
[OnePlus 3 & 3T Cross Device Development] atoyu:
new build up

https://androidfilehost.com/?fid=11410963190603852073