I think I found another bug:
Thanks for the info, @Jojo_Action. Please, could you submit an issue with these details? We can keep track of it there, and I will not forget it… 
Just trying to reproduce to get the issue into the system but that doesn’t seem to be that easy tonight 
I will try for a bit, but maybe it was just a strange occurrence…
No, i cannot reproduce it. And just read the post of @jofemodo underneath while editing…I wish I had saved the snapshot from yesterday but I already deleted it 
I was trying to get into the same situation from yesterday, but I couldn’t get the bug show up again.
Next time I will try to catch it 
Hi @Jojo_Action and others!
Reporting issues is very good because you help developers to improve the software. We really love to receive reports of issues, specially if the report is properly done and include all the needed context details and steps to reproduce the issue, etc.
In the other hand, to avoid generating noise and wasting time in reading/thinking/answering reports about “strange occurrences”, it’s always good practice to try reproducing an issue “from scratch” before reporting it. When reporting a new issue, it’s very important to include all the details (each time you report!): software version, hardware setup, MIDI controllers, etc. If you can capture the issue inside a snapshot, this is fantastic for us.
When you report a new issue, don’t assume developers remember something about your setup / use-case from previous conversations. Perhaps you think it’s redundant, because you know well what is your setup, but developers can’t remember the setup for each user.
Ahhh! And every detail is important for us. Devil is in the little details … 
All the best!
Okay it happened again, and I managed to save a snapshot and take photos:
I was trying some stuff from the driver’s User-Guide just to learn more about the driver’s modes and workflows.
And after some time I had the same case as I described in my post above, but I want to try to give a bit more detail:
Step Sequencer mode and reading along with the Guide. I cannot really tell what exactly, but I guess normal usage…Device-Mode, when I was in the Sequencer’s ZynPad-view where you see all the Pads.Mixpad modeI took this pic for the record:
Then I saved this snapshot:
001-APC driver 01.zss (33.0 KB)
I then removed all, by Main -> Remove all and reloaded the snapshot.
I was surprised with this on the APC:
Mixpad mode be highlit in Device mode
I hope this helps. If you need more info, please let me know.
EDIT: Filed an Issue: Issue: Akai APC Key 25: Driver: Pads from Mixpad mode are visible in Device mode · Issue #1216 · zynthian/zynthian-issue-tracking · GitHub
Thank you @Jojo_Action for taking the time to, very well, document this issue. I’ll have a look as soon as possible!
It happend again:
Hiere I post another 002-faulty APC driver 02.zss (25.3 KB)
Thanks again for the info, and sorry for not being fixed yet… 
Oh no stress…I can work on it anyways…
But I wonder if others can also reproduce it.
If not, why?
Would it also be possible to support the first version of the APC Key25 ?
It would certainly be possible. The major problem is it’s a little hard to develop without the kit in hand, so it’s probably best attempted as modifications of an existing code base by someone who has the piece of kit.
There is a fairly detailed breakdown,assuming no prior knowledge, of the process of actually getting to a position where you can start to code here…
Even if you don’t actually progress the code base having an understanding of quite how the magic is and can be performed is enlightening for everyone. . .
You also get less rook soup doing this so that’s got to be an advantage. . . .