Leaderboard

Hello! We just wanted to let you know that Pro1 production is well underway, and we expect to ship more units over the next few weeks. Continued restrictions on the movement of goods around China has resulted in some processes taking longer than anticipated and at slightly higher costs, but overall the situation in China is improving and we now have almost 100% of our factory staff back to work. This means that we can ramp up production as we work our way through the backlog of orders pre Covid-19. As always, thank you for your continued patience and support. Sincerely, Team F(x)tec

I prever vague statements instead of promises honestly. And even vague mails show that they haven't forgot us. Remember those "will be shipped before [august, september, october, november, christmas, new year, january, february]" mails which we got every month? I hated those. Now at least we know that we don't know when to receive it. This feels better than broken promises and expectations every couple of werks.

@v6akSorry, but how exactly was the information better back then? We have heard from them once a month (now almost once a week), were given immense promises (shipping starts at x, shipping is completed by x) and haven't heard of any problems until... well, until the deadline was passed and we got another delay. Too much information also inherets the risk that people leave the boat fearing that those problems will cost too much time. So it's a risky game to still provide us with some information. For me, this is better. I don't feel forgotten nor do I feel like they were lying

Actually no, I think in the serial number topic there was someone with 1k. I think what happened here is that most of my unit was "reserved" early due to my preorder but there was no qwertz keyboard available so it was put on hold. Or, qwerty and qwertz units are counted separately in production would be my other guess.

we expect to ship more units over the next few weeks. few - about 10-50

Thanks, moved your comment to the locked thread

Naturally, I would prefer the mail with the exact delivery date over anything, but I also thought rather well of this mail today: just the simple information, that production is up again, and rolling, not feeling forgotten. They're trying and working. To the people complaining about every step on the way: You got too much time on your hands. Keep in mind, you are waiting on a phone(non essential), not a kidney donation or heart transplant. Even when you have it, your life will not revolve around the phone 24/7, neither should it. I bought from a startup, I will try to be patient, may

You may try to rename .apk to .zip and open it using WinZip, WinRAR or Total Commander for example. Inside, there is a directory /res/raw, you can see the .kcm files there. For example, you can find the Hungarian layout in pro1_qwerty_hun_1.kcm or in pro1_qwertz_hun_1.kcm depending on the physical layout of your phone. The difference is the mapping at the top of qwertz version. If you look inside these files, their format is simple. For example, if you modify in "key 7" section at "label, base" the written "7" to "8", then save this file inside this .zip archive, then you have

Only if not even having the hardware counts as a hardware problem!

Dude, seriously get on this. It will literally take you 15 minutes to get this fixed with the fastboot files. Yeah sure it isn't official but I'd go nuts sitting on a bug like that. You'd be back up and running in no time.

On Dec 17 update it was told the production rate was ramped up. On Jan 17 Erik mentioned the batch was "6x bigger than the previous batches combined" and that they had produced 70% of the pre-orders. So 60% of pre-orders was produced in 5 weeks. While Fxtec cannot forecast, I can. Even at half the rate achived at January they should be able to produce remaining 30% of the pre-orders in 5 weeks. 🙂

Cause it could go faster.

Never did a reset since I got it in January. I'm actually using it 😁

Considering how often I've wiped the phone, nova's back up and restore feature is a God send.

For those that are curious, running the latest version of stock 202003. Safety net issue is fixed and in fact passes even if the boot loader is unlocked. Google pay works. Since I've been on Verizon via red pocket , my signal has been rock solid. Glad I made the switch. ATT stank to high heaven. @slion, can't you use the fastboot restore files to roll back to the October release and re-up date forward to fix your phone? Even the factory restore tool should work in that regard.

This is some next-level bad PR. Shame really. Apart from the shitty camera software and sometimes wonky Bluetooth I absolutely love the Pro1. Now if I could just get my hands on the rest... 🧐 Order Date Status Total Actions #238xx July 29, 2019 Processing €1,964.99 EUR charged at a future date for 3 items Deliver!!! #55xx February 28, 2019 Completed €667.00 EUR charged at a future date for 1 item

I only barely know a little Japanese from when I took it in high school. But you motivated me to figure out swiftkey, and yeah the only thing I had to do to change it to the way I want was not set it for hiragana. So I'm gunna update my table and first post, cuz Swiftkey seems to work great for Asian languages, the way I want to type them anyway. Certainly better than gboard with its popup boxes. But, Chinese works better than Japanese cuz have to use ctrl with the numbers for Japanese (like english) or tap the screen, which I actually found documented in settings, so it's not a

The source code you see at GitHub can be loaded by Android Studio and you can modify, then compile it. If you only modify a .kcm file then you will see its original name but when you use it, it will be your own layout, but the original name also can be modified in an .xml file. Basically the .apk file is a compressed image (.zip), so theoretically you can modify its internals - you may open an existing .kcm then you can modify it, but I don't know if Android will accept this modified file. You can not just drop the file into the filesystem unless you have root access, but another f

Their expected delivery is March 2021, so approximately a year from now. Yes - it looks to be an interesting product anyway, but as I heard, support of their older devices are not very good. I hope F(x)tec will be better regarding this. Same here, I hope they will have a Pro2 even if it is going to production after two years from now. I would also support F(x)tec if they keep this form factor, so a similar outfit.

March 2021 is their crowdfunding target date. And take those with a bit more than just a grain of salt. Not all Cosmo Communicator backers have their device yet either (though they have shipped more devices than Fx if you want to compare that). Hardware development is rarely smooth sailing. I'm fairly sure there will at least be a couple of more Pro1s shipped until then.

It seems to me the update frequency is inversely correlated to the production rate.

C’mon F(x)tec, I need another eMail telling me to wait just a little bit longer.

Every. Single. One. We have just accepted it as one of the things we have to live with. High pitch buzzing sound. It's godawful.

Though I like the versatility of Nova, I find that it really stinks in assuming the same grid layout in 1:2 portrait and 2:1 landscape. Here the stock launcher solution of seeing it as two (roughly) equally sized blocks, seems like a much more clever solution. A few launchers offers more or less independent layouts. That obviously has a lot of benefits, but means you will need to set things up twice. But most launchers (including Nova) that at all handles landscape take the lazy route of just squeezing and stretching the grid - apart from looking horrible, it also makes widgets more or less us

I think fxtec left two zeros there. I am now waiting 41 weeks since my pre-order and 40 weeks since my payment. I think it would be more realistic if fxtec wrote "Order your Pro1 today. Shipping worldwide in 40-60 weeks."

Yes, correct, only way to fix it now. An update is coming shortly (or was it next week?)...

I thought they were supposed to provide another OTA that's fixing it. I can't be bothered doing a reset.

If you enable Developer Mode you can force APTX or any other codec for that matter under developer options... Try forcing it, maybe it will succeed. It could be just a handshake issue.