EskeRahn

Try the app "KeyEvent Display", see if e.g. pressing "1" and YellowArrow+"1" gives the same.

Thanks for the suggestion, Hope it will work. My daily driver is getting these issues to a degree where it is getting a nuisance, so if it can be fixed with a few hours of fiddling it might be worth it,

Please note that they at some point said that their Zendesk system moved pending cases to the back of the queue when a new mail arrives from the same mailaddress, If that is still the case, your repeated mails MIGHT have moved it backwards in the queue before it was ever handled. 😢 I do not KNOW if that is the case here, but it MIGHT be. I have no idea what is going to happen for any backers left after their Nov 8 update.

Yup tried both I will await if anybody else has it, If not, I will try a wipe all the user data, and reinstall everything. (it is my spare/test-device, so tolerable)

Is anyone else having issues with app-updates in the android market? I normally have automatic updates OFF, but even if I (for test) set it ON, I get the same bug, that after most of the download it stalls. It can be a tiny update less than 1MB. It most often stops at 99%, but can be earlier. If earlier putting in and out of aeroplane mode usually get it to 99%. Google's Updates works just fine on my Pro1 on stock. And my Pro1X on stock yesterday, (all using the same Google account). Last this one updated was January 3. So that could have been on 21.0 So MIGHT be related to

I tried to pull out the APK for the Pro1 and use it on the Pro1X, but it did not work. adb pull /system/priv-app/Launcher3QuickStep/Launcher3QuickStep.apk Launcher3QuickStep.zip

(lineage-22.1-20250111-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20240928_150548) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

to @DoctorClu, I agree with @claude0001, but LineageOS also has it drawbacks, over stock, though for some they might not matter. Pros and cons.... Personally the lack of multiple key-layouts, that was broke a few versions ago, makes it almost useless for me (use it for tests only). And there might be some app that have very high security requirements that might not work.Could e.g. be bank apps, or some apps for putting official papers like drivers licence or similar identification apps on the phone. Some might work fine though, but not all.

My best suggestion is LineageOS on your Pro1/Pro1X, as this is Android15, so should be supported a few years yet by most apps.... But indeed for new hardware we are in a limbo, And i really doubt that anyone will attempt making a new one - though I still hope for it....

They report that they have fixed it 🙂 Thanks @Casey 👍

(lineage-22.1-20250111-nightly-pro1-signed.zip on December 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20240928_150548) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

Interesting it was OFF at my Pro1 (note not Pro1X) after upgrade - surprising difference.

Half a second is a very long time for any real intended double strokes for normal users. it would be a daily nuisance for most users. It is placed under accessibility for a reason, it is intended for those with some neural issues affecting their finger control.The default is off, so could well have been there before, but I have not noticed it either. Could be new

I can confirm that the keyboard deteriorate over time. My daily driver (stock android) has several keys that have become unreliable, giving 0,1,2 or even 3 chars when pressed once.

(lineage-22.1-20250104-nightly-pro1-signed.zip on December 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20240928_150548) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage. Note that this is just a few days after the initial 01->04

(Note that 22.1 was released just a few days ago. See this)

I have no idea if there are any difference, but you could try to upgrade to the brand new 22.1, see the thread by @TeZtdevice here.

@TeZtdevice Has started a new thread on the new 22.1 here: I have switched, and will thus no longer be posting here on 21.0 specifics.

I was unaware they added these nice instructions, but that is almost exactly what I did, having already fetched the MTG package for 15 a month ago, and prepared the batchfiles i usually use with suitably bumped numbers.

Did a dirty flash (no factory reset) from lineage-21.0-20241228-nightly-pro1-signed.zip on December 1 security patch and MindTheGapps-14.0.0-arm64-20240925_175633 to lineage-22.1-20250101-nightly-pro1-signed.zip on December 5 security patch and MindTheGapps-15.0.0-arm64-20240928_150548 using adb sideload And all seems to work as before. 🙂 We still can only select one keyboard layout though, so no easy layout switching, for multilingual usage. 😢

@Slion made a service for the old Pro1 long ago handling case close. AFAIK nothing similar is made for the Pro1X, as it does not generate an easy to catch code as the Pro1 did. I would be very interested if something similar exists for the Pro1X also.

Searching for "hall" https://community.fxtec.com/topic/2781-pro1-factory-test-mode/?tab=comments#comment-59844

There are two hall sensors. We have that in the long case thread....

(lineage-21.0-20241228-nightly-pro1-signed.zip on December 1 security patch installed smoothly using adb sideload and MindTheGapps-14.0.0-arm64-20240925_175633) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

There still is the bug that has been there quite a while, that the system in that is to protect the Pro1X from being overcharged, sometimes kick in so it will not charge at all. I see no pattern in when it happens, it can heal it self, so a later charge attempt work. And no it is not a plug issue. Once it charges, no amount of unplugging and replugging will bring it back in the state of refusing to charge, so it is a software bug.