EskeRahn

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 🙂

To make sure all three sub-LEDs are working, try the first test on the list described in this thread. It turns on Red, Green and Blue one at the time, and then ask if it worked. And if you try oher tests BE CAREFUL! There is one calling emergency with no warning. (see my comments a little down the tread for descriptions in English)

It is certainly a big leap between an Iphone and a Pro1. Nice that some variety exists now, so each can find what suit them the best. I for one hope I never have to go back to Ios. Though my magnetically attached landscape&portrait keyboard solution for it worked reasonable well. See here for more images. (Note how it when attached in portrait, is mounted so the device is centred between G and H)

Yeah, Though I sit with one question for @tdm, @Sean McCreary and others helping: Where are your guys donate buttons, so we can send you 'a beer'?

Found a reasonably sober review over here , He is quite positive (well they sell it...), though he ends up with a little on who it is for... (Google translate)

Let us hope you get a replacement or a fixed unit quickly.

Thanks for reporting. Let us hope they can use this to reproduce It, I tried to reproduce here, but was unable to. Can you elaborate a bit on how it happens?

Here a (collage) version with my descriptions (and colouring) added.

The lines goes green when it see a change. That is line two light op after first opening-event, and line one after first closing-event If you do not see this you most likely have a hardware error. If you do see this, what you report is most likely a software issue.

For the bug you see it sounds like it almost certainly is something with the Pro1 not handling some network changes correctly, perhaps changing bands? But the reboots others see we do not know if they are also network related, or something completely different. I guess when they fix the bug you got, we will see if it help others or not...