doc: add region table, map for recommended devices

Implement reordering from untitaker's suggested changes.
This commit is contained in:
oopsbagel
2025-06-29 02:05:58 -07:00
parent 60922afc87
commit d03debe67c
2 changed files with 14732 additions and 12 deletions
+14708
View File
File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 1.2 MiB

+24 -12
View File
@@ -1,17 +1,29 @@
# Supported devices # Supported devices
Be sure to check your location's [supported frequencies](https://www.frequencycheck.com/) against a device page before obtaining a device.
## 1. Recommended devices
These devices have been extensively tested by the core developers and are widely used. **Use one of these devices if you can.**
| Device | Region |
| ------ | ------ |
| [Orbic RC400L](./orbic.md) | Americas |
| [TP-Link M7350](./tplink-m7350.md) | Africa, Europe, Middle East |
The TP-Link M7350 also works in the Americas but is usually more expensive.
![device_regions](device_regions.svg)
_Derivative work of [this file](https://commons.wikimedia.org/wiki/File:International_Telecommunication_Union_regions_with_dividing_lines.svg) by [Maximillian Dörrbecker](https://de.wikipedia.org/wiki/User:Chumwa) licensed [CC BY-SA 2.5](https://creativecommons.org/licenses/by-sa/2.5)_
## 2. Functional devices
Rayhunter is confirmed to work on these devices.
| Device | Region |
| ------ | ------ |
| [Wingtech CT2MHS01](./wingtech-ct2mhs01.md) | Americas |
| [TP-Link M7310](./tplink-m7310.md) | Africa, Europe, Middle East & Americas |
## Adding new devices
Rayhunter was built and tested primarily on the Orbic RC400L mobile hotspot, but the community has been working hard at adding support for other devices. Theoretically, if a device runs a Qualcomm modem and exposes a `/dev/diag` interface, Rayhunter may work on it. Rayhunter was built and tested primarily on the Orbic RC400L mobile hotspot, but the community has been working hard at adding support for other devices. Theoretically, if a device runs a Qualcomm modem and exposes a `/dev/diag` interface, Rayhunter may work on it.
If you have a device in mind which you'd like Rayhunter to support, please [open a discussion on our Github](https://github.com/EFForg/rayhunter/discussions)! If you have a device in mind which you'd like Rayhunter to support, please [open a discussion on our Github](https://github.com/EFForg/rayhunter/discussions)!
## Tier 1 - Fully supported devices
These devices have been extensively tested by the core developers and are widely used. We recommend running Rayhunter on one of these devices if you can.
- [Orbic RC400L](./orbic.md)
- [TP-Link M7350](./tplink-m7350.md)
If you are in the US, use the Orbic. TP-Link M7350 also works but is usually more expensive to obtain. Otherwise use TP-Link M7350.
## Tier 2 - Functional devices
Some developers have succeeded in getting Rayhunter running on these devices, but they have not received the same level of adoption as tier 1 devices.
- [Wingtech CT2MHS01](./wingtech-ct2mhs01.md)
- [TP-Link M7310](./tplink-m7310.md)