EskeRahn

PS do NOT expand the caps hole that much on the real units, the LED on the PreProd unit is much weaker (and the hole smaller), hence the need here... PreProd left Retail right. Backlight off, caps on for both.

You can see the square 'mat' around the green above... Just did a new more successful attempt expanding it further to a larger part of the mat. (the white damage from my first attempt is roughly in the middle now, as I scratched practically to the lower edge of the 'mat')

You should try tipping the keyboard against the light, and at the right angle it can be seen that the yellow print (and the green Caps) is a coloured square slightly lifting the black. If you got sensitive fingertips, you can actually feel the slight 'jump' gliding the finger lightly over the key tops with yellow print. NOTE that some got the mat but NOT the print, I guess prepared for different prints. (e.g. the W on qwertY). It is easiest to spot on Caps. I tried to extend the small green dot on the preProd unit, not that succesful, but it clearly shows the white under green under

Either, as they both involves a hard keytop on what I assume is a clear rubber mat

Let me put it this way: I made the underscore on the PreProd unit longer by scratching... (it currently has SFOS without backlight, so can not show a usable photo...)

It sends keycode_home afaik

....Or someone making a small android program listening on the keyevents, and catching F3 and F4 and convert them to sleep and wakeup. Have you tried if something as simple as the .kcm can do it for us as a temporary measure?

(moved the spare batteries discussion over here)

My original batteries for my Sony Ericsson Xperia Pro are still good. The important thing is to remove it from the device (or just insert a piece of plastic as an insulator at a terminal), If the battery is charged and left with only self discharge, it keeps it charge for years, and can still be charged. Just make sure that you charge them say every second or third year, so they do not reach 0V. That is the problem with newer phones, you can not leave them truly off and hence the battery will be murdered, if the phone is just kept in a box, without occasional re-charging. I also got (chea

I think it IS coating. More precisely i think the keys are clear, and then have some white coating, and some have a small square in yellow (or green for caps), and then finally a black coating, Similar to what Lenovo are doing (less the coloured squares).

Please keep discussion on it working or not and how to test/remedy in the existing thread here Not to have everything duplicated...

It is definitely the best technical solution not requiring any DIY at all we have seen (yet?) What for you is a plus, would for some of us be a scare off: The motif. But a more anonymous version might have a broader appeal. And I bet you can easily adhere in a strategically placed magnet in the card-holder, if we can get them to change the keys it send. I bought some for for another project here, unless you buy 50, the shipping is higher than the item cost....

Interesting alternative. I guess it would have been simpler to take a £4 flip case for a Huawei P20 Pro, and just adhered the logo part from the sleeve.

(Moved the more general discussion not on the notification led over here)

But it looks like simply replacing sending KEYCODE_F4 (86h) with KEYCODE_WAKEUP (E0h) and KEYCODE_F3 (85h) with KEYCODE_SLEEP (DFh) in current logic will do the trick with no other changes. 😎 YouCut_20200218_095817803.mp4

The point is that that the case needs a strategically placed magnet, matching the position of the sensor. It already sends F3/F4 on close/open. So all we need is that F(x)tec alter it from sending KEYCODE_F4 (86h) to KEYCODE_WAKEUP (E0h) and from sending KEYCODE_F3 (85h) to KEYCODE_SLEEP (DFh) YouCut_20200218_095817803.mp4

No no no, use the link.... It is MAGNETIC and works in either landscape or portrait....

Tried on stock with adb shell input keyevent 223 adb shell input keyevent 224 And they work perfect.....

Yes just tested in KeyEvent, we do indeed get an F3 when I put a magnet close and an F4 when removing if. Just as the keyboard send an F5 when closing, and an F6 opening. So then the big question is if that can be used somehow, but maybe that is really not a lineage thing, but merely a stand alone android app, that should react on these, and could be used on either lineage, or stock. (Though I would recommend to on Lineage to map all four to some more odd keys, as some might want to use F1-F12 for something. Some odd candidates: ADD: Though F4 replaced with KEYCOD

As far as other posts goes, the Pro1 does not seem to support exFat, so go for Fat32. There is a thread on SD here as well, so maybe a more relevant place to start. But I see nowhere mentioned that ha can not see the card at all. So Let us keep the camera stuff apart

The Pro1 got TWO hall probes, one for the slider and one for a lid! See this. So it is prepared for a flip-case. Can you guys doing the LineageOS patches for the Keyboard slider copy that detection code, and use it to handle screen off from the other probe also? That would be pretty awesome! Actually I was very surprised that the Hall sensor was there, but it does not seem to do anything.

(That is what the XDA link he tried suggests)

Just tried to insert an SD-card (formatted in another phone or pc years ago), booted the phone, started the Snapdragin camera, setting, storage, selected SD, back, took, an image, and it worked well. (Changed back to phone, pulled the SD card and checked on a computer and the image was where) Try a small card, to see if that makes any difference (the one I used was an old 1GB I pulled from a Galaxy Wave(!) a few days ago for playing with SFOS)

The link you are posting is on LineageOS, have you flashed that? If so I will change the title to reflect that 🙂

Ah I see. Just wanted to make sure if yours has a hardware or software issue 🙂