DroidLink 2.0 V2
DroidLink 2.0 V2
Security and stability hardening:
- Validates room codes, SDP, ICE candidates, and controller payload sizes
- Limits stale, duplicate, oversized, and excessive signaling data
- Uses secure room-code generation and tighter TURN response parsing
- Disables cleartext Android traffic and app-data backup
- Restricts screen-capture service broadcasts to DroidLink
- Improves broad Android controller mapping and Controller Test behavior
- Preserves the working WebRTC video, game-audio, signaling, and low-latency controller architecture
Important scope:
- Players 3 and 4 are not enabled in this build. Safe multi-peer video requires a tested multi-PeerConnection host architecture.
- Microphone voice chat is not enabled. It requires safe mixing/isolation from the existing game-audio capture pipeline.
- Firebase server-side authorization still requires deployed Firebase Authentication/security rules; APK-side validation alone is not a complete access-control boundary.
Build verification:
- :app:testDebugUnitTest passed
- :app:assembleDebug passed
Physical-device security, streaming, and controller verification is still required.