tdm

If you don't see any boot logo or anything, that is surely a hardware issue. I'm afraid it's time to talk to support. 😞 It is possible... I'd say likely... that it's just a loose connector. But you and support need to decide whether you should disassemble the device or let them do it.

Yes. It does whatever lineage usually does. I'm not going to wait for the timeout 5 times to try. 😉 You, as a user, do not switch to enforcing. It is my job to fix all the enforcing issues and then enable enforcing mode.

Pretty sure it works for everyone else. Send me a PM and we can try to figure it out.

No I don't really play games on my phones... or anywhere really. That's what happens when you have kids and an android hobby. 😉 Interesting to know that it's also in stock, thanks. That will surely help.

Perfect, thanks. Installed VLC and set it to OpenSL ES. mp3 playback is crackling. Will investigate. I haven't used my device much yet. Still need to get my carrier to figure out the voice call issue.

What exactly are the issues with sound? How can I reproduce them?

Okay I've spent several hours trying to get TWRP to decrypt userdata and still no joy. I am going to put that aside for now and focus on other things. So as I recall, the top 3 things people wanted were display margin, fingerprint mitigations, and TWRP. What's next on the list? I believe the only things blocking official builds are FM radio and selinux. And I could probably fudge on FM radio if nobody cares about it. Though I really should get it working soon.

The boot loader is qcom code. The OEM modifies it for the device: display initialization, button access, things like that. I don't know offhand if the unlocked warning is defaulted to on or not, but they certainly could have disabled it in any case. All devices have Secure Boot off and always have. This is not really related to the boot loader lock.

Seems to be a bug in AdUps. I rebooted after waiting a bit to make sure it was done. The update was successful.

Sure, please file an issue on my tracker (and also on the new community tracker). This seems like an AOSP bug, so I will probably look to see if it has been fixed in AOSP master. If not, I will try to send a patch to them.

Sure that sounds like a good change.

Here is the post where I described how to change the keymap: https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/?do=findComment&comment=45512 Also, I realized that I may need to make a third keyboard layout "qwerty-intl" to support multi-lingual keyboards using the QWERTY keyboard, as @auvo.salmi is doing. I don't know how many others are doing this. Anyone?

Yes you can certainly try just splash first.

You most likely have a full fingerprint set in /persist. Delete everything under /persist/data/fingerprint and reboot. That should fix it.

I had issues with slots and it has also had issues with lineage recovery in the past, but that may have been fixed. I always used to use opengapps just out of habit, but never liked it because their installer script is insanely complicated. After having issues with A/B devices I switched to MtG and I'm not going back.

Recovery shows the current slot on the screen. It can also be found in Android by "getprop | grep slot", and there is even a fastboot variable "fastboot getvar current-slot".

You can choose to install to either slot after the initial Lineage install. Just be aware that recovery will install to the opposite slot as the running one. gapps is supposed to persist if you have it installed. But people have reported issues with that, and I have not yet investigated. But it is always safe to flash gapps ... it will just over-write itself harmlessly. Again, be aware of the slots and remember to reboot recovery prior to flashing gapps.

Yes absolutely.

test9 is up. Changes: * Fix notification light. * Fix WiFi signal strength indicator. * Add fingerprint mitigations. Notes: The vibrator seems to work but I am seeing errors in the log. Please let me know if it works or not. Either way I will be looking into fixing the errors. The fingerprint backoff defaults to 2 seconds per attempt. This can be controlled via these properties: persist.vendor.fingerprint.auth_delay: the auth delay in seconds, defaults to 2. persist.vendor.fingerprint.auth_backoff: whether to backoff between attempts, d

I'm trying to push a release out today, but it may slip to tomorrow morning (Seattle time, naturally). The current fixes include fixed notification lights, fixed wifi signal strength, and a delay for failed fingerprint authentication. COVID-19 affects development because I am in Seattle which is currently in full freak-out mode over the virus. Fortunately it hasn't hampered me that much (yet).

Well, sort of. I have the BSP minus GMS (aka. gapps), but it is missing the device signing key. It's not hard to add a minimal GMS. So I could make an "almost" stock that is signed with a different key. Obviously my version would not get OTA updates, I would have to provide updates myself.

So I'm talking to the Lineage folks and discovered that there is a setting to only accept fingerprint touches when the screen is not off. But it is a build-time setting. That is, you cannot toggle it. So I'm not sure if it would be appropriate because one of the cool things I like about fingerprint sensors is the ability to unlock the device without touching any other keys. Aside from that, I did discover a way to control the fingerprint behavior without doing anything too hacky. It just involves copying the AOSP fingerprint service to the pro1 device tree and modifying it. So

If you are on stock ... well ... that is a bit tricky. Do you have a root solution? If so, you simply run "mount -o remount,rw /vendor". If not, perhaps find the copy of TWRP that someone built and use it?

... but keep in mind, the slant arrows will be configurable at some point. It's on my to-do list.

I would think that using a DFS channel is the likely cause. Note that the 1+5/5t has the same WiFi chip but somewhat different configuration for the DFS features. So you can play around with the WiFi configuration file to see if that helps. The configuration file is at /vendor/etc/wifi/WCNSS_qcom_cfg.ini. You can find the 1+5/5t configuration file used in Lineage here.