EskeRahn

AFAIK, it is only minor details that makes it different, like a different keyboard mount (it covers the screws) i'm not sure what else is different. It got no imei, so I can not use it as a phone, so some of the phone antennas might be missing too without me noticing..

(lineage-18.1-20210816-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above. Did not try to do a factory reset first...

As I (normally) only charge the LOS Pro1 weekly, it sometimes get quite low, I have been down well below 20%. Anything below that seems to be unpredictable. It can jump from 15% to 0%. Not that uncommon percentages are just estimates.

Thanks, so it must be down to some apps not working well with LOS 18.

Please note that I am (still) on 20210726, so that might be why I don't see the issue.

See also this thread on some experiencing charging issues. https://community.fxtec.com/topic/3408-pro1-on-lineageos-181-only-charges-if-i-reboot-it-first/

Several seem to report this, so I tag @Sean McCreary to hear if anything has recently been changed that might affect this.

Ah nice! I was looking forward to someone testing that 🙂

i'm pretty sure this is expected behaviour, as the system tries to prolong the small time of battery stamina left, by reducing speed.

I would try to (temporarilly) manually stop user-installed apps one by one, and see if one particular app triggers the odd behaviour on LineageOS. Have you rooted_ Could it be Magisk? (mine isn't rooted, plain Lineage and OpenGapps 11 Pico)

Works fine here too. Either with a regular charger, a fast charger or a pc-usb port. (I usually charge it through the PC weekly before updating the OS - use it for test only, hence the whole week stamina)

It seems like the best shot at it getting to work is if FxTec can do something similar to what @peter.s.fidelman described UniHertz did with AT&T to get the Pro1(X) whitelisted - I have no idea what it takes to do so (AFAIK it is not as easy to swap the IMEI on th Pro1, so most likely it would be to get existing IMEI-ranges whitelisted), but let us tag @Waxberry and @Erik and see if one of them can perform some magic here 🙂

Contact fxtec and hear if they got it as a spare part.

IT WORKS!!!! 😮😮 Here is what I did boot to bootloader fastboot flash boot_a lineage-17.1-20210222-recovery-pro1.img Roll down to "Recovery Mode" with VolDown, and press Power to select. Await recovery boot. Select "Apply update", "Apply from ADB" for main flash adb sideload lineage-17.1-20210222-nightly-pro1-signed.zip From main menu, select Advanced, "Reboot to recovery". Await recovery boot. Select "Apply update", "Apply from ADB" to add Gapps adb sideload open_gapps-arm64-10.0-pico-20210327.zip If prompted (shortly after 47%) tap

No. We are not even allowed to downgrade from 18.1 20210809 to 20210726 ...Though there is a SLIM possibility that it might work it works, if you do not attempt to boot into 17.1, but stay at bootloader or recovery level

Navmii works fine on both stock Android and AICP, so assume it works on Lineage too (The preproduction unit I use for Lineage lacks the GPS antenna)

Thanks for the reply. I personally merely use Lineage for tests currently (so no big deal with resets). I'm just reporting so others can decide if they should upgrade or stay on the 20210726 for now. 🙂 If someone need an app that uses the accessibility keyboard hook and interferes, but does not use it frequently one can consider as another option to leave the accessibility off for the app, and only turn it on when needed temporarily. People should also note that it is not all apps using the accesibility hooks that interfere. (e.g. There are no issues with Greenify)

(lineage-18.1-20210809-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But keyboard bug reintroduced is not yet fixed, see comment from @Sean McCreary above. Did not try to do a factory reset first... But did try to flash back to 0726, and that claimed the data to be corrupt, so was forced to reset... So made a third flash WITH a wipe... and that did not work with the 0809, so went back to 0726, with another wipe required. And things work again. I hope for better luck next week . 😇

From what I can google VoLTE uses SIP, so if VoLTE is working with your carrier so is SIP. But obviously SIP might work even if VoLTE does not.

Good news! Indeed thanks to @Sean McCreary again. 👍

(lineage-18.1-20210726-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712)

Indeed, a flip case is the least bad available, and I have used similar too for over two years. But it is not to everyone's liking. See this (long) thread for various options.

In Denmark it is one year full warranty, and the second year you have to prove it was the manufacturers fault. (That is why planned obsolescence is not uncommon to kick in shortly after the second year)

(I moved the above three comments over here)

It is certainly not an easy road for a small company being swindled like they were. I'm amazed they got the stamina to push on, and did not just close their business. And indeed if they are so unlucky as to be flooded with warranty requests it might be very hard for them to fulfil what they legally are obliged to. So a big thumbs up from me for their will to fight, And fingers crossed on the road ahead being more smooth,