Leaderboard

Just wanted to provide links to source files that makes our Pro¹ keyboard. That can be used as reference for anyone wanting to understand and customise Pro¹ keyboard experience by building Lineage OS. From low to high level files we have identified the followings key components: Device Tree Structure Include, contains GPIO pin mapping to scan codes: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi Permalink Driver, brings together GPIO and aw9523b controller input to define the scan codes sent to user space: h

468 is what Google chose to use in the Android framework to signal keyboard slider behavior, for example it is what forces the display into landscape mode when the keyboard is open. Unfortunately, they also use the same keycode for case events 😞 Changes to this will be difficult to merge into LineageOS, as the code is shared among all devices. This is why our fix for non-English keymaps and accessibility apps was rejected...

Since you are saying you are poor I would say yes, go for big brand high volume phones. You could also save money by not getting the flagships as well, go for midrange models instead. Pro1x is not for poor people I'm afraid as you better make sure you have a backup phone just in case your Pro1 has an issue. Low volume devices from startups are more likely to have technical issues. Moreover if you buy a Pro1x today you just don't know when or even if you will ever get one. It is a risky pre-order and your money is gone long, long before you get the device. Having said that you need to know

You mean sideload your own build over an official one? That will only work without wiping data if you migrate your setup from 'official' to 'testing' keys. Also, at least for LOS 16.0, the official recovery would not allow me to sideload my own build. I had to first flash my self-built boot.img using fastboot (to both slots, just to be sure 😉).

While a couple of the people who work on LineageOS for the Pro1 read this forum, the majority don't. The best way to get our attention is to open a bug report using the instructions on the LineageOS wiki: https://wiki.lineageos.org/how-to/bugreport FWIW, I have not seen the problems with charging you are having, but I don't regularly run the battery down very far either.

To be absolutely correct, @tdm fixed it. I just did the typing 😉

Hi I only just started using my Pro 1 and went straight into installing Linage 18.1, so I have never used it wth stock. The phone never charges unless I reboot it first. I tend to charge it when it gets to the 15% warning. In settings, battery it says "plugged in, cant charge at the moment" I have 5 differnet cables, and 6 chargers and direct usb power sockets or several computers USB2&USB3 and it does not work with any of them until its rebooted. It does not work with the provided charger or cable. If I reboot, it will imediately start charing with any of the ca

While working on our keyboard I could not help but noticed those oem_halla and oem_hallb GPIO events definition: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi As I'm the developer of Fx Service which provides smart case functionalities for Pro¹ I can tell oem_halla is the case close event and I'm guessing oem_hallb is the case open event. @Sean McCreary Is there any chance we could reroute those events to Android Sensor API somehow? I reckon that should make them more useable especially the case o

For me (on LOS 16) sideloading my custom ROM from the official recovery would just fail (without anything getting flashed), so I am not sure if this is the same phenomenon.

Yes, that's the correct procedure, which worked for me since I got my Pro1. Upon flashing the ROM it switches the active slot. A reboot is then needed to make sure any additional software is actually sideloaded into the right OS.

No, I do not think so. As far as I know, the "testing" keys are not unique to a certain building environment, so you should be able to flash the new build over the previous one without migrating. Did you actually solve that issue you had with installing Gapps and other Apps on your custom build?

Do you mean you have used WSL (Windows) environment for compiling and now you would like to move it under VirtualBox and a Ubuntu inside? What do you expect from it? Increase of compiling performance? I would think the very same source tree may should work but I don't know. However, somehow I could not even sideload LineageOS of my own build without doing a factory reset. Do you nhave any ideas what may I have done wrong? I have installed my build, then Magisk and MintTheGapps and did the same thing after sideloading the new build. However, it seemed to have an endless

Swapped: A=Keyboard, B=Case - at the least that is the naming used in the FactoryKit....

I am needing a new phone, and I really like that the battery is replaceable. My last 2 phones the battery over heated, and swelled up, due to high network usage, and I couldnt replace the battery... I had to just live with a swelled battery for years now. I am grandfathered in on the old verizon unlimited data contract, and I use about 300 gigs a month. It is my only source of internet in the mountains where I am. Since then I have bought an external fan for the phone, hopefully that will help keep it cool. TMI? Anyway... I couldnt find a waterproof rating in the specs' list, does an

Most likely a scancode for historical reasons is a byte, somewhere in the 'pipeline', so the map to 464 must happen later.

The Hall_a is the keyboard open/close detector, the Hall_b is the one in the display (case detection) They are called a and b in the 'factorykit'-test (The one just above OTG almost at the bottom) See this

Fixed. The CR is under review here: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/315298 Oh, and there is an associated SELinux policy change that is also needed, but the implementation is still under discussion

(lineage-18.1-20210830-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.

I have made a lot of keyboard-related changes on the code, now I will try to summarize them. Also, I have tried to reach a state what probably all of us may find useful and also original working can be kept in case someone does not need additional features at all. Driver-related changes I have initialized some additional virtual nodes of keyboard driver's kernel module where driver's behaviour can be changed. Some additional settings were necessary to make them accessible to system UI. Also, I have borrowed some of the ideas like what @Sean McCreary has already done. Th

Ah, so though obviously very impractical, at the least you will be able to charge it this weird way, until the bug is found and fixed. But really odd that only some are affected by it. I use a pretty dumb no name charger, to keep the charging current low (about 5W), to be kind to the battery, I wonder if that is related? ADD: I'm using a charger with roughly 5W cap. I have tested that it starts fast charging too, but did not leave it fast charging for a lengthy period. But as fast charging gives quite a heavy heating of the battery, it just MIGHT be a security mechanism tha

I hope you are half pulling our leg about the swelled battery for years and the external cooling fan. Lol I'm not sure how Verizon will handle you if you are grandfathered in on an old plan. The Pro1 will work on Verizon following the instructions in this thread. https://community.fxtec.com/topic/2133-fxtec-on-verizon/page/5/?tab=comments#comment-41839 But this method requires that you have a Verizon SIM that has been activated in an approved phone with VoLTE. If you have that, you should be fine. But there is no way to know for sure in advance. I chose to have a sepa