Skip to content

Validate cleaned Godot Android integration - #11

Closed
linuxificator wants to merge 3 commits into
upstream/android-oboefrom
upstream/godot-android
Closed

Validate cleaned Godot Android integration#11
linuxificator wants to merge 3 commits into
upstream/android-oboefrom
upstream/godot-android

Conversation

@linuxificator

Copy link
Copy Markdown
Owner

Fork-local validation only. This PR compares the cleaned three-commit Godot Android contribution directly against upstream/android-oboe (the head of Shorepine PR shorepine#1136) so CI exercises only the dependent Godot changes. It will be closed after validation and will not be merged.

Add a transport-only Java AmyClient helper to the Android service AAR and teach the shared Godot Amy.gd wrapper to use it on Android.

Android keeps the same high-level Dictionary-to-wire API as desktop/web, but sends each generated wire message over the app-private SOCK_SEQPACKET amy.sock transport. The Godot process does not load or compile the AmySynth GDExtension on Android and does not start or stop AmyService.
@linuxificator
linuxificator force-pushed the upstream/godot-android branch 2 times, most recently from 33d08d5 to 342a66d Compare August 23, 2026 18:54
Add a small Godot Android example that uses only the shared Amy.gd Dictionary API. The example packages the Android service AAR through a Godot export plugin and deliberately excludes the AmySynth GDExtension and AMY source from Android exports.

Add Android CI that exports ARM64 and x86_64 APKs, enforces a single AMY native implementation in the APK, and proves the high-level Amy.gd -> private socket -> :amy service -> Oboe audio path on an emulator. The emulator acceptance test deliberately ignores unrelated Godot renderer/UI failures once the AMY transport is established; it still fails on socket transport errors or missing/non-matching audio.
Document the Android Godot backend as a transport-only client of the independent :amy service. Clarify the common GDScript API, prebuilt-AAR packaging, same-UID private socket model, supported Android surface, desktop-only direct C-API/configuration differences, safe backend readiness handling, and the fact that Android exports must not include the AmySynth GDExtension or AMY source.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant