Leaderboard

Thanks @tdm, links added here 😁

To configure Night Light you need to edit that config.xml resource overlay: https://github.com/LineageOS/android_device_fxtec_pro1/blob/lineage-18.1/overlay/frameworks/base/core/res/res/values/config.xml It is in fact overriding values from the platform config.xml in which you can find all defaults: https://github.com/LineageOS/android_frameworks_base/blob/lineage-18.1/core/res/res/values/config.xml From the two quadratic equations defined in our config, Pro1 uses the native one, at least in the configuration I tested: config_nightDisplayColorTemperatureCoefficientsNative Red co

As you mentioned - it's all about the scancodes. This means manufacturers can make all keyboards the same and just put different labels on the keycaps to make mass production cheaper then rely on customers to chose the matching language setting in their operating system. The ISO physical layout (tall enter, split left shift) has many language variants, ISO-US keeps \| near where it is on an ANSI (wide enter, big left shift) board while ISO-UK one puts \| next to left shift and ISO-FR (French AZERTY) and ISO-DE (German QWERTZ) don't have a \| key at all. From what I've read I find it ver

The places where I saw "\" character are: The right of a small backspace above big enter The right of "right shift" below big enter in a place where turbo was placed in later keyboard models (to reach power / sleep / wake functions) Above right shift but left of big enter Above small enter and below backspace (between them) The left of ZXC keys Maybe there was also a layout where "\" was placed between CTRL and ALT keys or a similar position So its placement is not constant at all. However, if there is a button between left shift and ZXC keys, it is de

On my proposal the left AltGr should really be labelled Sym and then everyone can map it to whatever they want, Del for instance. The right AltGr is really needed, not least for Alt+Tab.

I think @tliebeck's question (which is also the thread title) is quite easily answered: because we need at least two keys which standard keyboards usually have on a sixth row above our five rows, Esc and Del, and unfortunately there doesn't seem to be a standard for five-row keyboards which include those two keys. Plus, there's at least one special key for Android which has no analogy on PC keyboards. That said, Fxtec could perhaps have found some existing keyboard on one of the many existing laptops/notebooks/netbooks than would have made a better model for our keyboard than what we have

(Just downloaded, will flash within minutes 😍) It did not install with the previous AICP-q boot.img, but it did install with the latest LineageOS 18.1 .img open_gapps-arm64-11.0-pico-20210712.zip installed as well. So now i'm back on AICP after being 'unfaithfu'l using LineageOS 18.1 for some weeks on the 'final sample' too. Lovely. 😁 Battery saver "Battery may run out soon ....blah blah .... 40%" I would say that kicks in a little early.... But it was when it still installed apps in the background, so the projected remaining time was low as could be expected. I usually turn

Hi everyone, first post here ! My "traditional" smartphone on / off key is unfortunately dead, I can use it, but if it decide to shutdown I won't be able to boot it again. I'm looking into buying a Pro1 X, the physical keyboard being obviously the major argument, but I'm wondering the ETA of delivery. I won't be able to use my current smartphone for too long. I've read some threads talking about months or year of waiting for some costumers of the Pro1. The Pro1-X seems to be fairly new, November is the first shipping of this model ? I've read about the change of architectur

They were supposed to be sent in March then they had to change the chip and delayed until August, then again to October/November as currently advertised. They have been giving monthly updates on Indigogo but nothing yet in September so should be any day.

I think so. It does fire as a keyboard key, but even as an accessibility service you don't get it because the screen is locked. Same issue on Lineage yes until we implement a proper sensor for it. See post and link above. I may get around doing some clean-up at some point yes.

Just an idea on Lineage. Perhaps you should grey-out or hide the screenfilter when on lineage, until you find a workaround? In the Advance settings I guess the four key-filters are irrelevant to Lineage too, right? If so you might hide (or disable) when on Lineage. I know that on stock you had to use the proximity sensor to wake the screen, as the hall sensor did not fire. Does the same go for Lineage?

I don't use Alt-Tab much (yet, that is – maybe I should start to), but I guess I would be fine with using left-AltGr + Tab, too (left thumb + left index finger). I confess I still find the plethora of modifier keys on the Pro1 keyboard more confusing than helpful 😉

The funny thing here is that if you on a PC with a keyboard with 'tall' Enter key select US-keyboard (That is what I normally use), then you will find \| IS placed next to Z, so the two keys seem to be wired the same - rather odd... I have not checked their scan-codes. That is the key in e.g. UK keyboard three right of L is new, and NOT the one above Enter in the US-layout, that one is MOVED to left of Z. Strange...

US Int. layout works fine on LOS 18.1 yes. Though the default one provided by Android is far from complete, many AltGr character mods missing. The French accent dead keys are working though.

Me, I'm just happy it boots... However you have a point, if your phone does not boot I guess it's really secure 🥴 😁🤪

+1, that would be a much better key placement. I will definitively use backslash at the bottom-left corner regardless of the print but that is a right place for it and none of the positions of back- apostrophe key is perfect (that would be the position of ESC), so placing it below backspace is a valid option. I would also live without that key but in my national layout, that button is "0" anyway, so it is definitively used by at least one international layout.

I like Slions version, except I would swap the backslash and back- apostrophe keys. to more usual placements, and especially in light of other qwerty-based languages where the accents are usually on the right side

Yes, with F(x) + A but it is not the latest LineageOS (but an official one).

Just a final note. Have most everything set up again and I am loving being back on AICP-- my favorite tweak being that it uses Slim Recents. Still tweaking, but everything is running smoothly.

This has very obvious security implications, however. If you do this, you should be aware you are disabling some of the malware protection Google has built into Android. As an alternative, you might consider including gapps inside your custom OS image, like the OEMs do. For more details on how to do this, see: https://github.com/opengapps/aosp_build

Right now you will need to use 'adb' to install the custom keymap, and there isn't any app to help you create the map 😕 @Slion made this nifty QWERTY keyboard image with each key labelled with the 'key number' in yellow: The manual process is to choose which key you want to remap, and to look up the keycode you want it to generate in this list: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h You will need to convert the keycodes from decimal to hexadecimal if they don't begin with '0x'. The custom keymap is a file with lines contain

Okay, virtually everything in this thread is over my head. Can someone direct me to good sources to figure out how to create or modify a keymap and what to do with it. I'd really like to understand how to make this modification on my Pro1 and I'm willing to do my own homework, but would appreciate being pointed in the right direction. 🙂 TIA.

Just released Fx Service v1.1.0 with support for Lineage 0S 18.1 Should work on LOS 17.1 too but it won't on 16 at the moment. https://slions.net/resources/fx-service.8/ I have yet to test the release version I uploaded but the debug version worked fine. Though I did not use it for any length of time so I can't tell you how stable it is. I have not tested for regression on stock ROM but I reckon it should work just the same as before and does not bring anything more so you could stick to the previous version if you are on stock. When the accessibility service turns on it s