EFForg
[Feat] Add steps to documentation for developing new devices
What problem does this feature solve or what does it enhance?
Currently, the documentation is unclear on what devices need to have support for rayhunter.
Proposed Solution
It would be nice to have some documentation that not only lists how the program generally works on a technical level (ideally a flow chart?), but also lists what requirements client devices need, so that a developer can more easily port the program to new hardware if desired.
Alternatives Considered
N/A
My specific motivation for this is because there are currently only 1 device for the Asia/Oceania region that are actually obtainable in Australia, and from all the links provided for UZ801, only ONE actually delivers to australia, and that's through amazon, and I'd love to develop additional (ideally more australian accessible) device support for further research.
we have had multiple threads in Discussions about new devices:
https://github.com/EFForg/rayhunter/discussions/479 https://github.com/EFForg/rayhunter/discussions/484 https://github.com/EFForg/rayhunter/discussions/517 https://github.com/EFForg/rayhunter/discussions/560
I agree that a docs page summarizing this would be helpful.
I'm pretty sure the TP-Link M7350 actually works in Australia and the docs are wrong. Basically if it is being sold locally, you can probably use it to connect to the internet there, and then rayhunter also probably works.
Unfortunately the M7350 is >$120 local currency here. From what I can gather, the main barriers to getting any device working is the usb debugging support + ADB, plus a qualcomm modem and exposing via /dev/diag?
yes, except we don't specifically need USB debugging or adb, any way to acquire root shell will work.
@oopsbagel could probably write a pretty great page about adding new devices :)
