Slion

That is very optimistic.

Yeah that can take a long long while too. Feeling sorry for you @LAMENT

Last I checked reddit app didn't do landscape. Yesterday while on a call I wanted to switch to speaker phone and remembering my Nokia E7 reflexes I opened up the keyboard with little hope it would automatically switch to speaker. It didn't and the phone app is stuck in landscape while on a call. I wonder if there are third-party phone apps that would support that.

As I'm investigating how to implement qwertz support I thought it could be nice to have support for gamepads too. Any gamer out there wishing for a such a feature? Maybe it just does not make sense if you do not have analog stick support anyway.

For me too, speed is not the main reason for wanting landscape physical keyboard. Redacting and formatting large posts and articles or files is where Pro1 shines over virtual keyboards.

Poorly designed then 😁 All devices can do landscape. Sadly way too many applications do not support landscape mostly for cost saving reasons.

SwiftKey is the software keyboard, you can use it together with keyboard layouts such as FinQwerty or FxQwerty.

It could be it is not on the default keyboard mapping. What's your layout Qwerty or Qwertz? If qwerty you could try FxQwerty it gives you a bunch of similar shortcuts albeit different. I'm not sure if FinQwerty would help there.

That's just 163 Pro1 on that pallet 😉

I do believe desktop keyboards hide the Function key from OS and applications mostly for legacy reasons. Back in the days OSs did not have support for Function modifier. To keep doing this on modern OS like Android is questionable. Hidden Function key certainly has the added advantge to make a custom keyboard plug & play too but that point is also irrelevant for smartphone with built-in keyboards. By hiding the Function key from applications you reduce customisation opportunities from third-party application developer while increasing the work load and maintenance burden on lower leve

I do.

It's just about enabling third-party solutions.

My impression is that if LOS would mostly stick to stock scan code they can still implement all their features using layouts without breaking existing third party layouts such as FinQwerty and FxQwerty and other apps. However there is still that other controversial issue of the ALPHA vs FULL keyboard. I sure hope that does not make it to stock without being configurable. Again I can't praise @tdm enough for his work on LOS and beyond. My point is that I'm under the impression that as far keyboard goes much the same could be achieve while providing compatibility with stock and third-party

Indeed, to me WYSIWYG rules. PS: I have not giving up on your custom qwertz layout 😁

More code path harder to maintain. It's very unlikely I will ever bother adding LOS specific features in my apps, mostly because I'm not using it for now. The point of LOS is that it is compatible with Android. I do think fixing what's broken like the sym key makes sense. However leaving the rest of the scan codes and default mapping untouched would have been the easier and better option, as far as compatibility goes.

Sym key is indeed broken on stock at the driver level if I recall well. It should indeed be one of the Alts.

Compact laptop like keyboards have been a thing for over a decade. This morning I happen to have four keyboards on my desk and just as many Fn keys 😁 Though PC keyboards do not usually expose their Fn keys to application developers which is I understand exactly what @tdm has done on LOS. However luckily for app developers mainstream smartphone OSs have typically exposed Fn as any other keyboard modifier which makes a lot of sense and provides much needed extra customisation options on exotic devices featuring non standard keyboards.

I would not call it broken, I would call it basic. I also understand why FxTec did not push too hard to improve it knowing they can't please everyone and developers can publish their own layout anyway. I merely use a custom layout to extend the existing basic functionalities. Since I have a bunch of apps out there making use of keyboard shortcuts I was just trying to understand the differences between LOS and stock having never used LOS myself. Now I think I do understand: Changes in the driver means scan codes are different meaning custom layouts are not compatible. Func

@tdm does FinQwerty and the likes even work as intended on LOS since the keyboard driver was changed and the keyboard was set to ALPHA? Stock qwerty provides things like Alt + U for umlaut dead key I believe. FxQwerty provides possibly more of such international characters though the current version is geared more toward French than German it does give you ß with Alt + S.

Same opinion, so why would they stop taking QWERTZ order? I guess I can kiss my AZERTY goodbye 🤣

@EskeRahn I would create a new thread called "No Function key on LineageOS", tag it with keyboard and lineageos I guess.

Indeed they are as you will never find them there on any other keyboards.

Not so, Function key is for device specific features, meaning any app using it is supposed to be aware of the hardware it is running on.

/ and ?

My point exactly, slant arrow is Fn on stock.