Initialize the repo for the OpenBeam application

[Copilot]

Three UX/NFC bugs in the sharing flow:

1. Double title — Theme.Material3.DayNight.Dialog renders its own window title slot above the dialog box, duplicating the tv_app_name inside it.
2. NFC tap sound on non-writable tags — enableForegroundDispatch lets the OS play its default tap sound whenever any NFC tag (e.g. a payment card) is detected, even if we do nothing with it.
3. HCE / other NFC apps not blocked — foreground dispatch doesn't pause Host Card Emulation, so the device could still respond to payment terminals while sharing.

Changes

• ShareActivity: call supportRequestWindowFeature(Window.FEATURE_NO_TITLE) before super.onCreate() to remove the window title slot before the Dialog window is created. (supportActionBar?.hide() doesn't reach this; it only affects the AppCompat action bar layer.)

• NfcShareHelper: replace enableForegroundDispatch / disableForegroundDispatch with enableReaderMode / disableReaderMode:

  • FLAG_READER_NO_PLATFORM_SOUNDS — suppresses the OS tap sound for all detected tags.
  • Reader mode pauses HCE while active, blocking payment terminal responses and other NFC apps.
  • Non-NDEF tags (EMV, ISO 15693, etc.) are silently dropped in the reader callback — Ndef.get(tag) and NdefFormatable.get(tag) both return null for them.
  • The reader callback runs on a background thread; pendingMessage / onResult marked @Volatile.

• ShareActivity: SoundManager.playBeam moved from onNewIntent (now a no-op) to the NfcShareState.Writing branch — plays only when writing actually begins on a capable tag.

Original prompt

Initialize the repo for the new application OpenBeam, which is an attempt to clone "Android Beam" experience for newer Android OS versions. There is another project that implements similar, https://github.com/jzadl/openbeam , you can have a look for additional info.
Your mission is to gather information from Android Beam original functions and development code, the integrations available, and information about Quick Share functions and development code, how to integrate it. Write documents with relevant findings to keep local context available (quote the source URL or docs) and make brief summaries for the technical relevant part as we want to implement.
The app should not open by itself nor the icon should appear on the App menu, as it is a service used when "sharing through applications".
Some of the resources to share are URLs, Vcards (contact info), and images.
When sharing an image, scan the image if contains a readable QR code, and if so, interpret it and convert to NDEF compatible message (expected codes are URLs and WiFi credentials, define the class to allow supporting more types in the future).
If the image does not contain a QR, fallback to Quick Share implementation to share the file.
Avoid Google implementation as much as possible (prefer OSS alternatives without Google Services), but you may add it if required for maximum sharing compatibility and enhanced experience.
Write documents with plan and technical details and start implementation right away.
Add translations for Spanish, Catalan and English. Define a top-most UI when sharing, share once and then close/exit the app when done. Add sounds when interacting. Be brief but concise. Make as much as you can in this first iteration.

[github-actions]

✅ Debug APK artifact is ready for commit cba5f1e .
💾 Download APK artifact here.
Workflow run: https://github.com/duhow/openbeam/actions/runs/28736334047