I use my droid with Strava too. Here's what I've found after a couple of months:

If you're losing part of the ride, shut the phone display off a couple of seconds after you acquire GPS signal and the clock on the app starts registering seconds passing. This seems to have ended that problem.

Elevation stats often don't even come close.

"Max speed" can be all over the place.

I live near the ocean too, and I regularly ride across bodies of water. At least according to Strava.

My wife and I went on the same ride on Saturday. She's slower than I am. I waited for her on the top of several hills. But our elapsed time, and ride distance, should have been the same. She rode a mile farther, climbed 1200 more feet, and averaged a full mph faster---according to Strava. Using the same brand/model of android phone.

Stopped time--at least for the brief stops at red lights, and the occasional "dash into the weeds to water the bushes" stop, is often logged at moving time at low mph. Something like 0.5 mph to 1.5 mph. Not that I care, because IMO average speed for a ride should take this into account anyway. But why have an "elapsed time" vs "moving time" feature if it often doesn't work with android?

Long story short---go with Garmin if you care about accuracy. I'm not that concerned with it, but I have a birthday coming up in a month and may hint to the bride.