This object is in archive! 
Brouter doesn't calculate route
Solved
Hi there.
In the last few months, I'm having problems calculating routes with Brouter.
I installed the latest Brouter version on Android, downloaded the areas I use to navigate, but when I press a place in the map and choose to navigate to that point, Locus shows a message on the top center of the screen with "Processing..." and nothing happens.
I have to switch to GraphHooper to be able to get the route.
Mind you that the sattelite icon is green, which means I have GPS fixed and available.
Any help?
Thanks, Zdeněk.
That worked!
Why did that happen? Brouter needed update or was it something else?
Thanks, Zdeněk.
That worked!
Why did that happen? Brouter needed update or was it something else?
I just want to inform that I found the problem with Brouter. If the app isn't running in the device, Locus is unable to use it to calculate the route. I have to open Brouter app and then make the route calculation. Is this a known problem or is just my device?
I just want to inform that I found the problem with Brouter. If the app isn't running in the device, Locus is unable to use it to calculate the route. I have to open Brouter app and then make the route calculation. Is this a known problem or is just my device?
The procedure is very straightforward. If Brouter app is terminated in the device, Locus cannot open it when calculating a route and shows the message "Processing..." on the top centre of the screen.
If I open the app outside Locus and then try to calculate a route, Locus works as expected.
The procedure is very straightforward. If Brouter app is terminated in the device, Locus cannot open it when calculating a route and shows the message "Processing..." on the top centre of the screen.
If I open the app outside Locus and then try to calculate a route, Locus works as expected.
I don't know what to say to help...
Brouter and Locus have all its permissions allowed (Brouter with storage and Locus with storage, location and microphone) but when I terminate Brouter app (with KillApps app or forcing it to stop in Android configurations) Locus is unable to initiate Brouter app and calculate route.
Maybe I'm doing something wrong, but this worked fine for years. It's only a problem since a few months ago.
I don't know what to say to help...
Brouter and Locus have all its permissions allowed (Brouter with storage and Locus with storage, location and microphone) but when I terminate Brouter app (with KillApps app or forcing it to stop in Android configurations) Locus is unable to initiate Brouter app and calculate route.
Maybe I'm doing something wrong, but this worked fine for years. It's only a problem since a few months ago.
Just to inform that this issue was marked as solved, but it's not.
I still have this problem.
Just to inform that this issue was marked as solved, but it's not.
I still have this problem.
which app version do you use. LM3 or LM4 (free, Silver, Gold ?
What phone do they have and android. I need to enable in my car start in android permissions.
which app version do you use. LM3 or LM4 (free, Silver, Gold ?
What phone do they have and android. I need to enable in my car start in android permissions.
I have LM4 Silver version.
Tha app seems to be correctly installed (I reinstalled it several times, with the same result) and it worked well for years until a recent Locus update.
It has the storage permission accepted in Android definitions, so I don't see anything strange in the system configuration.
I have LM4 Silver version.
Tha app seems to be correctly installed (I reinstalled it several times, with the same result) and it worked well for years until a recent Locus update.
It has the storage permission accepted in Android definitions, so I don't see anything strange in the system configuration.
Starting from A10 (or A11) Android has introduced that apps need the permission for the automatic start.
I don't know what kind of phone and Android you have.
For me it's under Apps/ Permissions / Auto Start
And BRouter also needs the exclusion of battery optimization. Otherwise it can't work in the background.
Starting from A10 (or A11) Android has introduced that apps need the permission for the automatic start.
I don't know what kind of phone and Android you have.
For me it's under Apps/ Permissions / Auto Start
And BRouter also needs the exclusion of battery optimization. Otherwise it can't work in the background.
I have A10 and a Ulefone Armor 9E.
I don't see the options you mention, but the only permission BRouter asks for is storage, which is granted.
The strange thing is BRouter worked fine till a while ago, and I don't know if something changed in the app or in Locus to trigger this behaviour. I'll have to dig more into this, but I'm surprised I'm the only one complaining about this...
I have A10 and a Ulefone Armor 9E.
I don't see the options you mention, but the only permission BRouter asks for is storage, which is granted.
The strange thing is BRouter worked fine till a while ago, and I don't know if something changed in the app or in Locus to trigger this behaviour. I'll have to dig more into this, but I'm surprised I'm the only one complaining about this...
Not every app asks for these permissions. I also found these only by chance and thus found my problems. Also see if Brouter has updated recently.
At Locus there are somewhere old versions, you could try with that.
You have to wait until someone from the Locus team answers. Is just vacation time.
Not every app asks for these permissions. I also found these only by chance and thus found my problems. Also see if Brouter has updated recently.
At Locus there are somewhere old versions, you could try with that.
You have to wait until someone from the Locus team answers. Is just vacation time.
Ok, I tried with OSMAnd and the problem is the same.
It seems Brouter app can not be killed and must work in the background at all times.
Thanks for your patience.
Ok, I tried with OSMAnd and the problem is the same.
It seems Brouter app can not be killed and must work in the background at all times.
Thanks for your patience.
Replies have been locked on this page!