EskeRahn

Thanks. Well then at the least we know it is NOT related limited to two SIMs. 🙂

Thanks for explaining. Yikes to the Assist part, It is the app just called "Google" that is the first thing I disable and removes permissions for when installing a new Android instance. It have a truck load of permissions granted to it self. But as many keep this mess installed you are right, Meta-key could be problematic in general.

From the reports I have seen on the stock, it seems people can use aptXhd but not aptX - can not find any logic in that though....

Three chars 3 / 4 not ONE char ¾

Generally an AC high voltage input might have the issue, and a low voltage DC is very unlikely. Could be induction but I guess surface currents could be an issue too, or simply an 'unclean' ripled DC signal. It would be nice with a setting for the sensitivity, to adjust to match different humidity and skin texture.

Yes and if meta can NOT be used as a modifier, mapping it to the Logo is fine, it would be a bad idea to waste two keys for it. We already got Alt+Tab and Alt+Sh+Tabfor task switching. The example was supposed to be "3","/"."4" or maybe I should have used "3","7","/"."4","1" to avoid misinterpretations..... And indeed modifiers are much more important to be fast than short-cuts as explained.

Installation and setup of test7 went smoothly, Thanks. Have not had time to test thoroughly in any way, but the fake keyboard is now present when closed 🙂 Have not encountered anything unexpected

I will try it immediately... *LOL* Odd that it looks so much better than stock android. I am too lazy to flash it back to stock, just to make sure it is not this unit that is magically better.... EDIT: Checked again, and the issues is there, but not at the very lowest brightness settings, And I think I got tricked by that, as the LineageOS seems to allow me to go darker, and this hides the problem also....

I disagree that it would be a good idea to waste two modifiers for Shortcuts. These are MUCH less important as fast than what is printed on the keys IMHO. Shortcuts are single-shot stuff, to launch a program, special chars should be fluent in entering a text-stream, say entering question mark or entering "3/4", So it would be completely tolerable to move one hand to do say Meta+A for a shortcut.

AH! I have troubles using touch with some chargers and cables too, though not all. No Ghost touches as such, but 'just' misinterpreted touches. PS I see it with wall chargers only, never connected to a PC.

I think I want a 'compromise'-version, if possible. Let the yellow arrow Keys send Meta BUT combined the keys with yellow print send the printed. So YellowArrow+P still sends "/" resp. "}" for qwertY resp. qwertZ. That is ALSO change Fn+P to Meta+P. Sure that will remove two possible short-cuts for qwertY (P&L) and some more on qwertZ. Just brain-storming here: Would it be possible to have a LONG press of Yellow+Letter be the shortcuts and a normal press whatever printed?

In landscape indeed yes (though only BT). But note that this ALSO sits magnetically attached in portrait, for poorly coded apps or BB-die-hards.

BTW in this thread they are talking about the screen having a green tint at low brightness. I do NOT see this in LineageOS. Have you guys added something compensating this on LineageOS, or does anyone have a good explanation? See below....

Well the obvious candidates would be the two keys right of 0, so KeyFn+KeyMinus and KeyFn+KeyEqual And awesome that a new build is close. I have just promoted the FinalSample from SnapDragon to your Test6, and it generally runs really well HAH! and as I wrote this I had the first crash on the PreProd *LOL* talk about Hybris... It needed a 7-sek power press to get alive. It was at 18%, and has plummeted from 60% in five hours(!). It was idle on the desk with screen off and no internet. It seems the main culprit (according to GSAM) is android.hardware.audio@2.0-service

I agree on that. People have different hand size, and more or less dry skin, so how much each is affected is quite different, so would be nice if we could compensate it. My personal favourite would be the most primitive approach. Present the API with a reduced 'physical' size of the display, So people can select as wide bezels as they need, that are displayed black, and independent for the two sides. This might require a boot after changing the bezel size, but that would be acceptable in my book. Having it happening in the HAL-layer, would mean that there are no programs that would ever k

I doubt it is BY qualcomm but believe it is just FOR devices with qualcomm chips. But have not been able to find a site that looks like the author. I do not even know if the linked site contains clean or infected packages... If you see a page like this, different bodies disagree on it being safe or not... I doubt it is....

https://android-apk.org/org.codeaurora.snapcam/ I do NOT think this is a safe place to download from, so for info only. (that the different packages for 2.0.002 differs with over a factor 2 in size, is HIGHLY suspicious IMHO)

It would be interesting to dig into the what Meta and Fn are 'designed' to be used for. As we got TWO independent YellowArrows and one LogoF, they almost cries for being mapped as Left and Right Meta, respectively Fn. Unless there is a very good reason to do it the other way round...

And some switch back from two to three when they get old... 😂 Would it be pushing it (excuse the pun) seeing a plain keyboard slider as a handicap friendly version of a real keyboard device like the Pro1? 😇😇

That could be an argument that bicycles should have three (or more wheels) as two-wheeled are hard to operate in the beginning. 😜

Is it just me, or does other NOT see this issue with LineageOS. Has they added some compensation, or?? My fault. Got tricked by LineageOS allowing the screen to go to lower brightness, where the problem is also dampened.

Too bad. That sort of make it useless. I would want something similar to what we got with Alt: Press and release of Sym to show the help, and Sym used as a modifier (if you remember the combos you want).

This may sound silly at first, but have you tried to hold it earpiece down? Autorotate unfortunately does not handle that well stock android, but there are apps that can remedy that. And it is build in options in LineageOS:

Well that is too far for tests anyway. I had hoped it was so close so it was easy to test.

Hmm, that makes it hard to reproduce. If/when it happens next time, try to check the time since last boot, to narrow down the location if we are really lucky it is close by where you live, so it would be easier to test if it could be provoked. I mean if it is 100km away, it is hard to test, but if it is say 1km easier...