EskeRahn

I have looked too, without finding it. And combining the modifiers seems to have no or strange results. Try Shift+Sym and either B or Z and you get ZB or sometimes BZ (similar for C&M, X&N, A&Space) so does not bode well for possible combinations giving access to the symbols There apps like "UniCode Charmap" that gives access to a long list, but obviously tedious to fetch and paste in that way.

Have a look here: https://android.onse.fi/finqwerty/#pro1x "English US" (no finqwerty) also includes them

Did you try FinQwerty? It now also has layouts for Pro1X.

The WiFi seems pretty unstable, but when it works it is OK - I must admit I have not used it for anything other than updating the apps (and the OS) since I played with it initially, and yet it seldom gets through 10 app-updates without throwing the WiFi connection at the least once (1m from router and at the least 40m from nearest neighbour net), In aeroplane mode, it uses a mere 2% a day, that is pretty impressive. (due to the unstable WiFi, the Stamina is bad with WiFi ON, but that is to be expected by frequent reconnect attempts, so not a stamina-issue, but a side effect of the WiFI-inst

(lineage-19.1-20221010-nightly-pro1-signed.zip on October 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

(edited the title to be general on Pro1X sale)

Yup, got LOS 19 on the pre-production unit, and it is not bad at all..

Flashed aicp_pro1_s-17.1-WEEKLY-20221005.zip on security update 2022-03-05 Still initial boot-loop after flash, And still completely confused! Despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11??? So time to give up on AICP on Pro1 I guess!!! ...when I find the time this test-device will likely get Sailfish again...

The lot of mails MIGHT be the problem... For all we know on their help-desk system, sending a new mail, joins the new and the old mail, so they can be handled together, BUT at the bottom of the queue. And don't ask me on the why it is this way. But at some point they told us that is how it works.

Have a look here: Most likely it is a carrier-limitation, not white-listing the Pro1 / Pro1X

Though the AICP-R has now fallen out the bottom of their download list, it is still available from their "vault" https://media.aicp-rom.com/vault/pro1/ 😁

(lineage-19.1-20221003-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Exactly, it does not make any sense, and R falls out the bottom next Wednesday, So no more AICP to us....

Interesting. Does the solution you got working require the phone-display to be set to 1920x1080 (see a few posts above), or does it crop the sides on then monitor? Or does it offer two independent screens?

Flashed aicp_pro1_s-17.1-WEEKLY-20220928.zip on security update 2022-03-05 Still initial boot-loop after flash, And still completely confused! Despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11???

Until windows started to require signed drivers (that they later relaxed on), I felt the same, super easy plug and play, how hard can it be...? But later I could not get it working at all, and understood what people was on about., To an extend I limited myself to OTA, for the weekly updates. And PTP&MPT still worked just fine, but fastboot was a lot of trouble. but after a lot of experiments i got things working with an ancient cheap $1 usb-hub, that is terribly slow. And when I got a new PC it got even worse, I then optimistically plugged the USB in the docking hub, and it have worked fla

Interesting, I have not done their OTA for ages.

https://nerdschalk.com/change-screen-resolution-adb-android/ Will test.... Thanks for the idea. ADD The resolution change works - but that is not enough to get HDMI working. adb shell wm size 1080x1920

(lineage-19.1-20220926-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Very interesting. If the info I quoted earlier is true, it might 'only' support FHD, so if that is the case, we might also need a way to get the phone to crop the sides from 2160 to 1920, so it can act as FHD to be able to mirror. If we are very lucky that is enough, as you have proven that it already somehow understands what is going on.

Yes, it can be easier to get things working with an old port, or perhaps using some hub. Obviously the usb-driver can also be the issue. Or even cables / can be quite a puzzle... On my Yoga it only works with an unsigned Google driver, and when going through a hub - currently using a thunderbolt 4 docking/hub

Sad story indeed.... I know the feeling of getting into the 'red field', and not wanting to waste any more time/or money to get things right, from dealing with other companies. I'm awaiting a Pro1X, so not in the market for buying one. But hope yours will find a new owner soon.

Looking for other phones with same chipset we got this list on gsmarena I tried googling for hdmi and one of them (the motorola G30) but found nothing. I did find a fairly officially looking answer suggesting using casting instead, so that sort of points toward that the chipset might not support it, and thus the link I first found could be wrong....

Are you sure about that? https://en.wikichip.org/wiki/qualcomm/snapdragon_600/662 I do not know if it is true or not, BUT it would mean that it can not just mirror the standard 2160x1080 resolution of the main display, and that MIGHT be what is preventing it from working when plugged in. So we would have to get the device into a FHD (or less) mode, for it to be able to do the mirroring. (I have no idea if the chipset/os can handle individual images on the two)

I wonder if that was a typo, or you being extremely pessimistic.... 😇