FlyingAntero

You can use KFMark without root also but then you need to use ADB via computer to activate monitoring. With root you can just use Magisk module to enable monitoring. Without root: - Download KFMARK-Android-1.5.apk and KFMARK-Windows-Activation-Tool-1.5.zip from here: https://github.com/aifou-kfmark/KFMARK/releases and setup ADB connection before monitoring With root: - Download APK-file above and KFMark Enabler via Magisk KFMark is in Chinese and it is not fully open source so I don't know how realible it is. I tried to use GameBench first but I was not able to get it

EDIT: The cause of the problem has been found: Original post: monitored couple game sessions with KFMark and noticed that Pro1 has indeed some issues with gaming performance. The phone cannot keep up steady FPS during game play because CPU freqs goes up and down all the time. To me it looks like issue with kernel settings rather than throttling. Here are few gameplays compared to the Redmi Note 4 which has much weaker CPU. Both have FullHD(+) screen so results can be compared. Light game: Subway Surfers F(x)tec Pro1: average 52FPS (limit 60FPS) Redmi Note 4: av

Some of my friends are not so familiar with flashing via fastboot mode so they just have to wait. I was hoping that the fix could arrive within few weeks. I believe that there isn't much that F(x)tec can do if the sertification is pending on Google's end.

What is the current situation with the update that is supposed to fix SafetyNet? Is the certification process still going on?

Here is The video where Martin talks about The mechanism.

Astro Slide 5G can run full Linux like other Planet Computer devices. It has dual boot functionality. However, I would still choose "Pro2" because of the form factor. But If "Pro²" will never happen then I can consider Astro Slide 5G.

I am not sure If I am going to replace my screen right away. Currently, everything is working normally and the crack is only a visual issue (for now). I can live with it. However, since the screen is damaged it can break to non-functional more easily anytime. So I need a spare part for backup. I will take pictures of the components when I am going to change the screen. I just don't know when that will happen.

Oh dear, I just broke the screen of my Pro¹. I was sitting on the floor and the phone slipped from my pocket. It was only 10 cm drop! Everything still works but there is one crack across the glass. I just ordered replacement screen but I will also need those stickers. @Serolfic can you order some stickers for me?

Yes it is. However, fixed version of that was started again for those who did not update the OTA earlier.

Is there an older build available that I could flash to my phone and then update to latest OTA? I don't mean the factory image (2019). Just a build before this SafetyNet issue.

I got my 4th reboot yesterday. I have had my phone for one and half month now. It is a rare issue for me and it is only happening when I am travelling. I can't reproduce it near my home. I am pretty sure that it is the same issue which was reported on Sony devices. Any plans to implement the fix soon? Is this bug also in Lineage OS rom?

This issue is fixed in the latest OTA-update. There is also a work around available: - https://f-droid.org/en/packages/com.punksta.apps.volumecontrol/ Please, use the search function next time since this is third thread to same issue. https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y/htmlview#gid=0

New review from Pocket-lint (updated 3 March 2020) https://www.pocket-lint.com/phones/reviews/147291-fxtec-pro1-review-details

Maybe you should try Lineage OS since community has done great progress with the software. Audio issues are fixed in the latest test10 build and official Lineage OS build should be just around the corner. F(x)tec can also use the fixes provided by community (like keyboard driver) in official firmware. https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/

I just tried PUBG first Time and won. There must be some magic on Pro1.

There is a screenshot of the update window which shows the size of the OTA update. I added the picture to my previous message. If you can't see it anymore after clearing cache and reboot then maybe F(x)tec took it off?

EDIT2: It looks like that I mixed decimal and binary, see @david post. I checked from Twitter that manually downloaded OTA update has different size than normal OTA update. The OTA zip file is 73,14 MB but if you downloaded it normally it is 69,8 MB. Also, manually downloaded OTA zip file is named as "update-20200304204235-20200106110451.zip" compared to the "QX1000_EEA_20200304204235_20200304-2044" what is shown in system updates settings. So, is there some differences? https://twitter.com/JH174941/status/1235746109735063554 EDIT:

Since the keyboard driver is now fixed I can play whatever I want. Most likely I will stick with nostalgic platform games like Sonic and Mario.

Every other phone that I have owned informs during boot if bootloader is unlocked. I think that is a security thing in Android. I booted my phone and checked from FastBoot Mode that device state is "locked" and secure boot "no".

Yes, I got my device in January and I believe that it was locked when I received it. I haven't seen bootloader unlocked notification during boot.

I belong to this category since I downloaded the OTA zip to internal storage and updated manually. My device can't pass SafetyNet (CTS Profile Match: Failed) and I can't find Netflix from the Play Store. However, Play Store tells me that my device is Play Protect -certified.

I had same effect today and on previous updates as well. I don't know if it is a bug or not. Maybe rest of the install process is done during reboot? BTW, is there official changelog anywhere?

At least for me the update worked from internal storage.

Installed it right away, thanks! It seems that security patch level is also updated to 5th October 2019. EDIT: I can confirm that keyboard issue is indeed fixed. I can now play Sonic and Mario or whatever like a charm. Super awesome! It looks like that all keyboard driver issues are fixed now. I can now press "7", "U", "J", "N", ".", "UP" and "Enter" keys (QWERTZ) right after I wake up the screen. I don't need to press some other key first.

I am not sure if I got everything right but I thought we have two options (source) Make the keyboard act like the PC version, or Make the keyboard act like the print So we should make QWERTZ units act like the print in the first place so that we can look at the print to press the right key. Then, if we want customize it, we can remap it to Scandic with as little as possible changes. Gigadoc2: "Personally, I am strongly in favor of the second option, to make the keyboard act like the print suggests. Not only because I sometimes need to look at the print to press the r