yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
You need to mount system, before accessing it - after copying, don't forget to check the unix permissions and resetting the sepolicy context. From the twrp terminal (after mounting system from twrp's mount menu):

cp -v /sdcard/Download/audio_policy_configuration.xml /system/vendor/etc/
chmod 0644 /system/vendor/etc/audio_policy_configuration.xml
restorecon /system/vendor/etc/audio_policy_configuration.xml

The xml is the same as the los' shipped with the abandoned commit I've linked in my last post: it's fixing vorbis. The same "trick" on wmv offloading doesn't work. mp4 containers will work if the encoding codec is supported. If the codec isn't supported, it can't be played - no matter in which file container it comes; this happens mostly with non-free codecs (aka codecs requirering a license fee.

Since you are rooted, you can do that in the running rom with a rooted adb shell - don't forget to remount system rw.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Well... sweat for me, too! After updating to lineage-16.0-20190528-nightly-oneplus3, my op3t automatically reboots to twrp (twrp-3.3.1-0).

Now I'll try to install an older LOS version.

Edit: Flashing lineage-16.0-20190523-nightly-oneplus3 did not help. The phone still reboots to twrp. :(

Edit: Downgrading to twrp-3.2.3-10 and flashing lineage-16.0-20190523-nightly-oneplus3 did not help. Preparing for a wipe. :(
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Update of my son's device this morning (OP3T + latest build + latest TWRP + Lineage Downloader app) .. No sweat (su = LOS addon)

+ https://xdaforums.com/showpost.php?p=79619065&postcount=2103 .... No sweat (su = LOS addon)

+ https://xdaforums.com/showpost.php?p=79619368&postcount=2104 ... No sweat (su ?)

Question 1: do you use Magisk ?

Question 2: wipe cache/dalvik and system + flash build+gapps+su (if needed) ... sweat or no sweat ?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No Magisk or something like that for me!

Wiping caches + system, flashing LOS, gapps and su did help - no more sweat.

Anyways, it's still a dumb situation if a system update may crash your system. :(

Good luck for anybody who wants to try out the new version.

BUT BE WARNED!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
My last question : ext4 or f2fs for data and cache ?
[OnePlus 3 & 3T Cross Device Development] :
rescue party on update

I would really like to see to see a proper issue report for the "rescue party on update"-issue, including at least:

detailed description of the prior to update setup, including at least:

detailed fs setup for userdata and cache

versions of twrp, rom, su package (if used) and gapps

version of all mods (including Magisk modules)

version of all bootimage or system altering packages, scripts or files (i.e. the changed xml file, I've posted for the vorbis issue)

version of installed (not active, but all installed!) substratum themes, is one of them active on update?

all non-standard default apps

the way the current setup was generated: i.e. clean flash, migration from 15.1 (if so, how?), restored backups (which and how?)

complete list of modded apps installed (i.e. gcam, opcam etc.), including exact version

exact description of all steps taken to update

recovery log of the update (only possible for non-autmatic reboot)

exact description of what happens on (failing) system boot: do you see the boot logo? Is the boot process reaching boot animation? Be aware boot logo and boot animation are different stages of the boot process! Do you reach the passphrase input for secured boot if enabled?

pstore of failed boot (important!!!)
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
ext4, both

1) ext4, both

2) Lineage-16.0-20190520 or some days earlier, latest official twrp, LineageOS su script, stock OpenGApps

3) none

4) none

5) none

6) AdAway, Blitzer.de, Boomerang, clever-tanken.de, ES File Explorer, F-Droid, Facebook, Firefox, Instagram, Jodel, Kik, Layout, FB Messenger, Note Everything, Snapchat, Springfield, Terminal Emulator, Torque Lite, WhatsApp, Wifi Analyzer

7) Migration from LOS 15.1, updated via LOS Updater, no restored backup

8) none / don't know what it is

9) Update downloaded with the default LOS updater, it autorebooted to twrp, twrp autoflashed and autorebooted

10) Can't deliver because of autoreboot. But I watched the process, I didn't see any "red" lines or abnormalities.

11) After the flashing process the phone rebooted, showed the bootlogo, then asked for passphrase for secured boot, accepted it, showed the bootlogo again, then vibrated like it does when I switch the phone on, booted to twrp and tried some "Recovery party" or something like that.

12) Can't deliver, don't know how and what it is.
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
Looks like the phone no longer goes by itself in to dark mode when battery gets under 15% (I think it was like this due to the battery saver).

At the beginning I thought it was cool but, no more, thanks! [emoji28]

It was very annoying especially if you were playing a game or watching a video, because it causes the system UI to restart and usually that was the reason of loosing the progress on many apps running in that moment.

I don't know if this was a known issue or if I was the only one affected but it's on the past now so I'm very grateful. Many thanks to the dev! [emoji1362][emoji1362]

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=8530490]Not-Aus[/MENTION]:

Thanx for the answer.

Without pstore from the failed boot everything is guessing.

Two points, which cought my eye: gapps package size (I always recommend pico or nano and 8nstalling the missing apps as user apps from playstore - installing all gapps as system apps replaces many system files with the strangest side effects) and migrating from <16.0 (some commits i.e. changing some paths to vendor while migrating were commited later then others, so they maybe wasn't there, when you migrated yoir setup). But withoit knowing the reason for the reboot after the failed boot, this all is guessing.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Same issue for [MENTION=2044343]accuphase[/MENTION] :

OnePlus 3, /data in ext4, fw5.0.8,

Encrypted with stock los 15.1 and stock twrp 3.2.3-0 months ago

Dirty update to los 16.0

Gapps nano

==> https://xdaforums.com/showpost.php?p=79618983&postcount=2100

==> https://xdaforums.com/showpost.php?p=79073090&postcount=1101

Common point: migration from 15.1
[OnePlus 3 & 3T Cross Device Development] :
Maybe.

[MENTION=2044343]accuphase[/MENTION] and [MENTION=9350973]All[/MENTION] suffering from incoplete boot: do you agree? Would you please put together all information the way [MENTION=8530490]Not-Aus[/MENTION] did, please? And most important: if the incomplete boot ends up with twrp's rescue party, save the content of /sys/fs/pstore.
[OnePlus 3 & 3T Cross Device Development] :
I'm really puzzled: flashed today's build manually with and in latest twrp 3.3.1-0 ... no sweat :)

I will test it tomorrow the other way round: flashing tomorrow's build via build-in ota updater and latest twrp ...
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
I got another clue to why I get booted into 'RescueParty'.

When I install using 'TWRP manager' (which automatically reboots and installs via TWRP) everything is fine.

During installation I get 'Unable to mount storage' as one of the first lines (in red) - but installation succeeds.

When I use the built in updater, I also get 'Unable to mount storage' - but it is immediately followed by 'Unable to mount data/media/TWRP/.twrps' - and installation continues but after reboot it fails and reboots to 'RescueParty'.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I feel like our knowledge level on the topic at hand is different enough to require a layer of customer service between us. But you're here, I'm here, and we're conversing, so I'll take the opportunity to learn if you're willing.

1) I moved to LOS16 from Sultan's (non official) LOS14 (via a clean flash). I remember LOS14's stock music player not having any trouble with my wmv files. Is that likely a change he made outside of the official stream?

2) Why would I need to remount system after I mounted it earlier?

3) can you check my understanding of this commands?

cp -v /sdcard/Download/audio_policy_configuration.xml /system/vendor/etc/

Copy -verbose from /download to /etc, correct? That makes sense.

chmod 0644 /system/vendor/etc/audio_policy_configuration.xml

Change file permissions, ok, makes sense.

restorecon /system/vendor/etc/audio_policy_configuration.xml

This command restores the SELinux security content for the file. Why is that lost in the process? Does that encrypt the file like the rest of the system?

4) Finally, will these changes persist after an update?
[OnePlus 3 & 3T Cross Device Development] legendavey:
Today's build includes the commit for an expanded volume panel that allows changing all streams - not just the media volume! ?

https://review.lineageos.org/244295
[OnePlus 3 & 3T Cross Device Development] BillGoss:
2. If you've already mounted the system and can access it, then you shouldn't need to mount it again.

3. SELinux is not related to encryption but controlling classes of permissions. The security context of files on the sdcard are different from those on the system partition. So, after copying the files you need to restore the appropriate security context, hence use restorecon.

The ls command with the -Z option (if available) will list the security context information for files.

Side note: file managers, such as Solid Explorer preserve the security context of the target when you copy a file over an existing one.

4. Flashing an update overwrites the system partition so you need to redo the changes. If you set up an addon script in /system/addon.d then a dirty flash can restore the changes, but a clean flash (wipes system) will always require the changes to be redone.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
op3: Rip ANT+

==> https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/245236

and perhaps coming soon (credit [MENTION=5091734]dianlujitao[/MENTION] ... Thanks for the job) :

==> https://review.lineageos.org/q/status:open+op3+dianlujitao
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=2911853]BillGoss[/MENTION]' answers are perfectly good, I'm just filling the gaps:

[MENTION=4800121]Sultanxda[/MENTION]'s 14.1 build has vorbis offloading disabled: https://github.com/kerneltoast/andr...mmit/6b2d84ec55c690bfed3f63771a7ae9e8127bdb6f

That's what I derivated the fix from (as already told, this doesn't work for any other codec then vorbis since 15.1).

You need to read the context more carefully:

The running rom mounts system ro (readonly), if you want to alter anything on the system partition (like copy a file) you need to mount system rw (readable and writable). Since system is in use, you need to remount system rw.

No.

Since nobody but you, the creator of the deleted jira ticket and me expirience this issue, I've thought there's no need for a flashable zip. If more users demanding this, I can make one. Or you look for a los based rom with this commit applied... ;)
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Or I just find a music player app.

Thanks a ton for explaining everything.

---------- Post added at 11:46 AM ---------- Previous post was at 11:34 AM ----------

Thanks for taking the time!

That wording is likely precise to someone familiar with the subject, but reads as ambiguous to me. Does "preserve the security context of the target" mean it maintains the security context of the file I've copied, or it converts the security context of the copied file to that of the destination directory?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
One copies source to target.

If the target already exists then Solid Explorer will retain/preserve the target's security context when it copies the source file over.

If the target doesn't already exist, the target will have the source's security context. In this last case one would still need to run restorecon.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION]

[MENTION=9708417]Eric_Lev[/MENTION]

'RescueParty' is back again when I'm flashing today's build via build-in OTA updater in combination with latest twrp. The twrp flashing process doesn't bring up any issue-messages, after 'successfully' flashing and rebooting into system start process: boot logo -> input encryption key -> successfully encrypting -> boot animation from LineageOS -> ... -> boot animation from LineageOS -> restart into twrp -> showing red 'rescue party' message, today's build deleted in /data/lineages_updates.

The only way to bring up my device up to live again, flashing back a nandroid backup :)

It seems the build-in ota updater has some incompatibilties with twrp versions higher than (incl.) 3.3.0-1 or vice versa. twrp 3.3.0-0 is the latest working combo with the ota-updater at least for me.

Btw. I've recognized the twrp versions 3.3.0-1 and 3.3.1-0 are around 3'ish mb larger than the versions before ...

After flashing back the working nandroid backup, booting successfully into system I've flashed MANUALLY in twrp 3.3.1-0 the latest LineageOS build -> successfully -> NO SWEAT AT ALL.

pstore files attached - hope it helps

Edit: corrected the 'boot animation' and 'boot logo' wordings, thx to [MENTION=4405529]nvertigo67[/MENTION] ;)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Test of build update from 0528 to 0529:

- via Lineage Downloader app (Play Store) : no sweat

- flash in recovery : no sweat

- via OTA Updater : no sweat

Clean flash of LOS 16 (i.e. I didn't migrate from < 16).

See my signature for my setup.
[OnePlus 3 & 3T Cross Device Development] :
Thanx.

It's important to get feedback of "anybody expiriencing this". "this" is a constantly failing ota update with twrp >=3.3.0-1. My fault, I'd be more precise.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I read this a while ago ...

"If you wonder if it's time for a clean flash, the answer is "yes" - this is also true for car tires and underwear!" (a well-known developer ... ;) )
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
Can someone check this problem? It's related to LineageOS oneplus3.

Thanks.

https://gitlab.com/LineageOS/issues/android/issues/764
[OnePlus 3 & 3T Cross Device Development] :
Stop crossposting!

Did you try enabling/disabling absolute volume? Or changing the bt codec?
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
I am sorry for that. I did disabling absolute volume and still the same, I changed BT Coded to AAC, by default been to SBC and it's doing the same...

Related to (move bt pro?) Bluetooth streamer pro, when I turn on A2DP Blocker, the sound is crackling in my headphones, but when I turn it off, works fine.

Maybe check the logcat that I provided on bug report :D
[OnePlus 3 & 3T Cross Device Development] :
I've no clue what's going on: I did a complete fresh and clean install: twrp 3.3.1-0, yesterday's LineageOS build, LineageOS Su, OpenGapps nano, no Google backup and I've got rescue party after ota build-in update flash with today's LineageOS build ...
[OnePlus 3 & 3T Cross Device Development] :
Does manual flashing with 3.3.1.0 work? If manual flashing also fails, please get a recovery log. If manual flashing works, start a logcat before you start the next ota in Updater (so we get a logcat from starting ota to reboot to recovery), please.
[OnePlus 3 & 3T Cross Device Development] :
Yes, manual flashing in twrp is working ...

I will need some time after these multiple flashing tests ...
[OnePlus 3 & 3T Cross Device Development] kryzeK:
I'm currently facing a terrible bug: when I receive any call my phone freezes, I can't answer the call or open any app. My 3T backs to normal only if I reboot it.

Anyone has the same problem?

Build 20190530
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No such issue on my side.

Maybe it's time for a clean flash ...

==> https://xdaforums.com/showpost.php?p=79633103&postcount=2131
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Sounds like you either flashed the full Opengapps which replaces the phone app, or have you replaced the phone app manually. This can cause the symptoms you're explaining. Make sure to flash the nano package of Opengapps. And also, if planning to change to another app for phone handling, make sure to set that app as default in settings, after that you can disable the standard phone app without having to use any third party freezing apps.

Skickat från min Nexus 7 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For reminder:

Even if not specified in OP, Open Gapp pico or nano is strongly recommended to avoid modifying system files (see NLOS OP).
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5091734]dianlujitao[/MENTION]:

Sorry, to bother, but do you have any information on why one of the best features of livedisplay is thrown away?

https://review.lineageos.org/q/topic:"kill-livedisplay-temp"+(status:open OR status:merged)

EDIT: To be more specific: I like the livedisplay implemwntation over the (now used) aosp implementation (Display->Nightlight) because it can be comfigured much warmer.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Yeah, if this continues to occur after today's update, unfortunately I will have to do a clean flash...

I always use gapps nano, and my phone app is the stock one.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Is this working? I updated to latest build but still seeing the same panel as before.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Yes, the expanded volume panel that allows changing all streams works fine since 20190530 build.
[OnePlus 3 & 3T Cross Device Development] :
Look closer: the audio settings gearwheel icon is replaced by an arrow to left (bottom of the not expanded expandable volume panel). Tap it and the expandeble volume panel changes from not expanded to expanded.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Ok guys, the problem occurred again with today's build.

Let me explain better what happens: first, I was wrong, this does not happen when someone calls me, this happens at random. And my phone does not freeze, I can usually use my launcher and systemUI (qs panel, lockscreen etc). But when I try to open any activity/any app, nothing happens or after a long time opens but only displays the "splash screen".

A reboot solves it.

I attached a logcat, could anyone please investigate this? I did not want to clean flash to have this problem again, this has happened since the 20190530 build, before that it was all perfect. And my last clean flash was just under 2 months ago, this really should not be happening :( I love LOS, I wanted to continue using this.

Any help with more info/logs/tests, please tell me. Thank you!
[OnePlus 3 & 3T Cross Device Development] :
Unfortunately the "no background " option is gone now with the new wallpaper app.

When I delete /system/background I can still use my gallery for setting an (black) background, though the link in the launcher settings is giving an app not installed message when selecting the background option. Would ve nice if option was gone when app not available or referring to the other background options available (gallery etc....)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
New wallpapers in 20190601 build and you can select a black background ... see the two screenshots below.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Counter view: My biggest gripe with LiveDisplay is that you can't set a start and end time and have to rely on the system to change colours for you. This control offered by Night Light is just better in my opinion.

Also, I don't think this is [MENTION=5091734]dianlujitao[/MENTION]'s choice, looks like it was a Project Director level decision instead. :)
[OnePlus 3 & 3T Cross Device Development] :
Of course it's not. It's not device specific. But I hoped he has some background info on the "why".

Sadly, you've cutted my original question. I've added my personal preference, to avoid answeres like "use Night light", not to question the decission. I could have asked just the other around: why has Night light dismissed for Livedisplay?

There are two working implementations. First it was moved from A -> B, and some months later vice versa - I'm just interested in the reason. I don't want to change the decission, I want to understand it.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Apologies for cutting your original question. Perhaps a better place to ask this would be the LineageOS IRC where you can address this question to the entire team. :)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Perhaps someone can ask them if Livedisplay is responsible for the 'Phone is Starting' bug on many Oneplus devices running LOS/Based ROMs? It' a theory.

Strangely the OP3/T on LOS seems to be the only one not affected. There's only one report in this thread and that was a long time ago. Other devices are plagued with it.

I got a few people to capture logs and i got one myself. Livedisplay errors were the only thing i could see that were a common factor. Now i hear someone built a ROM and removed Livedisplay, replacing it with the Omni display implementation, which supposedly fixed the issue.

There was also a zip containing a 'fix' that originated in the LOS Telegram group that worked perfectly. It stopped the bug in it's tracks Someone posted the zip on XDA a while ago and then nothing more was said about it. Whatever the 'fix' did, it hasn't made it into ROMs, and yet it still works. I can see what the zip contains but i have no clue what it does.

Perhaps someone can decypher it:

https://xdaforums.com/showpost.php?p=79249663&postcount=16

The early theory was that it was Magisk causing the issue but then it affects people who don't use it.

Nobody on the forums for the afflicted devices seems to have a clue. ROM Devs try various fixes which do nothing. There has to something useful to be gleened that the OP3/T are the only devices on LOS that seem to have escaped the issue. I get it on my LOS Based ROM on both my phones. You could then say, 'well it's that ROM that's broken', but it affects Official LOS on many devices too. Just not this one!

So strange.
[OnePlus 3 & 3T Cross Device Development] SedyBenoitPeace:
As for this recommendation, if I want to use Google Apps for other stuff like dialer (that there isn't in pico or nano), can I install after boot or in every case is something that will cause to me the "call freezing" bug for example?

Unfortunately I'm prisoner of Google Ecosystem :)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I use nano gapps and I have also installed Google Phone and Messages from the Play Store. I have not had any problems with either of these apps.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
On my side, I occasionally have the 'Phone is Starting' bug on our two OP 3T and I then have to restart the system.

On the latest build (20190601), my son's device had the bug and not mine !?

I will now check if there is a relationship with a Livedisplay patch.

We do not use Magisk but LOS addon su.
[OnePlus 3 & 3T Cross Device Development] :
+1 for me the same on my OP 3