Has the Motorbike problem been fixed in 4.0.3???

[Thomas Scharrer]

@Con-Hennekens thnaks for the answer again.

I cant find any app power settings in my app or iPhone, maybe this doesnt exist on iPhone?

[Con Hennekens]

@Thomas-Scharrer, Ah, now I see you are on IOS. Does IOS offer no energy settings on apps whatsoever?

I will not just accept that it is not working (without screen on)

Well you have to admit that usually motorists want to be able to look at their nav. I think the app was never intended to be used the way you do. Especially knowing that it is ill advised to do so. But that does not rule out that a method will be implemented to leave the voice active with screen off.

I have to use google maps where this is working without any problem.

Well Google Maps does not navigate the routes you make in the MRA planner, does it? I guess that there are plenty other apps that will do better then Maps (for scenic multi-WP routes that is).

[Thomas Scharrer]

@Con-Hennekens

I just dont like having my phone mounted on my bike and many others also dont like that. I understand that you dont recommend navigation only with voice commands and I can add to this that I am using a Beeline device instead of mounted phone. I am simply importing my routs created in the MRA into the Beeline.

Yes, correct googlemaps cannot navigate the MRA created routs so basically you have to put a created route manually into google maps.

[Corjan Meijerink]

We will work on this in the future! Currently the app indeed does not continue the instructions when the screen is locked.

[Nick Carthew]

@Corjan-Meijerink said in Has the Motorbike problem been fixed in 4.0.3???:

We will work on this in the future! Currently the app indeed does not continue the instructions when the screen is locked.

Yes it does, I have just tested it. 100% all instructions and camera warnings.

[Nick Carthew]

@Thomas-Scharrer said in Has the Motorbike problem been fixed in 4.0.3???:

@Nick-Carthew thanks for the answer.

are you using an iPhone or Android because as @Con-Hennekens mentioned above, it seems to be possilbe to solve it on Android with the settings.

It would be really interesting to hear about your test. Just be be more clear, the navigation is not totally cancelled when the phone is inactive but there is no voice guidance coming anymore when the phone is inactive. I have tried this many times because I also thought there must be a way to make this work but as soon as I have the phone active again the voice commands work so if I would ride with holding the phone in my had (which is obviously not possible) then it would work.

I use an iPhone 11 and have just arrived back from my test. I can confirm that all voice instructions and warning bleeps can be heard with the screen off.

Do you have Background app refresh switched on for MyRoute-app?
You’ll find it in Settings > General > Background app refresh.

I had my phone mounted on my bike and started my journey. I then switched the screen off, instructions were coming through loud and clear to my Cardo Scala Packtalk Bold. I left the screen off for about 10 miles during which time I received lots of instructions and a camera warning bleep.
After about 10 miles I turned the screen back on which was a pain because I use facial recognition to un-lock my phone. Pulled over, gloves off and I punched in my PIN code to un-lock the screen. MRA was on screen at my location.

So I can confirm that the navigation app continues to run and announce turn by turn instructions in the background with the screen off.
Check your Background app refresh

[Nick Carthew]

@Corjan-Meijerink I unlocked this topic to give the OP chance to respond to my test result.

[Con Hennekens]

@Nick-Carthew, great test! I'll try to repeat it on Android.

[Thomas Scharrer]

@Nick-Carthew Hi and thanks a lot for testing however I just checked this and I have backrough app refresh on for the myroureapp.

maybe the problem or difference is that you had your phone mounted and not in your jacket pocket? maybe because it was mounted it was nor completely locked or so?
I am just guessing but it must be possible somehow to explain why it is working for some and not for others?

[Nick Carthew]

@Thomas-Scharrer said in Has the Motorbike problem been fixed in 4.0.3???:

maybe the problem or difference is that you had your phone mounted and not in your jacket pocket? maybe because it was mounted it was nor completely locked or so?

I wouldn’t have thought that would make any difference.

A good test would be:
Try starting a route with your screen on so that you can hear instructions and then turn your screen off.
That’s how I tested.

[Thomas Scharrer]

@Nick-Carthew

I have even tested this in the car a while ago to have better control of what is happening.

I put my helmet with my Sena on max volume on the passenger seat . I started a navigation, drove around and everything worked fine but as soon as I turned around the phone so it became inactive / locked the voice guidance stopped.

I then started another navigation with google maps and I could do whatever with my phone and it worked.

and for @Corjan-Meijerink it also didnt work when he tested

[Nick Carthew]

@Thomas-Scharrer said in Has the Motorbike problem been fixed in 4.0.3???:

but as soon as I turned around the phone so it became inactive / locked the voice guidance stopped.

What do you mean when you say you turn your phone around so it became inactive?

I use the off button on the side of the phone to turn the screen off.
I can assure you that it worked for me as described earlier.

[Thomas Scharrer]

@Nick-Carthew its also fine to use the off button but I had the phone lying on the passenger seat facing up and turned it around to face down so it becomes inactive

[Nick Carthew]

@Thomas-Scharrer Well I suggest that whatever setting you have that turns your screen off when you turn it over is causing the problem. When navigating my screen stays on when I turn it face down.

[Con Hennekens]

@Nick-Carthew said in Has the Motorbike problem been fixed in 4.0.3???:

A good test would be:
Try starting a route with your screen on so that you can hear instructions and then turn your screen off.
That’s how I tested.

I tested exactly that with my two android phones this morning, after allowing the app on them both to be running in the background.

The results on both: NO audio whatsoever. What strikes me on both phones is that the message that is halfway spoken when I push the lock button gets finished perfectly fine, so lock mode does not seem to interfere with that, and talking in lock mode is perfectly possible. BUT there are significant differences between them even so.

When I unlock my CAT I need to give it the unlock sequence first and select the app to display because it shows the homescreen first. But it is on the right spot immediately and resumes the voice guidance. It looks like the route has been followed correctly all along.

When I unlock my P30 Pro it skips the unlock procedure and focuses on the app immediately, the map scrolls from the old position (where it got locked) to the current position and resumes voice guidance. So it looks like it was not following the route all along.

Now it could be of course that the CAT scrolled to the current position in the time between pushing the lock button and finishing the unlocking procedure, but I can't be sure about that.

So, it feels to me that voice guidance is not triggered in lock mode (on Android), and I have to assume the app is not following the GPS at all in lock mode.

[Nick Carthew]

@Con-Hennekens said in Has the Motorbike problem been fixed in 4.0.3???:

@Nick-Carthew said in Has the Motorbike problem been fixed in 4.0.3???:

A good test would be:
Try starting a route with your screen on so that you can hear instructions and then turn your screen off.
That’s how I tested.

I tested exactly that with my two android phones this morning, after allowing the app on them both to be running in the background.

The results on both: NO audio whatsoever. What strikes me on both phones is that the message that is halfway spoken when I push the lock button gets finished perfectly fine, so lock mode does not seem to interfere with that, and talking in lock mode is perfectly possible. BUT there are significant differences between them even so.

Interesting, so we have two Android phones that do not play audio, one iPhone that doesn't and one iPhone that does!

When I unlock my CAT I need to give it the unlock sequence first and select the app to display because it shows the homescreen first. But it is on the right spot immediately and resumes the voice guidance. It looks like the route has been followed correctly all along.

When I unlock my P30 Pro it skips the unlock procedure and focuses on the app immediately, the map scrolls from the old position (where it got locked) to the current position and resumes voice guidance. So it looks like it was not following the route all along.

Are the location permissions the same for both phones?

[Con Hennekens]

@Nick-Carthew, yes they were identical and set to "always allow". I think maybe the location services themselves fall into sleep mode when locking the screen, but I cannot find any setting for that.

EDIT:
I did find this text on the internet however:

Concerning our use case, ACCES_BACKGROUND_LOCATION permission should be in the manifest, but I cannot imagine that being not the case.

The last yellow sentence would indicate that our use case is not possible at all, a few times an hour is clearly not enough. So I assume there is more to it than can be read here.

source: https://developer.android.com/training/location/background

[Rob Verhoeff]

@Nick-Carthew said in Has the Motorbike problem been fixed in 4.0.3???:

Yes it does, I have just tested it. 100% all instructions and camera warnings.

I can confirm this. This morning, while driving and navigating, I opened a different app on my iPhone 13 for a moment ( ). To my big surprise, the voice instructions continued to provide route guidance. An undisclosed feature?

[Con Hennekens]

@Rob-Verhoeff, well I don't think running out of focus is identical to running with locked screen. I have not tested that. I will (for Android) when I get the chance.

[richtea999]

@Con-Hennekens said in Has the Motorbike problem been fixed in 4.0.3???:

Concerning our use case, ACCES_BACKGROUND_LOCATION permission should be in the manifest, but I cannot imagine that being not the case.

The app definitely asks for ACCESS_BACKGROUND_LOCATION, so in general it should work OK in the background on Android if the user or OS hasn't restricted permissions (accidentally or otherwise).

[Note that the OS is getting more invasive nowadays (Android 11 onwards?), and it can disable permissions - but only if the app hasn't been used recently, for many days for example. But that's not the case here.]