Rob. S.

Here's mine, finally got it yesterday! Yay! 🙂 (QWERTZ 8/256 GB IGG order from Oct 2020, with the QWERTY 8/256 GB website order from Sept 2019 hopefully arriving soon too, though no tracking confirmation yet.) Coming from a (shifted) QWERTY, 8/128 GB Pro¹ with LineageOS 18.1 (didn't bother to upgrade to 19.1 yet with the Pro¹ X now actually within reach), I thought going back to stock Android would be a significant change for the worse, but so far I don't feel it is. Except for the right/lower speaker dropout problem, I haven't found any issues yet, which of course doesn't

Doesn't sound like a contact issue for me, either. If it were, the dropout phenomenon wouldn't reliably go away with the volume dialed up, which it seems to do for the people who've been reporting this. Also, a contact problem would produce some kind of noise between loud and silent phases, which doesn't happen here at all. The cuts are absolutely clean. Is there even anyone who doesn't have this issue? I'm no low-level systems programmer, but intuitively I would locate the reason at the bottom of the driver stack, like in the speakers driver, if there is such a thing. Headphones-o

I get wildly flashing triangle/circle/square icons when I tap and hold the square icon which is strange, but I get split screen mode by a short tap on the square icon, a short tap on the size-reduced app's icon, and then there's the split screen option. (I keep forgetting how this works as well, with so many changes in past Android versions...)

Problem is, the Pro¹X they wanted to build actually was a Pro¹ — just with more flash storage (optionally), a blue casing and some of the already existing alternative ROMs preloaded, possibly after helping to make them more stable in case of Sailfish and Ubuntu Touch. But then they didn't get the SoCs anymore, even though, as I understand, the SoCs were paid for and promised. And as that SoC was already out of production at that point, they couldn't get it anywhere else, either. So they made a complete redesign for a current SoC. Which, unfortunately, loses compatibility with existing RO

Another shipping update on Indiegogo: So we now know that there is a – albeit smaller – third batch coming, too.

Today's delivery attempt failed because the delivery person wanted to collect import VAT (130 €). Next attempt tomorrow. (FedEx did not announce the fact, let alone give me the option to pay online beforehand, as UPS did last time I received something through them... )

(OpenCamera supports it too, but obciously this is Pro1 and not Pro1X) On the Pro1, so does 'Manual Camera'.

Just for the record, my Pro1 has a clearly felt two-step behaviour in the shutter release button. When I press it until there is a substantial resistance, the camera focuses, and then I need to apply more pressure to take the shot.

I've become wary of screen protectors! I've told the story already, but some time ago, I applied one such thing right after I had self-installed a new display panel from Aliexpress, lest I would break it again. Next thing I did was trying to wipe some dirt off the screen, and with the swipe I catapulted the phone from the table onto the stone floor, because the protector had a slightly sticky surface whereas we know the phone's bottom to be dangerously slick. Needless to say the display broke again in the process! Also, my impression is that a screen protector might save a display from mi

When I get my 2019 order which is supposed to come as a blue QWERTY 8/256 GB Pro¹X (no tracking confirmation yet; the 2020 order which *is* scheduled to arrive on Thursday is QWERTZ), I might be willing to swap, given it actually does come in blue.

Right, and that includes hope for a longer support with security updates.

That would be good if the user could decide for each app which keyboard mode it should use, but that's not how it is. In a browser, for example, I rarely find myself wanting the autorepeat feature, whereas I often need accented characters, and by tendency I find browsers using autorepeat mode instead of giving me the character selector. That said, with the Pro1 + LOS 18.1 I'm not missing the char selector box anymore, as I get all accented/umlaut characters I need with fairly easy-to-type Sym+Char combinations, but I'm sometimes annoyed when I would like to do autorepeat but get the chara

If you still haven't received one when all of batch #1 has shipped, you will have a reason to complain, and rest assured I will complain in case the phone I ordered in Sept 2019 won't come in batch #1, too. If you cannot contain yourself for the few more days that will take, all the more so after you have been waiting for more than two years now, your fuse it too short. And then tell us which other tiny, but "thriving" and "efficient" company has been denied an already promised supply of SoCs, making scrap out of their mainboard, in place of which they then had to create a completely new

You can email fxtec.(info@fxtec.com) I'm pretty sure they have some. Right, that's how I got mine (together with a USB-C module that eventually has become available as a replacement part, too, just on time before my current phone would completely lose its recharging ability) 🙂

My guess is, as I just wrote here, too, given that I now have received tracking info for my Oct 2020 IGG order (8/256 GB QWERTZ), but not yet for my Sept 2019 Pro¹ order (changed to 8/256 GB QWERTY Pro¹X), that they tried, at least roughly, to sort orders/perks into those two batches according to order/backing date, but didn't care for any specific order within the batches, as that would make just a few days difference anyway even in the worst case. Also, as some already said, F(x)tec might have no influence anymore on the sending order once Expansys/FedEx has taken over a pallet/container...

Would be really nice if we had one or two older generations of LineageOS officially supported in parallel at least for some time after the most current version became officially supported... Depending on how good stock Android is implemented this time and how well I get along with Android 12, I might actually stay with stock for the time being, and look forward to seeing whether Android 13 will impose more nuisances on us or actually improve things again for a change. (Yes, stock Android is 11; I suppose @Noob refuses stock Android for a different reason.) Good thing is I'll be able

In addition to In the end, for me only replacing the screen helped (in my case, Fxtec's replacement unit which actually is the complete upper half of the phone)...

For screws (M1.4x2mm is indeed correct) there are a few more posts with links to sources here. I've actually found those black ones nice enough to not bother anymore with stickers 🙂

After all that time it's more than understandable that we get confused about the exact year 😉, but I guess that should read 2020, as that was the year the Indiegogo campaign started? Anyway, good to know that notifications for first batch shippings are still coming up, and good to know that there definitely are a whole lot of IGG backers already in batch 1, too!

Hey, I thought I was the only one left with an order dating back as far as September 2019 😄 Or maybe destination region? There's no tracking info for mine (September 2019, qwerty) yet – which is supposed to go to Europe...

Just for the record, there are IR transmitter addons for android devices which don't have their own IR blaster: https://www.irdroid.com https://irdroid.eu

I guess for the Pro1 X the same applies as for the Pro1 (probably no external DAC, otherwise it surely would have been mentioned in the specs):

@EskeRahn Might make sense to pin these three threads, what do you think?

Right, and so far it looks like they're at least prioritising unfulfilled Pro1 orders over Pro1X IGG orders. (On the other hand, a few more days won't kill us, either, and at this point I'll be happy if and when I get the phone at all...)

Neither have I (September 2019). Looks like their shipping order is similarly incomprehensible as it was back in 2020.