enricobuehler
08ab2b6bee
WifiLock.acquire() enforces the WAKE_LOCK permission, which the manifest never declared — every acquisition since the first Wi-Fi lock shipped threw SecurityException, silently swallowed by a bare runCatching. The phone's own accounting proved it (dumpsys wifi: high_perf/low_latency active_time_ms = 0 across weeks of streams): every on-device session ran with Wi-Fi power save fully active, whatever the code intended. Verified live after the fix: both locks registered in WifiLockManager, mPowerSaveDisableRequests=2, ping RTT to the streaming phone 3.8 ms avg. A failed acquire now logs loudly — this class of failure must never be invisible again. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
74 lines
4.3 KiB
XML
74 lines
4.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
|
|
|
|
<!-- punktfunk/1 QUIC/UDP data plane. -->
|
|
<uses-permission android:name="android.permission.INTERNET" />
|
|
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
|
|
<!-- mDNS discovery of _punktfunk._udp on the LAN (native mdns-sd browse). Requested
|
|
opportunistically — raw multicast reception needs only the MulticastLock, not this. -->
|
|
<uses-permission
|
|
android:name="android.permission.NEARBY_WIFI_DEVICES"
|
|
android:usesPermissionFlags="neverForLocation" />
|
|
<!-- HostDiscovery holds a MulticastLock while the native mDNS browse runs — raw multicast
|
|
reception needs it (also an OEM Wi-Fi power-save hedge). -->
|
|
<uses-permission android:name="android.permission.CHANGE_WIFI_MULTICAST_STATE" />
|
|
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
|
|
<!-- WifiLock.acquire() ENFORCES this (a normal permission, granted at install). Without it the
|
|
stream's Wi-Fi locks throw SecurityException and power save stays on: downlink delivery
|
|
clumps at beacon intervals — hundreds of ms of latency mush + periodic whole-frame loss.
|
|
Its absence went unnoticed for weeks because the acquire was wrapped in a silent
|
|
runCatching (now logged). -->
|
|
<uses-permission android:name="android.permission.WAKE_LOCK" />
|
|
<!-- Enforced from Android 17 (SDK 37) for ALL local-network traffic incl. the QUIC socket.
|
|
Harmless to declare on earlier releases. -->
|
|
<uses-permission android:name="android.permission.ACCESS_LOCAL_NETWORK" />
|
|
<!-- Mic uplink to the host's virtual microphone (requested at runtime). -->
|
|
<uses-permission android:name="android.permission.RECORD_AUDIO" />
|
|
<!-- Gamepad rumble feedback. -->
|
|
<uses-permission android:name="android.permission.VIBRATE" />
|
|
|
|
<!-- We target phone + TV from day one: keep the app installable on TV (no touchscreen) and on
|
|
devices without a gamepad. -->
|
|
<uses-feature android:name="android.hardware.touchscreen" android:required="false" />
|
|
<uses-feature android:name="android.software.leanback" android:required="false" />
|
|
<uses-feature android:name="android.hardware.gamepad" android:required="false" />
|
|
|
|
<!-- appCategory="game": a game-streaming client IS a game as far as the SoC is concerned.
|
|
On Snapdragon devices (and other OEMs with a Game Mode / Game Dashboard) this makes the app
|
|
eligible for the vendor's game performance profile — the aggressive CPU/GPU governor and
|
|
scheduler treatment games get — which, together with the ADPF hints in the native decode
|
|
path, is what keeps clocks up for low, consistent decode latency. Also groups it correctly
|
|
under Games in battery/data usage. Advisory: devices without Game Mode ignore it. -->
|
|
<application
|
|
android:allowBackup="false"
|
|
android:appCategory="game"
|
|
android:banner="@drawable/tv_banner"
|
|
android:icon="@mipmap/ic_launcher"
|
|
android:roundIcon="@mipmap/ic_launcher_round"
|
|
android:label="@string/app_name"
|
|
android:supportsRtl="true"
|
|
android:theme="@style/Theme.PunktfunkAndroid">
|
|
|
|
<!-- Game Mode config (Android 13+): declare we support Performance mode and opt OUT of the
|
|
OEM interventions that would fight the negotiated stream — resolution downscaling and
|
|
FPS overrides. A game-streaming client renders exactly the host's mode; a platform
|
|
downscale/FPS-cap corrupts that. Ignored below API 33. -->
|
|
<meta-data
|
|
android:name="android.game_mode_config"
|
|
android:resource="@xml/game_mode_config" />
|
|
|
|
<activity
|
|
android:name=".MainActivity"
|
|
android:exported="true"
|
|
android:configChanges="orientation|screenSize|keyboardHidden|screenLayout|density|navigation"
|
|
android:theme="@style/Theme.PunktfunkAndroid">
|
|
<intent-filter>
|
|
<action android:name="android.intent.action.MAIN" />
|
|
<category android:name="android.intent.category.LAUNCHER" />
|
|
<!-- TV launcher entry. -->
|
|
<category android:name="android.intent.category.LEANBACK_LAUNCHER" />
|
|
</intent-filter>
|
|
</activity>
|
|
</application>
|
|
</manifest>
|