Google's location

[flamingm0e]

After seeing all this back and forth, I just tried it myself.

This is 100% the app.

Changing absolutely nothing else but the Google location accuracy and launching MRA. I get the pop up. Samsung Galaxy S23+ on Android 13.

Now, it's not necessarily the app's PROMPT, but it's caused, by likely something in the manifest file telling it to use Google Location API instead of the Android location api.

The app is forcing a requirement of the Google Location API. Period.

[Con Hennekens]

@Matt-Flaming said in Google's location:

The app is forcing a requirement of the Google Location API. Period.

Some people seem very keen on throwing this over the fence of MRA, without considering the much more complex programming of Android compared to the MRA App, and the fact that most users do not suffer this problem.

[flamingm0e]

@Con-Hennekens said in Google's location:

the fact that most users do not suffer this problem

Because they aren't turning off Google location accuracy?

Please, for once, can we actually discuss the problem rather than defending everything MRA does?

[Con Hennekens]

@Matt-Flaming said in Google's location:

Because they aren't turning off Google location accuracy?

I have three different devices ALL NOT having this problem, and I am smart enough to disable these dreadful "improvements" of the location services, thank you. This is what I am telling from the get go in this discussion. It is too easy to say it is "just an App problem".

But yes, I am pretty sure that MRA devs will have to invent a workaround to circumvent other parties enforcement of these location options. That's usually how it works with the Googles and the Apples in this world.

I think there is not much to discus any further.
MRA Devs promised to look into it. We will have to wait for that.

[richtea999]

@Con-Hennekens said in Google's location:

Some people seem very keen on throwing this over the fence of MRA, without considering the much more complex programming of Android compared to the MRA App, and the fact that most users do not suffer this problem.

Other location-enabled apps still work with that Google Location Accuracy option disabled. MRA is the the odd one out, as far as I can tell from a quick test.

For example, switch it off (it's a system-wide option in Settings. -> Location -> Location Services in Android 13) and try Google Maps.
You get the same popup, but selecting 'No, thanks' doesn't lock you out of using Google Maps - you get an approximate location instead.

I struggled to find another map app that pops up the same warning, but these apps below managed to locate me within 25m or so (I'm indoors right now) with the option disabled:

• TomTom GO Ride
• Maps.me
• Kurviger
• OS Maps

On the positive side, we know MRA will be looking at it at some point.

[RetiredWingMan]

@richtea999 if I turn off Google location, I constantly get the following error and I can't get rid of it.

[richtea999]

@Doug-Robinson
Exactly! That is the problem.

Press 'OK' and it will start working again (i.e. it enables the 'Google Location Accuracy' setting again)

Rather than lock you out, MRA should 'gracefully' continue as best it can without the additional Google setting, especially since GPS is enabled and you'll still get a high accuracy location fix in most circumstances.

(Enabling Google Location Accuracy will give better results indoors, and where satellite visibilty is poor, such as high-rise city streets with very tall buildings all around you, but at a cost of data collection by Google, which some folks would prefer not to allow.)

[Con Hennekens]

@richtea999 said in Google's location:

MRA is the the odd one out

Yes I know it is, but that does not mean the error lies within the MRA app. I am sure no one at MRA thought: "let's force the location improvements". It is a bit like the "homograph" discussion elsewhere in this forum. That is a proven bug in IOS. The fact that other apps found a workaround for it does not change that. One way or another, I hope the MRA Dev team will find a workaround for this one too. Because I too are certainly NOT in favor of the location accuracy nonsense.

I am beginning to think these kind of things are flutter related. The platform independent way of developing leaves a lot of tasks to the OS. That's easy in terms of coding, but gives more chance of undesired side effects, and less handles for workarounds or deploying alternative methods.

@richtea999 said in Google's location:

Enabling Google Location Accuracy will give better results indoors, and where satellite visibilty is poor, such as high-rise city streets with very tall buildings all around you, but at a cost of data collection by Google

I seriously doubt accuracy benefits at all. You add a less accurate method to enlarge accuracy? Yes indoors maybe...

And for the data collection by Google: better not use smartphones at all. And no, Apple does not help. They will just skip the toggle for such a function. And both will collect data, even with the slider disabled...

[flamingm0e]

@Con-Hennekens said in Google's location:

but that does not mean the error lies within the MRA app

MRA is telling the OS to use that API and not the Android Location API.

It's MRA. Stop trying to defend it.

@Con-Hennekens said in Google's location:

I am sure no one at MRA thought: "let's force the location improvements".

Nobody here thinks that. It's a BUG, but it is indeed MRA.

Please. For the love of Pete, stop trying to defend MRA so hard. Some of us have spent time developing on Android. We're not morons.

[Con Hennekens]

@Matt-Flaming said in Google's location:

MRA is telling the OS to use that API and not the Android Location API.

I am no developer, so I am not afraid to admit others have more insight in this. But what I am telling is that for many people, including myself, the disabling of location accuracy DOES NOT pose that error message. So the problem is a little more complex than just calling one or the other API. I am not a moron either, thank you...

[flamingm0e]

I just tried this with 3 different devices. Android 9, 10, 13. All exhibit the same exact behavior. That's not a coincidence, and it's not that complex.

I guess that I should go back to just reading the forums and not interacting with the community, because it's obvious that the people that act like MRA can do no wrong don't really care about involvement with people that may have differing ideas than theirs. Enjoy your echo chamber.

[richtea999]

@Corjan-Meijerink said [12 days ago] in Google's location:

We’ll definitely have a look again

There's nothing else to be said.
Somebody please lock the thread.

[Corjan Meijerink]

@Matt-Flaming @Whinging-Biker I've worked on a solution for this issue which will be available in the next Beta & release (4.0.3).

More details about this update will be announced tomorrow

[flamingm0e]

@Corjan-Meijerink I appreciate the effort, but I'm not that interested in any of this any more. I don't think the harassing chat message I received after my previous comment, was warranted.

[Corjan Meijerink]

@Matt-Flaming to be brutally honest, your attitude at certain points in time (over a longer history than the one you and me have since the Next development) did not contribute to your general reputation.

The forum is public, with lots of different opinions and we all tend to help each other. Yet, some people annoy the community more than others. Shake it off dude.

I appreciate all feedback and do tend to pay attention to everything, but I can only work as fast as I do (which is pretty damn fast). So ignore others that annoy and don’t make these comments in my direction. I have no knowledge about private messages sent to you, keep me out of it.