TetoTV Beta

A TV-first media library, playback, and tracking client for Android TV, Google TV, Fire TV, tablets, and phones.

Download Beta · What's new · Report an issue · Discord · YouTube

TetoTV runs directly on the Android device with no companion server required for normal browsing and playback. This repository contains the complete application source and the Beta release channel—not only APK downloads.

Watch the TetoTV setup walkthrough

These captures use synthetic demo titles and local fixtures. The displayed QR points to a reserved .example domain and is not a live pairing session.

The Public updater repository intentionally has no release while the Public build is held for review. Existing Beta installations continue to update from the Beta repository. Android never permits an in-place install of an APK with a lower build code; Developer Mode does not bypass that platform rule.

TetoTV's Modern Layout is built around visible focus, predictable D-pad movement, large-screen spacing, and a reliable path back to navigation. Google TV devices use the Android TV build. Android phones use the same theme and features with a bottom navigation bar in portrait and a left rail in landscape.

The phone and tablet layouts are part of the same Android app and use the same accounts, profiles, playback, tracking, downloads, and Watch Party features as the TV layout, adapted for touch and smaller screens.

The current universal APK supports:

• arm64-v8a (ARM64), used by many newer Android TV, Google TV, and Fire TV devices.
• armeabi-v7a (ARM32), used by many older or lower-cost Fire TV devices.
• Android 7.0 / API 24 or newer, including Fire OS 6 and newer.

Fire OS 5 devices cannot install the current build because they are below the minimum Android API level.

TetoTV installs directly on the TV or Android device. Normal discovery, source selection, playback, tracking, and downloads do not require a companion app, Docker container, desktop process, or self-hosted TetoTV server.

You connect only the services you choose. Account linking and Watch Party use TetoTV-hosted coordination where needed, while Plex and Jellyfin require a personal server only when those optional integrations are enabled.

TetoTV includes a generic compatibility layer for user-supplied HTTPS extensions. Extensions are untrusted third-party code, are not reviewed or endorsed by TetoTV, and remain subject to bounded runtime and network controls. Technical compatibility does not mean that an extension or its content is lawful, safe, or approved.

TetoTV ships without a catalog, suggested repository, provider, media index, or automatic installation path. Users must add extensions themselves and should connect only services and media they are authorized to use. Provider cards can display recent compatibility results and the last test date to help diagnose user-configured integrations.

Third-party services and extensions can change independently of TetoTV. TetoTV does not host or relay their media and does not guarantee their availability, legality, security, or fitness for use.

The Manga reader preference is enabled by default, and first-run setup asks the viewer whether to keep it enabled. Core Manga does not require Developer Mode. It can be disabled in Settings > Services. Disabling it removes the book destination and blocks reader routes without deleting the local library, progress, settings, or downloads. Disabling the reader pauses active and queued Manga downloads and suspends pending Manga tracker delivery until the feature is re-enabled. Downloads stay paused until the viewer explicitly resumes them. Its discovery/runtime entry points are separate from anime extensions and use only sources the viewer adds. New sources use a Seanime-format manga-provider extension installed from a compatible Marketplace repository the viewer entered. Previously saved OPDS 1.x/2.0 and declarative data catalogs remain accessible, together with existing library entries and completed downloads; the new-source UI does not offer a new OPDS/data-catalog setup flow. Manga extensions provide a source-search, chapter-list, and page-resolution flow similar to a dedicated source-based reader; they do not require a personal server. TetoTV does not ship, suggest, rank, or remotely install a manga catalog, repository URL, provider, or title.

The in-app Manga > Sources manager now presents that flow directly as repositories → extensions → browse. Repository entry is blank by default; the extension catalog supports name/author and language filters, explicit install/update confirmation, enable/disable, and uninstall controls. It accepts compatible Seanime/Teto Marketplace JSON containing manga-provider entries. Mihon/Tachiyomi index.pb stores contain native Android extension APKs and are explicitly rejected as incompatible rather than saved or treated as working TetoTV repositories.

The reader includes paged, vertical, and webtoon reading; right-to-left and left-to-right navigation; single, double, and automatic spreads; page-fit, spacing, background, preload, and book-animation controls; app-private reading progress; categories/statuses, chapter bookmarks and unread filters; bounded chapter-update checks; and compatible reading-order or ZIP/CBZ chapter downloads. The sequential download queue supports pause/resume and batches of the next 5 or 10 unread chapters. Active manga downloads use a best-effort Android foreground-service lease so they can normally continue after Home/minimize. They are not scheduled server jobs: force-stop or process death ends the transfer. On reopening, interrupted jobs remain local until an explicit resume asks the matching enabled Seanime source for fresh page capabilities using the active profile's protected title identity. Remote URLs and request headers are not persisted; changed capabilities or a missing source can require re-downloading/reselection. Verified retained pages are reused only after fingerprint/hash checks. Paused jobs stay paused. Automatic spreads can use a separating vertical fold or hinge so an opened foldable displays two physical pages without losing the current reading position.

Previously saved OPDS and declarative data catalogs are data-only; they do not install extensions or execute code. This does not describe the new extension path: a Seanime manga-provider extension is untrusted JavaScript or TypeScript that runs inside TetoTV's bounded QuickJS compatibility runtime with public-HTTPS-only networking, request/response limits, cancellation, and no direct Android, file, native, tracker-token, Discord-token, or Debrid-token access. TetoTV does not load Tachiyomi/Mihon APK extensions. An installed extension and the hosts it calls can observe the searches, titles, chapters, request paths, public IP address, and ordinary connection metadata needed for that request, so viewers should install only providers they trust and are authorized to use. Optional OPDS Basic, Bearer, or API-key credentials are entered by the viewer and kept in Android Keystore-backed secure storage rather than in the repository document, catalog/download database, or diagnostics. Credentials are forwarded only to the exact source origin; reader redirects to another origin continue without them. If Discord Rich Presence is linked and enabled, the open reader can share the title, chapter, page/total, and a validated public book-cover URL. Protected/signed covers and local images fall back to the TetoTV logo. TetoTV never forwards a user-added source/catalog URL, page URL, or request headers to Discord. Turning title sharing off hides both the title and cover, using Reading manga and Private chapter while retaining page/total activity.

Optional manga tracking requires choosing and confirming the exact record on AniList or MAL; SIMKL is not a manga-tracking option. Future reader completions with whole-number chapter numbers can update that record, with protected owner/account-bound pending retries. Linking does not upload prior history or change score, volume count or online list status. The local encrypted backup flow uses a passphrase and Android's document picker with preview/confirmation; it includes supported Seanime library/history/reader settings, not downloaded pages, source installations, credentials or tracker links/outbox. See Manga library and reader for controls, limits and recovery behavior. These features are not a device-compatibility certification.

Experimental Aniyomi extension compatibility is a separate feature. Its repository, install, discovery, and reader entry points remain available only while Developer Mode is enabled; turning Developer Mode off revokes an active Aniyomi reader session. The normal Seanime manga flow does not require Developer Mode.

Only connect catalogs and download material that you are authorized to use. The manga source and repository format documents the supported source types and security boundary.

The 2.0 Beta can save supported individual episodes or whole seasons from sources the user is authorized to download to a persistent Download Manager. Downloads are stored in a predictable show, season, and episode structure and include queue state, progress, speed, storage use, pause/resume, retry, cancel, and delete controls.

Completed episodes appear as offline choices in the normal source picker and play through the normal MPV player. Basic show metadata and artwork remain available offline, watch progress is saved locally, and queued AniList/MyAnimeList updates retry when the connection returns.

Downloads continue while TetoTV is minimized. If Android stops the process, an unfinished season plan resumes the next time the app opens. Android force-stop always ends active app work. Sources that rely on short-lived or private authorization may need to be selected again.

TetoTV can connect to supported Debrid accounts selected and authorized by the user. Results can appear alongside user-configured extensions, downloaded media, and personal-library sources.

Direct peer-to-peer playback and downloads are optional Beta features and are off by default. Enabling them requires a warning because public peers and trackers can see the viewer's public IP address, and the device may upload pieces. TetoTV uses a bounded temporary cache for playback and clears it when playback closes.

Users are responsible for the services and sources they configure and for following the laws that apply to them.

AniList and MyAnimeList connections are optional. Either tracker can sync lists and watch progress, while a local profile keeps the app usable without a tracker account. Catalog metadata uses mapped backup services when AniList is temporarily unavailable.

SIMKL is also optional. Current builds use SIMKL's official TV PIN flow: the configured TetoTV companion advertises only the registered application's public client ID, then the app requests and polls the short-lived PIN directly with SIMKL. No SIMKL client secret or TetoTV callback is used in this normal path. The linked account can supply the profile, lists, list status, and episode progress used by TetoTV. Anime writes use the AniList or MyAnimeList IDs that SIMKL accepts directly, while list results retain their canonical SIMKL ID and include a visible View on SIMKL link instead of guessing identifiers.

The source integration remains deployment-gated: the operator must register the TetoTV application with SIMKL, obtain any API or commercial-use approval required for the intended distribution, configure SIMKL_CLIENT_ID, and deploy the matching companion capability before users can connect. The client ID is public application metadata; it is not a user API key.

Calendar notifications can alert viewers when followed Sub/simulcast episodes reach their scheduled airtime. Dub alerts are separate and remain idle unless TetoTV has a verified Dub schedule; the app does not guess a Dub release from the Japanese broadcast time.

Discord Rich Presence is also optional and can show what is playing after the viewer links Discord.

Plex and Jellyfin are personal-media integrations, not requirements. When configured, TetoTV matches library episodes to the anime being viewed and adds them to the same show page, episode screen, source picker, history, progress, and previous/next episode flow used by online and downloaded sources.

If Plex or Jellyfin is not configured—or the selected episode is not in the library—those sources stay hidden. A personal media server is required only for the integration the viewer chooses to use.

TetoTV uses MPV for its integrated player across supported user-configured services, downloaded media, Plex, Jellyfin, and local files. Playback controls include:

• Previous and next episode.
• Intro and outro skipping when timing data is available.
• Optional filler skipping and filler labels.
• Progress-bar scrubbing with scene previews.
• D-pad seeking, including held-button seeking.
• Playback speeds from 0.5x to 2x.
• Audio, subtitle, aspect-ratio, and decoder controls.
• In-app trailers on supported show pages.
• Automatic source fallback that keeps position and preferred quality when possible.

Viewers can also choose a specific installed external player in Settings. External players do not carry TetoTV's Watch Party, skip, fallback, or progress controls while the other app is open.

Create or join a Watch Party from navigation, an episode screen, or the player. The host controls playback while guests stay synchronized. Rooms show participants, support host transfer and kicking, and display small join, leave, kick, and transfer notifications.

Watch Party is enabled by default but can be turned off in Settings, which removes its navigation and episode-screen entry points.

1. Open the current Beta release. No Public APK is currently published.
2. Download the file ending in -universal.apk.
3. Allow installation from the browser or file manager if Android asks.
4. Open TetoTV and complete the short setup.

The universal APK contains both ARM32 (armeabi-v7a) and ARM64 (arm64-v8a) native libraries for compatible Android TV, Google TV, and Fire TV devices.

TetoTV checks the two GitHub release repositories directly. APK downloads do not pass through a TetoTV server, and the app verifies package, version, architecture, and signer information before opening the Android installer.

• A future Public build will use the 1.0.x version line after a separate release review. The Public repository currently returns no release.
• Beta builds use the 2.0.x version line.
• Release history remains available in Developer Mode. Android still blocks installing a build with a lower build code.

The main TetoTV repository holds the full Flutter, Android, native-integration, test, documentation, and release-tooling source. GitHub Releases are one part of the project, not the purpose of the repository.

Anonymous crash reporting starts enabled only on genuinely new installs, is disclosed during setup, and can be turned off there or later in Settings. Existing installs keep their stored choice; an upgrade does not silently opt in an installation with a missing legacy preference. Manual diagnostics still require the viewer to choose to share them. Reports include a bounded 48-hour troubleshooting timeline while automatically removing credentials, room codes, media URLs, filenames, and private-server information.

Beta builds offer an approximate anonymous aggregate live count, enabled by default with a Settings opt-out. It sends only active or streaming for a short-lived process session—never a profile, title, episode, source, device ID, URL, filename, or private-server information. Public builds disable this presence; no Public APK is currently published.

Read the complete privacy documentation for report contents, redaction, optional integrations, and network behavior.

TetoTV-authored source code is available in this repository under the MIT License. Distributed releases include the required third-party notices and native corresponding-source materials, including pinned MPL-covered source used by the optional direct-torrent engine. Bundled third-party components keep their own licenses and terms.

TetoTV uses third-party services and open-source components but is not affiliated with, sponsored by, or endorsed by AniList, MyAnimeList, SIMKL, Discord, Amazon, Google, Plex, Jellyfin, or any streaming or Debrid provider. See the content and source policy for the repository boundary and reporting path.

For public bugs and feature requests, open a GitHub issue. For announcements and community support, join the TetoTV Discord. Security vulnerabilities should follow the private process in SECURITY.md, not a public issue.

When reporting a bug, include the TetoTV version, device model, Android or Fire OS version, steps to reproduce it, and a diagnostics report when possible.