Leaderboard

I've implemented a new feature in Lineage OS Pro¹'s keyboard driver to be able to use Fn+Tab as Alt+Tab as this is most convenient for multitasking with two thumbs. This thread is to track that issue specifically so please stay on topic. I'm trying to contribute this back to official Lineage repository. Here is my change request on Gerrit: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315155 There was also a pull request on GitHub but that's just going to be closed as the GitHub repositories are just mirrors I guess: https://github.com/Linea

I agree. The point is to comfortably switch apps while keeping your thumbs on both sides of the keyboard and not having to use the touch screen. Yes. I had added back the "+" manually and it is building now ... 60% and going strong. I expect a flashable LOS 16.0 with Fn-Tab functionality in 2 hours or so ... 🙂

@Slion, I think you introduced a typo in the latest revision of the patch. Build fails with ../../../../../../kernel/fxtec/msm8998/drivers/input/keyboard/qx1000.c:1709:41: error: expected ';' after expression size = sizeof(struct gpio_keys_drvdata) ^ I think that line should stay like in the original code: size = sizeof(struct gpio_keys_drvdata) + pdata->nbuttons * sizeof(struct gpio_button_data); You probably deleted the "+" by accident in the latest edit.

You don't have F(x) Service installed by chance? ;)

Works for me with AOSP keyboard on LOS 16.0. Others report it also works on LOS 18.1. So maybe the feature can be switched on/off somewhere. Do not know where, though ...

On the subject of "it's obsolete the day it's out", well yeah, it's true and the price is a little bit out of touch compared to Samsung mega factories, but it's not the same production scale, and we have enough alternatives if we must. But this obsolescence is not very surprising tbh: I never bought a phone people were not scoffing at one year later, asking me when I'll upgrade... at best. Most times they look at you with pity you couldn't buy the latest iphone the day you got your normal "I'd rather buy cheap phones I can break than break a 1.2k iphone and have to pay hundreds for a new scree

The patch (patchset 6) applied cleanly against my LOS 16.0 tree. Just started the build ...

That's different. When you write all caps irrespective of the CapsLock state, you are in "Super-Sticky-Shift" mode. One enters that by hitting Shift twice (without pressing any other key). Disable by one more Shift press. That's a feature, not a bug, I guess. 🙂 The phenomenon @Slion mentioned is an inversion of CapsLock. I.e. with LED on you type minor letters, with LED off capitals.

Why am I not surprised you are using a different filesystem than everyone else? 😉 Good luck with the new build!

Do not worry, has happened to me once on LOS 16, too. I did not reasearch the issue, though. Just rebooted. 🤗

Is it really possible that we have not photo thread yet? I'll start one with one of my first snaps to test the camera. Shot with the "Manual Camera" app as JPEG + RAW (DNG), RAW developed with Silkypix Pro Developer Studio 9, which took far too much work to get a result similar to the original JPEG.

I have one more bit of information that might help you simplify your patch. The keycode definitions in qx1000.c support modified keycodes, e.g. KEY_TAB | KF_ALT While this does the expected thing, triggering the code path you want, it does not support multiple keyup events expected by PhoneWindowManager.java. Consequently if you make these changes: diff --git a/drivers/input/keyboard/qx1000.c b/drivers/input/keyboard/qx1000.c index db637ff17455..d53cbeb4ec7a 100755 --- a/drivers/input/keyboard/qx1000.c +++ b/drivers/input/keyboard/qx1000.c @@ -304,7 +304,7 @@ static const u16 qwerty

I think I fixed it in the last patch. Did a build and testing it again.

I don't think we want most of the functionality. We want the actual Alt+Tab functionality. that the point of those changes. Yeah we don't want that when we can have the real thing. Reminds me of a bug they introduced lately in Vivaldi Web Browser where you have to hit Ctrl+Tab twice to get to your previous web page, that pissed the hell out of me 🤣 I'm open to alternative solution but I doubt there any while you can't remap the right Fn key from KCM to actual Alt. I was floating the idea of having a new keymap that would not mask the right Fn key from the system but that's n

Yes, the behavior is a bit different. Instead of cycling through the list of apps by holding ALT (or Shift+ALT) and pressing TAB multiple times, it only toggles between the two most recent apps when TAB is pressed multiple times. But you can still select which app you want using the touchscreen. The code paths for these two methods of activating the task switcher are different. Your changes to the kernel driver are triggering this code: https://github.com/LineageOS/android_frameworks_base/blob/lineage-18.1/services/core/java/com/android/server/policy/PhoneWindowManager.java#L3421

This is a great idea, but there is a much simpler way to get most of the functionality you want. See https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315172 and https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/315173 With these two small changes Fn+TAB will bring up the task switcher. The behavior is a little different as you must press the key combo twice to switch to the last app (vs. automatically switching when the keys are released). Also, these patches introduce a bug that disables Alt+TAB :-( That's certainly unexpected beh

I think we are saying the same thing. Maybe I wasn't clear-- I do not always have the terminology right. All I was saying is that, if recovery is showing you are on partition a: and you adb sideload the update, it still shows partition a: You then have to reboot to recovery and it shows you are now on partition b: Wnat actually accomplishes the change in partition is magic to a noob like me. 😄 And yes, reboot to recovery is not needed after Magisk and Gapps.

Yellow arrow

Indeed settings are spread all over so can be hard to find, unless you can guess a keyword and find it by search.... I'm currently looking for the rather odd 'feature' of vibration feed-back on hardware-keyboard touch. And no the setting for haptic feedback on touch is not coupled with this.

I obviously don't build LOS, but I've never had a problem with Gapps showing up when sideloading LOS via ADB. I have always used @tdm instructions, as mentioned by @EskeRahn. I adb sideload the latest LOS nightly, then reboot to recovery, which changes you from the a/b partition you were on to the other a/b partion where the update was installed. Then I adb sideload Magisk and Gapps (in that order, if it makes a difference-- I don't think it does).

Nothing against it, but just to be clear, what do you mean with Fn? The key with the F stylized after the Fxtec logo?

Right, this also works here (that was I ran into).

Sticky shift (and super-sticky-shift) work fine here on 18.1, using AOSP as soft keyboard as @claude0001 indicated.

Solution: adb install <full-file-name-apk> Though really we should report those issues upstream to Lineage I guess.

Good point, Fn+Shit+Tab works as Alt+Shift+Tab would with that patch already.

Could it be some a/b stuff. The normal procedure install the main image to a, and then a recovery boot, and the gapps are put to b. (see batch a bit above)

Alt+Sh+Tab is also useful, so would be nice if Arrow+Sh+Tab could mirror that as well, as this could be done with thumb+index left side. (Your change might do that already, have not looked at the code)

We'll see. I think the proposed behaviour is definitely useful. If the patch does not apply cleanly, I'll try to backport it. If all goes well, I'll start a LOS 16 build with your new driver code in the evening and will report tomorrow.

That would make a lot of sense, indeed. If the patch gets accepted in the kernel branch, would it be in effect for all LOS branches (16.0, 17.1, and 18.1), or just for 18.1? I could test against 16.0 by applying the patch to my local copy of 16.0. Should I?

No idea. I use the normal AOSP keyboard shipping with LOS 16. I suspected it was a feature of the latter, but at first sight I can't find any setting related to that. When I hit-and-release "Shift" once (without any other button), I enter "normal-sticky" shift, i.e. the next letter is capitalized, the following ones are lower case again. This is a quite common accessibility feature to enable use of a keyboard with a single finger (for e.g. disabled people). Hitting "Shift" twice makes capitalization "super-sticky" for me, meaning all letters are entered as capitals until "Shift" is p

I have experienced it again on LineageOS today. CapsLock was off and it has started writing capitals. Changing CapsLock state had no offect but pressing and releasing shift had - it stopped doing it after I have pressed it once. I don't know if it missed a release state or what happened anyway but here is official LineageOs 18.1 running on previous build (not the actual latest).

Thank you. 18 years are pretty good which is only possible if her health is good and also her owner takes car of her. Sad she has passed but I think she had a good / valuable life. My cat is really clever and patient (as she was in her entire life) and her eyes, ears and brain are still healthy. She had an accident with my dog years ago and her spine has injured majbe around 6-7 years ago or so and sometimes she limping for one of her rear legs, but sometimes it can not really seen depending on maybe a bad jump. She don't really jumps anymore (only when it is necessary), but

Yes, it is. Maybe something does not run or not in the right time... Right. Also it checks for the existence of custom keymap file, and if so, it disables keyboard-related options (so not only if it was enabled, but also if it exists). I think it was in use during testing and didn't really take much attention otherwise. No, everything was fine except the filesystem. It checks for a directory using a method which is not supported under certain filesystems (but only a few). Now it compiles since about 3 hours I think, so it will go through if it does not run out of sp

She is a beauty for her age 😃 She looks a lot like mine, sadly she passed a few years ago, she was over 18 years old.

I wonder if this could be related: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/314887 Maybe there is a fix coming up.

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 😄

The location has changed, the teardown guide is now here: https://github.com/imax9000/fxtec-pro1-teardown

It's because some people are getting to take only out of focus photos, like I am. 😩

Oh man. It must be that my camera is kaputt. (Maybe from the beginning?) I never could figure out how to get the camera to focus properly. All my shots are ridiculous, as if I was using a 2004 VGA phone camera 🤦‍♂️ Example: Taken of my new toy and my youngest feline from inside the garage. Such a garbage focus.

Are you a collector? 😄

Finally i got my third Pro1

...and she is my 15 years old cat four days before the rainy day above, in a sunny day:

You backed them via IGG if I recall correctly. You can't compare the two. I'm not agreeing with how things work. Spec changed, I would want my money back too. But, you bought via IGG. After a backing term has passed, this money is used to start up. New design = startup. IGG backing = basically no rights, not afterwards at least.

Good morning everyone, The credit was transferred to my account "immediately" after my post here. In any case, I received an email from f(x)tec within a few hours and the money arrived in my account in Germany via TransferWise the same morning. I'm talking about 13 January 2021, the day I started this thread. Greetings from Germany kabay

Just some photos done in noob mode (stock camera, default auto settings)

....Here a simple Crop from Paint to FHD (0,6MB)

You mean like to show what the damned Mole did to my lawn in cover of the snow now melting? EDIT: Removed to clutter the thread a little bit less....