FlyingAntero

That could also be done with MacroDroid and Keyboard/Button Mapper. Atleast there is a setting for it but I did not test it.

That feature can be automatized with MacroDroid and Keyboard/Button Mapper. I just tested that it works. Also, you can have screen timeout quick tile on stock too. There are apps for that in Play Store like Caffeine.

This could be possible with Tasker. Please, check the guide from below for reference. Obviously the trigger has to be changed from WiFi to keyboard state. According to the comments the max delay for screen lock is 30min in Android Pie for AutoTools. Alternatively you can use Custom Settings action for longer delay. Permissions needs to be tweaked via ADB. Disable and enable your lock screen at will (No Root!) BTW, have you tried Smart Lock? It can be very handy also. EDIT: Yes it is working. See more from below.

I can get 6h SOT without battery saver for 1 day. I posted a battery graph to other thread earlier. Do we need two separate threads for battery talk?

Do you mean that FinQwerty layouts are working just like on stock If you enable "custom keymap" on LOS?

It does not work. I have Xperia XZ1 Compact which is working fine (VoLTE) with the same SIM. My carrier also checked that I have modern SIM in use which supports VoLTE.

If you launch Snapdragon Camera app via hardware camera button you will not see preview of previous pics. It will show preview icon if you launch camera via app drawer.

It is grayed out and I cannot switch it on.

I contacted my carrier but they claimed that Pro1 does not support VoLTE. They used my phone number to check it from their system and I also linked F(x)tec website to them. Then I told that I know others that have VoLTE enabled on Pro1 so it should support VoLTE. They started to investigate the issue further but the end result was that they believe that Pro1 does not support VoLTE or my device is broken. They even asked if I could test with other carrier that is confirmed to work with Pro1. My carrier said (or atleast claimed) that they are not using whitelisting. Every VoLTE support

@tdm So we would need to provide those code lines for the changes compared how the keyboard works when German is selected? Am I right? I can find the numbers for the keys from GitHub but is the whole "keymap code line" available some where for reference? I can find some examples from the closed issue 35 Keyboard layout QWERTZ not correct #35 I can try to provide correct code lines for QWERTZ. I don't know how to handle the QWERTY since it is much different than QWERTZ. It is difficult to place Å, Ä and Ö to right place and move other keys some where else.

Generally, I like that there are only minimal changes compared to the prints. For Finnish I would like the layout provided by FinQwerty. Most important changes are: Y <-> Z Ü -> Å Then it is a matter of opinion which one is better: A: ß -> + + -> ' B: ß -> ' I think that most of people would prefer A option even though I like the B option (only minor changes). I just like that Yellow arrow combinations are like they are printed to keyboard. Shift combinations for the top row can be like they are on the FinQwerty layout

Did you remember to select QWERTZ from the device specific settings on LOS (settings>system>keyboard)? It should be working good with German.

It is used for collecting depth information. It can not be used to actually take a picture. Depth sensors usually has a little effect to the picture quality now days.

It is a known issue on stock ROM. I believe that random reboots on low signal network is also relared to this.

I am from Finland. QWERTZ suits quite well for us since we have Ä and Ö letters also and instead of Ü we are using Å. Then Y and Z needs to be swapped. So, only minor remapping is needed from QWERTZ to Scandic.

I am not familiar with German letters so I don't know either. I see that you implemented FX combinations also (like FX + c gives calculator). Nice! So far I haven't seen any issues with the keymap.

Great job! I installed the latest version successfully. First row shift is acting like a FN (except that shift + ß gives ẞ but that is probably like it should).

Those are Android's default combinations but Pro1 is missing search key. Would be nice to know how to remap it. Chen was wondering to add search key but community did not like the idea. See more from below.

Yes, you are right. They just list devices that are guarentee to work. I think that VoLTE could work with my carrier on LOS (Pro1). I will report the situation once I will flash LOS again to Pro1. I am just wondering what might be setting that enables VoLTE on some ROMs.

I live in Finland and my carrier is DNA. I have two devices: Pro1 and Xperia XZ1 Compact. Here are my results: On stock firmware (both Android 9.0 Pie): Pro1: VoLTE is disabled XZ1 Compact: VoLTE is enabled and working On Lineage OS Pro1: Not tested XZ1 Compact: VoLTE is disabled and not working XZ1 Compact is running unofficial version of Lineage OS 17.1 (Android 10) so that might be reason why VoLTE is not working on LOS. The changelog says that "IMS does not fully work for some carriers yet" and I flashed different firmware to phone before I flashed LOS

New color option coming? 🙃 https://mobile.twitter.com/chenliangchen/status/1288801744328298498 Chen:

For me, it took about 1-2 weeks to get used to the size. Also, I had to change my grip little bit. First I tried to type while keeping my palm "behind" the phone but then I kind of "dropped" the phone more to my fingers. Now it is much more natural. My previous QWERTY phone was Droid 4 so it was big change. If I need to type few words I might use virtual keyboard but for everything else I use physical keyboard.

I don't have LOS anymore installed but if I remember right, that was not the case in every situation. Finnish layout changes these base letters compared to the prints: Y <-> Z Ü -> Å ß -> + + -> ' However, I was still not able to type "@" with "Yellow arrow" + "Q" combination even though "@" is printed to "Q" key as a upper character in QWERTZ.

According to what @moep said earlier it seems that QWERTZ model is not in production currently. Maybe the supplier is not able to ship keyboard mats or the production for QWERTZ units has ended.

OnePlus Nord has the same issue and it seems to be even worse. There is a video on the article. The OnePlus Nord already appears to exhibit display tinting issues I am wondering if this issue could be fixed with custom kernel like on Pixel 4 XL? Custom kernel fixes green tinting issues on some Google Pixel 4 XL units