Slion

Ho wait that's only an issue when the keyboard is open. It's like the task switcher still thinks you are in portrait. Not an Android bug then but really a bug of LOS for Pro¹.

That's indeed no an issue when using navigation buttons rather than navigation gestures.

Is it just me or the fact that they swap the task switcher direction between landscape and portrait is very annoying. When in portrait to scroll through your tasks you drag vertically, do that in landscape and you close your task. Who the hell comes up with ideas like that at Google's Android. Moreover the way they capture the preview screenshots for the task switcher is rather useless in landscape. I'm in a ranting mood 😁 LOS 18.1 is awesome so far but it looks like it's going to take weeks of bug fixing to get it as useable as stock... That's kind of why I postponed flashing i

Another major issue is that when the keyboard is open and you focus a text field in a browser for instance you get a useless band of empty screen at the bottom, that's possibly not an issue when not using navigation gesture. It looks like it tries to show an empty navigation bar. That one is pretty much a show stopper for me as it prevents proper use of keyboard in browsers. Chrome, Firefox Klar/Focus and Fulguris are all affected. How do we report bug for LOS? Do they track those on GitHub somewhere?

Spellchecker in browsers not working there either… Well I only tested Fulguris but I'm going to assume that's the same in all Chromium based browsers like on stock. This is so weird how could have this bug carried over from stock to LOS, does not make much sense to me. At least there is hope this could be fixed in LOS I guess.

Amazingly this is also an issue on Lineage 18.1. https://gitlab.com/LineageOS/issues/android/-/issues/3878

Can't find Netflix and Disney+ on Google Play. Assuming that's an issue with SafetyNet. How can I sort this out?

Thanks already up and running, awesome!

The LOS installation instructions are pointing me to this gapps but there is no 18.1 version. Any tips?

Fixed it! Thanks @_DW_ for pointing to Google's USB driver. It needs to be installed, however you also need to modify the driver INF file so that it lists Pro1 as compatible. Since you modify the INF you also need to have Windows setup in test mode so that you can install unsigned driver. Thankfully I had that enabled already as I've been working on some Windows driver implementation lately. You need to add the following lines to the INF file [Google.NTamd64] section (assuming you are running Windows 64 bits): ;F(x)tec Pro1 %SingleAdbInterface% = USB_Install, USB\VI

Eventually trying to flash LOS on my Pro1 and I have that same issue. Device shows the bootloader menu but no device are listed by fastboot. Busy trying different ports without luck to far.

Your expectations have just been fulfilled. This is delays until the end of the year. It looks like they don't have a fully assembled device yet. They are just saying they will assemble the first prototypes late August, more likely in September I guess. We would be lucky to get the first devices to customers before the year is over.

@claude0001 I'm still on stock but I'm once again considering trying out LOS. However I would like that LOS device to be reliable. Then I see the current official 18.1 build possibly has some issues with battery and keyboard apparently... so your 16 build seems tempting however being based on Android 9 I'm assuming it still does not have proper dark theme support and built-in gesture navigations which to me are major motivations for switching to LOS. Also, from what I gather, if I am to settle for LOS I may have to modify the keyboard driver as implement by @tdm and that means doing my ow

@claude0001 Why do you stick to LOS 16 which is based on Android 9 which is the same as stock? What about 17.1?

That's to be expected if you are looking at the LOS source code cause that's hard coded in the driver.

My understanding is that neither Fx Qwerty nor FinQwerty are working on LOS cause the keyboard driver has been significantly changed, notably modifying scan codes.

How long have your been using your Pro1 for?

That's a good deal.

@DesSuburbia Yes there has been QA issues with Pro¹s. I got to unbox three of them. One was DOA with keyboard short circuit, one had the touch screen fail within 6 months and one apparently works but is mostly sitting in a drawer. Luckily with two broken devices I could assemble a fully working one which has been one year in daily use without failure since I replaced the display half. If I recall well FxTec took 10 weeks door to door (Germany-UK-Germany) to repair the one device I sent them. I'm not surprise they forgot about your device. Typical for start-up having to deal with logistics

I've been using mine as my daily driver for 16 months now. Though having a backup phone is good advice no matter what you use as you primary device. I have other devices I can use when I'm home and I do tend to avoid using Pro1 when doing long video calls as audio quality issues can too often get in the way.

I thought those were genuine albeit expensive. I think that guy was just clever to invest in a batch to resale them. Don't blame me if you get swindled though.

That should work from Android 10 so I would say yes. I never tried LOS myself though.

There is no 8gb version at this stage. This is just a Pro1 with blue casing.

We do know they had plans for an Android 10 upgrade before the SoC changed. My guess would that they just won't have the resources to do that now, but you never know, the very existence of our Pro1 proves FxTec is very resourceful indeed.

Don't you get auto updates then once MindTheGapps is installed?