Raja Luck - Permissions, Battery and Background Behaviour

Raja Luck is a real-money colour-prediction platform popular across India. Players deposit funds through UPI providers such as PhonePe, Google Pay and BHIM, join timed rounds where they predict a colour or number outcome, and withdraw winnings directly to their linked bank account. Because stakes and payouts involve actual rupees, the app you install on your Android device deserves careful scrutiny at the operating-system level. This site covers Raja Luck from a device-management perspective, permissions, background behaviour, battery impact and clean removal, so you stay in control of your phone while you play.

Raja Luck Every Permission Requested, and Which Ones to Deny

When you sideload the Raja Luck APK and launch it for the first time, Android presents a series of runtime permission dialogs. Internet access and network-state are declared in the manifest and require no dialog, both are essential for live round countdowns and UPI deposit confirmation via PhonePe or Google Pay. Vibration fires a haptic pulse on round results; safe to allow. On Android 13 and above, POST_NOTIFICATIONS is a runtime ask; grant it if you want withdrawal-confirmed alerts, but you can deny it and navigate manually without losing any gameplay.

CAMERA appears legitimately during KYC verification when your first withdrawal crosses the document threshold, grant it temporarily, then revoke it afterward at Settings → Apps → Raja Luck → Permissions.

Deny READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE (Android 12 and below) if you do not want the app writing files outside its private sandbox; gameplay continues normally. Deny ACCESS_FINE_LOCATION outright, no colour-prediction mechanic requires GPS coordinates. Any prompt for READ_CONTACTS, READ_SMS or RECEIVE_SMS is a hard stop; legitimate UPI flows use Android's one-time-password API and never need your full inbox or address book.

Raja Luck Notification Channels You Can Silence Individually

Modern Android splits app notifications into discrete channels, meaning you do not have to silence Raja Luck entirely just to stop one noisy alert type. Open Settings → Apps → Raja Luck → Notifications and you will typically see channels for round-start countdowns, promotional offers, transaction status and general system messages. Transaction-status notifications, confirming that your PhonePe or BHIM deposit landed, are worth keeping on. Promotional and round-start channels can be toggled off without affecting your ability to track withdrawals.

If you want round alerts only during specific hours, use Android's built-in Do Not Disturb schedule rather than revoking the notification permission entirely. Set DND to lift between, say, 20:00 and 23:00 IST when rounds are most active, and the app's alerts surface only in that window. This is a cleaner approach than toggling the POST_NOTIFICATIONS permission on and off, which forces a fresh permission dialog every time you re-enable it on Android 13 plus devices.

Raja Luck What the App Does While the Screen Is Off

With the screen off, Raja Luck maintains a persistent WebSocket connection to its game server so it can deliver round-result pushes without a full wake cycle. This is standard practice for real-money apps and costs roughly 1 to 3 MB of background data per hour on a stable connection. Where it differs from casual games is the keep-alive interval: because round windows are short, often 60 or 90 seconds, the app pings the server more frequently than a chat or news app would, which keeps the radio active longer and adds a measurable drain on both data and battery.

Android's Battery → Background usage limits screen (or the equivalent on MIUI, ColorOS and Realme UI) shows cumulative background data per app over the last seven days. If Raja Luck appears near the top of that list on days when you did not actively play, the background connection is running beyond its useful scope. The fix is to set the app's background data to "Restricted" when you are not playing, then switch it back to "Unrestricted" before a session, a two-tap change that prevents idle radio usage without uninstalling anything.

Raja Luck Battery Optimisation on Xiaomi, Realme, Oppo and Vivo

Chinese-brand Android skins aggressively kill background apps, which can interrupt Raja Luck's WebSocket mid-round. On Xiaomi / MIUI, go to Settings → Apps → Manage apps → Raja Luck → Battery saver and set it to No restrictions during active play, then revert to Battery saver afterward. On Realme UI, the equivalent path is Settings → Battery → App quick freeze, ensure Raja Luck is not listed there. On Oppo / ColorOS, visit Settings → Battery → App energy consumption details and allow background activity. On Vivo / FuntouchOS, open i Manager → App Manager and disable "Auto start manager" restriction for Raja Luck.

The trade-off is real: allowing background activity extends the keep-alive connection and costs extra battery. A practical middle ground is to enable unrestricted background only during your intended play window and use the brand-specific "Battery saver" or "Auto start" toggle to curtail it afterward. Users who play for one or two sessions a day and then restrict background report a noticeable improvement, roughly 5 to 8% better end-of-day charge, compared with leaving the app fully unrestricted around the clock.