yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there,

I updated to the latest version of LOS 18.1 on my OP3. My phone is encrypted but when it's starting up, it doesn't ask for my password during boot.. Same thing to access TWRP. But in the security preferences, it says that the phone is encrypted...

Is it normal? It doesn't seem to be.

Thanks!
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I've been wondering the same thing. I assumed that the encryption was changed to file-based encryption (FBE), which means that the encryption key is not needed for files encrpyted with device key. But now that I checked

getprop ro.crypto.type

, it returned

block

. This means that the whole disk is encrpyted (FDE), which requires unlocking every time you boot the phone normally or to recovery. The thing is, I don't need to unlock it in either case, i.e. anyone with physical access to my phone has access to my files as if there were no encryption.
[OnePlus 3 & 3T Cross Device Development] [GER]Roxxor:
As far as I understand, the device is encrypted with a key in the Qualcom security chip. If you do not set a PIN/Password, then the security chip just hands out the key without checks and the phone can "unlock itself". This is still handy if you factory reset your phone: The security chip deletes the key, and the data can not be recovered (in contrary for it just plainly being written to the flash without encryption).

You have to set a PIN/Password in the security settings. As soon as this is set, you wont be able to decrypt without it. Thats also why you can cahnge the Pin! If the Pin would be your key, all data would have to be reencrypted everytime. But as it is just a Pasword for the real Key to be unlocked, it may be changed.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I am using a pattern lock. I'll try if changing to PIN or password helps.

For reference, I use Magisk, and I did a dirty upgrade from official LOS 17.1 and haven't noticed any other issues or weirdness.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
OK, I managed to sort it out. I went on to change the screen lock method, and I noticed the following message about accessibility services:

I had set up an open source app called FakeStandby as an accessibility service. I went on to disable that, and the message from the screenshot disappeared.

Then, I disabled screen lock altogether and set it up again. Now the devices asks for unlocking when I reboot.

E: There's also a mention about the device no longer using screen lock to enhance data encryption when enabling an accessibility service.
[OnePlus 3 & 3T Cross Device Development] quotendepp:
Hello folks,

beginner here so my question might be answered somewhere, I'd just like to make sure to do it the right way and there's so much information over the years:

I flashed LineageOS 18.1 on my OP3T and everything works fine, only safetynet doesn't pass. I'm not rooted, but my bootloader is still unlocked, so I suspect it's that. I read in this thread that some of you are using LineageOS with locked bootloader. What's the current right and safe way to achieve that?

Thanks a lot in advance!
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
1. First and most important, you have to have a current TWRP installed.

2. Locking the bootloader is doing a factory-reset, all your data (also data/media !!!) is wiped.

3. There was a problem with encryped phones and OTA updates, when the device rebooted for the OTA-update, decryption was failing/missing and the device went into a boot-loop :-(. Never dared to check if that was fixed, always downloaded the updates on PC and flashed via sideload.
[OnePlus 3 & 3T Cross Device Development] rohan164:
yes, working, you need to add some code in build.prop file every time when you do an OTA update.

the code is available in this thread, search for it, you will get it.

volte will not show in status bar after adding the code to buidld.prop. but it works.

to test it, turn on the data & make a voice call, if data is not disconnected during your voice call, that means VoLTE is working.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Look here.

https://xdaforums.com/t/rom-official-nightly-lineageos-18-1-for-oneplus-3-3t.4230665/post-85054297
[OnePlus 3 & 3T Cross Device Development] 02rajesp:
Mobil install custom rom oneplus3
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Its because Oneplus added a T-Mobile carrrier profile. Casual could active VoLTE way before but the step where to advanced.
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Where did you read about this?

Usually lineage cannot boot with locked bootloader.

That´s basically not working because the bootloader will check the rom for a genuine signature.

Obviously only official OOS has this signature so with a locked bootloader, the device won´t boot up.

This is actually the intention behind all this bootloader locking and unlocking.

However safetynet should pass.

I´m rooted with magisk and haven´t changed the rom fingerprint so safetynet should work.

However i´ve seen cases with two identical devices running the same software configuration but one of the two simply failing safetynet for no reason: After a fully clean flash it was fixed so i suggest trying this first.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Thats wrong for this device. LineageOS can boot with locked bootloader, as the key is known.
[OnePlus 3 & 3T Cross Device Development] malerocks:
There are comments in this thread that indicate you can have a locked bootloader. You have to unlock it for the very 1st install and after finishing the installation, you can lock it again should you wish to.
[OnePlus 3 & 3T Cross Device Development] batmanfeynman:
Hi everyone. I am facing Issues with sending SMS with JIO (An indian carrier with LTE only network).

I have 2 sim cards: One from JIO, a 4g only carrier and another from Vi (Vodafone) which has 2G/3G/4G. I flashed Lineageos first more than a year ago and everything was fine. But sometime around april this year SMS stopped working just for the JIO sim. Calling and Data work fine. I am not sure but i think I updated(17.1 -> 17.1) before this happened. Today i finally decided to investigate this. I tried the JIO SIM on another android phone as well as an iPhone and it works fine. but on my OP3T, it refuses to receive or send SMS. The Vi SIM doesn't seem to have any issues.

Another interesting sidenote is that if i remove the sim from the iPhone and put it in the OP3T, it doesn't work until i reboot the OP3T!

Can someone help me figure out what the problem is?

I tried updating to 18.1 today. It didn't solve the Issue. So currently I am on 18.1
[OnePlus 3 & 3T Cross Device Development] Chris_0147:
Hello I would like to know about a very stable ROM to play since I will buy this phone in a short time there is a compatibility problem of some ROMs with the OnePlus 3T
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I don't think it is worth buying the 3T. This phone is too old.
[OnePlus 3 & 3T Cross Device Development] :
It is not my intention to hyjack this topic, though when the op3t does not have any issues and the battery is okay then it still is a very good phone, though not for heavy gaming anymore. ..

Talking about and rom to play with; Xtended is a nice and stable rom with a lot of options to play with. Lineage is also very good and does have by far the largest user base though much less options to play with.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I think the phone is definitely worth buying if you can find one cheap enough. It's still fast enough for daily use. I would take op3 with this rom any day over a new phone with manufacturer-locked Android.

The age is a pro in that you should find dirt cheap ones at this point. There are two drawbacks, however. The batteries are no longer new (mine is still good enough for normal use), and there's a common HW issue with rear camera focusing. It's a bit of a roulette when buying a used device.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi,

I can't find the gps.conf file, well I don't know how to look for it and edit it. 😅

Could you tell me how to do it?

I am using LOS 18.1 on my OP3 without any google apps and the GPS takes a lot of time to find me (like 5-10 minutes and sometimes it doesn't find me at all). And my phone is rooted.

Thanks!
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I believe the path is /system/vendor/etc/gps.conf

Use any file manager that knows about root. For example Amaze from F-droid. It also includes a text file editor.

I would suggest using pool.ntp.org since that seems to find the closest server for me (noticeably better than the ones with the continent).
[OnePlus 3 & 3T Cross Device Development] snyperius:
Just like Hemuli said.

Although I have a few things to add:

I use Total Commander (it's as lightweight as a root file explorer can be and does everything I need without any unnecessary extra features; you can also download it from apkmirror and install it manually, although that way it won't update automatically).

And if you don't travel abroad much, you can find the active NTP servers in your country on https://www.ntppool.org (active servers list on the right-hand side of the page). I find it even faster than letting the pool come up with the correct server. Navigate to your country's servers and copy-paste their address to the top of the NTP server list in your gps.conf file in the same format as the addresses that are already there (NO '#' AT THE BEGINNING OF THE ADDED LINES!). Don't forget to save the file.

This way my phone gets a GPS fix in less than half a minute indoors (outdoors it just takes a few seconds) with the "GPS test" app. (The "GPS status & toolbox" app used to be better, but now it takes ages for it to get a fix for some reason.)

Also, make a backup of the modified gps.conf file so that you don't have to edit it after every system update. Just copy it in /system/vendor/etc/ and overwrite the original file.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Thank you everybody for your answers!

Are you using Magisk to get root? I do and can go to /system/vendor/etc/ with Amaze or Ghost Commander, being root, but then I can't modify the file gps.conf, it doesn't save (opening it with Amaze text editor or Ghost commander text editor), I don't know why... If you have a solution, I'm interested.

Thanks again!
[OnePlus 3 & 3T Cross Device Development] snyperius:
Try Total Commander. Select the file, "Edit file", add the lines, tap the save icon, allow everything it prompts for and that's it.

Or copy it to a folder that doesn't require root access to modify its contents (like the Download folder, for example), modify and save it there, then copy/move it back to its original location and allow the file explorer you're using to overwrite it.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I have a 3T, will be using that to test out Android 12.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
As a 3T owner in Scandinavia, I disagree. I missed some pretty good standards and eploits. I cant hack VoLTE on, Oneplus didnt add the full connectivity stack that was possible, I and mnay got scewed by Oneplus with the leaks, OxygenOS was bad becuse of bad code, OP should pick a phone with up to standard. 3G is shutting down and the phone isnt supported.
[OnePlus 3 & 3T Cross Device Development] malerocks:
I think it's fine to keep using it if you have one and slap on custom ROMs, etc. I definitely wouldn't buy one anymore. Even when buying a used device, I will prefer a more modern one.
[OnePlus 3 & 3T Cross Device Development] Ran94:
After every update, my button settings and gestures are not working. I need to again disable and enable them. Is this a issue for everyone?
[OnePlus 3 & 3T Cross Device Development] snyperius:
No.

Only weekly kernel panics for me
[OnePlus 3 & 3T Cross Device Development] Ran94:
Oh, I'm using OnePlus 3. I recently installed LineageOS and updated with nightly builds twice and this happened both the times.

Even though "Swap Captive buttons" is enabled after the update but it works as though the buttons are disabled.

Same with Gestures. I changed "V" gesture to enable/disable flashlight, but after the update camera opens instead of flash. (on ux it still shows flash though)
[OnePlus 3 & 3T Cross Device Development] snyperius:
Which ROM was installed before LOS? Was it a clean install of LOS? Is the display of your phone the original one or was it replaced by the official OP repair shop?
[OnePlus 3 & 3T Cross Device Development] Ran94:
Yes It's a clean install. Yeah I replaced my display by Official OP repair shop.
[OnePlus 3 & 3T Cross Device Development] [GER]Roxxor:
Anyone knows how to get VoLTE working for Telefonica/O2 Germany? Tried a different build prop, didnt work for me. Now that all 3G is shutting down, I experience horrible call experiences.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
I had flashed OOS 9.0.6 and followed a guide like that:

[Guide] VoLTE + VoWiFi working for German carriers

[UPDATE] Updated QPST version + new how to Exciting news, jamal2367 from https://jamal2367.com has developed a way to get VoLTE + VoWifi working for many countries + carriers. If you are on Vodafone and you are having problems with...

xdaforums.com

Unfortunately the phone defaulted back after a couple of minutes. Later on I read that deleting the files in /system/something/or/other prevents that from happening, but I had already restored my backup.

Hope somebody can shed some light on this.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Do you mean this ?

https://xdaforums.com/t/rom-official-nightly-lineageos-18-1-for-oneplus-3-3t.4230665/post-85546663
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
No that didn't work for me. VoLTE seems different depending on provider/location. I had to change the provider profile with the PDC tool.
[OnePlus 3 & 3T Cross Device Development] Domovoi0ng:
Thank you deeply!! Waiting patiently on stable release to install.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Looking at the mbn repo there are carriers specific and common mbn. There have been reports of people activating 4G calling out of the box thanks to Android 11 API.
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Have you had any success with importing mbn files using PDC tool?

For some reason, when I click import and select an mbn file, nothing actually happens; EfsTools didn't help either.

I contacted my carrier and I got a response stating that VoLTE is enabled by default, but my phone shows "IMS not registered" in *#*#4636#*#*
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
No I didn't import anything just used the ones that were directly available.

Did you unload the default one beforehand and did you put the phone in Full-Port Mode with *#801#?

But like I said even though it said VoLTE (or was it 4G+ ?) in the OOS status bar and there was an HD symbol when making a call the phone defaulted back after a couple of minutes. Wether that's because of the wrong mbn profile or because the phone writes something to system or efs I'm not sure.

Sure if you're lucky but if it would be that easy I bet dianlujitao would've already implemented it. I mean when I tested my Sim in a Oneplus Nord VoLTE worked in seconds but I guess it uses some sort of a RIL standard handshake that goes straight to the firmware. But I'm way out of my depth here.
[OnePlus 3 & 3T Cross Device Development] Immortalis:
No, I used adb method to enable diag mode, even when I was on OOS for a moment, but PDC tool did detect my phone nonetheless, so I'm not sure what's wrong. Is it important to use Engineer Tools built in OOS?

I even used unbrick tool to nuke entire system, go back to OOS 6 and start over, unfortunately it didn't help.

But I did unload the default profile first, yes.

Anyway, I'm grateful that LOS exists, OOS was laggy as hell in my experience
[OnePlus 3 & 3T Cross Device Development] borisSweden:
For some reason, phones are using a universal IMS/mbn/3gpp approved 4G registration since last year. If its a module/API, surely it can be ported. Phone with 820/821 arent that much supported, only a small group of carriers sold the phone because of hype. Also the Qualcomm mbn site isnt updating its repo

GitHub - JohnBel/QualcommMBNs

Contribute to JohnBel/QualcommMBNs development by creating an account on GitHub.

github.com

But there is another more archaic solution. Its the Sony modem port solution but Jamal stopped adding mbn files.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Get a root explorer from F-droid.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Mmh I guess that should work too but you I can only tell you that it worked briefly with *#801# / Factory Mode. Maybe you didn't run PDC as administrator?

FYI atm I'm back on OSS atm
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Any useful hint on how to get / generate the rawprogram_unsparse_without_qcn.xml and Patch0.xml for QFIL?
[OnePlus 3 & 3T Cross Device Development] Immortalis:
I tried with or without admin privileges, same thing happens
[OnePlus 3 & 3T Cross Device Development] snyperius:
There probably won't be a stable release. LOS 17.1 never had any. The weekly builds are stable and reliable enough for daily use
[OnePlus 3 & 3T Cross Device Development] borisSweden:
No. The QPTS thread on the Hacking forum isnt that updated. Only guy who gives out QPTS instruction is this guy from Finland

MT-TECH.FI - IT Blogi

Tietotekniikkaan ja tietoverkkoihin keskittyvä blogi.

mt-tech.fi
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
I highly recommend making backups of your EFS partition in every way possible!

All right, seems like I got it working for O2 Germany:

Basically I followed this guide in LineageOS directly:

[GUIDE] Enable VoLTE/VoWiFi on LineageOS 17.1 for EU carriers Oneplus 6T

As Profile I selected H3G_DENMARK_COMMERCIAL, the options are very limited:

No module, edited build.prop or configured APN.

Edit: This Method worked for my 3T but not for the Oneplus 3 since H3G_DENMARK_COMMERCIAL is missing.

Edit2: The Method I got VOLTE working for another Oneplus 3 was as follows:

I installed the lastest OOS (9.0.6) to get full Engineering Mode working and followed this guide:

OP6, 7, 8 - Freedom Mobile, Koodo, Telus, Bell - VoLTE and VoWiFi Calling - WORKING!!!

Luckily the EFS Tools / mbn part wasn't necessary as there where more options then before:

So I proceeded like I did in the LineageOS 17.1 VOLTE guide in the first part of my post, selected H3G_DENMARK_COMMERCIAL, made a backup of EFS and restored LineageOS with OOS EFS. That worked briefly but resulted in connection issues and eventually reverted back to default.

The upside was that,

using only one SIM (Sub0)

, H3G_DENMARK_COMMERCIAL was still active on the Sub1 and now visible in PDC using LineageOS

From there on it was simply a matter of using the LineageOS 17.1 VoLTE guide again.

As for workarounds I couldn't get step 3 (adb shell) working so I used Terminal Emulator for the setprop command.

Also to prevent the phone from defaulting back to the OEM-Overseas profile I deleted the respective OEM_ files in /system/etc/firmware/mbn_ota/

P.S. Take this with a grain of salt I'm obviously not a dev and used a more ham fisted approach i.e. took the risk of having a paper weight.

I highly recommend making backups of your EFS partition in every way possible!
[OnePlus 3 & 3T Cross Device Development] Immortalis:
I was somewhat following this guide and got it working too, on a profile "Volte_OpenMkt-Commercial-CMCC" (Play Poland).

Importing profiles doesn't work, and I'm not sure if modifying NON-HLOS.bin made a difference.

I'll keep trying, maybe new profiles will show up in PDC.

But hey, if it works :D
[OnePlus 3 & 3T Cross Device Development] borisSweden:
I dont even get European profiles. Only US, Chinese and OEM test profiles.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Its possible but nobody is maintaining that trick. How do you parse Sony modem files? Who knows.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
So...I take you have a A3000. Yeah that's a problem and a half.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
No, its the A3003 as I live in Europe.
[OnePlus 3 & 3T Cross Device Development] :
A3003 is Europe or Asia:

android_device_oneplus_oneplus3/init/init_oneplus3.cpp at lineage-18.1 · LineageOS/android_device_oneplus_oneplus3

Contribute to LineageOS/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com

Obviously they are shipped with different efs profiles (since OOS firmware is the same, but results in different ürofiles shown in pdc).
[OnePlus 3 & 3T Cross Device Development] borisSweden:
How can I fix this?
[OnePlus 3 & 3T Cross Device Development] :
What exactly do you think is broken and needs fixing? The init extension sorting the different models seems perfectly ok to me.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
So I need to reflash my ROM? I do have a backup of my OOS efs portion. I could flash it over the hardened LOS ROM.
[OnePlus 3 & 3T Cross Device Development] :
Shouldn't result in problems, nor is restoring efs interfering with any rom.

BTW: before using pdc (or efs explorer) I'd strongly recommend testing backup AND restoring efs.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Well I also have hope that the autoselect mbn file will fix this year.

For real, why has there not been any attempt to master the Qualcomm settings? Do we need to make a cash bounty? Why no custom mbn files.

I remember from the LOS AMA that they don't use leaked code. But they still use the blobs. They should implement QPTS hack to the ROM so users can utilise every tech that is present in the SoC.

I'm not asking you, there should be some experts with a expired NDA.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
I found issue with 3G call. Wifi+3G sounds excellent and I get a high AMR-WB count.

Calling with only 3G is bad. I believe 3G has a bad dual channel data connection.
[OnePlus 3 & 3T Cross Device Development] snyperius:
3G networks are getting shut down all around the world. Your issue might be related to that
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Not that, I still have very good coverage for 3G. For some reason 3G cant do data and calling very good. When Wifi is connected(I dont have VoWifi yet in Sweden) the 3G connection isnt overloaded.
[OnePlus 3 & 3T Cross Device Development] hemantkarandikar:
After going thru hoops with flashing twrp I finally could flash lineage-18.1-20210920-nightly-oneplus3-signed.zip on my 1+3 running stock 9.0.6. The ROM flashing and booting was quite smooth and quick. I haven't really faced issues reported here like gps lock, VoLTE (Airtel). But I see the following -ves in Lineage 18.1 w.r.t. Pixel 2 running Android 11.

1. wifi doesn't switch to the strongest network

2. File transfer via Google Android File transfer Tool ( for mac) is erratic . It was pretty fast with Pixel2

Found that flashing twrp on fully stock 1+3 was problematic. I almost had given up.

When I tried to boot into the twrp ( 1st time), from fastboot by using power + Volume down nothing would happen or I would find myself fastboot.

Realised that I had to lock bootloader before traying to boot in twrp recovery. I have done custom rom flashing after a long time, so probably I didn't realise the need for re-locking bootloader.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Another option to make TWRP stick is to flash Magisk. Android File Transfer isn't maintained anymore personally I use MacDroid these days, it's not free though. Can't say anything about the Wifi issue since I don't use mesh networks.
[OnePlus 3 & 3T Cross Device Development] hemantkarandikar:
Thanks. Can one flash magisk without a custom recovery like twrp and root? If yes, can you point to the procedure? I searched but I am not sure.