pengchujin/aerial-tv

This page introduces an external open-source repository. It is not an HDATF product.

What it does

Aerial is an Android TV home-screen app that shows applications and wallpaper instead of advertisements and recommendation feeds. Its main users are owners seeking a different launcher for televisions such as Xiaomi and TCL models. Remote input, installed applications, input sources and photos produce an app grid, control center and screensavers. It uses Kotlin and Jetpack Compose, while a QR-linked phone page supports photo uploads and wallpaper settings. Deployment requires APK installation, TV-side ADB approval and permission configuration, with a documented restoration path that does not delete system apps. Source builds require JDK 17 and Android SDK 36. Aerial videos and daily backgrounds use external Apple and Bing materials, so connectivity and separate copyright conditions matter. Default-launcher recovery and startup behavior vary by device, and elevated permissions and optional persistent ADB require careful review.

License

MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.

More in this category

• tywr/Nordwand-Mono
  Nordwand Mono is a compact monospace font project for developers' editors and terminals. Characters and font settings determine code and symbol rendering in fixed-width cells. Alternative glyphs and OpenType stylistic sets provide selectable arrow ligatures and joined repeated symbols. These features need explicit editor or terminal configuration and do not automatically apply everywhere. Custom font generation requires Python 3.11 or newer, font-building dependencies and a configuration file. The README describes drawing glyphs with Python classes and adjusting dimensions such as height. It warns that changed metrics may require manual glyph corrections. Separately from GitHub's headline license, the font files have a SIL Open Font License 1.1 notice, so distribution must distinguish code and font terms.
• Gathin23/cleanyourtv
  This is a collection of a launcher, per-device package lists, an assistant prompt and management tools for owners who want a simpler Android TV or Google TV home screen. Inputs are the TV model, installed apps, features to retain and the desired home layout. A computer on the same network inspects the TV through an explicitly authorized ADB connection and disables selected packages rather than uninstalling them. A Java launcher then supplies a favorite-app dock and an app grid and becomes the default Home. Themes use configuration files and artwork, while cards declared by other apps appear only after owner approval. Getting started requires developer options and debugging approval on the TV and a Python environment on the computer; building the launcher also requires JDK 17 and Android SDK 34. The restore tool re-enables packages from the applied list and restores the stock launcher, but cannot undo unrelated changes outside that list. Fire TV supports the debloating portion only, and this Android launcher does not target Samsung Tizen or LG webOS. Review the device-specific list and recovery path first because needed apps or update services can be disabled, and turn debugging off afterward.
• PC2005-cloud/dsh-pet
  dsh-pet is a DeepSeek Harness plugin that presents execution state through animated characters and speech bubbles, alongside a workflow for making character assets. Inputs include session and tool events, display settings, animations and responses from a selected model. A browser overlay and transparent Electron windows show working, waiting, success and error states, with dragging and multiple characters. The state-processing source distinguishes an intermediate tool result from completion of the whole goal to avoid premature success during automatic continuation. Registration in the host's plugin manager must be followed by a restart, and desktop mode may download Electron if the runtime is absent. Chat and usage displays depend on host models and provider credentials; standalone mode supplies animation but not host-dependent chat or usage functions. A local HTTP API exposes state and animation and bubble control without authentication and must not be published externally. Custom assets require separate video generation, transparency processing, normalization and conversion, while Safari transparency needs alternate assets and configuration. Code is described as MIT, but animations, prompts and source videos carry a non-commercial restriction and separate attribution requirements, so code and asset rights must be distinguished.
• tangency-labs/solidcraft
  SolidCraft is a Rust parametric 3D CAD application for parts rebuilt from dimensions. Designers supply sketches, dimensions and constraints, then build solids through timeline features such as extrusion and fillets. Parameter changes recompute affected geometry. Outputs include design files, exchange geometry such as STEP and STL, and preview images. Desktop, browser and headless CLI interfaces are provided, with JSON command examples. Its MCP server lets an AI invoke the same design commands, measure parts and inspect images. AI operation requires a separately connected MCP client; controlling a running desktop app needs an additional bridge configuration. The project describes itself as early but usable for simple parts, and reference-part tests do not establish full CAD equivalence. Download packages are not yet signed, and automation file-access boundaries need review.
• anujasid/mcp-for-blender-pro
  This is a Blender extension with an AI chat workspace and a built-in MCP server for artists, technical artists and developers automating scene work. It combines a creative request with scene and object information, then uses tools to create or edit objects, assign materials, capture the viewport or prepare scene exports. A companion Studio window exposes conversation, scene previews, approvals and a task board. The documented team workflow uses a manager, workers and reviewers in sequence, with one correction attempt before a second failed review stops the chain. The release targets Windows x64 with Blender 4.2 or later, and setup additionally requires a selected tool-capable model and configured cloud credentials or a local model endpoint. External MCP clients require the server to be enabled and an authenticated local connection, while OpenCode keeps its provider credentials separate from Blender profiles. Asset services may require additional keys and their assets retain separate licensing obligations. Approval and Python validation are not a security sandbox, external clients control their own approval policies, and the implementation and resulting scene quality were not independently tested here.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.