works for me both on my archlinux machine and my steamdeck with steam and non-steam games. I’ve even played NFSU2 with it =] . I don’t think it required any more configuration than just pairing for me, no special drivers or tools. Maybe it needs a firmware update (I don’t know if that’s a thing, just a thought)?
Ah, I should have been more clear. The CRITERIA section of the sway documentation states that class matches support regex, so instead of using a * as you did in your example you’d use a regex any .*. So I think (untested of course) that for_window [class="steam_app_.*"] allow_tearing yes should work.
The comment in the code for allow_tearing notes that it must be enabled on the output as well. Here is the relevant output documentation. There are several other notes/recommendations there as well you should probably pay attention to.
Are your games all wine/proton games? For me in sway they all have the same class followed by some uid thing:
] > swaymsg -t get_tree
[...]
#92: output "DP-5"
#70: workspace "21"
#126: con "Automobilista 2" (xwayland, pid: 171976, instance: "steam_app_1066890", class: "steam_app_1066890", X11 window: 0x5400001)
Or gamescope:
] > swaymsg -t get_tree
[...]
#92: output "DP-5"
#70: workspace "21"
#124: con "Assetto Corsa" (xdg_shell, pid: 170694, app_id: "gamescope")
EDIT: Also allow_tearing was added to master 3 weeks ago, so this is definitely not in the current release. FYI to anyone who might try it.
Gatgetbridge (your link) has a breakdown of devices they support https://gadgetbridge.org/gadgets/ . You can click through the vendors to find devices which are both “highly supported” and “no vendor-pair”. Meaning most/all the features work without any reliance on the vendor app.
As for the similarity you are asking about with pixel->GrapheneOS, there are very few watches that can run an alternative open source firmware or operating systems apart from the ones that are already open source, like bangle.js, pinetime, etc. Wearables are even more specialized than phones, they require specialized code designed specifically for them and would likely require pretty extreme effort to reverse-engineer.
I use a pebble 2 HR with gadgetbridge but the watch it self runs the old pebble firmware which gadgetbridge talks to. This is fine for me, but if you are looking for a more modern watch you may have to make some compromises.
AOSP gallery that comes with GrapheneOS. The app info says it’s called com.android.gallery3d. There’s some info here in the docs about the relationship between camera, edit functions, and the gallery app.
No, I don’t have markup installed (it is there in apps but not installed from the mirror).
I think in my case the screenshot functionality is built into AOSP and the editor you get when tapping the resulting preview overlay in the lower left corner of the screen is part of the “gallery” app since using the “edit” feature from gallery launches the same editor. Maybe GrapheneOS just sets that as the default editor, I’m not sure.
What android OS do you use? On stock Android 14 (GrapheneOS, but it’s not a GOS feature) this functionality is built into the stock screenshot tool.
pwr+voldown -> tap screenshot that appears in the overlay after you take it -> tap the crop tool . I suppose step three could be removed but what if you want to do something that isn’t cropping? There are lots of other features so at some point you have to tell the tool what you want to do.
broad support for generic smart watches
Gadgetbridge is pretty well on it’s way to this. They roll out support for new devices monthly it seems like. Of course there are always feature X and Y that fitbit or garmin does that it doesn’t, but it’s quite an impressive project. I use it with a pebble 2 HR.
Memories and Gallery (actually deprecated by photos) are not the same thing, just to clarify. I’m not in a position to agree or disagree with any of the statements here since I’ve never used immich, but I don’t want people to think that the default photo viewer in nextcloud is what was being discussed here.
If you want to monitor sleep with it charging at night isn’t possible, and remembering to charge every single day during the day is annoying in my opinion. Not everyone wants sleep monitoring though, or likes to sleep with a watch on, so I get why there’s some division on the subject.
My pebble 2 hr lasts about 5 days and I’m very happy with that frequency of charging. I think it was a bit better when new but that was a long time ago.
hmm, or bluedat
wrotedat
TIL the Cammus C5 works as a generic HID Force Feedback device in Linux. That really makes up for the weird marketing.
I’ll be honest, I did not expect to ever hear another person mention Foobar2000 ever again. And now to learn they have an android app!!! Hmm, may have to use that for a bit just for nostalgia sake.
I also use Vimeo for videos I can’t send directly to people or host my self. For example if I post a FreeCAD howto I put it there so I can link to it from comments and stuff and I know everyone will be able to play it. While it’s not open source, It’s really pretty great as an alternative platform with all the youtube like features and more (you can change your video title if you make a mistake for example).
Thanks, that’s really great info! Aaaannd just like that the stack of keyboard boxes gets a little higher and my wallet gets a little lighter =]
The bottom three boards are a Japanese layout with ISO English keycaps right? Are the function layers programmable on those? I’ve always wondered.
I use a Tex Yoda II and operate the function layer with my thumb on the middle trackpoint mouse button so very little movement is required (see image). I have always loved my Topre boards though and would like to replicate this convenience on something using Topre. The Japanese layout with extra bottom row keys and a smaller spacebar seems perfect in theory. It’s a lot of money to spend on something I might not be able to use at all if it’s not programmable though.
Yeah honestly the aliexpress listings are more detailed than a lot of the sites that have been suggested or that I’ve been able to find on my own. Maybe I should just suck it up and get them there.
Weird coincidence that the exact reason for this thread is addressed in https://github.com/nextcloud/android/releases/tag/rc-3.35.0-01. RC2 was just released yesterday.