Marcos Scheeren marschr

This is just a dump of some interesting undocumented features of webOS (3.8 specifically, on early 2018 4k LG TV) and other development-related tips.

Homebrew app ideas

OpenVPN frontend (OpenVPN itself is easily buildable and runs on webOS TVs: https://discord.com/channels/407937994037919756/835489130967859251/906943542457401395)
App autostart manager - dynamically update arbitrary app config and register it as input (see Registering an app as an input)
webos-vncserver frontend with autostart option
Package hyperiond into Piccap directly
Quick Screenshot (expose HTTP port that just returns PNG of current screen contents)
Custom IR remote codes editor/updater/blaster

Enable PipeWire on Ubuntu 22.04

This guide is only for original Ubuntu out-of-the-box packages. If you have added a custom PPA like pipewire-debian, you might get into conflicts.

Ubuntu 22.04 has PipeWire partially installed and enabled as it's used by browsers (WebRTC) for recoding the screeen under Wayland. We can enable remaining parts and use PipeWire for audio and Bluetooth instead of PulseAudio.

Starting from WirePlumber version 0.4.8 automatic Bluetooth profile switching (e.g. switching from A2DP to HSP/HFP when an application needs microphone access) is supported. Jammy (22.04) repos provide exactly version 0.4.8. So, we're good.

Based on Debian Wiki, but simplified for Ubuntu 22.04.

tl;dr: Samsung is a bunch of crap company that doesn't inform their customers about serious limitations on their Wearables lineup. Great hardware, dog poo software.

So, what's this about: Samsung omits a bunch of crucial information for consumers anywhere on the Galaxy Watch product pages - at least on those for the Galaxy Watch 4, Galaxy Watch 5 or Galaxy Watch 6.

They omit on the product pages, the pages that should inform a consumer about requirements and limitations, that:

unless you're rooted, the companion phone actually must be a phone, tablets and even phablets like the Galaxy Tab Active 3 are not supported. (If you're rooted, you can patch that away. Just follow along for the guide)
only certain wearables

A Short IPv6 Guide for Home IPv4 Admins

This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.

Let’s begin.

First of all, there are some concepts that one must unlearn from ipv4:

Concept 1

	/*
	root@ArcherC7v5:/# nvrammanager -r /proc/self/fd/1 -p soft-version
	soft_ver:1.1.0 Build 20201120 rel.50406
	fw_id:C339BA6D3F263C8AB6919A76DF430336

	root@ArcherC7v5:/# md5sum /usr/bin/nvrammanager
	404b8d952f7cdc97199a0afc2e081a9a /usr/bin/nvrammanager
	*/

	int nm_checkSoftVer(int param_1,int param_2)


	# This file is responsible for the communicating with the Ollama Server
	import json
	import requests

	class Ollama:
	'''
	This class is responsible for communicating with the Ollama Server.
	The conversation memory is stored inside this class.
	'''