Skip to content

Conversation

@SebiAi
Copy link
Contributor

@SebiAi SebiAi commented Mar 19, 2025

The original text specifies that it checks for the Pro only. But the function checks if the model string of the device contains A059 which therefore also supports the pro's model string of A059P.

I don't have a 3a and 3a Pro to test this but from what I can see from the decompiled code this should be the right and originally intended description.


Mentioning this here because I doubt that the issues will be read any time soon - this was found by @Fr4nKB, all credits of the below described findings go to him:

The mapping of the glyphs to the A_#, B_# and C_# constants might be wrong:
image
There seems to be a deviation between the documentation and how many zones each of the A_#, B_# and C_# constants have.
A_# should have A_1 to A_20 constants according to the documentation - the other constants are therefore also not aligned with the doc.

I would appreciate it if I could get in personal contact with the person running this project.

The original text specifies that it checks for the Pro only. But the function checks if the model string of the device *contains* `A059` which therefore also supports the pro's model string of `A059P`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant