tdm

I may have missed something for the qwertz setting. I'll check.

That was for debugging the keyboard issue, you can read about it a page or two back.

I've gotten the stock keyboard driver to work with Lineage, mostly. I was having an issue generating forward slash on QWERTY, but other FN combinations seem to work. And the any-key-to-wakeup feature is not there. But other than that it seems usable for a test. @DieBruine and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. http://files.nwwn.com/android/pro1/boot-stock-kbd-1.img I've put the code here just in case anyone wants to look: https://github

Camera is all closed source blobs between the kernel driver and the camera app. It spews out amazing amounts of debug information, but I have never been able to make sense of most of it. So... probably not, unless we get really lucky.

To be fair, this is Qualcomm's mess not FxTec or IdeaLTE. Both stock and lineage use the Qualcomm qcacld driver for WiFi. Just different revisions. Apparently some revisions are buggy for some people, other revisions are buggy for other people. Maybe I just got lucky and picked the revision that seems least buggy?

Most likely recovery.

That was just a guess. Too bad about the damage but I'm glad you got it back at least.

This is usually scripted with a small shell script / batch file. That's how Google does it with Nexus/Pixel. I thought Chen provided one? But otherwise, no, you cannot flash to multiple partitions with one command. It is one at a time. And yes that is tedious and error prone. Hence the scripting.

Alright I got the stock keyboard driver transplanted into the Lineage kernel and it builds. Now I just need to take care of the key mappings and make the FN key work like it does in Lineage. Hopefully I can get that done tomorrow.

Run getevent. It won't run in a shell, it requires adb. But it does not need root.

Switch the keyboard to type FULL. Get an adb root shell and run: mkdir -p /data/system/devices/keychars cp /vendor/usr/keychars/Builtin_Keyboard.kcm /data/system/devices/keychars/Vendor_181d_Product_5018.kcm sed -i 's/type ALPHA/type FULL/' /data/system/devices/keychars/Vendor_181d_Product_5018.kcm You can also edit the keymap to your liking. @3zet recently did this.

Pretty sure there is not. And even if there was, I'm guessing it's probably wiped by now.

Lineage recovery will offer to install from sdcard if, and only if, a physical sdcard is present and it is able to be read without any decryption (eg. it is not used as adoptable storage). Lineage recovery will not offer to install from /data (including "internal storage" because the data partition is encrypted and Lineage recovery does not have any decryption capability. And yes, file-based encryption counts, because all files in /data/media are encrypted under FBE. This is not a bug. This is how recovery is supposed to work. TWRP bends the rules with data decryptio

My Pro1 seems to work fine. Can you share a sample picture that exhibits this issue?

Sorry guys, I'm a bit busy with work lately, plus just had a couple kids birthdays. But I'll get the kernel with stock keyboard driver as soon as I can.

Lineage does not do verity (checksum) on /system or /vendor. It can't, if it is to allow addons like gapps and su. If you want to investigate why your modifications aren't working, the first step is to get a logcat.

Thanks for the thought. It's mostly just me and @npjohnson but I'm not sure about his feelings on donations. We have both received devices for development, which I personally consider due reward in itself.

I really wish FxTec was more communicative. It's super sad to see all the reading between the lines, guessing, and tossing information together because nobody is told what is actually happening or not. I'm not officially authorized to say anything about OTAs, but I will just say don't hold your breath for stock Q or R. But of course Lineage should have Q in probably a couple weeks and then R pretty much as soon as all the other devices.

Because there is no separate recovery partition, recovery lives in the boot partition and gets updated with every ota.

Apologies to the Eagles... It's Hotel Pro1, you can logout anytime you like but you can never leave. 😂 Seriously though, I have no idea. Perhaps PM an admin?

Yes but I'll need help from you to describe what keys should be mapped.

All issues for the radio (cell modem) are going to be exactly the same as stock. All of the radio code is closed source. WiFi is mostly open source, but I have taken the stock qcom code for this with no changes. So it should be pretty much the same as stock. There may be some differences in the wifi configuration file that affect performance. I haven't looked at that in a while. As for the keyboard, I really am at a loss to say why @DieBruine is having so many problems while others are not. I suppose I could make a Lineage kernel with the stock keyboard driver to t

Pie is old, very few actual changes are being done to affect functionality. If a build works for you, do not feel any need to update to a newer version. Except maybe for security updates.

The Pro1 seems to have a bit weaker reception than other devices. But be aware faking signal strength bars is common in the industry. You need to compare reception with actual signal numbers in dB to be sure. And always judge functionality based on ... well ... functionality, not signal bars.

Stock has had two keyboard drivers. The original one that IdeaLTE wrote does not do polling at all, it is entirely interrupt based. As a result, it cannot detect many two-key combinations. A lot of people noticed this and the driver was disliked by many people. @netman rewrote the keyboard driver to use polling. This is the current stock driver and this is the code that I started with to write the Lineage driver. It polls at 15ms. My driver defaults to 40ms, but the fast poll option in settings changes it to 20ms. So... I am not understanding how the st