if your app does not require multi-touch support on every screen, it can be disabled by adding this lines to your app theme

#sdk #multitouch #theme

<item name="android:windowEnableSplitTouch">false</item>
<item name="android:splitMotionEvents">false</item>

if your application is declared to use the Manifest.permission.CAMERA, which is not granted, trying to use the MediaStore.ACTION_IMAGE_CAPTURE action
will result in a SecurityException

however, you can bypass this restriction by using a similar action – MediaStore.ACTION_IMAGE_CAPTURE_SECURE

#sdk #permission #camera

sometimes you need to create an activity the only purpose of which will be to perform some action and finish immediately. these activities do not actually display the user interface, they finish themselves before they are resumed

there is a theme for such activities that you can use – android:Theme.NoDisplay

#sdk #theme #activity

there are scenarios where you cannot run the application with the debugger, for example when the application process is restarted.

to be able to attach the debugger in the right place there is a method Debug.waitForDebugger(). it will block execution until you attach the debugger manually

#sdk #debug #restart

the Activity class has a reportFullyDrawn() method. It is useful when you want to measure the time from startup to the moment the app content is loaded

call it when the UI is fully rendered and populated with all the necessary data, logcat will output how much time has passed from startup to the moment of the call

#sdk #activity #startup

If you want to go completely full screen - there are plenty of tutorials. But if you have a device with cutouts there is one more thing to do.

Add to your app's theme android:windowLayoutInDisplayCutoutMode and set it to always. This will allow your app to extend into the cutout areas on the all edges of the screen.

#sdk #theme #fullscreen

Since API level 30, the View class has a method isShowingLayoutBounds, which returns true if the view is attached and the system developer setting to show the layout bounds is enabled.

This is useful if you want to add debug drawing for a custom view in a nice way.

#sdk #customview #debug

There's a classic problem: create an intent that will only open email clients, and will have an attachment. The tricky part is that Intent.ACTION_SENDTO cannot accept an attachment, while Intent.ACTION_SEND opens not only email clients.

The solution is to use seleclor, which allows you build an intent containing a generic protocol while targeting it more specifically to open email clients only.

#sdk #intent #email

val selectorIntent = Intent().apply {
    setAction(Intent.ACTION_SENDTO)
    setData(Uri.parse("mailto:"))
}
val intent = Intent().apply {
    setAction(Intent.ACTION_SEND)
    setSelector(selectorIntent)
    // Add attachment
}

The View class has an API for setting a tooltip, that will be shown to the user on a long click, or on a mouse hover event.

You can specify the tooltip text by calling the View#setTooltipText() method.

#sdk #view #accessibility

Since API level 31 the apps are required to check for SCHEDULE_EXACT_ALARM permission in order to use exact alarm APIs.

To make the user’s life easier, you can set the Intent's data URI to specify the application package name to directly invoke the management UI specific to your app.

#sdk #permission #alarms

val intent = Intent(
    Settings.ACTION_REQUEST_SCHEDULE_EXACT_ALARM,
    Uri.parse(context.packageName),
)

If you have a transparent activity, you might as well want to disable a splash screen.

Luckily, there is a flag just for that.

#sdk #theme #splash

<item name="android:windowDisablePreview">true</item>