[ROM][Official][Nightly] LineageOS 17.1 for OnePlus 3/3T

[Not-Aus]

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?

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!!!

BTW, how is the stability of 18.1 for OP3. Can it be used as a daily driver (when compared to 17.1)?

Its stable!

 

[highdiver_2000]

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.

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

 

[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.

 

[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

 

[DjDeViL66]

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.

Thx, I missed it

 

[Max1306]

Does VoLTE works in Germany with the latest Lineage. Stock ROM do not allow VoLTE in Germany.

 

[borisSweden]

Nope, i'm in latest lineage 17 and still using GPS (USA Navstar) and GLONASS (Russia)

Edit: tried today and voila Galileo satelite

How did you get CF value on the Oneplus 3T?

 

[borisSweden]

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.

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.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

 

[nvertigo67]

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

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

Another problem is the Legacy GNSS HAL for LineageOS

android_hardware_lineage_interfaces/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

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

 

[borisSweden]

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

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.

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

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.

 

[nvertigo67]

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.

Got that wrong. I still don't get the benefit of QZSS for galileo.

Is it better?

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...

 

[borisSweden]

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...

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.

 

[nvertigo67]

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.

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.

 

[borisSweden]

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.

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.

 

[borisSweden]

In the end: if we'd have the choice between similary stable and compatible 3.18.y kernel and a 4.4.y kernel, I'd go for 4.4.y - as long as stability and compatibility differs, I'd go with the more stable and compatible kernel: 3.18.y. I'm not the most gifted kernel dev, if excellent kernel devs fail on making 4.4.y as stable and compatible as 3.18.y, I highly doubt there will be a break through in the near future.

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.

 

[nvertigo67]

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.

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 ).

If Oneplus software is the issue, open source blob alternatives should be reconsidered

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.

(now that OOS is EOL and obsolete, they should open source the software and release schematics after the ColorOS merge)

*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.

 

[borisSweden]

*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.

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.

 

[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?​