Leaderboard

What the heck happened to delivering all pre-orders in January? If they just dispatch by that time we will only see devices in mid to end of February.... I am getting really sick of this. If I don't see a device this month I'll refund and be done with it.

Yea, the waiting is not much fun... Soon your life will be restored.

At least remove the hairs and give the screen a wipe on your shirt or something before taking a picture, please!

Then say Pro1 three times out loud (or once with a scottish accent)

As much as I love root access, I'll probably do without it for awhile on my clack when it arrives as it sounds like there's currently a certain amount of disruption in making it work. Perhaps @Waxberry will get the software people to add the root access switch in developer settings like LOS has. Not that this is terribly important, but I know I would appreciate it, and I'm sure I wouldn't be alone.

Nice. I'm (among other cables) still awaiting this one https://www.ebay.co.uk/itm/362332003394 And I hope it will be slightly more compact. The images/rendering are not that clear on the size, but it looks very compact.

https://www.fastcompany.com/90446946/this-wacky-smartphone-proves-why-so-many-phones-look-exactly-the-same

Okay so I bought this -> https://www.ebay.com/itm/Flip-PU-Leather-Magnetic-Card-Cover-For-Huawei-P20-P30-Mate-20-Lite-Pro-X-Nova-3/123548882300 I ordered one in black for the Huawei P20 Pro based on EskeRahn's website, but one that shipped to US sellers (and didn't look as maximally cheap as possible). The case arrived today, and I made the following modifications (pictures at end). It supports my use case of protecting the screen from scratches and hopefully some drop resistance, while getting out of the way for keyboard use or camera photos. Pretty, it is not, but I can n

Root switch would be convenient, though probably not allowed on Google's Android indeed. Magisk does more than just simply provide root though. On that note I'd like to urge F(x)tec to provide updated flashable images along the OTA updates or at least updated boot.img that can be patched with Magisk later. It appears to be not technically impossible to scramble together the image file from an intercepted incremental OTA archive and the initial image, but I don't think there's been success in this yet. Root is technically not an advertised feature like the alternative OS support, but I hop

I'm guessing the same thing that happened to delivering in July. Or 'Summer'. Or 'within a couple of weeks of payment'. Or early November. Or mid November. Or by the end of November. Or early December. Or "definitely by the 20th of December".

Every day I wait a small piece of me dies.

That review lives somewhere I don't. Shipping incomplete software? Wow when was the last time you got something which does not receive patches the following months? Sure most smartphones work great from the beginning, but they all have the same 3 components... The only valid point here is the FP sensor which is indeed horrible.

Just to complete with a follow up, the error was rooted in using USB 3.0 Port. As soon as @Astaoth used a USB 2.0 Port via a docking station, the flashing process worked as expected

Putting it in a bag of dry rice or using desiccant products won't require you taking it apart. They just make the air very dry, hence removing the water that made its way inside your phone. If something didn't short circuit and create physical damage, removing the water should allow it to work again.

Hurray! That's awesome! What a great leap in production 😄

Black Beauty arrived today:

Mine is 225.

Is it some sort of tradition to post cases covered in gross bits of dirt, mysterious white flecks, and hair? 🤢

Yes, I think there was one batch that didn't go to London first, but was sent directly to the European customers from our Hong Kong warehouse. We are legally required to pay VAT in Europe, which we already charged our customers for, therefore we are pre-paying the duty for EU-based customers. I am not sure if this is happening again though, as we'd likely continue shipping to London first and then to customers. Either way, customers are unaffected, and if there is a problem, let support help you with it - [email protected].

You know you can just paypal fxtec some money if you so badly want to go above and beyond to help them? Taking a net negative (waiting longer AND paying more AND giving them a zero interest loan in the meantime) is literally the same as giving them money, so you might as well just do that..... If you want to give fxtec the "absolute best future possible" just give them all your money. You can't put out absolute statements like that and then not follow it up. There is no line in the sand if you want the "absolute best future possible". Why not work for them for free, too?

For anyone else wanting to be able to intercept OTAs, here is what I've posted before. https://www.thecustomdroid.com/how-to-capture-ota-update-url-android/ At least one person was able to use the directions to get the URL: And here are the directions on how to flash it, in theory. The problem is that users have reported that we don't have a real recovery with the Pro1 and I'm not sure if TWRP is to the state where it can do this either. https://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/ And no idea what this would d

Bluetooth keyboards are THIS:

Had it been mine, I would open it and see how easy it is to disconnect the battery. But I'm a technician, If you are not familiar with electronics, have someone that are do it, and as @VaZso said, the faster the better, especially if there is a risk of salt or other minerals in the water. If the water is clean disconnecting is not a must, though still recommendable. My next step would be to see if I by a lucky chance could get to the water, and remove some of it with say a cotton pin, or e.g. a corner of a piece of toilet paper. But again it is delicate business, so important you know wha

I think salted water is one of the worst thing one can have inside a phone - basically because it conducts and it causes corrosion and that is the cause why you need to disconnect battery. If you are lucky, the phone may work after cleaned, but there is no guarantee if it will ever work again. So that is why I would disassemble it to disconnect at least the battery - so to have a chance for it to work again. Otherwise it may also "eat" the PCB.

e.g https://www.amazon.com/Replug-Breakaway-3-5Mm-Audio-Adapter/dp/B0013KXCMO/ref=cm_cr_arp_d_pdt_img_top?ie=UTF8

Have you tried any of these options? https://www.wired.com/2014/02/thats-deal-wet-phone/

1. Two settings are relevant to this: A. In settings there are slider settings, these are settings specific to the keyboard. One says force landscape when keyboard open. If you turn this on, it'll work for the majority of apps. B. In quick-settings, you can turn on auto-rotation. This works for more apps than the force landscape slider setting, but some apps are still forced portrait no matter how you rotate. C. If you must turn apps landscape that are forced portrait, use split screen to put them on half the screen. 2. I havent played with this but I think it

Yes it works fine and show me the serial number of my Pro1. For more informations, I have "fastboot version 29.0.5-2" and I'm with Archlinux EDIT : as some others have noticed, the compatibility is not good with USB 3.0 ports. With an USB 2.0 port, it worked fine.

Yes. That is the difference between real life and advertising images. 😇

I think I'll just stick with Pro1.

Here my attempt, with inner part removed, rotated and glued back. Note the uneven look of the inner back around the camera when opened for photo, as this part was previously glued to the back, before rotating. Cut-outs for buttons and fingerprint reader on one side, for 3.5mm and usb at the ends. Plus a cut for the secondary microphone, and finally hole for notification LED and speaker

Exactly this. So far (not tried to EDC it) so good.

So, not to sound like Grandpa, but how on earth does wireless charging help anyone and why is it considered desirable under any circumstances? I see absolutely no advantage to it at all, and some pretty serious drawbacks in efficiency and longevity, to say nothing of the high probability of massive additional EMR exposure at some point. What is it about wireless charging that makes some of you sad that the Clack doesn't do it, and what does it allow you to do better than what you could do without it? The adapter pad seems to be the worst of all worlds, in that it has all the drawbacks, but los

So clearly something is odd with the way it processes rotation information, perhaps a bug in the magic added for the keyboard slider. I'm certain that it's all in software and will be resolved in time.

https://www.travelchinaguide.com/essential/holidays/new-year/dates.htm "The Chinese New Year of 2020 falls on January 25th (Saturday), and the festival will last to February 8th, about 15 days in total. 2020 is a Year of the Rat according to Chinese zodiac. As an official public holiday, Chinese people can get seven days' absence from work, from January 24th to 30th."

Perhaps cheating was not the correct word to describe my feelings on the matter. Clearly you did not read my clarification....I'm not in the least bit upset that I don't have mine already. I understand exactly why they aren't here yet, and as such I'm willing to cut them far more slack than it appears they'll need. "All you did" was far more than "use an opportunity." You took money away from F(x)tec by buying through a reseller, who will keep a cut of the profit. You took away an opportunity for a member of the general public to discover the Clack, thereby taking away an opportunity to b

You do realize people's situations can change over time? When I pre-ordered in early 2019, my financial situation was different from when they asked us to pay in August. And I would've cancelled my order if my friend hadn't offered to lend me the money. And even now my situation is different from back in August. That said: I'd rather cut back on other things than not have a slider keyboard phone. I've been waiting for this for a decade. I imported and used outdated US phones in the past because touchscreen keyboards are a nightmare (for any kind of purpose). I used the Galaxy S4 with a BT

I just hope that referring to the phone as "the Clack" never catches on.

I'm a bit confused. I just downloaded the 20191028 file successfully. The index links to the LineageOS page and the Factory Restore page. But if you followed the link in the OP of this thread you should land on the Factory Restore page directly. The links for all the restore files are there and should be working.

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.

Agreed and agreed! Having a tool like this is a huge plus and something worthy of much gratitude. Fantastic! What a bonus!

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 flash

I agree. The situation is not seemed to be unfixable or really hard to be fixable. Sending back for guarantee is not a good decision. Maybe selling the device is or to find a service person who has more patience or skills to do the well-described steps. ...but doing this while somebody is trying to help and definitively not stuck somewhere is also not a good decision...

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 un

Wait, what?!? What shop? Where you bought it? As in you returned it and are done with it for good, or is this just temporary? I hope it's temporary as @tdm was/is working diligently to get this corrected for you, and the solution might very well help everyone. @tdm I have been watching and reading this issue with interest, as always thanks for all your support!

Well, I am looking at the programming files and it shows that it's writing both xbl_a and xbl_b from xbl.elf. So that part should be good. The files themselves should be good, I have flashed my device with these bits on multiple occasions. So I am a bit confused why this isn't getting you to the bootloader. You should at least get a splash screen no matter whether you hold the volume key or not. I've updated the full firmware package on my website to use the older, working programmer. The new md5 starts with 6b0... You can try downloading that instead of

Okay ... according to the device I have here ... root@QX1000:/ # ls -l /dev/block/by-name/ | grep sdb lrwxrwxrwx 1 root root 15 1970-02-09 03:12 xbl_a -> /dev/block/sdb1 root@QX1000:/ # So /dev/sdb contains xbl_a and nothing else. This is the second stage boot loader for slot a. So you did not overwrite anything that cannot be easily replaced. But xbl_a should have been flashed by the package that I sent to you, and that should have allowed you to get to the "upper" boot loader ("abl", or fastboot). Can you

Okay that helps. Let me investigate a bit and see what is on /dev/sdb. Let's hope no radio configuration lives there.

Okay that works for me. I have limited time myself until January 6.