yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For me, yes ... but for a few guys, no issue with OTA updater ... Read the previous posts of nvertigo67.
[OnePlus 3 & 3T Cross Device Development] James Bottomtooth III:
Is the default camera app not as good?
[OnePlus 3 & 3T Cross Device Development] :
Thanx. I know formatting data is a pain in the 0ss!

I've expected that, because userdata shouldn't be touched on automatic flashing. Since you've used 3.2.3-10 for formatting we can exclude incompatible format (f2fs<->ext4, as well as formatting with non-3.2.3-10), too.

Though I really appriciate your help, I dislike the content of your answer, because that leaves me clueless for now.

Would you check the /cache/recovery/block.map file next time the autoupdate fails, please? In twrp's termonal:

file /cache/recovery/block.map

Depending on the result, try to open/view the file (i.e. if file returns zip or data, try to unzip -l; if ascii is returned try to view with less or cat).

Does anybody know, if it's possible to get a recovery.log from a successfull automatic flash?
[OnePlus 3 & 3T Cross Device Development] DarthVesh:
It's nice but the ports are nicer
[OnePlus 3 & 3T Cross Device Development] unimke:
Anyone notice a visual issue on the status bar after turning off airplane mode? The signal bars increase in distance.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
my new config: cache/data in f2fs format.

same error code (in French... as usual)

I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to install via mapped zip '/cache/recovery/block.map'
Erreur lors de l'installation du fichier zip '@/cache/recovery/block.map'
Traitement du fichier de script terminé
I:Set page: 'action_complete'

In TWRP terminal:

file /cache/recovery/block.map
sh : file: not found
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Here you go, including the block.map and ucrypt_file.

PS: it was a bit tricky to get because you lose root and I didn't want to go back into recovery in case the log got overwritten, and I couldn't access the files using ADB (no permission), so here's what I did:

- extracted the boot.img from the zip

- patched it using Magisk Manager

- copied the patched image to my PC

- booted into fastboot

- flashed the patched boot image

- rebooted the phone

- copied the files (as I now had root again)
[OnePlus 3 & 3T Cross Device Development] cowgaR:
I thought formatting data on 15.1 will decrypt the phone. Guess need to catch up with progress...

Also, did not know f2fs supports encryption, thought it's only possible on ext4 fs.

Anyway, great thread and I welcome enthusiasm here. Thanks to all involved and nvertigo in particular.
[OnePlus 3 & 3T Cross Device Development] warque:
I formatted data using TWRP 3.2.3.0, but first

i backed up my data in ext4 encrypted

formatted to f2fs

then restored data

still encrypted after all those (btw I lost all my photos and videos, good thing I got them backed up in cloud)

if I recall correctly they say that TWRP 3.2.3.1 has issues with encryption, please correct me if im wrong.

Now, Im using 3.2.3.10 as suggested.
[OnePlus 3 & 3T Cross Device Development] :
Why does LineageOS Downloader app install updates successfully & OTA fail?
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
Maybe this has already been mentioned: What bugfixes / features are not included (or will never be included) in the official LOS 16 as compared to the beta builds?
[OnePlus 3 & 3T Cross Device Development] michie:
Nothing, they are compiled from the same source
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Please find attached the requested file.
[OnePlus 3 & 3T Cross Device Development] michie:
My apologies, I was not aware of a new unofficial update.

As the title of this thread states official it was obvious to me to conclude that unofficial builds stopped and that we were talking about the preview builds.
[OnePlus 3 & 3T Cross Device Development] :
Great. Thanx.

I belive I've found something:

03-12 11:14:41.575 6803 6803 W uncrypt : type=1400 audit(0.0:178): avc: denied { fowner } for capability=3 scontext=u:r:un
crypt:s0 tcontext=u:r:uncrypt:s0 tclass=capability permissive=0
03-12 11:14:41.578 6803 6803 I /system/bin/uncrypt: update package is "/data/lineageos_updates/lineage-16.0-20190311-night
ly-oneplus3-signed.zip.uncrypt"
03-12 11:14:41.579 6803 6803 I /system/bin/uncrypt: encryptable: yes
03-12 11:14:41.579 6803 6803 I /system/bin/uncrypt: encrypted: yes
03-12 11:14:41.579 6803 6803 I /system/bin/uncrypt: writing block map /cache/recovery/block.map
03-12 11:14:41.579 6803 6803 I /system/bin/uncrypt: block size: 4096 bytes
03-12 11:14:41.579 6803 6803 I /system/bin/uncrypt: file size: 596263018 bytes, 145573 blocks
03-12 11:14:41.579 6803 6803 E /system/bin/uncrypt: Failed to set pin_file for f2fs: /data/lineageos_updates/lineage-16.0-20190311-nightly-oneplus3-signed.zip.uncrypt on /dev/block/bootdevice/by-name/userdata: Permission denied
03-12 11:14:41.579 1290 6802 I RecoverySystemService: uncrypt read status: 0
03-12 11:14:41.580 1290 6802 E RecoverySystemService: uncrypt failed with status: -1
03-12 11:14:41.580 6803 6803 I /system/bin/uncrypt: received 0, exiting now
03-12 11:14:41.580 1290 6802 E ShutdownThread: Error uncrypting file
03-12 11:14:41.580 1290 6802 E ShutdownThread: java.io.IOException: process package failed
03-12 11:14:41.580 1290 6802 E ShutdownThread: at android.os.RecoverySystem.processPackage(RecoverySystem.java:475)
03-12 11:14:41.580 1290 6802 E ShutdownThread: at android.os.RecoverySystem.processPackage(RecoverySystem.java:498)
03-12 11:14:41.580 1290 6802 E ShutdownThread: at com.android.server.power.ShutdownThread$7.run(ShutdownThread.java:772)

Would you like to try again (incl. getting the logcat), but before starting Updater switch to permissive selinux (adb shell su -c "setenforce 0"), please?

If it's, what I think (missing selinux rule for uncrypt), I wonder why it's working for some people...

EDIT: with 'adb shell su -c "getenforce"' you can checkmif the above command has worked. This should return "Permissive".

If you arn't rooted, yet, use Magisk.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
!!!! .... GREAT .... !!!!!!

su 0 setenforce 0 (via terminal app) .... OTA updater works fine ..... Many thanks nvertigo67 !

Please find attached the logcat file.
[OnePlus 3 & 3T Cross Device Development] :
Thank you very much!

[MENTION=5091734]dianlujitao[/MENTION]:

We need your help here:

why does this hit only some users? From my point of view this should effect all users, shouldn't it?

where should these two rules be placed? In the oneplus3 device repo or in the lineage device repo (device/lineage/sepolicy?

grep avc: log_OTA_Enforce_0.txt |grep -e uncrypt -e block.map -e lineageos_updates|audit2allow -p /mnt/export/data/src/los16/out/target/product/oneplus3/root/sepolicy

#============= system_server ==============
allow system_server ota_package_file:dir getattr;

#============= uncrypt ==============
allow uncrypt self:capability fowner;

Extremely special Thanx to [MENTION=9708417]Eric_Lev[/MENTION] and [MENTION=2911853]BillGoss[/MENTION]!!!
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Anyone getting error 7 while updating LineageOS 16?i've dirty flashed 16 over 15.1 and the latest build eon't5 flash.

Already redownloaded it.
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
Which TWRP Version?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] mueslijam:
running latest firmware?

5.0.8 is required

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/243493
[OnePlus 3 & 3T Cross Device Development] multiwirth:
​

Latest version but i've read the recovery log and the firmware is too old.

---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------

Yeah i guess sometimes it is useful to just read the recovery log it told me what's wrong :D
[OnePlus 3 & 3T Cross Device Development] anavarro8794:
Is it just me or, March 10 release there is a rapid batter drain?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's you. I'm also on 190310
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4756384]Der-Knuffi[/MENTION], [MENTION=9751482]mueslijam[/MENTION] … @"all"

**** PLEASE READ THE THREAD ****

Tips from [MENTION=5091734]dianlujitao[/MENTION]

-You need at least OxygenOS 5.0 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.

- Install a compatible Recovery (My unofficial TWRP (3.2.3-10) is highly recommended: https://androidfilehost.com/?fid=1395089523397907195)

Reminder about firmware (https://xdaforums.com/showpost.php?p=79051655&postcount=976)

Just in case, if you encounter "error 7" when flashing the next nightly, update your firmware to OOS 5.0.8: https://review.lineageos.org/c/Linea...plus3/+/243493

OP3T: https://github.com/nvertigo/firmware...8-firmware.zip

OP3: https://www.celsoazevedo.com/files/a...odem-firmware/

Credit: [MENTION=4405529]nvertigo67[/MENTION], NLOS release post

Reminder about 3.2.3-10 TWRP (https://xdaforums.com/showpost.php?p=79099786&postcount=513)

If you have used 3.2.3-1 for formatting userdata the encryption footer is removed. oos is forced encrypted (this means, that oos tries to encrypt an unenfrypted userdata partition on boot). If there is no space on userdata reserved for encryption footer that doesn't work and the rom can't boot.

3.2.3-0 will format userdata with encryption footer. 3.2.3-10 will only preserve the space for encrypton footer, if it's present - if no encryption foozer is present, 3.2.3-10 will not create a new one.

To get the encryption footer back, use 3.2.3-0 or format with fastboot.

Once you have the encryption footer back, 3.2.3-10 is highly recommended..

Credit: [MENTION=4405529]nvertigo67[/MENTION]

Reminder: a clean installation is better than successive dirty installations!

So if you want to save time:

- Backup your personal data and your app (e.g. nandroid backup, Migrate - https://xdaforums.com/and...-tool-t3862763, …etc)

- Perform a clean installation (full wipe in ext4 or f2fs format - install your ROM, Gapp and SU) then re-install your app and personal data

==> It is not time-consuming ... between 15 and 30 min max.
[OnePlus 3 & 3T Cross Device Development] realtos:
Wish regular update??
[OnePlus 3 & 3T Cross Device Development] :
Today's update is online :)
[OnePlus 3 & 3T Cross Device Development] caryle:
Love you guys! Thx!
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
I am having heat and battery drainage issue. I have found this on logcat spamming continuously.

https://hastebin.com/epeyokozoj.coffeescript

PS: I am using latest gapps from opengapps
[OnePlus 3 & 3T Cross Device Development] rakshith-ravi:
Hey dev, just tried this ROM. It looks like outgoing calls don't seem to be working. Every time I try to make a phone call, it keeps saying "Call ended" even before it gets connected or even before I hear a dial tone. I would go on a limb and say that it has something to do with VoLTE, since I'm using Jio 4G (LTE based) SIM card, but I'm not entirely sure. SMS seems to be working just fine. Incoming calls don't seem to be working either. Is there a setting that I should change or something to get it working or is that a known bug? It doesn't seem to be listed in the list of known bugs so I'm just curious
[OnePlus 3 & 3T Cross Device Development] BillGoss:
"Normal" phone calls work just fine - I don't use VoLTE.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Yeah i guess volte patches aren't implemented as of right now
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
probably a gapps bug
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
volte is probably not supported currently, not sure.
[OnePlus 3 & 3T Cross Device Development] hc8708:
Issue with Alarms, only ring when screen is turned on otherwise rom is pretty stable.
[OnePlus 3 & 3T Cross Device Development] rakshith-ravi:
Wait so how do I disable VoLTE? Cuz if I can get calls to work, this is my daily driver!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You're on your own there. I don't even know if telcos in Australia support VoLTE. I've not turned anything off.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
They work fine on my phone.

In fact, I've not come across a single problem with this rom.

I've been using it for two days.

Battery performance is good. Overnight battery drain was only 1%; screen on uses 10%/hr. This is the same as what I get on OOS and NOS.

Very nice work, [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] michie:
Everything seems to be working well, thank you!

Can't seem to get the Pixel launcher to work though, it keeps crashing. Installed it through open gapps aroma. It shouldnt be related to any missing libs or configuration as the open gapps package takes care of this right?
[OnePlus 3 & 3T Cross Device Development] :
Have you tried installing pixel launcher as user app instead?

See https://xdaforums.com/showpost.php?p=77129446&postcount=3282 for in detail explenation, why you have less problems when installing additional gapps as user apps and replacing as less rom's systemmfiles as possible.
[OnePlus 3 & 3T Cross Device Development] michie:
I didn't but only for the main reason that the google feed won't work when it's not installed as a system app. It works on Nitrogen with the same gapps package though so must be some dependancies missing. I'll try to get a log of the crash.

Edit: I checked the system files and it appears it does not include pixel stuff like the pixel framework overlay. I am able to run the pixel launcher by adding the files manually with correct permissions.
[OnePlus 3 & 3T Cross Device Development] hauckk@sfreserves.org:
Just letting you know I dirty flashed from sultans last official 14.1 build may 2018 encrypted up to your newest build still encrypted and all is going well

Steps I took in twrp were

flash 5.07 modem firmware zip

Then dirty flash official 15.1 zip

Then dirty flash latest 16.0 build then magisk and gapps

Encryption still works no lost data
[OnePlus 3 & 3T Cross Device Development] pharandeamit:
Do the Google Pay works on this Rom without denying telephony permission to Google Play Services? because on Havoc OS it won't work unless you deny telephony permission to Google Play Services. Let me know. Thanks.
[OnePlus 3 & 3T Cross Device Development] dakid1235:
Great ROM. One question how do I control the alert slider settings? When I put it into any of the three options it turns the ring volume off?
[OnePlus 3 & 3T Cross Device Development] dom001:
Same here. Everything works except gcam. :(

At the sultal 14.1 "Arnova's v7beta9" was the latest gcam mod that worked there: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/

Now on this dirty flahed 16 no gcam-mod seems to work: I immediately got force-close. I tried this 5 hints without luck :( https://www.celsoazevedo.com/files/android/google-camera/troubleshooting/
[OnePlus 3 & 3T Cross Device Development] Notor1ouS-:
regarding dirty flash vs clean install:

it's placebo. no difference for me and battery is exactly the same.

did a 'dirty' flash from 15.1 to 16.0 and it's working.

clean install is needed when something is clearly broken.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
My config: full wipe + clean install / last current build / Open Gapp nano / official LOS addon SU / FW 5.0.8 / TWRP 3.2.3-10 / encrypted data / f2fs format for cache and data

A possible issue with manual updating Open GAPPs (not reported in this thread unless I'm wrong)

When I update my current open gapp (via recovery + wipe cache/dalvik or not), the first update works fine but a subsequent update (the next day or another day) leads to a Google Play Store issue (app fails to open despite a clean cache, a re-boot sytem, a dirty build/gapp/SU re-install ... etc).

Note that I have/have had this problem with previous unofficial and official LOS 16 builds (dirty or clean install).

Is anyone else experiencing this issue?

[MENTION=2867000]Notor1ouS-[/MENTION]

Please, read this post: https://xdaforums.com/showpost.php?p=79052953&postcount=987
[OnePlus 3 & 3T Cross Device Development] :
Don't!

If you clean flash on the first boot, not only the basic setup up is created (GSetupWizard), but also the g config db is created. All gapps will be updated according to your ps settings. gservices are always auto updated - no matter of your ps settings.

If gservices is updated with changes to g config db, the updating process takes care of that. On rom updates the addon.d scripts takes care, that the currently installed (aka updated) versions are saved and restored.

If update gapps manually you may succeed or not. I don't think, that the count of updates play in here (besides the statistically effect, that if you asked 1+n times for trouble you increase the chance of getting trouble compared to asking once for trouble... ;) ). There are quite some scenarios, where trouble will be there for sure: i.e. if the flashed gapps package has a minor gservices (and/or db) version compared to the installed (aka autoupdated) version, or if packages that has been included on first time setup (GSetuWizard) has more/other apps and/or services then the later dirty flashed ones.

This is also one more reason why I recommend to clean flash on major version bumbs of the rom. Though it is - at least - guaranteed that the newly dirty flashed gservices and db have a higher version number, it's always enough room for strange side effects. I know many people claim it's working (I can hear them in this very moment crying "but it's working for me, you smart-arse"), since it's proofed something is fixable by a clean flash (generally by wasting someone else' time), but I know of not a single user proofing this has NO side effects... ;)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION]:

Thank you very much, it's a clear explanation... as usual!
[OnePlus 3 & 3T Cross Device Development] ciarpame:
I moved from 15.1 from 16.0 with a dirty flash, apparently without issues and following a suggestion (Please note that if you’re currently on an official build, you DO NOT need to wipe your device.) found here: https://lineageos.org/Changelog-22/.

I never did it before and, by the way, the instructions are quite contradictory, as I was confirmed on reddit.

But I don't want underestimate the gurus indications found on this thread (I really don't want to have to report a bug tomorrow morning caused by my dirty flash upgrade and wasting someone else's time to deal with my issues) and I have a question for them.

For the rest of the Android world not dealing with custom ROMs (99+% of devices I suppose), moving from a major version to another with a dirty upgrade is not an option, is the only way to upgrade. I bought a Nexus tablet years ago, it was two major OS releases behind the current one, so I had to do a couple of dirty flashes even before beginning to use the device. Why doing the same with LineageOS it seems to be so dangerous?

Maybe the reason is that an average Android user is flashing new ROMs a few times during the device lifecycle and such ROMs are (hopefully) well tested before being released, while a LineageOS typical user is flashing a new ROM build (at least) a few times a month and it's messing with firmware releases and partitions formatting and so it's much more likely to introduce issues? Or maybe commercial Android releases are more solidly designed or tested for a dirty flash major release upgrade?
[OnePlus 3 & 3T Cross Device Development] :
If you never expirienced yourself, nor ever heard of someone else expirience that a clean flashed solved an issue, this is very understandable and I'm crossing my fingers for you, that it stays that way.

On the other hand: it's exactly that attitude, that consumes quit some of my time:

I'm doing public custom los builds since cm-11 on galaxy tab s. When I sum up the time I needed to hunt phantom issues in the logs that were finally solved by a clean flash it's around 300h (60 times, ~3h each begging for logs and information and searching the logs, 2h to argue against "but xyz says clean flashing and factory resets are placebo"; "but on abc def reports it's working"; or one of my favorites "I've never need to do this before).

If you look at the vendor driven support forums, or look at the transcripts of other vendor support channels, "clean flash" or "factory reset" is often read/heard, isn't it?

Though you've never expirienced the need of a clean flash, nor ever heard/read of someone else needed a clean flash, concluding that a clean flash is never needed is no only tough, but also not matching reality.

In my expirience a clean flash on major version bumbs of the rom is recomendable.

---------- Post added at 17:03 ---------- Previous post was at 16:19 ----------

If users dirty flashing from 14.1 to 15.1 and dirty flashing from 15.1 to 16.0 have expirienced a crashing snap (with builds prior to 0305), but users that has done - at least - one clean flash instead doesn't have suffered from this, clean flashing can't be placebo.

Your statement itself claims clean flashing can't be a placebo:

"it's placebo" is an obvious contradiction to "clean install is needed when something is clearly broken". If something is clearly broken and a clean flash fixes that, it can't be placebo, can it?

Nobody likes clean flashing. But claims should be checked with reality and not just with the personal likes. Though I would like if clean flashing is just placebo and is never necessary again, it's still wrong.
[OnePlus 3 & 3T Cross Device Development] Cmindo:
Anyone noticing issues with Spotify and sound output?

To explain, it works fine when using the Phone Speaker but when I plug in an AUX cable to use an external speaker (e.g. Car speaker), the audio cuts out.

I have found a workaround by letting the song play through the phone speaker first then plug in the AUX afterwards (as opposed to before), although I feel this is a bug that needs to be addressed.

If it's just me then I'm not sure what the issue is, and it only started happening when I cleaned flashed LaOS for the first time (was fine in ArrowOS 9.0).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
==> https://xdaforums.com/showpost.php?p=79057711&postcount=1014

==> https://xdaforums.com/showpost.php?p=79060320&postcount=1025
[OnePlus 3 & 3T Cross Device Development] :
Answered really MANY times: disble/freeze/delete AudiFX. I'm answering this the 5th time!

This issue has many faces. If you only use bt you can alternatly disable aptx(*), if you use jack connected headsets, plug it in at the correct moment, for usb-c just disable AudioFX in the AudioFX settings and so on. To work around ALL aspects of this issue at once: freeze or delete AudioFX.

(*)tried with Teufel Move BT: though it works, it's like replacing the Move BT with one of these 3$ jack headphones you get in commercial airplanes, not matter what I set in AudioFX. Deleting AudioFX and using aptx is a much BETTER expirience.
[OnePlus 3 & 3T Cross Device Development] enochpc:
Just to save you having to read posts ten pages back, I have found if you disable AudioFX the headphone jack issues go away.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Reading the thread in its entirety or regularly can be useful to learn and understand ... and avoid asking the same questions over and over again... even if it seems boring... isn't it?
[OnePlus 3 & 3T Cross Device Development] :
Ten pages back? You found? Dude what's wrong with you?

He only needs to read the first line in the posting prior to yours (for you: it's on the same page).

And for more information on this issue (it appears for more audio sinks then only on jack), he just needs to read the second paragraph of the posting directly prior to yours (for you: it's on the very same page just before your posting, scroll back slightly, please):

Not using search before posting has become the standard, but ignoring the posting directly before your own claming this information needs reading "ten pages back" posting is a completely new level of ignorant habbits...