Database Info

Android Auto incoming calls

Not sure if it's a phone issue or Android Auto issue but I'm not getting a pop-up in Android Auto when a call comes in so the only way to answer the call is to swipe my phone. I did a reset on the phone today for other reasons but I swear it was working before. Can anyone think of a setting that's blocking this? I've checked the Android Auto permissions and they're all checked.
Sent from my MHA-L29 using Tapatalk

Little more info. I deleted and repaired my car to my phone, rebooted the phone, deleted and reinstalled Android Auto and still the same thing, no call control. Messages work as they should with an on screen pop-up.
Sent from my MHA-L29 using Tapatalk

No such problems here. All works as it should. Not sure what to recommend.

Got it finally. I unplugged the phone and stayed connected to Bluetooth. Called my phone from another phone and the call came through on the Ford sync 3 system giving me the options to accept or reject. I accepted it and while in the call plugged the phone back in which brought me to the call screen in Android Auto. Hung the call up and while still in Android Auto I called it again and the notification showed up and gave me the call screen when I clicked it. Unplugged and retried again about 5 times and the notification pop-up and phone screen work as they should.
Sent from my MHA-L29 using Tapatalk

same issue
Having the same issue, will try your solution. Thanks!

Sorry to resurrect the thread but I wanted to thank you for the solution. While my Pixel in 7.1.2 was working no problem, having to switch out of the M9 just for this issue wasn't ideal. Followed the outlined steps and sure enough, I can take calls as expected whether I'm connected to Auto or not. Turns out the 100th Google search is the charm. Thanks!

Same issue with huawei honor 8
I am having the same issue with the huawei honor 8, and the fix does work for a time. The darn issue keeps coming back, which is obnoxious. Any one have an idea of what is causing to bug?

i heard its an EMUI issue and not an issue the phone particularly, and its up to Huawei to fix this. Im having the same issue which is tough considering i just came from a galaxy s7e that gave me tons of issues, but worked perfectly in AA

Bluetooth Connection Problems with Garmin Vivosmsrt HR

Hello again,
after my themes problems at the last time, I have a new problem and I don't found a solution. The problem is between my Honor 6X and my Garmin Vivosmart HR/Garmin Connect Mobile. I use these combo round about a half year, with some little (normal) problems. If the connection is gone, I restart my phone and everything works normal.
On Thursday evening, the connection between my phone and my Garmin is gone. I try on Friday everything.
These are the things I try
- Reboot the phone
- ‎Reboot the Garmin
- ‎clear cache and data of the app
- ‎Factory reset of the Garmin
- ‎uninstall the Garmin app, reinstall
- ‎Factory reset of my Phone
Nothing helps...Now the problem is, that I can't pair the Garmin. The Garmin shows a pairing code, but the code is after 3 seconds away. In that time I don't have a chance to type the code in the phone. After 3 or 4 tries the app said, that there is a problem.
Now I don't have any more idea.
A try with my Huawei Mediapad M2 tablet works. That connection works.
Other Bluetooth devices (speakers, earbuds) are working.....
Have someone an solution ? I'm a little bit frustrated about it.

I had a similar problem just yesterday. I was unable to pair the 2 devices due to the possibility to insert the code before the possibility goes away (exactly as for you). I was able to do the pair restarting several times the 2 devices, turning off and on both Bluetooth, waiting until the possibility to insert the code didn't vanish after few seconds. But then I had another problem: the Forerunner was not reconnecting after loosing connection due to devices separation.
Here my lucky attempt starting from scratch (unpair and reboot both devices): ***on the phone I set the timeout for visibility to all devices to infinite*** (initially was 2 seconds).
Here the magic: I was able to pair the 2 devices without issues, I can even separate them and when they are insight the connection is immediately recovered.
Hope this help.
Cheers

Ok, I will try it. The first fast try didn't work. So if it doesn't work, I will take a look to the new Huawei Mate 10 (lite)
I have installed the firmware new, but that is not the solution. I can't understand what the problem is. It is a very scary thing.

So, after many trys I am frustrated....It didn't work. The Honor an Garmin Support doesn't reply. What I try is the bluetooth connection to two cheap Fitnesstracker (under 20 Euros) and they are working without any problems.

Same here. The pairing code is gone after some seconds and a new one is generated, making it impossible to pair the devices. Anyone who has an idea? Worked just fine with my old Xperia Z1C

Tontauber said:
Same here. The pairing code is gone after some seconds and a new one is generated, making it impossible to pair the devices. Anyone who has an idea? Worked just fine with my old Xperia Z1C
Click to expand...
Click to collapse
Even miracast is problematic most of the time

Thank you for sharing your experiences. This doesn´t make me very optimistic...

Hi, I was able to pair my Honor 6X with my Garmin Fenix 3 HR, after many tries, using the various suggested techniques (restarting, leaving visibility on etc.)
It appeared pretty much like a lucky moment to have been able to pair.
The connection is however not very reliable - the two devices disconnect from each other frequently and do not automatically reconnect.
Very frustrating.
On different forums I read that many people are having problems with the bluetooth of the 6X, not only with Garmin trackers, but also with Fitbit.
Apparently there will be an firmware upgrade to the next Android/EMEI version by the end of this year, or beginnning next. I hope that will fix the problem.
I would be grateful when someone has a fix, but for the moment it looks like it is a known problem/bug, without fix.

I just bought a vivosmart HR+ and have the same problem. Has anyone tried to downgrade to 4.1 and pair the device? I'm curious if this would allow it to pair, and then if the pairing would survive the update process back to 5.0. If no one has tried, I might give it a shot this weekend. I lucked upon this device at my local Target as "rapackaged" for less than half price ($85.00 as opposed to $179.00).
As far as bluetooth problems with the 6X goes, I've experienced problems with a Pebble Classic and my Android Wear Sony SW3. Both paired just fine, but would stop receiving notifications at random, making them unreliable at best. It seemed to only happen with the 6X. My previous S5, BLU R1HD, and work's S6 never gave me these problems. I too am hoping a future update solves this. I considered trying EMUI 5.1 from the ROM section, but users seem to be reporting other problems there that I don't want, such as reboots, etc.

I happened to buy a second Honor 6x for my wife. It came with EMUI 4.1 and I tried to pair my Vivosmart HR+, but had no luck. I couldn´t even get a pairing PIN in the Garmin app. It would just do connection timeouts.
So EMUI 4.1 seems to be no solution.

Good news: at the garmin forums, some user called fin.pimlico had a clue where to search for the error and came up with a procedure that worked for me.
but read for yourself:
https://forums.garmin.com/forum/on-...unable-to-pair-fenix-3-with-android-7-0-phone
Good luck!

Hopefully this will help me out. My phone is having to be sent in to the service center for repair some I bricked it. So when it comes back, I'll definitely give your a shot. Thanks.

Garmin devices are developed to pair through Garmin Connect, and not Bluetooth. If you open and close your bluetooth connection, and try to manually pair devices, you're going to have problems. Skip trying to pair and connect altogether, open the app, and do EVERYTHING through the app, NOT MANUALLY.
---------- Post added at 03:33 PM ---------- Previous post was at 03:30 PM ----------
When I say skip, I mean delete ("forget") any direct connections you've already established through Bluetooth between your device and your phone, and go for the "Garmin Devices" option in the app, tap on "Add Device" and follow the steps until you manage to connect directly through the App.

@scolfaro
You´re right, but unfortunately this isn´t the problem we are dealing with here. The pairing of an HONOR 6x didn´t work from within the Garmin app. As I mentioned before, fin.pimlico tracked down the cause of the error and his solution of temporarily deactivating Wifi, GPS, and Data connection during pairing (from within the app) worked for me.

Tontauber said:
Good news: at the garmin forums, some user called fin.pimlico had a clue where to search for the error and came up with a procedure that worked for me.
but read for yourself:
https://forums.garmin.com/forum/on-...unable-to-pair-fenix-3-with-android-7-0-phone
Good luck!
Click to expand...
Click to collapse
Thanks for posting this. My device came back to me today and I was able to successfully pair my tracker with my Honor 6X.
Well, the connection is flaky at best, I've had to repair twice already. I wonder if it will be better on one of the other ROMS, like Lineage OS....

I received an email from Garmin today that basically said that they've been working with Huawei and that the problem has been fixed. They said unfortunately, it means our device needs an update so we're at the mercy of Huawei to release the update. Below is a copy/paste of the email they sent me:
Dear Customer,
According to our records you’ve contacted us regarding connectivity issues with your Huawei phone and Garmin device. Please know that this is a very high priority issue for us and that we have escalated this issue to Huawei Engineering. We’ve recently been pleased to hear that their team has identified the solution to the problem but that it will require an update to your Huawei phone. We have requested an expedited release of this fix, but unfortunately at this time do not have a commitment from Huawei as to when this fix will become available.
We’ll be sure to keep you informed as soon as any additional progress is made on this issue.
Thank you for your patience,
Garmin Product Support

this is why I sold my 6x and got me a G5+ instead... not that that's any help, but still... super device, questionable software...
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
lordmorphous said:
Thanks for posting this. My device came back to me today and I was able to successfully pair my tracker with my Honor 6X.
Well, the connection is flaky at best, I've had to repair twice already. I wonder if it will be better on one of the other ROMS, like Lineage OS....
Click to expand...
Click to collapse
btw, I'd definitely try my hand with any LOS 14.1 build you can find...

i'm on P9 Lite; same problem; tried flashing 2 LineageOS ROMs to solve - look good and fast without Huawei bloatware but still do not sync with Garmin and other issues

Tontauber said:
@scolfaro
You´re right, but unfortunately this isn´t the problem we are dealing with here. The pairing of an HONOR 6x didn´t work from within the Garmin app. As I mentioned before, fin.pimlico tracked down the cause of the error and his solution of temporarily deactivating Wifi, GPS, and Data connection during pairing (from within the app) worked for me.
Click to expand...
Click to collapse
I tried to follow fin.pimlico's instructions scrupulously, but my Honor 6X will not let me proceed with Add Device without WiFi and Mobile Data being on. How are you able to do that? Anyone else get that error when trying to proceed with WiFi and Mobile Data off?
I was able to connect via Garmin Connect after uninstalling all updates to Google Play Services. I don't expect that connection to survive once Google Play Services updates again, as it unavoidably will. Hopefully, this will give a clue to someone highly skilled and experienced in Android inner machinations.

@NotNalb
I did it like "magi3x" in this thread:
https://forums.garmin.com/forum/int...rt-hr-and-huawei-p10-lite-pairing-issue/page2
"After the phone searches for the watch and asks you if you want to pair it or go on searching, I click "yes" and IMMEDIATELY minimize the garmin connect app and turn off Wifi, and GPS.
I return to GCA and wait for the pairing pin to appear.
Before I enter the PIN on the phone i return to settings and turn on Wifi and GPS again.
Back in GCA I enter the PIN, press OK and the pairing is successful.
I had to try this several times in order to get the right timing but in the end everything went smoothly."
Click to expand...
Click to collapse

Unbelievable. Oneplus claims that a bug is now a feature.

Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!

I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie

MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.

nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!

nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all

kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.

So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders

Phone functionality intermittently lost after upgrading to P

If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.

Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.

mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.

Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.

Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.

brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..

Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.

brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.

Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.

App updates hang / delayed notifications

Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?

This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.

mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.

selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.

This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.