If I correctly understand Google's overly-complex privacy UI, people can disable the storing of their interactions with the "traditional" Google Assistant. Google will reportedly be phasing out Google Assistant during 2025 and is replacing it with Google Gemini Assistant. According to this Google support page , it appears that there is no way to prevent Google from storing (and reading) everything you say to their "improved" assistant: > **Even when Gemini Apps Activity is off**, your conversations will be saved with your account for up to 72 hours to allow Google to provide the service and process any feedback. This activity won’t appear in your Gemini Apps Activity. Google says all your conversations with their Gemini Assistant will be saved "with your account", but I'm not seeing them disclose ***where exactly*** all your conversations will be saved. Nor does Google mention any way to manually delete sensitive conversations or accidental recordings that Google makes when it mistakenly thinks people are talking to their AI bot. Am I interpreting Google's words and actions correctly? **Is Google's new Gemini Assistant much less private than the product it is replacing, given that Gemini Assistant *always* saves every conversation you have with it for up to 72 hours?**

In Android 16, how does one get Google Assistant to recognize and call locally stored (non-synced) contacts? When trying to use Google Assistant to make calls by saying *"Hey Google... Call \"*, it always responds with *"Sorry who do you want to call?"*, and then pops up a pane that states *"Pick a contact"* that, when tapped, just opens the Contacts app. The pane also shows *"Call \"*, where *\* is the correctly spelled contact name, indicating that the problem is not a voice recognition issue. What's been tried: - Fully updated everything (apps, Google Play Services, Android). - Reluctantly enabled many permissions for the Google app, including: Call logs, Contacts, Microphone, Notifications, and Phone. - Within **Settings > Apps > Assistant > General**, enabled: Google Assistant, and set the Preferred input to Voice. - Within **Settings > Apps > Assistant > Personal Results**, enabled: Personal Results, Lock screen personal results, and Personal suggestions on lock screen before you ask. Please note that I also tried making calls using Google's AI Gemini Assistant, but it always says that it is still being developed and cannot currently make phone calls. This question is related to, but different from, this old question: [How do I navigate to a contacts address using my voice?]( https://android.stackexchange.com/questions/92859/how-do-i-navigate-to-a-contacts-address-using-my-voice)

I don't use Google Assistant, so I disabled it, by (1) opening the Google app, then (2) going to settings from the profile icon, then (3) choosing "Google Assistant" settings, then (4) scrolling a long way down to "General" settings, then (5) toggling off the top toggle that simply says "Google Assistant". However, sometimes the device thinks I long-pressed the home button (e.g. if I swipe up too slowly) and pops up a Google Assistant nag screen asking me to re-enable it. How do I stop the Home button from doing this? There don't seem to be any related settings in the Google app settings. I've found dozens and dozens of articles explaining how to disable Google Assistant - which I've already done - but not how to stop this home button behaviour. Device is a Samsung S22 Ultra running Android 14 and OneUI 6.0 if that's relevant.

I'm trying to set up my motorcycle Bluetooth headset (Fodsports BT-S2) to let me use Google Assistant. It has the following Bluetooth profiles: - A2DP-SNK - AVRCP - HSP - HFP I've managed to find an old APK of 'Smart Bluetooth Headset' which has allowed me to map the normal 'redial last number' button to the more useful 'Google Assistant'. That seems to be working flawlessly, opening the assistant and making the normal beep awaiting voice input. The problem I have is that it doesn't pick up the audio from the microphone on the headset, only from the phone itself. I've tried various combinations of the settings within the Google Assistant, as well as various mono routing apps to try and get it to work. One of these mono routing apps was successful at one point. However, my setup was no longer using A2DP, and so I was forced to endure poor sound quality. Is there any way I could either: 1. Make Google Assistant correctly use the microphone on my headset? 2. Force the phone to use only the microphone part of my headset, instead of the phone's built-in microphone, whilst retaining the A2DP mode for audio?

I use a Google Pixel and yesterday, Google Now asked if I'm interested in travel time updates to a shopping mall I recently visited and I happened to tap on 'yes'. Now, it shows me the ETA to that place all the time. I wish to disable ETA for this place now. I'm pretty sure this feature was available as a yes/no question in Google Now > Customize > Everything else. But at the moment, I do not see it. Has it moved elsewhere? Anyone having insight on this, please help.

When trying to send a message to all in Google Home app I get this message saying that no speakers are connected: > “Entschuldige, anscheinend sind derzeit keine Lautsprecher mit deinem Konto verbunden. Deshalb kann ich keine Nachrichten übertragen.” #### English translation of message provided by Apple translate. > “Sorry, there seems to be no speakers connected to your account at this time. That's why I can't transfer messages.” However my speakers (Samsung HW-S711GD Ultra Slim Soundbar, 2 Chromecast Audio, 1 Chromecast with Google TV HD) are connected and streaming to them with Google Assistant works (for example using: Ok Google, play radio XY on chromecast). I am assuming that by sending a message to all the Google Assistant will play this message on these speakers. Is this assumptions correct? What could make the assistant think my speakers are not connected?

I'm on Samsung Galaxy S24 Ultra. If I have a recording active, then I find that Bixby and Google Assistant refuse to enable listening in the background to wake up, by calling them up using voice.

Google Assistant can't start when another app is using the microphone

I can start them manually, so the problem is not exclusive access to the microphone. I've tried like five different recording apps and I just get the same message, when I try to activate it in settings. I'm not really sure what the problem is here.

When asking Google Assistant (on a Samsung Galaxy A54) to call a specified person, if it can't find the contact, it resorts to looking for and automatically dialling a phone number from the internet. This can be wildly incorrect - it has been known to start expensive international calls. Is there any way to force Google Assistant to restrict its search to the user's contacts?

Is there a way to stop the push notifications coming from Google Assistant telling me it is running an automation? I don't want a notification telling me "Running Living Room Lights" because I can see they are on.

This morning my smartphone (an A55, Android 14 (6.1.43-Android14-1)) is spamming notifications inviting me to try the Gemini AI and/or to use Google Assistant. - My Google Assistant is disabled in my account - Google and Google Play aren't allowed to send normal notifications - Google isn't allowed to send notification when its screen is locked I've rebooted my phone. But I'm receiving __more than one hundred notifications per hour__ interrupting my work as a popup, or doing a bip, while appearing on my locked screen. Like: - "_Google Assistant is ready to help you, Activate_", - "_Try: Say 'what the weather?' to Gemini_" - "_Say: 'How to set an alarm to 7am?' to Gemini_" Endlessly, on the locked screen. How to stop these notifications coming?

I would like to reverse a behaviour on Android 14 that was introduced with the September update. - Previously (this is what i would like to see): Long-press of the home button brings up Google Assistant (eg. for Calling, setting alarms, etc.) - Behaviour since the update: Long-press of the home button brings up some google overlay feature to "circle to search". Bringing up the assistant now moved to some obscure swipe gesture from the corner in. I have looked in the settings on how to define behaviour of the home button but not found anything. Ideally there would be sth like a mapping table. On here, the closest thing I found to this usecase is a ticket that deals with switching off both functionalities (assistant and the circling feature: https://android.stackexchange.com/questions/255899/how-to-stop-disabled-google-assistant-popping-up-on-home-button-long-presses Any nifty way where I can directly define the behaviour of the homebutton and set it to the assistant? Alternatively any other way, eg a launcher? - Android version: 14, September Update - Phone: Samsung A55 5G Thanks all!

I have a Pixel 7. For months now I've been using Keep for notes I enter by voice through Google Assistant. It now longer works correctly. Please help. Thanks in advance. ### Here's what I used to do Press the Assistant button, say "take a note" Assistant says, "alright, what would you like it to say" I say, "get a new phone" or whatever Assistant says, "alright, I've saved your note". And the note shows up in Keep, either through my phone or through the web. Life was grand. ### Here's what happens now Press the Assistant button, say "take a note" Assistant says, "alright, what would you like it to say" (or sometimes "What do you want it to say?") I say, "get a new phone" or whatever _Assistant says "Alright, which app do you want to use?"_ _OMG_ I have to say "Keep". ### What I want it to do NOT FREAKING ASK ME WHAT APP TO USE EVERY FREAKING TIME! #### What I've done to try to fix it. * Reboot - didn't help * Open Assistant Settings, verify Google Keep is checked - yes Keep is selected. * Open Assistant Settings, disable notes and lists, reenable - didn't help * Open Assistant Settings, disable notes and lists, reboot, reenable - didn't help * Install some other Notes and Lists provider - tried to install another list app. Didn't make a difference * Tried Gemini - OMG, near as I can tell, Gemini doesn't even know what a note is. Switched back to Assistant. Still didn't fix the issue. * Remove Keep, reinstall - same problem ### Possibly related Immediately prior to this behavior I installed an additional Gmail account in the Gmail app. I had three accounts installed, taking a note by voice worked fine. Installed a fourth account, and taking a voice by note started asking which app. Correlation does not imply causality, so I don't know that this was the cause. But for what it's worth, I uninstalled the fourth account, and it didn't fix the issue. ## Addendum It works correctly in the car, through Android Auto.

I am using a Motorola phone which has a dedicated Google Assistant button, but I don't use the assistant much. Is it possible to customize the button and use it for some other activity?

I activated my Pixel 7 on September 21. Voice recognition worked for two days, now hasn't worked since September 22. Phone calls work, people can hear me. The Camera successfully captures sound when recording video. However, voice recognition no longer works for apps where it is the primary purpose of the app. - I open **Google Assistant**, the screen indicates it is listening for my input, but nothing changes or comes on screen when I speak to it - When using GBoard, I click the mic icon to begin **speech to text**. The phone dings, the mic flashes indicating it is ready for me to speak, but does not transcribe any text as I am speaking - I hit record in **Recorder**, and it doesn't capture any audio when speaking to it - **Now Playing** doesn't work, no songs have been captured since 9/22 despite being around plenty of music Here's everything I've tried: - Install all latest system updates - Ensure all Google Assistant and voice permissions are enabled - Restart phone in Safe Mode and out of Safe Mode - Factory reset phone and log in with a different Google account The phone has never been dropped or seen any liquids. Everything else functions as expected. Does anyone have advice on how to correct this? (I would assume it's not a hardware issue, if phone calls and video audio capture work with no issue)

The following is my build.prop file. I just can't find the device model option so I can modify it. I'm trying to change my device model to Pixel XL so I can run Google Assistant properly. # begin build properties # autogenerated by buildinfo.sh ro.build.id=NMF26V ro.build.display.id=lineage_titan-userdebug 7.1.1 NMF26V 399d12a5d9 ro.build.version.incremental=399d12a5d9 ro.build.version.sdk=25 ro.build.version.preview_sdk=0 ro.build.version.codename=REL ro.build.version.all_codenames=REL ro.build.version.release=7.1.1 ro.build.version.security_patch=2017-01-05 ro.build.version.base_os= ro.build.date=Tue Jan 31 23:31:20 PST 2017 ro.build.date.utc=1485934280 ro.build.type=userdebug ro.build.user=jenkins ro.build.host=phenom.zifnab.net ro.build.tags=release-keys ro.build.flavor=lineage_titan-userdebug ro.product.brand=motorola ro.product.name=lineage_titan ro.product.board=MSM8226 # ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete, # use ro.product.cpu.abilist instead. ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.cpu.abilist=armeabi-v7a,armeabi ro.product.cpu.abilist32=armeabi-v7a,armeabi ro.product.cpu.abilist64= ro.product.manufacturer=motorola ro.product.locale=en-US ro.wifi.channels= ro.board.platform=msm8226 ro.build.characteristics=default ro.cm.device=Pixel XL # end build Update: I have further changed the manufacturer and brand to Google and the product to Pixel XL, but it still had no effect.

When I say "Hey google", I no longer hear a chime (since some recent-ish update). Lots of places online suggest to turn on the Switch Access accessibility feature, which would supposedly fix the bug (supposing it's a bug). But my Moto G62 5G doesn't have the "Switch Access" feature. Then I had the idea to use a macro app such as MacroDroid to intercept the "Hey Google" and react with a chime, but I didn't find that sort of trigger - neither in MacroDroid nor in Tasker. Any ideas? :)

I have a Pixel 7. I have typically been able to just go to the search bar on the bottom screen of my phone and say set an alarm and it always set an alarm. Now it's sending me to a website. Is there any way to take it back to just setting the alarm?

When the phone is locked & screen off, it will never hear my voice. How do I get OK google to work when the phone is off? The option seems removed for non Google Pixel/Nexus phones. I want to convert my old android phone into a Google Home (so I can say "Ok Google, turn off the lights" in my bedroom). I have an old Samsung Note 2. I used Odin to put TWRP on it so I can run LineageOS w/ Gapps, and now I have Google Assistant running on it. However, when the phone is off, it will never hear my voice. I can turn on and off the smart lightbulb in my room with my voice now. But there is no "always listening" "wake word" for "Ok Google Everywhere" anymore. Pretty sure Google removed this feature so you have to buy a Google Home device. I want to be able to use Ok Google anywhere, even when charging my phone.

Is there a command to make it refresh the web page currently shown in the browser on my phone? I tried multiple variations of "Hey Google ... Refresh the web page" but it instead shows me search results or opens Wikipedia. Argh. Want this to refresh it when I have dirty hands, so no touching, must be just voice.

I wanted to know if there was a command for Google Assistant to connect a specific Bluetooth device. It would be very convenient to use in the car so you don't waste time fiddling with your cell phone.