EskeRahn

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...

It would be really nice if we had an "append" function, I also often feel the need for a follow-up, where it just not seems optimal to generate a whole new reply-post.

Others can use Android Auto, see e.g. this or this So could be some settings or specific protocol that are teasing you?

Not quite.I was referring to this feedback from @ddark-il. I did not mean to blame the network in any way, but that the Pro1 seems to have a bug on some specific network changes (at the least his specimen seems to have). As I said it is not confirmed if this can explain the other reboot-issues that are reported, Could be two separate bugs, or a specific way to trigger the same bug.

Yes. But only the first line seems to be in the 'recommended' header, so it is important that it says something relevant, e.g. the date of newest post update.

Oddly I can not recommend the FIRST post, but I can recommend a specific reply, like I just did here for the test. So when we want to make a thread that can be handled this way (one of) the first replies can be used to point to the original post.... If it is say the second comment and just refers people to read the initial post just above, we would have same functionality.

NO it was not, you remember wrong, sorry... That is a MUCH OLDER screen dump, as can clearly be seen by the "Shipping globally is estimated to be July 2019" that was changed around mid June. I do not remember the exact day, but on June 17 it had been changed to "Summer 2019", see e.g. this. So you dump is older than that... We got a newsletter on July 2 saying "We anticipate that payment will be requested at the end of July, ahead of an expected shipment date in early September." Unfotunately the WayBackMachine has no points between April and August of this page. But your dump matche

That would be the "Hal_a" sensor. See also this

Amazing stretch, 10mm. Have you got a link for it, or did you buy it in a store?

But that is only 14.4 cm long, is the bottom so elastic that it could stretch almost a whole cm extra? Or did you heat it?