Facepalm - it would appear that while all the instructions I read say to disable gpsd.socket, none say to reenable it. Maybe under different circumstances it's not needed, but it *seems* to have worked for me.
I followed this video:
One thing still unclear is why changing the ip from 127.0.0.1 to 0.0.0.0 in /lib/systemd/system/gpsd.socket. In my case, doesn't seem to matter.
Anyway, I put all this on the top to spare others some reading.
Apologies if this is a duplicate - I thought I'd asked this last night but didn't see it listed under "My Topics"
Somehow, in troubleshooting my second Pi4 w/AB203, I have changed something on my primary Pi4 w/AB203 so that gpsd no longer comes up at boot. This is my primary Pi4 w/UART gps. It had an issue whereby it would sometimes show the wrong location, but I was told this was due to vgps running. Maybe when I disabled that I somehow disabled something else?
I use the gpsd.socket, you can disable it but then you must enable and start the gpsd.service to be launched all the time. The use of a .socket in systemd allows for the creation of the socket so other services or processes see that it's up but the process itself isn't running.