AVNC is open source and it at least has a mini keyboard where you can queue Super to be held with your next keypress
https://f-droid.org/en/packages/com.gaurav.avnc/
If you're using a USB or Bluetooth keyboard, it's probably not possible for you to use your actual super key on it. That gets translated to "Home" in Android which is why you go back to your launcher. For whatever you're trying to do, software keys is probably the only option.
That's great, could they fix 4090's literally starving themselves of power and hard crashing unless "Power management mode" is set to "prefer maximum performance?"
This has been an issue since launch. It isn't even the default setting!
Ahhh RVC is the right word for this sort of thing. Thanks! It's crazy that this was a one day project!
Your AI voice in this sounds pretty natural. Did the AI generate this just via text? Or was it "overlayed" to the original V voice? I've never really messed with voice AI before, so learning how you trained it well enough to fit right in with a game would be a pretty interesting read! I'll even take a TL;DR, I know writing takes a while 😅
Keep in mind that Lawnchair is buggy and consistently 2 years behind the latest version of Android. I'm using their 12.1 beta, and it still crashes with null pointer exceptions about twice a week. And, on Android 13 and 14, integration you would expect between the recents screen and Lawnchair does not work. These are the gestures you're talking about.
And here we are on the launch of Android 14, with no development of Lawnchair for Android 13 in sight.
I should also point out, these gestures you're mentioning only work on the stock Pixel launcher, the AOSP launcher, and Lawnchair. This is because starting with Android 9, Google baked the recents switcher directly into the launcher app. And, it has to be a system-level app with a special system config that allows the launcher to perform this function.
This is why root is needed for the Quickswitch module. Lawnchair has the code to do this (at least on Android 12), but you have to overwrite a system config to allow Lawnchair's package name to be capable of serving the recents screen.
There have been a few RCE's for Android 11 and up impacting both Bluetooth and the Baseband.
Bluetooth:
Baseband:
Of course, Android 11 is still supported as of right now, so if you have been getting security updates when available, then you are good. I just know there are phones running 11 and below that don't even get security updates, so those are the people that need to watch out. You can check your Security Patch Level in settings to be sure.
Does the missing comment show up in the Lemmy web UI?
I think this just happens when a comment gets deleted. Sync can show the child comments, but the Lemmy UI just hides the entire thread.
I run my own Lemmy instance, there is an option on my administration page called "blocked instances." I've added it there.
Thank you! I'll look into reducing the log spam.
Try again with the latest version of Lemmy Easy Deploy.
I am now building multiarch images for 0.18.x, and my script will now default to my multiarch images, so there is no longer a need to build it yourself :)
Before this week, I would have told you no. But I have big plans for the 0.18.1 update.
The Lemmy team has completely broken ARM support with seemingly no plan to support it again. They switched to a base Docker image that only supports x86_64. This is why your build fails. I still don't understand why they would move from a multiarch image to an x86_64-only one.
I've been working on this for about a week, and just yesterday I finished a GitHub Actions pipeline that builds multiarch images for x64/arm/arm64. I currently have successful builds for 0.18.1-rc.2. In a future update for my script, I will have it use these, that way ARM users don't need to compile it anymore. I just ask for a little patience, I haven't been able to do any work on Lemmy Easy Deploy since I've been working on this pipeline :)
I also do want to qualify - don't get your hopes up until you see it running for yourself. Ultimately, I am just a DevOps guy, not a Lemmy maintainer. I haven't tested my ARM images yet, and while I did my best to get these to build properly, I can't fix everything. If anything else breaks due to running on ARM, it will be up to the Lemmy team to fix those issues (which is not likely anytime soon, if their updated x86_64 Dockerfiles are any indication).
But, fingers crossed everything goes smoothly! Keep an eye out for an update, I'm working hard on it, hopefully I can get it out in time for 0.18.1!
EDIT:
Of course I had to just go and open my mouth. This doesn't look good. I may need to remove ARM support from Lemmy Easy Deploy entirely until Lemmy figures this out :/
Be aware, it's not free as in costs $0, it's free as a "Giveaway," where you must accept these terms: