EskeRahn

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,

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

Stick-splitting: slightly under, it was stamped 2020-08-25. 😇

It would indeed be nice with some official info on what is going to happen with the original Pro1 - I am unaware of any info. Peronally I have given up hope on any updates. And should we get any after all, I will see it as a pleasant surprise. So I guess our best chance of a somewhat updated Android system is LineageOS 18, optionally with OpenGapps or MindTheGapps. But it will require som rooting trickery for some security demanding apps like banking apps to work... See the LineageOS 18 thread

@tomthegeekand @SCΛRECROW. Maybe a silly question, but did you remove all residues of the old strip and put the new adhesive strips the same places? It could be hat you are supposed to cut it to fit?

We have had a discussion on the oddities of carrier behaviour and VoLTE over here

It is a bit more complex than a simple yes or know as it depends on the carrier. See e.g.

I did notice that they in the May update mentioned these two, but did not reflect on stock Android not being mentioned. Add: The June update mentioned it though (my emphasising): So I assume I am just over-interpreting.....

Have I missed some announcement, or am I interpreting what they are writing wrong? Will it initially be available with these two OS only? I see no mentioning of plain stock Android.

(lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247) Then redid with the new OpenGapps 11, Including a WIPE of the user data! (lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712)

I totally agree that the Pro1/Pro1X is not a device for everyone. For those entering a modest amount of texts, a real keyboard might not outweigh the various issues (size, weight, curved display and many others) but for us that uses a keyboard a lot, there are few alternatives. And in my book comparing those ends as an easy win for the Pro1. BUT that is my personal weighing, other might end up prefering one of the few alternatives, or even decide to let do with a fake (=touch) keyboard, to get a device sold in millions or billions, and thus (most likely) a more smooth experience..

Though a full case is definitely an interesting option, it will make the space above the top key row less, so the two are not independent. Also note that a regular screen without curvature, would cause the same, unless it was smaller, with a curved housing. And that effect (less the protection of the display) can easily be achieved with software leaving a passive black margin on the current screen. Personally I got no problems with the top key-row. But for people with large(r) thumbs and/or long nails and/or a full case, I can see the problem. So that would suggest that it would have been

There is a silly setting that automatically tuns the phone on when a charger is applied. It can be turn off from a pc (If i remember right it is a fastboot command, but could be adb)

This sounds like a much better idea. Hidding yourself in the head with a mallet to get rid of a headache is not recommended either, though you might be lucky that it works...

The hardware of the qwertY and the qwertZ models is identical, except the print on the keys. The software handles qwertY as the default. When qwertZ is selected by the user, the keys are remapped.

I am in an odd in-between position. I have no issues with the size of the keyboard. (I use std qwertZ, not the shifted qwertY) But on one hand the screen is too big to use one handed as touch only, while keeping a secure grip. My thumb is incapable of covering the full display. On the other hand I'm so old that a smaller screen, in a font size I can read effortsless, would leave even less data on screen....