I'm currently toying with a similar process which I think falls under the interoperability exemption:
- Get an apk online, you haven't accepted a EULA.
- Run jadx to get some code to work with
- Ask Claude to extract the protocol specification cleanly for a Bluetooth device with capabilities etc.
- Use Claude to implement a version as a TUI/CLI in go, rust, whatever.
I get to use a device I own with a local Bluetooth connection from my machine, maybe Home Assistant. I do not contact any online services (there are none anyway in that case).
Since it's to avoid getting locked in with proprietary OS, it's a clean room reversing through a spec and an LLM produced a non copyrightable output...
Can I just release this however I want?
Probably a basic MIT or CC0, whatever...
decompiling the apk is where you might trip up against DMCA etc. I've been doing this exact same thing with great success, if there's a mobile app you have the keys to unlock any bluetooth device (and maybe turn it into a Home Assistant component while you're at it).
- Get an apk online, you haven't accepted a EULA.
- Run jadx to get some code to work with
- Ask Claude to extract the protocol specification cleanly for a Bluetooth device with capabilities etc.
- Use Claude to implement a version as a TUI/CLI in go, rust, whatever.
I get to use a device I own with a local Bluetooth connection from my machine, maybe Home Assistant. I do not contact any online services (there are none anyway in that case).
Since it's to avoid getting locked in with proprietary OS, it's a clean room reversing through a spec and an LLM produced a non copyrightable output... Can I just release this however I want? Probably a basic MIT or CC0, whatever...