Share your experience!
Issue:
-Car headunit Kenwood DDX9016DABS
-Paired to Sony XZ
-Phone is locked via swipe, pattern or finger print security option. All security gives same result.
-I press button for voice control on headunit which initiates Google Voice on Sony XZ via Bluetooth connection. From the headunit I hear beep tone for ready.
-I say "Dial 1196" or "Dial Frank" etc
-I hear Google Voice response on car speakers "Dialling 1196 on speakerphone"
-Sony XZ connects call to Sony XZ loud speaker.
This should have been connected via active bluetooth connection not speakerphone.
My previous Sony Z2 behaved correctly under this scenario.
SIde notes.
-If I use Kenwood onscreen Kenwood phone dialpad or onscreen Kenwood phone contacts my outbound call will automatically connect via Blueooth audio on Kenwood. Issue only affects Google Voice dialling.
-Once call connects I can use Kenwood onscreen button to switch to bluetooth audio.
-If swipe unlock is in use, first call from Google Voice will "wake" phone and leave phone in unlocked state allowing for second/third call to succeed.
If phone is in unlocked state Google Voice dialling works as intended with call connected via Bluetooth not Speakerphone.
How to fix?
Hi @brett1,
I'm sorry to hear about this, I understand that it must be quite annoying.
Your post was very informative, I appreciate that! Is there any chance you could capture this in a bug report as well? I could then forward it internally for investigation.
To do this:
1. Go to Settings > About phone > Build number, tap 7 times on the build number.
2. Go back and select Developer options then set Logger buffer size and change it to "4 MB"
4. Restart your phone, then replicate the issue
5. Go back to Settings > Developer options, select "Take bug report" followed by "Interactive bug report".
When the report is ready you will receive a notification. Tap the notification to share it. I suggest you upload it to Google Drive and then choose to share a public link to the upload and include the link in the PM.
6.12.25.21.arm64 (base in 41.2.A.2.223 /system)
6.12.25.21.arm64 (user install)
6.13.19.21.arm64
6.13.23.21.arm64
6.14.17.21.arm64
6.15.21.21.arm64
6.15.23.21.arm64
6.15.24.21.arm64
6.16.25.21.arm64 not work
6.16.33.21.arm64 not work
7.0.12.21.arm64 not work
For completeness
problem continues in
7.1.29.21.arm64
7.2.19.21.arm64
this would be much appreciated if shared on Google Products forum for android.,
@nolramlb wrote:this would be much appreciated if shared on Google Products forum for android.,
https://productforums.google.com/forum/#!home
I already have a simulcast there.
https://support.google.com/websearch/forum/AAAAgtjJeM4br_ToLRd18M/?hl=en
Any response from Sony about the problem that effects their device I have bought?
Does Sony acknowledge the problem and have any time frame to fix the issue?