Change-Id: I77443672f75e1554b4ef91fb5ef58611f310f696

Change-Id: Idd8c3f3fa90d3ecf6e5b8eef98767cf8b2a8f299

* actions/checkout@v3 -> actions/checkout@v4
* actions/setup-java@v3 -> actions/setup-java@v4
* actions/upload-artifact@v3 -> actions/upload-artifact@v4

Change-Id: Ib4a69e348202d81643815f583dde6513c8b3b90a

Change-Id: Ic5a07212bdc12d7a095a74395d7f56b36fbb11e4

Change-Id: I51f96c95dfc2a32b3cf1702d96ecf3d5195ca35b

Change-Id: Ia6f2d09b179b9934d05f251ab00969fb3a1666bd

Change-Id: I73efe731187e166c4293eb4721c36859ab3d7170

Change-Id: I1818d5928bc9b42171bd0032d93e851324617b73

Recorder is already properly handling requests to record audio
and return the file as Uri.

However, we also need to explicitly grand read permissions for the
Uri, otherwise the requesting app can not use the recording.

  E MediaPlayerService: Couldn't open fd for content://0@media/external_primary/audio/media/1000000046
  E MediaPlayerNative: Unable to create media player
  E ByodPresentMediaDialog: Cannot play given audio with media player.
  E ByodPresentMediaDialog: java.io.IOException: setDataSource failed.: status=0x80000000

Test: CTS-Verifier - https://source.android.com/docs/compatibility/cts/verifier


  - BYOD Managed Provisioning
    - Start BYOD provisioning flow
    - Sound recorder support cross profile audio capture
Test: manualTests#com.android.cts.verifier.managedprovisioning.ByodFlowTestActivity
Change-Id: Ic107d21ae309a425842b94eeea11c614e3357bbe
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>

Change-Id: If8c9f13c9fc3509c354475d22731695f7a2b73b6

Usually a safe set of optimizations

Change-Id: I1074af3a758439ff82771b03bdb0c4484828ca25

Change-Id: I1cecdd062b672764cb3f34d0f2e6477ed41f0154

Test: pipx run reuse lint
Change-Id: I60e94334e4a7bd3da2ed88ed4bc2dc1d024bc301

This reverts commit ff238798.

Reason for revert: In some locale (e.g. Japanese) the change produces invalid filename that contains "/" (e.g. "Sound record (2024/09/29 19:15:33).wav"), breaking the app.

Change-Id: I7216cc3fb2897c993b526e5b9ed7ac2553aabb86

Change-Id: I7f370fc094d2eb6613be7462048327bf31e32422

Change-Id: I1d58491f417943a204178aee8b12843dc2f44c50

 Conflicts:
	app/Android.bp
	app/src/main/res/values/styles.xml

Change-Id: Iae5642e56c52691935bb66f5a0e4705955a0f6e9

Change-Id: I10b0c4a4bdde87a5113c9efede4f75e5c27a06cf

Since the service isn't exported no other app can start
and/or interact with it, only explicit intents within
the app are supported.

Note: They got changed and notification worked without
      fixing the manifest.

Change-Id: Ic2c21834c494b51395a57f7a8593f612ad13dba7

Query code stolen from Glimpse

Co-authored-by: Luca Stefani <luca.stefani.ge1@gmail.com>
Change-Id: Ibed443b7e0b0860a1a4511987c9a8b5cde14096a

Change-Id: I13a9e87b0c0ca804f6125515189337e673db1994

Change-Id: I0b2767e06e3db1a0a36a294fa45e83f5f9a263e0

Since BuildConfig is deprecated we now get the package
name from the application context
We remove the app name from the service actions, as those
actions are to be handled only internally in the service,
they don't need to be specific.

Change-Id: I4205f7af457955b59790201a97ea60b8bec4d0aa

Theme app according to our palette

See merge request !36