Colors invert randomly

[Alerymin]

Verification

• I searched for similar bug reports (including closed issues) and found none was relevant.

What happened?

Colors inverted for no apparent reason

What should happen instead?

Colors should stay the same

Reproduction steps

?

More details?

Looks similar to #1022 but did not happen when charging
Happened on 2 different Infinitime watches

Version

1.14.0

Companion app

No response

[KaffeinatedKat]

yea i'm really not sure why this happens, and i've seen it occur multiple times while working with the display driver. My best guess is there is some issue with how we are writing to the LCD control register, and accidentally (perhaps an overflow) writing the command to invert the colors. I'll have to do some investigation to be sure though

[riban-bw]

I have seen this happen. Would a (temporary) work-around be to assert the flag to not invert colours when accessing a screen, e.g. watchface / info.

[DEPSUT]

This has happened to me, but I know a way of reproducing this issue.

You need to turn on lower wrist to put the watch to sleep and go to the paint app, then just keep holding the screen and lower it until the screen turns off, and after you turn the screen on again, all the colors are inverted, I have attached a video showing it.

It may have something to do with the issue #1992

20240131_175223_1.mp4

[KaffeinatedKat]

I can reproduce this as well. This issue seems to also be the roots of the issue we're experiencing with #1869 (#1869 (comment)). There is some kind of issue with how the display is being controlled (SPI), which is causing unexpected behavior with the display

[mark9064]

Having a consistent repro is amazing, thanks!!!!

[Alerymin]

I managed to trigger this bug by turning off and on multiple times the watch. I never managed to reproduce it though.

[JF002]

I've just merged @2046 #2046 ! This issue will hopefully not occur again :)
Thanks to @mark9064 for their great work!

[Saarsk]

I've just merged @2046!

I think maybe you didn't intend to @ the user 2046 but instead refer to #2046? :)

[JF002]

I think maybe you didn't intend to @ the user 2046 but instead refer to #2046? :)

You're right, thanks for letting me know about this typo (and sorry to user 2046 for the unexpected ping :) ).

[Ghoelian]

I just ran into this issue for the first time, running on the latest commit on main right now (commit 79ee886). Looks like it's not entirely fixed yet.

[Ghoelian]

Actually sorry nevermind, I didn't validate the firmware so it reverted back to some other commit I don't remember.

[Ghoelian]

Hey it's me again. The issue just resurfaced, this time on 1.15.0 (my own fork though).

Here's some pictures:

[KaffeinatedKat]

what does your fork modiy? This bug should no longer be possible with the fix that was merged - John Crawford Sent from Proton Mail Android

…

-------- Original Message --------

On 2/25/25 01:17, Julian Vos wrote: Hey it's me again. The issue just resurfaced, this time on 1.15.0 (my own fork though). Here's some pictures: [PXL_20250225_080900465.jpg (view on web)](https://github.com/user-attachments/assets/fe757c7c-f748-45db-8276-b6662ff82f5a) [PXL_20250225_080837832.jpg (view on web)](https://github.com/user-attachments/assets/76dbde92-fa0b-4358-8313-1266e260c797) — Reply to this email directly, [view it on GitHub](#1984 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AOVXCZESGE6JFRZQXG66FA32RQRLDAVCNFSM6AAAAABS4FKBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRGA3DSMBZGI). You are receiving this because you commented.Message ID: ***@***.***> [Ghoelian]Ghoelian left a comment [(InfiniTimeOrg/InfiniTime#1984)](#1984 (comment)) Hey it's me again. The issue just resurfaced, this time on 1.15.0 (my own fork though). Here's some pictures: [PXL_20250225_080900465.jpg (view on web)](https://github.com/user-attachments/assets/fe757c7c-f748-45db-8276-b6662ff82f5a) [PXL_20250225_080837832.jpg (view on web)](https://github.com/user-attachments/assets/76dbde92-fa0b-4358-8313-1266e260c797) — Reply to this email directly, [view it on GitHub](#1984 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AOVXCZESGE6JFRZQXG66FA32RQRLDAVCNFSM6AAAAABS4FKBQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRGA3DSMBZGI). You are receiving this because you commented.Message ID: ***@***.***>

[Ghoelian]

OTOH I added 2 settings related to vibration, and added a weather controller to a watchface. Could that have anything to do with this bug?

I'll look at the diff when I get home to be sure.

[9cxndy]

I got hit by this as well. didn't happen when charging, lower wrist is turned on. I am running 728da0f with the background heartrate PR (#1718)

edit: repro method in this issue doesn't work. there probably is another way to trigger this bug. this just happened randomly to me so i don't know how this happened.