Leaderboard

Don't run the fastboot flash lock over terminal and then use the volume keys to turn the bootloader lock back on. Update: The FxTec team has graciously extended a helping hand. Also, I'm working with TDM to help determine what's wrong with his factory reset tool before I utilize FxTec's assistance. I will update this thread soon with the outcome.

As my engineer friends like to say, the job of an engineer is to make stuff that's idiot proof and the job of the universe is to make a better idiot. In the case of this, the universe had a small victory. This is the tool: http://files.nwwn.com/android/pro1/factory.html This all started because a food truck I wanted to go to was only accepting Google pay. I relocked my bootloader while running LineageOS (using fastboot flash lock ). I was going to flash back to stock after I did this. However, after doing so the bootloader (screen that says START) on it would not

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."

Well the revamped website still says shipping in 4-6 weeks if you order now, so you should have it soon!

It's finally here

🙂

Hi SailfishOS community port has been updated to 3.3.0.16 and is available in the testing: repository for general use. The testing: repo is for general users, and the devel: repo for devs...the initial SailfishOS releases were made using the devel: repo so you need to switch them or install a release built from testing: If anyone needs to know how to do than then ask. Update process is as always: devel-su ssu 32 3.3.0.16 ssu ur zypper ref zypper dup

Sad, thought those bugs were ironed out. But thanks for reporting. Let us hope they are reading @Erik @Waxberry The fix is to use FinQwerty and select "German for physical qwertZ".

I thought somebody did manage to get the launcher apk at least. But then you'd still not have the source code.

Can you pack the launcher with a backup program maybe? That way you could use it on LineageOS and other systems

Bump! F(x)tec is advertising the Pro¹ with "LineageOS"-Support. Well, ok, I flashed the test build of LineageOS, but F(x)tec should _really_ open source their launcher!! (...and publish it at F-Droid or submit some code to Lineage's Trebuchet, if they want to adopt those features.) Damn it, what's wrong guys?!

No. But stock could at least pull in all the lineage fixes/etc fairly easily.

Hmmm, I've got something today 😊

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

Yes, I wanted to do that anyway, thanks 🙂

Did someone find a good solution, that doesn't take 2-4 month to arrive? I recently recieved my phone and experience the same rattle. Honestly (despite the company saying otherwise) that is not normal. If I hadn't been following the forum here and thus knowing about the easy fix, that would have been a reason for me to ask for a replacement immediately.

It seems that OnePlus 8 models with curved AMOLED screens are also suffering from this issue. They have screen panels made by Samsung. OnePlus 8 Pro pre-order units reportedly have varying screen issues OnePlus already fixed the issue (and accidentally touching issue with curved screen) partially with recent update. OnePlus 8 Pro OxygenOS 10.5.5 update brings partial fix for 'green-tint' screen issue, plus touchscreen sensitivity tweaks Funny thing is that DisplayMate didn't notices any issues in its review. Maybe they had fully working unit or they do not test

You can read through the older discussion of this here: Exsum is this is a known bug that hasn't been fixed yet.

If safetynet is required, the ONLY solution is unrooted stock. This is the new normal. For the past few years this could be worked around with magisk, for both root and custom rom, but no longer with latest google updates. https://twitter.com/topjohnwu/status/1251712525843918853 So this is even more reason for us to want stock to fix problems/issues. I mean the community buglist of issues https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y hasn't changed since last year, other than the March multiple-keypress fix which was a very important and w

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

@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?)...

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

Already bookmarked me some 0,5mm silicone tape in case ever get my device 😆 I would rather use something with a closed surface that is less likely to accumulate particles. It seems to be an easy fix that should be implemented at the production level for future runs. Just look at the E7 some more. That one didn't rattle so fxtec can get there too.

Will report. But I fear the 1mm is too thick, unless it is very soft. (I ordered it for experimenting with self adhesive bumpers)

Only that I do not know where to get it just as thin/soft. 🙂 But sure should technically be expected to be more durable, and easier to keep clean. ADD: I already ordered some 1mm neoprene adhesive, but it has not arrived yet, so do not how good/bad it would work. https://www.ebay.co.uk/itm/223689641795

Did factory reset and that helped for a day or two but now again woke up to the phone caught in a boot loop. Gets about 3 seconds of functional time after booting and then freezes and restarts. EDIT: OK so disabling wifi in that 3 second window managed to keep it from rebooting immediately. Phew. I was also on 2.4ghz band. However I still don't understand why it would spontaneously turn off and reboot for no reason after running fine for hours and especially when inactive at night.

Not sure if it was reported already, but when having selected the German layout for the physical keyboard in the system settings, yellow arrow + some keys does not work as expected. arrow+l gives ? instead of ' arrow+ö gives ö instead of \ arrow+ß gives ß instead of ? arrow+e gives e instead of € arrow+r gives r instead of °