Leaderboard

It's finally here

🙂

Contact us at https://www.fxtec.com/contact-us and we'll see what can be done.

Got my phone on Monday, but I have been super busy. Just now I have started to set it up. Tbh, I am little surprised that it even arrived 😄

Hmmm, I've got something today 😊

I think your first idea is good. Make it an Anniversary gift. It should make it in time... Although I think Independence Day is more likely than Memorial Day.

Have you tried fastboot continue? Or fastboot update? If I remember correctly it's important you flash a file with the same version bootloader that you have on now. Otherwise I suggest you try these: https://forums.oneplus.com/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ Helped me twice with different phones, with their corresponding drivers and files of course... Good luck!

@Slion could you add your app to F-Droid? Thanks.

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

Bumping this thread. I am not able to get the factory reset tool to see my device. Do I need a special cable in order for it to see it? I am in bootloader mode. Edit: I don't know why this isn't obvious, but to enter EDL mode from the bootloader you need to hold both the volume up, down, AND power button. The device will reset to the logo and then a black screen. The factory reset tool will be able to work then.

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.

I have the following problem on my fresh out of the box Pro 1, and I was wondering if it was just my device: When the slider is closed, so using the phone like a keyboardless phone, there is a physical click sound when tapping on the screen, especially the left and right hand sides when in portrait. See this short video I made demonstrating the problem: I'm not talking about haptic/vibraion feedback, as I have that disabled and anyway it does it when the phone is off. The problem seems to be the slider mechanism pivoting or wobbling such that the screen part bangs

I honestly think it would be a good idea to certify lineage, as that is getting way faster updates.

Pre-Order: August 19, 2019 Really, really, really been trying to be patient, and I know a lot of things have not been within anyone's control, but wow! Was hoping to replace my wife's Priv(as she is adamant her phone must have a keyboard) which is now really starting to get in bad shape, First as a Anniversary gift Then as a Halloween gift Then as a Thanksgiving gift Then as a Christmas gift Then as a New Years gift Then as a Valentines day gift Then as a St Patricks Day gift Then as an Easter gift Then as a Arbor Day gift

From what I have noticed, the side without the second arm is not as firmly fit (or because the upper part is supported by the other arm) and that's why the clacking happens. For me, when the keyboard is open in landscape upper left corner is completely still, but right corner is able to move just a little to make clacking noise. For me it seems like that the fit between the bolt holding the arm in the screen and arm in the base could be more finely tuned or the second arm should also exist in the bottom to generate more pressure to keep the screen balanced. Since the spring really do

Thanks Erik.

Welp, after reflashing with the factory reset tool several times, the device is still soft bricked. I am sadly unable to boot the phone. Makes it to the bootloader and won't make it past it. For future reference people, DO NOT RELOCK YOUR BOOTLOADER IF YOU'RE RUNNING LINEAGEOS! If there's anyone smarter than me out there with tips I would appreciate it. Looks like i'm going to have to roll back to an older phone. @tdm do you have any suggestions for this sad soul?

They are, I believe. I think Craig simply meant the only way to get safety net now...

Alas no, we are waiting for a TWRP that can decrypt first. Until then TWRP is only really useful for SFOS users.

EDIT: The cause of the problem has been found: Original post: monitored couple game sessions with KFMark and noticed that Pro1 has indeed some issues with gaming performance. The phone cannot keep up steady FPS during game play because CPU freqs goes up and down all the time. To me it looks like issue with kernel settings rather than throttling. Here are few gameplays compared to the Redmi Note 4 which has much weaker CPU. Both have FullHD(+) screen so results can be compared. Light game: Subway Surfers F(x)tec Pro1: average 52FPS (limit 60FPS) Redmi Note 4: av

Your are one Year old now, I was hoping you d have grown up a little more, to a shipped order, or even a received order. But you are just a Pre Order, you can't do anything by yourself, and sometimes i really wondering "What s the Point". Fx Tec, got me last year with their news about OTA update, I told my self, wow those guys are really pros. I think you all remember this one: Then came most fraudulous email ever at the start of August And yet I fell for it and paid... Shipping in early September, what a joke, now you can tell it, when you got all the money

Glad to hear. Though we (now) know that you did not need to take the hinges apart in the first place. So will be easier for the next one that needs to open it. 😉

No, there was a need for a screwdriver and a prying tool for what I did. The keyboard is glued, but I didn't feel the need to go into it.

It's definitely the Snapdragon 835 CPU. The sound issue is a bug with the system forcing a power saving rule as investigated below. This is at the top of our list for the coming update/s.

Well good that you reported it, and the more details the better. I'm not in anyway saying that they by optimisation wenot could extra out of the hardware. But I think they are more than busy with fixing bugs & malfunctions, so the easier we can make it for them to narrow down where there is an optimisation needed, the more likely it is to be implemented. It could be as simple as some code left in a debug mode somewhere, that uses/wastes time on logging, or it could be a complex thing needed. And worst case it is a limitation with the screen hardware/interface. So the more it

Yup. As I usually say: Every £1M spent on a device selling 1M pieces is just £1 each, but for a device selling 10K it would be £100 each... And this goes for development and optimising just the same... And this is also why we should not expect massive ad campaigns at e.g. super bowl... So everybody should spread the word to everybody they think might be just a little bit interested, or might know one that is... The best chance of this being a success is if the info on it spreads viral.

Great success! I have a linux box in the basement, and it was able to fastboot flash on the first try. Must be some software or driver issue on *both* my windows machines. 😞

Yeah I just flashed my device using the latest full image (October 2019) from the factory reset tool. Still no dice. Bootloader won't let me boot. I'm going to try once more with the original October flash image. But if it doesn't work, it seems I have ruined my phone for good.