Leaderboard

@VaZso there's also this Docker image you can use. It didn't work for me in Windows 7, but worked in Linux and I think the Docker experience is much better if you're on W10, which you must be if you're using WSL.

I wonder how many of you guys there are. Hope they are going to ship your Pro1X first.

I paid for an original Pro1 back in Feb 2020. I'm still waiting on it.

@SlionI've never needed to modify the inf before but it really is a bit random what machine picks up what with the android debugging stuff. Sometimes windows is fine with what it installs automatically sometimes not. I guess I've just been lucky and not needed to do that yet on the PC's I've got. Glad your working though!

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.

Yeah, I am currently copying it from a 1TB SSD to a 2TB SSD but they are not recently installed and the former is also my live backup of important projects in case the latter dies which is a faster M.2 drive. Also this project has a plenty of files and I don't know if it will completely restart the process or continue it. 🙂

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

OK, if you wipe it should boot. Somehow the equivalent of: "Nuke the entire site from orbit!" Obviously the only way to teach 'em manners ... That it takes ages after a flash is normal ... or, at least, I got used to it.

Did you migrate to "testing" keys as I explained (or tried to) here:

First things first: Congratulations! You have just build your own operating system for your phone. May zombie-apocalypse come, you will be among those who rebuild the world. Time to open a beer or something. It's interesting that you have a much more powerful CPU than mine but still get similar build-time (all assuming the amount of code is similar from LOS 16 to LOS 18). Mine is an ageing Core-i3 3220T, with only 3 of its 4 (hyperthreaded) cores assigned to the VM. It is my home server, which I use because its the only machine that runs 24/7 anyway. And, as the server does many othe

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.

Would it be possible and even sensible to make LOS behave a bit more like stock here, meaning that it would become compatible with FinQwerty/FxQwerty custom layouts? They seem to have worked well for anyone who's used them. I don't have that experience as I never used stock. I was happy, though, with how the US International keymap used to work in LOS 16.1, but I also find 18.1 a bit lacking...

Sep 2019 here 😆 – plus a Pro1X order from Oct 2020, to improve the odds for getting at least one phone at some point. It's all very well for me to laugh of course since in the meantime I was lucky to get a pre-owned Pro1 and I'm totally happy about it...

No idea, honestly. I build only once per month and wipe everything in-between as I am limited in disk-space. I had a build fail once due to it running out of space after I did not clean out the previous one ... A fresh sync-and-build takes 10 ... 12 h for me (3 VM cores, 6 GB RAM), approx. 4 h of which it spends downloading all the stuff (100 Mbit/s). I honestly do not care about the speed. I start things in the evening and have my image when I wake up in the morning. 🙂

It just worked.

I'm hoping to retire my Moto Z3 one of these days (as the Livermorium Keyboard Mod ain't happening). Do we think fxtec will be able to make enough of the redesigned Pro1X's to cover all of the existing orders, and have stock left over to sell retail?

(on stock triggering the hall sensors sends a key-combo)

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 😁

Nice 🙂 But does it REALLY need the Accessibility rights for this? (I do not care for any of the other functionality of the package, that is why I stay on v0.4 on stock)

(Moved some keyboard related over here, thanks for the suggestion @Hook )

Right - connection speed is good but it only uses one core out of eight; okay, virtual eight. 🙂

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.

You are right but although it is not practical, it doesn't bother anybody. 🙂 Hehe, I was thinking of I have used it before... err, yes, there is a dedicated alt key there. 😄 Anyway, it takes a while for the repository in docker image to synch / come up.

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.

It looks good while both can be defined in .kcm file. However, that would be a bit deeper modification than what I thought to be necessary to at least keep the same functionality what worked in stock OS. Anyway, it can also be done following the scheme what @tdm has done. ...but would you use the separation of fn keys for anything?

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

It may happen also ctrl buttons are wired together, but it isn't a huge problem compared to loosing all of the FN functionality. ...and that is a hardware limitation which can not be improved like software limitation. 🙂 Edit: Anyway, there are reserved locations in keyboard driver (I mean in the buttons representation), I don't know what they are exactly - it would be good to have the hardware wiring to find it out easily or to see why they are in the row.

Did the same: https://slions.net/resources/fx-qwerty.7/

Seriously it worked really well for me under stock OS - I took the project what @Anssi Hannula has created (finqwerty), removed all the layouts from it and only installed two custom layouts for me, but only one of them was in use on my Pro1. That was a custom build renamed to not conflict with original software which was also installed. Anyway, these kinds of custom layouts do not consume power resources like a special application would, these layouts are reachable in the same way like original layouts - absolutely a perfect solution which does not need root access but exactly works lik

I didn't say it is a bug. Anyway, I have tried to get QWERTZ variant to work with QWERTY keymap where I can also reach characters which is often used in my language and slant arrow was a perfect key to reach them as it exists on both sides. If it is an intended work of it, then it is a regression. It would be perfect and -ex variants should has the raw layout, without any remappings at driver level. However, the name of QWERTY can be a bit misleading if F(x)tec will publish non-shifted physical layout together with Pro1-X. Basically it is all about SHIFTED and NON-SHIFTED la

Never retreat, never surrender! The true spirit of a Spartan. Go, @Slion!

It works like this (in .kcm file): key W { label: 'W' base: 'w' shift, capslock: 'W' ralt: 'm' meta: 'p' alt: '\u0302' fn: '|' fn+shift, ctrl+fn, fn+capslock: '\u00c5' } You may define what key combinations should do what in a similar combinations like above (the above is just an example and not more). I was mentioning the keyboard if it would no

I could overcome the case sensitivity issues even when trying to build from a Windows mount but there was another failure shortly afterward that you can't avoid apparently. I'll make another attempt with WSL this time from an actual ext4 file system rather than from a Windows mount. Apparently that should work: https://www.xda-developers.com/how-to-build-lineageos-on-windows-10-using-wsl-2/ https://github.com/microsoft/WSL/issues/7283

Seems to work fine as I went to bed but it did not work in the morning anymore.

😄 We'll never fix that bug, I guess ... Keep going!

I'm still hoping I won't have to. Why make it easy when you can make it complicated 😁 Trying to fix that case sensitivity issue… I already had WSL setup so could not bother setting up another linux env. I want my brunch 🍳

lol. Seriously. As I said, fire-up a VirtualBox (or whatever hypervisor you prefer) and install Ubuntu LTS in it. Make sure to assign enough disk space, 200 GB is absolute minimum. Much more is needed if you want to make several builds in a row (much faster) whitout wiping everything in-between.

I can reproduce your issue on qwertz layout with qwerty keyboard. Sounds like a mapping bug in that array indeed. It just goes to show how little testing LOS as had on Pro1. You should open a bug on GitLab about that one issue. Keep it focused and short.

Pushed a new version that should fix screen wake up by proximity sensor when opening the case.

Well I have for now given up on AICP and replaced it with LOS 18. Though I liked AICP, and definitely will reconsider if something new is happening.