marmistrz

We really should have a wiki describing all the LineageOS modifications compared to stock. The built-in layout indeed works, unlike on stock. Currently one advantage of using (left) alt instead is that it's sticky, unlike sym (right alt).

Eh, you can't do inline replies on this forum. You're right, one can use left alt as a modifier key. I made mistake while modifying the generation script 🙂 and it's why the generated keymap didn't work for me. Expect a Polish layout using alt for diacritics in finqwerty soon^TM 🙂 Your reddit post doesn't really explain the internals, just the implemented features. How exactly is fn handled inside the driver and why isn't it done in the userspace? If I'd like to prevent alt from opening emoji, is it AOSP keyboard that should be modified? Does it have anything to do with the LOS

My 2015 OnePlus 3 does MUCH sharper photos than the Pro1. (I even checked gcam out of desperation and it's still worse) I'd expect a decent camera for such a high price (especially that the device aspires to be a premium device)

I don't know much about the architecture of Android, but maybe the process responsible for detecting key repeat/long press (probably some equivalent of X.org) has too low priority and gets deprived of the time quantum?

Oh, I meant double shift as caps lock. I'll edit my post.

As for GitHub issues, we probably should have a single keyboard issues metabug. I've noticed several issues with the current state of the hw kbd support, some of them are scattered across several issues, some not reported yet no way to turn off autocapitalization fn isn't sticky (but probably should) double shift acts as caps lock (but shouldn't, because we have a hw caps lock key) custom keymaps are broken under LineageOS: fn & alt are not respected. For instance, if the kcm maps alt+e/fn+e to ę, the sign ´ will be emitted anyway alt opens an emoji drawer (it

You can change the selinux mode without flashing a new image afaik: SELinuxModeChanger (Set SELinux mode on boot) - https://f-droid.org/app/com.mrbimc.selinux

I've just seen it in Conversations, which is a pretty lightweight app, which rules out a problem with a heavy app.

Can this be related to https://github.com/anssih/finqwerty/issues/17 ?

I tested fast poll. The setting seems to alleviate the issue, but it's still present, mostly in Fennec F-Droid. (which as really heavy app) My most important question was not answered: is F(x)tec aware of this issue? Can we expect an upstream fix? This seems to be no new issue and multiple users seem to be affected. cc @Erik

You once said you only support addonsu, not magisk. addonsu has been dropped in Q, making magisk the de facto solution btw. https://www.xda-developers.com/lineageos-dropping-superuser-addonsu-implementation-favor-magisk-manager/

Yes, this happens to various keys and various apps. I have the impression that more often on heavy apps like Fennec F-Droid but not exclusively. Fast poll seems to help so far, but I'll keep on testing.

How come that in 2020, when everything's done online, you need to visit a bank branch to add a new payee?

Hi, I noticed that sometimes while typing on the Pro1 a key gets "stuck" and produces input for ~1s after it's been released. This happens on both stock and LineageOS. In such a situation, I'd get many repetitions of a letter on stock (for instance: rubbbbbbbbbbbbbbb when typing rubbish or lauggggggggggggggg when typing laugh). On LineageOS, this is registered as a long key press, which triggers the diacritic selection dialog. It's a total bummer when trying to get decent writing speeds. Is this some driver issue F(x)tec is aware of or is it a hardware issue?

Could we have some community wiki about the protective cases? I know about the blogpost by @EskeRahn, but I saw that others recommended some other cases... and I don't think I have the time to get through 34 pages of the thread 🙂

Wait, does it mean that I didn't need to flash the LOS 16.0 root add-on? xD I did it almost automatically, because every time I flashed LOS before root was not included by default 😛

Is the su-hide patch opt-in/opt-out? I have absolutely no reason to hide su from any of my apps and this sounds like something that could break some apps really needing su.

I'm still not sure: if I update test10 to test14 through the LOS recovery & sideload (without fastboot) and test14 doesn't boot, will A/B take revert me back to test10?

For me neither 2.0 nor 3.0 worked. I uploaded the USB dump in my previous post.

I think I have flashed all the available updates to stock before flashing Lineage. Btw. is it possible to update firmware without reverting to stock? Can I somehow make a restorable backup with the LineageOS recovery or something else, so that I can go back to test10 if things go wrong? Or will A/B just do the right thing for me? I can't find the option in the LOS recovery. Is the TWRP from some different thread compatible with LineageOS? (there's no separate recovery in system-as-root, that's why I'm asking)

Thanks a lot. I'm going to mention it in the OP.

@daniel.schaaaf, you mean the OTA updates of the official Fxtec ROM? Why would this happen? Disclaimer: I'm using LineageOS, so I can't even test OTAs.

Hi, It took me a while to figure it out, so I'm writing it down in case I need it in the future. 🙂 The OTA zip doesn't work with the Pro1's system-as-root, so one has to install it manually. So here's the guide. The procedure was tested on LineageOS. WARNING: following this guide on stock will break OTA updates. See post #4. 1. Download the zip from https://f-droid.org/en/packages/org.fdroid.fdroid.privileged.ota/ and unpack it. 2. Execute the following commands: adb root adb remount mv permissions_org.fdroid.fdroid.privileged.xml org.fdroid.fdroid.privileged.xml adb pus

Has anyone managed to install the F-Droid privileged OTA? I flashed it as usual with adb sideload, but the app is missing from the launcher and the f-droid apks are nowhere to be found on the filesystem. /edit: I created a tutorial on the forum

I managed to flash the LineageOS recovery! I found some USB hub, connected it to the USB 3.0 port, connected the device to the hub and fastboot flash worked. I have absolutely no idea why, but here's the USB dump.