EskeRahn

Nice 🙂 And funny that as a Dane with some knowledge of English and German I can actually read it without translation 😆

That sounds like a good hint! 😁 Too bad it did not help out with the Signal-related issue you had.

That could do the trick, yes 🙂

(lineage-17.1-20210329-nightly-pro1-signed.zip on March 5 security patch installed smoothly using adb sideload and opengapps pico 20210327)

You can fake input through adb, both keyboard and touch AFAIK. Never tried the touch though, but pretty sure I've seen it describes somewhere.... ADD: adb shell input tap x y https://stackoverflow.com/questions/3437686/how-to-use-adb-to-send-touch-events-to-device-using-sendevent-command

I'm not even sure that a TWRP exists for the Pro1 except for Sailfish (see this)... We better have some with better knowledge on this stuff answer that.....

...Perhaps the launcher saving wallpapers there?

Could sound like a 'vital' app has been moved (or had its storage moved to SD, and then the SD removed, leaving the system confused. So guess the hunt is to find and disable that app.... Any of these that might help?

(See line 3 of the original post)

And I assume adb root (& adb unroot) does not work either? You could also stop those you do not want disabled (e.g. Signal) Stop would not normally lead to data-loss.

Well if the purpose 'merely' is to have it booting long enough to get data out, I would continue your path and disable anything that are not essential. REMEMBER the silly thing that since about Android 4 you will also have to explicitly STOP the stuff you disabled! Yes I know it is absurd, but it will NOT be stopped by disabling it... see e.g. this. (And it autostarts even with a deep boot, if it was not stopped before the boot ) You mentioned Magisk. I'm not familiar with its details, but it is complex and powerful, so might complicate the whole task.

Just a crazy idea, you can try key input from ADB by the key events, one by one. e.g. adb shell input keyevent 29 https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_FUNCTION

Perhaps a better way would be to make one common 'Index-thread' on important hints in the HowTo section, with links to the relevant threads/posts. And have that pinned, and UNpin the currently pinned ones, (like mine on ROMs) and have links to those instead. It would be important to find a good title so people actually open it! Perhaps something like Facts hub, Base for commmon questions, hints, issues and solutions or a similar broad (preferably shorter) title... But It would require someone to actively curate what should go there and what not. And perhaps it should be accompan

They use the same BOE screen, yes. I bought a few as spares too.

(I merged the new thread in)

If you look carefully at the keys with secondary print in yellow (and green), with strong light falling in the exact right angle you will see a square 'bulging' up. So I concluded the keys consists of a transparent base a layer of white paint on some keys a coloured square field (painted or a sticker?) a black layer where the missing paint generates the symbols, (there might be a transparent protective layer on top) The US shifted QWERTY clearly uses the same base as the German QWEERTZ as the areas that bulges are the same, no matter if it is black on qwertY i

Note that (as mentioned earlier) there aren't that many yellow 'labels' mounted currently, so this layout would require more than 'just' a different top black layer print. (It is not conflicting though, but would require a change with more yellow 'labels'. that would just be hidden under the black for existing layouts.)

(Note that this retired perk dates back to before IGG opened up so you no longer have to be an actual backer of a project to see the extra info, so back then it could be used as a stepping stone for those that were undecided on taking one of the perks for a Pro1X)

I must admit I took the perk out of curiosity to see what "digital appreciation pack" meant. Perhaps it is fancy words for an email saying "Thanks" 😜🤣

Of course, the key tops could be manufactured with 'edges' to protect the labels, somewhat like this Maybe a path to go for a Pro2?

Certainly an interesting idea. Though it will be much harder to provide good stickers for the smaller keys, simply due to the lesser surface area for the adhesive. And they need to be elastic too, or mounted with some heating to handle the convex curvature of the keys. On a standard keyboard with concave tops each time we press at the normal centre of the key, it would press the sticker firmer on. Not so on convex keys like the Pro1 where the stickers would have a natural tendency to loosen at the edges. I see that a few keys were without the need of stickers, so if they were provide

Ah! That one. Sure - Forgot I actually took that too. If I buy yours, would you buy mine 🤣

I have very few voice calls, and 99% of those I do either with a headset or in hands free mode, so I'm not the right one to ask on the sound quality. Actually the sound quality I do experience is OK, it is the other end that is complaining about the quality on hands free, unless I talk in a loud and clear 'meeting-voice', rather than normal conversation.

I would expect VoWiFi calls to be similar to VoLTE here. in principle the same, just a matter of what paths the data-parcels take. And the big difference to std calls is the (in principle) HD-voice quality. and it could be as simple as this HD-voice engine being faulty.

Hard to say. A GUESS could be that the bug is triggered by this Enhanced mode but might also have other triggers....