⚠️ USE AT YOUR OWN RISK
Most parameters listed here are undocumented and unsupported by VMware/Broadcom.
Always back up your.vmxfile before editing. Test in non-production environments first.
Parameter availability depends on VMware product version, host OS, andvirtualHW.version.
⚠️ Disclaimer: This guide is provided solely for educational purposes. The creator assumes no responsibility for any damage, data loss, or other adverse effects that may occur as a result of following these instructions. Proceed entirely at your own risk!
Many users who have rooted their devices finds issues where system or third-party applications detect the root status and refuse to operate. This guide outlines a procedure to hide root detection on the majority of Android devices, specifically the ones running Noble ROM for Samsung S9/S9+/N9. The approach detailed here leverages KernelSU-Next in conjunction with SuSFS.
It is exciting to see so many new color features for the CSS Color Module. There are nevertheless a couple items that resulted in a "raised eyebrow response". This Gist is mainly going to focus on one: the use of the LAB version of LCh instead of LUV LCh, which may be better suited for the task but appears to have been dismissed as if irrellevant.
I DISAGREE. Luv is in common use and very relevant, and LuvLCh or one of the several LuvLCh variants has distinct advantages over LabLCh for use cases such as choosing color for web content for displays.
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
| """ | |
| A Bitbucket Builds template for deploying | |
| an application to AWS Elastic Beanstalk | |
| joshcb@amazon.com | |
| v1.0.0 | |
| """ | |
| from __future__ import print_function | |
| import os | |
| import sys | |
| from time import strftime, sleep |
Side note: The latest edge build of KeeAgent plugin offers an option for creating a WSL compatible socket. This would be very handy. I already tried to use that socket, but the socket file is currently empty and ssh inside WSL 2 is unable to use it. This appears to be a very new, unreleased and unstable feature. I will follow the development of it and when it finally works (well, for me) I will update this HOWTO. But until then, please use the proven wsl-ssh-agent/npiperelay.exe approach below.
Thanks to the instructions for WSL 2 of the wsl-ssh-agent project, KeeAgent works great in WSL 2 now:
https://github.com/rupor-github/wsl-ssh-agent#wsl-2-compatibility
The approach uses minimal and well-maintained tools.
- 14.08.2025: Improve: Improve title of this gist.
| //Override in your touch-enabled view (this can be differen than the view you use for displaying the cam preview) | |
| @Override | |
| public boolean onTouch(View view, MotionEvent motionEvent) { | |
| final int actionMasked = motionEvent.getActionMasked(); | |
| if (actionMasked != MotionEvent.ACTION_DOWN) { | |
| return false; | |
| } | |
| if (mManualFocusEngaged) { | |
| Log.d(TAG, "Manual focus already engaged"); | |
| return true; |