TROUBLESHOOTING

• “For those getting Location Disabled, do this: Android Settings, Security & location, Privacy Location, Use location slider. If it's off, slide so it's on. If it's disabled, slide to off, then on. RFinder should be listed under Recent location requests. Back out then Restart twice. The GPS at top of radio needs a couple minutes to lock with a good look at the sky. Seconds if it's had a recent lock, up to 10 if it's past a month or so.” Source: David Dobbins
  
• “If you pull down the dropdown from the top of screen. Look for teardrop (location) it should be highlighted, tap on it if it is not highlighted. May have to swipe to the second page to find, and reboot the phone. Easier way.” Source: Bob Vincent

“…I got the Android Auto to work. The trick was connecting a data cable between M6 USB port, not charge port, and the vehicle.” “One thing I am not sure that matters, I did have developer turned on. I generally do this with all my android devices to let me play around with the configuration.” Source: Randy Umfleet

“M6 users: FYI, in case you're getting low audio reports and not sure where the teeny tiny microscopic microphone hole is, it's here, lower right corner. That's where you want to speak into.” Source: David Dobbins

OpenSpot 4 Pro from SharkRF
Issue: B1+ (UHF frequency) not hearing announcements/transmits in DMR simplex from the OpenSpot 4 Pro.

RFinder.net/Customer Support Response/Info:
“I would like to acknowledge that the fact that the other radios are acknowledging when you transmit on your RFinder, simplex DMR does work. What simplex is, is the transmission and reception frequencies being the same. And this is working with the other radios.

The issue with the OpenSpot is that DMR spectrum is not at the typical 0 through (+) 1000 or so offset spectrum that most hotspots and radios use. In many circumstances, the OpenSpot hotspots actually use a (-)1000 offset, which can cause a misalignment in the DMR spectrum in some cases. Many radios have a broad DMR spectrum, whereas RFinder devices have a stronger, but more specific spectrum range that requires being within more direct range.

What I have been trying to do, is figure out where the range is for the OpenSpot hotspot for you. I was working with a user who had the OpenSpot 1 and 3, and said -1000 on the QRG offsets of his radio allowed it to connect, when he had the same issue as you. If you don’t mind, could you increment your radio’s QRG offsets back by -200 up until -3000? If your radio still does not work at that point, we will evaluate what the next steps will be.”

User Note:
Picked up a new B1+ at Ham Radio Outlet, and the unit works with the OpenSpot 4 Pro (hears announcements, tx, rx). It appears the issue was with the first unit itself; for some reason it wasn't compatible with the OS4 Pro. New unit - sideloaded current (Oct 20, 2022) RFinder version without issue: rfinder_ham_rf1_1.6.apk

If using Mint Mobile and hearing slow speech, set the APN Protocol to IPv4 (instead of IPv6).
On B1-Plus: Android Settings | Network & Internet | Mobile Network | Advanced | Access Point Names | Mint (or T-Mobile US LTE) | APN Protocol | IPv4

Issue: While in DMRoIP, radio will go red for tx and then drops off.
If you are not getting the double tone when pressing PTT, check volume on the right side of your RFinder B1 if the volume is mute. Lowest setting- you won't get the tone when pressing PTT, increase the volume on the right side and press PTT- you should get the double tone when pressing PTT when the TG is inactive.