Leaderboard
Popular Content
Showing content with the highest reputation on 01/02/2020 in all areas
-
Just received a tracking number! Very cool and VERY hyped! My order number was in the #48xx range, payed on august 1st. For everyone still waiting: Please bear it a little while longer, it is definitely coming!10 points
-
Also received TN! QWERTY, #48xx and paid 31.07. Also hyped again :)8 points
-
It's arriving today, we called UPS this morning. They delayed it because of Christmas and then New Years, but it's definitely coming today. Worst case we'll send the tracking tomorrow, but we're aiming to send the tracking for the small batch today.7 points
-
Got my TN view minutes ago. Great news! QWERTZ Slider, #49xx and IGG coupon user. Looking forward to this great phone! Very happy to see the phone is on it´s way I really cross the fingers for all of you to have them in the next view weeks in your hands. Pretty sure f(x)tec is working on it as hard as possible. Hope everything will now go a little smoother than the last view months and we see a great future for QWERTZ/Y Slider!6 points
-
I find it perfectly believable. All it says is that is what they AIM to do. I AIM to lose weight, stop drinking and generally be a less cynical b*****d in 2020. The evidence of my last n decades on the planet is that this isn't going to happen either.5 points
-
Regarding the "Keyboard Lost" issue, we have worked out a test OTA for the fix during Christmas, and internally tested. Because this happens very randomly, and not always caught by internal team, we have asked some users to help verify if the fix work. (Many thanks to @TeZtDevice ) and the issue seems to be gone. The fix is working. However we would love to invite more users who constantly experiencing this issue to help verifying if the bug is completed fixed. Please let me know. (There is a risk of test OTA being incompatible with future official OTA so reflash might be need4 points
-
4 points
-
3 points
-
As of my Pro1 again. Yesterday I put on a "BROTECT" screen protector bought at protectionfilms24.com and I cut another protector bought at bestskinsever.com to fit the back and sides. I feel it is more comfortable to use the phone now because I was afraid I will hurt the device somehow and now I feel it is somewhat protected. I hope some pre-cut full-body protectors will be available after a while, but I feel convenienced with end result. The cutout near camera lens and noise microphone is not perfect, but still I feel it is much better that way. My back panel has a metallic-co3 points
-
I tend to think Chen wouldn't have put this out there on his personal twitter unless he was very sure. But, sure, no one knows. There have been a flurry of TNs this morning, as promised, probably the small batch Erik referred to.2 points
-
On the 11th Dec I requested a refund, after a number repeat requests, my money was eventually refunded 14 days later - one day before the bank said they would start a recovery procedure! ...So one of you lucky people may get a phone ahead of schedule 😉 If F(x)tec survives this farce, I may see you when the product goes retail and has a hard case. TTFN2 points
-
Chen said on Twitter that the small batch (I suppose) should arrive to F(x)tec office in the 1st week of January. So customers could expect to receive their unit next week. https://mobile.twitter.com/chenliangchen/status/12105193798274048002 points
-
My web page answers that, mostly. There are situations where the device must be disassembled to enter EDL, but they are exceedingly rare. Almost always either the PBL will fail to load XBL and panic to EDL (this is what devyl 's device did), or XBL will load and check for the data short on the USB connector that the EDL cable provides. So really you only need to disassemble the device if XBL is functional enough for PBL to load but not functional enough to make it to the USB check.2 points
-
Page load really is quick, much faster than with the Sailfish Browser, and it can handle up to ten tabs with no memory issue. Scrolling is fast, sometimes too fast, you have to be more gentle than with a mobile browser. Most of all, the video shows that I can operate tabs and navigation just from the keyboard (new tabs, close tabs, focus address field, reopen tabs, switch tabs, previous/next), which not only feels great, but also is very efficient and faster than anything else I could imagine on a phone. Coming back to the Sailfish Browser really feels painful just when I need to open a tab or2 points
-
Oh, and just so everyone knows... This tool and the linked factory packages are meant to do a "normal" factory restore. It does not, by design, reset every single bit that the factory programs. For example, it will not reset the frp partition which contains the boot loader lock flag and the Android factory reset allowed flag. Nor will it reset the radio parameters. Etc. I wrote this tool and I have full access to the underlying capabilities of the programmer. If a normal factory reset does not work, I can generate packages to read and write every single bit on the flash2 points
-
I'd like to expand on this a bit. If you screw up your device then you are responsible for fixing it. Returning the device to the retailer is bad for several reasons: (1) you screwed up and you are making someone else eat the cost of your mistake which is not cool. (2) the retailer has less incentive to stock the device (and any non-mainstream device generally) because they are seen as less reliable and thus less profitable. (3) the reputation of FxTec suffers. So resist the temptation to take the device back and claim that it "just stopped working". Not only is it un2 points
-
Please note, this is not an official FxTec tool. It is my own creation. FxTec should not be expected to support this tool or any damage caused by its use. This tool will allow you to restore your Pro1 to a factory clean state no matter how badly it is messed up. You may use it to restore a "bricked" device or just load the latest firmware. You can find the software and detailed instructions here: Factory Restore for FxTec Pro1 Please report any issues here.1 point
-
I have searched high and low for the mass of the Pro1, and as far as I can tell F(x)tec has managed to keep this a secret--until now! Here is a comparison of the pro1 vs some other similar phones: Pro1 - 244g Iphone 11 pro max - 225g Priv - 192g N9000 - 180g Iphone 11 - 181g Droid 4 - 179g Elephant U - 166g G1 - 158g1 point
-
You will have to unlock it, according to this post.1 point
-
I haven't used (nor even purchased) the Pro 1; but I've used about a bazillion keyboards over the decades and never found that any of them took more than a few hours to get used to. Usually a lot less than that, truth be told. I guess part of the reason is because I was an on-site computer/network tech for a long time, so I used a lot of devices. You get pretty good at shifting gears. The old-school BB keyboard was my favorite because the smile shape and other tactile cues seemed to aid muscle memory acquisition. But I can't say that I "hated" any physical keyboard on any phone I've ever1 point
-
I'd like to believe this, but I cannot any more. Too many missed hopes & promises; as per another thread I've now been refunded. The last straw, for me I'm afraid, was selling to resellers. Then seriously expecting us to believe they could massively scale up to complete ALL pre-orders in a matter of weeks, over the world's biggest holiday period, when they've taken months to produce perhaps only a few hundred so far. So I will wait to see if & when Clove are restocked, & then decide if this long over due handset is worth it anymore....1 point
-
Okay, that was weird. Noticed this morning that my phone wasn't working. No calls, no texts, etc. It occurred to me to try what @EskeRahn suggested above, but when I went into the phone menu, I discovered all the switches had been turned off. I switched them back on and everything is fine. It's tempting to think this was some side effect of rooting, since that is the only change I have made lately. I'm not sure how (these hidden settings are stored in boot sector?), and to be clear it may be coincidence. However, I would prefer that to be the case rather than "There's this weir1 point
-
My guess is that the batch is so small that UPS lost it down the back of the sofa over the holidays.1 point
-
That's how I feel. I tend to keep phones for a long time, so I want them to have bleeding-edge hardware when I buy them. A two-year-old chip effectively shortens the device's useful life by two years. On the other hand, an easily-replaceable battery that doesn't require breaking the phone in order to fix it is a powerful plus that I am balancing against the 2017-era chip in deciding whether to purchase this phone. The 6 GB of RAM is also a plus, but 8 GB would have been more so if it were powered by an 855 or 855+. The unlockable bootloader is also a plus, of course, even though I pr1 point
-
1 point
-
1 point
-
I have tried HDMI output, it also works well. I have tried two adapters: - This one works for screen sharing but no audio going through - This one is more than a HDMI output but audio also going through HDMI here, USB ports are working, I have also connected a power supply while a video was playing on Youtube and it could also charge the phone (but only with 5V, so no Quick Charge this way). However, LAN interface is currently not working (maybe appropriate kernel module is missing). (Currently it is a bit more expensive than it was earlier but it is also not a cheap device - I th1 point
-
I think there is a deeper worry beneath this: The fear of this being the last real slider keyboard phone, perhaps forever, and not unlikely for many many years. And If so, the newer the specs at launch, the less outdated it will be in say 10 years. Many of us are replacing really old phones with the Pro1.1 point
-
I finally got around to doing the steps listed in the OP and it worked flawlessly. I'm now rooted with Magisk. Thanks, @Craig1 point
-
We can still draw the conclusion we are a jolly bunch of pollclickers :).1 point
-
FYI, I have imported the Pro1 FinQwerty v1.5.1 key character maps (kcm files) into my LineageOS builds. If there are other kcm files that people have worked out for the Pro1, I'd be happy to add them as well. The current FinQwerty maps add support for Czech, Danish, Finnish, Norwegian, and Swedish, as well as the alternate German mapping. For reference, you can find the patches required to add additional kcm files to a device build here: https://github.com/mccreary/android_device_fxtec_pro1/commits/lineage-16.0/AsantiKeypad The last of the three is not necessary for the stock Pr1 point
-
Yeah it is horrible, the outsourcing of work into captchas is becoming more and more aggressive. Mine was even worse:1 point
-
AT&T works great (Pay As You Go). I used them for years and had no trouble. Actually kind of happy to be back with them.1 point
-
QED. This is for some unconditional fans around here or some species without principles.0 points
-
So FxTec is shipping phones to non-IGG preorders AGAIN? Before fulfiling IGG preorders (such as mine, I'm sure there will be more people). @Erik, do you care to comment on this?0 points
-
I also did not havve an IGG coupon.0 points