When on calls and using Bluetooth (Lg FP8) if i get a notification the audio on the call becomes robotic and I can't make out the words of who I am speaking with. I have to toggle speaker on and back to BT to get it to stop. Doesn't happen with every notification, and isn't isolated to just one app afaik. Anyone else have this issue?
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Try a network reset.
If that doesn't work try a hard reboot (soft reset).
ah0y said:
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Click to expand...
Click to collapse
Here's a list of bugs as of Nov. 27 and their status:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com
Related
Hello there.
I am using the X since a few weeks. It is a damm nice phone. perfect size, brilliant display and the rest of the specs is cool too.
But:
I can connect it with my car. I can get calls in the car using the audio + mic from the car. But I cant use the phonebook. And so I cant see who is calling or even use the carphonebook for dialing a number or use favs.
BT itself is working: I already transfered e.g. contacts via BT from my old phone. The UP MOVE is synching.
I also tried it on an BMW F20 - same problems.
In other forums ( e.g. oneplus ) I found some other persons with the same problem. They "solved" it by buying an app calles "Bluetooth Phonebook". It seems that the app will add/replace/change some BT Profiles.... It seems that there is an profile missing: PBA, PBAP Phonebook Access Profile.
If this is so, it will mean that OnePlus is not finished with the Oxygen 2.2.0.
The offical support can´t answer this question to me
Questions:
Can someone tell me how to check if this profile is on my phone?
If not present - how can I add it by myself?
Any other helpfull ideas?
Bluetooth Phonebook app is the easiest option.
Or i believe BT works with cyanogenmod
http://forum.xda-developers.com/one.../rom-cyanogenmod-13-x-oneplus-x-onyx-t3279784
I would not rely on Oneplus to fix it as the problem still exists in the Oneplus 2 and thats been out even longer than the Oneplus X.
Workaround
I also have the exact same issue with my 2015 BMW. BT connection for calls work stable but contacts are only synced partially. My solution was to again and again delete and re-connect my OPX until in one instance all contacts were available in the cars phonebook. I then stored all important contacts into the cars phonebook so that they are always present independently from the connected phone. Not ideal but a workaround.
The issue for the OP2 was solved with the latest OTA update. So hopes are that OPX will receive the same fix...
I also have the same problem with Seat Léon St.
According to OnePlus community on Google+, this issue has been solved with the last update of OnePlus 2.
I already contacted OnePlus Support on Twitter but they cannot confirm.
Envoyé de mon ONE E1003 en utilisant Tapatalk
I had a similar problems. With my OPT and OPX with My 208 GTi. Using Bluetooth Phone book from the play store was the easiest option.
Sent from my OnePlus X USO g Tapatalk
+1 BMW e71 2012 / Ford Kuga 2015. Bluetooth phone book solved both, although Ford sync took a couple of attempts.
Something that oneplus needs to sort. Shouldn't need to pay to get this basic functionality
That's a known bug on OxygenOS from loooooonnnggg time ago, it was finally solved on OP2 in the last update so, it must also be fixed on OPX in the nest update...
On CM12 \ CM13, etc, it works great with all car bluetooth systems...
at the moment i am still in contact with the OP Support Team.
They are still NOT commenting the missing BT profile in Oxygen.
The App "BT Phonebook" is realy working. So imho its a missing basic feature of OP and has to be fixed.
Yesterday I got an OS update on my OPx but in the readme was nothing mentioned about BT
This is probably not what you guys are looking for but i had the same problem with my sony headunit no contact names would display just the phone numbers. I have since installed custom rom CM13 by ashwin and everything is working contacts display names and i can search people to call through the stereo settings etc.
Indeed. I don't really want to flash but my wife was connected to my car with her OnePlus One within the minute and streamed Spotify... So yes, this is not we really want but at the end, OxygenOS is a bit bugged
I have the same problem with my 2011 Mazda 6. Bluetooth Phonebook did NOT solve this issue for me...
jevgeje said:
I have the same problem with my 2011 Mazda 6. Bluetooth Phonebook did NOT solve this issue for me...
Click to expand...
Click to collapse
yesterday the support was contacting me: They know about the issue and are working on an fix. No date
Hi There,
I have bought a used Galaxy Note 10.1 (2014) LTE for my mother and flashed lineageOS 14.1 nightly march 2018 on it. So far, it had no or only only minor issues (maybe a not responding app here and there or crashing trebuchet launcher very few times). The main purpose should be whatsapp. I was not expecting any problems, but it turned out that when we want to start a audio call, whatsapp freezes after 3 or 4 seconds or so. The counterpart just hears "toot-toot-toot..." and whatsapp freezes (not completely, but it begins to respond veeeery slow and one can not hear anything anymore). I found out, that it freezes only when I turn "handsfree" mode on, this means, when I turn on the speaker with the speaker icon in whatsapp. This is mandatory, because there is no other way to hear your counterpart (except maybe using a headphone, I did not try this yet, but this would be a hassle for my mother and I had none to test in the first place). The freeze does not happen as long as I don't turn on handsfree mode (but as mentioned, this is the only way to hear the other person). This happens in both directions: incoming AND outgoing audio calls.
What I tried:
- clear app cache
- clear app cache and data
- reinstall whatsapp
- update lineageOS to october 2018 version (was march 2018) and reinstall whatsapp
Nothing worked. Any ideas? Anyone had the same issue?
P. S. If it was my device, I simply would try to work around that, but this is the first "computer" ever for my mother, and I don't to bother my mother with more complications e. eg. explaining how to use a headphone etc. I promised her that a "computer" would enable her to do "phone-calls" to our relatives for free plus text-chats and photos/videos. Now this is a stupid situation for me, as you might see... So any help will be appreciated!
P. P. S. By the way... lineageOS tells me on their website that lt03lte is no longer maintained, and so is the galaxy sII (i9100) for example. They also deleted the link to the nightlies for the i9100, although one can download a nightly dated 20181216 on their site through doing a google search. But for the lt03lte even the nightlies download page has disappeared. Even if the developer does not maintain the devices anymore - why do they delete the link to the last builds or even shut down the download page as with the lt03lte? I was lucky to have downloaded the october version for the lt03lte back then, but I don't understand why they take the last builds off their site. Can anyone explain what taking down the last builds is good for, even if there will be no more builds in the future? I don't get it...
Thank you all
regards
bb
Since the Pie update if I have bluetooth on and connected, my s9+ has no notifications sound. It will vibrate but no sound. I have checked what I think it could be and tried the device in safe mode to eliminate an app issue. Seems Pie has a notification bug. How do I submit issue to Google or get help?
Any ideas on the issue?
So I did a network settings reset on the device. Seems to have fixed the issue.
jadams161 said:
So I did a network settings reset on the device. Seems to have fixed the issue.
Click to expand...
Click to collapse
I have the same issue on Samsung S9 with Pie.
Because of your post I reset my network settings but the issue is still there. (all the wifi and Blutooth settings are gone).
So, that doesn't seem to fix it.
You just need to reconnect to your wifi and Bluetooth connections. Mine worked until I restarted the S9 back to no notification sound.
Same problem here. If my bluetooth device is connected, but not in my ear, I don't hear the regular notification sound as I did before the upgrade to Pie.
Sent from my SM-T820 using Tapatalk
jadams161 said:
You just need to reconnect to your wifi and Bluetooth connections. Mine worked until I restarted the S9 back to no notification sound.
Click to expand...
Click to collapse
Sorry, but in my eyes that is not a fix if it doesn't survive a reboot.
It's probably a workaround hack with nasty side effects of loosing all connection info.
Someone tried with a factory reset? I'm thinking about doing it, but if someone did it and it did not work...
Enviado desde mi SM-G9650 mediante Tapatalk
JavoSpam said:
Someone tried with a factory reset? I'm thinking about doing it, but if someone did it and it did not work...
Enviado desde mi SM-G9650 mediante Tapatalk
Click to expand...
Click to collapse
I have done the factory reset and nothing has been changed, still same issue
I believe Samsung can solve this issue, but as usual they are lazy as their monthly update
Notification Problems in Android 9.0
I don't know whether this is the correct forum, but I am having problems with repeating notifications that worked perfectly well in 8.0 before the update.
I use an app "Prof Reminder or Missed Call Reminder" that allows repeating notifications with a specified notification sound and repeat period.
With this app, I have been unable to get repeat notifications with WhatsApp, the first comes through, but then after nothing (it seems the signal is dismissed).
When using BlueMail (email app) repeat notifications work perfectly.
Have checked app the settings, permissions etc., and everything looks correct, been through it so many times and double checked everything.
Cannot understand why one app works perfectly, yet another will not work!
Would appreciate any advice or experience, if this is the wrong forum please let me know.
Were are the Notification being stored since Pie?
It looks like to me they are in the system and not reachable unless rooted. Since Pie, I've lost needed sounds that no longer are available.
Is there a way to add back some of the lost sounds that existed prior to Pie?
Notifications for indiviual apps do not sound. I have an app sound for messages but it does not work nor do anyother app sounds work even the Settings Sound does not sound for any app that is requestiing an individual sound. Is this just mine or are others having the same problem???
My notification sound is reset to zero about every day or other day since the upgrade to Pie (no bluetooth involved). No idea what causes this but I am pretty sure it's up to Samsung to fix.
It's occurring on Pie based ROM's. Verified in LineageOS 16 & crDroid 5.4. When connected to Bluetooth , phone is not ringing in speaker but vibrates. So you'll miss calls if you not wearing the Bluetooth headset.
Reported at https://github.com/crdroidandroid/android_frameworks_base/issues/245 , but they mentioned this needs to fixed by core team.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.
Hello,
since I purchased my Redmi Note 10 (which came with MIUI Global 13.0.7, Android 12) I experienced some bluetooth issues which I hadn't with my previous phone (Redmi Note 7 with Android 10).
E.g.: I'm wearing a device (Dexcom G6) which sends every 5 minutes my blood glucose value to my phone via bluetooth; if I'm away for a while, the device doesn't reconnect automatically but asks for pairing again... and until I confirm I don't get new values. This could happen several times per day.
I've read a lot of people complaining about this behaviour (that seems related to Android 12); several workaround are suggested but nothing really solved the problem. I can provide more details if needed
Btw, the connection with Miband 6 is unstable too.
These issues are quite annoying and, as I said, I didn't experience them with my previous phone, so I'm wondering if switching to a custom rom can help me on this!
Hello,
Changing ROM can help, if the problem is software and related to MIUI for example.
As a last resort, I think it doesn't cost anything to try custom ROM, it is always possible to go back to the initial MIUI, if necessary.
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
spider1163 said:
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
Click to expand...
Click to collapse
Thanks for your reply!
Bascially, there are several apps well known in the diabetics community that can be used to read values from the device: xDrip+, Dexcom etc.
They all worked flawlessy on my old phone but with the Redmi Note 10:
- xDrip+ disconnects for 20 minutes after each reading (it should be 5)
- Dexcom asks for BT pairing now and then, sometimes even when I'm near my phone
Of course I disabled battery optimization.
These issues have been reported by users since Android 12 and not only on Redmi phones...
I tried to follow some suggestions:
- disable BT battery optimization: this was possible on Redmi Note 7 but I can't find such option on my Redmi Note 10;
- use apps like "Blue Car Tethering" that force BT tethering with paired devices; this improves the situation but doesn't solve it (with Dexcom I get fewer BT pairing requests, and with xDrip+ I get readings every 10 minutes);
- on "developer options": change "ACRCP Bluetooth" and "MAP Bluetooth" versions, but it didn't work even trying all possible combinations.
I'm experiencing problems with my Miband 6 too, that sometimes disconnects from its app; this didn't happen on my previos phone but it could be related to some bugs with the app itself.
My feeling is that, generally speaking, BT is more unstable.
Important: there are also users claiming not having issues with Android 12 at all, so maybe they are related to some manifacturer customizations; that's why I'm wondering if using a custom rom can help.
Sorry if I was too long but I tried to give more details.