Slion

Right now here is what I'm thinking we should be doing: - Fn keys remain silent. - Special feature so that right Fn can be used to alt+tab and as Fn too. - Maybe add extra functionalities to Fn layer optionally or default.

@VaZso Thanks for you comments. What do you want to modify/fix in the drivers? You do know that AltGr is the Sym key? If you need an extra layer of modifier you should be able to remap the Home key AKA FxTec key to a meta modifier or whichever one works for you.

This driver is not for Pro1X, just for Pro1.

Though you can get all the French characters you need using diacritrical dead keys. Now I'm starting to understand the amazing work that @tdm has done with those drivers by making them compatible with standard layouts.

I'm not exactly sure yet but not that much really. Add a new set of layouts that would: - Unmask the Fn keys so that custom layouts can remap them. - Decouple the Fn keys, I guess they will be mapped to so called left meta and right meta. - Look at why custom keymap is not working as it should. - Fix other bugs if any. Now that I understand that the qwertz driver layout is there to fix the scan code for compatibility with standard layout I'm not sure it makes sense to provide drivers layout compatible with stock and FinQwerty.

The size of my WSL ext4 partition file is over 250GB after the build. So you may want to make sure you have like 300GB available. It took like 10mn to rebuild the driver after modification and I could indeed see the logs I added in logcat. It will be a day long remembered, it has seen the end of Slion's Lineage OS ignorance and will soon see the end of all bugs in keyboard drivers 🥳 Off to bed guys, hope to find the time to tweak that driver tomorrow. That's all that needs to be done.

Got 2TB SSD 🥳 it took quite a hit though with that little venture…

I know. right! 32GB RAM, it was 100% CPU during build so definitely CPU bound, M2 SSD super fast, actually installed it recently to do just that. Was just adding some logs to the driver and rebuilt, took almost exactly 10mn, not that bad.

Was actually fast to boot once I wiped. Off to try build a modified keyboard driver.

Of course not 😁, just did a wipe and it did boot.

Also I think it's not booting. Just tried to sideload it without wiping. Now it's stuck on the loading animation. @claude0001Do I need to sign it somehow?

Took my i7-7700K workstation about 6h30mn to build Lineage OS over WSL. Excluding repo sync. The resulting zip file is suspiciously about 45MB smaller than the official release.

Took my i7-7700K workstation about 6h30mn to build over WSL. Excluding repo sync.

Yes it will be possible to have a profile matching stock.

https://android.googlesource.com/platform/hardware/qcom/display/+/cba1cee4750a80db4b476c3273b06a6d575859f6/msm8998

Though HDMI is just mirroring, would be nice if it did support desktop mode. I wonder if enough of the drivers are open source to be able to implement desktop mode.

It just worked.

I tried that quick this morning and it worked, though it was not connected for much more than 60 seconds I reckon.

I would not count on that. You better pre-order.

Really? 🤣

Same on LOS really, it's just that the events are a bit different.

Yes the the whole thing is implemented around that accessibility service. I don't even recall how it was done before. Your data is mine 😁

I wondered about that too and I could see only two explanations: Nobody uses alt+tab other than me. I'm just the most perfectionist Pro1 user out there. Yes it does, at least a couple of hours I guess depending on your specs and connection speed.

We are aiming at better than stock 🙂 Exactly just offer more driver level layouts As I explained above already, I want to do alt+tab using the right Fn which is what Fx Qwerty does for instance. Doing alt+tab using the left alt is very unpractical with two thumbs.

Also great news it looks like the two Fn keys are not hardwired. I reckon we should be able to give them different mapping. See that logs sample: 2021-08-25 17:26:08.645 0-0/? I/aw9523b: gpio_keys_gpio_report_event: desc=fn_l code=464 state=1 2021-08-25 17:26:08.796 0-0/? I/aw9523b: gpio_keys_gpio_report_event: desc=fn_l code=464 state=0 2021-08-25 17:26:14.106 0-0/? I/aw9523b: gpio_keys_gpio_report_event: desc=fn_r code=464 state=1 2021-08-25 17:26:14.285 0-0/? I/aw9523b: gpio_keys_gpio_report_event: desc=fn_r code=464 state=0