Bluetooth is very hit and miss for me. Mostly miss. I wouldn’t buy it for Bluetooth support. It just doesn’t work most of the time. At least not on later firmware.
What I bought it for was Glonass support (Russian satellites). In theory more accurate due to additional satellite support and they claim good for in trees. Turns out I’ve had the odd ride slightly off at times, some segments won’t match in Strava. Still seeing a bit of straight lining in places. No different to on the phone basically. Advice is though to ensure it’s got a good fix first. Don’t just wait for it to beep it has GPS fix, which is very quick. Check the system GPS menu and ensure it’s got all or most satellites, or just wait a good few minutes with it out in the open before starting the ride. A lot of reported data loss has been when fix isn’t quite right. Also, haven’t tried 1s sampling which might help with straight lining. Currently have it set to Smart.
And then there’s general ride data loss. Not sure it’s the 510 though. I’ve nailed it down to either the use of Garmin Express to sync, or powering off the device after saving a ride before uploading. I’ve eliminated both and not losing rides any more.
Personally though , I wish I’d bought a 500 for a fraction of the price, or an 800 for similar price and includes mapping. More mature products.