Leaderboard

It does this because F(x)tec makes the key generate KEY_HOMEPAGE. The fix is to change this in the kernel source, e.g. https://github.com/LineageOS/android_kernel_fxtec_sm6115/commit/41b535243dce9e057069adda494cbbaf8c720f35

The question mark is there, it's Alt-L! I completely overlooked that there is a fifth layer in that layout with the Alt key modifier, even if only a few keys are assigned there, and I only noticed it browsing through the .kcm files from github... Even though these FinQwerty layouts were originally designed for the Pro1 with it's "shifted" physical QWERTY layout, they are still quite functional on the Pro1 X as they're overlays for actual keys like A or LEFT_BRACKET, not for lower-level keycodes. There may still be some more minor differences to how it used to work on the Pro1 (

Thanks! Just noticed that the FinQuerty layout I had chosen was for the Pro1, not Pro1X...

I suppose I could take the tin foil hat off for a while and give them a try 😀. When I plug my PrawnX into my laptop it shows up as 'Fx_tec_Pro1X_BENGAL-IDP__SN%XXXXXXXX' Most of the photography discussions go over my head, but I find FreeDCam quite a nice app.

The 48MP sensor produces 12MP images after interpolation - I guess it is a sales thing that Sony market it as 48MP, and this is usually just copied by those that use it. e.g. FxTec. We have this difference discussed in another thread somewhere... Interesting with the 662/665, what software are you seeing this on? If I check my Pro1X with "Aida", it says "Qualcomm snapdragon 460/662", "Device Info HW" says "662", but "CPU-Z" says "665". So I guess that the app sort of takes a guess on the cpu based on the info available, rather than get an actual ID back - that could explain discrepan

Inware says "BENGAL" for my Pro1X, which is the codename for the Qualcomm Snapdragon 662 SM6115.

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.

The site says it is 662 with 12MP https://fxtec.com/pro1x

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 🙂

We got no real info here, but we do know that many US carriers makes it it hard to do BYOD, so check with you carrier first, or be prepared to look for another carrier. There are some good info in this thread on what various US users have tried.

I have stopped expecting any logic here, though I still expect that I will get it at some point.

That's good news for me; it's the exact model I ordered. The bad news? My ID is 1874. No dice on this allotment. It does make me wonder, though: might I (and others who ordered that version) be prioritized in the next contributor batch as well?

Hello, when will the phone be available in the US or for purchase in the UK?

What they are now sending is the 8/256GB Blue QWERTY-EN, So those of us with more rare choices (like my Scandinavian keyboard) will have to wait further, despite having a number way below 568.

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

They changed the download site (this is Pro1, not Pro1X). As usual practically everywhere on the web these days to poor 'design' with extreme waste of screenspace. (see image below) And the recovery boot image now always have the name boot.img, so you would need to manually rename or move in subfolders to to keep pairs of files for later usage. (previously the recovery image were named e.g. lineage-20.0-yyyymmdd-recovery-pro1.img for 20.0 ) But it works as usual: (lineage-20.0-20230306-nightly-pro1-signed.zip on February 5 security patch installed smoothly using adb sideload and Mi

I have 328 and have not yet got any info concerning my device.

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...

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

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.

Guess I was lucky my Bank was suspicious of the order and I had to dance around with them for a while. I'm in the 900s. Lol.

> 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. 😯

Actual update here:

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.

😄 Indeed; a bit of patience might be in order. I'm still waiting for the Pro1 (later changed to Pro1X) I ordered in Sept 2019. (I did manage to get a pre-owned Pro1 early in 2021, though, and I received another Pro1X ordered from Indiegogo in Oct 2020 about half a year ago, which I've been using since then...)

January of which year?

I truly believe that is what happened too. I wish my husband had gotten his Pro1x, but 2 years was just a little long to wait. I wish they were going to actually refund the money. I think they are hoping that in 3 months they will have enough new orders to do some refunds. I do appreciate the fact that they are not taking new orders. At least they did that right.

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

I completely agree with all of @kevg's points. I'm not a programmer, but I work in an IT company that provides exceptional support. I'm telling you that this sort of behaviour wouldn't fly at our company. If there are weird issues with our platform we're onto it, we let the client know what we're doing and get support directly with the developers. Even if it costs us in the short term, the benefits to reputation far outweight it. I'm part of that Beta Telegram group, it's a waste of time. Good people on there trying to figure things out, but little response or movement from staff at Fxtec

You can ask..., i did in November 2022. Until now, no refund and no phone...