Touch controller error warning on PineTime

[Elara6331]

• I searched for similar bug reports and found none was relevant.

What happened?

Touch controller error warning appears on PineTime on boot

What should happen instead?

Touch controller error warning should not appear on PineTime

Reproduction steps

• Install the DFU artifact from Add motion service #754
• Reboot PineTime

More details?

This did not happen before installing the artifact from the mentioned PR.
After tapping Proceed, touch works as expected.

Version

add-motion-service

Companion app

No response

[Riksu9000]

If you have an issue with a PR, it should be mentioned in the PR instead, but this may not be related to that PR specifically as it doesn't change the code relevant for detecting the error.

I couldn't reproduce the issue. Did you validate the add-motion-service firmware after you flashed it? If not, what was the version that it rolled back to? Did you reset by pressing reset in the validation dialog or by long pressing the button? What is the value of Touch. in the about screen? The error is shown if it is something other than b4.0.1.

[Elara6331]

If you have an issue with a PR, it should be mentioned in the PR instead, but this may not be related to that PR specifically as it doesn't change the code relevant for detecting the error.

Yes, I realized that and believe it has to do with one of the changes for 1.7.0 since the PR was in that milestone. I mentioned the PR because I wanted to make sure there wasn't something wrong there specifically, though that is unlikely.

I couldn't reproduce the issue. Did you validate the add-motion-service firmware after you flashed it? If not, what was the version that it rolled back to? Did you reset by pressing reset in the validation dialog or by long pressing the button? What is the value of Touch. in the about screen? The error is shown if it is something other than b4.0.1.

Yes, I validated it. All I see in the touch field is 0.0.0.

[Elara6331]

Interesting. It now says 0.1.1

[Riksu9000]

I suspect that your watch may have unfortunately ended up with a different touch sensor. When did you get your PineTime? @JF002 has mentioned receiving PineTimes with wrong sensors before and that Pine64 has had to refuse a batch due to a wrong sensor #489 (comment).

If your watch works fine, then you can just ignore the warning. If this issue is widespread, then the error detection might need to be removed, as it would show too many false positives.

If we were to release 1.7.0 with this error detection, we should definitely warn users that it may trigger false positives and that they should report whatever the Touch. value is here. @JF002

[Elara6331]

I got it a couple weeks ago. The touch does work fine (other than the random touch inputs which others also seem to experience).

[geekbozu]

I'm also getting this on my development kit Riksu, Which is running current dev+ some patches. It also does not happen everytime. I will look into it more soon :)

[JF002]

This feature was added in #489, and it looks quite safe as all PineTime should be equipped with the same CST816S touch controller.
I knew that one batch of PineTime was returned to factory because they mounted the wrong controller, but as far as I know, those units were never shipped to end users.

So, if we saw this error message on actual PineTimes, we might have an issue in the code that detects the controller or we are facing some unknown variation of the hardware..

@geekbozu Could you investigate this on your device? Does the touch controller returns another device ID, or is there any error in the code? Thanks!

[kieranc]

I also see this error intermittently on my watch which was in the mid July 2021 batch
I just checked about when it happened and it was showing 'touch. b4.0.ff'

[Elara6331]

Something very strange seems to be going on. I checked the about screen again and it changed again to b4.1.1. Then, I left the screen and scrolled a bit. InfiniTime crashed (possibly unrelated), and then when it rebooted, there was no warning and the value was b4.0.1.

[JF002]

Here's a picture on a devkit equipped with the wrong touch controller (this is a proto version and it was never releases (and never will) to the public. IIRC, this is a CST716 instead of the CST816. It doesn't work properly on InfiniTime as it does not support all gestures we need.

As you can see, the version detected is 20.80.2 (chip.vendor.version).
I would have expected the vendor ID to be the same on both device, but that's not the case.
This makes me think that those ID might not be as reliable as we would like... or maybe there are multiple "vendors" for the same chip? or clones?

Also, I couldn't reproduce the behavior detailed by @kieranc and @Arsen6331 (the ID that are different from time to time), even after reseting my units multiple times...