EskeRahn

Well on the last "them" part. AFAIK the Moto Mod was a Chen only project. Adrian and Chen created F(x)tec together to create the Pro1.

You could try to install KeyEvent, The camera key on mine sends a code=80

So we need to have a little patience 🙂

Well maybe if we could summarize the pros and cons of various ideas, including those completely abandoned (and why) , it will be easier to consume than six pages of suggestions and comments....

Hmm if something has been jammed in that port in a way so this amount of force was needed to get it out, I wonder if the interior card readers could be more or less mechanically damaged too...

Ah silly me, I just heard you said landscape did not really look at the images, should have spotted that you opened it. A guess could be lacking insulation so the HAL-sensor somehow can interfere with the digitizer. I tried it here, and was unable to provoke it, so (at the least) it is not a general issue, but a specimen specific bug.

It looks like it is right about the magnet & hal-detector pair. Does it do the same if you squeeze the top display part opened? If not what about the bottom part? My GUESS would be that the hall sensor somehow interferes with the display...

A bit more relevant:

...E.g. see this IBM 3179 terminal keyboard with coloured and grey keys without print (BTW note the distinction between Carriage Return end Enter)

If we do not want to 'lock' specific functions to the keys @Craig labeled as Sym and ⬈ above we could have some 'neutral' geometric shapes (e.g. arrow, circle, square...) in different colours or shapes, and then let the OS+layout combination define the actual functions as most suitable. E.g. AltGr or Sym might be vital in some combinations, but a complete waste of key(s) in others. I have previously encountered keyboards with coloured squares.

At the bottom of this blank piece of paper please...

Yeah, that would require to let go the left hand while using say left index finger for the arrows. I use the combo for marking too, but not so often that I would find a changed grib problematic.

The whole idea was to have both Shift+Altgr and Shift+Ctrl as one-thumb presses. The price of a slightly moved slash seems low to me. Also remember than in combinations like Ctrl+Alt to my knowledge Ctrl+AltGr is doing the same, so that would still be available as one thumb.

Just a thought more, We could move the whole arrow block one key to the left, this will allow for a modifier close to Shift on the right.... (obviously this will push the "/" key right of the Up-Key)

there is a Pro extra on the first layout by Craig above (thinkpad-style) that some stuff distinguishes between right and left ctrl, but as standard only has one Fn, AltGr and sym, no distinction is needed on the two. But obviously it makes shift+ctrl harder.

Also remember Ctrl+F5 in browsers...

If possible on all OS I would prefer it secondary on BS too. But remember Del have other delete functions than deleting a character in a text-editor. It is generally used to delete a selected object in many situations. E.g. deleting a file in a file manager. So would be missed in some contexts if omitted,

I think you got an important point there, the exact colour in thin print close to a dark surrounding will be hard to see. The globe in your print shows the problem, even in the brighter colour,

The bottom part is straight forward, but the upper....

An issue to remember with alternatives to the layout. The keys are small. Except some rare cases with small symbols like for diacritics, generally more than two symbols on the key would just require the print to be so small that it could be more or less illegible, perhaps except for those with eagle eyes.

Would be cool with a dedicated case. But I think it is close to impossible less some compromises... As can be seen in other threads, some have created their 3D-printed cases, and though this for some is an ideal solution, for others the blocking the screen edges is an issue. (But for some even a bonus!) Another possibility is a flip-case. Not ideal for all either, as we (obviously) need to flip it open to use the phone. Again for some acceptable, for others not. Finally is the half solution (that is part of both the above) to only protect the lower half, And though better tha

Apart from what @VaZsoalready said. These two components are most likely super easy to change in the production line, not having to do anything else than mount a logically different chip. More drastic changes are less easy, and would most likely require changes of drivers too (and worst case some new certifications). My guess would be that they do not need to change a single line of code for the memory&storage upgrades. Perhaps a config file, if the chip does not report the size itself.

Yes as I understand it they are experimenting with "dual boot", allowing us to have more than one system on the device at a time. And with 256GB, splitting it should not be a problem for the majority. I personally hope for the ability to have a primary Lineage partition, and then a small one with Stock Android for any picky apps, that will not run on Lineage. (And for debugging if something do not run as expected under Lineage)

Like the idea. Though one could say that it would be more suited in a LineagOS forum, as it is not limited to the Pro1 / Pro1x. And perhaps it already exists there? And a new thread here with a post linking to the general forum would be a better option, benefiting more users.

Ah well then at the least we know they got the request! My guess is that it is these odd UK banking rules that are teasing again, I bet the top dogs has been super busy with e pro1x launch. But let us tag @Erik just to be sure.