tdm

Do you actually have two SIM cards inserted? I believe Lineage has cleaned up the Qualcomm stuff for multi-SIM so that it looks nicer. That may include hiding options that are not available/useful.

I believe holding volume-down while powering on the device will bring up the fastboot menu. In there, you can use the volume keys to select recovery and then press power to boot. Note that if you see stock recovery instead of Lineage recovery, you are booting to the wrong slot. So switch slots using fastboot and then boot into Lineage recovery, wipe data, and reboot.

Try booting into recovery and wiping your data. Especially if you forgot to do this before.

Yessir, I certainly did. But I don't think it does what you expect. I have no way to correlate the system fingerprints with the vendor fingerprints. All the script does is check if the system data has been wiped. If so, it wipes the persist data. Note that removing all fingerprints does not (currently) count -- the script only checks for the presence of the system fingerprint file, not that it is empty. But you still have the issue of the vendor HAL never deleting fingerprints. So, if you enroll more than ten fingerprints without deleting the persist data, you will always run

Official lineage does OTA updates in the background like stock. No cables needed. But it can take nearly an hour because the updates are full, not incremental. I'm working on incremental support.

Doesn't Lineage have this issue fixed? Might want to give that a try.

I can try to investigate. Send me a logcat in PM. Also, if you have root access, a kernel dmesg would be good.

See for yourself: https://photos.app.goo.gl/bXsZoydGZnEyzUNK8 I did tap the screen to focus, as I was not patient enough to wait for auto-focus. It is unlikely the sensor is a different brand or model, as I removed support for most of the unused sensors. But perhaps there could be some differences, I guess. Kernel logs from boot may help identify the exact sensor.

I see the thread. I don't know what could be wrong, and neither does @npjohnson. And the camera focus seems to work fine on my device, so I can't test it myself. If someone wants to send me a pair of logs showing stock camera focus and lineage camera focus I can take a look.

Possibly failure to get a DHCP lease. Can you tcpdump on the router?

Interesting, never seen that before. It must be automated. And I'm pretty sure data decrypt won't work. What reason is there for wanting TWRP over Lineage recovery other than data decrypt?

Indeed. Before you lock, make absolutely sure that you have "allow bootloader unlock" enabled in the security settings. If you lock with that disabled and anything goes wrong, you need EDL to fix it. And trust me, EDL is much more finicky about USB ports than fastboot, as many here can testify.

t5 was the original model name for the Pro¹ before Google made them change it to QX1000. You can change the assert in the zip.

Perhaps try a different USB cable or a different USB port? Maybe even a different host computer?

Not yet, at least from the kernel. But I would like to make that possible.

This issue may be either hardware or software. But I don't think anyone else is having this sort of issue...? There is a known issue with key repeat when the system is under some load, but certainly key ghosting should not be happening. Did this issue happen on stock? Could you install stock to test?

Encryption is specified in the fstab, /vendor/etc/fstab.qcom. Unfortunately, there is no way to edit the fstab on stock due to Android security measures. You should be able to successfully edit the fstab on Lineage.

I cannot guarantee that but you can try.

It should, yes. But I haven't tested it. Can someone else confirm or deny hotspot functionality?

I'm not sure what you mean. This tool is intended to put your phone back to factory state. You may choose to not flash data, in which case it will preserve your existing data.

So in case anyone is interested, here are the firmware partitions included: abl, bluetooth, cmnlib, cmnlib64, devcfg, dsp, hyp, keymaster, mdtp, mdtpsecapp, modem, pmic, rpm, tz, xbl These should be all of the A/B partitions excluding boot, system, vendor. The shipped images should currently match the 2020-07-07 OTA. And by the way ,this was all @npjohnson ... I did not really want firmware shipped because it's kind of pointless right now -- all stock builds have functionally identical firmware and that is likely to remain the case indefinitely. But Lineag

Lots of posts in the last few hours so I'm going to do a bulk reply. here... @Wasmachineman_NL @DieBruine the Pro1 has not licensed aptX and the required aptX libraries should not be installed. Therefore aptX should not work. I am not familiar with the meaning of "HD audio" as it relates to BT. Perhaps someone can enlighten me? @EskeRahn @FlyingAntero the new build is larger because Nolen added "firmware" to the build. I'll have to look into this to see exactly what was added and where. Also, the changelog does not update exactly in sync with the builds. I'm not s

Yes, a new keymap file is the easiest solution. The instructions you linked are for editing the kernel keyboard mapping. Let's call this the keymap file for clarity. This is not the same thing as the Android keyboard character map file(s). Let's call those kcm files. You could probably use either to change your keyboard combinations. I suspect that changing the kernel keymap would be the "more correct" way to do it, but it is a bit more difficult to work with than kcm files. Shifted combinations can be edited in kcm files, yes.

The fingerprint daemon, which reads the actual fingerprints, is closed source. However, I did change the fingerprint HAL to alleviate some of the false reads when you accidentally touch the sensor. That may be what is causing problems. You should be able to effectively circumvent the authentication delays in the HAL by setting this property: persist.vendor.fingerprint.auth_delay = 0

The source is here. It goes into /vendor/usr/idc on the device. I intentionally named it after the device name so that you can override it easily. See the search logic here.