Leaderboard

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

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

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.

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!

...official los 20.0 is out 🙂

This is a bug in the stock OS, and happens because they modified Generic.kcm despite the comment at the top of the file instructing them not to. We have fixed this problem in LineageOS here: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver-19.1 Hopefully F(x)tec can include these changes in a future update.

I am not assuming anything. Believe me, I know the scale of this issue. I follow all the platforms where Fxtec is on, and I know it's a wide-spread problem. The reason I asked for this particular ticket is because the demonstration video attached can be of use for the developers to troubleshoot. And yes, it is our top priority issue along with the battery protection. Also, thank you for not sending us a ticket regarding a known issue, it does help us speed things up.

Some of the modifier keys are mapped a little differently from stock, but the driver is still the same one as F(x)tec ships. The most important differences are the 'F logo' key is mapped to META, and the SYM key is mapped to AltGr (ralt). The old behavior of the 'F logo' key (KEY_HOMEPAGE) has consequently moved to 'F logo' + ENTER, but you can now use any of the other keyboard shortcuts built into Android. This list is contextual, and 'F logo' + '/' will bring up the list of shortcuts defined by the current app. FWIW, this is the same mapping as LineageOS uses on the Pro1. Among other mi

When you are worried about privacy, the single most important step is to get away from manufacturer-taintedbranded ROMs, Google Apps, and the Play Store. A publication demonstrating that by network analysis of phones' upstream traffic has actually been posted here before. Privacy-wise, you can essentially get on-par with all those self-proclaimed "privacy-first" OS's by simply installing LineageOS without Gapps and using F-Droid for your app needs. Sounds hard, and few do this, I know. On the other hand, If you think you can't live without Google services and Google apps, no amount o

Not a scam, just really unfortunate company. Chen who started to make dream come true is one of us: real linux and tech enthusiast and nerd/geek. Just a lot of bad luck. I am one waiting for my device still. From indiegogo crowfund.

LineageOS 16.0 has been updated to include backported ASB fixes up to patchlevel "5 January 2023", celebrating one year of support beyond Android 9 EOL 🙂. At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 fetch the ROM dated 20230111. Remember that this is for the original SD835-Pro1 only! The note about lacking upstream code-review still applies (see above): all I know is that the system seems to run fine on my own prawn. As usual, all mods with respect to the official lineage-16.0 tree are available as a tarball for reference. Have a lot of fun.

Found it. The problem is if you only take the first part here: If you go in by the "Enter fastboot" this way will give exactly the reported FAILED (remote: 'Command not supported in default implementation') fastboot: error: Command failed But if you choose "Reboot to bootloader" you wlil get to the menu where it works. OKAY [ 0.000s] Finished. Total time: 0.000s

Until we are using tdm's driver, there will be undesirable interactions between the F(x)tec's custom keymap and the keyboard language selection in Android. Have you selected a language and layout as directed by the persistent notification to "Configure physical keyboard"? Don't do that. 😜

I can attest that a Pi4 works flawlessly so far for flashing for me. Just had to do: sudo apt-get install -y android-tools-adb android-tools-fastboot to install the tools needed.

Believe it or not, this is how we used to create OS distributions back-in-the-day. Fattire even wrote a short poem about it: So Many Zeroes! A Children's Book By Dr. Seuss (a.k.a. fattire) Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review. "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?" And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor. "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!" So Blue packered his tracks with a /

As have others on Discord. Sean says it's "moderately stable" which is good enough for me. Probably not that different than the first unofficial test versions of Lineage 16 we got from TDM for the Pro1, and those were rock solid. As soon as I have a Pro1x, I'll be installing it.

For some weeks, as a workaround for the bad LTE connectivity, I've been carrying a sensibly small and light mobile LTE router (TP-Link M3750) fitted with a second SIM card from my mobile provider, taking from the same data quota that the phone itself would use. For the time being, this workaround provides good internet access when I'm not at home, also while driving in my car, for both the phone and the devices for which I would otherwise use the phone as an access point like my laptop. (Too bad that while it takes a Micro SD card, too, this is limited to 32 GB; otherwise I could store my

Here is the latest update from F(x)tec:

I guess it would also help to install some monitoring app like LTE Discovery and report observations. "LTE connectivity is bad" is too general statement. In my case (and I also reported it on Telegram channel): I am in area where the Pro1x mostly uses LTE channels B3, B9 and B20. B9 and B20 are quite OK to signal level around -110dBm, but B3 is a disaster, even at level -85dBm. Now the example problem is: In the area I have available B20 with -90dBm and B3 with -85dBm and of course Pro1x chooses the one with apparently stronger signal (B3). As a quick fix it would help to force modem

@Casey, please do not assume that only people opening tickets are affected by the connectivity problems. I think many of us (including myself) regard this as a general problem of the device that will be fixed in an upcoming software/firmware update. These hopes are based on last year's October and December updates, where you acknowledged poor signal and connection drops as one of the most notable bugs of the stock Android ROM, and wrote you were preparing an update to fix this. Assuming the problem is already being worked on, I thought it would not be helpful to open yet another tick

The Pro1 seems really problematic with regard to fastboot. I recently flashed my wife's Fairphone3 using my Thinkpad X250 without any problems. That same PC never succeeded with the Pro1 ... There seem to be multiple factors affecting flashing, especially in fastboot mode, and some are not controllable in a daily-driver PC. E.g. many USB-attached peripherals are not "removable" in a laptop. Hence my advice to just use a dedicated system for all Pro1 flashing. Using adb/fastboot from a Raspberry 2 or 3 just works(tm)! They're hardly more expensive than a separate USB hub and are usefu

Hey 😄 We're quite behind on our customer support tickets at the moment as the person maintaining this was on leave for 2 weeks. We currently have a backlog of tickets from around Christmas last year, and will be working on them accordingly. Please note, we do not ghost any of the requests we receive. Apologies for this and thank you for your patience!

Split the above from the 19.1 thread Link for rom: https://download.lineageos.org/pro1 Just attempted a dirty flash from Lin 19.1 MTG12 to 20.0 MTG 13 arm64 (Android security update 2022-12-05) It boots nicely after a while, so seems to work with all preserved 😄 AND the long lasting keyboard&Accessibility bug (both 18.1 and 19.1) has been fixed, so Greenify and Android Assistant both works again - awesome

I think they know that something is happening but not necessarily know what. I also think they are very dependent on the origin - when I wrote my problem by e-mail in my native language, I have received a reply in English... when I have asked representative by phone about the different language of the reply, she told me English is their internal communication... so if I understood well, all complaints are translated to English then forwarded to the center where they check/decide what to do. I have just received an e-mail the second time that they have checked their system and not fou

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.

@Noob : click sound, yes. I would say no mecanic problem here. I glue one touch with cyanocrylate a few months ago as he felt, and had no issue since. I test with three press on different touch like 'aaa eee ddd ccc sss ooo mmm....' and see what happens, then I found this : when pressing the bottom part of the keyboard the bug disappeard. As far as I understand @veRYANgry solve the problem with tightening the two bottom screws, wich could be related to my problem.

Me too! Hopefully sometime this year 🤣

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

I've installed the 20230120 image on my device, and so far everything is going nicely. No (new) problems to report. However, as anticipated, early indications are that this build does not improve the LTE situation, so I will continue to keep my device locked at 3G.

Awesome! Too bad I'll be back with my Prawn-X only on Monday evening ... Can't wait ...

As already mentioned before, I use my Pro1x not only for data access (both regular mobile networks and Wifi), but also for calling (outgoing and incoming) and sending text messages using the traditional SMS (and also MMS if necessary). I disabled using VoLTE (voice over LTE) and also changed the priority for voice over Wifi to make it the last resort in case of Wifi being the only connectivity available (i.e. no mobile network coverage), because the call quality was rather bad with both VoLTE and voice over Wifi, but it works for me without any considerable issues apart from this (in addition

I would be happy with an unofficial release so I can finally start using the phone that is useless (to me) since it arrived in august...

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

Try to install Finqwerty from Play store. It will add additional keyboard layouts which you can chose in settings. See this. Btw, there is a small bug in Finqwerty for US layout (not properly showing ':' ) But it is already reported and if someone needs corrected apk before author will fix it, write me, I compiled corrected version.

It's very hard to reproduce on our side (UK/China), all RMA'd devices we receive have no problems with our SIM... The cell connectivity/GPS appears to be more based in the US region. Yes, this would be very helpful to us. Feel free to send it via email and we'll relay this back to the team for further investigation.

*off-topic* Yes, stick to that beautiful machine as long as you can. I love those old laptops that were actually compactified versions of true workstations -- with all ports, interfaces, and peripherals ever needed. I sadly will have to retire my beloved T400 soon (due to lack of video acceleration in recent Firefox). It is to be replaced by a T470p that can't even come with an optical drive bay. All for the "added value" of a few mm-thinner frame ...

Yes, that is the question.

After trying to actually use my Pro1-X as a phone, I am now convinced that community devs simply refuse to invest further effort into a Lineage port until at least the most blatant bugs in the device are ironed-out by the manufacturer. Few will want to invest time and effort into a new OS for a device that does not work on the most fundamental level of a phone. If the Pro1-X's connectivity problems are indeed related to the modem driver, we'll just have to wait until F(x)tec pump out a new stock to base on. If the issues are hardware-related, the device is practically DOA for many users a

I'm sorry to see that your Pro1-X does not charge/boot up upon arrival. Could you let me know your support ticket ID? I will follow up with your enquiry over there.

I'm not very technical, not a noob, but a knowledgable user willing to find and RTFM if I know where it is. Principly a Windows user, but am using Linux more and more (because I have two very knowledgeable and patient friends who use Linux professionally). I always found Windows to be very picky and inconsistent with flashing. Since switching to Manjaro Linux on a Thinkpad X230, I have had no problems. Didn't have to download anything. ADB and fastboot were already there and I can use them from any directory. It just works (note, I have only ever flashed Lineage so far). If a user l

Running the OTA updater right now. Had some issues starting the update because the updater kept crashing when I hit "Install". Fixed it by going to Settings -> Apps -> Show System Apps and deleting the Updater's app data.

I think when playing games, Pro1x seems to be better. Performance and graphics are both outstanding. I tried playing best games online on both devices and i found Pro1x better performance

Got there in the end.. I put the comms problem down as Windows version and or CPU architect using USB 3.0 port. Bear-metal with up to update win10 and Intel HQ7700 got me over the line. My ferdora rig is packing a Ryzen 7 3000. Let's see how I got with UBports.. Thank all for all your input (M_P)

I made exactly the same mistake (you'll find my similar post somewhere a few weeks ago) But don't stress, the link EskeRahn gave you works, I followed the guide and got my phone working again. Just go through it carefully step by step. I can also confirm it does work in a Windows VM running on Linux, it does with Qemu/KVM anyway.

So, wow, this is even weirder than I thought it would be, but it isn't LOS 20 or the Pro1 itself, so that's a relief. What was going on, and it seemed to be new behavior coincident with installing LOS 20, was that when I connected my Pro1 to the USB 2.0 hub to charge, the lightning bolt would appear and then it would go off. So then I tries a 2.0 cable to the wall and it was okay. Then I tried to a USB 2.0 port on my Linux laptop and the same thing that happened with the hub, Lightning bolt came on, then went right off. That's when I remembered that the USB 2.0 hub is connected to my

Exactly. Here is a part of the text on the receipt, which the driver signed (which you do not have VaZso): Please pay the amount shown to our courier against receipt of the above mentioned shipment. The courier will release this shipment only against payment of the amount shown - in cash/by cheque. Receipt only valid with our courier's signature.

A friend works in business consulting. His take on this: It's a completely automated process and Fedex would loose money if humans look at this. They outsourced the problem to the debt collection company. So just open one ticket, sent them the proof they want, document everything and wait for the debt collection to take over. Then send them the documentation and let them close the case. I don't think this is good behavior as a company, but it is also not something to get stressed out about. I think documenting everything is key and what I learned from my case: I should have not worri

My guess is, FedEx is not malicious per se, but as long as they don't lose substantial amounts of money through their broken import duties collection scheme they have no incentive to do something about it. Maybe the affair needs more publicity, like a lawsuit...

Yes, they have collected TAX/VAT from me in cash (the same as was mentioned in VAT-handling paper I had to fill for them), then they have tried to get me pay again electronically and still it seems like if I was speaking with robots. Local colleagues promise of forwarding the problem to the center (another country), then calling me back where the latter never happens, instead, I am receiving a "we have not found your payment"-like e-mails which I write a reply usually in 1-2 hours but never receiving any follow-ups. Be aware with FedEx and do not give them money without receipt as it se

I would be happy if you could share what helped in your case, so we may check if it also helps in other cases (different mobile operator) or if a different setting seems to help.