My partner and I both have the exact same bluetooth speakerphones (Driventalk BHF2000). They are supposed to automatically download the phonebook from the phone so they can announce who the caller is on incoming calls. It works on his Galaxy S2, but not on my Note. Every time I initiate the sync, at acts like it's downloading, then it says "download cancelled".
Is this an issue with the Note that anyone else is experiencing? I'm on stock KK9, but rooted.
Related
Serched for but have not found this problem described. Periodically (avg 1x per day) my tilt enters a state where there is no sound at all either way during a phone call. The status shows dialing and connected, but neither I nor the receiving party can hear anything at all, though the phone call does go through. Other sounds work fine in other applications, its just the phone.
Once it enters this state the only remedy I have found is reboot.
Any thoughts?
Thanks in advance
John
happened my TyTN II.
In my case, I found my bluetooth headset started up Voice Commander by accident. Problem fixed after starting Voice Commander and Exit it gracefully one more time.
Worse case, a reboot will fix it.
My nexus 6p has been working perfectly with my 2016 vw for past couple of months. Now, I can no longer send a text message or hangouts message. Still connects perfectly, makes calls and navigates by voice but no longer listens when I want to dictate a message. This seemed to happen overnight as it has always worked perfectly before and I am not aware of having made any changes to my phone or car. How weird. Anyone have any ideas?
I'm having the same issue with my Galaxy S7 Edge running Android Auto on my Pioneer AVH-4100NEX. I went on vacation and my car sat for a while and now when I'm in Android Auto mode I can't receive and send text messages. I ask Google for the weather or to do a calculation and I get nothing. However, if I ask Google to dial someone whether in my contacts for not, it dials the number. Does this make any sense? There doesn't appear to be any official Android Auto support. I contact Pioneer and they told me my contacts weren't syncing with Android Auto which was strange enough when they said it, but given the fact that I don't get a reply when I ask GoogleNow for the weather means my contacts shouldn't have anything to do with it. Any help would be appreciated.
Thanks,
Matt
Hi,
I am getting annoyed with my Watch now as it doesn't seem to behave consistently.
Making a call via my phone using the watch:
I used to be able to say 'call <persons name>' to the watch and it would initiate the call on the Phone. No I just get a 'calling xyz' display/timer, that then does nothing.
Many Thanks,
Paul
Bloody annoying.
Sometimes it will ask me for an option where to call from.. Phone or watch.
I usually keep cellular off.
Text via google assistant does not work unless it's via phone sim. Stupid implementation. Hope they fix this.
So the new automatic screening option is awesome, except the note that "Automatic screening won't work if your phone is connected to headphones or speakers." Apparently my Galaxy Watch counts as this.
I never use my watch to make or answer phone calls, but I DO want the incoming call notifications/vibrating because sometimes my phone isn't handy and it let's me know so I can run and grab it if need be.
So a couple questions:
1. Anyone know if this behavior is the same for WearOS watches?
2. Anyone think of a way to address this? I tried disabling the phone toggle in the bluetooth connection, but that ended up preventing the notifications (though it did enable the screening).
Surprised more people haven't bumped into this issue.
I've been using my gen4 fossil and the automatic screen call works with it.
Bit of a disappointment that the basic function of the phone is not working correctly!
In order to be heard on a call I need to switch on speakerphone. Anyone else had this issue?
Tried wiping the cache and restarting the device.
Verified that the microphone is working. I can make calls with Messenger, WhatsApp etc.
Upon hanging up, there is an audible pop on the receiver end during my tests.
Affects both incoming and outgoing calls.
NX627J_V1AMB with build NX627J_ENCommon_V2.03. The phone came with V1.03 but did not test calling.
Phone app build version 11.0.
Any help much appreciated.
Hi,
Ordered my phone with EU distribution and came with NX627J_ENCommon_V2.03 and I don't have such a problem. Maybe flashing went wrong? There are many users experiencing issues after flashing.
Sent from my NX627J using Tapatalk
Hi, this was after flashing but I've since debricked (using https://forum.xda-developers.com/nubia-z20/how-to/tool-nubia-z20-unbirck-tool-t4009227) so believe I'm on the correct firmware. If someone can confirm this is the case that would be useful otherwise I will try and flash firmware