You are correct, the set up is incredibly confusing now, due largely to Android security restrictions.
I also now have two folders of profiles. As I understand it:
- in Locus mode Locus can access its own internal Brouter profiles plus the ones in /brouter/profiles2. It then communicates with Brouter via an api and Brouter then writes a copy of the selected profile into _its_ system data folder (Android/data...) under the name of remote.brf and uses this to calculate a route.
- in Brouter mode, Locus relies entirely on Brouter and the settings in Locus cannot be used and are greyed out. Brouter accesses its own system folder directly and uses either its default profile/mode mapping or the one you can set up yourself in the Brouter app. So, this uses the Android/data... folder. As far as I can see this way of doing things has little to commend it now and is largely historic.
Sent from my moto g(6) plus using Tapatalk
I also now have two folders of profiles. As I understand it:
- in Locus mode Locus can access its own internal Brouter profiles plus the ones in /brouter/profiles2. It then communicates with Brouter via an api and Brouter then writes a copy of the selected profile into _its_ system data folder (Android/data...) under the name of remote.brf and uses this to calculate a route.
- in Brouter mode, Locus relies entirely on Brouter and the settings in Locus cannot be used and are greyed out. Brouter accesses its own system folder directly and uses either its default profile/mode mapping or the one you can set up yourself in the Brouter app. So, this uses the Android/data... folder. As far as I can see this way of doing things has little to commend it now and is largely historic.
Sent from my moto g(6) plus using Tapatalk
The following users thanked this post: Menion