Join now - be part of our community!

Google voice dialling via bluetooth uses speakerphone for call if phone is locked

brett1
Visitor

Google voice dialling via bluetooth uses speakerphone for call if phone is locked

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?

7 REPLIES 7
Christofer
Champion

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.

brett1
Visitor

I have done some Google App version testing and these are my results.
Issue starts in 6.16.25.21.arm64 and then continues to current version.
 
Work:

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

brett1
Visitor

For completeness

problem continues in

7.1.29.21.arm64

7.2.19.21.arm64

brett1
Visitor

I have considered this for a while now and now I believe the "security" for Android is all over the place.
 
1)You should not be able to call or message someone while a phone is locked.
Having a paired Bluetooth device is a form of user identification but really is a fairly weak identifier.
I could steal a paired Bluetooth device with the handset then make calls to anyone I like without authenticating who I am.
 
 
It appears Android 7.1.1 prevents use of Google Voice from a locked phone on the phone itself but allows some access if a paired Bluetooth device initiates the Google voice.
 
 
Apple by default allows Siri from handset while the phone is locked. It then allows from the phone calling and messaging while locked.
Apple allows the user to opt out / disable Siri from lock screen, but this would prevent Siri use in say a car while it is impossible / illegal for the user to unlock the device.
To me this appears Apple has a brand new "bypass the lock screen" problem introduced by default Siri settings.
 
2)Google App has a weird "security" measure that prevents a call connecting via Bluetooth but allows via speaker phone if phone is locked.
This Bluetooth restriction makes no sense.
Google App allows the call to connect, a Bluetooth device could have initiated this call via other methods to overcome this "security" and the Bluetooth device can switch the audio to Bluetooth once the call is connected anyway.
 
 
3)A paired untrusted Bluetooth device should not be able to initiate a phone call from its contacts, dialpad or other methods..
Current Android 7.1.1 entirely / incorrectly / insecurely allows these calls.
 
4)Android has "Smart Lock" where I can add my Kenwood DDX9016DABS as a trusted device which allows my phone to be automatically unlocked if connected.
This is the answer to the above security problems. Allow a user to specify paired devices to explicitly trust regardless of lock state.
 
This does "work" while my headunit is connected I no longer need to enter pattern/finger/voice or face etc to unlock, instead only an insecure swipe is required to unlock.
 
However this does not work with Google Voice dialing.
Google Voice considers the phone still locked until after the insecure swipe. This is the same if insecure swipe lock method was the lock type for the phone.
 
 
 
Conclusion:
-Android 7.1.1 has a security flaw that it allows unauthorized phone calls and use of Google Voice while a phone is locked if initiated by a paired Bluetooth device.
-Android 7.1.1 Smart Lock use should be required for a paired Bluetooth device to use the phone while locked.
 
 
-Google App since 6.16.25.21.arm64 has a bug where it connects phone calls to speaker phone if phone is locked. This bug may have been introduced while attempting to prevent unauthorized phone calls while locked.
-Google App / Android OS while phone is locked should only allow access to "Ok Google" unlock authentication.
-Google App / Android OS if initiated by a paired and trusted Bluetooth device should allow all functions.
profile.country.PH.title
MarlonUk1
Expert

this would be much appreciated if shared on Google Products forum for android.,

https://productforums.google.com/forum/#!home

brett1
Visitor


@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

brett1
Visitor

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?