EskeRahn

(lineage-18.1-20211213-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

It is really odd that this is seen by a number of people, but not everyone. Would be nice to understand the root cause. Is it a quality issue on displays or connectors? Is the connectors sensible to e.g. humidity? Is it an assembly issue, that goes wrong on some? Is it a grounding issue? Is it a special mechanical stress that triggers it, that we could all accidentally trigger? Air humidity? Or??? I see something somewhat similar to the described while using a non-grounded cheap charger (tried several). But no issues while charging it through a grounded pc. So this make me think of s

Indeed. Splitting sticks: On indiegogo (like any other crowdfunding) we do not "purchase" an item, we make an "investment" and hope to get the perk we selected in return. But like buying shares (where we hope to be able to sell it later with a profit), there are no guarantees. The risk we take is why the price of a perk is usually substantially lower than doing a (pre)order on the same item.

Update to December 8, with November 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

See how 'easy' things are, even for this minor fruit company, according to nikkei here. Surprised that some seems to expect that it is super easy for a huge player like FxTec to get parts as they need them, just they try a little harder....

Indeed some apps with mixed functionality could need the permission to offer functions the individual user might not need. And if so indeed removing the permission solves the keyboard interference. Also note that not all apps using the accessibility API will interfere. E.g. Greenify stops apps in another way than the fake keyboard entries Android Assistant generates.

(lineage-18.1-20211206-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

There is a lengthy talk on the keyboard-accesibility issue in the Lineage thread. In short they made some fundamental changes to fix another issue for many users. And that fix is incompatible with the way apps with the accessibility privilege (using it to fake keyboard inputs) works. Android Assistant is a simple example of that.

If the usb-board is functioning, I would expect the LED or display to react when applying power. If the display is not working, but everything else is, the LED should turn on. If the display is working, I would expect something to happen in the display. So going for the simplest options first, I would certainly start looking at the USB side (charger/cable/board)

If it is the usb-board that is damaged, it might work as a temporary measure to hold the plug at a certain angle. Try and see if you can get the LED to light up. This way you might be able to charge it enough, so you can get any needed data out. (Oh. And if you have not already tried, try a different cable and/or charger, you could be lucky that it is merely a broken cable)

In short, no I'm not telling you that.... Reread

Update to December 1, with November 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

I'm not sure you can on stock Android. (At the least it might require root). Could be easier on Lineage, and is easy on AICP though.... (see also this old thread - think I will merge the two)

(I made a skeleton for such a gui for a pc, but never finished it, has posted it somewhere in here - forgot where though.) FxtecKeyboardSetup.zip

Splitting sticks we got 16 updates the last twelve months, but granted five of those was in December. Let us hope we get more than one update this December too 🙂

I'm pretty sure that is exactly it. I have not tried installing, but I believe they have described it in the Lineage 18 thread. Selecting (e.g.) German, without installing anything, you CAN get umlaut with Alt+U followed by a vowel, e.g. U. Not super elegant, but possible. I'm not sure if there are ways to get them more directly, Sym and Alt does the same here. Similar for other accents with I and E ( plus ~ on a physical shifted qwertY keyboard)

I'm sure lawyers can find a number of ways to interpret "once a month"... 😁 But I'm quite sure everybody would be really p...ed if they just posted an 'update' saying "Still waiting on/for XXX. So no news.", a few times a month to meet this. And they might not even be aware that this requirement is there. The problem is that we all want the device we took a perk for, and thus hope to get, and thus we want to know when we can expect it in our hands. And as they most likely can not say that, no matter what they write until they know will be a disappointment. But do not misunderstand. I

(lineage-18.1-20211129-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

Well the original Pro1 is no longer available and the Pro1X is -according to last months update from here- expected to be ready about now. But we do not know how large their backlog is, And transportation is a mess too these day, so really hard to guess when you would get it if you ordered it today. I would positive surprised if it would be 2021.

Do you expect say one making a washing machine to stock all the parts that might be needed to repair their machines for the whole expected life time of the device? I doubt anyone would. The sensible thing to do is to stock what can be expected to be needed within some reasonable time frame, where any needed reorder can be expected to be fulfilled. And with new models you never really can be sure which spare-part will be the one in most demand, so they would not want to buy a lot of parts they are never going to use. The problem now is that reorder fulfilment expectations that ma

On the charging issue, see my posts here in the AICP thread also.

My GUESS is that it is a bug in the system that is supposed to prevent overcharging while plugged in and about fully charged, by keeping it an about fixed level. In some circumstances it kicks in too soon, and keeps it at way too low fixed limit (I plugged it in at 17% yesterday)

Update to November 24, with November 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread)

I have for the first time had the 'not really charging' bug. No matter if connected to fast charger or slow charger, and no matter how many times I unplugged and re-plugged. Restarting brought the charging (connected to fast charger) up from 3mA(!) to 300mA. Unplugging and replugging brought it to 2000mA, where I disconnected and connected to slow charger, charging with 1000mA. I plugged it last night, and it kept it at 18% over night but did not really charge... (currently downloaded and now installing update)

This is a general pc issue, not limited to the Pro1. It can be REALLY tricky to get fastboot connection to work. I was lucky with my ancient 2016 laptop, everything worked smoothly. Not so lucky with my 2021 one.... (Both Lenovo Thinkpad X1 Carbon, just newer generation...) Sometimes just using a different port on the same PC might do the trick. Sometimes you might need a hub. Sometimes a different cable is what it takes. You could try a completely different computer, if it is one time only, just to unlock....