InfiniTimeOrg / InfiniTime

Firmware for Pinetime smartwatch written in C++ and based on FreeRTOS
GNU General Public License v3.0
2.76k stars 944 forks source link

Visual glitch when turning on the screen after initiating a firmware update #295

Closed n0toose closed 3 years ago

n0toose commented 3 years ago

Steps to reproduce

joaquimorg commented 3 years ago

Please indicate the version you are running, if possible an image of the problem.

joaquimorg commented 3 years ago

I think that RC2 solves the reported problem.

n0toose commented 3 years ago

I think that RC2 solves the reported problem.

I managed to reproduce it immediately after updating to RC2 too. I'll give it another shot as I'm setting up my development environment.

petterhs commented 3 years ago

Fix should be in RC3

n0toose commented 3 years ago

I completely missed this.

n0toose commented 3 years ago

I'll give it another shot and try to break it then promptly close the issue.

joaquimorg commented 3 years ago

I think that RC2 solves the reported problem.

Yes the fix is in RC3, my mistake.

JF002 commented 3 years ago

@panos Do you confirm this issue is fixed in RC3?

n0toose commented 3 years ago

Sort of. It looks okay, visually. However, I scrolled away from the "Firmware update" screen, turned off the screen and turned it back on. That resulted in a crash, which I did manage to reproduce in the earlier versions as well before, but I was a bit confused by the visual glitches and assumed that the issues were connected.

n0toose commented 3 years ago

It's not the exact same as the thing I reported initially, which has been resolved, but it's just a small difference in the steps.

pfeerick commented 3 years ago

I can reproduce it... one nice thing with DFU being able to recover mid update now though is that after the reset the update will auto restart (with nrf connect, at least)... gadgetbridge is refusing to do updates... unknown element or some other obscure and unhelp error message.

n0toose commented 3 years ago

Gadgetbridge is refusing to do updates... unknown element or some other obscure and unhelp error message.

Disconnecting and reconnecting the watch helps.

pfeerick commented 3 years ago

lol... I have no luck ever getting gadgetbridge to do an update... only had it even attempt to do it once... and that failed... I try it every now and then when doing different DFU updates and it spits that error out... so I stick with NRFConnect as it consistently 'just works'. I'll certainly give that a try next time, as I do want to give it a chance ;)

n0toose commented 3 years ago

lol... I have no luck ever getting gadgetbridge to do an update... only had it even attempt to do it once... and that failed... I try it every now and then when doing different DFU updates and it spits that error out... so I stick with NRFConnect as it consistently 'just works'. I'll certainly give that a try next time, as I do want to give it a chance ;)

It's a bit bootleg, but you can also try renaming the .bin file in the releases and appending a .fw prefix. That's what I did when I needed to get out of Pinetime-Lite and use Infinitime instead.

JF002 commented 3 years ago

I'll close this issue. Please open another one regarding the crash during the OTA when leaving the firmware update screen if it's still present in 1.0.