Leaderboard

Yes, you can. I'll list the general steps below, let me know if you have any questions: 1. Unlock bootloader first by following the guide here. 2. Then, flash the GMS-less recovery.img by doing: adb reboot bootloader fastboot flash recovery recovery.img 3. After that, reboot your Pro1-X to recovery mode. On dead Android logo, use button combo : Power + Volume Up adb reboot recovery 4. Use Volume buttons to navigate the menu to select "Apply update from ADB", and use power button to select. 5. We will now use ADB sideload to flash the "“merged-qssi_bengal-ot

Would be awesome if FxTec could offer a setting selecting Full and Alpha, would be totally acceptable if a reboot was required after changing. With a switch people can choose what they prefer. IMHO both have their Pros and Cons, so would be great if each user could choose what matches our needs best.

..., complaining the fingerprint configuration would have changed although it hasn't, disable developer options and try again. For me, it seems to have done the trick with the Pro1X on stock Android 11. (I was suspecting a device-specific issue, although my Pro1 did behave similarly for some time, and if I remember correctly a reinstall or upgrade of LineageOS fixed it. Anyway I thought I'd send my bank a message—ING, Germany's biggest direct bank—complaining that their app cannot really be used with the fingerprint scanner, making it a nuisance to work with it. Two or three days lat

I'm having the same issue, and it looks like a bug in the firmware. I had already reported it, let's hope someone is taking care of it. Here's a sample stack trace from logcat, that nicely shows how a filed mUiMode is not properly initialized when a new DisplayLayout-Object is created: 09-13 21:27:20.823 2872 2872 E AndroidRuntime: FATAL EXCEPTION: main 09-13 21:27:20.823 2872 2872 E AndroidRuntime: Process: com.android.systemui, PID: 2872 09-13 21:27:20.823 2872 2872 E AndroidRuntime: java.lang.NullPointerException: Attempt to read from field 'int com.and

Much can change in peoples live in a couple of years. I see nothing wrong here - there could be a large number of different reasons. Though as being one of the many still waiting, I can envy those that got it, and feel frustrated that it was not those that wants it that got it in the first wave, despite being in the first third of the super early birds.......

Hi there, I've just received the Pro1x and I only want to use android without GMS. Although I can debloat it from adb I woud ask if it's possible from FXtec to make a stock build without GMS or if I have to wait until some lineage OS build comes to reallity. I'm the only one with this needs? Thanks in advance!

I have had the same thought. Could be nice to have a donor or two at hand if something breaks down in my daily driver. (That was working on the donor)

I have recently ran into a similar issue on my Pro1. I have installed AnyDesk which has installed a service and I had no FinQwerty-like layouts working until I have found that application was the cause of my issue and disabled its service. (Pro1, LineageOS 18.1 here.)

Having been a long time E7 user myself (in particular since 2011 until the arrival of Pro1x one month ago 😉 ), I was searching for such a solution as well. I asked the FinQwerty author about possibility of sticky keys support in FinQwerty and he mentioned that this support would need to be provided by FxTec - quoting his response: --------------------- Regarding sticky modifier keys: On Android, the modifiers become sticky if the keyboard is declared as type ALPHA in the base .kcm file. However, on Pro1 the keyboard is declared as type FULL so sticky modifiers are not enabled. Sounds

Slightly related - I had issues with FxService effectively disabling FinQwerty layouts on my Pro1x (only the default layouts worked correctly, FinQwerty layouts behaved as if I had the default stock QWERTY selected). I reported the issue to @Slion (the author of FxService), but he probably couldn't have analyzed it in detail due to only having Pro1 and not Pro1x.

Thank you very much, it's awesome! I sent the ticket number by DM.

We can ship a new Pro1 screen to you as soon as we can confirm your order ID and address. The cost would be £149 + shipping fee (I can simulate a shipping fee for you if you can provide your address). For the return/repair process, after we received your Pro1, it should take no more than a few working days to get everything sorted (depending on our backlog), then an extra few days for shipping back to you. We don't charge you for looking into the device, but if parts are needed for replacement, we will quote you. In this case, I speculate the problem could either be caused by a broken scr

Sometimes in life you are a lucky guy, and the problem-app begins with an "A". Anydesk was the influencer in my case. I did not even had to uninstall it. Just removed all the rights in the special-rights chapter. And my physical keyboard is giving me the proper values again. Thanks to all !

Thanks very much for your help, all. You put me on the road to figure it out, without flashing and without even doing a factory reset. I had installed Button Mapper, version 3.09 (current version) on both the phones, and used it to disable the shutter button on the bottom right of the phone. Once I uninstalled Button Mapper, the physical keyboard behaved as expected, and the question mark key worked again. So I guess there's no free lunch at present. I can choose to avoid all those accidental triggerings of the camera button, but only at the cost of losing some of the fun

QWERTZ with 'Physical Keyboard' set to 'German' indeed generally works. Although there are two bugs in the layout which make both the accent grave or backtick < ` > and the apostrophe < ' > unavailable:

A little more digging: It is when "Android Assistant" is given the accessibility privilege that the layouts act strangely on Pro1X