EskeRahn

Yeah, I think it was a little gesture appreciating her getting in more than a handful of new orders from her network, If I remember other posts right.

It is physics, not the motor...

We should consider this in the how-to-open thread.... Another option is to add some of the adhesive anti-slip tape intended for stairs (black or transparent) e.g. this And cut a roughly 2-3 x 150mm piece (Use a hobby knife or similar, as the sand kills the blade, do not use a good pair of scissors...), and put along the back edge. (so it does somewhat belong in the casing thread...) This will give you a VERY easy lift. (The same material is GREAT for compact cameras with slippery surfaces like Sony RX100 III) Mine ended on 3mm+ and could/should have been less.

I think the cut for this offer were somewhere end of June or early July. They originally stopped it on June 17 (+/-) but then extended it a (few?) week(s).

Rememeber that Ctrl and YellowArrow are next to each other on both sides, so the combo is easy to do with one finger. That is why FinQwerty uses Ctrl+YA as a 'doublet' of Sh+YA

I moved it to the sailfish thread. 🙂

We know the numbers - but just can not find them..

As said in other posts I think the problem here is simple physics: The counterweight of the vibrator is a standard one, designed for a 2-3 times lighter phone. So they would have needed a larger counter-weight and thus a larger motor, adding weight to the whole system (and as these would likely not be standard components, also additional costs)... But I struggle too, especially walking. As I 99.9% of the time use my phone with vibrate only. I have not even set the ringtone on my Pro1, so do not know how it would sound....

Hmm. Mine does, so sounds like something conflicting. Does sliding open the keyboard wake the display as it should, or only pressing power?

Is the keyboard turned off while closed on Lineage? If not squeezing the device might send a key, and we do not want that to wake in say a pocket. So if it is NOT turned off closed it should be a single key hard to press by squeezing. If it IS off closed, other things should be considered. The modifiers would be good, as there is no 'risk' in tapping those, the same way there is in taping a key that could have a function. If say an incoming call arrives just as you press Enter, so 'any' keys might not be optimal. So safe keys in all scenarios will be the Shift-keys, as neither of t

I almost solely use thumb-typing on the Pro1.

As previously mentioned a S20+ full-body back-over-front case was expected to fit the screen, but too long. This morning this arrived, and well it does fit the screen sideways, and is too long, BUT it makes the edges of the screen out of reach, and that what not what I was hoping for. On the other hand the edge sticking out makes it easier to push up the screen. It is not for me, so I have not bothered to try to cut and melt it shorter....

No no, spelling error meant motif, sorry Tried to contact the seller on other colours - no reply.

I would like stickers like the round ones for the cases... I have actually planed to ask a friend of mine that makes stickers to produce something like that.

Well an app that is trusted today might not be trusted tomorrow, especially after updates.... In principle it is always a good idea to work with minimal privileges needed. So if an app does not need it all the time, but only under special circumstances, it make perfect sense to only let it have the big hat for that specific task. It is REALLY hard for the ordinary users to keep 100% track of their apps, especially if updated. The benign app might be sold to another company that proves to be crooks, by the time you spot it in the news, it might be too late.

Yes. And ah I see, these events are not going through the .kcm... Damned... Then we will have to wait for F(x)tec to change F3/F4 OR we need a program listening for F3/F4 keyevents, and then 'alter' these (or absorb them and emits the correct ones). Obviously just a temporary hack until the codes are changed.

Just to be sure, does these work by you (they work here) adb shell input keyevent 223 and adb shell input keyevent 224

I never tried to fiddle with the KCM files, but looking at what @Anssi Hannula is doing in e.g. this would something like this not work?

The odd thing is that I have no real trouble with the RIGHT hand on the qwertY only the LEFT. My GUESS would be that the right side generally varies more between keyboards. Different shape of Enter, Some got a numeric keyboard right of the letter block... The left side on the other hand, there has been total agreement on since the typewriter days... So that is anchored firmer in my brain. And that the numbers are NOT shifted makes the whole thing worse, as they in my brain are misalligned with the letters... I have been using Lenovo Laptop keyboards for long, and I STILL can not

We actually know the raw production price without paying any licence fees or anything from the customs documents ($300), and we have heard them call these fees "hefty", so let us for a moment assume they at some point have sold enough at current price and have paid all the development costs with interests, I doubt they would be able to ship them even with zero 'profit' for $500, so I don't think there is a huge margin to cut from... So don't hold your breath for it.

Let me guess, you have used/tried a Nokia slider like e.g. the E7 or N87 before? If so it is like biking, the body remembers.... 😎

Exactly the qwertZ with FinQWERTY is like what we would expect of a keyboard, just reduced, and I for one can quickly adapt to that. The shifted one is constant trouble for me. When I used it extensively I make errors the other way round on a pc... Actually I think the shifted would have been easier if it was say Dvorak or ABCDEF... if the keys are not in their proper QWERTY positions anyway.... As you then would need to learn an unrelated keyboard. Because the letter-shifted qwertY is so close to a real qwertY, my mind has a hard time keeping them separate, It is like when I speak a

Take a photo, so you can prove who messed with it, if something is wrong 😜 But glad you finally got it.

The numbers you are sending are wrong... wakeup is E0h or 224 decimal, and sleep is DFh or 223 decimal, see the links above. Sorry you were talking scancodes, but that is not the scancodes for F3/F4 afaik

Should be available in the generic.kl i guess? or any vendor .kl ? see this generic says 102, and so does all the others I checked.