I reboot the Windows tablet for my home gateway every weekend. Yesterday (8/5), I did the same thing. But when it rebooted and I opened the APRSIS32 client software, it wouldn't connect to the Mobilinkd TNC3. It's paired, but it doesn't connect.
This problem surfaced on my laptop station (KD0TLS-7) a couple of months ago. It took weeks of wrestling with the Mobilinkd to get it to connect over Bluetooth. In both cases, the Mobilinkd TNC4, 3, and 2 have all worked fine for years. For no apparent reason, all three of them suddenly wouldn't connect.
I looked around for help with the laptop, but found nothing useful. The usual and generic "Check your BT drivers" was popular, but did no good. Others suggested tweaking the BT settings to "Automatic", which also did no good. Mobilinkd support merely suggested that I remove and pair the TNC again, failing to grasp that pairing wasn't the issue. Still, I did that. It changed nothing.
Eventually, I created a new port in APRSIS32 for the TNC4, leaving the old port for the TNC2. That did work.
Unfortunately, the solution that worked on the laptop is not working on the tablet.
I've posted the relevant info on the Mobilinkd support forum, but I'm not expecting much.
So... without the Mobilinkd TNC, my gateway is non-functional. I've exhausted any potential remedies. It seems that Microsoft has hosed its BT stack so badly that it can't be repaired. I've heard numerous complaints from others that BT headphones, mice, etc. have stopped connecting after working for long periods. It works fine until it doesn't work, and then you get to listen to people telling you that their BT device works fine, so it must be you that's the problem.
I've confirmed that all three Mobilinkd TNCs work on APRSDroid. But you can't run a gateway on APRSDroid.
