Repository navigation
Dual Screen Device Improvements #129
Description
This issue is a collection of feadbacks/improvement suggestions following the initial Armada build with support for the Thor's second screen.
-
Need to suppress KDE's external output picker on first desktop session
-
Add the ability for users to pin their virtual keyboard on the second screen for dual screen devices
-
Only the bottom screen is turning off when closing the lidFixed with f7795bd -
Sliding the combined brightness slider all the way down is leaving both screens completely dark, potentially leaving users stranded without being able to see their screenFixed with 1d4482b
Activity
Zombrexo commentedon Jul 20, 2026
A lot of work/improvements you're bringing forth here for one singular device on an OS that is currently basically in alpha, I think that these types of enhancements probably should be postponed until the OS has come to a stable enough release stage.
Maybe instead bring forth 1-2 suggestions at a time, that would certainly be easier to set aside some time for instead of suggesting what that could become a few weeks of work for one singular device.
Raxcoms commentedon Jul 20, 2026
These were feedbacks given organically throughout the discord server during testing that I was asked to create an issue collecting them here so its easier to keep track of 🙂
virtudude commentedon Jul 20, 2026
Yes, I asked. Didn't want to lose all the feedback. Thanks @Raxcoms.
Zombrexo commentedon Jul 20, 2026
Then I apologize for what I wrote as it was out of place for me to do so since you asked the guy to do so, but don't you think that you're just maybe starting to put a lot of work on yourself, at this point at least link a patreon or something so we can pay you for this.
virtudude commentedon Jul 20, 2026
No apology needed I appreciate people looking out for reasonable scope. I am conflicted on how deep to go with the Thor to be honest. On one hand it's a very popular device but on the other it has a lot of unique needs compared to other devices we support. It's why it's taken me so long to decide which of the Thor PRs to merge. Even when other people do the work dual screen introduces a lot of ongoing complexity to the codebase.
Zombrexo commentedon Jul 21, 2026
For not to mention the issues people keep having with the Thor (me included) and then trying to figure out whether or not those issues are hardware or software related, and whether or not the issues is because the person(s) experiencing them is due to poor QA from AYN or not.
[-]Ayn Thor second screen improvements[/-][+]Dual Screen Device Improvements[/+]tslmy commentedon Aug 1, 2026
Love how we are zooming out from one particular device (AYN Thor) to the whole class of dual-screen devices @JPyke3 . I believe AYN Thor will not be the last flashable model with 2 screens in our human history.
Also, whatever patches we make in this direction will foreseeably help with external display support. Your single-screened device may be dockable someday!
tslmy commentedon Aug 3, 2026
@Raxcoms : Can I propose to add one entry:
"In desktop mode, on-screen keyboard should always appear on the bottom screen, not the active display (which could be the top screen of external monitor). Also filed as a feature request upstream to the KDE project."
I have a PR #194 to satisfy this feature request of my own, if you want to backlink to PRs that aren't merged yet.
Speaking of back linking to PRs, this is where I usually find "one GitHub Issue for many topics" kinda awkward. Do you think we can move to a GitHub Project instead, so that we can have a kanban-style view to all dual-screen-specific asks? This will also pave way to more formal project management and roadmapping.
JPyke3 commentedon Aug 3, 2026
I do generally agree but the awkward thing about dual screen devices is we only support two. So I made a small exception here.
If we would prefer separate issues for all of these we can do that and we can use a dual screen tag or just the tags for these two devices
Raxcoms commentedon Aug 3, 2026
I initially created this issue just to collect a set of comments I had made over on discord.
It was mostly intended as documentation, making use of an issue to to do
I do agree that now that things are more organized and there is work being done for these that we should have multiple issues for these
I've created them and linked to the original post so you guys can locate things more easily 😊
JPyke3 commentedon Aug 3, 2026
Thanks heaps! Going to close this one then. We can track all this individually.