Leaderboard

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

Is it possible to flash this with adb or fastboot? I'd rather not figure out how to set up a windows VM with USB passthrough just to play with this phone.

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

Just a note that on Droidian you should change the HWCOMPOSER-1 output, so something like [output:HWCOMPOSER-1] # scale = 3 scale = 2.5 default scale is 3.

There is a GMS-less Android build available. I updated the G-drive link in here: I suggest using QFIL method to flash rather than adb sideload. Good luck!

We have spare Pro1 screen in our UK office which we can ship to you directly. But I can't promise this will fix your issue as we don't know the root cause of this. If you'd like, you can submit a ticket to info@fxtec.com and we can initiate a return/repair process to have a look?

Flashed aicp_pro1_s-17.1-WEEKLY-20220921.zip on security update 2022-03-05 Now I'm completely confused. Still initial boot-loop after flash, But despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11??? (I downloaded again, did a binary compare, and a re-flash - just to be sure, but....)

In Android Auto at one point I was getting "GPS Signal lost" every 20s or so. I've discovered that not only is my phone not receiving calls, it's not registering on the network so that attempts to call or text me fail. This is with a brand new SIM. Something is up and I need a fix or else I need a new phone.