Skip to content

Conversation

@jo-bitsch
Copy link

aoa-proxy is a tool to interact with Android devices using the Android Open Accessory Protocol.

📦 Package Details

Maintainer: Jó Ágila Bitsch @jo-bitsch

Description:
This package aims to make working with Android Open Accessory (in
particular v1) as easy as possible.
It has 2 modes, depending on the state of the attached Android device.
(1) Announce mode: When the Android device is not yet in AOA mode, this
program announces its identity to the Android device and tries to
put it into AOA mode.
(2) Forwarding mode: Forward all input from stdin to the AOA device and
all output from AOA to stdout.
For OpenWrt, it includes a hotplug script and a service to automatically
announce itself and forward AOA traffic to SSH/dropbear.

It is particularly helpful for initially configuring a newly flashed OpenWrt
device if you need to set initial networking parameters.


🧪 Run Testing Details

  • OpenWrt Version:
  • OpenWrt Target/Subtarget: x86_64, generic, 24.10.5
  • OpenWrt Device: x86_64, generic, 24.10.5 in QEMU

✅ Formalities

  • I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

It does not contain a patch.

@jo-bitsch
Copy link
Author

This is a resubmission of #22538, as the newly introduced formalities check requires a submission from a different branch name

Thanks a lot to @GeorgeSapkin and @BKPepe for guiding me so far through #22538.

@jo-bitsch
Copy link
Author

There seems to be an issue now with using libb64 (https://github.com/openwrt/packages/actions/runs/20530645860/job/58981616804?pr=28184#step:6:6117, https://github.com/openwrt/packages/actions/runs/20530645860/job/58981616800?pr=28184#step:6:6122, etc)

This worked fine locally. I'll have to investigate a bit further.

@jo-bitsch jo-bitsch force-pushed the add-new-package-aoa-proxy branch 2 times, most recently from d16bead to 1a8e58e Compare December 27, 2025 13:35
@jo-bitsch
Copy link
Author

The last build had an issue in the following step:
Test and Build / Feeds Package Test Build / Test mips_24kc (pull_request)

In particular: https://github.com/openwrt/packages/actions/runs/20539726246/job/59003830984#step:17:35

(1/3) Installing libatomic1 (14.3.0-r5)
  Executing libatomic1-14.3.0-r5.post-install
(2/3) Installing libusb-1.0-0 (1.0.29-r1)
Bus error (core dumped)
Error: Process completed with exit code 138.

This is from installing libusb-1.0 and at this point doesn't touch my code yet. (And the same works fine on the other platforms.) I'll update the copyright year as suggested by @GeorgeSapkin. Let's see if this is a transient issue.

aoa-proxy is a tool to interact with Android devices using the
Android Open Accessory Protocol.

Co-authored-by: Jeffery To <jeffery.to@gmail.com>
Signed-off-by: Jó Ágila Bitsch <jgilab@gmail.com>
@jo-bitsch jo-bitsch force-pushed the add-new-package-aoa-proxy branch from 1a8e58e to 6ad282c Compare December 27, 2025 18:53
@jo-bitsch
Copy link
Author

So the failing checks now are:

  1. The same as above, a bus error while installing libusb-1.0 seemingly unrelated to this PR (as the new package was not even installed yet in that step) in mips24kc.
    While this happened for the second time in a row, this does not seem to be transient, but seems to be another issue, independent to of my PR. libusb-1.0 as part of the base feed from the main openwrt repo (https://github.com/openwrt/openwrt/blob/main/package/libs/libusb/Makefile) and a dependency of many many packages is presumably much better tested though.
  2. An error building the Docker Container because of a transient error with the docker registry for i386_pentium-mmx.

The code changes from the last commit to this one were only the change of the copyright year in a comment.

@GeorgeSapkin Please advise, how I can proceed.

Thanks a lot for your help and guidance so far. I really appreciate it!

@jo-bitsch
Copy link
Author

When I'm running the mips_24kc environment in docker/qemu (my host is a amd64 running ubuntu) I get the exact same error:

$ docker run  --platform linux/mips_24kc -ti --rm openwrt/rootfs:mips_24kc sh

BusyBox v1.37.0 (2025-12-27 18:26:10 UTC) built-in shell (ash)

/ # apk update && apk add libusb-1.0-0
 [https://downloads.openwrt.org/snapshots/targets/malta/be/packages/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/base/packages.adb]
 [https://downloads.openwrt.org/snapshots/targets/malta/be/kmods/6.12.62-1-1dd18a42a75eb83b03f5cc18551d863d/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/luci/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/routing/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/telephony/packages.adb]
 [https://downloads.openwrt.org/snapshots/packages/mips_24kc/video/packages.adb]
OK: 10529 distinct packages available
(1/2) Installing libatomic1 (14.3.0-r5)
  Executing libatomic1-14.3.0-r5.post-install
(2/2) Installing libusb-1.0-0 (1.0.29-r1)
 60% ########################################################################################################################################                                                                                        qemu: uncaught target signal 10 (Bus error) - core dumped
Bus error (core dumped)
/ # echo $?
138
/ # 

As this is completely independent of my PR, should I open an independent issue?

I'll try to analyze this further.

@GeorgeSapkin
Copy link
Member

It's probably something Qemu-specific. I don't think it's relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants