You can already run Linux apps using Termux and Termux-X11, and I’d say the performance would be better than this demo, because this is running in a virtual machine and uses it’s own kernel, whereas with Termux you’re running your apps directly on top of the Android Linux kernel. Also, you don’t have the overhead of running ChromeOS on top of Android.
And this is one of the reasons why I don’t like 'em. They’re way too overengineered, IMO. Which is weird because so many mk enthusiasts prefer minimal setups. In my case for instance, I just have a braided Type-C cable running straight from my board to the back of my desk. Just a simple, straight line. Easy to connect/disconnect/clean/maintain/replace. Minimal. I personally don’t see why/how an aviator cable could improve either the aesthetics or the functionality. In fact, I can only think of downsides.
Samsung midrangers like the A15 / M15 / A25 etc have both the jack as well as an sdcard slot. There’s also the Motorola G34 and the G84. And finally, there’s also a flagship - the ASUS ROG Phone 8 Pro. And a whole bunch of Chinese phones which I won’t bother mentioning.
That 240W is only for SuperVOOC. PD however goes only upto 65W. Plus, being that big and single-port only makes this thing completely pointless for everyone except VOOC users.
It’s easiest to just register a domain name and use Couldflare Tunnels. No need to worry about dynamic DNS, port forwarding etc. Plus, you have the security advantages of DDoS protection and firewall (WAF). Finally, you get portability - you can change your ISP, router or even move your entire lab into the cloud if you wanted to, and you won’t need to change a single thing.
I have a lab set up on my mini PC that I often take to work with me, and it works the same regardless of whether it’s going thru my work’s restricted proxy or the NAT at home. Zero config required on the network side.
This shouldn’t even be a question lol. Even if you aren’t worried about theft, encryption has a nice bonus: you don’t have to worry about secure erasing your drives when you want to get rid of them. I mean, sure it’s not that big of a deal to wipe a drive, but sometimes you’re unable to do so - for instance, the drive could fail and you may not be able to do the wipe. So you end up getting rid of the drive as-is, but an opportunist could get a hold of that drive and attempt to repair it and recover your data. Or maybe the drive fails, but it’s still under warranty and you want to RMA it - with encryption on, you don’t have to worry about some random accessing your data.
AIO Launcher - not for everyone, but I prefer function over form. :)
No, you’re right. There’s no organisation options. It’s pretty barebones overall, and doesn’t look great on large foldables either. Guess there’s no reason to switch from my current launcher.
Well yeah, you need the full name of the file. PowerShell will not automatically asumme the extension of a file.
Also that empty string error means there’s a blank line somewhere in your input list, so you’ll need to get rid of that.
Ah, I misplaced a quote in my code, I’ve update the post - try version.
deleted by creator
That means there’s a duplicate entry, check the full error message for the file name. You can also use the -Verbose switch to see what’s going on.
There’s no point in having a CSV for just a single column, just make it a simple text file and it’ll simplify the code a bit. So assuming you have a file called names.txt, here’s a one-liner that can do the trick:
$names = cat "\path\to\names.txt"; $i=0; dir | % { ren $_ "$($names[$i])"; $i++ }
As long as the order in your text file matches the order shown by dir, you shouldn’t have any issues. Maybe do a dry run with a -WhatIf to the ren first to see how the files are being renamed, before you do the actual rename. :)
I’m not familiar with GMMK boards, usually you’d use dfu-util to flash the QMK firmware, maybe if you can save/extract the firmware bin file from the exe (dry run it in Wine perhaps?), you could flash it using dfu. But I’d first check if your board supports that.
But you could always just install Windows to a USB stick and boot from it, you don’t need to find a separate Windows machine. I mean, you don’t even need to even buy a license or anything so you’ve got nothing to lose here.
And in case you’ve got an existing Ventoy USB, then you can just install Windows in a VM, and drop the VHD into your Ventoy USB so it doesn’t pollute your drive with a bunch of files. You’ll end up with a nice and self-contained copy of Windows, just like any other Linux ISO, and you can use it in situations like this without feeling guilty of dirtying your PC.
Neither do most phones these days unfortunately. The ones that do have them are not mainstream phones, which means the chances of a fully working custom ROM for them is next to zero.
And refactor the code a bit to be on the safe side - change the name of the project and remove any references to litigious companies. And use an anonymous handle + VPN/proxy chains so they can’t sue you.
Honestly it boggles my mind that devs contribute to emulators like these using identifiable names and traceable IPs, when everyone knows how these greedy corporations operate. Did no one learn anything from the Sony vs Geohotz case, or all the subsequent takedown against emulators? Why do these devs keep falling into the same trap again and again?
They don’t have to be financial - many corporate apps will not work on custom ROMs - the most popular ones being the ones by Microsoft - eg Teams, Outlook etc.
Similarly, some games may also not work, such as all the ones by Niantic (Ingress, Pokemon Go etc) and typically many online multiplayer games.
Finally, this will also affect popular streaming media services, such as Netflix, Amazon Prime etc.
There are workarounds for some of these - some with certain compromises - but there’s no guarantee that they’ll continue to work. So before you look into any workarounds (if you use the above three categories of apps), know that it’s a constant game of cat-and-mouse, so it’s not for the faint hearted.
I doubt this is an Akko-specific issue- most keyboards should be using the standard USB HID drivers built into the kernel. This has most likely got something to do with your DE or distro config, maybe an error in a config file somewhere, or some script/plugin behaving funky. I know in the past KDE’s Snap Assist plugin was known to cause the keyboard to stop working; kwin scripts could also do weird things. Or could be a third-party program, like a keyboard remapper (kmonad, wayland-mouse-mapper, kbct etc).
You could try switching to a different DE temporarily to rule out a DE issue, but before you do that, maybe boot from a live USB of a different DE or distro (or maybe even try two ISOs of your current distro - one ISO with whatever DE you’re using currently, and another ISO with a different DE) and see if it works in there? You could create a Ventoy live USB to make it easy - just dump all the different ISOs on the drive and you can select which them when booting.
If, in your testing, you find that your keyboard works fine with the same distro and DE, then it would point to a config issue. In that case, the easiest fix is to just blow your .config folders away (or create a new user account) and start fresh.
But if in your testing you find that the keyboard works under a different DE but not the one you’re using, then it’s likely a bug with the DE, so perhaps consider filing a bug report. But maybe try the same DE with a different distro first to make sure it’s not a distro-specific bug.
Does it also intelligently merge/hide duplicate articles from different sources?
Bazzite. Here’s why:
But since you said:
and if you’re really serious about squeezing the best performance, then check out the Arch-based CachyOS - unlike most other Linux distros, Cachy has optimised x86-64-v3 and v4 packages in their repos, which means apps can make use of advanced CPU instructions such as SSE3, AVX512 etc. Most other Linux distros on the other hand still use x86-64-v1 for compatibility reasons, which unfortunately means that you’d be missing out on all the cool new optimised CPU instructions introduced over the past 16 years.
You can read more about microarchitecture levels (aka
MARCH) here: https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levelsIn addition to the
MARCH, Cachy’s packages have other optimisations such as LTO/PGO, optimised kernel with the BORE and Rusty schedulers which are better for gaming, plus several performance-oriented tweaks which you’d otherwise have to do manually on Arch (such as makepkg.conf tweaks, pacman.conf tweaks etc).Finally, Cachy are always on the bleeding edge when it comes to gaming/driver/kernel/performance related stuff, so you’ll get all the good stuff even before Bazzite or other optimised distros. For instance, Cachy was the first distro to include the new nVidia driver which has explicit sync support for better Wayland compatibility, and they’re always on top of major Arch developments and provide detailed announcements which are relevant to gamers and performance freaks.
Eg, here’s their recent recent nVidia announcement:
So as you can see, they’re pretty on to it with this sorta stuff.
Now the Bazzite team are also like the Cachy guys and keep up with this stuff, but because they’re based on Fedora, they can’t be as bleeding edge or as optimised as Arch. So it’s up to you - if you prefer stability, a primarily gaming-focused optimisations, and want something that “just works” then get Bazzite; or if you want an ultra-optimised distro to squeeze out the most performance out of your box but also don’t mind ocassionally diving into the terminal and getting your hands dirty, then get CachyOS.
cc: @01189998819991197253@infosec.pub