Leaderboard

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.

@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 🙂

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

They have given their all to this dream. It's been such a journey, but they have shown such character, it's been 4+ years of blood, sweat and tears...but it has been worth it, look how far they have come from the first prototype up until now...here is to another 4 years of successful phone deliveries..hurrah! hurrah! hurrah!

I've uploaded my latest build of LineageOS 16.0 for (SD835-) Pro1. At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 fetch the ROM dated 20230223. It includes backported ASB fixes up to patchlevel "5 February 2023". As noted above, these backports are no longer receiving upstream code-review. All I can report is that the build runs fine on my own device. This ROM includes a new local patch, disabling the infuriating "double-shift = caps-lock" behaviour of the HW keyboard while preserving the useful "sticky-modifier" and "long-press for special-character" feature

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.

So after patiently waiting for fxtec to come through and give me my refund for my canceled order placed on 2021.04.21 I called my credit card company and disputed the charges. I gave them all the information (date order placed, order #, number of emails I sent asking for a refund, how I contacted them, and the fact that no credit or confirmation of refund has been provided along with no contact from the "finance team"). I am happy to report that despite it being over 2 years, my credit card company provided me with a FULL refund and said that they will handle the rest of the claim. I did

Great news, thanks. I will try to find time applying the beta this weekend. 😁

You're misrepresenting what @EskeRahn did, reading it backwards. What he did was trying to objectively judge their character from thorough observation and actual evidence collected over four years, of which he also presented some, which you choose to brush aside without so much as a syllable. You're perfectly entitled to apply a different reasoning and come to a different conclusion, but to be taken serious in an actual discussion you would need to take notice of his arguments and his evidence and counter them, not just reject his conclusion (which I think is well-founded) simply by saying "I

As harsh as it sounds, in retrospect, F(x)tec’s biggest mistake was to keep up the effort of delivering all promised devices to their IGG backers. That they tried (and are still trying) to get a device to any one who invested in the Pro1-X crowdfunding campaign is honourable, but, from a business point of view, it was the wrong decision. When it became clear that the SD835 could no longer be delivered, they should have declared the IGG campaign a fail, taken the money, and invested it fully into development of a viable successor of the Pro1, without committing to delivering any devices be

It is indeed sad news 😞 To my knowledge, if there is still demand for USB port repairs, I think we can order more. But there is a MOQ for it, so it just depends if our previous vendor still supplies this and if the demand is high. I'm able to provide the relevant schematics on a case by case basis. We do have a number of Pro1 parts still available to purchase/for repair: - Battery - Screen - PCBs - Camera - Connection cables - SIM trays - Fingerprint sensor/back covers Apart from these, we will need to see exactly what needs to be

That was very sad news, 😨 Will you get them at a later point? Wasn't The whole idea of the usb on a separate print that it should be easy to swap? If end of service, could you provide diagrams, so some handy persons could produce them, without the need of reverse engineering first? What parts are potentially available for the Pro1? If none/few it would be nice to know if we have to treat a Pro1 with the uttermost care as irreplaceable...

We haven't released a new beta build yet. But we're still on track to release one soon.

Thanks for bringing some positivity in a forum full of complaints. Yes, this phone was so close to being amazing, but things out of the company's control threw quite a few spanners in the works. I am disappointed, but optimistic that they will fix the main issues in time. It's really amazing that a small company could design and produce a mobile phone that looks and feels the same quality as what a huge company like Samsung produces. I really hope they can resolve the issues and more of us can switch to using it as our daily driver. I cannot wait to show it off to my friends, es

has anyone noticed FX has become much more informative in the comment section on indiegogo ? i dont know why but they seem much more in control again and its a very positive thing shows that they do care but in the past they might have had constraints

I was assuming they would already have been shipped , sorry to hear that you are still waiting I have a higher contribution ID so im also still waiting This is good news , since you are around this forum allot and a active user Its a way to verify the information that we are getting is truthful or false If you get the device as promised then we , all , most , uuuuh some of us can also look forward to receiving a device I also like this update because it shows they are still working on the problem of shipping devices to their contributors

January of which year?

I can only add that for me, in Germany, with either Vodadone or T-Mobile as the carrier (the third of three German carriers, Telefónica/O2, may be a different story, I have no such SIM card to try), the device is usable for both telephony and mobile internet access with some but no too severe connectivity issues, at least since I've been running the LTE Discovery app in "No-LTE cycle" mode. (Until I installed LTE Discovery I used to carry a mobile Wifi router with VoWifi enabled on the phone, which I still sometimes do and which of course makes for an even better and actually quite perfec

This is where that second hexadecimal number in each keymap rule is useful. It allows you to specify an alternate Linux event code plus any combination of Shift, Alt, AltGr, Ctrl, or Fn. F(x)tec moved the yellow labels around in ways that can't be matched by only rearranging the keys, and tdm gave us another layer in the kernel to fix this 🙂 Say the yellow label was 'Å', but the .kcm file defined that as 'AltGr + some other key'. You would define the last number in the keymap rule to be that other key, but with the 'AltGr' flag set as well, e.g. key_code | KF_ALTGR == key_code | 0x1000

So sad that such steps were needed, but at the least you got your money,

Hi All, Thought I'd post my experience so far with the Pro1X on stock firmware. Want to see if others are finding it similar, and also give people an idea of what to expect when they get theirs. The Good GPS signal Stock ROM relatively clean and vanilla Camera is pretty good Keyboad (obviously, that's why we all got one) love having a hard keyboard again. On screen keyboard is good too Screen is bright Glass screen feels really nice. Very smooth and scratch resistant Performace is fine, I don't push my phone very hard, but haven't had any iss

I might understand a clause like this with "alpha-releases", but the point of "beta" in general (as I Understand it) is to reach a wider group that is ready to accept even severe functional flaws, or even to return the device if bricked, but yet the company still honouring warranty, as the risk of a broken device is expected to be very small, and thus the company takes that risk, to gain the feedback from the users. That a beta test is often limited in numbers is obviously to reduce the risk for the company if many fails seriously. I'm a little sad that FxTec don't use beta in this way. A

The only issue with the Beta-program is the clause where you say that we void our warranty if we join. Not the best way to entice people to help. That is why I didn't join....

Relating to LTE connection drops, I've compiled a user manual to fetch modem logs in our beta-testing group. If you are able to reproduce any issues relating to connectivity, please join our program and give it a try!

"My phone works sometimes, all I have to do is install this app that fixes an inherent flaw in the OS and carry a black box with me everywhere I go."

The global supply chains, especially for tech products, have been disrupted for years. How is it today? We have traced the path of a smartphone and show where delays still occur. [...] If the device is already manufactured, as in this case, the retailer can be happy about this. His supplier in the manufacturing metropolis of Shenzhen in southern China has the product in stock and only has to send it to Europe. Both sides have known for a long time: "Only" has been extremely relativized in the past three years. Because a lot has come together. Not only was there the impact of the ini

I actually don't think this was a "backdoor" deal. The phones for supporters were put on palettes and sent to the Logistics warehouse to be sent out to backers in August. They also produced a limited run for Expansys Retail which were timed to go out and made available following shipment of the perks. What put a wrench in the works is that they hit a wall when a problem came up with their logistics contract. However, Expansys retail had received their units and proceeded to put them on sale (probably and agreed upon date that was supposed to be post-shipment) with only a minor markup from W

Well i agree with most things you said except the xda part. They detached themselves really quick. There has never been any article on xda`s website after the announcement "xda mad a phone". Also the xda-developer.com website went from development to marketing only. There is nothing positive to say about xda. But with the rest i agree 100%.

@Bob78 Good news, I just found a spare USB port from a previous RMA'd unit. If you'd like, I am able to reserve this one for you. Are you looking for replacing this module yourself or sending us the unit for repair?

...if you want you can post me PM I have some C connectors for fx purchased approx one year ago

I think "interpolation" is not quite the right word here. The idea with these 48 MP sensors is that they group equally-coloured pixels in bunches of four, and usually average over these four neighbors to yield a 12 MP image. This is called "pixel binning" and reduces noise through the averaging operation. Technically, in optimum light conditions, the camera could indeed record all pixels individually to yield a 48 MP image. But, seemingly, the Pro1X's drivers do not support that mode. As @EskeRahn and @daniele606 point out, CPU-Z is wrong. Other apps correctly identify the SoC as

Thanks everybody, now everything looks more clear to me: Interesting thread, I have understood a little better (or at least I hope) how digital photography works. Megapixels aside, which are not really important, the photos i took in my room don't looks bad compared to my Galaxy A52s. I will try to take some shots around this weekend. I used CPU-Z but "he" is probably guessing wrong, i also have "BENGAL" as model. Furthermore, "Aida" is reporting the exact same information mentioned above so i believe my device is just fine😊😊

Both 3C All-in-One Toolbox or Inware will do that. They use the part number (eg MSM8998 for the Pro 1's SD835) rather than the more familiar model number or whatever they call it. Inware is good if you mostly just want information. 3C has endless tools and is a little overwheming sometimes. 😉 Both are on Google Play.

Hi All, writing from Italy here, i just recieved my Pro1X. I was able to setup my Google account and other app. Checking some stuff around i noticed that the SOC is snapdragon 665 and the camera is 12MP. Am I completely wrong or should I have expected a 48MP camera and Snapdragon 662 with the Pro1X? It doesn't really matter as I don't need a new phone anymore, but i am just curious to understand if this configuraiton is not only for me. Happy to have finally received it 🙂

stopped fighting to get stock android and went to Lineage 20. completed the entire install on the first attempt within 20 minutes.

I can top that. September 2019 here 😉 Of course I can be more relaxed about it than others as I've been happily using a pre-owned Pro1 since February 2021, replaced half a year ago with the Pro1X that I had ordered via Indiegogo in October 2020 (and lately with an Expansys-bought QWERTY Pro1X to replace my QWERTZ phone...). Good news is, they still exist, they are delivering, and chances are that we do get our phones eventually...

Dear f(x)tec, I would like to inform you that some of us have ordered a Pro1 via your website three and a half years ago (November 2019), have since been upgraded to Pro1x and also have been promised a somewhat prioritized delivery compared to the IG backers. It would have been nice not to rub it into our faces that you might or might not have completely forgotten about us, since even the e-mail updates have ceased to come by. Please, get your shit together. Sincerely, a patiently waiting paying customer.

Actual update here:

This post isn't specifically about F(x)tec as I had the same problem with Unihertz. I got my Pro¹X about a month ago. I was excited. I love the keyboard. It's fun to whip out at parties. But it simply doesn't work. I mean, the most basic function of making a phone call: sometimes, the caller can't hear me. My issue isn't with the technical problem. It's a new phone, and hardware and software are hard. That's understandable. My issue is the lack of working with users to solve problems and the poor prioritization of issues. Companies can be forgiven when a user reports an issue bu

It has problems with VoLTE where the loudness setting of the handheld is ignored. For me, the VoLTE connection would also stall often while roaming - not sure is this is related to the Pro1 or to my carrier. However, I am in the comfortable position that German carriers will support GSM (ie. non-VoLTE) calls for years to come, so I just disabled VoLTE. Haven't had any call issues since. Regarding @sequestris saying the Pro1 is stuck on Android 9: This is true for the vendor-supplied ROM. There are very mature LineageOS ports from 16.0 (Android 9) all the way up to 20.0 (Android 13) i

For the Pro 1 Pros: Keyboard is there which is what I really wanted Good battery life Works well on wi-fi calling Can send and receive MMS on Wifi FABULOUS camera now that I have the right software on it (see unedited images below) Expandable storage Cons: Phone call functionality sucks. I drop about 50% of my calls, when I am not on wifi text messages often get hung or don't go through Voice clarity blows and I need to use earbuds or put it on speaker Screen rotation gets hung and I have to lock and unlock the screen to fix

I'm sure the Pro1x is not a money maker at this point, but Fxtec does have another venture that may be quite successful (you have to scroll to the very bottom of the page to find the FxTec link). https://www.linxdot.com/ I discovered it when Expansys sent me an add pairing the Pro1x with this device. It may be why they are not out of money. If so, great.

It may happen that antenna design of Pro1X is worse than Pro1's design (I don't know) but this problem sounds like most likely the SoC's firmware also has problems which should be independent of F(x)tec... or other manufacturers are actively doing workarounds on poorly written software of the main component of the phone? ...or other manufacturers are receiving firmware updates from Qualcomm to address SoC-related issues but F(x)tec does not? ...or something happens which triggers an issue what does not happen on other phones? ...

I'm on German O2 (cannot recommend), and mobile communication is horrible. Unfortunately I couldn't get the LTE-Discovery app to work on LineageOS. What is that "No LTE cycle"-mode actually doing? Meanwhile I have found Rx Monitor, which at least allows me to see what radio frequencies the modem is using, though that app (to my knowledge) cannot influence the modem behaviour. Contrary to what others observe, my Pro1-X works when it manages to connect on band 3 or band 1. It seems to fail when forced to use band 20, the "long-range" LTE frequency (800 MHz). Unfortunately, both, my Pro

It is important to understand that there are two F(x)tec phones: the Pro1 from late 2019 and the Pro1-X that is currently shipping (slowly). I own both of them. My original Pro1 has its flaws: its camera is not really good, the LTE and WiFi connectivity are ok-ish but not stellar, and even the keyboard -- the one distinctive feature of the phone -- has never been much fun to use. That being said, the Pro1 has served me reliably for almost three years as my only phone. I use it with a custom LineageOS ROM which I have configured to double as a miniature GNU/Linux palmtop. The latter functi

There is another layer, the .kcm file. For Scandic models of the Pro1-X I made this key character map: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1x/+/348323/5/AsantiKeypad/res/raw/keyboard_layout_fxtec_scandic.kcm The Unicode code point for Å is U+00C5, which is mapped from the key code for "LEFT_BRACKET" (decimal 26) here. I used Android's Swedish language overlay as the basis for the F(x)tec Scandic default .kcm file, and I suggest you choose the language overlay closest to your own and set up your kernel keymap to match. This unfortunately excessively com

Absolutely; the article just shows that even if everything else, like in manufacturing, goes as planned, and the manufacturer does not suffer from things like liquidity problems due to earlier obstacles, a simple delivery can take 2½ months.

> preparing shipments for the Pro1 X units allocated to contribution IDs ranging from 568 to 1126. My contribution ID is smaller than 568 and still waiting. 😯

I should add an update that the problem is currently consistently happening. I tried switching to fluenceplus by changing device/fxtec/pro1x/vendor.prop and rebuilding but that didn't help. I noticed some SELinux errors early in the boot so I also tried compiling in new_value=0 in SELinux to always make it permissive, and that made the symptoms of the problem slightly different but ultimately the same. I'm kind of stuck because ultimately the q6voice.c calls make a call to apr_send_pkt and I don't know where the source of this is.

OTA for the same was also smooth. This time, I stayed rooted. My experience is that, most of the time, OTA updates don't disturb root, but once in a while I don't have root afterwards. Don't know why, but no big deal. Easily fixed when it does happen.