Android Auto - issues and workarounds - Huawei P10 Plus Questions & Answers

Installed Blackball's fRomFuture ROM, working well and it's fast but the AA bugs are still there.
Bugs are:
- Phone calls go to the handset instead of showing on the HU. This prevents the HU from being able to control calls and I have to answer and end them with the phone itself. The workaround is to either stop the Dialer process before plugging into the HU, or install Google Phone 7.0.140861421-nonnexus (noarch) (nodpi) (Android 6.0+) and set it as default dialer. Only bug then is the clock/timer on calls shows system time or something like 422031:23:59. No big deal there.
- Waze works one time, but as soon as the phone is rebooted it will halt the maps process on the HU. App still works fine when unplugged. Once this happens you have to either; clear cache and data from AA, enable developer mode in AA and start Maps from the "Back to Sync" icon (developer mode adds options here - Ford Sync), or uninstall Waze. I have not found another reliable workaround and it seems like this is a very common Huawei issue, not just P10 Plus.
Wondering if anyone else has found workarounds for these?

Related

Phone won't mute anymore!

i all
I have a LG G watch R, i have had this around 10 months, its paired with my Nexus 5.
Over the past year there has been a few occasions where suddenly the "mute phone alerts and calls" option has suddenly stopped working! *Half way through the day all of a sudden id still get the message on my watch but my phone would make a noise too!
Usually i fixed this by uni stalling android wear, resetting the watch back to factory setting and re pairing them..this usually solved the issue until next time....however!
This time it happened again and no matter what i do it wont work! i have the option to mute phone call and alerts but the phone still makes a noise and is not muted! when i toggle the volume bar it used to say before "muted by android wear" but now it does not.
My phone was updated to android 6.0 last week but for the past week its been fine so i doubt it related to that as like i said its done this before on lollipop.
Few more things to note that may be related, if i swipe down in my notifications box it used to say "android wear connected" but thats no longer there, and if i go into the watch and go into settings and bluetooth devices it does not say anything it just says scanning for nearby devices, and i notced once it said nexus 5 disconcerted??
I must stress that i am connected to my phone as all my notifications come through on my watch fine.
Anyone had this or know a fix?
Thanks
Chris*
Did you find a solution?
Same problem here. I have moto x play (no developer edition) unlocked bootloader/rooted/lollipop 5.1 and LG G watch R.
In my case it seems related to Moto Display (Motorola'app similar to ambient display). If I disable it, mute comes back.
I tried to uninstall android wear app, and then installing 1.3 version. No fix.
On reddit I read that it should be the last update of Google play service instead: user restored his phone fixing the problem. I tried to uninstall play service (no factory reset)...no fix
EDIT: Ok I have just found a middle-solution. I downloaded a module for Xposed (True silent Mode), after activation you will not able to receive any vibrations or sounds on your phone, but you'll receive a vibration on your watch instead. It's similar to android wear function, the difference is if you disconnect your watch you have to disable the silent mode on your phone manually. Hoping Google (or Motorola in my case) fixes it soon in the meantime...
Looks like we are not alone: https://productforums.google.com/forum/#!topicsearchin/android-wear/mute
https://productforums.google.com/fo...context-place=topicsearchin/android-wear/mute
I see other reports and see the issue myself where android wear often says that the watch isn't connected anymore while the watch says it is. And voice commands etc. on the watch still works (I guess they go directly through GMS not involving the android wear app itself).
Maybe there is a bug between android wear and the detection of the connected watch that keeps thinking android wear that no watch is connected and then not muting the notifications on the phone.
Do you have the cloud sync enabled? It's in "privacy & personal data". I have.
Hi still have the same issue, and yes my watch thinks it's not connected also
I have tried both cloud synced and un synced
Try putting your watch on charge, then taking it off
It worked for me, you will notice when on charge the ph is connected but notifications are not muted
I think the ph must think the watch is charging...
The latest wear app version fixed it for me.
http://www.apkmirror.com/apk/google...-wear-1-4-0-2470307-gms-android-apk-download/
Hasn't for me

From Alcatel Idol 3 (6.0.1) to Axon 7 (7.1.1) - Notification problems

Hi Folks,
I try to keep my remarks / questions as brief/straight as possible.
Some days ago a huge German electronic-chain called Media Markt offered the Axon 7 for only 229€, for only a couple of hours. I could not resist although I was very satisfied with my Alcatel Idol 3 (4.7) with Android MM.
Now I installed the exact same Apps that I have been using on my Alcatel on the Axon 7 (Android 7.1.1, B04). I do not have the problems that some are mentioning on various fora like connectivity issues (Wi-Fi, Bluetooth, cell). My settings are Wi-Fi (always on), Cell on (but not data on so far, not in the need to do it), GPS sometimes on, Bluetooth sometimes on, Display very low, no automatic.
I have some weird notification issues with various apps installed by myself and strange behaviour with system apps.
Wherever it was possible, I've chosen the same settings (Energy, Apps) as with my Alcatel on Android 6.0.1.
But, I rarely get notifications (for example AquaMail, WhatsApp, eBay, etc.) or, I hear the notification sound (when my phone was on stand-by) but the symbols are not shown in the status bar, notifications bar?!?!?
Another strange behaviour is that of my podcast app, called Podcast Addict:
I listen to a downloaded audio podcast, pause the playback, for example to get a coffee in the meantime, go back to my phone, unlock the screensaver and the pause symbol that was shown in the notification, status bar on the device before I left the phone, is not there any more!?!?! I have to open the app again to continue listening to the audio file. The exact same applies for the stock music player.
Or, for example I receive a notification for an incoming WhatsApp message, shown on the notification bar, I do not open WhatsApp, the notification symbol should/is still visible, but after the screensaver has been activated (set it to 1 minute) and I have to reactivate the phone (be it by fingerprint or by pattern), the symbol is no longer there.
Another strange thing. The phone was in stand-by, I heard a notification sound, activated the phone, there was no notification symbol on the bar. I knew what App it was, so I opened it and yes, there has been something going on (the App is called Quizduell).
All these bugs (?), problems have never occurred running the Alcatel smartphone.
This is pretty annoying.
I already switched off the phone, wiped data cache, without success.
Maybe some of you can help me out, give me advice on where to look for the problems to be solved.
Thanks a lot in advance.
Cheers Christian
Change the power policy of each app to off which u use mostly in power manager in settings.... It will most certainly help you out..
@germanyandroid Do what the other guy said, that's really impoetant. Also what system are you on? A2017G B02?
I don't know what the Axons are shipping with right now. Be sure to update at least manually to 1.2.0 B02 (that's Nougat), to rule out any system problems. Welcome to ZTE's horrible OTA system...
Hi! Thanks so far for your help. Most notifications are now coming in without changes to the Battery Optimization settings. There is something wrong with these settings, which I will report in a separate thread.
Again, thanks for your help thus far.

google assistant cannot send whatsapp when phone is locked

I have a Wear24 running on Android wear 2.20 and AndroidOS 7.1.1. my phone is Nokia 6.1, runnung on android one Pie 9. everything is updated.
Bluetooth connection is fine, google assistant is also working, big tick was showed after the message was sent but no recordof this message found on my phone's whatsapp. occasionally it crashes whatapp.
Seems GA fails to wake up whatsapp and execute the instruction.
please help, thank you very much
solved! I have to dig deeper into setting and disable battery optimisation for whatsapp

Wear OS watch will not maintain bluetooth connection to Mi9T

My Casio Pro Trek WSD-F20 always loses Bluetooth connection to my Mi9T after something like 30-90 minutes. The phone still thinks it is connected to the watch (eg, still successfully sends notifications) but the watch says it is not connected to the phone (eg, "disconnected symbol" is displayed, Play store on watch will not open as "you are not connected"). Restarting watch does not restore the connection. Turning watch or phone Bluetooth off and on does not restore the connection.
However, restarting the phone does reliably restore the connection.
Watch and phone (MIUI Global 10.3.12 Stable) are both current on all software. I have done a factory reset on the watch, and repaired after forgetting watch on phone, removing Wear OS app and reinstalling. Problem remains. I am confident, but not completely certain, that I have turned off battery optimisation for everything that matters, even installing MIUI Hidden Settings which appeared to let me do this for Bluetooth. My phone is not rooted, and I need it that way for a couple of apps I use regularly.
What can I do to keep watch and phone fully connected? Thanks in advance.
Had a similar issue with my Gear Fit2 Pro. MIUI kills the process maintaining the connection between the watch and the phone.
I ended up disabling the MIUI optimizations in the Developer settings and change the autostart settings for the "Samsung Galaxy Gear Fit Plugin" (that's the app maintaining the connection between my watch and the phone) to enable and enabled the option to let the app run in the background without any restrictions.
Here is a good information about this stupid MIUI background process killing and how to prevent it: https://www.quora.com/How-do-I-keep-an-app-running-in-the-background-in-MIUI
Good luck
I had that problem when I was running Global ROM. When I switched to Xiaomi.eu, the problem seemed to have gone away.
grantem2000 said:
My Casio Pro Trek WSD-F20 always loses Bluetooth connection to my Mi9T after something like 30-90 minutes. The phone still thinks it is connected to the watch (eg, still successfully sends notifications) but the watch says it is not connected to the phone (eg, "disconnected symbol" is displayed, Play store on watch will not open as "you are not connected"). Restarting watch does not restore the connection. Turning watch or phone Bluetooth off and on does not restore the connection.
However, restarting the phone does reliably restore the connection.
Watch and phone (MIUI Global 10.3.12 Stable) are both current on all software. I have done a factory reset on the watch, and repaired after forgetting watch on phone, removing Wear OS app and reinstalling. Problem remains. I am confident, but not completely certain, that I have turned off battery optimisation for everything that matters, even installing MIUI Hidden Settings which appeared to let me do this for Bluetooth. My phone is not rooted, and I need it that way for a couple of apps I use regularly.
What can I do to keep watch and phone fully connected? Thanks in advance.
Click to expand...
Click to collapse
+1 to this, facing the same exact issue and fixing it temporarily using the exact method i.e. restarting the phone.
PS: I am using Huawei Watch (Classic/Original)
Same here with my Fenix 3HR.
I actually returned the phone due to this. Too many issues with too many apps being killed. And yes I did all the things that should/needed to be done to prevent apps from being killed. Too much work involved per app just to get things to maybe work properly.
Same issue for me using the eu rom. Clearing all data works without restarting the phone. Starting to get annoying.
I have the same problem as OP.
I had it with my Ticwatch E when paired with Redmi Note 4, while my girlfriend's Ticwatch E connected with ASUS Zenfone works great.
Now with Fossil Gen 5 paired with Redmi Note 7 I keep having the same problem.
Does anyone know if the problem happens with Xaiomi Wear OS watches or Amazfit watches?
I fixed it by accepting all permissions on the wearos phone app.
borofanuk said:
I fixed it by accepting all permissions on the wearos phone app.
Click to expand...
Click to collapse
What else have you done? I also have a Xiaomi Mi 9T Pro with stock 10.3.4.0 and I have the same issues. It is becoming increasingly annoying... I am desperate. Wear OS is battery deoptimized in both menus, set to autostart and still the Bluetooth disconnects after a few hours. It is pretty clear that the issue is after Wear OS, as Wear OS app is running , but the phone somehow cuts Wear OS from the internet.
PS: Also have tried custom ROMS... Evolution X does not have the issue, but has other issues (like the fact that Android Auto does not work).
It's fixed! I hoped the move to Android 10 would solve the bluetooth connectivity issues with my Casio Pro Trek watch but did not expect that it would. But it did!
I now have a Pro Trek WSD-F30 in place of the F20 I had when I first made this post. Prior to the Android 10 upgrade, the F30 connectivity to the 9T was just the same as the F20. Bluetooth connection helped for 30 mins or so after restarting the phone then 'dropped' (the phone continued to send notifications etc to the watch, but the watch displayed the 'cloud with a line through it' symbol to indicate it was not connected and would not connect back to the phone.)
The Android upgrade alone did not fix the problem; I also had to 'factory reset' the Mi 9T which is now at 'MIUI Global 11.0.4 Stable 11.0.4.0 (QFJEUXM)` based on Android 10 with the 2020-01-01 Android security patch level. My phone is standard and unrooted though after the factory reset I removed many of the pre-installed apps with Xiaomi ADB Fastboot Tools. The Wear OS app on the phone is set to have 'no restrictions' in Battery Saver and Autostart On. Otherwise everything is just 'as installed' and it all works well.
My F30 has remained fully connected to my phone for 3 days. WiFi on the F30 is set to Automatic and I get 2 days plus battery life (I only got this previously if I had Wifi Off). The watch is now behaving as I hoped it would when I first got it. What a delight.
grantem2000 said:
It's fixed! I hoped the move to Android 10 would solve the bluetooth connectivity issues with my Casio Pro Trek watch but did not expect that it would. But it did!
I now have a Pro Trek WSD-F30 in place of the F20 I had when I first made this post. Prior to the Android 10 upgrade, the F30 connectivity to the 9T was just the same as the F20. Bluetooth connection helped for 30 mins or so after restarting the phone then 'dropped' (the phone continued to send notifications etc to the watch, but the watch displayed the 'cloud with a line through it' symbol to indicate it was not connected and would not connect back to the phone.)
The Android upgrade alone did not fix the problem; I also had to 'factory reset' the Mi 9T which is now at 'MIUI Global 11.0.4 Stable 11.0.4.0 (QFJEUXM)` based on Android 10 with the 2020-01-01 Android security patch level. My phone is standard and unrooted though after the factory reset I removed many of the pre-installed apps with Xiaomi ADB Fastboot Tools. The Wear OS app on the phone is set to have 'no restrictions' in Battery Saver and Autostart On. Otherwise everything is just 'as installed' and it all works well.
My F30 has remained fully connected to my phone for 3 days. WiFi on the F30 is set to Automatic and I get 2 days plus battery life (I only got this previously if I had Wifi Off). The watch is now behaving as I hoped it would when I first got it. What a delight.
Click to expand...
Click to collapse
I can confirm MIUI 11 fixes the issue (I am on EEA version of 11.0.6.0). Normally I never upgrade unless I have very good reasons so for the last couple of months I was using a partial workaround using Tasker to reopen WearOS and reset the bluetooth connection. But I am happy to report this does indeed fix the issue.... so for all of you reading this thread and having a Xiaomi phone -> upgrade to MIUI 11.
Many thanks grantem2000!

Couple of strange problems with my Chinese headunit

Hi,
I have got a YT9216CJ head unit which, generally speaking, works quite okay, except for a couple of strange problems.
1. When I want to use Google Assistant, I am able to invoke it only by clicking the app icon. I am aware that they Hey Google feature doesn't work on most of the Chinese headunits. However, each time the car starts up and I load the assistant, it will go into the Settings screen and prompt to set Google as the default assist app. If I do that, it works perfectly fine until the next key off, after which the same thing repeats again.
2. CarWebGuru is unable to access any notifications - e.g. Google Maps, which is required to show turn by turn directions within CarWebGuru. It complains that I need to grant permissions to read notifications. No matter what I do, it doesn't work. However, this particular feature works magically if I go to CarSettings and change the bootup to be "reboot everytime". Then the notifications seem to work fine. However, each start of the car causes the headunit to take a minute or more to basically load up, which is a real inconvenience with my car usage pattern.
Any ideas of how to fix this or even if I can have any workarounds? Help is much appreciated as I have beaten my head for many, many hours trying to fix these things
have you solved the problem with google assistant ? i have the same problem.. please help me !!

Categories

Resources