Leaderboard

Started print this morning, 10h to go still:p

A quick update. Received my warranty replacement phone today. It has a different serial number. The stability issues I had before are now gone, so it seems likely that the particular unit I had before was faulty somehow.

THE OTA have been Temporarily suspended, as it had a bug breaking the "SafetyNet", fix should be on it's way quickly.

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.

So now key-chording/rollover works in Sailfish, Lineage, and finally stock with yesterdays OTA! I want my game gripper 😉

Currently playing the waiting game. :'( Stupid virus...... Hoping the keyboard will work well for SNES controller emulation when the waiting game is finished.

Yah it could probably work, but some testing needed. I think that it might be possible to get it to stay almost without lip by printing it slightly to small. But I need to find a good mixture of resin to get a good amount of stretch (using Monocure flex 100 and regular transparent resin). I will try making a part for the top as well!

today is the day, latest ota fixes all these 🙂

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

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".

Thanks to @Raksura for posting this in another thread, but let me put it here too, for more to see the progress.

Maybe you were matched with other people on smartphone but the keyboard gave you an edge over them?

Just wanted to point out, I think there IS a bootloader lock status indicator at boot, but it's subtle. When I boot, at the bottom of the lockscreen (after all the logos) is a small (really small) padlock. On mine, which has been unlocked since I received it as it came that way, it shows the lock open (A tiny space between the left side of the bar and the lock). I can't say I know having never been locked, but I would assume that if you are locked, the loop is closed.

Basically a sound output a few centimeters away of the main microphone doesn't seem to be a really good decision. Maybe if it has a really good filtering algorithm then it may distinguish its own noise and voice signal but it may not be an easy task... So I would no wonder if handsfree mode has some problems this way. I have checked my colleague's phone which also has two speakers but the opposite one is working in handsfree mode anyway.

This is the holster case I use, works well: https://www.amazon.com/Skycase-Holster-Handmade-Leather-Cellphone/dp/B081CMMNDV

Shame I already installed it! 😄

Hmm, I don't see any OTA. And trying to update from SDCard fails.

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:

The boot loader is qcom code. The OEM modifies it for the device: display initialization, button access, things like that. I don't know offhand if the unlocked warning is defaulted to on or not, but they certainly could have disabled it in any case. All devices have Secure Boot off and always have. This is not really related to the boot loader lock.

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.

Chen found this reply that might explain things....

Yeah, I think I finally can see the end to end steps and thus will think about rooting this week-end. Since I don't see the boot.img file in the zip (I updated manually), I'd ppreciate the file. Or tell me how to extract it. BTW, are we sure the boot.img changed from January? And, @EskeRahn really confused me, moving all this in the middle of my composing this post... 😉

It worked. OTA info screen: I then went into Magisk Manager and uninstalled it, telling it to restore the previous image. Next, started the download for the OTA: One interesting thing was that it automatically started installing after the download. I thought in the past that it gave you an option tap something to start the install after the download was done, but I could be mistaken about that. This means it is important to uninstall Magisk before even starting the download. It also showed 100% complete immediately after the download was com

I can now change the incall volume 🙂

Thanks for the warnings. Too bad so many programs try to 'be smart' and 'know better' to make sure the user gets a bad experience... 😖

I did some more adjustments now based on the test print, should be quite OK. If anyone wish to test and print it: https://aelv.se/hka/ul/FxTecPro1_case.stl And the files for modifying it are here: https://aelv.se/hka/ul/modelFiles.7z I can post it to shapeway when I have tested printing it and is satisfied with it, but seemed expensive, $22 for the cheapest option and about $50 for TPU.

Let's see, there are a number of games I play on the Pro1 Where Is the Setting Game How Do I Make This Stop Search Game What Does This Do Challenge The Volume Game Puzzle The Notification Light Game Holding The Pro Russian Roulette Can You Hear Me Challenge I find new games to play EVERY time I use it. It's such fun :D

Fx Service is an Android application notably enabling Pro1 smart case support. It also provides various solutions to common Pro1 problems or simply new features including: Smart case support: configurable lock and wake functionalities. Screen filter overlay to lower display brightness beyond system settings. Configurable vibration upon keyboard key action. Alternative auto-rotate solution to bypass system auto-rotate which tends to get stuck. Filter out unwanted system key input. Feel free to post here to discuss bugs and feature requests.

Thanks for keeping us all informed and glad it's sorted! 🙂

Ah, okay. Must be it... I'm set to swipe. I thought it might be bootloader because I think one of my Nexus phones used a lock icon for the bootloader, but it showed before the lock screen.

It seems like there are different ways for them to do it: 1) Provide another incremental update that will fix 20200304, and re-release the 20200304 and new update. This would mean people who did not take 20200304 would need to do 2 OTA updates. 2) Provide a full update, not an incremental. Everyone can apply this regardless of what they currently have on their phones. 3) They provide a new update that is only for people who have 20200106. Those people would get the keyboard fixes and not have SafetyNet issues. The people who have 20200304 would need to wait for the next O

Well sort of. Root ALSO breaks SafetyNet, but it requires more than just not rooted to pass. (yes yes, I am aware that rooted there are tricks to get SafetyNet happy)

Actually, I am wondering about this. I got the update OTA, and it broke Google Pay. When the new one is pushed, will it be identified as new in the Software Update system? Or will I need to download it manually as a ZIP and apply it myself?

I think this might just be a matter of measuring MB as a power of 10 versus a power of 2.

There is no such notification on boot when unlocked, but you can see it in the bootloader (the thing that comes if you hold voldn+power / adb reboot bootloader).

My mother used to say "It'll turn up" in just these situations. Probably not the best business strategy however LOL

Yes we can get two results, both bad:

It has worked before, answering red, and later green after it was fixed. But now:

Anyone who's unrooted, can you check your safetynet status after taking the OTA? I'm rooted, but I failed the check when I passed before.

I just compared the 20200106 boot image file to the 20200304 file with a hex compare tool and they are different.

I tried to make it in a large font and different colour.... https://community.fxtec.com/topic/2849-new-ota-update-stamped-2020-03-04/?do=findComment&comment=46346

I didn't see that you had a pointer over there. I still don't see one by you. :-)

Sorry, moved it all over here, as it is not related to the specific OTA, but more general usable 🙂

I added this to my post above, but I'm duplicating it here in case anyone missed it because it is important. If you don't follow the steps properly the first time you root, you won't be able to do what I documented above (which has also been documented elsewhere on the forums by other people, but for people reading this topic, and not seeing the others, it is good to have it here as well). ... NOTE: You have to originally achieve root in the proper way for this method to work. And that proper way is for Magisk Manager to be given a non-patched boot image file that is identical to

I'll buy you a beer if you do so! Or I will buy one anyway, but I'll make it a sixpack at least.

Remember that they are small, so they easily will be pushed aside when a larger customer wants stuff. Hard to fight the giants. Even though they may already be using multiple sources for standard parts, their volumes are so small that doing so for specialised parts, would add heavy surcharges.

THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

@Khalid I understand and agree with many of your feelings here. It's frustrating, especially after such a long wait, to have so many things get in the way of usability. I hope it gets better for you. But, if not, FWIW you can probably sell with ease (maybe for profit, see thread on used prices I've been watching), these clackers are in high demand right now. I do still struggle with my own Pro1 (like you), but it's actually really common for quality control to be on par with what you see here. In fact, I'm impressed FxTec has created something this stable and reliable. Here are some issue

Pro1 is under an approval (final stage) from Google to activate security features. Once it's finished we will release an OTA to activate contactless payment. Everything has been submitted and we are awaiting.