yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It'll be under Settings>Display. I can't show you exactly because I'm running 18.1 where it's called Prevent accidental wake-up.
[OnePlus 3 & 3T Cross Device Development] KAPTOIIIE4KA:
This is not the setting you want, it only prevents the screen from unlocking when you try to unlock the phone using your fingerprint.
[OnePlus 3 & 3T Cross Device Development] :
Sure?

DT2W works if the proximity sensor is covered (lay your hand on the upper front part of device)? Same for notifications (i.e. create a notification in google keep with reminder or let someone send you a sms): is the screen switched on, when you cover the proximity sensor when the notification is received?

BTW: Pocket mode is NOT about unlocking the device, but about screen on!
[OnePlus 3 & 3T Cross Device Development] KAPTOIIIE4KA:
When a notification arrives, the screen still turns on even if the proximity sensor is closed.

On firmware OxygenOS 9.0.6 "Pocket mode" works.
[OnePlus 3 & 3T Cross Device Development] :
@All:

Can anybody confirm DT2W is waking up the display with covered proximity sensor?

@KAPTOIIIE4KA

If so, please open a bugreport (https://wiki.lineageos.org/how-to/bugreport ).

If not, it's most probably a setup specific issue and you are on your own.
[OnePlus 3 & 3T Cross Device Development] christantoan:
Can't confirm here. Screen stays off after DT2W when the proximity sensor is covered.
[OnePlus 3 & 3T Cross Device Development] KAPTOIIIE4KA:
And if the phone is in your pocket and the screen starts ringing, the screen still does not turn on until you take it out of your pocket?
[OnePlus 3 & 3T Cross Device Development] christantoan:
I only tested using Signal call as my phone doesn't have any SIM cards.

Unfortunately, the screen is turned on and responsive to touch when a call is incoming. I tested this by covering the sensor and making sure DT2W doesn't turn the screen on.
[OnePlus 3 & 3T Cross Device Development] KAPTOIIIE4KA:
So the function is working for you?
[OnePlus 3 & 3T Cross Device Development] christantoan:
For DT2W, yes.

For calls, no.
[OnePlus 3 & 3T Cross Device Development] KAPTOIIIE4KA:
I would like it to work the same way for calls, because of this, I had to install a different firmware.
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
I won't call that a bug, screen on for incomming messages is a feature (isn't it silent, or is light disturbing your ears?) and, to be honest, it's the same for all 5 (different) devices used in my family. If you get to many notifications lighting up your screen, you should rather rething your notification policy ;-).

Greetz

Kurt
[OnePlus 3 & 3T Cross Device Development] :
On los 16 pocket mode was working for calls, too. May I ask which dialer you are using? Do you use the rom's shipped one or do you use the gapps replacememt?

Settings->Apps & notifications->Show all XX apps->Phone->Advanced->scroll down all the way

com.android.dialer (this is the shipped one)

com.google.androod.dialer (this is the gapps replacememt, if one decides to use a gapps package other then pico or nano)

Thanx for testing and verifying, especially since the original reporter wasn't very helpfull with his responses.

You missed his point. The way PocketMode (aka Prevent accidental wake-up) is intended to work is keeping of the screen while the device is in a pocket, to avoid accidently and unknowingly user interaction (i.e. swipe away a just received notification, answering or denying an incoming call etc.).

For notifications this means (depemding on configuration of notification) the notification sound is played, but the screen stays off.

For DT2W this means the screen isn't woken up.

For incoming calls this means the ringtone is played, but the screen stays off until you take the device from the pocket (while still ringing), then the screen awakes to normal incoming call state.

All of the above are mandatory (IMHO) features, as long as one doesn't use a flip-cover.

Though the behavior @christantoan describes (screen on for incoming call, though proximity sensor is covered) maybe a regression from 16 to 17 (or intended by los), I think it's more probable a setup related problem:

There are only two commits to pocketmode from 16 to 17. The first one is about PocketSensor registration (https://github.com/LineageOS/androi...c6fe2d34351f83c96131168f630b5133c328d0b88347d ) which obviously works - otherwise it wouldn't work for DT2W and notifications, either.

The other one (https://github.com/LineageOS/androi...c6fe2d34351f83c96131168f630b5133c328d0b88347d ) is related to the sensor, too: it's about file handling of the sysfs node for the proximity sensor, which works, too (see above).
[OnePlus 3 & 3T Cross Device Development] christantoan:
I'm sorry. As mentioned before, I didn't use dialer apps to test, just an VoIP call (via Signal) as my OP3T doesn't have SIM cards installed.
[OnePlus 3 & 3T Cross Device Development] :
Sorry, misunderstood that, I tought you've used the sip settings in the phone app for VoIP. (Could have sworn I've read sip... getting old... ;) )
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
TWRP 3.5.1 Released :​

TWRP 3.5.1 Released

TWRP 3.5.1 is out now for most currently supported devices.

twrp.me

​

Download twrp-3.5.1_9-0-oneplus3.img

Download page for twrp-3.5.1_9-0-oneplus3.img

dl.twrp.me
[OnePlus 3 & 3T Cross Device Development] cfli1688c1:
how do i swap the recent and back key?

** nvm, found it, search for swap in settings
[OnePlus 3 & 3T Cross Device Development] hellcat50:
Update: The dev unfortunately didn't answer, but that's not a problem because since the march security patch update, the app works again! So maybe it was a bug with the security patch itself which google fixed, idk. But it works again, that's what counts :)
[OnePlus 3 & 3T Cross Device Development] risheek7:
Airtel volte isn't working for me, however other networks are working just fine. (on both los 17.1 and 18.1)
[OnePlus 3 & 3T Cross Device Development] rohan164:
you are right. for airtel if you want volte to work, you need to modify build.prop . the modification is there in this thread.
[OnePlus 3 & 3T Cross Device Development] risheek7:
I tried that, it didn't do anything. It is really disappointing and annoying that no one is doing anything about this problem from such a long time, even tho a ton of builds have been released @dianlujitao could you please pay attention to this?
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Could you please be kind with the dev?

He is not payed to mantain this rom and you should be grateful that our old device is still receving official builds.

I'm sure that if he could fix he will fix, but please be patient.
[OnePlus 3 & 3T Cross Device Development] risheek7:
I am sorry that i lost patience after having waited from previous year. I didn't mean to be unkind and I respect @dianlujitao for what he does for our device.
[OnePlus 3 & 3T Cross Device Development] malerocks:
I don't know how to do this, but since it's all open source, can't someone (who knows how to) make the changes and commit to the repo for the next build?
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Is the Japanese just SBAS?
[OnePlus 3 & 3T Cross Device Development] server3249:
Will we get any more updates to 17.1?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No.

Continue here: Klick
[OnePlus 3 & 3T Cross Device Development] borisSweden:
GPSTest Database

Devices Manufacturer,Model,Name,Android version,API level,GNSS hardware year,GNSS hardware model name,Dual-frequency,Supported GNSS,GNSS CFs,Supported SBAS,SBAS CFs,Raw measurements,Carrier phase (getAccumulatedDeltaRangeMeters()),Navigation messages,NMEA,Inject Predicted Satellite Data Service ...

docs.google.com

Check this list. Maybe you can add QZSS or NAVCI instead.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
According to this tread for the Zuk Z2 pro, there is Galileo support

https://xdaforums.com/t/rom-8-1-0-s...xtended-rom-v5-8-z2-pro.3683238/post-76926203

Also maybe the Samsung Galaxy Note Fan edition(Snapdragon version/US) could support it. @nvertigo should check it out.
[OnePlus 3 & 3T Cross Device Development] :
For galileo:

Please read my previous posts and don't suggest devices w/o native android 9 (or better 10) blobs. The los 16 and 17 builds for the z2 don't use native z2 blobs, but kanged blobs, which doesn't support galileo... :(
[OnePlus 3 & 3T Cross Device Development] borisSweden:
What about the Samsung Galaxy Note Fan Edition(SD/US)? It was released the same time as the TAB S3.

Edit: it's the revised Note 7 that doesnt explode
[OnePlus 3 & 3T Cross Device Development] :
Did you check the prerequisites I've mentioned? What's the samsung model number? What's the los code name?
[OnePlus 3 & 3T Cross Device Development] borisSweden:
You know what, I got to existed that there was a US model of the Fan Edition. Actually it's the botched Note 7 so finding firmware will be impossible. But you asked model numbers so here they are:

Qualcomm Snapdragon 820 modelsEdit​

SM-N9300 (China Open Model)

SM-N930V (USA Verizon Wireless)

SM-N930AZ (USA Cricket Wireless)

SM-N930P (USA Sprint)

SM-N930T (USA T-Mobile US)

SM-N930R4 (USA US Cellular)

SM-N930R4 (USA Straight Talk)

SM-N9308 (China Mobile)

SM-N930U (USA Unlocked)

SM-N930A (USA AT&T)

SM-N930W8 (Canada)

BTW, would it be possible to find a solution in SD6XX series chips as the SD820/821 spec was passed to budget? There are many 14nm SoCs

Also after I looked at the GPStest database, a Google Pixel OG was spotted with QSZZ support, I have not confirmed this yet, I asked the OG Pixel forum.
[OnePlus 3 & 3T Cross Device Development] :
It's not possible to kang blobs from the firmware, if the firmware is not available/accessible.

I highly doubt blobs for other socs will work on msm8996pro/msm8996.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Is there anything not GNSS related that can be salvaged from other MSM8996/pro devices?

I have questions if you could kindly answer.

Is it the X12 modem that handles Bluetooth, cellular, GNSS, radio?

Is there a hardware requirement like a antenna for the other GNSS signals? The MSM8996/Pro supports USB-3 but we as users cant activate that speed because of Oneplus adding a proprietary USB port and blob for Dash charging. HW stops it.

Argument for the use of SD630,SD636,SD660,SD665,SD675 modem firmware is the use of Magisk Module firmware for the Aderno GPU. If its possible with that use case, there is a chance for it to work. Also it opens up more volte profiles to use with the Jamal tutorial instead of CNVParse of Sony modem firmware. playing around with EFS is hard.

Nearly all SoC using the X12 are the same, its just the 820/821 was rebranded and tweaked to be resold.

Or this can be summarized like the Oneplus 3 having support for Cat12 but Oneplus was cheap and only soldered to Cat6 with the X12 modem. Basically it's a X8 modem.
[OnePlus 3 & 3T Cross Device Development] S4turno:
The last 17.1 build (20210329) is about to be removed from LineageOS' website, so here's a copy/mirror in case someone needs it in the future.

lineage-17.1-20210329-nightly-oneplus3-signed.zip:

- download (sha256)

- recovery (sha256)

- torrent (build + recovery)

Hosted at the Internet Archive. Not the best speeds, but should remain online for a long time.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Sorry if the post is repetitive. I have been trying all options to get this working but no luck. I had moved from Official OxygenOS to Lineage OS 17.1 few months back on OP3. Unlocked boot-loader, installed TWRP, rooted using magisk(as some apps were not working with ROM).

After installing magisk and hiding the apps, some of the apps started working. But there are quite a few banking apps that are still not working. I am actually fed up with not being able to use banking apps. So need some help with it. Can I get answer to few questions? Please forgive they are noob questions

- I hid an app using magisk and later that app is updated, it stops working though it is still hid in magisk. Is this expected? What is solution for it?

- Can I update Magisk?

- There are still some apps not working no matter I hid, rename magisk. Any solution to it? Ex: HDFC, Citibank etc as in screen shot

- Can I update Magisk manager? Last time I hit of update magisk manager in the app and the app stopped working(doesn't open saying it is updating and it loops). I had to reflash magisk to get it to work again.

- Can any version of magisk be flashed on any device? Or is it restricted.

- How to fix ctsprofile error in safetynet? I now see Safety net api issue as well.

- Can we google for issues and use solutions recommended to other phones and apply to OP3 as well?

- Will upgrading OP3 to latest lineage OS lose media, data, magisk root?

- Can unrooting, locking boot-loader help? I read that doing so is risky and might brick the device.

My only aim is to use Lineage OS with banking and other apps intact. I do not need rooting etc for any other purpose. Is there an easier and long term solution than root/magisk etc? Any help will be much appreciated.

Please let me know if any more information is required.

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Solution can be to update Magisk or remove Magisk and / or lock the bootloader.

Maybe it will help to rename the TWRP folder.

Yes, please do this first! At first step update the Magisk App, as second step update Magisk.

Lets see if this problem still occurs after updating Magisk.

The "Magisk Manager" is now called "Magisk App". Yes, you should be able to update it. If not, just install it again.

It depends on. The Magisk page explains about restrictions.

But for our OP3(T): Yes, the latest version, please.

Lets see if this problem persists after updating.

Might depent.

Updating your LineageOS 17.1 to the latest available 17.1 will not lose media, data and magisk root.

Upgrading a 17.1 to 18.1 won't lose data, too but the system might end in a boot loop, in an unstable state and / or you might not be able to unlock it. So a clean flash to 18.1 is recommended. You would first have to backup all your data to a PC and then install your phone completely new.

Unrooting the phone can help, that should work without problems.

Locking the bootloader ->WILL<- make you lose all your data!!! Be sure to notice this!

Yes, sure. To make the most of it without Magisk, you could follow these steps:

1. Backup all your data to a PC and remember which Apps you need

2. Update TWRP to latest version

3. Update firmware to latest version

4. Lock your bootloader

5. Wipe all possible partitions on your device and format data

6. Install latest LineageOS 18.1 and the Google Apps addon package

7. Setup your device and encrypt it.

If you want Magisk, follow these steps:

1. Backup all your data to a PC and remember which Apps you need

2. Update TWRP to latest version

3. Update firmware to latest version

4. Wipe all possible partitions on your device and format data

5. Install latest LineageOS 18.1, the Google Apps addon package and the magisk.apk

6. Setup your device and encrypt it.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Thanks a lot for taking time and answering all the queries. After updating Magisk and Magisk app(to v 23.0), safetynet passes(even cts profile) and most apps are working(after hiding magisk). Any idea why Citi app doesn't work? Is it possible to debug?

BTW, how is the stability of 18.1 for OP3. Can it be used as a daily driver (when compared to 17.1)?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Maybe you can rename the TWRP folder, maybe you need to lock the bootloader, maybe both I don't know.

Attention, all data will be lost after locking it!!!

Its stable!
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Android 12 is round the corner. Time to upgrade my 3T. Unfortunately, Nitrogen OS has gone very quiet. I guess it is LineageOS 18 turn
[OnePlus 3 & 3T Cross Device Development] moto1022:
Hi, I hope this question is not posted before.

I'm unable to use PS4 controller on OnePlus 3T. Both Bluetooth & USB connections failed.

Any help is appreciated.

Thanks, regards.
[OnePlus 3 & 3T Cross Device Development] DjDeViL66:
Hi, my brother have an Oneplus 3 with Lineage OS 17.1 (October 2020) is it possible to share de last official release Lineage OS 17.1 ( I supposed in April 2021 ).

It's just for simple update thx for sharing
[OnePlus 3 & 3T Cross Device Development] DjDeViL66:
Thx, I missed it
[OnePlus 3 & 3T Cross Device Development] Max1306:
Does VoLTE works in Germany with the latest Lineage. Stock ROM do not allow VoLTE in Germany.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
How did you get CF value on the Oneplus 3T?
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Little late, forget about Galileo, looks like you maybe need to edit NV items with QPTS/EFS explorer. You see GNSS singals are like 4G signals, basically radio. But another promising possibibility is that the OG Pixel "supports" QZSS according to GPStest database.

GPSTest Database

Devices Manufacturer,Model,Name,Android version,API level,GNSS hardware year,GNSS hardware model name,Dual-frequency,Supported GNSS,GNSS CFs,Supported SBAS,SBAS CFs,Raw measurements,Carrier phase (getAccumulatedDeltaRangeMeters()),Navigation messages,NMEA,Inject Predicted Satellite Data Service ...

docs.google.com

Another problem is the Legacy GNSS HAL for LineageOS

android_hardware_lineage_interfaces/gnss/1.0-legacy/Gnss.cpp at lineage-18.1 · LineageOS/android_hardware_lineage_interfaces

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

github.com

There is no Galileo support.

But if Im uneducated and missed something, pls educate me on this issue nvertigo67
[OnePlus 3 & 3T Cross Device Development] :
What do you mean by "OG Pixel"? As far as I can see in the table ypi've posted all msm8996 equipped Pixels doesn't support galileo

Los oneplus3 doesn't use the legacy hal, but the caf implementation:

android_device_oneplus_oneplus3/gps 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
[OnePlus 3 & 3T Cross Device Development] borisSweden:
I didnt say look for Galileo my dude. I meant there is a MSM8996pro device supporting Japanese QZSS. Totally different. Pixel 1 2016 edition sounds better. look at line 107 and 110.

Is it better? We dont even get Carrier Freqency support with CAF. Also for the CAF blob to work with EU constilation, we need to edit NV values if we go by my theory. Its the same as opening a band , you open a GNSS band. The phone intercepts the EU signals but cant read them. If you do a adb shell dumpsys location, you will see a list of seen constellations.
[OnePlus 3 & 3T Cross Device Development] :
Got that wrong. I still don't get the benefit of QZSS for galileo.

Better then what? As far as I know, it's the only working solution (see OSS sources: https://github.com/OnePlusOSS/android_vendor_qcom_opensource_location/tree/oneplus/QC8996_N - los uses newer caf soirces). If the optons are working and not working, caf is the working option... Which is better, I guess... ;)
[OnePlus 3 & 3T Cross Device Development] borisSweden:
I mean its there. Also helps Oneplus 3/T users with better location in the far East. I dont know how to use EFS explorer for Galileo so the next best thing is QZSS. Instead of 3 you get 4 constellations if we dont count the mediocre SBAS support.

The setup is perfect. Android 10, MSM8996pro, Pixel.

But if you want to crack another nut there is the LG Q9, a 8996pro phone from 2019 with......BT5.0!

The 821 only supports 4.1 and we have 4.2. IDK what special sauce they used for that.
[OnePlus 3 & 3T Cross Device Development] :
I'm out at this point. Changing a radio profile with pdc is my limit - messing with efsexplorer without complete understanding of efs and efs editing seems to dangerous to me. I'be only a very limited understanding of the efs stuff.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Me to, I asked this guy https://mt-tech.fi/en/ who makes QPTS/EFS/QDXM tutorials. Doing backups is my limit. Also I cant decode the binary files. As porting baseband from SD6XX series is not adviced, I tought efs was the answear. I will have to read more about it.

But did you check the Pixel lead and LGs impossible Bluetooth implementation, I would guess ApTx would be gone.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Late question but what will devs do when its not feasible to keep using 3.18? Or will development be abandoned as the phone is old enough and not popular to work on. Either do EOL or go up the kernel version as it must be stable enough. If Oneplus software is the issue, open source blob alternatives should be reconsidered(now that OOS is EOL and obsolete, they should open source the software and release schematics after the ColorOS merge)

I know its Linux and has support forever but I wouldnt install Android 11 on my old Galaxy S2 i9100, 10 minutes of SoT isnt useful.
[OnePlus 3 & 3T Cross Device Development] :
3.18 still receives fixes, security updates and some backports (see https://android.googlesource.com/kernel/common/+log/refs/heads/android-3.18 ) I know of - at least - one dev, picking these in his sources (see the los microg builds of @MSe1969 ).

Source build rom devs take vendor precomplled software, when no source is available. By definition blobs are compiled closed source software. The term "open source blob" is oxymoron.

*lol* You are right. I just wonder, who will take the job to explain to oneplus and qcom to open source their software...

Since oneplus doesn't support op3/t anymore, even if you manage to convince the hardware vendors to open source their closed source stuff, this is irrelevant for op3/t.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
I tried, only got some upvotes and got buried by southeast asian (JIO)gatekeepers on that god forsaken 1+forum. Also getting a offcal dev to do a expired-NDA AMA is impossible as they wouldn't care. But they did release CyanogenOS code so there is hope, or we have to wait for a leak by a worker who hates OPPO.
[OnePlus 3 & 3T Cross Device Development] borisSweden:
nvertigo67 how is the japanese QZSS and LG BT5.0 going? Is it the same problem like EU constellation port, that they are kanged blobs?​
[OnePlus 3 & 3T Cross Device Development] Primokorn:
Stop posting this everywhere since OP3(T) doesn't support Treble at all.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
You probably did not mount /system, twrp does not mount /system by default
[OnePlus 3 & 3T Cross Device Development] bfm.95:
It just worked using fx file explorer manager

Thanks mate
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
file corrupted during upload, should be fine this time.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
New version works perfectly - thanks! Backed up and restored successfully both Android 9 and Android 10 roms.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Every time I try to delete the twrp file in my file manager, it doesn't work. Downloading a new copy just adds a number to it at the end. And rebooting doesn't help. Is something wrong with my filesystem? The files exist in the stock file manager app as well and are undeletable.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I had that problem too, try searching on the Nitrogen OS or LOS16 discussion, it was about disabling or deleting the data of the app Android Setup
[OnePlus 3 & 3T Cross Device Development] knpk13:
I know, the link in my post describes that solution. I tried it and it didn't work. Worked on Pie though.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Are banking apps working without magisk with the latest version especially from Germany?

For example DKB, Tan2Go, ...
[OnePlus 3 & 3T Cross Device Development] felixchris:
Can't confirm without magisk, but with and magisk hide no problem at all with the DKB app.