yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Yes, but use the twrp recommended in this rom's OP (aka SAR-TWRP). I'll adjust that in the fw package thread.

EDIT:

Changed: https://xdaforums.com/showpost.php?p=82344671&postcount=172
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
[MENTION=4405529]nvertigo67[/MENTION] i am able to flash for Oneplus 3T: oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip but got error while booting into recovery, prompted for encryption password and i do not know what is this default password.

Error messages

decrypt took too long to decrypt, kiling process,decryption failed..unable to mount the system...Password failed, try again..what is the Password?

I got stuck in recovery now..by the way i have used SAR TWRP...any help?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
default_password

or

https://xdaforums.com/search/thread/3866517?query=default password
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Disable the ok Google detection
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
tried already no luck :(
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
I have messed it up while installing 9.0.6 firmware..back to official TWRP followed by LOS 17.1 ( had to format and do a clean install), this where i am worried about flashing firmware directly,..not sure what went wrong..coudn't get rid off decryption issue but cancelled it and went ahead with other steps..:(
[OnePlus 3 & 3T Cross Device Development] :
Because higher frequencies have more difficulty with concretes like stone walls, I guess higher frequencies are using more power for the same range. I also think the effectiveness of the electronic components in the phone on lower frequencies will be better, though probably you will not even notice on the total battery usage. But, 2.4Ghz band is also used by a lot of people which is giving much more noise on the channels as on the 5Ghz band.

I think you just have to try yourself because it probably will depend on the situation where you are using your phone. And of course, we would be happy when you could share the results here for common knowledge!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Nothing like a good clean flash... Enjoy !
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Sorry for this Question again :) Do you have VOLTE working for you? and No LTE signal reception issues?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Because of covid-19 (France), I'm confined to the countryside (since the beginning of March) and the cellular/mobile network isn't great... so I can't answer for VOLTE ... I'm sorry!
[OnePlus 3 & 3T Cross Device Development] :
twrp should know of "default_password", I doubt it's different for SAR twrp.

The error message "decrypt took too long to decrypt, kiling process,decryption failed" is completely new to me. The typical error message if crossing the 5.x to 9.x bl border with encrypted userdata partion is complaining about wrong password. Maybe it's because we all have no expirience with going from 4.x bl to 5.x bl with 3.3.1-x based twrp, but I don't know.

The second error message "unable to mount the system..." is also completly unknown to me. The strange point is: twrp shouldn't mount system at start at all.

Maybe a recovery log can be helpfull, but honestly: I just don't know, since I havn't seen both errors, so far. I also don't know, how to save a recovery log with no userdata partition mounted.

If no one else has seen this error messages, I'd suggest to format data and system (since userdata seems to be gone anyway, I'd recommend to use the unmodded fw (oxygenos-9.0.6-firmware-3T.zip).
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Thanks for your response. even twrp has not accepted the password "default_password", so i had to skip by clicking on 'cancel', it allowed to format again proceed further..I checked teh firmeare version what we have now and it's the same as oo6 9.0.6 .. not sure if it helps to flash modded fw..?? where can i find unmodded fw?

All the error messages appear after providing the password and then system returns to decrypt screen prompting to enter the password again

By the way VOLTE is working for you? if no, how is single strength on LTE?

https://gitlab.com/LineageOS/issues/android/-/issues/1811
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip

VoLTE is a real sore spot for me:

I'm on mcc=262/mnc=02 (vodafone.de). VoLTE has never worked for me: neither with oos 3.x to 9.x, nor with custom roms. All the curtent efs edits with pdc don't work. When I wanted to try the "old" efs edits published on hubo forum, hubo has been shutdown.... Rule of thumb: if VoLTE has worked on oos, the chances are high it's working on los, too. If not the chances are good to get it work on los.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Thanks again..I can give a try..Should i go for dirty flash via official twrp followed by dirty flash of Los? or any other steps to follow..
[OnePlus 3 & 3T Cross Device Development] :
Sorry, dude, I've lost track of your current setup...

If you are on https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip with los-17 and have enrypted the userdata partition again, just stay with it.

If you are on https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip with los-17 without encrypting userdata, change to https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip BEFORE! encrypting again.

Stay with sar-twrp.

If you are on any other setup, please tell me again.

Disclaimer: I strongly recommend encryption!
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
I am on TWRP official,Magisk rooted,Not Encrypted,LOS 17.1, my Fw MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1
[OnePlus 3 & 3T Cross Device Development] mk_1996:
VOLTE works fine for me. JIO works,Vodafone works. do a clean flash. Flash the latest 9.0.6 package for your device(it should be specific)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Switch LOS recovery to TWRP recovery with a locked bootloader (BL) :

0. My setup : OnePlus 3T / FW 9.0.6 / ext4 / unencrypted / BL locked / LOS 17.1 build / Open Gapps nano / Magisk

1. Place the TWRP img file (.img) in the root of your /sdcard folder and rename it to twrp.img (or keep the original name but change it in the dd command below).

2. Enable Local terminal in Settings>System>Developer options>Debugging (see screenshot).

Note the Rooted debugging option has disappeared if the BL is locked ... so you can't use adb root !

(see [MENTION=2911853]BillGoss[/MENTION]'s post ... https://xdaforums.com/showpost.php?p=82169973&postcount=593)

3. Open Terminal app.

4. Enter the following code (see here - https://twrp.me/oneplus/oneplusthree.html)

$su
#dd if=/sdcard/twrp.img of=/dev/block/platform/soc/624000.ufshc/by-name/recovery
#exit

5. Close Terminal app and boot to recovery.

6. Enjoy

Note copying the img file to /dev/block/sde21 fails with a locked BL.. but I don't know why ?

Because it works with an unlocked BL (see [MENTION=8966809]Hazbelll[/MENTION]'s post ... https://xdaforums.com/showpost.php?p=82176795&postcount=609)

Edit: As a reminder (unencrypted only), you can lock or unlock at will your BL via fastboot without loss of data but a re-lock BL does not restore the screen lock (for me, a pattern) and fingerprints.

Note:

- it works with TWRP recovery but I have not tested with LOS recovery (as I am not sure it will work.).

- if you forget to delete your fingerprints and screen lock before performing a re-lock, read this post :

==> https://xdaforums.com/showpost.php?p=82299329&postcount=877
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Volte works fine on three UK on OOS 9.0.6. you might have to switch it on using *#800#*. Sadly no vowifi which is so annoying

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

Anyone having issues with logging in with your Google account at the moment? Tried to access a Google calendar invite but on the login page you cannot fill in your email address ass the keyboard doesn't open up (using gboard). It also happens when I try to use Google to logon to raise a bug on GitHub.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Could you share the details of 9.0.6 package and steps to flash?

I am on office TWRP, LOS 17.1, Magisk root, Not Encrypted
[OnePlus 3 & 3T Cross Device Development] knpk13:
Not sure what you're having trouble with exactly. Just flash it in TWRP like you flash a ROM. Other people have linked the download page for the firmware package as well. Keep in mind 3 and 3T have different firmware packages. Since you mentioned you formatted data and clean flashed, might as well flash the original (unmodded firmware).
[OnePlus 3 & 3T Cross Device Development] :
General note (not only the quoted posting is meant):

It's very important to specify the carrier exactly. The shortest and most specifc way is by the the mcc/mnc (mobile country code / mobile network code; look at your active apn setting). I belive that vodafone works for you: e.g vodafone.uk (mcc=234 mnc=27) is known to work, but vodafone.de (mcc=262 mnc=02) is not.

To help the device maintainer to fix e.g. apn settings and/or carrier settings (if volte is working on oos but not on los) it's mandatory to exactly determine the carrier (and/or subcarrier).
[OnePlus 3 & 3T Cross Device Development] :
https://www.mcc-mnc.com/ could probably help for people trying to get it working
[OnePlus 3 & 3T Cross Device Development] thesplitter:
To test VoLTE get a o² SIM, I too am in Germany, got a prepaid o² SIM just to test VoLTE because Vodafone offers it only on contract SIM cards
[OnePlus 3 & 3T Cross Device Development] tiga05:
I am looking for an option to disable the numbers in the aosp keyboard. I am pretty sure the upper row of numbers were disabled with in Android 9 and AOSP keyboard. Did I miss an option or is this just not possible? Or maybe its possible to change something on config file level?

Here is a screenshot of the row i mean:
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
It should be on the Settings-System-Languages and Input somewhere...
[OnePlus 3 & 3T Cross Device Development] :
I use a contracted sim. My dataplan has volte enabled. I know volte is working for mcc=262/mnc=07 (or 08; don't remember exactly). I don't need to test again.

Did I mention, that's mcc=262/mnc=02 what doesn't work for volte on oos, los and other custom roms?

I've been through this for over three years - I've fixed volte for some carriers as everybody can see in the los-15 and los-16 threads. I've explained many times, that if volte isn't working on oos it can't work on custom roms. I've explained many times how to debug/test if volte is working on oos but not on los.

Since I would mutate to a werwolf and start howling, if explaining again that volte works for one mcc/mnc double but not for another, I withdraw from all volte conversations.
[OnePlus 3 & 3T Cross Device Development] tiga05:
Well. I searched it multiple times and was not successful.

I took a quick look at my old I9100 with LOS 11 and AOSP Keyboard installed. There it looks like this per default:

But on this device I can not find an option to turn it off. :mad:

In my opinion: There is no option to enable/disable this. The devs just changed the settings internally. Maybe I can do something via config file? But where can I find such config file?
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Which nightly are you using? I have just installed 20200421 and as default i do not have these numbers on the keyboard....However i was restore data backup from Lineage 16 as well...

I remember i was suffering with this issue on Lineage 16 as well but how i remember it was nothing to done with config files. It was on the settings somewhere...

---------- Post added at 04:59 PM ---------- Previous post was at 04:47 PM ----------

Did you try languages & input Keyboards tab Virtual keyboard and tap on AOSP and you will see Preferences Appearance & Layouts Advanced etc.
[OnePlus 3 & 3T Cross Device Development] tiga05:
[MENTION=4140321]tyler19820201[/MENTION]

Well... I thought I could find someone here in this thread who have the same phone and also have LOS installed. I think there is a high chance for this in a dedicated LOS thread for the oneplus 3 smartphone :D. This person could watch for this setting and tell me wether for some reason I miss this setting or he tells me there is no setting for this.

You tell me there should be something in this menu. But is it there on YOUR smartphone or not? Of course I already searched this menu you mentioned (language and input -> aosp keyboard and then settings/layout/advanced and so on) . But i could not find anything.
[OnePlus 3 & 3T Cross Device Development] :
It's not really straight forward (yep, I apply for the euphemism of the week ;) ):

For a German keyboard, while System default language is English:

Settingd->System->Languages & Input->Virtual Keyboard->Android Keyboard (AOSP)->Appearance & Layouts->Custom input styles->+sign (opens Add Style Dialog): select Language: German; select Layout: PC

Tap on the <- sign; then Android Keyboard (AOSP)->Lanuage->Disable Use system languages->scroll down and select German as well as German (PC)

Open something with text input. After the virtual keyboard is shown pull down the notification and tap on Change keyboard: you should see (among others): German (which is w/o numbers line) and German (PC) whoch is with numbers line.

As stated: not really straight forward... ;)
[OnePlus 3 & 3T Cross Device Development] tiga05:
Thank you [MENTION=4405529]nvertigo67[/MENTION] for your explanation. Unfortunately I found a lot of how to's in the internet about showing a line of numbers like you described. But my problem is: I dont want see the line of numbers.

So, do you have the line of numbers by default like this:

Yes or no? Do you know how to disable this red marked line with numbers? This is all I want to know.:( Because this is not the PC keyboard like you described. Its the QWERTZ keyboard.
[OnePlus 3 & 3T Cross Device Development] Dirk:
No. Assuming that 'anomalous behaviour', whatever the cause, is exactly what the poster is trying to test, then what he's after is a bootable system post-update that is stable enough to test the app on.

I'm not going to attempt to understand why anyone would need to test an app in this way. If we accept that it's impossible to go from 9 to 10 without a clean install, then nobody will ever need to know how a particular app behaves after the update, because nobody will ever be able to find out.
[OnePlus 3 & 3T Cross Device Development] :
OT:

[MENTION=1763460]Dirk[/MENTION]: I know I've ripped that from the context, but it's a great quote to start from.

That depends on the definition of "has been possible".

If you want a stable and issue free expirience, history has proofed it's not possible (i.e. the awesome issue at the beginning of official(!) 16.0 builds, which only has shown up after dirty migrating from 14 to 15 to 16, or all the "pahantom"-issues solved by clean flashing).

It's always the same if a new major version shows up: the strongness of the wish to dirty migrate, is indirect proportional to the knowledge... ;)

Considering this is still an experimental build, dirty migrating is asking for trouble. In the end clean flashing is less time consuming, then dirty migrating and debugging.

If there's more trouble then knowledge our all time is consumed.

[MENTION=1763460]Dirk[/MENTION]: these are general thoughts on dirty migrating. If one needs to know how an app behaves in a dirty migrated environment, you are completely correct: there's no other way to find out, then going that way.
[OnePlus 3 & 3T Cross Device Development] percyylin:
Thanks for all the replies.

Oneplus 3T is my personal old phone and was rooted before.

My main purpose is verifying our app's behavior while Android upgraded from 9 to 10.

Since Android 10 we can't get IMEI and something else which is part of our device identification.

In this version of the app, we privately stored the device identification info and I want to verify all mechanisms work fine in Android 10 with next version of app.

User scenario: this version of app + Android 9 --> this version of app + Android 10 --> next version of app + Android 10.

I tried using Titanium Backup to backup the app and it's data in Android 9 and restoring it in clean-flashed Android 10 as Imnoa suggested.

It's in vain since we can't restore the pre-stored device identification info which was encrypted by a keystore key that would be wiped I think while System partition was wiped.

I think I need to find some other ways...or phones.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
You could try backing up the app using this tool I don't know if it function in another way as Titanium does, but it might be worth a shot
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Hi, I've found the following here: LINK

Maybe we can put this Information to post #1 or #2 of this thread.
[OnePlus 3 & 3T Cross Device Development] felixchris:
Coming back to NFC, can confirm it is not working.

Gpay doesn't register on terminals, Android Beam on other nfc phones also does not work.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Hmm.

- I've never seen the installation errors mentioned in the quote.

- Our Los install script doesn't check the values of build keys - it simply overwrites the system partition.

- Changes to system configurations between versions is one of the reasons for clean installs.

- Changing the keys in platform.xml (which is what the mentioned script does) won't fix changes in configurations.

So, from my perspective, this quote is only going to cause issues. If people follow the instructions they'll think that they can safely do dirty flashes across version changes, but the instructions don't actually make that possible.

I can tell you from personal experience that a dirty flash of Los 17 over Los 16 will not boot - I ended up back in TWRP due to Rescue Party.

The recommendation, as usual, is to do a clean install across major version changes.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Pretty sure that script is for flashing an official LOS build over an unofficial LOS build, and vice versa (of the SAME major Android version). That's when you encounter the "incompatible data" error. (I've had that on my OnePlus 2 a while ago IIRC). I'm not a dev, but my understanding is that it's because of different build keys or something.

The script is not for upgrading major Android versions. I'm not sure which use case [MENTION=8530490]Not-Aus[/MENTION] is advocating using the script for. Edit: Prob upgrading, considering there are no official LOS 17 builds to switch to or from yet.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Thanks for your answers.

I wanted to help my previous posters who weren't able to upgrade from official LOS 16 to unofficial LOS 17. I thought it could be because of the release keys.

In the past I was able to flash successfully official -> unofficial and vice versa with these scripts.

Regards :)
[OnePlus 3 & 3T Cross Device Development] chtitlou:
Really nice to see the new build of today.

However flashing it ended up to a bootloop (dirty flash, only cache wiped) -> Rescue Party in TWRP.

Wiping system partition beforehand solved the issue.

Will report bugs if I find some.
[OnePlus 3 & 3T Cross Device Development] immi803:
Any changelog for today's build?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Changelog is in the OP
[OnePlus 3 & 3T Cross Device Development] immi803:
My bad, didn't check op before post

Thanks :good:
[OnePlus 3 & 3T Cross Device Development] clavelm80:
I had to go back from Los17 (25/10) to Los16 because Android Auto was blocking the phone when connected to my car. Auto was unusable and I had to hard reboot my phone. Maybe it's fixed in the new release?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
So since backuptools is broken, I also need to flash the gapps package while dirty flashing the new build right?
[OnePlus 3 & 3T Cross Device Development] chtitlou:
I forgot that... It should be the reason why I entered bootloop... Flash gapps whatsoever if you consider flashing.

Besides, I can confirm wifi hotspot works fine. No soft reboot and data flows flawlessly now. And indeed Safetynet check passes.
[OnePlus 3 & 3T Cross Device Development] geiszla:
Does this mean that I can't set SELinux to permissive, or that SELinux is set to permissive by default in this build?
[OnePlus 3 & 3T Cross Device Development] Tolyan009:
yes, otherwise you get a bootloop
[OnePlus 3 & 3T Cross Device Development] The shiny beast:
Are you the gcam man? If so, thanks a million for your work and your latest works fine and dandy on this build.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
[MENTION=4405529]nvertigo67[/MENTION] i have flashed firmware successfully followed by LOS17.1 and stuck at PIN. after booting into system..i have read somewhere to disable the PIN but cannot find the thread..any help here
[OnePlus 3 & 3T Cross Device Development] :
That's why I've explained that's for German. Maybe you need to add something else, but thats the way I can change between number line and none number line. You asked for the setting and I tried to answer, which settings are working for me - there is no explicit number line setting. See attached screenrecord, that way I can disable that line.
[OnePlus 3 & 3T Cross Device Development] :
Fpr lockscreen:

https://xdaforums.com/showpost.php?p=82299329&postcount=877

If you mean secured boot passphrase: format data.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/

meanwhile found this and able to fix..and flashing fw from previous post didn't help to retain VOLTE :(
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Yes i have OP3T with LOS17 and i do NOT have these numbers as default. My keyboard settings are american english and for system language i use english and hungarian. apart of this i have not changed anything on settings so no clue why you are getting this numbers. All i can say do a nandroid backup and do a clean install with factory reset and check this issue on a freshly installed OS.

---------- Post added at 07:31 PM ---------- Previous post was at 07:16 PM ----------

If i put SIM card it does not recognize it at all. Does not find the network and no any kind of mobile data available. (3G 4G). Also if i try to connect to my network manually does not work. I was trying with 4 different SIMcards. Also was check that my phone has got issue with this so i went back to LOS16 and everything works perfectly. However LOS17 nothing. I was trying the last 4 nightly already and has got the same issue with all of them.
[OnePlus 3 & 3T Cross Device Development] saspipi:
Yep, strange issue. If I just start GMaps GPS locks great but whenever I start a navigation (by car) it keeps searching for GPS, and rarely jumps to the right location but then searching again... So navigation doesn't work at all. With other nav apps it's just laggy and slow.

That is for 16-04 build.

Now updating to 21-04.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Stock web browser app (Jelly) :

FYI, the previous Jelly reworks prevented interaction with text input fields in webpages - clicking on them doesn't bring up the IME.

The latest build ... lineage-17.1-20200422-nightly-oneplus3-signed.zip ... fixes this issue.

==> https://www.lineageoslog.com/17.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] Eggstones:
I have the same problem in both jelly and Chrome.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
You have or you had the same problem ? ... because build 0422 just fixed it.
[OnePlus 3 & 3T Cross Device Development] randy_crash:
Shifting to lineage os

I am using havoc os on my oneplus 3t. I want to shift to lineage os but the kernel is modified in havoc os. So do i clean flash lineageos normally or do I change kernel somehow?