Leaderboard

So, it appears that I was able to repair my Pro1-X's radios. Previously, telephony and mobile data wouldn't work for me, as documented earlier in this thread. WiFi, Bluetooth and GPS had always worked perfectly. It turned out that my Pro1X was missing most of its "antenna" connector springs. My main antenna (aka. USB) board was missing two of its three connectors, and the last one broke off while I was diagnosing the problem. See picture attached. It appears these things are really fragile. Also my "diversity" antenna board was missing one connector, which I found rattling in a

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

In a casual conversation in Discord today, while helping someone with a battery problem, Casey provided some information on the shipping situation. Hopefully that means there will be an update soon, I'll quote Casey so as to not misrepresent. After verifying that the photo in the last update was a new photo, he was asked if the units had been tested for battery problems. He said: I am just quoting from Discord. I can't answer clarification questions. I just thought this information would be nice for folks over here who don't go to Discord. As I said, maybe this means there

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

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

Make your displays last longer I've recently ordered a bunch of those 'b-ware' displays and out of seven, two were in good condition and one is usable (~20€ each). That's okayish since there are no good displays to order anymore. As the displays are so scarce nowadays and they never caused touchscreen problems when assembled in the original phones (Elephone U Pro), I've looked more into the touchscreen issues. I've inspected the frame and searched for a point of failure. And I think I found one. Using one of the broken displays in my order (big black dots over the display) I found o

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.

No, I think you got me wrong. No offence but, like many, you do not seem to understand what "Linux" really is. Do not worry, you are not alone in this. Especially people with many years of experience in running Linux on x86/64 servers or workstations often make wrong assumptions when it comes to embedded systems, like phones. Android does use a real Linux kernel, and thus is a true Linux system. You can grab its kernel source from kernel.org, configure it to you liking and create your own custom ROMs based on it. The only limitation is that you practically can only run the single major ke

It's hard to say whether these antenna connectors were broken when shipped, or due to disassembly on your part. Have you've heard the antenna rattle inside the phone when you first received it? Would that be the reason why you took apart your device to check? The antenna springs are indeed fragile. Not like other devices we see in the market, they normally have antenna pins pointing upwards, not sideways that contacts the frame. This can be especially seen in devices that have metal enclosures. The antenna springs on the Pro1-X are surface mounted via SMT, and the glue is to fix it in

I went to Hong Kong for that specific reason, is to coordinate with the warehouse and shipping partner and make sure our stock arrived safely. I understand your concerns about us being silent for the past months, there just wasn't much to tell everyone. Though, now I'm pretty confident we'll get devices shipped out asap. At the moment, our shipping partner has finished counting the stock and are awaiting our shipping list - which we're compiling as we speak. I estimate devices should start shipping in the next two weeks in batches.

Signs and wonders!

Long overdue post.. Apologies! Here's a guide on how to flash the Pro1-X stock OS with a script in fastbootd mode. This method works with Windows, macOS, and Linux. Please note, you will need to have your OEM/Bootloader unlocked before you proceed with this flashing process. Click the Google Drive link below for the documentation: https://drive.google.com/drive/folders/18Clj6qv4jXIFGfy0S1NO1K8DoN8bJ3Ms?usp=sharing

So ... I recharged my Pro1-X battery using a laboratory power supply after it had depleted completely, probably due to the "battery protection bug" mentioned by f(x)tec in their updates. It turned out that the most difficult part in this is getting to the battery. The Pro1-X is not nearly as "serviceable" as I expected. Separating the different parts of the body is not as easy as the instructional videos suggest. Also, the battery itself is glued into the phone, which makes its removal a scaring endeavour. Note that removing the battery from the phone is not strictly necessary for re-char

OK, fixed it. Prawn-X is back alive! 🥳 Turned out the battery was completely flat. After disassembling, I measured 0.00 V between the pins! I do not know how that happened, maybe I did accidentally leave the device on when putting it away. Still, I'm pretty sure the battery should never discharge to 0 V in any design scenario, as the device should automatically switch itself off before. I guess this is related to the "battery protection bug" f(x)tec keep mentioning in their updates ... Anyway, I was able to charge the battery to ~50% (3.9 V) using a laboratory power supply. After tha

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

@EskeRahn @Hook Agree with you both. It is a quid pro quo, and we also do encourage flashing different OS's, and beta firmwares from us should not void warranty. I've gone ahead and updated the Disclaimer. Please spread the word 🙂

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.

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

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!

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

You are right we should not jump to the conclusion but it certinly sounds like a reasonable explanation why it is working for some and not for others. And on this one I wonder what havoc that could make, depending on where it 'lands'?. It does not have to be a 0 to 3.8V short circuit to cause trouble, could be 'anywhere' exposed.

Welcome. Just curious, what brings you here? Waiting for a Pro1x, curious about keyboard phones, an old N900 enthusiast, an AI making a first post...? ;)

Yup I completely understand. I'll make sure we provide updates to everyone even if there's no news.

I've moved to a new address between the last update and now. When I saw the most recent update, I sent a e-mail to F(x)tec asking if I could have my shipping address changed. Interestingly, they responded and changed the address very quickly, and I even got a message from Indiegogo that the shipping address on my order was updated. I mention this because I've heard people on IGG claim that they couldn't change their shipping addresses with F(x)tec. The fact that I could do it quickly feels like an indication--albeit a small one--that they genuinely are hopeful things will work out this time.

That's an interesting theory. There was a previous theory discussed that the phone isn't able to handle lower frequency bands very well, but it could be that lower frequency bands somehow kick off more band switching. Be nice if there was software that could show you what bands are available to your phone at the moment and allow you to select one (regardless of signal strength) and lock it in as the one for your phone to use. I think that would create better control for testing. I know that my phone, which works, stays locked onto the same high frequency band even though others are availabl

About seven months now as my daily driver, straight out of the box the day it arrived. I must be in the lucky 10% to 90%. The hardware is nice and solid, the screen is nice, the keyboard is very nice, it doesn't struggle with any tasks I throw at it, I really like the blue colour. At least in my experience the PrawnX performs very well. I fully get your point. Lots of business models can be based on a subscription model, why not, it's an ongoing relationship. Maybe a donate button on their website. To me they're as good a cause as any other good cause, (or charity :)). I'd see

Sort of. ... It is an internally completely new product and not a minor upgrade as planned an advertised. Hence A (also) fell. But SURE they ought to have changed their communication material accordingly IMHO. We can agree that for some, indeed key functionality is not working. On the other hand for others it works fine. We have no idea of neither why it works when it does, nor why when it does not. Not even an idea on the size of the two fractions. IF we could say that it only worked under very special condition THEN I would agree on the claim - but again we do not know. I grew u

I was comparing the ports with the naked eye, and had to do some trial and error. I first tried the MI 8 port (this is for a Xiaomi MI 8 phone battery). That didn't seem to fit. Next, I tried the MI 6 port. The bar got in the way, so I flipped it around and when I was trying to figure out if I had gotten it connected, I noticed the charging board LED had lit up, showing voltage!! I grabbed an old USB charger that is limited to 1 amp. This charging board allegedly has an overcurrent protection mechanism where it will shut down if the current goes over 2 amps, but I didn't want t

Charging-only mode is part of Android, so the phone must be able to boot the high-level OS to charge. When you connect a power source, it will always start the Android boot process. If the off-mode-charge flag is set, it will start the charger program instead of the full Android UI. Yep, you triggered the "battery protection bug". The problem is in the closed-source firmware, and relates to the PMC configuration. LineageOS doesn't have licenses for this source code, so we need F(x)tec to fix it. The only way to avoid it is to periodically charge your Pro1 X, and once a month should be

Okay, I have been using my Pro1x for two weeks and it is now officially replacing my Pro1 as my daily driver. So I will not only be answering the thread question, but I will also be comparing my Pro1x to my Pro 1. They are both great pocket computers but the question was which would become my daily driver and which would be conscripted into the kind of experimentation I wouldn't feel comfortable doing with my main device. I like the Pro1x so much, that is the one I would like to always have with me. Also, for context (especially in terms of how I might not be like you), I live on the

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

We thought it would be a good idea to start a new thread and share the 3D model of our Pro1-X in a .step format for members who are interested in DIY-ing a phone case. The link below redirects you to a Google Drive folder with the .step file. https://drive.google.com/drive/folders/1u8c6_fxRFu2DU0tVqAxUe4QbA0VBVb4d?usp=sharing Feel free to share your ideas and progress down below for the community!

🎄 Christmas Update 🎄: A new build of LineageOS 16.0 (for SD835-Pro1) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. Go for the ROM dated "20221222". This build enables kernel support for PlayStation DualShock gamepads, inexplicably missing from the standard defconfig. 😉 There are no other changes since last week. As usual, my collection of mods relative to upstream is available. Why this is important: Turns out my son enjoys SuperTuxKart as much as I do, and he actually got his own DualShock3 for St. Nicholas Day. So we thought we could use th

OK, ok, I was probably overshooting a bit. Sorry. 🙂 However, my point was not about something specific they wrote in this latest update. It's more that I dislike the overall trend: One year ago, F(x)tec had an in-house developer actively working on Pro1/X kernel mainlining and alternate OS porting. At that point they seemed pretty serious about delivering a phone with official, out-of-the box LineageOS and UbuntuTouch support. As I wrote previously, this was a very important aspect of the initial Pro1-X concept. During this year, they first abandoned the "out-of-the-box" part (by shi

I just received this belt case from Aliexpress: https://www.aliexpress.com/item/33002799045.html I ordered size 5.1 - 5.5 inch. Pro1x in silicon case (for Huawei P20 pro) fits very well in it. Finally I feel like my phone is well protected against accidental damage 😃

fxtec-qx1050:~$ kmscube Using display 0xffffaf300560 with EGL version 1.5 =================================== EGL information: version: "1.5" vendor: "Mesa Project" client extensions: "EGL_EXT_client_extensions EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_explicit_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless" disp

unbelievable ! you did it ! Fxtec lack engineers like you. If my pro1x ever comes one day.... ...but however thank you ! 🙂

I wasn't able to 100% confirm that all units shipped out from the previous warehouse were working. Given the timeframe I had, it was quite impossible to check them one by one... Though, I understand your concerns and will reach out to those who did unfortunately receive a depleted Pro1-X and to offer support whenever we can.

Thanks for all the extra info. As you now know the count, l would love to know roughly how large a fraction of the waiting that will be served with the recovered devices

@ Casey - Thank you for joining the forum and giving us information. While the proof is the actual phone arriving and working, receiving actual information is a huge relief and boost to my morale on this situation, as it is to many others as well. Thank you for working toward as well as reporting on efforts toward a solution. Looking forward to more updates, hopefully positive ones.

Casey, I think that even a "there's sadly no news" kind of update would still have been better than complete silence. I seriously thought F(x)tec had gone belly up. But it's good to hear that!

Thank you @foxfreejack@Rob. S.@SchattengestaIt– I managed to macgyver the buttons back functioning by using the double sided electronic repair tape I used to reattach the display. I doubt we will get new videos from FxTec, but a big warning to everyone who is trying to disassemble/reassemble their phone: When removing the bottom cover, make sure to go nowhere near the buttons, else you will destroy them When removing the bottom be careful with he fingerprint connector, one wrong move and you will break the cable When reattaching the bottom cover, make sure to push out all but

Oh I'm not trying to say that it is not bad! What I'm saying is that we have not got a clue if it is 10% or 90% that are affected by the severe bug. we do not even have a clear pattern, so we can not say that it is likely or unlikely to work for anyone - and that only adds to the frustration... We do not even know if it is specific locations&carrier combinations that are not supported correctly, or if it is specific devices that would fail all over. I lean towards it being some particular environment it fails to handle correctly. My personal GUESS is that it is some band-swit

Latest update on IGG (here)

I think the worst problem in the judging is our lack of real knowledge of what was known when. In hindsight things look terrible, but that is not the same as saying that they did when the decisions were actually made. But sure their reputation is tarnished no matter if any actual 'guilt' can be placed of them doing stuff they knew were bad. I bet many that would be interested in a Pro2, would wait shelling out till it was actually available, and they hear the user reactions. Some of us feel certain that these are good guys fighting like lions to actually deliver, but I bet we are few

Not asking for a refund here (well, I backed via IGG, so not eligible for refund, but I would continue to wait even if I could). I believe I will get my Pro1x (actually, I will end up with two), just no idea when. I am lucky enough to have my Pro 1. If I don't, it's money I spent 2 years ago. It's been "written off" already.

Rapair missing pads/ways is simple on n900. ...always is better to use new usb connector...old one have have loose soo solder back old one is repair for short time.

Thank you Rob, turns out all I had to do was disable HD audio!