Craig

This is expected and has an explanation. On QWERTZ, the printed yellow should align with German layout I believe? If you change layout, then that layout will change the key that comes out based on the printed yellow letter going in. So for example if the finnish layout changes a to j, then if you press a j will come out. same thing for the yellow printed characters. I'm not good at explaining cuz I dont have a qwertz keyboard to give examples.

Some of the AOSP apps can be replaced with google apps if you use Opengapps. Browser is an example, it can be replaced with chrome. Just an idea if you're already a gapps user.

then how did you unlock?

You can do that without rooting by using adb root (enable in developer options) - if adb is working!

Not yet, but there's already a github issue about this missing setting.

I'm too lazy to confirm on phone, but on my pc using us-intl-altgr its right_alt " (right_alt+shift+') then e. That leads me to believe on pro¹ us int'l it'd be " then e (shift ' then e).

Yeah the assume part is the problem. Ask them when QWERTY will be in stock again and I expect you will get the same non-answer. Or maybe they'll have an estimate. But I doubt they'll try to claim they're in stock cuz even their warnings about dont share emails don't completely stop the spread of information, and the people waiting almost a year would be in uproar 😉

Technically we could program our own custom keycode, so if there is some combination LOS can't make by default, we could define it ourselves, if there were such an app. (I realize you actually made such an app, but if stock fixes/changes slant arrow behavior or you want to make it work for lineage, I doubt it'd take long to update.) For customization, there's another dumb thing stock did regarding slant arrows btw. Although in hardware they are separate (unlike the two shift keys for example), they assigned them in software to the same keycode! Before TDM made his custom soluti

They put the definition in for PC keyboard not thumb keyboard. We have thumb keyboard. How is there controversy? Why would someone not want this fixed?

The reason finqwerty is NEEDED is cuz stock did it wrong. It's not needed with Lineage cuz you can use the included layouts! We have Altgr! We have a solution for slash/questionmark.

How is that controversial? Is there anyone who thinks they didnt make a mistake there?

Yes. That's still true in LOS for QWERTZ. You just have a lot more default assignments than QWERTY (as we only need slash and question mark, you've got quite a few the way they did it).

Yeah exactly, he is fixing what is broken. There is no slash key. With stock if you pick any layout at all you have no way at all to really use them because then you have no way to get slash key with any english layout, and using us-intl is useless without alt-gr as are probably most of the other foreign languages. And their hack of a workaround (using no layout) makes it so shift doesnt even work right. So 100% what Eske said, this is most definitely a fix. Plus its a feature cuz we get home,end,pgup/pgdn, F1-F12 keys etc all natively, something Fxtec should have implemented and ho

That's what they do on Sailfish btw. Slant arrows are Right_Alt. And the Sym key is slash/questionmark. And that's a perfectly acceptable solution too. Both better than stock. What I actually hope to do, once we can reconfigure right slant arrow, is make it my slash key. But people who use international layouts may set it as Right_Alt (in addition to the right_alt lineage gives us on sym key and is the standard android keymapping for sym key on other devides like photon q etc, hence why its the key used for Android keyboard layouts level 3, just like PC, and something I assume wil

Yeah snapdragon camera has lots of issues. I watched a bit and was wondering if maybe it had to do with it seemed to sometimes keep trying to refocus. But yeah not much sound going on that I noticed. Lineagecamera is fine, yep. Another alternative for stock or Lineage is OpenCamera. It even recognizes our focus and shutter buttons. Although if you're trying to use the button with stock you'll need a 3rd party app to prevent the camera button from auto-launching snapdragon app, one of the many other problems with stock that were reported last year.....

How odd, maybe that's something funny with LOS keyboard definitions. I just took a quick look. You're appear to be using slant arrow combinations, which are hidden from userspace in Lineage. Modifiers you could use in your app would be left_alt and ctrl like stock, and LIneage also has right_alt on sym and meta on Fx key, but no access to slant arrows by apps, etc. (What we can do with slant arrow combinations under linage is define what keycode comes directly out of the driver). I haven't looked very close at your app but if you want it to be compatible with LOS, suggest us

It's a 21 minute long video, what exactly are we supposed to be looking for?

Hmmm. so if you cat /sys/class/rtc/rtc0/since_epoch after starting up with no wifi or sim it won't be accurate?

We need to get a Pro¹ in first place....

There is a fxtec community discord server, with a lineageos channel and we'd love to have you 😉 https://discord.gg/4GVR7rA There is also a bridge to discord server from riot/matrix: #pro1-lineageos:reverso.de There is also #fxtec on freenode irc. That's the only place I've seen los development discussion before, including mccreary in the past.

Based on what david said earlier I'd try the pixel 3.

Most things that are broken on stock have been fixed (or were never broken in the first place) on lineage....

You'd have to go way back in this thread to find where tdm explained it. But there is a keymap file we can edit that affects slantarrow combinations. Just understand that slantarrow combinations are handled in the driver, not in userspace, so the combination generated is what's sent to the keyboard app/layout. As to why? He probably explained his reasons. For me, now that I understand it, the reason I like it is it works ALWAYS. Some apps ignore the layout or keyboard settings, but they dont ignore the keys coming from the driver. With QWERTY the way F(x)tec designed the keybo

False advertising. When preordered, it was stated that they would be delivered before others. There's some type of breach of contract involved there and I bet there would be a chance of a legal case. But waste of time and money and wouldn't get you phone any quicker. Getting upset about it all over again is silly. We went thru this with Clove & Dragonbox last year, and they got 40 each iirc. Sound like this Japanese retailer got even less. Comes down to, if you want the device, and find another way to buy it before your official order comes thru (like when a retailer gets th

I'm just trying to understand. So with the slow OTA method you chose for your unofficial builds, we will have to to reinstall gapps/su? Or we won't? And the fast method you're not going to use because it wouldn't work for those with gapps or su, unless you made and additional build specifically for those with gapps/&su, in which case upgrades would be fast and we wouldn't need to reinstall gapps/su? And if this additional build were in fact made, would it require user use a certain version of gapps? (For example I use opengapps-mini; I like that it replaces AOSP apps and up to