FlyingAntero

Actually, now the changes are there but it does match with the other site that I linked. There are 2 extra changes from other devices (LeEco S2 and Samsung universal 7880).

You can find changelogs for every build from here. https://www.lineageoslog.com/16.0/pro1 lineage-16.0-20200727-nightly-pro1-signed.zip

F(x)tec Pro1 is in the news! LineageOS 17.1 adds support for the OnePlus One, Sony Xperia XZ2, XZ2 Compact, and F(x)tec Pro1 XDA did not understand something so don't get too excited. We are on LOS 16.0 so no LOS 17.1 (Android 10) yet. I believe that it is coming in future but we need to hold our horses for some time.

Where can I find the base kcm-file for LOS that I would be able to edit (QWERTZ)? FinQwerty layouts are available here: - https://android.onse.fi/finqwerty/kcm/ I know how to edit those kcm-files but I don't how to create kcm-file from scratch for LOS. If there is kcm-file available I could create new one and add it with root. (I don't know how to add kcm-files without root).

@tdm has done excellent job with Lineage OS. I am very grateful of his work. However, I still have to comment that there are still some hiccups with standard language packs on LOS if you are using QWERTZ. Finnish is now usable on LOS when it was totally broken on stock. Layout provided by FinQwerty is still better and that is the reason why I have not switched to LOS as a daily driver yet. Some special characters are placed very oddly on standard language packs on LOS. "Yellow arrow" is on both side of the keyboard so combinations can be reached easily.

As a Scandinavian I want to make one point clear. We do not have "/" and "?" marks as independent buttons on standart ISO QWERTY keyboard. Typically they are used as below: "Shift" + "7" = "/" "Shift" + "+" = "?" (where "+" is located next to the "0") Pro1 QWERTZ is arranged like this on stock when you select German except that there is a catch. Now those keys are working like this: "Shift" + "7" = "7" so you have to type "Yellow arrow" + "7" = "/" However "Shift" + "ß" = "?" and "Yellow arrow" + "ß" = "ß" (where "ß" is located next to the "0") Developer of the

FinQwerty does not work on Lineage OS since the driver is working differently. The developer of the app would have to re-create the layouts to make it work on LOS also. Special characters are not working since you can not use button combinations for "upper characters" at all. See more from here:

Samsung is using its own Fast Charging technology which may not be compatible with Qualcomm Quick Charge 3.0. I can confirm that my Pro1 does not charge with Samsung charger (Fast Charging) but my Xperia XZ1 Compact (QC 3.0) does not charge either. Both work great with QC 3.0 charger and Sony "normal" charger. See more information from here. Quick charging technologys are not compatible very often and even the cable can an issue. Pixel 4 does not charge with Huawei for example. https://www.androidauthority.com/state-of-usb-c-870996/

I think that it is little bit unfair. Your frustration is totally acceptable but that should not affect to the product review. You can criticize customer service as much you like but don't connect that to the phone itself. I can recommend the phone to my friends but I can't recommend to buy it from F(x)tec currently. I have guided them to look for second hand units until there is stock available somewhere.

I got little bit under 40 WPM with couple tries. I was still able to beat the others. 💪

Also, check that there is not dirt or fluff in the port that could cause problems.

I am using Pixel III XL input model also. BTW, MGC_6.1.021_RP1_V1.3.2-BSG port is working very similar compared to F1v9.6_6.2.030 in Night Sight even thought if you enable A8.1 config (to fix viewfinder). The colors are not cold (like on MGC_6.1.021_F1_V1.7 when A8.1 config is enabled) but it takes little bit longer to take the picture. For normal shots it is working good. Currently I am using Pixel 2018 ZsIR Hdr+ config. Issues on MGC_6.1.021_RP1_V1.3.2-BSG Panorama is broken Slow motion causes camera app to crash

It seems that first official Nightly build is available 🙂 - https://www.lineageoslog.com/16.0/pro1 Edit: here also, https://download.lineageos.org/pro1

This is not related to the topic but what do you have there in the background? Is it a phone with a keyboard case?

Ultimate Typing Championship is now open for everybody due COVID-19 situation. You can participate by using any keyboard. Who is going to try with Pro1 😆. - https://www.typrx.com/ Maybe we can choose a common test and compete against each other?

I have not noticed random reboots since March but I have not been travelling due COVID-19 situation (I am working from my home). That makes me believe that the root cause of the issue is the same with some Sony devices. I mentioned that earlier. All random reboots that I have faced have happened during travelling.

Here is a quick Night Sight mode test with F1v9.6_6.2.030, MGC_6.1.021_F1_V1.7 (A8.1 config off and on), MGC_7.4.104_V0a and F1MinimalMod2.1 ports. https://imgur.com/a/oRDYp46 These photos are taken in dark condition when the camera app itself suggests to use Night Sight mode. In my opinion, F1v9.6_6.2.030 and MGC_6.1.021_F1_V1.7 gives the best result and I can't see difference between these two. When I enable "Forcibly enable NS config for A8.1" (it fixes the viewfinder) on MGC_6.1.021_F1_V1.7 port colors are much colder. Picture quality is still great. Night Sight mode on MGC_7.4.1

If I have understand right the color tone issue on OLED screens is usually caused by a greater variation on panels than the manufacturer initially expected. Then the pixels of different colors on the screen behave little bit differently. Manufacturer need to map how much any color needs to be dimmed so that the brightness of the screen is exactly the same for each color. If this mapping is wrong, we get to a situation where some color is brighter at some brightness level than others which causes color tone issue. OnePlus 8 Pro had the same issue during launch but OnePlus was able to fix (at le

I have done more testing. I noticed that MGC_6.1.021_F1_V1.7 port (by san1ty like other Pocophone F1 ports) has a "Forcibly enable NS config for A8.1" toggle which will fix viewfinder on Pro1. Unfortunately, the toggle will also affect to the picture quality. When the toggle is on colors are quite cold but noise level is ok. When it is off colors are much warmer. So, MGC_6.1.021_F1_V1.7 has potential but it would be great if we could identify what NS config for A8.1 does. That could be the key to fix viewfinder on other ports too.

I am aware of that but so far everything is working great. I will move it a bit if I face issues. PS. Actually, the case is not made by me. It was made by previous owner of this Pro1.

I am using a PURO 1-in-2 magnet flip case for Huawei P30 Pro with my Pro1. See the pictures below. https://imgur.com/a/a8A7iZT I am not using the separate hard case so the Pro1 is attached to leather flip case with double sided tape. Also, a small magnet is added under the leather where you normally place a credit card so flip case can be used with Fx Service. I think that the end result is pretty neat. Later on, I might try to create a magnet hard case that can by used with my flip case. However, I am not sure if the thickness is enough for separate hard case.

I have found several Gcam versions where viewfinder is not upside down in Night Sight mode but none of those provides same quality than Pocophone F1 port. However, there are Gcam versions (like PMGC_7.0.009_HDR_Version_V13) where you are able to flip viewfinder from advanced settings menu. It will fix the issue on Pro1 even so the fix is meant for front camera. I am wondering If it possible to add that feature to Pocophone F1 port? Is there any app developer who would be able to help? @tdm @Slion ? Also, I tried to tune parametres with config-file on F1MinimalMod2.0_Moded_by_jairo_r

There are two mics on Pro1. First is next to the charging port and second is next to the camera module. Make sure that you have not covered mics during filming. If you are using a case check that the mic next to the camera is not covered.

That was not the case on my unit. Still the same green tint on low brightness with new update. If F(x)tec changed something they would most probably mention it on changelogs.

Same thing happens with Chrome. Only difference is that in Chrome the incognito notification will close incognito tabs and remove the notification. In Fulguris the notification opens incognito tabs so the notification never goes off. However, I don't know why the notification doesn't go away when you remove browser in recent apps. Probably it is related to Android's memory management. In general you should not "kill" apps by swipping them from recent apps menu. Closing Apps to Save Your Battery Only Makes Things Worse