Hook

It also helps explain why they had said Quertz were for Europe only. The US fulfillment center will probably not receive Quertz models. This makes a lot of sense. Everything I've ever ordered from the UK has been shipped to me from a fulfillment center in the US, including my subscription to MOJO magazine. ;-)

At least I hadn't seen that on the forum before. Seems to be a nice easy way for direct contact. Also new links at bottom (again, at least I hadn't noticed them before, but I'm not always on top of things) including a Term Of Sales Link which has interesting information including the fact that we have 14 days after we get it for buyers regret. I don't plan on having buyers regret, but is good to know it's there. Nice to see these things popping up (though it may be old news by the time this thread gets moderated :D).

They had said on the form to request the change to quertz that "QWERTZ keyboards can only be shipped to European addresses.." I didn't want one, I was just checking the form (being curious about most things), but I thought that was odd. The only thing I could think of is that the phones with qwertz may be being made and/or shipped from a different location that is being hit with tariffs. Apparently they are willing to accept orders from the US after all, but there is a penalty. I don't clearly understand why all the US phones aren't being hit with this. Not that I'm unhappy there was no Trum

This almost sounds like a particular Bank with it's own quirks. As I said earlier, Bank of America (Visa Debit) was just fine with the F(X) Tec purchase once they had determined I really intended to make the purchase and it wasn't fraud. The Bank in question may possibly be more rigorous than most big bank systems. Obviously, I'm in the US.

The page won't tell you why. The F(X) server doesn't really know why. Contact your bank. Once they clear it (unblock your card) it will go through fine. At least that's what happened with me.

I am 12xx and only got the notice a couple of hours ago. These emails are apparently being generated number by number and not in large batches over the 48 hours. It's coming.

Yes, indeed. Tried both cards and both failed. Called my bank and both my cards had been blocked for suspicious activity. Lol. Bank of America is a bit of a nanny bank anyway, you have to tell them when you are going on any kind of travel, but they do offer $0 fraud protection. Got it straightened out and got my order in and my cards unblocked. Life is good. ;-)

Yes, that's fine. I probably overinterpreted your phrase "with known bugs." No, I don't expect perfection, and certainly no device I have used has had anything close. Glad to hear that your test unit is stable.

I'm wondering if there is a control in the forum software to set up time based rules (e.g., can only create 1 new thread per 24 hours, can make only 3 replies in an hour). It's a much less intrusive limitation, but would likely turn away most robots. Just a thought.

I seriously hope this isn't the case. I think it would be bad if they started releasing buggy devices. They are much better off continuing to delay until they get things pretty stable. There will always be a bugs that pop up once you get a large number of users, but you want as finished a product as possible for your first impression. I'm willing to wait, just keep me informed. :-) Just my 2 cents.

It wasn't a keyboard phone, but I loved the trackball on my Nexus One made by HTC. That was one beautiful phone. Lasted me 3 years, but had a serious design flaw almost guaranteeing the power button would fail and it was a very convoluted DIY repair (HTC never owned up to the flaw). However, that trackball was amazing for precision cursor control. Thanks for bringing back the memory. :-)

For what it's worth (and I'm not arguing that they shouldn't give us a definitive answer here or in a newsletter), Chen Liangchen answered a recent query on the Facebook page with "[The F(x) Tec Pro1] is compatible with Verizon."

No, early September can be as few as 4 weeks (give or take a couple of dangling days) from the end of July. ;) Look, the original was written at the beginning of the year as what they were hoping for at a point where they really couldn't make accurate projections. Even with this new estimation, they have rightly qualified it with "anticipate" and "expected." I am confident they are going to get them out as soon as they can with the quality they want. I'm also sure they won't ask for money until they are sure on the delivery, whether it's 3 weeks or 6 weeks. As long as they keep me updated

I would imagine most folks would volunteer to beta test. Myself included. I imagine the form they said they will send will have the sorting variables. Region (they might want a sampling from different regions)? Experience/Technical knowledge? Use cases? Random drawing (lol)?

They say in the specs "5.99-inch 2160 x 1080 (FHD+) AMOLED" If I'm not mistaken, and I could be, 2160 is the vertical resolution and 1080 is the horizontal resolution. (assuming portrait orientation here)

It's AMOLED, so I think you will get what you want.

No, that location (order status) has always said that, I was talking about the pre-order page where it changed from July 2019 to Summer 2019.

No, it has been changed to "Summer 2019." Doesn't seem all that dire a change. Could it slip further? Sure. But how about we wait and see if it does. ;-)

I was thinking he was actually hoping for a happy July... as in the release of the Pro1. :D

I understand the concern with the dying phone, but I'm not sure why people (this is the second post to do so) are concluding in late June that the phone won't be ready until next year. They only changed their delivery date from July to Summer. That gives them until 20 September. I think software and hardware refinements and integration are hard to nail down to a specific month, but I think it's too early to make such a dire prediction. I do agree that communication is lacking but I believe they are working hard and they haven't asked me for any money so I'm willing to give them the benefit

I can't quite figure out this sudden leap to "it's not going to ship this year" when it is only late June. Yes, they aren't the most communicative-- they aren't big enough to have an actual social media person. My Nexus 6p has decided it's time to do the spontaneous shutdown stuff and so I have picked up a $99 Moto G6 from Google Fi to get me through and then become a back-up phone. Most of what I do can be handled by a mid-range phone for now, so I'll be fine for a few months with the G6 if need be. If the Pro1 doesn't happen, I'll probably end up with a OnePlus 7 Pro, but I'm actually

They followed up with another tweet to explain a bit: Hi guys, just in case you think you're missing an email from us. We emailed only our Japanese pre-order customers on Sat, all tickets were taken within 36 hours. If any other Japanese customers want to see the Pro1 we will be in Tokyo for an an extra day. Email us info@fxtec.com I wonder if they will selectively email by region for the others as well. I hope not-- I agree, I like to know about these things even if I can't attend. :-) It's just nice to know things are going on.

There's also two kinds of "updates." There's the OS, Android P, Q, R, whenever, and then there are security updates (probably more accurately termed patches). I honestly don't care which version of Android I'm "stuck on" as long as it works smoothly with my phone. I do care about getting security updates which should be almost Android version agnostic. At least I suspect so because, thanks to the Lineage developers, I am still getting security updates for Android 7.1.2 on my 5 year old Samsung TAB s tablet (all LineageOS, not a stitch of Samsung software on it). It has on it right now the

Yeah. I actually like the fact that they were transparently cautious (as opposed to cagey and elusive), not promising more than they knew they could deliver right now. Clearly their intent is to update as far into the future as possible but they were clear that it depended on not just them, that there were other variables in play.

For me, posting the link makes the tweet show up in the post. Here, I made a screen shot of the tweet. Let's see if this works in the forum: [attachment file=18021]