Leaderboard

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

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

I do not know anything more than was in the September 2021 update: Note the generic "your devices". As I own only an original Pro1, I would be quite happy if it was still given some (official) love, too ... 😉 On a more serious note, they probably hired him for his general skills in embedded ARM Linux systems, and will want to flexibly adapt his focus according to company needs (which makes perfect sense to me).

Here are the notes I saved for myself, in case it helps anyone: How To Flash Ubuntu Touch OS from windows 10: 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 Google USB driver from https://developer.android.com/studio/run/oem-usb#InstallingDriver Extract driver, edit android_winusb.inf and add the following lines, save, close. ;F(x)tec Pro1 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D0

No one will have experience with those, as the Pro1-X was released only a few days ago. For the Pro1, some success in mainlining has been made, resulting in (as far as I know) a PostmarketOS proof-of-principle. However, as the Pro1-X ended up being a totally different machine, nothing of that is likely portable easily. On the bright side, F(x)tec hired a software engineer specifically to help in mainlining the Pro1-X (and also the original Pro1, I guess). The Pro1 and Pro1-X are not even using the same kernel, so even in the (standardized) x86-world, this would not be possibl

Thanks for the guide and links. 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. I did it this way on Ubuntu: First Backup install https://github.com/bkerler/edl # Ubuntu sudo apt install adb fastboot python3-dev python3-pip liblzma-dev git sudo apt purge modemmanager git clone https://github.com/bkerler/edl.git cd edl git submodule update --init --recursive sudo cp Drivers/51-edl.rules /etc/udev/rules.

I also got similar results between Pro1, Pro1x and Titan Pocket for WiFi (posted in the first page), which doesn't mean it's great, but certainly is usable. I always felt that my Pro1 was not the best at network reception, but I still wouldn't have used anything else since I got it in late 2019. Mobile network reception is more critical to me than WiFi, and that I didn't compare between Pro1, Pro1x and Titan Pocket because I was too lazy to swap my SIM card, but again the Pro1 was not stellar there, but not what I would call horrible either.

@tschakram thank you, your instructions got me further than any other. I am stuck on: $ fastboot format:ext4 userdata Warning: userdata type is f2fs, but ext4 was requested for formatting. mke2fs 1.45.5 (07-Jan-2020) Warning: RAID stripe-width 1 not an even multiple of stride 2. /tmp/TemporaryFile-sPSRJM: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata and $ fastboot reboot fastboot fastboot: usage: unknown reboot target fastboot then

Thanks @toast, yes, it was in the official update. Also, they showed images of the first cameras they received, and they showed '586' in the print on the ribbon cable:

Okay, I've tried this out, and no, the process outlined by @Casey does not restore key attestation functionality. I don't need key attestation working on my device anyway, but hopefully there's a solution out there that will provide both working sensors and working key attestation.

I'm trying this now just OTA. I'll report back my result (but you know this takes a while, lol). You mentioned something about a 3 part flash. I was getting that from AICP-S. AICP-R and Lineage has always given me a 2 part flash when flashing from recovery. Don't know if there's any relationship.

The rear camera is a Sony IMX586. The sensor really has 48 MP, but the full resolution is only used internally, like for AF. This is standard for Quad Bayer layout sensors (the 20 MP, physically 80 MP sensor of the high-end OM System / Olympus OM-1 interchangeable lens camera, for example, has the same design and the same limitation). A full-resolution readout would not make much sense, as the colour matrix only has 12 million colour squares, each one covering an array of 2x2 pixels. (There are few phones with 12/48 MP sensors which make an exception, though, and try to make 48 MP results avai

https://play.google.com/store/apps/details?id=nextapp.fx&hl=en&gl=US https://play.google.com/store/apps/details?id=com.expressvpn.vpn&hl=en&gl=US My preferred file manager app and VPN provider. The FX name is just a coincidence 🙂

Thanks for the step-by-step guide. You might want to add the step on saving the "persist" image before flashing, as not doing so should prevent turning back to stock android (and most likely LineageOS also) without lost functionality. In Windows 11 it has been allowed (again) to install an unsigned driver, without test-mode, some months back. (About a year ago we could not)

I assume you have gone to Settings, apps, Advanced, default apps and specifically set your "Home app" to Nova? I don't usually have to do that with Android 11 and before, but I did have to do it with Lineage 19, so I wonder if Google has changed something up.

Never heard of that -- but then I've also never used stock Android 9. I tend to view this anecdote as proof of how much the Pro1-X (too) will leave its initial (software) problems behind once we see LineageOS up and soaring ... Firmware bugs are a different story, of course.

Ah yes, how things could have been different had they not been swindled...

Please do not put too much weight on my simple tests. It MIGHT be that not all bands work equally well, so if some depends on a frequency where it does not work well, their results would clearly be worse. We would need some more scientific approach to this with some suitable box that can act as an access point, and 'browse' through all supported channels of 2.4 and 5GHz, and then we should measure the time a band change takes, as well as the speed in each band. And all this at different distances... And with the device in different angles. Without a systematic approach we could easily be

I would advise you to relax. I guess, much of your first impression is determined from what other phone you come from. I asked, and @EskeRahn reported a direct comparison of the Pro1-X and Pro1 above, which I interpret as "on-par-within-the-measurement-uncertainty". @Rob. S. reported similarly in a different thread. I own only a Pro1, and was never super-happy with its WiFi or LTE connectivity, but it has still been perfectly usable over the last two years. So, in your place, I wouldn't worry too much about that point right now.

Adam helped me to get Waydroid to work! And shadow.tech works in Waydroid (no sound nor keyboard, though, so it's somewhat limited): See how to get Waydroid to run on SFOS and what doesn't work: https://github.com/sailfish-on-fxtecpro1/droid-config-halium-qx1050/issues/1#issuecomment-1215734546 The current list of issues after just one hour of use: Camera doesn't work (who cares? But it shows that some hardware is not visible to Waydroid) Vibration does not work Landscape rotation is borked (it just stretches ev

To make it clear, the drivers and whatnot of PRO¹-x are still not in mainline linux. That will happen, at the very least (if lucky!), next year. Whatever OS uses mainline linux and its drivers to run won't work until then.

I can only say: Patience. I'm in the first dozen from IGG in October 2020, and still no shipping info from FedEx.... Expansys/FedEx seem to handle the parcels from FxTec within each batch by country (in some unknown order). So depending on your country, it could be soon or weeks for a device in batch 2.

I ordered this one. I don't know what it will look like and whether it will fit on a rounded side or if it is just a flat sheet. Not yet arrived. I plan to cover the bottom of the device with heat shrink film to prevent scratches and sand particles. I cut out the necessary parts and then put the device in a rubber or silicone case. (maybe P20 Pro)

Do you remember: "Yeah, XDA made a phone and it’s only available for 6 weeks! ... and it's the world's first phone to run LineageOS out of the box!" https://www.xda-developers.com/pro1-x/

I took the liberty to edit the original post, as a new guide can be found here

meant the boot image, and sorry just three lines of output

My E7 is currently 12 years old and its hinge mechanism, which I use a lot, works flawlessly. There are zero signs of anything wearing out - nothing is loose or rattly.

Thanks for information and for summarizing this so nicely. I guess, most people are not aware that the typical camera sensor uses only a fraction of its pixels for each of the red, green, and blue colour channels, respectively. I also agree that, at the given size of phone sensors and lenses, and given the high density of a 48-megapixel sensor, just grouping pixels 4-by-4 is likely the most reasonable thing to do, except (maybe) for the most high-end phone cameras. That said, it is also true that, in the days before CCD/CMOS sensors reached today's insanely high pixel densities, demosaici

Sorry - not meaning to hijack, but has anyone had luck getting 4K video and does anyone know what the rear camera actually is? There's a physical label that says 48MP, but that sounds fake to me and the camera app goes to 12MP maximum.

That is not a preinstalled app. Installed stock Android is as vanilla as it can be 😄

There is a Matrix bridge indeed but I don't remember the address, maybe some others here can comment (@mosenuses it for instance). [Edit]: https://matrix.to/#/#fxtec:revreso.de

Wasn't there some tweet about Fxtec hiring/sponsoring a dev to work on porting LineageOS previously?

This is a known issue that was fixed in a later update, that you should get by OTA soon, or through the testing program when they open it to all bravehearted users.

It's Gorilla glass, and I doubt there's any phone on the market where it's easier to swap screens, provided you get the official replacement unit (which practically is the whole top part of the phone, replacement involves just five screws and a ribbon cable). As a cheaper option there also is the actual display available from sources like Aliexpress which is also not too difficult to replace, but involves gluing which carries the danger of a less than perfect result. Right, but there are other issues which may arise with protectors, and physically breaking isn't what you need to protec

We're experiencing this too! For what it's worth, Firefox is not affected. Does anyone know why this happens? We don't particularly want to disable the fingerprint sensor.

For what it's worth, we are grabbing files off a developer build server, whose purpose is to compile untested bleeding-edge code so the developers can test on actual hardware. Trying to install and run binaries from it is way out of scope; the intended use is to assist with the process of breaking the build in an orderly fashion.

I spent some time today playing with this (with the ultimate goal of getting Sailfish OS running), and for the longest time was unable to get either Ubuntu Touch or Sailfish OS to boot. Eventually I decided to try out older builds of Ubuntu Touch and discovered that no boot.img newer than the one found in #2807435728 seems to work. After reverting to the boot.img found in that build, both Ubuntu Touch and Sailfish OS boot fine.

Definitively no. I am one of the very first perks and received an email from FedEx today (and also from IGG since then) that my phone is being sent. My last name starts with V anyway. 🙂

Seeing the igg orders start to be sipped has caused that irritated feeling, that I thought I had completely quashed, start to reer its ugly head again. Oh well, I guess I'll go poke things with a stick to distract myself. Horray for progress being made!

I will tell you of my solution, which may be neither possible nor acceptable for you. I am retired and spend a lot of time at home. So I have two phones, my Pro 1 and a Motorola Power (slab) The Moto is my phone phone and car phone (Android Auto) and my Pro1 is my PDA (Though I keep a T-Mobile SIM active in it). My Moto is on Verizon. It is expensive, buying two phones, but it allows me to have the best PDA out there for doing text based tasks while having a solid and reliable phone. I initially did this to solve a problem, but honestly I have come to love this deconvergence (I'm n o

I can confirm that on my device, running Ubuntu Touch and Sailfish has killed the sensors in Android. I didn't make my backup of persist until after booting both UT and SFOS unfortunately. @Casey has just posted the Windows-based instructions for reflashing the factory image. Is it possible that the official software can properly add the attestation keys into persist, and the python scripts we've all be using do not? Anyone want to try it out?