flamyoad / adr_playground Goto Github PK

Use case to alert user from avoiding large downloads over mobile data.

Eg: Wifi connected to Hotel (not yet authenticated with password), mobile data on.

https://stackoverflow.com/questions/69741827/android-12-how-to-prevent-activity-restart-on-changing-phone-wallpaper

https://issuetracker.google.com/issues/199995249

it's wrong to use onStop to detect user tapping home button / changing to other apps 👎

With Android 13 comes READ_BASIC_PHONE_STATE which returns only some data like system version or network type to which it is connected, therefore being a less dangerous permission than the previous one.

let's check if it can be used to detect phone call

https://developer.android.com/reference/android/Manifest.permission.html#READ_BASIC_PHONE_STATE

https://dontkillmyapp.com/

https://developer.android.com/training/scheduling/wakelock

(Foreground service + Wake Lock + Letting user whitelist your app seems the only solid option if your app targets Chinese market).

Need to acquire a wake lock if you want your service keep running after the screen is off.

But from my testing, 15min+ is still good on Samsung. However, Seems FGS alone is not enough to keep app alive in bg :)

Starting in Android 13 (API level 33), users can dismiss the notification associated with a foreground service by default.

If you would like the notification to be non-dismissable by the user, pass true into the setOngoing() method when you create your notification using Notification.Builder.

https://stackoverflow.com/a/75026688/8621574

        return NotificationCompat.Builder(this, MY_FOREGROUND_CHANNEL_ID)
            setContentTitle("Title")
            .setContentText("Text")
            .setGroup("abccccc") // Prevent the FGS notification from being lumped in together in same group with others 
            .setContentIntent(pendingIntent)
            .setSmallIcon(com.flamyoad.styles.R.drawable.ic_notification_2)
            .setPriority(NotificationCompat.PRIORITY_HIGH)
            .setOngoing(true) // Starting in Android 13 (API level 33), users can dismiss the notification associated with a foreground service by default.
            .build()
    }

If an app has foreground service that depends on a RX stream that has lifecycle in @ApplicationScope (it's inside Application class)

If app is swiped up, foreground service will keep running, but is the app still running????

Any chance that closing the application manually will leave only the service running???

Context is the foreground service is broken if the @ApplicationScope stream is terminated.

It should be yes but We can't be too sure of it nowadays. Please check by running code on android 12 / 13

    // need to worry about transparency, !#!@#!@#!!#!@#!@#
    Glide.with(context)
        .asDrawable()
        .centerInside()
        .load(imageUrl)
        .into(object: CustomTarget<Drawable>(32, 32) {
            override fun onResourceReady(resource: Drawable, transition: Transition<in Drawable>?) {
            }
            override fun onLoadCleared(placeholder: Drawable?) {
                // no-op
            }
        })

fuck

Original image: https://w7.pngwing.com/pngs/941/692/png-transparent-black-small-apple-logo-logo-material-apple-logo-black-thumbnail.png

Downscaled INTO :

1. activate first FGS
2. activate 2nd FGS with android:stopWithTask="true"
3. swipe up app in Recents
4. 2nd FGS is still there

it shouldnt be possible