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)

We would like to install our app inside work profile , for this purpose we are using testDPC for creating the workprofile and will use the following command to install our app eg: adb -s emulator-5554 install --user 10 -r application.apk Its working for the android versions till 15 , but with android 16 getting the below error any way fix this issue..? > Exception occurred while executing 'install': java.lang.SecurityException: Shell does not have permission to access user 10 com.android.server.am.ActivityManagerService.handleIncomingUser:13871 android.app.ActivityManager.handleIncomingUser:5300 com.android.server.pm.PackageManagerShellCommand.translateUserId:3965 at com.android.server.am.UserController.handleIncomingUser(UserController.java:2895) at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:13871) at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:5300) at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:3965) at com.android.server.pm.PackageManagerShellCommand.doCreateSession(PackageManagerShellCommand.java:3976) at com.android.server.pm.PackageManagerShellCommand.doRunInstall(PackageManagerShellCommand.java:1626) at com.android.server.pm.PackageManagerShellCommand.runInstall(PackageManagerShellCommand.java:1562) at com.android.s

I often receive the following error message when attempting to perform Android security updates: > There was a network error while downloading the update. Please try again later or connect to a different network. In researching this error message, it is apparent that many other people have been reporting the same issue for years: - Update cannot be downloaded on specific networks : GooglePixel https://old.reddit.com/r/GooglePixel/comments/10whijh/update_cannot_be_downloaded_on_specific_networks/ - Not able to update to android 15. Shows error in network while downloading although connected to WiFi - Google Pixel Community https://support.google.com/pixelphone/thread/322921191/not-able-to-update-to-android-15-shows-error-in-network-while-downloading-although-connected-towifi - Pixel 7 System Update Fails : GooglePixel https://old.reddit.com/r/GooglePixel/comments/ycejcz/pixel_7_system_update_fails/ - There was a network error while downloading the update. Please try again later or connect to a diffe - Google Pixel Community https://support.google.com/pixelphone/thread/205161477/there-was-a-network-error-while-downloading-the-update-please-try-again-later-or-connect-to-a-diffe Over the years, people have offered "magical" solutions, such as toggling WiFi on and off, which likely has nothing to do with the real issue. Yet some do claim that such actions have temporarily fixed the issue (not myself, though). What's even more odd is that those reporters have not indicated they made any additional changes. In Google's latest Android version, Android 16, this issue is still present. Ironically, the issue seems to be most prevalent on Google's own Pixel devices. Does anyone know what is causing this bug and how to actually fix it? Update --- A couple of our community members asked some good questions... here are the answers: - The issue occurs regardless of whether WiFi or carrier data is used. - I've seen the issue occur on many Google Pixel devices, starting with the Pixel 4. Online reports indicate it was present going back to at least the Pixel 2. I've seen this issue on several Samsung devices as well, although online reports of this issue tend to mention the Pixel devices more often than Samsung devices. - Regarding proxies, VPNs, or blocked ports/servers, I need to investigate further. It definitely happens on a wide range of devices and on a wide range of networks, but perhaps there is a common element that I can discover.

After upgrading to Android 16 around 50% of apps fail to load past their splash screen. I've ensured all apps are up to date. Any other tips on how to troubleshoot this? **Edit**, these are some of the apps that don't open properly: - Kayo Sports , v 2.4.9. - Foxtel Go , v 6.6.1. - AFL , v 11.4.41550. - YesBet , v 5.9.0.

How do I turn off the spacecraft game in Android 16? It starts automatically when I put the phone on charge and gives me hundreds of notifications that can't be muted.