Leaderboard

Okay, a few things to note here: The slant arrow is not a standard key. Unless I missed something, it is never stated anywhere that the slant key is supposed to be a Fn key. Certainly most keyboards have a Fn key. But it was not on the original PC102 keyboard and it is not difficult at all to find a keyboard today that lacks one. Now, as for actually handling the slant arrow key: (1) How would you propose to do make it behave such that one can make it both act like a Fn key and have the yellow labelled keys be available without extra keystrokes being repor

I went directly from stock to Lineage and have Magisk 20.4 running on nightly 20200720. Also, @tdm thank you very much for all your work getting an official Lineage build for the Pro1.

So "/" and "?" are "device specific features?" That is what is incorrect behavior and incredibly inconvenient for the user. Luckily, the yellow symbols on the top row can be redirected to shift, but the insanely placed "/" and "?" cannot since they are on a letter key which is already making use of shift. I can't even imagine how they came up with such a scheme nor why they thought it would be a good idea. It's a human factors nightmare.

I think you misunderstood my point. When you press '/' on a normal keyboard, you don't do it with Fn down. That is incorrect behavior from the keyboard driver. An app would be within reason to interpret this as Fn+'/' and do something unexpected, or nothing at all. That said, it is very much possible to make the slant arrow into Fn modifier for the keys without yellow labels so you could press eg. Fn+1 and get F1. In fact this is one of the standard customization options on Lineage. You can do this with any key(s) that you choose.

Which missing standard functions are you referring to? The only yellow labels I see that isn't on a standard PC102 keyboard are the emoji label on Alt and the WWW label on the spacebar. Both of these are functional on Lineage.

I am pretty sure it's not. Try running getevent on stock and then pressing Fn+P to get a forward slash. You should see key down for Fn followed by key down for '/' or something similar. The Lineage kernel tries to emulate a normal keyboard as much as possible because the stock way of doing the keyboard is pretty awful. You must leave keyboard layout unconfigured or things break. Which is very confusing to many users because Android tells you to configure the keyboard layout. Further, because of this, you cannot leverage any of the locale specific keyboard layouts that ship wit

Totally, been using it since January.

I like ctrl + arrow keys for moving around in text, skips the cursor next/prev word.

It is possible that the Lineage GPS configuration files are not optimal for certain areas. Me or one of the other devs can look into that.

The thread is going far astray from display into keyboard land.... I wonder if it should be split, or these post merged into a different thread. Any good suggestions of a destination thread? Anyway I think that @Hook has the main point in this. The shifted Qwerty is not an optimal starting point, and that is what @tdm have found a quite clever way to work around so the keyboard acts like a (shifted) standard keyboard, that then can use standard language layouts on top. But I personally find that using qwertY on the qwertZ keyboard as done by FinQWERTY is a better starting point. Incl

Thanks. I have lost the overview: can someone wrap up? what are the important problems remaining in the official android? - call volume setting - wake- and backlight-on-keypress not enabled - Sym key Is it possible to use this phone with the official android?

I was reading some articles about this, and apparently someone else stared a forum on this topic, saying their Samsung Galaxy S10E got this message, too. Must be a mistake on AT&T's part like this article says here

...And can be combined with shift for marking. (You have to press shift before Ctrl)

I just found out by chance that Ctrl + Enter will submit a post on those forum. I'm using Fulguris Web Browser, I'm not sure that's relevant, it probably works the same on Chrome and others. I've known for a while that Shift + Enter goes to next line without creating a new paragraph. However that Ctrl + Enter trick is new to me. Though I guess it's always been there as a means to submit an HTML form. What are your favorites little-known keyboard shortcuts?

FWIW, I thought I should note on this thread why my device was not booting anymore, even on a new build: Magisk. Some of the recent changes must have broken this. I tried an older version and the latest from the canary channel, same problem. Back to standard SU for now.

Sound being borderline unhearable. I installed LineageOS and very briefly tried the camera: WOW WTF, it's miles ahead of the factory camera!

64 wpm from the Pro1. Physical keyboard, of course 😋 When I first got the phone in January, I struggled to break 30 WPM (and that was also before the OTA update that fixed the key ghosting problems). Things have gotten much better with practice.

I got a replacment screen from fxtec and it also has small deadzones at the edges of the screen. Maybe 5 mm wide. But they aren't really dead because they register swipes when I move from the middle of the screen towards the edge. But doesn't register if I swipe from outside an in, or try to press buttons close to the edge.

Indeed, what @tdm and @Tsunero said. I ended up leaving Verizon and going to AT&T. Hope you have such an option.

Your problem is Verizon, not the phone.

The phone works perfectly fine on reasonable GSM carriers. Verizon is neither reasonable nor GSM. Your fix is to switch to another carrier. T-Mobile, AT&T, or any of their MVNOs work perfectly fine. I'm on PureTalk which is an AT&T MVNO. Paying $80/mo for four lines. Or, if you insist on being abused by Verizon, I'm sure someone would be happy to buy the phone from you.

I have also called service provider's IVR system and I haven't noticed call is quieter than before... or at least it is still too loud.

I just called my mailbox and it's still pretty loud, even on the lowest call volume setting. mailbox = German for voicemail-thingy

Indeed, audio sounds much better overall. Awesome 🥳🥳🥳

Sadly I can confirm that wake- and backlight-on-keypress are not enabled with this update 😞 And Sym key seems to do nothing still...

Woooo, AMAZING update. Finally that very nasty sound crackling is gone, just tested it in several different games (including dosbox) and they all sound very nice now. Keep dem fixes coming!

Yup, looks like it just dropped!

Hey, some very good news on twitter, finally looks like some software fixes coming: https://twitter.com/chenliangchen/status/1280900929273958402 I'm hoping that whatsapp thing means the audio-crackle, which is one of the major issues (and a 1 line code fix) that has been plaguing everyone still on stock OS. And glad they fixed Esc key. Hopefully they also enabled wake-on-keypresss (for every key) and keyboard backlight on keypress too while messing with Esc. Hopefully they made SYM key right-alt. Hopefully set keyboard to alpha. Etc. Hopefully this also means someon

New mailing from Fxtec: Hello! We hope you are well and keeping safe. We just wanted to get in touch to give you an update with regards to manufacturing and shipping of remaining customer orders, but also to fill you in on everything that has been going on with the F(x)tec team. We are still currently understaffed as some of the F(x)tec team are on on furlough. This has undoubtedly resulted in our customer service and email responses taking much longer than usual to sort through and respond to, and for this we really do apologise. We are working through queries as quickly as we ca