Device stuck about f1s-sdk

[goranche]

@Icydeadpeople225
We can't really help you with that, our customer care might be the right place to turn to.
We only support the SDK aspect here and don't have access to other aspects of the support chain.

That said, I'll try to check if there is anything with that particular version of the firmware, and will reopen this issue if I find anything.

In the mean time, have you seen this blog post and video?
We've recorded it because the instructions were somewhat unclear 🙈

[goranche]

@Icydeadpeople225 hm... you shouldn't have the A revision of the firmware, which is kind of weird, but still shouldn't cause this many issues.
of course, having "played" the game of development for quite a while, I'm well aware that "should not cause" doesn't hold much value 🙄

We're working on an update function that could be used by end users (like yourself), but aren't ready with it yet (I won't bore you with the usual story: limited resources and priorities 🙈 )
I'll try to see if it's something we'll be able to move along faster, and let you know when I have more info.

In the mean time, I'm reopening this issue (so it doesn't get lost) and assigning myself.
(I'm not putting the bug label on this issue as it's not really an issue with the SDK itself)

[Icydeadpeople225]

Don't know if this is related but I've got customer support working on the issue too. (946820) I do tech support so I understand the difficulty. I've heard a few others online complain about the same symptoms so there might be other devices like mine. Let me know if you need something from me.

…

On Tue, Feb 18, 2020, 2:03 AM Goran Blažič ***@***.***> wrote: @Icydeadpeople225 <https://github.com/Icydeadpeople225> hm... you shouldn't have the A revision of the firmware, which is kind of weird, but still shouldn't cause this many issues. of course, having "played" the game of development for quite a while, I'm well aware that "should not cause" doesn't hold much value 🙄 We're working on an update function that could be used by end users (like yourself), but aren't ready with it yet (I won't bore you with the usual story: limited resources and priorities 🙈 ) I'll try to see if it's something we'll be able to move along faster, and let you know when I have more info. In the mean time, I'm reopening this issue (so it doesn't get lost) and assigning myself. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOPYBEWINSMUT7EAOV6YYCDRDOB4HANCNFSM4KRPH56Q> .

[goranche]

well... this will have to be solved by an update function in either the SDK, or (more likely) the official app. We're working on that 👍
I'm closing this till then, though.