1 views collected around this technical thread.
This article explains how to securely use Android components during development by identifying risk points, recommending proper use of the android:exported attribute, custom permissions, intent validation, and safe BroadcastReceiver and ContentProvider practices to enhance app reliability and security.
This article explains various Android keep‑alive techniques—including boot‑time auto‑start, account‑sync mechanisms, foreground services, and scheduled jobs—providing code examples and configuration steps to help apps stay alive while also showing how to disable these features on specific devices.
This article outlines essential security checks for Android components—including Activity, WebView, BroadcastReceiver, Service, and ContentProvider—highlighting common vulnerabilities such as exported components, SSL handling, saved passwords, implicit intents, and unsafe broadcast APIs, and provides practical code examples and mitigation steps.
Developers can create a custom Android lock screen by starting a foreground service that registers a dynamic SCREEN_OFF broadcast, launching a lock‑screen activity with keyguard‑dismiss and immersive window flags, handling swipe‑to‑unlock gestures, making navigation bars transparent, and integrating fingerprint authentication while respecting system security constraints.