Leaderboard

It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys

Production does indeed seem to be starting...

NEW Version of guide here Below the original text: (above inserted by EskeRahn) If you're reading this, it seems like you miss the good old Android OS or you've accidentally fried your PrawnX already! Don't worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1.2): https://drive.google.com/drive/folders/1_sgQ64ef9Di9kJ63Y6WNqllGRgRFOjac?usp=sharing We are still compiling/drafting a complete user manual for flashing your Pro1X, but hope this helps you out for now.

While all our work is public, we don't necessarily post a neon sign saying, "Break ur phone here!" 😉 The Pro1-X work is moderately stable now and has been moved to the official LineageOS org on GitHub: https://github.com/LineageOS/android_device_fxtec_pro1x https://github.com/LineageOS/android_kernel_fxtec_sm6115 You are welcome to use these for your own builds, but please be prepared debug any problems yourself. There are a few outstanding fixes on our gerrit, esp. this topic: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver Also, please remember that although we work

Hi folks, I just started working on the mainline kernel a few days ago with ichernev and so far I've got USB and simplefb up and going, no button, storage or regulators yet.

Hi. We(me+Ichernev) are currently messing around mainline kernel on Snapdragon 662. We are going to submit some base stuff pretty soon depending how maintainers will go on merging simple compatibles. However we are working on other devices, Redmi 9T(me) and Oneplus N100(Ichernev). While progress is going to be slow we will get there at some point, one of harder things will be Adreno 610 support due to no GMU but i hope this will be done by SoMainline for 665 SoC so we just can pick it.

Hey F(x)tec community! We thought it would be a great idea to invite Pro1-X owners to come join our beta testing scheme! We know our stock Operating System still needs optimising and requires further development, we believe with the help from our community members, it could speed up the progress of finding and fixing bugs/issues to provide you with a better user experience. Therefore, we created a Telegram group dedicated for users who are interested in testing new Android builds. Anyone with a Pro1-X will be eligible to participate in this programme. However, before you go ahea

LineageOS is a group project, and support for the Pro1-X wouldn't have been possible without Georg Veichtlbauer [email protected]'s efforts. And of course we built upon @tdm's work on the Pro1 as well.

Okay, I found the solution. This "member title" is actually considered to be sort of an exclusive perk for active users who have contributed a lot in the forums. In my Admin control panel, I was able to find the current threshold to "unlock" members title - 500 content posts. Considering @Hook's suggestion is very constructive, I've lowered the threshold to 0 contents required (unless there's any thoughts on this?), meaning all new/old users can set their own titles now. Enjoy! 😄

Please stop. You made your points, there are people here who invested in this project knowing that, you are doing a disservice to the intent of the project and to those that have supported this from the start, many of us have the Pro1 or supported it since then and see this is a project worth backing. You approach amounts to not achieving anything if whomever you are advocating for put money in through IGG then they need to read what that actually means. I have had my pro1 serviced and supported and I myself support the group even though the Pro1 is not my daily driver. But many of u

Dear Community, I have just received my Pro¹X yesterday (photoed near a Pro¹): Its build quality is absolutely perfect, it has no rattling effect, buttons are even and not too loose (similar to Pro¹). Its colour is good - I like original black colour but this deep blue also looks good. I see there is some room for improvement at software side (and I have not used it extensively), but so far I don't see its radios are significantly worse than Pro¹'s radios (however, there are some improvements yet to be done). I feel keyboard's backlight is different - either Pr

Following @esialb's thread on Ubuntu Touch, here's one showing that SailfishOS works too: ——— Instructions: - First and foremost, backup your "persist" partition. Better safe than sorry. Instructions are in other guides, Please, do not skip that step, there is no other way back to the vanilla persist partition. - Download and extract the latest artifacts.zip from the SailfishOS port repository: https://gitlab.com/sailfishos-porters-ci/halium-qx1050-ci/-/jobs - Pick your clacky Pro1x, power it down, hold down [Volume -] and [Power] until it boots

Since I ordered my first Fxtec phone, a Pro1, in Sept 2019 (which also seems to become the one to arrive last...) I've read everything Fxtec communicated (plus every comment in this forum), including a couple of personal mails from support, and while I've been having my doubts and a lot of bad feelings about the goings-on myself more than once, too, from all we know nothing of what they have said over the time can safely be called a lie. Wrong, overly optimistic estimates by the bucketful, yes, but really nothing where we can be absolutely sure they would have known beforehand that their annou

I saw today that both Pros are supported in the current release of Droidian https://github.com/droidian-images/droidian/releases/tag/droidian%2Fbookworm%2F24 AFAIK we should use the fastboot images to flash. Backup your persist partition Download the realease Unpack zip Use flash_all.sh --- First and foremost, backup your "persist" partition. Better safe than sorry. Instructions are in other guides, Please, do not skip that step, there is no other way back to the vanilla persist partition. We are seeing more and more users losing their attestat

We are aware of Expansys selling Pro1-X's on their website and we understand there's a lot of concerns and theories about the nature of these listings. We'll post a follow-up announcement to address this. But rest assured, all IGG and website orders are not compromised!

This is the complete guide on how to flash the stock ROM on your Pro1-X. We will be using the Qualcomm Image Flash Loader (QFIL) inside the Qualcomm Product Support Tools (QPST) pack to flash our XML-based stock firmware. Whether you want to restore your Pro1-X back to factory settings or fix a ‘bricked’ device, flashing the stock ROM back to your Pro1-X using Emergency Download Mode (EDL) with QPST/QFIL is the safest method. However, this process ONLY works on Windows PC. If you do not own a Windows Operating System computer, you may consider setting up a Virtual Machine (VM) on you

Regarding the bugs, I'm in the process of joining ubports as a contributor to scratch my own itches and share the fixes.

Hook wanders in, excited that he just got an email with a tracking number for his Pro1x, notices that he seems to be interrupting some weighty discussion and scampers back out of the thread.

Don't know why I didn't notice this before. I always liked signatures in forums so that folks could see, whether asking or answering, what devices you had. However, we do have a "member title" field in our profile. So I'm using it to let everyone know I only have a Pro 1 so that people can regard any answers I have about a Pro1X with suspicion. 😄 It's still a good idea to specify what model you are talking about in thread titles and posts as things can get confusing with the two different yet similar phones, especially if people have not listed under their names, but it is still usefu

FYI: https://forum.xda-developers.com/t/lineageos-20-for-pro1-x.4543997/

Finally, this issue has been fixed by restoring backup files. I need pass '--memory=ufs' for each command $ ./edl w persist ./persist_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst2 ./modemst2_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst1 ./modemst1_backup.img --memory=ufs $ sleep 3 $ ./edl w fsc ./fsc_backup.img --memory=ufs $ sleep 3 $ ./edl w fsg ./fsg_backup.img --memory=ufs $ sleep 3 Here is link for my backup files if you need them: https://github.com/steward-fu/pro1x/releases/tag/v1.0 Thanks

There's finally a build of LOS that works and I got myself a test build with it. It's still too early and barely works enough for the hardware but it's a great light at the end of the tunnel for LineageOS on Pro¹-X

This is the complete guide on how to root your Pro1-X with Magisk. Rooting you Pro1-X can allow you to 'unlock' superuser permissions along with flashing custom ROMs. This process will require you to have OEM unlocked before proceeding as we will need to use Bootloader mode to flash a patched boot.img from Magisk. It should take around 20-30 minutes for users who are new with rooting their phones. Instructions for unrooting your Pro1-X are also included in this user manual. Click the attachment below to download the user manual for rooting your Pro1-X with Magisk. How to Root

I found an easy way to fix this from any ROM, without having to wipe userdata. tl;dr: Edit: Make backups. It shouldn't be necessary, but you never know! Flash the 2020-08-25 stock ROM, but skip flashing/wiping userdata. More info here. Let it attempt to boot (for a couple of minutes). It (very probably) won't ever get through it, because the userdata partition wasn't wiped. This doesn't matter, though. It does flash the touchscreen firmware, which fixes the unresponsive screen edges. Edit: I did not time it, but I think I let it sit at the boot logo for 2-3

I had this problem. I found I was able to set everything up by doing it with no SD Card and no SIM Card installed. I set it up over wifi, then I installed my SIM Card and SD Card. Everything seemed to work fine after that. I've been using it fine for a few days, now.

Thanks for the work, people. Life got in the way here a bit. I did a bit of digging based on the rar shared in this thread by Kaali: The APK does seem to contain code to write config data to the chip (com.goodix.tools.ICParametersConfig.class). I attached a version of the *.cfg converted to decimal, separated by newlines. There are 239 bytes in total, which do not seem to map cleanly to the config information in the datasheet. I also attached a version of the flashing instructions with Google translations in them. I used the APK with my Pro1 in USB debugging mode, and after havi

There are so little instructions on the ih8sn in the internet so i thought i could share how to get it to work on pro1 if anyone is interested in that. Fresh install is not needed and you don't need magisk or any SU package to pass safetynet after this. Not sure if this works for other OSes than Lineage but someone can have a shot and tell if it does. Requirements: -ADB on your computer -Debugging and rooted debugging enabled on your phone from developer options. -Latest ih8sn aarch64 release downloadable here, extract the zip, you don't need the .conf file as it is for different phon

This just came in for those who ordered on the web:

Next week should be the start of production according to the newest IGG update 🙂

I was able to install and use Ubuntu Touch on my Pro1-X after locating the fastboot images on their development server: Jobs · UBports / Porting / Community Ports / android11 / Fxtec Pro1-X / fxtec-pro1x · GitLab. Unzip artifacts.zip for the most recent build, which will have out/boot.img and out/userdata.img. To install: unzip artifacts.zip cd out fastboot flash boot_a boot.img fastboot set_active a fastboot flash userdata userdata.img fastboot set_active a fastboot continue So far it's pretty decent. My intended use for the Pro1-X is pocket computer, not primary phone, and I don't t

To help you create your own custom keymaps, I updated @Slion's excellent keyboard map for the Pro1-X QWERTY layout and added the key numbers for each of the six modifier keys ('F logo' Fx, Shift, Ctrl, Alt, and right and left "yellow arrow" Fn). Remember that the two Shift keys are actually the same, as are the two Ctrl keys. Unfortunately, you can't map right and left Shift to different key codes, or right and left Ctrl either 🙁

@steff and @EskeRahn: While I agree to all you write, maybe there is one thing that can be said in F(x)tec's defence: From their perspective, everything must have changed at the moment they were forced to "upgrade" all pending orders for the original Pro1 to Pro1X's: As at least some of those were ordered (and paid!) way before the start of the IGG campaign, they essentially had the choice to betray either these original Pro1 customers (by postponing them until after end of the IGG campaign) or the Pro1X campaign-backers (by continuing to serve regular website customers alike, breaking IGG rul

It arrived and looks awesome 😎

Definitely F(x)tec is NOT scamming us. They are just struggling with this project and things have not gone as they planned (SoC change etc). Sure, F(x)tec has done mistakes during the journey but I think that they are trying very hard with limited resources. I received my Pro1 after long wait and during this week I am supposed to receive Pro1-X. Let's see how it works compared to Pro1.

Hi all, hope everyone had a great holiday! Just to update everyone regarding the next IGG announcement, we plan to post it next Monday - stay tuned!

It seems that LineageOS 19.1 will be available soon for Pro1: https://www.lineageoslog.com/19.1/pro1 More information: https://lineageos.org/Changelog-26/ (F(x)tec Pro1 mentioned) https://download.lineageos.org/pro1 I hope it'll fix the charging issue I've had with the LOS 18.1 🙂

Your points are well-taken, even in your first post. I don't know what has been happening. I suspect they don't have a lot of money to play with, which might be why they couldn't hang onto that in-house person. I guess I just appreciate their doggedness to get us hardware in our hands that then may be able to become what we want. They crowdfunded a phone they had already designed and built with only more memory and Lineage and UT ready to go. Suddenly, they lost the SOC they had paid for and found themselves having to design a new phone in a pandemic remotely in China. I don't know m

@Heruvim I got mine from here: https://www.expansys.com/ You might want to consider import taxes and warranty, there is some discussion here, search the forum on 'Expansys' for more info. Shipped to NZ in about a fortnight. No complaints at all from me, seems very solidly built and runs very well, new daily driver from day one.

They have published another update here:

I 100% agree that running inside a chroot or LXC container is 98% of what people would need. But one thing I would gain from using a mainline kernel, is kernel updates almost in perpetuity, rather than running a container on a fork of a 4 year old kernel. Additionally, it provides a path forward in de-blobbing many of the drivers and features inside our phones, which is a security improvement. I understand that right now this is mostly philosophical and problems for future sspiff, but I've been into handheld Linux devices for long enough to have felt the pain of not being able to upgrade

Nice! I just received my Pro1X (Black/6GB/128GB) yesterday, just unboxed it today and still haven't played with it much yet. I do have the original Pro1 and used the hell out of the thing. I installed SFOS, an Arch Linux ARM container and some apps, it's one of my favorite Linux PDA.

Sorry, we'll just have to agree to disagree. Where you see "intentional false information," I see overly-optimistic estimations, which, when they don't pan out, they get beat over the head with it. No wonder they kept communication less frequent until they got close to a real production phase. And of course hardware "quirks" would affect software, if the software has to use that hardware that is being fixed. My guess would be a that pre-production models went out in June. I don't know this, but that seems to be about when hardware tweaking was mostly done and the big concern was g

Original Equipment Manufacturer (OEM) unlock is needed when you want to unlock bootloader on your Pro1-X. Although having access to bootloader can allow you to root your device and flash custom ROMs, the downside is that you will no longer be able to use Google Mobile Services (GMS) such as Google Pay on your device. We firmly believe that by allowing users with more access and control over their devices can help them achieve more, which is why we shipped our Pro1-X’s with “OEM unlocked” by default to offer convenience when flashing other OS’s such as LineageOS and UbuntuTouch. But

If you still haven't received one when all of batch #1 has shipped, you will have a reason to complain, and rest assured I will complain in case the phone I ordered in Sept 2019 won't come in batch #1, too. If you cannot contain yourself for the few more days that will take, all the more so after you have been waiting for more than two years now, your fuse it too short. And then tell us which other tiny, but "thriving" and "efficient" company has been denied an already promised supply of SoCs, making scrap out of their mainboard, in place of which they then had to create a completely new

They have just shared an additional update containing shepping info here:

I've been lurking in this thread since it was first created and am one of the Pro 1 purchasers from the website ordered 01/27/2021. It's been a long road, getting from there to here! I signed up so I could thank everyone who has been posting the IGG updates here and bringing some transparency to this whole process. I originally ordered the Pro 1 because Verizon was barking that my old slider would not be supported and I would lose all service. Well, functionality has become more degraded and quirky, but I've been able to make it work well enough. I keep looking over my shoulder f

I think the other thing to look at is their perseverance. Given IGG offers no guarantee of delivery, most, given the obstacles they hit, might have thrown up their hands and walked away. This small group of folks is making sure we get our phones come Hell or high water. I can't believe they are going to have ended up with massive profits. They are doing this for the love of keyboard phones and they will deliver. Thank you Chen and the rest!

They have posted another update here:

This is an incomplete guide on how to flash the stock ROM (or in this example beta ROM with userdebug) on your Pro1-X. I used the windows instructions from Fxtec, and you should certainly read them and use them to assist in working through the reflash. I searched for an alternative to the recommended QFIL, and found a linux tool called QDL (Qualcomm Download). This tool allows you to flash Fxtec's XML-based stock firmware to your Pro1-X using Emergency Download Mode (EDL). I used this successfully to move from Sailfish OS to Android 2.1.6_userdebug. This may not be suitable for every

All the news we have are about f(x)tec (slowly) working through existing (pre-)orders that have in part been pending for several years. This should not prevent you from ordering a Pro1-X. As far as we know, f(x)tec finally always delivers. However, you should not count on getting you phone very soon. Also note that the Pro1 and Pro1-X do not "support" Linux in the way the PinePhone does. While some progress in mainlining the original Pro1 (the SD-835 variant) has been made, all existing GNU/Linux OSes for the Pro1/Pro1X that can at least remotely qualify as daily-drivers (SailfishOS, Ubun