Related

Google voice assistant issue

SalvatoreAliperti
2 months ago

Hello

I updated my venu3 to latest firmware (13.19) just a few minutes ago and I was happy to read in changelog report "Improvements to Voice Assistant interactions with various Android phones"

  1. My happiness stopped just later to have a long press on central button of my V3 SmileJoy

XUCI3SZxaaU?si=dpFz5SOKclFdvqfP

I've not any ideas about to solve it.

In others post, anyone suggest to unistall Google app in Smartphone and don't update it to last version. I done it but without solutions.

Last idea is to perform a factory reset to V3 but I'm almost certain that it no works.

Any experiences about? Advices?  

Thank you

  • 0 7 days ago in reply to 9525489

    Unfortunately there is not a timeline available, I will post here as soon as there is. If you would like to pursue a return you would need to contact Garmin Support in your region

  • 0 7 days ago in reply to 3755242

    If you would like to pursue a return you would need to contact Garmin Support in your region

  • +1 2 days ago

    Update as of 6/03/2025

    Ladies and Gents - 

     We received confirmation that Android 16 will be rolling out over the next few days. All indications are that this issue will be resolved by the OS update. Please watch for the update and install as convenient.

  • 0 2 days ago in reply to Garmin-Tracy

    Android 16 si metterà negli smartwatch? 

  • 0 2 days ago in reply to Garmin-Tracy

    Wtf Unamused  voice assistant will be working only with Android 16? Are you kidding, right?

  • 0 2 days ago in reply to Garmin-Tracy

    Most android phones are 6 months to a year or more away from the upgrade to a new Android OS, if they are even eligible for it. It will be in beta for a bit. Then device manufacturers will need to customize it to their version of the OS, followed by beta testing. Then carriers will need to test it and customize it for their locked devices. Then get released on phone that come out in the second half of the year and then eventually move to the latest phones currently out and maybe will make it 1-3 phone generations after that in far decreasing priority.  All that and we have no idea if this will even resolve it. Many phones that are carrier locked are lucky to get timely android security updates. 

    This isn't what I, or likely anyone would consider a practical solution. It has already been months, and we should just wait and hope for another 6-18+ months for a fix?

  • 0 2 days ago in reply to Garmin-Tracy

    Android 16 is not the solution of the problem.

    We all bought a watch expecting that we can use it the next 4-5 years without any problems or buying a new phone.

    Your software team must be able to make updates for the watch and or the app, they are solving codec or bluetooth problems...

    How you are explaining the prices of the watches when your teams are not able to make some problem solving updats?

    There are some other manufacturers, i e Suunto, Polar usw

  • 0 2 days ago in reply to Garmin-Tracy

    So if I go out and buy the latest phone I might be able to use the function I paid for by the end of the month. With the phone I have just going into Beta testing for Android 16 I will have to wait until the end of the year to use a function on a Watch I paid a lot of money for. How is this acceptable? surely your experts should be addressing the issue to fix on the current android system rather than hope it works on the next version, And then how long will it work for? Worked fine on 15 then stopped, many updates later still not working. Great way to lose customers. Never again will I buy Garmin if this is the customer care they give.

  • 0 2 days ago in reply to 3755242

    Garmin and customer care/service are polar opposites. Pretty darn good products when they work but customer service  after purchase is severely lacking.

  • 0 1 day ago in reply to Garmin-Tracy

    Hi Garmin-Tracy,

    Really appreciate your presence on these forums. Glad you're listening. This issue is frustrating for all of us I'm sure!

    As BlackScarab mentioned below, we could be many, many months away from an Android 16 rollout by manufacturers (incl. Samsung, which is a very popular brand). Some phones will never get it. So with respect to the team, this is simply not a solution. 

    I'll likely be forced to return my new Venu3 if a more efficient fix isn't implemented (or at least some assurances) before my return window closes. I purchased this watch specifically for the voice functionality on offer. :( Garmin makes great products; we know y'all can work this out!

    In the meantime, a stop-gap measure might be helpful (ie. it would be good if users could at least get Bixby working for basic functionality, like setting alarms or etc. I did actually have that working before I tried to switch to Google Assistant, but can't get it back). Thank you!