EskeRahn

(I was lazy and did it OTA too, this time, went fine)

I'm pretty sure the Pro1 does NOT support PD. You can charge the device though a PD port though.

(lineage-18.1-20211004-nightly-pro1-signed.zip on September 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.

Not saying that their timeframe will hold, but have a look at this See https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control#/updates/all I assume they by total mean the processes involved in the first batch. I have no idea of the amount of people/machines set up for this, and thus no idea of the batch size and whether batches are produced in parallel, so it is pure guesswork how long it will take to fulfil the pending orders (and we do not even know how many that is). But I tend to agree with @brunoais on this. It could be possible, if all goes well,

(Download and flash worked smoothly too)

(lineage-18.1-20210927-nightly-pro1-signed.zip on September 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.

Download and flash worked smoothly too.

Even if I got the rights, I do not know how to do it, and anyway it should be for the company to decide, so let me tag @Erik

Could well be what I see on AICP-R, as being the same base (AFAIK).

Maybe you need to unsubscribe and re-subscribe, to trigger it again? (on IGG click you account-name top left, Settings, and then the Emails tab)

That is odd, I got an automated one sent from indiegogo 11 hours ago. So either some mail-filter is teasing, or indiegogo no longer have you on their mailing list, I highly doubt that this rather small group gets it sent out spread over that many hours.,

ADD: A really low priority bug. When attepmting unlocking with the fingerprint scanner from display-off it quite often does not work.. If I then press Power and tries again (from the lock screen) it (AFAIK) always works, including the haptic feedback. I THINK it is could be related with how deep it sleeps, that is if after a while in lock it might work if by some chance I touch it while a wake lock has woken the system, e.g. to check mails. But that is pure guesswork. This is absolutely a low priority issue, but just to the list to remember if more important things fails to do as ex

(lineage-18.1-20210920-nightly-pro1-signed.zip on September 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.

An odd bug with 1.1.3, on AICP-R: It very often auto-opens when lid closed, after some seconds. (with the "....screen lock aborted") It MIGHT be related to the motion detector, as it seems easier to have it stay off when on a table. But there are no full correlation, at the best a tendency, but could be multiple factors, that effect when it triggers and when not. A not too slow 'close-open-close' on a table seems to work quite often.

Just an idea on Lineage. Perhaps you should grey-out or hide the screenfilter when on lineage, until you find a workaround? In the Advance settings I guess the four key-filters are irrelevant to Lineage too, right? If so you might hide (or disable) when on Lineage. I know that on stock you had to use the proximity sensor to wake the screen, as the hall sensor did not fire. Does the same go for Lineage?

Thanks for your guidance. 2½ years ago I started on a project doing exactly that, but lacked the information, I will try to find time to finish it. If anyone wants to finish it, or fork it PLEASE feel free, it is in simple C# and feel free anyone, all I request is if someone uses it to make something useful, is that I get a copy. 😁 (Just reopend it, and it is currently not much-more than an UI template) I had an idea that it should have some 'layers' that could be shared/imported by dfferent languages. say you had a math-layer that you mapped to Ctrl+Yellow, Or whatever, someo

The funny thing here is that if you on a PC with a keyboard with 'tall' Enter key select US-keyboard (That is what I normally use), then you will find \| IS placed next to Z, so the two keys seem to be wired the same - rather odd... I have not checked their scan-codes. That is the key in e.g. UK keyboard three right of L is new, and NOT the one above Enter in the US-layout, that one is MOVED to left of Z. Strange...

(Just downloaded, will flash within minutes 😍) It did not install with the previous AICP-q boot.img, but it did install with the latest LineageOS 18.1 .img open_gapps-arm64-11.0-pico-20210712.zip installed as well. So now i'm back on AICP after being 'unfaithfu'l using LineageOS 18.1 for some weeks on the 'final sample' too. Lovely. 😁 Battery saver "Battery may run out soon ....blah blah .... 40%" I would say that kicks in a little early.... But it was when it still installed apps in the background, so the projected remaining time was low as could be expected. I usually turn

Thanks @tdm, links added here 😁

I like Slions version, except I would swap the backslash and back- apostrophe keys. to more usual placements, and especially in light of other qwerty-based languages where the accents are usually on the right side

Thanks. But if it ONLY works with German, this seams to break the whole original idea of letting the qwertz/qwerty switch select all the necessary remapping to get a standard layout so ANY available android standard layout could be selected, fitting the users language. ADD: Obviously if I select a qwerty based language on the qwertz keyboard with the qwertz switch, I EXPECT the letter between T and U to send a Y, and similar others will not match the print. (and obviously similar issues the other way round) No better or worse than if I selected to write with another language on a phy

Ah I see. Please note that their support mail system (zendesk?) works in a way collecting mails in the queue, so sending in a new mail pulls back the previously mail to the end of the queue.

I currently have two Pro1s on Lineage, and am unable to reproduce the issue, no matter how much I let it charge or discharge, and no matter if it is a slow or quick charger. One of them recently factory reset (had AICP on it before). So unless there are unknown hardware sub-variants, it must be something different we got installed that somehow triggers (or remedies) the issue.The only explicitly battery-related I got installed is GSAM battery manager, and 3C all-in-one Toolbox. Both just monitoring the usage.

Sad to hear. But just to be sure, are you on stock Android or LineageOS? (Some are having charging-issues on Lineage)

As I read what @3zet writes, the point is if you have some software that stops charging when full (to prolong battery life when constantly connected). Charging ought to be accepted again once below a certain threshold.