JOBIANS TECHIE Jobians

Elink ECast STB remote (Node.js)

Control an Elink "ECast" set-top box (the boxes driven by the Android app com.elink.stb.elinkcast) from Node.js or Termux, without the app. Written by reverse-engineering the app's network protocol.

Zero dependencies. Node 14+.

Not affiliated with Elink. For controlling devices you own.

Quick start

Running a real Linux userland (Alpine via proot) inside a standalone Android app

A working, no-root, no-Termux-dependency recipe for chrooting into a Linux rootfs from your own Android app. This documents every wall hit along the way and the actual fix for each, since most of the failure modes here are non-obvious and under-documented.

End result

Bundling proot (or any Termux binary) inside an Android app

This is a recipe for taking a binary/library built for Termux and getting it running inside your own Android app via ProcessBuilder, without root.

Why this works

Termux builds its packages against Bionic libc using the Android NDK, so the resulting binaries are already ABI-compatible with plain Android apps. The trick is just:

Getting the files into a location Android will grant execute permission on.

Here’s a simple GitHub Gist version you can paste directly:

Fix QEMU Debian No Internet

Problem

No internet in Debian VM:

ping fails
DNS not working
ens3 is DOWN

Vite React next-themes Dark Mode Fix

Minimal <head> snippet to prevent the flash of white background (FOUC) in Vite React SPAs using next-themes (chakra ui).

<head>
    <meta charset="UTF-8" />
    <link rel="icon" type="image/svg+xml" href="/vite.svg" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>App</title>

🧩 QEMU Performance Comparison Summary

Host: Termux on Android (ARM64 / aarch64)
Device: Android phone running Termux
Virtualization: QEMU emulation (no KVM acceleration)

🖥️ Virtual Machines Compared

VM	QEMU Command	Architecture	Notes
🟢 ARM64 Guest	`qemu-system-aarch64`	ARM64 on ARM64	Native architecture, efficient
🔴 x86_64 Guest	`qemu-system-x86_64`	x86 emulated on ARM	Heavy software emulation via TCG

🛠️ Android Emulator Crash FIX — `StartService FAILED with error 4294967201`

❗ Problem

When launching the Android Emulator, I kept getting this vague and frustrating error:

Running Android Emulator hypervisor driver installer
[SC] StartService FAILED with error 4294967201
The emulator process for AVD  has terminated.

	#!/bin/bash
	# Configure GRUB for serial console in Debian (Termux-friendly)

	GRUB_FILE="/etc/default/grub"
	BACKUP_FILE="/etc/default/grub.bak.$(date +%F-%T)"

	echo "🔹 Backing up current GRUB config to $BACKUP_FILE"
	sudo cp "$GRUB_FILE" "$BACKUP_FILE"

	echo "🔹 Configuring GRUB for serial console..."

	async function getFinalUrl(inputUrl) {
	// Extract the ID from the input URL, https://adrinolinks.com/{id}
	const idMatch = inputUrl.match(/\/([^\/]+)$/);
	if (!idMatch) {
	throw new Error("Invalid URL format, can't extract ID");
	}
	const id = idMatch[1];

	const url = `https://tackledsoul.com/includes/open.php?id=${id}`;

	const crypto = require('crypto');
	const {
	TextDecoder
	} = require('util');

	// Static Key and IV (from client JS)
	const base64IV = "Wzk3LCAxMDksIC0xMDAsIC05MCwgMTIyLCAtMTI0LCAxMSwgLTY5LCAtNDIsIDExNSwgLTU4LCAtNjcsIDQzLCAtNzUsIDMxLCA3NF0=";
	const base64Key = "Wy0zLCAtMTEyLCAxNSwgLTEyNCwgLTcxLCAzMywgLTg0LCAxMDksIDU3LCAtMTI3LCAxMDcsIC00NiwgMTIyLCA0OCwgODIsIC0xMjYsIDQ3LCA3NiwgLTEyNywgNjUsIDc1LCAxMTMsIC0xMjEsIDg5LCAtNzEsIDUwLCAtODMsIDg2LCA5MiwgLTQ2LCA0OSwgNTZd";

	function parseKey(base64Str) {