Leaderboard

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

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

This has been done here by others indeed (namely @claude0001and you for Android/Lineage, and others and I did it for Sailfish and Droidian too, but I believe I'm the one who used it the most on those two OSes: https://youtu.be/-dgD5jci8Dk, https://youtu.be/8PnDZtKzsSc, https://youtu.be/rgxrJj37xOs). To some extent, running a custom WM onto Droidian (the host, not a LXC container) is feasible too. I have a Pro1 running Droidian with both Phosh and Sway (plus my i3wm container too), but there's a significant issue on the Sway side because the resolution is twice smaller unless I set scaling

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.

Sadly there's nothing fully working yet, and it's hard to know the status of things that were promising. - Kholk/Angelo showed very encouraging progress with mainline on the Pro1 (msm8998) more than 1.5 years ago, but then I didn't see more news about it or instructions (but we may have to check his commit history somewhere?): - Then, as @claude0001mentioned, @Danct12managed to boot Arch ARM on Pro1, but I think it's stalled and he is not working on it anymore (due to touch noise that mainline doesn't dampen): - And then, the same @Danct12 ported postmarketOS to

How about the approach of running some kind of Linux using Termux and PRoot, like AnLinux? You don't even need a rooted Android. I quickly tried a minimal setup of AnLinux (minimal Ubuntu + Xfce) which installed in a few seconds and does look like fun, except that after first install it doesn't come in native resolution and the RealVNC viewer I've used here (it uses VNC to display itself) doesn't seem too user-friendly, either, at least not at first glance.

I've seen other benchmarks which, all in all, attested the SD 662 only slightly lower performance compared to the SD 835. From that I would expect to hardly notice any difference at all in actual use, perhaps with the exception of a rare app that heavily uses one of the operations for which the difference is more significant. On the other hand, that's only the CPU; the GPU is substantially slower indeed. Still, as of now, the Pro1 X doesn't feel any less snappy to me than my old Pro1. But then again, except maybe for the BB PRIV, I never used anything but midrange phones which always performed

@VaZsogreat to see! Thanks for the longish first impressions! Can confirm, the built quality is excellent imo Kudos to @Erik btw for designing that awesome animated bootsplash logo. Care to share what format you used and where you pushed it to 😅 I could try make one for SailfishOS and UB.

Nice comparison, and good looking Pro1 (I bet it's a spare)! Thanks @VaZso.

More ram, new camera-chip, an over three years newer chipset that will get security updates, and a two major versions newer Android too.... For many that alone says update. My daily driver has since 2019 been a retail Pro1 on stock android. And when I get the retail Pro1X as I perked for, I expect it to take over, and demote the Pro1 to tests (and as a backup device) But sure for some power hungry tasks the Pro1X is slower. But for a lot of tasks the difference is minor. Not unusual that an older flagship is close to a newer midrange chip. Have a look at e.g. this https://nanoreview.

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

If you want to run mainline Linux out of principle, I totally respect that. 👍 But, on the practical side: what do you think you would miss if you ran your favourite GNU distro in a container of Android, Sailfish or UBTouch, as proposed by @matf-kabouik or @Rob. S.? Many think of an Android/Lineage chroot or an UBTouch/Sailfish LXC as an "emulator" or a "virtual machine", and therefore have the gut feeling that any software installed in such environments would not be "really" running on their phone. That its speed of execution would be slower compared to the "host OS". That it would s

I noticed another small difference the Pro1x is ~10g lighter and way less slippery than the Pro1.

Small clarification, you can just take any Pro¹ or Elephone U/Pro fitted protector since the display of our Pro¹-X is exactly the same. Protectionfilm24/Schutzfolien24 @Hooklinked above just reacted fastest to my information that the Pro¹ foil they cut fits. As i could try having a spare Brotec foil for the Pro¹ around and applied it to the Pro¹-X. Same perfect fit. The Elephone U/Pro search will likely even bring up tempered glass screensavers. Those have never been marketed for the Pro¹. But fit nicely, again due to exactly the same display unit. But i am not a fan of those, imo they br

If I recall right @tdm and a few other did the LineageOS 16 for the Pro1 before going public, though they at some point showed some test-versions, see this

...and not necessarily hosted at GitHub or GitLab... Sometimes it is better to filter unnecessary "noises" around a project till a point it needs more testing and it may have more contributors after a specific point of development...

Pretty sure I read that somewhere from someone who would know. Fortunately we have a Pro1x preorderer who seems to be able to work on mainline too, and even if Angelo is independent again, he might still want to work towards mainlining both devices (after all his work on msm8998 was long before F(x)tec said he was part of the team), so all hope is not lost.

I'm seeing it as well (thought it was just me!) It doesn't appear to be at a consistent time, so it being stopped or crashing is something I'll try to look into when it next happens.

The closer you can get to Linux in the way you mean it, currently, is Droidian, which is like Mobian but based on the Android kernel.. They already have a port working, which I aim to test later this week. But no news on mainline yet. Techwizz on the Discord is motivated to work on it, but it's a huge task so I don't know how far they can get alone. I believe Angelo no longer works officially for F(x)tec, but don't know what is the reason for that. I heard he is in an community dev group though, but no idea if he is active at the moment.

Anyway, I have just received my Pro1X which should be a very early one of IGG orders and it has a serial number somewhat above 5000 which may mean (if they are not numbering inconsistently or randomly inside batches) it may be near 5000 Pro1s (or let's say more than 4000) around the world... or may not if the numbering does not reflect the queue.

I had this problem while traveling on a highway at one direction near a specific place several times but not always. Since a point in time I did not experience these spontaneous reboots maybe after one of the stock upgrades but definitively not since I use LineageOS on my Pro1. Anyway, I have received my Pro1X today - I plan to write something about it but basically it is well assembled, however, I feel stock system still needs improving. ...it remembers me of Pro1's stock system like the way the screen does not come up well on Pro1X after moving the phone off my head for example..

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

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 just received my pro1 x, while using it in the dark i missed the keyboard backlight. Is there a trick to turn in on or is it defective?

I am in the early stages of tracking something very strange indeed. I've been getting alerts for a few days from my own internal network monitoring (Nagios) that my primary wifi AP is often dropping packets on its ethernet interface. Since I've been busy with other things (not the least of which is the Pro1-X itself), and the packet loss isn't enough to cause problems, I didn't look into the situation carefully until last night. Once I pulled up my reachability graphs, I realised that the issues seem to have started at exactly the same time I received the Pro1-X: There are a c

Also check if Caps changes. And if you are in E.g.Settings search (at the top), does the fake keyboard disappear when you slide open the real one. (Trying to find out if it is the light in it self that is the issue, or it does not detect the keyboard being opened)

Thanks to @mosen, this link... https://www.protectionfilms24.com/article/2x-brotect-flex-full-cover-screen-protectorfxtec-pro-1-x-5145664.html

Thanks for your neutral review! The camera issue when keyboard is open is fixed in a later update if I remember correctly, that you could get as OTA soon (hopefully) or in the beta program (see other thread here).

You may also check if your Pro¹X stays in landscape mode when the keyboard is open while you rotating the device.

cool! Seems pretty consistent!

Tried to do them on a Pro1 and Pro1X single core Pro1: 394 Pro1X: 307 multi-core Pro1: 1604 Pro1X: 1294 compute (opencl) Pro1: 1943 Pro1X: 383 compute (vulkan): pro1: Fails, 408 (0 on Horizon detection) pro1X: Crashes the entire app And the big difference is in the GPU parts only

well, with respect to your numbers, mine seem to be on the optimistic end of it. So I'm putting the Pro-1X in the best light possible.

To me it make sense that they have taken a principal decision not to tell what is going on. If they did, they would have endless questions on how far they have come, and if it would be possible to get an early version for testing et cetera. It make a lot of sense waiting to they have something fairly close to an acceptable version. But that said I'm (also) impatient and would love to have an idea on when we will get it. It is like the Pro1X it self, worth waiting despite felling that the waiting time is killing us....

If you are lucky... otherwise that Pro1 would has been also converted to Pro1X... I would still wait for LineageOS... support also did not come too early for Pro1 but it is a much better system. I hope there are some work in the background and Pro1X will also get official LineageOS support, it would worth a lot.

It is a good idea but I would not think it is an easy job hunting for a used Pro1.

i think we have to start with a other Point. I use the Phone since Friday with no Problems by making some longer Calls (1 Hour) and my phone rings everytime so no forwarding to the Voicebox. -> Phonecalls are working So i think the problem is to search in the type of Networks. i am located in Germany (Munich) and use Vodafone GSM/WCDMA/LTE With the Data Connection i have some Problems in the underground but this i have with every Phone. I have now made the change described here, And will test it the next days.

Just a wild guess. Could it be that the Nova process is stopped (or perhaps even crashes?) and the system fall backs to using another launcher? It could be the battery optimiser or other software that 'cleans up' background bloat, that tears your nova down too? Next time you see, before reselecting, try to go to apps, and see if the Nova is stoppable, or already is stopped. You might need to make sure it can not be optimised, if it does not support Doze properly. (Under the apps, and the app, advanced, and battery, see battery restriction and battery optimisation).

If they are using the hardware drivers from stock android, the issues are unlikely to be limited to one OS.

Just made a test comparing Pro1X to my BB Key2 - on 5 GHz Band. There is some difference, knowing the Key2 is not the best Phone on Wifi. (The stronger connection is the Blackberry) Distance 3 m.

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.

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)

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.

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

Okay, it looks like this problem actually does not appear after I flash Ubuntu Touch. (I do, however, now have the problem that the screen goes black on UT whenever I close the keyboard, but that's unrelated!) Not sure at this point why I saw such variability on my AP going back to the day I got the Pro1-X. But it does appear that at least the worst examples of the problem are exclusive to Sailfish. I have updated the topic on this post appropriately, and will continue to investigate!

Oh of course. My post was intended to be a "helpful hint", not a "waah this doesn't work". 😆

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.

Screen protectors reduce the likelihood of a shattered display whether or not they are tempered glass, and not by absorbing the impact of a drop. Scratching your screen is scoring the glass, making it significantly more fragile.

I wish we would hear something about Lineage for the Pro1x, given they are allegedly shipping soon. @tdm @npjohnson Is there any news on the Pro1X front, or are you bound by an NDA?