With the difference being these were settings to help locating you more quickly. Sorry, I didn’t realise it could be counter-intuitive with the switching things off and switching things on stuff in the context here.
You are now left with pure GPS capability. Even if GPS works, this might take a while to locate you depending on the circumstances, it still technically works as designed then.
I have the same problem since e OS 1.5 on my FP3 and FP3+. The only app that does not have a problem locating my Fairphone correctly is Here WeGo. Magic Earth is completely useless since 1.5.
However, similar to PCs there is a slight difference between a “warm” reboot (device doesn’t get switched off, just reboots) and a “cold” start after switching the device off.
Difference in behaviour with this has been observed e.g. with fixing network-related trouble (seen this myself, cold start is better for fixing) and with influencing launcher behaviour, interestingly, for instance here and here.
After reading in the thread “Naturalist (Ornithologist App) gets no location” that the localization issue could be related to the location module “Mozilla Location Service” and that good or better experiences have been made with “Local NLP Backend”, I installed “Local NLP Backend” and deactivated “Mozilla Location Service”. And in fact, the location works much better, almost as well as before. And if I understood correctly, there are apps that access this backend and others that only use GPS. That might explain why Here WeGo is more precise in location than MagicEarth and /e/OS.