Vitaly

@tk dilan kumara Is the firmware installation stuck and the tablet is not working? Or was the update download stuck?

DashCast v1.0.0DashCast v1.0.0 — Official Stable Release DashCast graduates from alpha and beta to its first official stable release. What's new Brand-new interface: the entire UI has been redesigned from scratch in Material 3, with a consistent navigation rail, modern bottom sheets, dialogs and tiles across all screens (Main, SysInfo, Diag, Log, Settings). Hardened projection lifecycle: the start/stop flow of cluster projection has been reinforced to prevent the edge-case bugs reported during beta (black card, stale surface, restart loops). Teardown and re-creation of the mirror surface are now synchronous and deterministic. Stability & cleanup: full lint + javac audit pass, dead code removed, thread-safety hardening (SimpleDateFormat in SysInfoActivity now uses ThreadLocal), 12 locales kept in sync. Community A dedicated Telegram channel has been created for support, feedback and discussion: https://t.me/+QPk_dmTVaNkxMjFk Documentation The documentation has been fully rewritten to match v1.0.0 and is available at: https://kiroha.github.io/byd-dashcast/ Install Download DashCast-v1.0.0-debug.apk below and install on a BYD DiLink 3.0 head unit (Android 10, platform-signed environment). LinksAPK download GitHub release page

DashCast v0.9.94Audit cleanup pass 2 (post-0.9.93) Following the exhaustive read-only audit on the alpha/0.9 branch — incremental fixes, no regression. Improvements 🗑️ Dead code removed: orphan DashCastDaemon.java (~170 LoC, zero references, never invoked via app_process) ⚡ Perf: SysInfoActivity — 4× SimpleDateFormat allocations replaced by ThreadLocal cache (thread-safe) 🎨 Layouts: explicit paddingStart on activity_main / activity_sysinfo (RtlSymmetry fix) 🔒 EditText: importantForAutofill=no on log_filter + et_search_apps (debug fields) Metrics Lint: 75 → 71 issues Java code: −170 LoC Build: SUCCESSFUL, javac 0 warnings versionCode: 152 → 153 Intentionally not fixed 28 UseAppTint, 24 SmallSp, 8 ButtonStyle, 7 NestedWeights, 2 TooDeep/TooMany — UI design items, require on-device validation Branch: alpha/0.9 (no merge to main) APK: DashCast-v0.9.94-debug.apk (BYD platform signature) LinksAPK download GitHub release page

@BydSy26pro Have you tried installing the app via a USB flash drive?

DashCast v0.9.0What's Changed since v0.8.7 This release starts a phased migration to Material Design 3, matching the target design in mockups/mockup_m3.html. The migration is split into 5 phases to detect any regression early. This release is Phase 1 only — foundation work. No layouts or business logic have been touched, so all existing features must keep working exactly as in v0.8.7. Phase 1 — Foundation Build & dependencies Bumped compileSdkVersion from 29 → 33 to enable Material 3 components. targetSdkVersion and minSdkVersion are still 29, so runtime behavior on the BYD Seal (Android 10 / DiLink 3.0) is unchanged. Added new dependency: com.google.android.material:material:1.9.0 (last version compatible with compileSdk 33). Theme Switched AppTheme parent from Theme.AppCompat.DayNight.DarkActionBar → Theme.Material3.DayNight.NoActionBar. The theme now exposes the full Material 3 color attribute set (colorPrimary, colorOnPrimary, colorPrimaryContainer, colorSurfaceVariant, colorOutline, etc.) so M3 components (MaterialButton, MaterialCardView, MaterialSwitch, …) introduced in later phases will automatically pick up the right palette. All legacy theme attributes (colorPrimaryDark, colorAccent, textColorPrimary, textColorSecondary, windowBackground) are still mapped to the original color resources, so existing layouts that reference them keep rendering as before. Color palette Added the full Material 3 token set to values/colors.xml (light scheme) and values-night/colors.xml (dark scheme): Primary / secondary / tertiary / error families Surface container levels (lowest → highest) Outline + outline variant Success and warning custom tokens Source color is #1565C0 (BYD blue), with the dark scheme tokens taken directly from mockup_m3.html so the rest of the migration can match the mockup pixel-for-pixel. All previously existing color names (bg_main, text_primary, text_secondary, bg_card, bg_dialog, colorPrimary, etc.) are preserved untouched so existing layouts continue to render identically. What is NOT in this release No layout file has been modified. No Java/Kotlin code has been modified. No feature, setting, dialog, navigation flow or business logic has been changed. No new Material 3 components have been introduced into screens yet — that work starts in Phase 2. Upcoming phases Phase 2 — Migrate common components (Button → MaterialButton, Switch/CheckBox → Material*, cards → MaterialCardView, FAB). Phase 3 — Migrate Welcome + Settings screens (navigation rail, top bar pattern). Phase 4 — Migrate Main + Diagnostics screens (most complex; keeps all cluster / ADB logic intact). Phase 5 — Migrate System Info + Log screens and list-item layouts. Full Changelog: v0.8.7...v0.9.0 LinksAPK download GitHub release page

DashCast v0.8.7What's Changed since v0.8.6 UX Improvements Reconnect popup disabled by default — The "relaunch last app on cluster reconnect" popup is now opt-in (off by default) to avoid intrusive prompts for new users. Enable it in Settings if you want the behavior. Internationalization Added settings_reconnect_popup translation in all 12 supported locales: French, English, German, Spanish, Italian, Arabic, Belarusian, Kazakh, Russian, Turkish, Ukrainian, Uzbek. Corrected French wording for the reconnect popup setting. Previous (v0.8.6) Made the reconnect popup fully opt-in via a new checkbox in Settings (PREF_RECONNECT_POPUP). Fixed a race condition in FloatingRemoteButton where show() was silently lost when called before the overlay was ready — added sShouldBeVisible static flag with deferred visibility after createOverlay() and onStart() re-sync. Full Changelog: v0.8.6...v0.8.7 LinksAPK download GitHub release page

DashCast v0.8.6DashCast v0.8.6 — Floating button reliability fix Branch: alpha/0.7 — not merged to main Build: 117 · platform-signed · API 29 Bug Fix FloatingRemoteButton race condition (cc939a3) The floating 📺 mirror button and the in-app "Show Mirror" button were intermittently invisible after launching an app on the cluster then hiding the mirror view. The behavior was non-deterministic ("random") because it depended on service startup timing. Root cause: FloatingRemoteButton.show() was silently discarded when called before the overlay was ready. Two async gaps caused this: Service startup race — startService() is asynchronous; sInstance and mFloatView are null until onStartCommand() + createOverlay() complete. Any show() call during this window was lost. Overlay permission grant race — On first install, SYSTEM_ALERT_WINDOW is auto-granted via ADB shell (async). During the grant round-trip, mFloatView remains null and the overlay is created with View.GONE. Nobody re-called show() after creation succeeded. Fix applied: File Change FloatingRemoteButton.java Added static volatile boolean sShouldBeVisible flag. show()/hide() now persist the desired state before attempting the view operation. After createOverlay() succeeds, the flag is read and the button is made visible immediately if an app is active. MainActivity.java In onStart(), explicitly re-sync btnShowMirror visibility + call FloatingRemoteButton.show() whenever mCurrentDashboardApp != null and the service is already bound. Covers the stop/start lifecycle where updateDashboardStatus() is not re-invoked. Impact: Both the floating overlay button and the top-bar "Show Mirror" button now appear reliably regardless of service/Activity lifecycle ordering. Upgrade notes Direct install over v0.8.5 — no data loss, no uninstall needed versionCode incremented (116 → 117) LinksAPK download GitHub release page

DashCast v0.8.5What's changed since v0.8.2 This release replaces the broken getTasks() state poller, removes a dangerous diagnostic button that could brick the cluster until reboot, and applies a full multi-axis audit pass (HIGH → LOW). Display-state poller — getTasks() → pidof (v0.8.3) Problem: The log-only poller from v0.8.2 confirmed what the symptoms had suggested: IActivityTaskManager.getTasks() on DiLink 3.0 does not report tasks running on the cluster VirtualDisplay. Tasks on the main display were visible, tasks on display 1 (Fission) were never returned. This made the original mutating reconciliation logic — disabled in v0.8.2 — fundamentally unfixable: there is no way to ask the ATM for the cluster app's running state. Fix: reconcileDisplayState() no longer uses getTasks() at all. It now runs a pidof <package> over the existing ADB localhost relay (uid 2000), which can read /proc despite hidepid=2. A single async call every 5 s, with the active package captured by reference; logs the PID when alive, clears cluster state and stops the mirror when the process is gone. The previous ~80 lines of IActivityTaskManager reflection were removed. The state poll is started/stopped together with the screenshot loop, so it only runs while MainActivity is in the foreground. Diagnostic safety — OSD On/Off buttons removed (v0.8.3) Problem: Testing the experimental btnFissionOsdOff button in DiagActivity revealed it sends sendInfo(1000, 20), which disables the entire cluster display on the BYD Seal EU. Once triggered, the cluster cannot be re-enabled by the app: a hardware reboot via long-press of the volume button is required. Fix: Both btnFissionOsdOff and btnFissionOsdOn and their handlers have been removed from DiagActivity, along with the four related strings (diag_btn_fission_osd_off/on, diag_fission_osd_off_sent/on_sent) and the corresponding Button widgets in activity_diag.xml. The section description was shortened to reflect the reduced set of controls. Diagnostic correctness — overscan read fixed (v0.8.3) Problem: DiagActivity attempted to read the current overscan via wm overscan -d 1 to confirm the value applied by the settings screen. On API 29, wm overscan is write-only: it accepts coordinates but returns an empty body. The diag screen always reported "overscan = 0,0,0,0", masking the real persisted value. Fix: The verify step now runs dumpsys display | grep -i overscan instead, which exposes the SurfaceFlinger-side display overscan rect actually in effect. Multi-axis audit (HIGH findings, v0.8.3) MainActivity.reconcileDisplayState — use-after-destroy in the pidof callback. The async pidof callback was posting a Runnable to runOnUiThread that re-checked package equality and then mutated UI fields. Between the bg-thread pidof completion and the Runnable running on the main thread, onDestroy could fire and null out the views referenced by clearClusterState()/stopClusterMirror(). Now the Runnable first checks isFinishing() || isDestroyed() and returns early. ClusterService.findRunningTaskId — NPE on getRunningTasks(). am.getRunningTasks(50) is documented to return a non-null list, but on rare framework error paths it can return null (observed historically on third-party Android forks). The helper now null-checks the return value and returns -1 instead of dereferencing a null List. Multi-axis audit (MEDIUM findings, v0.8.4) ClusterService — move-task-thread post-destroy guard. The unnamed background thread spawned by moveTaskToDisplay() posts its result back to mMainHandler. Between onDestroy (which already drains the handler with removeCallbacksAndMessages(null)) and the bg thread posting the next Runnable, there is a small window where a posted callback may execute after the service is dead and reach mLauncher/mMirrorManager (both freed). A new volatile boolean mDestroyed is now set in onDestroy(), and every post-callback in the move-task-thread path (success branch + fallbackLaunch posted runnable) returns early when the flag is set. MainActivity.onDestroy — mMirrorSurface not released. The Surface wrapping the TextureView's SurfaceTexture was retained until GC after the Activity was destroyed. onDestroy now explicitly mMirrorSurface.release() and nulls the field, guarded by a try/catch (Exception ignored) for the case where the underlying texture was already torn down. AdbLocalClient.sendInfo — incomplete shell argument escaping. The s16 argument to service call AutoContainer 2 ... s16 "<infoStr>" previously escaped only ". If an infoStr ever contained $ (variable/arithmetic expansion) or ` (command substitution), the shell would interpret it before reaching AutoContainer. Escaping order is now: \\ first (avoids double-escaping the backslashes we are about to insert), then ", $, `. No current call site uses untrusted input here, but the function is on a public ADB-relay path and the fix is preventive. Multi-axis audit (LOW findings, v0.8.5) UpdateChecker.downloadToFile — HTTPS→HTTP redirect downgrade. The manual 5-step redirect follower accepted any Location header, including http://.... A misconfigured GitHub CDN response or a hostile MITM could downgrade the APK download to plaintext. The platform-signed APK would still be rejected by PackageInstaller on signature mismatch, but the new check fails fast with "Insecure redirect target: ..." if the redirect target is not https:// (case-insensitive, Locale.ROOT). MainActivity.startScreenshotLoop — Activity reference held by ADB executor queue. The screenshot loop passed MainActivity.this as the Context argument to AdbLocalClient.captureClusterDisplay. While a capture was in flight, the static sExecutor's task queue held a strong reference to the Activity. After verifying that captureClusterDisplay only uses the context for connect(), getExternalCacheDir() and getCacheDir() — all valid on applicationContext — the call site now passes getApplicationContext(). The bitmap is still delivered on the Activity via runOnUiThread inside the BitmapCallback, so the UI path is unchanged. Verified clean (no fix applied) The audit also confirmed: All Parcel.obtain() / MotionEvent.obtain() are recycled in finally All InputStream / Reader / Writer / Socket use try-with-resources Single ad-hoc ExecutorService (in SysInfoActivity) calls shutdown() after submit registerReceiver ↔ unregisterReceiver paired in MainActivity bindService ↔ unbindService paired in MainActivity.onDestroy VirtualDisplay.release() in finally in DashCastDaemon SurfaceFlinger display token released in MirrorDaemon.stopMirror() All SharedPreferences writes use apply(), never commit() PendingIntent.FLAG_IMMUTABLE used everywhere except UpdateChecker where mutability is documented to be required by PackageInstaller TLS via system TrustManager (no custom verifier, no insecure Random) No exported component without a system-protected action or a signature-level guard No secrets/PII logged Branch: alpha/0.7 — not merged to main APK: debug build, signed with the BYD platform keystore Compatibility: BYD Seal EU (DiLink 3.0, API 29), 1920×720 cluster VirtualDisplay owned by com.xdja.containerservice LinksAPK download GitHub release page

DashCast v0.8.2What's changed since v0.8.1 fix: convert display-state poller to log-only mode (d863984) Problem: The 5-second IActivityTaskManager.getTasks() poller introduced in v0.8.1 was incorrectly clearing cluster state (mirror view + app icons) every time it ran. When a user launched an app on the cluster, the mirror would appear but then get killed ~5 seconds later by reconcileDisplayState(), resetting the UI as if no app was running. Root cause: getTasks() on DiLink 3.0 most likely does not return tasks running on the VirtualDisplay (Fission display). The poller interpreted the missing task as "app is dead" and called clearClusterState(), which: Cleared mCurrentDashboardPkg / mCurrentDashboardApp Removed shared prefs Reset the adapter (no active icon, no red kill cross) Called showAppList() — hiding the mirror view Fix: reconcileDisplayState() now operates in log-only mode: Still polls getTasks() every 5 seconds while the Activity is visible Logs ALL tasks with baseActivity, topActivity, and displayId for each entry Logs a summary showing whether the tracked cluster/main packages were found and on which display Does NOT mutate any state — no clearClusterState(), no setMainPackage(), no shared prefs writes Bonus improvements in the logger: Also checks topActivity field as fallback when baseActivity is null Logs when getTasks() returns null or empty (was silently returning before) Full task dump enables post-test analysis of what the DiLink ROM actually reports The reconciliation logic will be re-enabled once we confirm getTasks() behavior on the BYD head unit via these diagnostic logs. Branch: alpha/0.7 — not merged to main LinksAPK download GitHub release page

Open BYD The app uses ADB and lets you remap steering wheel buttons to control car functions like AC or windows, launch apps automatically, use split-screen, and cast apps to the dashboard or move them back to the main screen. In version 5.1 there was a mini mode (just a small window on the right) of the dashboard that the app supports, allowing you to save custom offsets and resize of the projection while in that mode. It works well on DiLink 5.1. There’s partial compatibility with DiLink 5, where some features like split-screen or car controls may not work depending on the version. On DiLink 6, BYD locked down several of these features (casting to the dashboard, split-screen). OpenBYD 1.0.apk

BYD SDK 🇺🇸 English The BYD SDK is a development toolkit and API platform for creating custom applications and integrations for BYD vehicles. It enables developers to access vehicle data, interact with the infotainment system, navigation, climate control, battery and charging information, and other smart vehicle features. The SDK is designed for Android-based in-car applications, monitoring tools, multimedia services, and third-party ecosystem integrations within the BYD platform. 🇷🇺 Russian SDK для автомобилей BYD — это набор инструментов и API для разработки собственных приложений и интеграций с мультимедийной системой автомобиля. Платформа позволяет получать данные автомобиля, работать с функциями мультимедиа, навигацией, климат-контролем, состоянием батареи, зарядкой и другими возможностями интеллектуального автомобиля. SDK предназначен для создания Android-приложений, сервисов мониторинга, мультимедиа-решений и интеграции сторонних сервисов в экосистему BYD. Version Download v1.0.5 sdk_v1.0.5.zip

DashCast v0.8.1What's changed since v0.8.0 feat: activity task manager polling (bb7bb0c) MainActivity — replaced trust-only-our-bookkeeping approach with a 5-second poll of IActivityTaskManager.getTasks() while the activity is visible. Detects three edge cases the previous logic missed: App crashed or OOM-killed → task gone → stale cluster/main state is cleared App moved to display 0 externally → reclassified as main-display Main-display app moved to cluster externally → promoted to cluster state Uses the same displayId reflection pattern already proven in DiagActivity. Poll runs in onStart() / onStop() — zero background cost. Extracted clearClusterState() helper shared with the reconciliation path. fix: eager cluster state clear before async kill/restore (f6a50cf) MainActivity — prevents a race condition where the 5-second display-state poll could fire between moveTaskToDisplay(pkg, 0) and forceStopApp(), incorrectly setting mMainDisplayPkg. Three paths fixed: doKillApp, restoreBydDashboard, originCluster. The captured package is still forwarded to restoreBydOnCluster / restoreOriginCluster for the force-stop before sendInfo(18). feat: cluster surface diagnostics buttons (e1cd30b) DiagActivity — new button row in the Fission Pipeline section to investigate the partial-surface projection issue (native Qt HUD overlays remaining visible above/below the VirtualDisplay): Button Command Purpose 🔍 Measure surface DisplayManager + wm size/overscan -d X + dumpsys display Read actual VirtualDisplay dimensions OSD Off sendInfo(1000, 20) Attempt to hide Qt native HUD overlays (speed / gear / battery) OSD On sendInfo(1000, 19) Re-enable Qt native HUD overlays Overscan 0,0,0,0 wm overscan 0,0,0,0 -d X Remove artificial margins on the Fission display Branch: alpha/0.7 — not merged to main LinksAPK download GitHub release page

DashCast v0.8.0DashCast 0.8.0 — Pre-release Stabilization release closing the alpha/0.7 development line. Eighteen consecutive sanity passes (P0 → P16) hardened lifecycle, concurrency and native resource handling across the entire application and the system-level MirrorDaemon (uid=2000). No new user-facing features; no API-level bump; target remains Android API 29 (DiLink 3). Pre-release: not merged to main, remains on branch alpha/0.7. Baseline: v0.7.9-alpha → v0.8.0 · 17 commits · versionCode 96 → 111 Highlights Cluster mirror reliability: no more orphan SurfaceControl display tokens on daemon setup failure; Surface/SurfaceTexture lifecycle now mirrors the size-changed/destroyed contract end-to-end. Concurrency hygiene: every long-lived background thread is now named for tombstone/anr triage; activity-scoped executors use named daemon ThreadFactory; volatile mDestroyed flag added to every Activity that posts back to UI from a worker. No more ANR-risk paths in onCreate: boot-time cleanup of cluster display affinity is now off-loaded to a daemon thread. Native resource leaks closed: 5 × Parcel.obtain, 3 × MotionEvent.obtain, 1 × InputStream and the setupMirror token are all released on every exit path (success, exception, lifecycle end). Dead code removed: 4+ unused methods, 1 orphan BroadcastReceiver, the entire profile-feature placeholder UI, redundant Handler/StringBuilder instances. Resource lifecycle & native handles MirrorDaemon.setupMirror — when createDisplay succeeds but a later SurfaceControl.Transaction reflection step throws, the catch path now calls stopMirror() (which captures the token, nulls the static, then invokes destroyDisplay) instead of merely clearing the reference. The SurfaceFlinger display token is no longer leaked for the lifetime of the daemon process. (P16) ClusterInputForwarder.injectTouchAtMulti — MotionEvent and Parcel are recycled inside a finally on both daemon and non-daemon paths, even when InputManager.injectInputEvent() / Binder.transact() throws. (P9, P10) ClusterInputForwarder.injectKey — Parcel is recycled per iteration inside the daemon for-loop. (P9) MirrorDaemon.readParcelable(MotionEvent) — recycled in finally. (P11) ClusterMirrorManager.stopMirrorViaDaemon — Parcel recycled in finally, symmetric with startMirrorViaDaemon. (P9) UpdateChecker.httpGet — InputStream closed via try-with-resources. (P10) Concurrency & lifecycle safety MainActivity.onCreate — cleanupDisplayAffinityAtBoot() (which performs N IActivityTaskManager binder calls via reflection) is now off-loaded to a daemon thread boot-cleanup-fallback using getApplicationContext() to avoid Activity retention. Eliminates a latent ANR risk when the persisted cluster-package set is non-trivial. (P15) MainActivity.onDestroy — screenshot handler lambdas are now cancelled via removeCallbacksAndMessages(null); the screenshot-loop TOCTOU race against mScreenshotRunnable is closed. (P1, P12) AdbLocalClient.sExecutor — now uses a named daemon ThreadFactory (adb-local-N). (P13) MainActivity.loadAppsAsync — executor uses a named daemon ThreadFactory (load-apps). (P14) MirrorDaemon.injectMotion (daemon path) — MotionEvent is recycled in finally. (P11) BootReceiver — wrapped in goAsync() + result.finish() to prevent the background reflection thread from being killed mid-execution by the system. (P1) DiagActivity / SettingsActivity / SysInfoActivity — every one of the ~70 runOnUiThread posts is now guarded by a volatile mDestroyed flag, with a safeRunOnUiThread() helper for the diag screen. (P2, P4) SysInfoActivity.publishUpdate — the worker-side mDestroyed check before runOnUiThread is now duplicated inside the main-thread Runnable (the original check was racy against onDestroy between queueing and dispatch). (P16) FloatingRemoteButton.createOverlay — removed redundant local Handler, reuses mDimHandler. (P9) ClusterMirrorManager.unlockHiddenApis — guarded by AtomicBoolean; the VMRuntime.setHiddenApiExemptions reflection chain is no longer re-run on every Activity recreation. (P2) Correctness fixes AdbLocalClient.startMirrorDaemon — safeOut() was converting empty strings to "(empty)", causing the post-launch ps -A verification to always succeed and masking real daemon-start failures. Replaced with direct getAllOutput().trim(). (P5) MainActivity.moveTaskToDisplayZero — now returns true when the task is not found (the goal is "task absent from display 1", not "task moved"). (P1) DiagActivity.runAdas — fixed argument inversion bug. (P8) LocaleHelper — applyLocale() and saveLanguage() separated; attachBaseContext no longer writes to SharedPreferences on every Activity creation. (P1) Robustness & defensive guards AppCompat AlertDialog from a Service — FloatingRemoteButton now uses WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY for its in-service dialogs (a non-Activity context cannot host a default AlertDialog window). (P7) PendingIntent flags — FLAG_IMMUTABLE everywhere except UpdateChecker.installApk where FLAG_UPDATE_CURRENT (without IMMUTABLE) is required by PackageInstaller to inject extras (documented inline). (P7) Foreground services — both ClusterService and FloatingRemoteButton call startForeground() within the 5-second window and provide setSmallIcon(). Performance AppListAdapter — per-bind new ColorDrawable() allocations replaced with reusable ConstantState instances (CS_FG_ACTIVE, CS_FG_ON_MAIN). (P4) LogActivity — adaptive polling switched from a fixed 500 ms cadence to 500 ms when entries change / 2000 ms when idle, then short-circuits the whole rebuild when neither the entry count nor the filter changed. (P1, P7) Cleanup & dead code removal AdbLocalClient — removed scanSniffer(), killSniffer(), checkTaskBoundsOnDisplay() (no callers), SNIFFER_KILL_CMD constant. (P2, P8) AppLogger — removed shareTextAsFile() (no callers). (P3) MainActivity — removed dead mShowMirrorReceiver BroadcastReceiver (FloatingRemoteButton uses startActivity, not sendBroadcast). (P3) ClusterMirrorManager.startMirror — unused Context parameter removed. (P3) ClusterInputForwarder — dead forwardTouchFinal() removed (only multi-pointer path is used). (P1) AppShortcut — unused intent field and constructor parameter removed. (P1) SysInfoActivity — redundant StringBuilder re-init before executor.submit() removed. (P1) LogActivity — removed dead TAG constant. (P8) Profile feature — placeholder UI removed entirely: spinner (MainActivity), section (SettingsActivity), layout blocks (activity_main.xml, activity_settings.xml), profile strings in all 12 locale files. (P2) Code quality Pref-key constants — every literal "byd_app_prefs", "recent_cluster_apps", "boot_auto_start_enabled", "show_category_filters", "visual_overscan_mode" etc. centralized as SettingsActivity.PREF_* constants and referenced from MainActivity, BootReceiver, FloatingRemoteButton. (P4, P5, P6) AppListAdapter — magic colors 0x1A4CAF50 / 0x141565C0 extracted as COLOR_FG_ACTIVE / COLOR_FG_ON_MAIN named constants. (P2) Misleading Javadoc — FloatingRemoteButton comment corrected (uses startActivity, not broadcast). (P3) Compatibility Target SDK / min SDK: unchanged (API 29 / DiLink 3, BYD Seal EU) App signature: unchanged (platform-signed) Permissions: unchanged Cluster display id: still hardcoded to 1 (intentional, DiLink 3 constant) Verification 5-axis static audit completed (concurrence / resources / Android-API29 / security / correctness) All 17 commits build green (./gradlew assembleDebug) No API 30+ symbol introduced No new dependency added Known limitations carried over from 0.7.x DiagActivity contains 12 anonymous new Thread(() -> ...) lambdas — kept as-is (internal diagnostic tool, short-lived tasks) UpdateChecker.installApk PendingIntent deliberately mutable (PackageInstaller contract) wm overscan ... -d 1 hardcoded for DiLink 3 cluster display Artifacts DashCast-v0.8.0-debug.apk — platform-signed debug build, installable on BYD Seal EU DiLink 3 head units. Branch policy This pre-release stays on alpha/0.7. No merge to main yet. Promotion to a stable 0.8.x line is gated on device-side validation. LinksAPK download GitHub release page

DashCast v0.6.8-betaWhat's changed — v0.6.0 → v0.6.8 v0.6.1 — i18n cleanup Purged 400+ unused translation keys across all 12 locales Fixed hardcoded strings that were bypassing the translation system v0.6.2 — Bug fixes & performance Fix ghost-restore bug: PREF_CLUSTER_PKG/PREF_CLUSTER_NAME now correctly cleared on force-stop, preventing a killed app from reappearing on the cluster after Activity recreation Dead code removal: collapsed duplicate isFavorite branches in AppListAdapter i18n: extracted 5 new keys (OTA dialog buttons, overflow menu labels) to all 12 locales Performance: reduced SharedPreferences open calls from 3 → 1 in ClusterService inset getters v0.6.3 — Sanity QoL #2 Extracted all hardcoded French notification strings (FloatingLogButton, FloatingRemoteButton, SysInfoActivity) to R.string across all 12 locales 5 new string keys added v0.6.4 — Fix ANR risk findRunningTaskId() (calls ActivityManager.getRunningTasks()) moved off the main thread to a dedicated background thread, eliminating an ANR risk in the resize button handler v0.6.5 — UX improvements Status dot (grey/yellow/green) alongside cluster status text Real-time search bar to filter the installed app list List/Grid toggle button relocated to the title header (always visible) Cluster panel collapse strip (▼/▲) to go full-screen while keeping the mirror Inset overlay preview: orange bands show resize margins during adjustment One-shot first-launch tooltip: tap any app to send it to the cluster 3 new string keys across all 12 locales v0.6.6 — Robustness & polish 30-second activation timeout: re-enables the button and shows a toast if the cluster never responds Kill confirmation dialog: AlertDialog before force-stopping any app (avoids accidental taps) Relaunch button (↺) in the control panel header: force-stops then relaunches the current app OTA changelog now rendered as styled Markdown (## headings, bullet lists, bold) 150 ms fade animation on list ↔ mirror transitions Active row background tint (green/blue semi-transparent) on currently active items Reconnect reminder: after manual re-activation, offers to relaunch the last cluster app 8 new string keys across all 12 locales (179 keys total per locale) v0.6.7 — Auto-apply saved insets Per-app insets (wm overscan + resizeActiveTask) are automatically applied 500 ms after a successful cluster launch if custom values were previously saved for that package Guard: cancelled if the active cluster app changes during the delay No manual Apply tap required v0.6.8 — Fix recents cleanup after kill Fixed silent failure of task ID extraction on Android 10 / DiLink 3.0: grep -o '#[0-9]\+' unsupported by Android busybox → replaced with portable sed BRE Wrong ID extracted (recents index instead of TaskRecord ID) → new sed expression targets only the TaskRecord entry am task rm does not exist on Android 10 → replaced with am task remove + app_process64/32-bit fallback via TaskRemover reflection helper Added [DashCast-recents] log line in LogActivity for on-device verification of extracted task IDs LinksAPK download GitHub release page

DashCast 0.5.1Comprehensive i18n support localized hardcoded strings across UI, overscan layouts, and system Toasts in all 12 supported languages. Fixed missing 'Adjust' button from the manual UI diagram. LinksAPK download GitHub release page

DashCast v0.5.0-betaSecond Beta Release! Merged all 0.4.x refactorings (UI revamp, app-specific Overscan memory saving and injection, intent fixes, native reflection code). LinksAPK download GitHub release page

DashCast v0.2.1Version 0.2.1 🛠️ Bug Fixes & Stability Resources: Safely closed the BufferedReader stream in MirrorDaemon.java using a try-with-resources block to prevent memory leaks (orphaned streams from dumpsys). Broadcaster Permissions: Applied the UnspecifiedImmutableFlag to UpdateChecker.java to resolve intent false positives during the silent OTA update process. Manifest compliance: Explicitly added the android:exported="true" attribute to the main entry point, as required for Android 12+. UI Memory Leaks: Added the @SuppressLint("StaticFieldLeak") annotation to FloatingRemoteButton.java to suppress warnings regarding its managed, bound lifecycle. 🧹 Optimizations Orphaned Strings Cleanup: Removed unused string resources (such as menu_settings) across all localizations and dictionaries, reducing the APK build size. Storage Management: Identified and cleared old, invalid PackageInstaller sessions that were consuming massive amounts of persistent cache storage (~800 MB from previous development builds). LinksAPK download GitHub release page

DashCast v0.2.0-betaFirst beta release What's new OTA updates: DashCast now updates itself automatically from GitHub Releases Download progress bar Install via PackageInstaller with system confirmation prompt Pre-release toggle in Settings to receive alpha builds Package rename: com.byd.myapp → com.byd.dashcast Bug fixes Removed broken watchdog (false positives on DiLink 3.0) Fix OTA: removed FLAG_IMMUTABLE from PendingIntent → PackageInstaller result now received correctly Fix blocking update dialog → dismissed automatically when install starts LinksAPK download GitHub release page