yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Migration from 9.0.4 fw to 9.0.5 fw :

Before :

==> OnePlus 3T / FW 9.0.4 / TWRP 3.3.1-0 / ext4 / unencrypted / BL locked / LOS 16.0 build / open gapp pico / LOS addon su

Note that my 9.0.4 fw was unmodified ( https://github.com/nvertigo/firmware-3t/blob/master/archive/op3t/oxygenos-9.0.4-firmware-3T.zip)

How to proceed:

- Boot to TWRP 3.3.1-0

- Flash oxygenos-9.0.5-firmware-3T.zip (credit: [MENTION=4405529]nvertigo67[/MENTION])

==> https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.5-firmware-3T.zip

- Reboot to System

After :

==> OnePlus 3T / FW 9.0.5/ TWRP 3.3.1-0 / ext4 / unencrypted / BL locked / LOS 16.0 build / open gapp pico / LOS addon su

Right now: No issue.

FYI, the updating to 20190808 with Lineage Downloader app (Play Store) worked as expected ... with 9.0.5 fw.

If needed, oxygenos-9.0.5-firmware-3.zip (9.0.5 fw for OP3) ... https://github.com/nvertigo/firmware-3t/blob/master/archive/op3/oxygenos-9.0.5-firmware-3.zip

As reminder : Modded fw ... https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Thanx [MENTION=4405529]nvertigo67[/MENTION] !
[OnePlus 3 & 3T Cross Device Development] niljoste:
>> Are there people have freeze (notification led white and phone totally blocked with screen off) with efficiency battery profile ? Every time I use it, after a random time (between 10min to 2h) i have this. Only solution is to force reboot with power button.

I had that problem and thought my phone was broken. I almost bought a new one :) Didnt recognize it was the profile, so i reinstalled stock where the freezes dont appear! It happened not while using the device but when IT was in standby.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
In order to determine what's causing the problem I would do one step at a time and test to see when the problem happens. So:

1. Factory reset in TWRP

2. Install only Los zip (nothing else)

3. Reboot and don't restore any apps or data or accounts

4. Test sounds and phone calls.

If all is ok, then you know it's not a hardware or ROM issue. 5. Flash Los su and gapps; reboot and, again, don't restore anything

6. Repeat tests.

If all is ok, then you know the issue is with something you've either restored or installed on your phone.

Happy hunting!
[OnePlus 3 & 3T Cross Device Development] Lord Broker:
Hi. Can anyone help me with my bootloop? This is my situation. I was (am?) on 20190731 nightly, and 9.0.4 firmware. Decided to update to newest 20190810 via manager in settings, so I downloaded it and I thought that's it. Unfortunatelly phone was doing updating in twrp and then wanted to mount something, after that I was in recovery so I did a system reboot and it didn't boot there, instead after some loading get back to twrp and wanted to mount and that's my bootloop, I can't reboot system ;(

Edit. Should I just install 9.0.5 firmware and then dirty flash rom? (dirty means with no wiping, yes?) sorry for stupid questions but I just don't want to make it worse. Thanks.
[OnePlus 3 & 3T Cross Device Development] :
Stick to xda rule #1 and search before posting: automatic flashing from Updater is broken with twrp 3.3.1-0. Boot to twrp and just dirty flash the rom's zip again.

Automatic flashing with twrp-3.2.3-0 or twrp-3.2.3-10 works.
[OnePlus 3 & 3T Cross Device Development] Lord Broker:
I did that and it didn't solve the problem. When trying to boot to system there is request for PIN an then LOS booting animation for about a minute. After this there is not a system launch but goes back to twrp and asking for password to decrypt data, over and over again.
[OnePlus 3 & 3T Cross Device Development] :
Do you have any mods (i.e. magisk, themes, etc.) installed?

You can try wiping system and reflashing the rom and the exact same gapps package as before. If that doesn't help, format data and clean flash.
[OnePlus 3 & 3T Cross Device Development] rg_gapa:
I have this issue from time to time (once a week at most)
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Does anybody know why the security patch is this month only from 1st August and not from the 5th?
[OnePlus 3 & 3T Cross Device Development] ranaxda200:
Is the vendor security patch level 1 April 2019 correct?
[OnePlus 3 & 3T Cross Device Development] :
https://review.lineageos.org/c/LineageOS/android_build/+/252608 (Luca's last comment)

Next build will have 5th:

https://review.lineageos.org/c/LineageOS/android_build/+/252908

Vendor sec patch level relies on the patch level of the blobs: as long as the blobs are taken from oos 9.0.3 is April, 9.0.4 is June and 9.0.5 os August.

[MENTION=5091734]dianlujitao[/MENTION]:

Since we are using currently 9.0.4 (https://github.com/TheMuppets/proprietary_vendor_oneplus/commits/lineage-16.0/oneplus3) it should be June.

IMHO it doesn't make much sense to fix this, because we can increase it to August as soon as 9.0.5 blobs are merged. And it doesn't really hurt to have April...

EDIT: if this bothers you, you can edit the date string in /system/build.prop (from twrp, if you aren't roozed).
[OnePlus 3 & 3T Cross Device Development] mr.klee:
So I flashed this ROM, did a full wipe and I still have a huge battery drain. Over night (8 hours) I lost 65%. Same problem with stock ROM (both 5.0.8 and 9.0.4). Any ideas what could be wrong? It started when I changed my battery... But now it's the same with two new batteries and the old one.

Thanks a lot!
[OnePlus 3 & 3T Cross Device Development] Uqbar:
It looks like a battery problem.

Are the new ones "real brand new original" packs?

The battery management is done through a small circuit attached to the battery pack itself. If damaged or not the right one it will give just headaches.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Maybe Google Play Services?

Version 18.3.82 has a battery drain problem

https://www.androidpolice.com/2019/...-services-update-has-a-battery-drain-problem/
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
I have drain to. It os Google play services. Tell me the best version GPservices for This problema please
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm running 18.3.85 and I have no drain.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I'm also running 18.3.85 and no drain on my side.
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=80068217&postcount=966
[OnePlus 3 & 3T Cross Device Development] Nixeus:
Hello guys,

I never tried LOS on my OP3T....is it better than the Stock Rom ? I don't do game or special ****...just want a better batterye life and stability for every day use.

Any advices ? Stay on stock, or go LOS ?
[OnePlus 3 & 3T Cross Device Development] crypta:
not using it ?. seriously you'll notice they are not really needed. use microg + aurora shop.

and yes, IMHO one main feature of Los is getting rid of Google. if you want to stay with Google, which is OK, why not just rooting oos?
[OnePlus 3 & 3T Cross Device Development] kousik:
Did anyone see/solve a problem where the phone automatically switches to Vibrate mode (no ring)? I need to check the icon, and then manually bring it back to ring mode. I'm trying to find a pattern when exactly the switch over happens. If I knew ahead of time I'd let the phone run under logcat and post.
[OnePlus 3 & 3T Cross Device Development] NVDX11:
Noob question, Can we add volte icon to status bar ? & if yes then how?
[OnePlus 3 & 3T Cross Device Development] felagund:
Is there a quick fix for roaming data I've missed?

I'm using a nightly from the week just before the pie firmware requirement (build from 8th of June) and now on a business trip enabling roaming data doesn't work and apps complain about no network so it's good that I have a spare phone to use for tethering by chance.

Roaming calls work fine though.
[OnePlus 3 & 3T Cross Device Development] :
What's your setting for network selection? I found that roaming only works correctly if automatic network selection is choosen. This may be different depending on carrier and dataplan.
[OnePlus 3 & 3T Cross Device Development] felagund:
Automatic network selection is on and I can't turn it off actually as it turns on again. I tried toggling it, toggling roaming data, rebooting, etc. but nothing worked. I just wondered if I've missed info for a fix and am not very good at crawling through logs. I think I have the apn for my home network manually set up so I wonder if this might be causing the problem. In a few hours I'll get the opportunity to swap sim cards and try without APN. I think I read earlier in the thread it can be reset through the dev options so I'll give it a go.
[OnePlus 3 & 3T Cross Device Development] :
The issue with broken manual netwprk selection was fixed in February (https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/240026 ). I've never expirienced it again since the fix was merged.

Do you have any mods installed? Build.prop hacks? This seems really strange to me and may relate to your roaming issue.
[OnePlus 3 & 3T Cross Device Development] felagund:
No mods or hacks but it might be due to dirty flashing and updating from 15.1 thanks for the info. I'll do some tests and try to resolve.

Thanks for the info and don't waste* more time with this case. If I have an update I'll post it but it seems specific to my setup.
[OnePlus 3 & 3T Cross Device Development] fashion_live:
I just unlocked and rooted my op3. i would like to install this rom.

I have to install

1)Firmware (where can i find it?)

2)Lineage ROM

3)Gapps 9.0

It's confirmed?
[OnePlus 3 & 3T Cross Device Development] :
Depends on what you've installed. If you come from oos 9.0.2 or later, you have already the needed fw.

My fw archive: https://github.com/nvertigo/firmware-3t/tree/master/archive (the filenames not containing bl-km-5.0.8 are plain stock fw packabes.)

If you need to update the fw, you ,ay consider usimg the modded fw. For details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

For opengapps use pico or nano.
[OnePlus 3 & 3T Cross Device Development] d.schmidt:
Hey,

I managed to successfully install the nightly of today. Almost everything seems to work fine but for blocking calls. The OnePlus3 is my backup phone which I don't want to receive calls on. I've tried probably a dozen different call blocking apps but none prevented the call notification to show up. Is there any way to achieve this?

Preferably without 3rdparty app of course...
[OnePlus 3 & 3T Cross Device Development] :
Why not just disable notifications for your default dialer app? The notification settings for the rom shipped dialer are very fine grained.
[OnePlus 3 & 3T Cross Device Development] felagund:
Resetting APN within the APN menu fixed it and it also worked on manual selection, not only automatic. It just selected the neighboring entry : instead of telenor internet it selected globul(the older network name before telenor acquired it) and I start thinking I might not have set it up manually.

Anyways it works fine now. Settings related problem.

Wrong attachment but how do I delete it from XDA app :D
[OnePlus 3 & 3T Cross Device Development] :
I think with next nightly the PIS issue will be solved... ;)

https://review.lineageos.org/252878

https://review.lineageos.org/252879

https://review.lineageos.org/252978

---------- Post added at 19:36 ---------- Previous post was at 19:33 ----------

Haha, when can we come for eating your home made nasi :silly:

Just press edit and delete attachment at the bottom of your screen below post ;)
[OnePlus 3 & 3T Cross Device Development] :
I think it's the complete topic, which is needed to fix the hwc2 stuff (btw: hardwarecomposer chrashes were always much more suspect to me in the logs by [MENTION=1763460]Dirk[/MENTION], then the livedisplay hal errors itself):

https://review.lineageos.org/q/topic:%22fix-hwc2-outdoor%22+status:merged

Let's crossing fingers, that PIS is really solved with these... :good::good::good:

---------- Post added at 19:48 ---------- Previous post was at 19:39 ----------

Is this for the web interface or the xda app? The forum app included in xda labs doesn't offer such "luxury"... Whenever I use it, I'm looking desperatly for options found in the web interface...
[OnePlus 3 & 3T Cross Device Development] :
Hmm.... did not read that part I guess, thought he was talking about editing in normal browser.

Do not use the app so can not answer this question, sorry.... :confused:
[OnePlus 3 & 3T Cross Device Development] felagund:
The XDA app is somewhat lacking yes. I tried through the app first.

Thanks for the tips!
[OnePlus 3 & 3T Cross Device Development] d.schmidt:
https://i.ibb.co/QcKq1tJ/IMG-20190821-145343-993.jpg

(replace * with s, i'm not allowed to post links as I don't have enough posts yet)

All notification checkboxes are checked and greyed out for the phone app. Or are we talking about something else?

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

Ah, I can select "silent and minimise" there. But I cannot disable all notificationa right? And I still get missed call notifications... better than before but still not perfect. And I still get vibration alarm.

---------- Post added at 01:13 PM ---------- Previous post was at 01:00 PM ----------

AAAAHAAA! The trick is not to open notification settings for the phone app but to open general notification settings and then disable all notifications for phone app there. I fiddled a bit with vibration settings and I finally don't notice anyrhing of a call anymore.

This is for now all I need because right now I have no second SIM card that I want to receive calls on.

At some point I will probably need that. Any clue why the call blocking apps do not work? Can anyone confirm or tell me an app that works for them?
[OnePlus 3 & 3T Cross Device Development] fashion_live:
Sometimes when I talk on the phone, during a call, the screen remains black and does not activate (during the call). What can it depend on?
[OnePlus 3 & 3T Cross Device Development] lobotomize:
Screen timeout, or the proximity sensor (if you have the phone up to your ear, the proximity sensor triggers a screen-off so you don't mash the end call button with your cheek, for example)
[OnePlus 3 & 3T Cross Device Development] fashion_live:
If I move the phone away from my ear, the screen remains off
[OnePlus 3 & 3T Cross Device Development] lobotomize:
does it turn back on if you hit the power button? Could still just be a screen timeout.
[OnePlus 3 & 3T Cross Device Development] fashion_live:
if i press power button, screen doesn't turn back on

It happened with oreo also
[OnePlus 3 & 3T Cross Device Development] DoN LoUhI:
Guys NFC is broken , it is just me or I am missing something..
[OnePlus 3 & 3T Cross Device Development] :
Yes, you missed reading before posting: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79901210#post79901210
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION], I read somewehere about your kernel for nlos.

What is the difference with default Los kernel and is it available as kernel only package?
[OnePlus 3 & 3T Cross Device Development] :
Answer moved to the correct place: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post80108342#post80108342
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
With your help I successfully passed the fw-barrier :)

Starting:

unlocked BL

TWRP 3.3.1-0

FW: 5.0.8

LOS 16.0 (2019-06-03) + OpenGapps

no root, no magisk, not encrypted

These were my upgrading-steps:

delete fingerprints & display lock

no backups cause the system was clean (there is a older nandroid on my nas, just in case)

fastboot oem lock

wipe / factory reset & wipe data via TWRP

install FW 9.0.5 by nvertigo, LOS 16.0 (2019-08-21), OpenGapps pico

reboot

NFC:

NFC working

- after deleting /data/nfc/nfaStorage.bin1

- reboot

- switching nfc off/on

--> may be i did not place the nfc-tag in the right way... after wiping data, there should be nothing left, should it?)

Everything else seems to be working fine:

BL locked

Play Protect certified

Fingerprint working out of the box

Did I understand right?

Downgrading TWRP to 3.2.3-10 I will be able to update my system OTA?

But new FW I need to flash via TWRP, don't I?

Sadly my time is limited strongly, too.

So it's really much work to read the thread. But it's worthy, as I updated my device this way without any (okay, without too much) trouble.

At this point I want to thank you for all the research and developement!

I may try changing PIN of german ID card via AusweisApp2 later.

[MENTION=4405529]nvertigo67[/MENTION]

As this is a clean flash, i could do some research and create some logs for you. Maybe about the updater?

fyi:

I want this phone to replace my old one (Motorola Moto X Style/Pure) in a few days, maybe next week. Therefore my SIM is still in my old phone.

My goal is a Play Protect certified Phone passing SaeftyNet.
[OnePlus 3 & 3T Cross Device Development] Dirk:
OTA would work on 3.2.3-10 but you need to use latest TWRP to keep Bootloader locked. As you want Safetynet to pass i suggest picking the latter and just give up on OTA. Do it manually.
[OnePlus 3 & 3T Cross Device Development] :
Phone is starting (aka PIS)

The hwc2 fix is shipped since 0821 build. Has anybody formerly suffering from PIS expirienced PIS with 0821 and later builds, or can we consider PIS really fixed? Since I've never expirienced PIS I can't answer this myself.
[OnePlus 3 & 3T Cross Device Development] trachyte:
So like a zillion other people I flashed the 9.0.x firmware and borked my encryption. I have come to terms with having to wipe all of the data.

I'm still curious exactly what the firmware did to ruin the encryption though. Android FDE uses a randomly generated master key that is encrypted with the user's password + a signature using a key from the TEE. The encrypted master key is stored in the crypto metadata (on-disk); given the location and the fact that Android still knows that the user's password is correct, it seems that the encrypted master key was not altered.

So then the firmware upgrade wiped the TEE? In that case Android shouldn't be able to know that the user's password is correct. AFAICT the crypto metadata stores the final encrypted master key only (post-TEE signing), which means it should only be possible to verify that the password is correct if Android has the ability to sign using the original key from the TEE.

So then the firmware upgrade modified the on-disk data in such a way that it can't be decrypted using the master key? I'm no expert on AES-CBC, but I would think that even if the firmware changed a few blocks of the disk's data it would still be possible to decrypt all of the other blocks.
[OnePlus 3 & 3T Cross Device Development] Dirk:
That is of course an open ended question. If it isn't fixed, for any given user the bug could strike today or a month from now. If nobody has had a single occurence in the next two months i would consider it 'really fixed'.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7065487]trachyte[/MENTION]: I wondered that myself. Maybe this fact shine some light on this: the corruption (data unrevertable lost) takes place on first boot. So the assumption that the bootloader is altering the metadata of the fs is very probable. I'm still beliving that this is not a bug or something oneplus has done accidently, but this behavior is intended. This is not the only strange behavior of the 9.0.x bootloader. The "auto-unlocking" [MENTION=9708417]Eric_Lev[/MENTION] has described is the strangest behaviour, followed by disabling selinux.

---------- Post added at 11:35 ---------- Previous post was at 11:25 ----------

I always thought there are people expiriencing PIS on a regular basis quite often. If it's only hapening once in two months it's barely worth mentioning as an issue. Of, course only the first group is addressed by my request - maybe that's not clear enough in my previous posting.

The best bet we have are the op5 users expiriencing PIS 8 out of 10 times when rebooting, you've reported of.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I don't think anyone here experienced the high frquency that some users on the OP5/T had. Those high frequency cases seem limited to crDroid so maybe there was some bad juju going on in that ROM that made the bug worse in those cases. All we can do now is wait to see if anyone reports it on any LOS/Based ROM across all affected devices.

My own experience with frequency was something in the region of one-in-twenty boots. Even rebooting once a week, that's twenty weeks before being certain the bug is squashed. Of course, with all users taken together, you'd expect someone to be staring at a hanging phone right this very minute if it wasn't fixed, (either natively or using the zip).

Time will tell. I would urge people to stop using the zip fix though, so that the native changes can be tested. (Unless, like me, they just want to carry on disabling Livedisplay altogether).
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
how do i uninstall the google play service application?

where to download this option?
[OnePlus 3 & 3T Cross Device Development] :
Clean flash without gapps.

gservices is NOT part of the rom: yu've installed it, when flashing gapps - if you don't want it, don't flash it.
[OnePlus 3 & 3T Cross Device Development] trachyte:
I spent a few hours tracing through the Android source code that generates the 'Password correct but data is corrupt' error, and I'm more convinced than ever that the data is recoverable. I had thought Android was doing some sophisticated corruption checking. Nope. It tries to mount the encrypted filesystem and if it fails for any unknown reason, it is considered corrupt. And on top of that, Android instantly sets the CRYPT_DATA_CORRUPT flag in the crypto metadata footer and writes it to disk. So any future boots will always display the corruption message even if everything is otherwise in the correct state for the data to be decrypted. Literally OnePlus could have set the CRYPT_DATA_CORRUPT flag in the footer and that would have caused all of this. No need to wipe the TEE or mess with the master key or data.

My assumption about the password check was correct. Both the password and the original TEE signing capability are used. So the TEE was not wiped and the master key was not altered. In fact, the decrypted master key is in memory when the error message is displayed. You could printf() it and use that to decrypt the data manually. Edit a couple days later: Turns out I was wrong about that. I was looking at code that only applied to non-HW encrypted data.

I'm dumping my partitions now and once that is done I'll do some more debugging.
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
I managed to change the PIN of my ID-card using AusweisApp2.

As sombody mentioned before, I had to try a bit to find the right position. . (Mine: ID-card in "portrait-mode"; photo, more exactly my chin, directly on camera)

It really seems to depend on millimetres. It is only working without my case (spigen).

Just flashed OOS to check: It is the same there.

Since NFC-Tools may access NFC-Tags even through my case and it is all the same with stock, I would blame the app too...

I am back now: FW 9.0.5 from Stock / LOS 16.0 / BL unlocked

Found out, that my apps are working nevertheless. :)

So here we go [MENTION=4405529]nvertigo67[/MENTION]: If you want to work on the updater, I want to help you. Just tell me what to do.