[Regression]: on version 10.1.0 with android getCurrentPosition takes at least 30 seconds to load. I tried ^8.2.0 and it takes only 0.02s about flutter-geolocator

[sulaimanpgm]

I have the same problem.

[eb-so]

I'm also on 10.1.0
My device is Redmi 8 and it hangs forever
I noticed the issue only after I upgraded to flutter 3.16.5
I tried changing the settings from high to medium but still seeing the issue
Note: the issue doesn't appear on my emulator Pixel_3_API_30

[mvanbeusekom]

Hi @tomasbutkevicius, @eb-so,

Thank you for helping out and @eb-so for confirming that the safe_device plugging is the cause. For now I will close this issue, however I will keep an close eye on it and see if there is anything we can do to improve the situation.

In the meantime, if you have any additional information or feel this issue should not be closed, feel free to leave a comment with argumentation and I would be happy to reconsider and if necessary re-open the issue.

[GustavoFigueira]

Same here, I've tested on two devices:

1 - Moto G54: almost instantly
2 - Realme 8 Pro: takes about 4-5 seconds

[TimHoogstrate]

Dear @tomasbutkevicius,

For now I cannot reproduce this. However, I noticed that you added a required location accuracy "best". Could something be interfering with your location determination. Is it also happening if you play a bit with the location settings?

Kind regards,

[mvanbeusekom]

Hello @tomasbutkevicius, @GustavoFigueira , @eb-so,

This problem has been reported before (see #1243) and several developers confirmed the issue being related to the use of the "safe_device" plugin. Could you confirm if this is also the case for you?

[tomasbutkevicius]

@mvanbeusekom hello, I can't check right now but I do use safe_device plugin

[tomasbutkevicius]

changing the accuracy did nothing

[eb-so]

@mvanbeusekom Sorry for the late response but that's true the safe_device plugging was the issue, kind of weird behavior.

Thanks for the help 🙏

[tomasButkeviciusAdapt]

Thank you for your attention and work guys! But I am wondering why close the issue if it's not resolved? I would prefer to leave the issue and when you resolve it then you can close because now it would be like ignoring this, would it not? Also keeping this issue open could be a reminder of what needs to be fixed?

[eb-so]

@tomasbutkevicius Maybe it's safe_device package issue, I'm now using root_jailbreak_sniffer as a replacement with no problems

[mvanbeusekom]

@tomasButkeviciusAdapt, I have closed the issue because I strongly suspect the issue is not related to geolocator but as @eb-so also mentions with the safe_device plugin.