-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No voice in 0.13 #922
Comments
Hi @chooble , were you using an |
Hi @devotaaabel! No I wasn't using |
@chooble Can you add a After adding this, can you verify that |
I am also not getting voice in 0.13, and, like @chooble, am constructing my own DirectionsRoute based on a response from our own OSRM route server. It worked fine earlier and still works well except for the voice. I've got nothing else to add at this point and have been drawn off to another urgent project for a few days -- I can spend some time troubleshooting with you early next week if it's still a mystery. |
@tonyc10 Do you mind trying the same suggestion #922 (comment)? Voice instructions are provided by the response from the directions API, so I think something may be going on with that. |
@danesfeder Hi! I added the MilestoneEventListener and getting this output (instruction is in dutch): I'm logging this:
And the output is:
|
I used @chooble's logging code and looks like my results are the same:
|
Hey @chooble @tony-cj can you both test your issues again with our newest release of the SDK |
I don't seem to get it working. I've set the .language and .voiceUnit in RouteOptions like you described in the release notes. Also the .voiceLanguage in de DirectionRoute builder. |
@danesfeder i think the error could be related to a missing error case during the download of the mapbox voice file: MapboxSpeechPlayer.java If the response is not successful ( |
No luck for me either. I put in 0.14.0, fixed the breaking API changes,
and ran it — still no voice. I also played around with the RouteOptions
like Tristan.
I construct my DirectionsRoute from the JSON of our OSRM server, with a
RouteOptions I build. All worked, including voice, prior to 0.13.0.
- Tony
…On Fri, Jun 1, 2018 at 4:28 AM, Tristan ***@***.***> wrote:
I don't seem to get it working. I've set the .language and .voiceUnit in
RouteOptions like you described in the release notes. Also the
.voiceLanguage in de DirectionRoute builder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#922 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADjrbeWxb2Ku48VbNUGK09oQX2cmg6z1ks5t4Qk0gaJpZM4T0ptS>
.
|
@skienzl I'll get that in the next release. |
@devotaaabel @danesfeder , do you have an ETA for the solution? Did you already found cause of the problem? |
@chooble we have still been unable to reproduce your error, but I did add an extra call to retry using native TTS if |
Hey @chooble 👋 Could you retest your issues again with our newest release of the SDK |
0.15.0 brings back the voice for my app! Hooray!!
To summarize my experience, 0.13.0, 0.14.0 = no voice; 0.15.0 = voice.
Thank you.
…On Mon, Jun 25, 2018 at 7:41 AM, Pablo Guardiola ***@***.***> wrote:
Hey @chooble <https://github.com/chooble> 👋 0.15.0 was released
including @devotaaabel <https://github.com/devotaaabel>'s above-mentioned
changes.
Could you retest your issues again with our newest release of the SDK
0.15.0
<https://github.com/mapbox/mapbox-navigation-android/releases/tag/v0.15.0>
?
cc @tonyc10 <https://github.com/tonyc10> @skienzl
<https://github.com/skienzl>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#922 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADjrbcMgjkL13N7x5f1VHMGs-_crRawpks5uANqVgaJpZM4T0ptS>
.
|
I do now get a crash when selecting the mute button (speaker icon) on the
turn by turn display:
java.lang.NullPointerException: Attempt to invoke virtual method 'void
com.mapbox.services.android.navigation.ui.v5.voice.MapboxSpeechPlayer.setMuted(boolean)'
on a null object reference
at
com.mapbox.services.android.navigation.ui.v5.voice.NavigationInstructionPlayer.setMuted(NavigationInstructionPlayer.java:50)
at
com.mapbox.services.android.navigation.ui.v5.NavigationViewModel.setMuted(NavigationViewModel.java:100)
at
com.mapbox.services.android.navigation.ui.v5.instruction.InstructionView$6.onClick(InstructionView.java:593)
at android.view.View.performClick(View.java:5637)
at android.view.View$PerformClick.run(View.java:22429)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6121)
at java.lang.reflect.Method.invoke(Native Method)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
When voice wasn't working, selecting that button had no effect.
…On Mon, Jun 25, 2018 at 10:21 AM, Tony Case ***@***.***> wrote:
0.15.0 brings back the voice for my app! Hooray!!
To summarize my experience, 0.13.0, 0.14.0 = no voice; 0.15.0 = voice.
Thank you.
On Mon, Jun 25, 2018 at 7:41 AM, Pablo Guardiola ***@***.***
> wrote:
> Hey @chooble <https://github.com/chooble> 👋 0.15.0 was released
> including @devotaaabel <https://github.com/devotaaabel>'s
> above-mentioned changes.
>
> Could you retest your issues again with our newest release of the SDK
> 0.15.0
> <https://github.com/mapbox/mapbox-navigation-android/releases/tag/v0.15.0>
> ?
>
> cc @tonyc10 <https://github.com/tonyc10> @skienzl
> <https://github.com/skienzl>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#922 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADjrbcMgjkL13N7x5f1VHMGs-_crRawpks5uANqVgaJpZM4T0ptS>
> .
>
|
@Guardiola31337 Great! It's working now! 👍 🥇 |
It's been a year since I thought about this (or looked at this app) but I can share some code. Looking over this, it was pretty thick stuff — the key was migrating the polylines to version 6. From our OSRM server, I got a response that fit into this Kotlin data class:
With Waypoint being:
I got one or two objects in the
Good luck! |
Thanks, but I’m curious, how did you build the var options (routeOptions) Osrm can now return polyline6. |
@tonyc10 |
Here is the code I had to build routeOptions:
fun routeOptions(
start: Point,
end: Point,
includeAlternatives: Boolean = false,
uuid: String = start.to(end).hashCode().toString() // just a
unique string here
): RouteOptions {
return RouteOptions.builder()
.baseUrl(BuildConfig.BASE_URL)
.accessToken(Mapbox.getAccessToken()!!)
.user("mapbox")
.profile("driving-traffic")
.alternatives(includeAlternatives)
.geometries(DirectionsCriteria.GEOMETRY_POLYLINE6)
.continueStraight(true)
.voiceInstructions(true)
.steps(true)
.roundaboutExits(true)
.overview(DirectionsCriteria.OVERVIEW_FULL)
.voiceUnits(DirectionsCriteria.IMPERIAL)
.language(Locale.US.getLanguage())
.bannerInstructions(true)
.coordinates(listOf(start, end))
.requestUuid(uuid)
.build()
}
the way you are doing it, it was filling the voiceInstructions and bannerInstruction ?
If you say so. Does the RouteOptions code above provide more insight?
…On Wed, Jul 31, 2019 at 4:07 PM JFDionne ***@***.***> wrote:
@tonyc10 <https://github.com/tonyc10>
And I'm wondering, the way you are doing it, it was filling the
voiceInstructions and bannerInstruction ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#922?email_source=notifications&email_token=AA4OW3L23UA25KS3ROB7OPDQCH5JPA5CNFSM4E6STNJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IR6FQ#issuecomment-517021462>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA4OW3JSDAP46TFJBSXN3BDQCH5JPANCNFSM4E6STNJA>
.
|
@tonyc10 I'll try your code, but what was the value of BuildConfig.BASE_URL? The url of your osrm server? or api.mapbox.com? |
The URL was to our own OSRM instance. I had voice working, that was always
required, although there was an issue I had to work around at some point --
maybe it wasn't working in an SDK version release.
…On Wed, Jul 31, 2019 at 5:20 PM JFDionne ***@***.***> wrote:
@tonyc10 <https://github.com/tonyc10>
Sorry, it was more a question :) with your code do the voiceInstructions
got filled?
I'll try your code, but what was the value of BuildConfig.BASE_URL? The
url of your osrm server? or api.mapbox.com?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#922?email_source=notifications&email_token=AA4OW3IZOMIO5WM53TVIZ3TQCIFZPA5CNFSM4E6STNJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IXOBQ#issuecomment-517043974>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA4OW3PUNXNTNUKFO6Z4IK3QCIFZPANCNFSM4E6STNJA>
.
|
@tonyc10 Thanks you for all those information :) |
Since 0.13 I am not getting any voice instructions.
I get my routes via an external server which gets the DirectionRoute from Mapbox. Then I process the json to create a DirectionRoute via the Builder. When using the builder I set the RouteOptions.language:
And the DirectionRoute.voiceLanguage
I start the navigation this way:
I also tried different combinations of .language, .voiceLanguage and .locale. Also not setting them, but with no result.
There are no logs or errors describing what is happening.
Android API: 27 (OnePlus 5) and 24 (Samsung J5)
Mapbox Navigation SDK version: 0.13
Expected behavior
I expected that the navigationView would give me voice instruction without the need to change anything in code when transferring from 0.12 to 0.13
Actual behavior
No voice instructions
The text was updated successfully, but these errors were encountered: