Leaderboard

In case you have root, you can take a look at /sys/class/power_supply/... For my Moto Z Play, I made an Automate Flow (script) to read and write to certain files (e.g. in /sys/class/power_supply/usb/) to control charging speed, stop charging at 85%, and even prevent apps like the Play Store to detect that the phone was charging. I did not have the time yet to make a script for the Pro1, so I can't tell which subdirectory in /sys/class/power_supply/ controls charging... /sys is a virtual file system connected to the kernel. You can open files under /sys (as text files) to get informat

Peuh you know what I do ? I use only QWERTY and never ever type accents, anywhere (pc, phone, work, family). You d be surprised how tolerant people are of 0 accent writing in French. Fuck AZERTY. Burn AZERTY. Add accents to QWERTY 😄

There is one on QWERTY. No self respecting French is using QWERTZ 🤣

You are probably determined to do it your way, which is fine. However, did you even consider to just use the provided QWERTZ layout as it is? All the special characters in your example sentence can be typed using the standard layout in LOS 16.0. "ö" is available as a key of its own. "í", "é", and "á" can be typed using the dead-key function of "´" (i.e. "´" followed by "i", "e", or "a"). Just sayin' ... Typing french is indeed more complicated, as only "´" and "ˋ" have a dead-key function (on LOS 16, that is), not "^", which is a pity ...

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.

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...

Okay, it has an inline specifier. Anyway, I don't know why it complains me about AIDL CHECK API / "No API file exist" Maybe it has something to do with my host system. :S

Although the CPU is fast, generally it is better to keep the code simple. By calling a function, it needs stack handling and some amount of user memory handling, so calling a function several times in a row at driver level may not be advised. So by using need_forced_modifier() and modifier_forced() may be readable better, performance-wise it is better as it was - at this level a bit larger code may be better if it runs faster. I don't know if compiler optimizes it out or not however.

You are right, I have read that later on writing my message, sorry.

Interesting... if I also creates /data/system/keyboard/keymap file then it can be enabled in settings but it still does not take effect... still something needs to be checked. It takes effect if I manually pass the whole file to /sys/bus/i2c/drivers/aw9523b/6-0058/keymap

Yes, I did just a few minutes ago.

Strange indeed.

I switched my keyboard to US International and it seems to work for me.

Using English(US) layout, it does (except with software that takes over the keyboard like Softmaker Office). This is strange; last time I tried, I could bring up the emoji selector by long-pressing alt on LOS 18.1, but right now I can't, no matter in which app. This is QWERTY with English (US) International keymap.

@Sean McCreary I've created a kernel pull request though I'm pretty sure that's not supposed to be happening on github but somewhere in Lineage gerrit. I have to take a look at the contribution process: https://github.com/LineageOS/android_kernel_fxtec_msm8998/pull/1

Though I used it for years, old AZERTY really sucks. However I'm a big fan of the new AZERTY standards and have converted most of my keyboards. They are so convenient for international French like myself you can easily type in most every European language without having to look up ASCII codes 😁 Shame that nobody seems interested in adopting the new standards. French people are creature of habits and do get stuck in their old ways even though they don't make sense… so it seems 🤣

See this thread:

Not yet but there are feedbacks on this forum about it...

Has anyone had issues charging their phone? This has happened to me twice this week, worked again after a restart. EDIT: My mistake, thought I posted to the Lineage 18.1 thread. 😦

If you're willing to spend a few bucks, another build option is to use AWS or a similar cloud instance. It's been a while since I've done it, but in the past I used a super grunty EC2 and built Lineage in under 2 hours. Good to do as a once off, but maybe not so much for frequent builds, especially if it's incremental.

Hi there, I'm happy seeing people hard digging in Pro1 and LOS. Sadly I have no competence at this level, but seeing this make my journey 😄 Thanks not to give up. I'm using LOS 18.1, and in keyboards aspect LOS17.1 was better, pressing Alt with Emoji is completely buggy, and a (very)few time ghost keys appears, I haven't see this since LOS16.1 in my first pro1 at the very beginning of LOS. THANKS ! you are completly right ! CHEER UP !!!

Right, keymap (hardware layout): QWERTZ Software layout: English/US, but I would like to have an option to complement it to easily reach national characters QWERTZ (as hardware layout) was much better as an international keyboard than QWERTY because the latter was shifted, so buttons apart from US alphabet were mixed up. So, basically QWERTZ was the more like standard QWERTY than the one named as QWERTY which had mixed keys, that is why I chose QWERTZ. Shifted QWERTY would not work well for international use as a lot of non alphanumeric buttons are in a very different place th

Using English(US) layout, it does (except with software that takes over the keyboard like Softmaker Office).

Just for the record, now I've experienced the same for the first time after I reinstalled LOS 18.1 from scratch. AccuBattery showed 47% charge level and 7mA charge current (i.e. nothing). ACC is set up to stop charging at 75% and to resume charging when the charge level drops to 70%. AccA app reported "not charging" (with the cable connected) where it usually says either "charging" or "discharging". Contrary to what I was remembering, opening the AccA app (or restarting the ACC service) didn't restart charging, either, so I had to reboot, too. So according to AccA ther

That works on LOS 16. That was discussed a few days ago. Seemingly the emoji palette is not enabled by default on LOS 18.1. It is a setting of AOSP keyboard.

Yes, stock OS did not distinguish QWERTY and QWERTZ and I think also the handling of keypresses were worse. ...and it will continue to work anyway even if it would be usable for others. I don't know how specific it is, but the use case: Pro1 has a relatively few amount of keys My language has a lot of keys which adds to English alphabets I can reach all characters instantly by using both slant arrows Current driver does not allow using slant arrows for this purpose but mostly could be added while normal use case does not change It seemed @Slion may a

As far as I know, the driver in Lineage has been made different from the one in Stock for a purpose. And it has worked quite well for many people across 3 Lineage releases now. You seem to have a very specific use-case (that I still do not understand), which is totally fine. But please do not blame everyone else for being happy with things as they are. If you propose changes, please do not look only at your special case. Not that I understand much of the discussion, but the suggestion of @Slionto add one or more additional keyboard profiles to fulfill your needs seems reasonable and would

I don't think so, I could not see it working that way and AltGr is designed to be something else. Basically that is the very same keypress as "right alt" simply they needed a special key on international keyboards (back in standars PC) and as a result, they has renamed right alt to AltGr which became a "special shift" for extra characters the layout not has as standard. For example, if you connect a keyboard to a PC which has Hungarian layout but your OS was set to English/USA, AltGr will be right alt. If you connect a standard (USA) keyboard but OS is set to Hungarian layout, right

Yes, that is why we started pushing a lot of messages here. 🙂 What is why I have started digging into the driver is the practically absolute inability to remap keys pushed together with slant arrow. I have also found other things in the fn-part of the buttons and I would also suggest to add AltGr function to those buttons even if there are hardcoded layout settings. If there would be another setting(s) beside QWERTY and QWERTZ then it is possible to build the very same keyboard map what stock OS has (named as QWERTY) and also a non-shifted variant which then will be combatible with

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.

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

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.

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'm using the "English (US), international style" layout for the physical keyboard (QWERTY), and I've attached what I get from it (made with Softmaker Office for Android on the Pro1) with the help of the Sym key when (as in most if not all browsers) I have no access to the long-press special key selection popup. Unfortunately, while this key map covers much including everything the German language uses, I already can see it does not even remotely cover the French accents. keys.pdf

I just confirmed that the brand-new German AusweisApp2 (meaning "passport app 2") – which uses the credentials stored in the latest version of the NFC-enabled German passport (which I had to renew recently) to safely and securely authorize me online in various situations like dealing with the authorities (instead of having to visit them in person) for things like registering a new car – works perfectly with the F(x)tec Pro1 running LineageOS 18.1 (with Magisk and MagiskHide). Our phone is not yet mentioned in the list of compatible smartphones, but it might be soon, because I made use of the

I got a response from Fxtec on my support ticket: Hopefully they do fix it for the Pro1, and not just the upcoming Pro1 X!

I had this problem also on stock when Android did a soft restart and somehow caps lock was toggled before it (I think in closed state). That was during my software reboot-loop I think when kernel was still counting up but Android has restarted on top. So I don't think even if the keyboard driver is the reason.

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