Pulled out a node to use just for testing purposes (heltec t114 v1 which was known faulty hardware and was replaced) and plugged it in to my PC in the basement, and for some reason it wouldn't pick up ANY other nodes in the Contact app. I tried reseating the antenna, tried a different antenna, tried moving it around, eventually figured out the reason it wasn't seeing anything was that it had been reset and the region hadn't been set yet. Set the region in settings (and had to manually reboot), and suddenly I've got nodes to talk to.
We should probably have some kind of prompt/initial setup screen if we detect that the radio's region is unset so it's more obvious what is going on in this situation and give the user an easy way to get started.
Pulled out a node to use just for testing purposes (heltec t114 v1 which was known faulty hardware and was replaced) and plugged it in to my PC in the basement, and for some reason it wouldn't pick up ANY other nodes in the Contact app. I tried reseating the antenna, tried a different antenna, tried moving it around, eventually figured out the reason it wasn't seeing anything was that it had been reset and the region hadn't been set yet. Set the region in settings (and had to manually reboot), and suddenly I've got nodes to talk to.
We should probably have some kind of prompt/initial setup screen if we detect that the radio's region is unset so it's more obvious what is going on in this situation and give the user an easy way to get started.
<!-- github-sync-id:2839314902 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Pulled out a node to use just for testing purposes (heltec t114 v1 which was known faulty hardware and was replaced) and plugged it in to my PC in the basement, and for some reason it wouldn't pick up ANY other nodes in the Contact app. I tried reseating the antenna, tried a different antenna, tried moving it around, eventually figured out the reason it wasn't seeing anything was that it had been reset and the region hadn't been set yet. Set the region in settings (and had to manually reboot), and suddenly I've got nodes to talk to.
We should probably have some kind of prompt/initial setup screen if we detect that the radio's region is unset so it's more obvious what is going on in this situation and give the user an easy way to get started.
I fully support this. I ran into a similar issue just this week!