yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Interesting! I have no clue why, but on my own (userdebug, of course!) builds, disabling as well as enabling persists a reboot...

breakfast oneplus3
including vendor/lineage/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
LINEAGE_VERSION=16.0-20191212_162104-release-oneplus3t
TARGET_PRODUCT=lineage_oneplus3
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=kryo
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.2-nvertigo-efi-x86_64-Gentoo/Linux
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ3A.190801.002
OUT_DIR=/mnt/export/data/src/los16/out
PRODUCT_SOONG_NAMESPACES= hardware/qcom/audio-caf/msm8996 hardware/qcom/display-caf/msm8996 hardware/qcom/media-caf/msm8996
============================================
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I can confirm, it's months that this happens...

Apparently this does not happen to everyone with LOS
[OnePlus 3 & 3T Cross Device Development] RKS96:
Check link, 2nd answer! Everything is explained here why ADB gets reenabled and why user type can't be used! I just wanted to know if it is possible to modify system files with root to disable this option after flashing. TNX
[OnePlus 3 & 3T Cross Device Development] :
After testing a fourth time, this made me mad. After some more digging, I found:

The difference is not the BUILD_VARIANT or something with the builds itself, but magisk. magisk overwrites ro.debuggable=1 with resetprop to ro.debuggable=0, as you ca see here:

adb shell su -c grep -e ro.secure -e ro.debuggable -e ro.kernel.android.checkjni -e adb default.prop
ro.secure=1
ro.debuggable=1
ro.adb.secure=1

but

for i in ro.adb.secure ro.debuggable ro.secure ; do echo -n "$i=" && adb shell getprop $i; done
ro.adb.secure=1
ro.debuggable=0
ro.secure=1

What makes Android debug persisting reboots on my setup is ro.debuggable=0.

ro.debuggable is set in /default.prop, which is part of the ramdisk in bootimage. Since resetprop requires root, that's no option for you. To change ro.debuggable to 0 you just need to make yoirself a zip, which dumps the bootimage from it's partition, unpack the bootimage, unpack the rootfs cpio archive (contained in unpacked bootimage), change ro.debuggable to 0 in default.prop. repack the cpio rootfs archive, repack the bootimage with the modified rootfs cpio archive, resign the repacked bootimage with aosp verity keys and finally reflash the new bootimage.

As a starting point for unpack/modify/repack/resign bootimage is AnyKernel3 from [MENTION=4544860]osm0sis[/MENTION]: https://xdaforums.com/showthread.php?t=2670512. You just want to modify rootfs (called ramdisk in tne AnyKernel3 thread) only, instead of replacing the kernel and modify the ramdisk. AnyKernel3 comes with a teplate, which considers signing.

This way you can modify ro.debuggable without root access.
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
What i have to do to update to a newer build when iam already on LOS 16.0?

Last Time i got stucked at bootloop and cant boot to system anymore.
[OnePlus 3 & 3T Cross Device Development] locateiowa:
The updater app has had issues on the OnePlus 3/t for quite a while. It's safer to update by downloading the zip from the LineageOS website directly, booting into TWRP, and flashing it yourself from there. :)
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Weird, I've always used the updater and I haven't had any issues, worked flawlessly.
[OnePlus 3 & 3T Cross Device Development] locateiowa:
From what I've read, it might depend on the version of TWRP you're using. Here's a link to another user's experiences using the OTA updater with different TWRP versions: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79632279#post79632279

I can't speak from personal experience here, since I haven't done any experimenting myself, but it seems like this could be the reason why you haven't run into any issues with the updater app.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Is your phone unencrypted?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Yup, I update every other day with the updater and no issues so far.

Had the latest TWRP until a couple of days ago, not flashed the last one yet, so I've not tested it with that one yet.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
F2fs or ext4?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Ext4, I don't see many advantages to use f2fs, ext4 is more mature and reliable to me.

You think the file system may be why the updater is a problem for some?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's a possibility.
[OnePlus 3 & 3T Cross Device Development] :
This is the first report of failed automatic flashing with Updater apk on an unencrypted device. So far this(?) bug has randomly hit setups with encryption and boot passphrase set.

EDIT:

This is definetly somethimg completely new. The unbootable system after update on encrypted and boot passphrase protected systems is due to addon.d scripts referencing something under /data, which is not accessible on such systems when automatic flashing is used.

The fix for encrypeted and boot passphrase protected setups is still not merged: https://gerrit.twrp.me/c/android_bootable_recovery/+/1664

Maybe it's the same bug, which just hasn't been reported for unencrypted devices, yet - or it's a new issue. In deed it's something different - see above.

The real problem in hunting this (no matter if the same or something new) down is getting debug info. I've no idea, how to get a recovery log from a failing automatic flashing twrp session. That this bug shows up randomly, doesn't make debugging easier...

For now the only workaround I can think of, is using Updater app only for downloading the updated zip, but avoid the automatic flashing and apply the update manually.

If anybody has an idea how to debug this without a log from the failed automatic flashing in twrp...
[OnePlus 3 & 3T Cross Device Development] RKS96:
Hi. Does anyone know how quickly change between performance profiles under Settings>Battery>Battery saver and Performance. Quick toggle or widget? TNX
[OnePlus 3 & 3T Cross Device Development] capz21:
What Google Camera are people using with this ROM? :p

And what firmware is recommended to use? Just flash latest 9.0.6? :laugh:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Read the OP
[OnePlus 3 & 3T Cross Device Development] capz21:
Ok... just flash latest firmware (data is fine, have backed up). Thank you.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You do know that firmware doesn't touch the data partition or system partition and that it's never included in any backups, right?
[OnePlus 3 & 3T Cross Device Development] capz21:
Isn’t there that data corruption bug or whatever?
[OnePlus 3 & 3T Cross Device Development] :
Yep. It's sepolicy. Set to permissive, and Snap works.

12-26 09:29:03.129 12202 12202 I .lineageos.snap: type=1400 audit(0.0:13): avc: denied { execute } for path="/data/user_de/0/org.lineageos.snap/code_cache/com.android.renderscript.cache/librs.yuvtorgb.so" dev="dm-0" ino=472848 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=file permissive=1

Maybe more. I've to step back from Magisk 18 to 17.1. 18 disables all noaudit rules, which makes you seeing ALL denials...

This should help:

allow platform_app app_data_file:file execute;

For now put it in device/oneplus/oneplus3/sepolicy/plattform_app.te. I guess it will finally go to device/lineage/sepolicy.

Apropos Snap: does anybody know how to use the buildin qr reader with the new Snap ui?

EDIT:
[MENTION=5091734]dianlujitao[/MENTION]:

I don't think it's op3/t specific, but we need this in order to make Snap starting:

https://github.com/nvertigo/android...mmit/1c6a908b4b17288dba164b98e50df077b8066c30
[OnePlus 3 & 3T Cross Device Development] 666biker:
Hello, how stable is this unofficial LineageOS 16 build please? I am on latest LineageOS 15.1 and want to update to android 9.

all fine for daily use? battery life as well? Thanks
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Go and Update. You will be surpriced how stable and battery friendly it is.

Make a clean Install.
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
+1

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] 666biker:
enough to wipe system partition and user data will remain?
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
Its better to wipe Data and system.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] helderfp:
[MENTION=5091734]dianlujitao[/MENTION] , here a bug report
[OnePlus 3 & 3T Cross Device Development] xdaxdaxda1:
Does other kernel work with lineage os

I was wondering if other kernels like xtended, Hdk, fk would work with lineage os as it includes awesome performance profiles options , does those profiles work like it works with stock lineage os kernel. Does kernel manager like kernel adiutor , fk, ex work on top LOS profiles? What steps to take care of while flashing custom kernels.

BTW my OnePlus 3 working superbly with Los 22/12/18 , I didn't face any bugs except during setting up device (it take 2 Networks/attempts to setup the device.) Why so stable?
[OnePlus 3 & 3T Cross Device Development] namanjr:
Not very stable since it's a beta with frequent updates but there's no noticeable bugs or battery drain vs LineageOS 15.1. Only thing is LineageOS 16 doesn't have all the features of LineageOS 15.1 yet since they are still porting them. I've used it as a daily driver since selinux was set to enforcing.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Lol! It's been a daily driver for many people since it first came out. I've not had any FCs or reboots on it at all.

Battery life is excellent. I find it just as good as stock OOS.
[OnePlus 3 & 3T Cross Device Development] mbroeders:
Agreed, amazing ROM and great as a daily driver!

One question: although my system language is set as Dutch, Google maps is is showing in English. Is this a bug or is there a language option I'm missing?
[OnePlus 3 & 3T Cross Device Development] :
I think this is a misunderstanding. Classical staged software development has been something like this: alpha->beta->(optional: release candidate)->release. In short that has meant something like: alpha - the idea, proof of concept, first running versions; beta - adding features, let non-devs test, tune ux; release candidate - feature freeze, iron out last (if there are any left at all) issues (mostly visual or cosmethical); release - the version that get shipped to customers.

In this cycle it's clear, that "stability" is not necessarily related to one of this stages: a software could be very stable on beta, but there are features to add till rc. Or a beta stage sw was stable, but with adding a feature it got more unstable again, or, or, or...

Of course: the probability of stability was highr on release then on beta, but there was never something like: beta = unstable; release = stable.

Some time ago some people started a staging pattern alpha-beta-stable, which seems to be no problem. But there is a problem: reception. People start thinking this implies: if we have a stable stage, all other stages have to be unstable by definition...

According to stability (sw not crashing) all of [MENTION=5091734]dianlujitao[/MENTION]'s beta builds are much more stable then i.e. the first shipped releases of win nt or win 3.

Bottom line: the (beta) builds of LOS16 are stable enough for a daily driver - since everybody has differnt demands, one or another key-feature may be missing at the current stage.
[OnePlus 3 & 3T Cross Device Development] sembraottobre:
reply please...
[OnePlus 3 & 3T Cross Device Development] namanjr:
Stability in software means the code is very well tested by a wide range of users covering all use cases. Generally all new changes to code will go though the same standard if they aren't just simple fixes. Feature X could work for 90% of users but cause a crash or worse for 10% who had a certain config difference. Look at the Windows 10 data deletion bug that only affected people who updated right away. People on Windows 10 LTSB were completely unaffected.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Chromecasting works fine, can't answer for Intel Miracast as I don't use it because it's not as refined as Chromecasting, more laggy and worse picture quality generally at least using the Miracast reciever in my LG Smart-TV.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
With these picked

https://review.lineageos.org/q/topic:"pie-qcom-wfd"+(status:open OR status:merged)

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/237182i

I can stream to a win10 setup as well as to a ms widi adapter.

The widi adapter is found within 20 seconds - the win10 streaming target needs up to 3 min to be found.

I can confirm the quality is not as good as streaming to a fire tv 2 box (chromecast).
[OnePlus 3 & 3T Cross Device Development] suyashlimaye:
Is the network speed meter broken in latest build?
[OnePlus 3 & 3T Cross Device Development] 666biker:
hello it is somehow possible to get SuperSU working on this latest build?

I have installed SuperSU 2.82 latest, and seems not works for me.

Thanks.
[OnePlus 3 & 3T Cross Device Development] knpk13:
SuperSU has essentially been abandoned from what I last saw of it. Chainfire sold it to CCMT and I haven't seen any updates from them since then, so it probably doesn't even support Pie. You're probably better off using Magisk.
[OnePlus 3 & 3T Cross Device Development] :
True. Another thought: would one like to use a closed source root solution not or free and open source software? Though I really liked SuperSU and have bought it to support [MENTION=631273]Chainfire[/MENTION], the decission was one of the easier... ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Nope, no corruption bug.. There's an issue with having an encrypted data partition with an unlocked bootloader and going from OOS 5x to 9x firmware.

If you're in that situation, then you either format the data partition to remove the encryption or use the modded firmware from https://xdaforums.com/showthread.php?p=79758055
[OnePlus 3 & 3T Cross Device Development] RKS96:
I found an app which would do exactly what I want, but it doesn't work on LOS 16. RLY nobody knows of similar solutions? Or maybe it can be implemented in LOS by developers? TNX
[OnePlus 3 & 3T Cross Device Development] ciarpame:
My safe choice is "Google Camera 5.x, Arnova's v8.3b1". It never crashes, white balance works, no weird errors.

I had several issues with 6.x versions. Before writing this message I decided to try again a 6.x camera, so I installed "Tolyan009: 6.2.030_TlnNeun_v.0.6d.apk" porting. In 20 minutes I took several shoots but after a while I got this message "Can't take photo: Not enough storage left on this device". After a forced stop camera works again but it means that 6.x it's still less reliable than 5.x, at least for me.

Download page: https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552
[OnePlus 3 & 3T Cross Device Development] TarrasQ:
Have a similar issue for a while now. about 50% of the time pressing power button will cause the screen to display/wake correctly, other times, the button backlights just light up, nothing on the display, just have to press power button to lock phone again, then press it once more to attempt to wake it up correctly.

Video showing it happen.. youtu.be/9lfo2EPSrwg (dont have enough posts to direct link)

It is a replacement screen, so maybe that is an issue? any other way to diagnose the problem?

It does also seem that despite nothing comes on the screen, the screen s still responsive, tested by disabling the requirement to unlock the phone, press the power button to 'wake the phone' and pressing on the screen opened apps etc.. so when it did wake up correctly those apps had loaded.
[OnePlus 3 & 3T Cross Device Development] :
You havn't searched enough. Look at https://xdaforums.com/showpost.php?p=80480431&postcount=3349 fff.

[MENTION=5188739]dmukhin[/MENTION]: Did you make any progress on the flashable kernel patcher? If not: do you want to share a current kernel with the dtsi exchange?
[OnePlus 3 & 3T Cross Device Development] bendodge:
Warning! Flashed from 2019-12-18 to 2019-12-24 and I couldn't boot. The changes to Dalvik seem to have caused issues.

Storage encrypted. Bug report here: https://gitlab.com/LineageOS/issues/android/issues/1504

Edit: False alarm. This is a randomly-occurring issue with automatic updating on encrypted phones.
[OnePlus 3 & 3T Cross Device Development] anyone23:
My OP3 is working fine after upgrading from 2019-12-11 to 2019-12-24.

Edit: My phone is encrypted too.
[OnePlus 3 & 3T Cross Device Development] :
No issues on my side flashing the latest LineageOS. OnePlus 3, encrypted

Have you flashed via internal updater by any chance?
[OnePlus 3 & 3T Cross Device Development] :
This dalvik change https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/265495 isn't used for op3/t currently (needs adjustment in the device tree like: https://github.com/nvertigo/android...mmit/1c9b1f7dbe5652a07574449e3e4be0a0ea07726e ) and https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265496 doesn't seem to make any problems.

Looks more like an issue of your setup, which we can't know with no detailed information. From the pstore I'd guess some audio mod doesn't like your update procedure.
[OnePlus 3 & 3T Cross Device Development] bendodge:
Thanks for the responses.

I don't have any audio mods that I know of; just TWRP + Lineage. I may have to rebuild.
[OnePlus 3 & 3T Cross Device Development] :
If you build on your own this can have multiple causes. I've thought you mentioned you are using the nightlies.

Maybe it's your update routine (hit the automatic flashing issue?), but without information, this is pointless guessing.
[OnePlus 3 & 3T Cross Device Development] bendodge:
Poor choice of terminology; by rebuild, I meant backup and wipe everything, install fresh, and restore data.

I'm installing nightlies via the built-in updater. When trying to rescue myself, I flashed the zips in /data/lineageos_updates via TWRP. I started months ago by clean flashing an official nightly via TWRP.
[OnePlus 3 & 3T Cross Device Development] :
This doesn't make sense: clean flashing (wiping data, systen and caches, followed by flashing rom and gapps) helps, if the current setup has issues. The curtent setup is stored in data. If you clean flash and restore data, it's the very same as dirty flashing.

In other words: if your current setup is the culprit, restoring this setup can't be the solution.

Restore your backup and manually update the rom.

You hit the automatic flashing issue. Search the thread and you'll find this shows up randomly on encrypted setups and renders them unbootable. Workaround: manually flash updates.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
I did the same, here it worked.
[OnePlus 3 & 3T Cross Device Development] bendodge:
Thank you; this worked.
[OnePlus 3 & 3T Cross Device Development] fhloston:
Rescueparty

I just did the following:

- Boot to recovery

- install image twrp-3.3.1-1-oneplus3.img, reboot recovery

- install Stable9.0.6 Firmware+Modem_OnePlus3.zip, reboot recovery

- install lineage-16.0-20200102-nightly-oneplus3-signed.zip, wipe dalvik/cache, reboot system

Result:

Rescueparty, console-ramoops and pmsg-ramoops-0 attached

Previous state of device:

lineage-16 from november, 9.0.5 firmware, opengapps nano, encrypted
[OnePlus 3 & 3T Cross Device Development] :
Which fw version did you start the fw update from?
[OnePlus 3 & 3T Cross Device Development] Adrianer:
I have installed the build from January, 2nd 2020 on my 3T, but for some reason the "Android security patch level" string is still "August 1, 2019":

My previous installed builds had also that patch level, which is quite strange as as far as I can see, the build from 24.12.2019 should already have the patch level string from December 2019: https://download.lineageos.org/oneplus3/changes/ and https://review.lineageos.org/265279

How can that be?

EDIT:

Found it: I had a Magisk module installed that seems to have overridden this...
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Do you have a Magisk module or a script for passing Safetynet?

Because these tweaks will set the patch level in Settings to august.

Otherwise, you can check the real patch state with the command "adb shell getprop ro.build.version.security_patch" (or direct in a terminal app in LOS - then without "adb shell" of course)

or just look into the build.prop in /system
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
It's correct, Dec securty patch is installed! that 's a trick allowing you to bypass safetynet ?
[OnePlus 3 & 3T Cross Device Development] :
Dalvik heap configuration

[MENTION=5091734]dianlujitao[/MENTION]:

This has been introduced 2 weeks ago: https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/265495 I'm using this config in my builds since then. I see neither any drawbacks nor any advantages.

That being said, I still think it's a good idea to use the los global config instead of a per device config. Do you want to have this https://github.com/nvertigo/android...mmit/1c9b1f7dbe5652a07574449e3e4be0a0ea07726e pushed, or do you want to keep the current (oos) config?
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
Did anybody get the DKB TAN App running on a current Build?
[OnePlus 3 & 3T Cross Device Development] :
Safetynet status? Play Protect status? Bootloader status? Error message of the app?
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
Safetynet passed

Play Protect ok

Bootloader locked

The App is closing instant and referring to the DKB Website

On my Nexus 5 with Android 7 (also Lineage) and without Magisk its working.
[OnePlus 3 & 3T Cross Device Development] :
Can you get a log from the crash, please? (adb logcat)
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
ofc, upload and I'll merge
[OnePlus 3 & 3T Cross Device Development] MarkMRL:
I found your post while googling for this issue. I have LOS 16.0 on my OP3. Does the file from your attachment still work? I haven't enabled root but if anyone confirms that it works I will add it because with no ogg vorbis support I can't play half of my library outside of VLC.
[OnePlus 3 & 3T Cross Device Development] :
Comment out the offloading for vorbis like this: https://github.com/nvertigo/android...mmit/e900e945661f923921bfdd883e5636d0670a86b2

Or use this file: https://raw.githubusercontent.com/n...los-16.0/audio/audio_policy_configuration.xml

If you decide to replace the file instaead of jist editing it, check permissions and selinux context after replacing.
[OnePlus 3 & 3T Cross Device Development] dmukhin:
Sorry for silence. Kernel with fixed device tree, it may help for some OnePlus 3T screens replaced. For me it cured nearly all still black screen issues. Actual problem is in the combination of on, off and color profile commands. Plus panel driver itself. Since most of replacement screens are some garbage or sample parts from factories it is hard to expect stable results
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
Sorry for the late response.