Leaderboard

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

I was able to retrieve my package from the FedEx location today by showing my identification; all set.

I just confirmed that SD card works, and there is hope for Waydroid. I can start a container and a session, but didn't get the UI to start (the loading splash screen spins indefinitely). Adam Pigg managed yesterday to start the UI once: However it's still not really working: closing Waydroid or stopping the container crashes the whole system and a hard reboot is necessary, and Adam could only start the Android UI once, it didn't work at the next boot. It is encouraging though because it appears to be technically feasible, it should work eventually.

The Pro1-X has a single-stage camera shutter button. The website will be updated accordingly...

I spent some time today playing with this, 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.

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.

As well as LineageOS 19.1 and AICP-S (And the box can even be navigated in with arrow-keys and selected with Space or Ente plus Esc for cancel, if you want to avoid touch)

I ordered my "pro1 x" in November 2021 and it arrived yesterday 09/aug/2022.

In my opinion, adding something with even minimal texture to the back will offer far more protection than any screen protector (never use them), The best protection you can give you screen is making sure the phone doesn't slide or slip. 😉 It was easier with the Pro1 as most skins provide matte black and it looked perfect. Getting a skin that looks attractive on the blue back will be harder and may require something custom.

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

AICP-S 17.1 for Pro1 ADD: They have broken AICP-S so it does not work at all in the versions available, even after extracting the boot.img from the zip it self. See my post later in this thread 2023-04-05. They had a few versions that worked (almost) though, the last being aicp_pro1_s-17.1-WEEKLY-20220914.zip . --------------------------------------------------------------------------------------------------------- New version of AICP-S 17.1 based on Android 12 is available for download here: https://dwnld.aicp-rom.com/ aicp_pro1_s-17.1-WEEKLY-20220810.zip It is VERY

Okay, not too far rebuilding. Might try the experiment, just to see. Will have to be later tonight.

Great finding, thanks for posting about it. I edited the first post accordingly. Meanwhile, my old container works, it was just a permissions mixup due to my backup/restore procedure: [Edit] Damn, I wrote "Home seet home". What a fail. :<

For a limited time I put up the old recovery image here. lineage_18.1-20210913-recovery-pro1.img

For this experiment, I used the recovery for Lineage 18 from 20220425 as that is what I had stored away in my archive. Newer than yours, but to be honest, I don't think it makes a difference. It's possible the recovery for Lineage 19 has more of a problem with AICP-S because it is more sensitive to whatever is wrong, so it could be that something that was changed later in 18 could be a problem.

Thanks for the tests. Yes your guide is very close to what I do, also based on what TDM taught us. And indeed something sounds fishy. What is the recovery boot image you are using? And I also noticed tht the seventh boot is different. Already before the yellow AICP comes up, the 'flickering' of the FxTec logo is different. And it goes to a blue logo before it boots AICP (under some circumstances requesting a reset during the process),

I use the set of instructions I have always used, based on TDM, which I posted here and you have inked to in the ROM thread. They have always worked with me, including up through AICP-R. I double checked everything. I'm back on Lineage 19. Everything went smoothly and I'm rebuilding. There is something hinky about the files being supplied as AICP-S, I'm convinced. I'm staying away for now as I only have onePro1. 😄

@Hook Are you sure you are flashing to the A/B you are booting into? I use the below bat, to do stuff. Notice the a in these two lines: fastboot flash boot_a %1 fastboot --set-active=a (I assume they could just as well both have been b, and that the important thing is that they are equal) @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause echo * sending %~n1 fastboot flash boot_a %1 shift fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually

@EskeRahnOkay, I think there is a real problem here. I noticed this time, watching tiny text on th ePro1 as "AICP-S" installs that it announces itself at the end of the run as Android 11. But I also noticed it has 3 parts to the install where, I believe (but haven't verified) that LOS and previous versions of AICP have all had two parts. When I clean install "AICP-S" with MTG12 (both with and without Magisk), at the final bootloop I get the recovery screen that says it can't load Android system. If I try "AICP-S" with MTM-11, the gapps of course, won't install. Whatever this thin

Getting on it now. Will let you know what happens. 🙂 Do I need to go through the initial setup, or just see if it boots? Edit: Going ahead and doingh the most basic setup to take me to the desktop. That's it.

....And if it does not work, and you have more time to spare,please try the gapps-free AICP-R -> AICP-S , thanks 🙂

Yes, please do the full optimistic dirty flash, that is AICP-R + MTG 11 -> AICP-S + MTG 12, if that works we are 99% sure a gapps-free AICP-R -> AICP-S would also work.

(OpenCamera supports it too, but obciously this is Pro1 and not Pro1X) On the Pro1, so does 'Manual Camera'.

This was already posted as a separate thread. The email went to everyone.

I'm not Gapps free, but I'm wiping everything, so I can start with AICP-R if that will help the data collection. Should I flash R and then go to S or would it be better for me to Flash R and MTG 11 and then Go to R. I guess, my question is, are you asking me to do a dirty flash from R to S? I never do dirty flashes of a jump from one major version to the next, I always wipe clean. But if a dirty flash will answer a question, I'm willing to do it and start over if it goes sideways. Just clarify what you would like. 🙂

I'm going to give this a shot on my Pro1, wiping everything Lineage 19. Be great to have AICP working. I'll let you knopw how it comes out. 🙂

(OpenCamera supports it too, but obciously this is Pro1 and not Pro1X)

Basically it should start camera application on pressing camera button which is a default behaviour, I am receiving a popup on my Pro1 to select which camera app to start (that is a non-default behaviour). Half-pressing only works properly using stock camera app as others are not prepared for two-stage camera buttons. It may also happen Pro1-X does not have a modified camera app which handles this button properly, but otherwise I don't use stock application on my Pro1 as it was not really stable - for that, a 3rd-party camera app takes several times better photos, but Pro1-X has a diffe

Basically this is the behaviour what some digital cameras or even Nokia N900 did. So pressing it half-way, it prepares for taking a photo (setting focus for example), then it takes a photo when fully pressed. This functionality has worked on Pro1 using its native camera app but mostly not using 3rd-party apps. Basically I have not really used that button, mostly because there is no official silicone rubber for its back and there is no bump for this button on the one which I currently using and which was made for a different phone. However, it is not really easy to feel these two sta

I haven't ventured outside yet to experiment with the camera, but the camera button has me pretty confused. Unlike double-pressing the power button, which just opens the camera app, pressing the camera button launches the app and then snaps a picture automatically. I never owned the original Pro1, so I'm not sure what this 2-stage thing is.

I found them necessary, with the additional clarification that this needs to be done from the boot loader. fastboot from recovery doesn't seem to work properly when flashing a nonstandard boot.img.

Edit: Oops, duplicate post, because of fumbling with the phone...

The Pro1X in blue, would make it easier to keep track on which is Pro1 and Which is Pro1X... 😁 I currently have one retail Pro1 I bought, one final sample Pro1 and an early preproduction Pro1. And today got a 'verification sample' of the Pro1X (black), and will (hopefully soon) get the retail Pro1X I perked for...

Oh thanks much for that. I admit I had just assumed, based on the design of my current OnePlus cover, that that wasn't an option for the Pro1. Shame on me for not searching the forum first! (I shamefully admit to having completely missed the Pro1 and not discovering F(x)tec until the Pro1-X, so I've got a lot to learn!)

It most certainly can! 😄 I have been using it since 2019... See e.g. the slo-mo video where I use one from the 'open' thread here. I have a lot of blah blah in this thread in my blog, and we have a long thread in here as well. Sure it is DIY, but we are talking a few minutes of work that anyone can do (no special skills required at all) YouCut_20200123_155044091.mp4

Pro1-X has arrived in Finland, one day late, but I'll take it. It is definitely not blue, but it is 8/256, and I never had a strong feeling about the colour, so this is fine. I should add that first impressions are very good. The hardware feels excellent, very good build quality. Great screen. I have not tested any connectivity yet. The hinge mechanism feels excellent. Only disappointment is lack of screen protector, as mentioned by others. There is neither a preapplied protector nor an included separate one. I have in the past kept my phone in a flip cover, which obviates

The -X has a single stage button, I suppose the specs page needs updated. Can confirm the on the original pro1 first stage is rather devoid of tactility, works for me though.

Just for the record, my Pro1 has a clearly felt two-step behaviour in the shutter release button. When I press it until there is a substantial resistance, the camera focuses, and then I need to apply more pressure to take the shot.

Pick your poison, basically. One is a master to convince you that everything is great. The other is little bit more honest in my opinion.

I haven't read it, but guess it in many words says "We will track you, and steal all your data, without asking again, and you have to pay for the data transfer doing so".

After flashing, the UT is reset & runs the first boot setup wizard. Weirdly, a final `fastboot set_active a` hangs.

Same. I bet this is a radio firmware problem, not a radio hardware problem. I'm sure as more people get their devices, these kinks will get worked out.

For what it's worth, I run the stock OS that shipped with the Pro1 and haven't had any issues aside from needing to reboot the phone every so often (I think to refresh my phone on my carrier's network or vice versa) to receive texts and calls. I don't have anything sensitive on my phone that could be compromised but I use it mainly with zero trust principles. I accomplish this in part by using a different email for my phone than my actual email, disabling BT, location, and WiFi, except when I am explicitly using one or more. Even then, I only connect to trusted devices (BT; not to exceed X

To be this slow I would guess they are filling the last little gaps in a container full of other stuff with phones. Two working weeks and still less than 100 reported sent is pathetic but Fxtec have obviously done their bit as it is happening. As someone who ordered a couple of days from the original IGG end date I should be near the end of batch 2, which at this rate might arrive in time for Christmas. At least Ubuntu will be ready by then!

I hope you are right. We will have to wait and see to we have more units delivered to see if this is for a specific unit, or a general issue. Though at the least for the Astroglide, radio firmware is bit more complex to update, according to the EE section of their update - it might or might not be the same for Pro1X.