Database Info

[Q] Did Samsung ever fix the low level volume fluctuation?

Hello,
Did Samsung ever fix the low level volume fluctuation problem through the headphone connection on the 7.0+? Listening to lower level music files at lower volumes resulted in the volume jumping up and down slightly. The problem occurs regardless of whatever music player app is used. The files play fine on the Samsung Galaxy 5.0 player and other devices.
Thanks!
Update: It's not fixed.

This thread is the only reference I could find to this issue anywhere. Is it documented more fully somewhere else? Is Samsung aware of it and planning to fix it? Any references or other help would be greatly appreciated.
I've had my 7.0 Plus for about a week, and yesterday was the first time I tried listening to some classical music favorites featuring very soft choral passages. I couldn't. The volume surges every couple of seconds during soft passages. It sounds as if some demented engineer thought it would be a good idea to add an automatic volume equalizer to make sure the music never gets too soft. No. Very bad idea.
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.

Sun_Cat said:
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Click to expand...
Click to collapse
I've had the same problem with 6210 from day one. Other than album art being screwed up, it's the only real annoying problem I've had with the box.

The problem may be in the default player. I use poweramp and don't experience that
Sent from my DROID BIONIC using XDA

It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.

Sun_Cat said:
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Click to expand...
Click to collapse
I hear it using TuneIn Radio. Hoping for a fix with ICS.

UPDATE
I've found two earlier references to the issue:
A review on Amazon from last November (reviewer says he's notified Samsung)
A post by this thread's OP, also from November (like me, he thought it sounded like Automatic Gain Control; unlike me, he remembered the right name for that feature )
Again, any more references, especially from Samsung, would be appreciated.
ETA: I found one on the Samsung support page (search for the string "How can I stop the volume" and click on the text to open the answer). It was answered, not by Samsung but by an anonymous user, who said "Sorry charlie, but you've got a headphone jack with a malfunctioning sensor. Sorry!"
I suppose that's a plausible explanation, but against it is the Amazon reviewer, who said he had the same problem with two different units. And then there's me and the OP here.

redsmear said:
The problem may be in the default player. I use poweramp and don't experience that
Click to expand...
Click to collapse
I installed Poweramp. Nice app, but it doesn't help with this problem at all.
To hear the problem you have to be playing music with sustained passages that are very soft. With most pop, rock, and jazz it won't be noticeable. That's probably why the issue isn't more widely reported.
Try this video in your YouTube app. If your Tab Plus is behaving like mine, you'll hear several volume surges during the first 20 seconds or so. ETA: Crap! I can't post outside links. Here's the last part of the YouTube URL, after the slash: watch?v=6-i1ESIRKdA.

One more clue
And I found one more indirect clue in the Samsung Troubleshooting Guide under the heading GT-P6210 Volume Drops When Headphones Are Plugged In:
The volume on your Tablet will drop 75% when you plug in your headphones. This is a preventive measure for acoustic shock to your ears. The volume can be increased after the headphones are connected.
Click to expand...
Click to collapse
Obviously this proves nothing about the issue we're discussing, but it is suggestive because it tells us that something in the firmware is deliberately designed to mess with the headphone volume.

Aha, so it's not just me who noticed this "feature" then

For anyone who is experiencing this issue and wants to let Samsung know about it in one place, I've started a public thread on their Facebook support wall. You'll have to imagine the first part of the usual Facebook URL since I can't post links. Here's the last part, after the slash: samsungsupport/posts/10150588609036213

Nothing from Samsung Support on Facebook since yesterday morning. One other person has posted there (thanks, Mark, if you're reading this). It would be nice if a few others would chime in.

I'll chime back in. I'm glad somebody else has finally noticed! The problem also exists with the Verizon SCH-i810 (Tab 7.7) but, perhaps, to a lesser degree.
I strongly suspect the (Yamaha?) driver and/or its configuration -- see the original post from November that shows the (configuration?) files. I suspect that file may hold the key to the problem. Problem is, I have no idea what the numbers actually mean and didn't find any documentation for those numbers (data sheets, etc.). I did attempt at the time to tweak a few numbers using my "best guess" by comparing the entries for rx-speaker vs. rx-headphone vs. rx-headset. but no discernible effect was heard.
No prizes for guessing who was raising such a fuss in November.
The "Sorry Charlie" answer is incorrect and I flagged it as such.
UPDATE: I found the 7.0+ /etc/audio files and I have the 7.7 /etc/audio files. There are some differences in the numbers and the 7.7 audio files (LVVEFS) have some comments (!!!) in them so maybe I can track down pertinent parameters.
Anyone else have an opinion or another idea? Is this a waste of time?

Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.

Sun_Cat said:
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Click to expand...
Click to collapse
They just answered about 1/2 an hour ago. They provide a link and ask us to go to the Samsung Service Facebook page and fill out a support form. Might as well. Keep the pressure up on someone over there.

Agreed. I just submitted their form with full details. We'll see whether they follow through.
A hint to anyone posting there: Samsung appears to be great at stalling by asking follow-up questions. Include as many pertinent details as possible in the initial post, such as model, wi-fi or data-enabled, serial number, firmware, streaming or stored music sources, which apps, etc., etc., and so forth.

Well, at least they're responding, but I'm not sure it's helping. This morning they replied to my original Facebook post:
We can suggest checking to see if the same problem occurs in a different set of headphones or speakers. If the problem persists we will suggest servicing your Tab.
Click to expand...
Click to collapse
I've already checked with different headphones (not speakers; I've already told them several times that it's a headphones-only issue!), so I already know that the problem isn't due to one set of headphones.
This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.) I'm reluctant to send it in for service. The problem is subtle enough that someone lacking a trained musician's ear is likely to just say it's fixed and send it back. We already know that the fellow who mentioned this issue in his Amazon review got a second unit exhibiting the same defect.
Also, I have not heard from Samsung directly in response to submitting the official support form the other day, so I can't now tell whether or not this latest comment on the wall is coordinated with that other support request.
Does anyone have any advice? Has anyone here dealt successfully with Samsung support in the past, on any issue at all? How did you do it?

Sun_Cat said:
...This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.)
Click to expand...
Click to collapse
I agree. I don't believe it's a headphone jack issue either. I'm going to wait until ICS comes out and then decide what to do if it's still an issue.

I've tried adjusting some numbers in the .txt files -- no change yet. Maybe I'm adjusting the wrong file. Who knows?
I'm surprised there aren't more complaints. It's easy to identify. Headphones, earphones -- doesn't matter. The problem exists with Samsung's earphones. They can't run away from that one. Doesn't the 7.0+ come with four audio files? I can't recall if the problem could be reproduced with those files, because the problem needs periods of relative silence to get into the "AGC" mode. I think the Samsung support is in typical "denial mode". Problem? What problem? Let's go through all the permutations of user error or workaround before considering that there is a problem. It's a matter of problem ownership -- and Samsung isn't owning it.
The questions I would ask are: "Have you tried reproducing the problem?" "Do you know how to reproduce the problem?" "Who has the capability to reproduce the problem, if you can't".
Yes! Just found the Samsung music files, going to try to reproduce with all Samsung supplied software and equipment.
UPDATE: Reproduced the problem on Galaxy Tab 7.7 with all Samsung supplied files/software/equipment:
MATERIAL:
1. Samsung supplied "Music Player", no EQ
2. Samsung supplied music file "Silky whisper.mp3"
3. Samsung supplied earphones, white with button and mic (I think it's pretty generic to Samsung)
Steps:
1. Start Music Player.
2. Make certain volume is all the way down and the sound is muted (slash through speaker)
3. Press the volume up button once, twice (once to unmute and one step higher)
4. Play music file. Note how the piano cuts in and out throughout the song, especially during the opening of the instrumental.
I suspect that Samsung is going to hand this issue off to Yamaha. The constant in this matter is the Yamaha-sourced audio chip/driver/library/configuration/firmware.
Here are some files to compare from /etc/audio (I added the model to the name):

TonyBigs said:
It's a matter of problem ownership -- and Samsung isn't owning it.
Click to expand...
Click to collapse
Agreed. That's why my first question to them on Facebook was "Are you aware of the problem?" No way will I send my GT7+ to them for service until they take that step.
I'll try your steps later today and see if I get the same result. Maybe we can gang up on them.
I have one additional datum since last week. I've tried to reproduce it on Bluetooth headphones, and the problem does not show up. It's only there with plugged-in headphones.
I suppose this could be interpreted as evidence slightly inclining toward the "defective headphone jack" theory. But I still don't think so. If anything, I think it could be related to the Self Aware Volume Ghost on the Galaxy Nexus, which Samsung apparently did acknowledge. Except the Nexus bug was much more obvious since the volume control indicator actually appeared on the screen and changed.

[Q] Message Access Protocol - HandsFreeLink

I have a 2013 Honda Accord which has an infotainment system that supports MAP. My phone asks if it wants to give it access, I said yes to all double checked in the settings that all are checked but it still doesn't do anything when someone texts me. It is supposed to Auto Read them and I made sure that setting is on on my car as well. This system should be the same as some Acuras as well.
Some additional info: When I choose select account it says this phone doesn't support this feature.

Same problem here with an aftermarket BT deck.

Has anyone got MAP to work with anything?

Works fine with 2012 BMW
MAP is flawless on my 2012 BMW iDrive system.
B

bwagner said:
MAP is flawless on my 2012 BMW iDrive system.
B
Click to expand...
Click to collapse
Did you do anything special? Or does it just work after connecting it to Bluetooth. I fear this is a Honda issue but that doesn't make much sense since it does support some Android phones that probably had MAP before and the iPhone.

I received a similar prompt asking about the car accessing my calls and another about messages. Accepted both and it just works.
MAP was added to CM 10.2 awhile ago, and it worked the same on my LG Optimus G (basically a Nexus 4).
B

Doesn't seem to work on my e90 my10 Idrive. It used to work with sense ROM but not with cm 10.2 on my HTC one x
Sent from my Nexus 5 using Tapatalk

Anyone have any luck getting this to work? I get an envelope icon on my iMid screen, but an error message stating "the connected phone does not support this feature" when it attempt to read out the message. I have a 2014 Accord EX-L.

I'm in the same boat as OP. I've got a 2013 Honda Civic Si and a Nexus 5, and they don't work well together.
From my research on this, I believe this to be a flaw within the Hangouts app, and not a communication problem between the phone and the head unit. After playing around with it for a while (deleting the pairing profiles, repairing the two devices, clearing the system in my car, etc.), I noticed a few things that lead me to this conclusion. After a few connection attempts, the car only successfully read me one message. Afterwards, the text message functionality on my i-MID was selectable, but clicking the enter button wouldn't do anything. Checking my phone, Hangouts was also frozen. The phone was telling me (via ringtone and notification popups) that I was receiving texts, but I couldn't read them until I disabled BT and force closed Hangouts.
Is this a common problem that we are all experiencing? Can any of you confirm or deny these ideas? Also, which messaging app is everyone using (I don't want recommendations, I want to know if this is Hangouts' fault or not)?

Got a 2014 accord same problem. My fix was stopping hangout.. Works fine now I have a nexus 4 running 4.4.4
I think the Honda only uses Sms only and hangout tries to convert it
Sent from my cm_tenderloin using XDA Free mobile app

gecoffin said:
Got a 2014 accord same problem. My fix was stopping hangout.. Works fine now I have a nexus 4 running 4.4.4
I think the Honda only uses Sms only and hangout tries to convert it
Sent from my cm_tenderloin using XDA Free mobile app
Click to expand...
Click to collapse
So did you end up having to use a different SMS app, then? If so, which one worked for you?

I used the stock Sms app that came with the phone. My problem was I saw the text come thru on my accord , but was unable to hear or see the message.... Same problem with my old texts also. I do not use hangout so disabling was not a problem
Sent from my cm_tenderloin using XDA Free mobile app

gecoffin said:
I used the stock Sms app that came with the phone. My problem was I saw the text come thru on my accord , but was unable to hear or see the message.... Same problem with my old texts also. I do not use hangout so disabling was not a problem
Sent from my cm_tenderloin using XDA Free mobile app
Click to expand...
Click to collapse
Ah, well, that's a bit different that the problem I've currently found myself in. For me, the text messaging functionality is permanently disabled in my i-mid display. I'll give getting rid of hangouts a try, though!

cdchris12 said:
I'm in the same boat as OP. I've got a 2013 Honda Civic Si and a Nexus 5, and they don't work well together.
From my research on this, I believe this to be a flaw within the Hangouts app, and not a communication problem between the phone and the head unit. After playing around with it for a while (deleting the pairing profiles, repairing the two devices, clearing the system in my car, etc.), I noticed a few things that lead me to this conclusion. After a few connection attempts, the car only successfully read me one message. Afterwards, the text message functionality on my i-MID was selectable, but clicking the enter button wouldn't do anything. Checking my phone, Hangouts was also frozen. The phone was telling me (via ringtone and notification popups) that I was receiving texts, but I couldn't read them until I disabled BT and force closed Hangouts.
Is this a common problem that we are all experiencing? Can any of you confirm or deny these ideas? Also, which messaging app is everyone using (I don't want recommendations, I want to know if this is Hangouts' fault or not)?
Click to expand...
Click to collapse
I can confirm that my car's Nav system is able to notify me and then read SMS messages from my hangounts app on my N5 without any issues (Toyota). I can also send SMS messags from the car (thru' N5). Works fine, everytime. So, I don't think it is a hangouts issue.

jj14 said:
I can confirm that my car's Nav system is able to notify me and then read SMS messages from my hangounts app on my N5 without any issues (Toyota). I can also send SMS messags from the car (thru' N5). Works fine, everytime. So, I don't think it is a hangouts issue.
Click to expand...
Click to collapse
I'm struggling with my Toyota... I have the Non jbl system with Nav. When I click on Bluetooth settings it doesn't give me MAP as an option to check (even tho I granted access to view messages) but I unpaired and repaired a few times and it did give me the map option and it still wouldn't receive my msgs

gmitch528 said:
I'm struggling with my Toyota... I have the Non jbl system with Nav. When I click on Bluetooth settings it doesn't give me MAP as an option to check (even tho I granted access to view messages) but I unpaired and repaired a few times and it did give me the map option and it still wouldn't receive my msgs
Click to expand...
Click to collapse
The message access option should have been there every single time (unlike what you described). I'd suggest deleting the pairing from the phone and the car, and to try again. If the problem persists, try to pair it to another car (Toyota or not) and see if it works with that. If it does, that means it is an issue with your car's system. If it doesn't (and the other car can pair to other phone's with message access properly), it may be an issue with your phone.

jj14 said:
The message access option should have been there every single time (unlike what you described). I'd suggest deleting the pairing from the phone and the car, and to try again. If the problem persists, try to pair it to another car (Toyota or not) and see if it works with that. If it does, that means it is an issue with your car's system. If it doesn't (and the other car can pair to other phone's with message access properly), it may be an issue with your phone.
Click to expand...
Click to collapse
Went and messed with my dad's avalon and it worked no problems with his on the first attempt (MAP was there and it asked and was granted access). Going to try to repair one more time with my car before I take it to Toyota.

gmitch528 said:
Went and messed with my dad's avalon and it worked no problems with his on the first attempt (MAP was there and it asked and was granted access). Going to try to repair one more time with my car before I take it to Toyota.
Click to expand...
Click to collapse
Kinda glad to hear that it is working ok with another car - but at the same time, I'm not sure how helpful the dealership will be (assuming the problem d1oesn't get resolved by re-pairing) - automotive firmware is basically written in stone - very hard to get them to fix it. They usually keep blaming the phone. Good luck.

jj14 said:
Kinda glad to hear that it is working ok with another car - but at the same time, I'm not sure how helpful the dealership will be (assuming the problem d1oesn't get resolved by re-pairing) - automotive firmware is basically written in stone - very hard to get them to fix it. They usually keep blaming the phone. Good luck.
Click to expand...
Click to collapse
Well you were pretty much right. They kept blaming my phone. So annoyed it doesn't work but not the end of the world. Maybe the Nexus 6 has a better shop

gmitch528 said:
Well you were pretty much right. They kept blaming my phone. So annoyed it doesn't work but not the end of the world. Maybe the Nexus 6 has a better shop
Click to expand...
Click to collapse
I assume you told them that it works with the Avalon - and they stuck with "it is your phone"... UGH! Funny how it works fine with one car, and not with another (even though both cars are made by same manufacturer). Yes, it must be using a different BT stack/hardware/software, but why not use the same one across the board? sheeeeeeeesh

Google Pixel No Sound issue

Guys, this issue has been pestering for a month now and I seem to have not found a fix for this yet. I first started to notice the problem with my phone when I was unable to attend the calls, the screen will usually get stuck or i will not be able to swipe up the green button during the call. Even if sometimes I manage to i will be able to hear the other person speak but I wont be able to speak to them. So sometimes once I restart the phone it will seem to work fine for an indefinite period of time and again it starts.
Then things started getting very bad, sometimes during normal device usage, the screen just turns to a monochrome black and white screen ( just as you see when there was no signal on older television sets). And when I switch to the bootloader screen, when I power the device on, I get a very thin green line for an instant on the screen and then the booting sequence starts.
I have made a lot of factory resets and stock image flashing, and by far I noticed one considerably situation, the times when the sound functions fine, the booting sequence where the 4 google dots animation appears and when there is no sound, the booting sequence gets stuck on Google and made by Google screen.
Other observations are during abnormal device behavior, no function related to sound will properly. To elaborate it, Google assistant wont work, videos cannot be played and even the system sounds wont be heard. I am open to suggestions here. Please let me know what can be done to test the phone out. FYI I know there is a problem with the Pixel microphone, but I am not convinced that its the exact problem. Please correct me if I am wrong. Thank you.

Sounds like a hardware defect. RMA if possible.
Sent from my Pixel using XDA Labs

It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.

That's the only way I suppose!...did you get the phone directly from the Google store?...are they accepting phones bought from a retailer?...since I am in Singapore now...Google support is next to nothing here...try contacting them but it's of no use...only when I get to India I will be able to go forward with the replacement!.....but the thing is .... yesterday...I updated the phone to Oreo and the audio stopped working completely....and after repeated switching between safe and normal mode....the speakers are working now...but the microphone is still busted.

This happened to me, I was given a replacement phone from EE UK

Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.

MK1207 said:
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
Click to expand...
Click to collapse
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did

ndiri said:
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
Click to expand...
Click to collapse
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!

MK1207 said:
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
Click to expand...
Click to collapse
well, its been almost an hour the phone wont turn sound back on.

Keep switching it to and out of safe mode...at some point ideally at least the speakers must start lest the microphone. Tried contacting Google about it and no response at all...mine started acting weird only for the past month...I suppose from the Aug months patch update....tried reverting it back to previous stock versions...but I suppose the damage is permanently done

When I contacted google, they told me to send it back to Canada and let someone there give it to google.. which won't happen in my case , my phone also started acting like this after Oreo beta . Now I will restart the phone whenever it happens to get it back working :/

The only reason I am still sticking to this phone is coz of it's camera. Planning to get back to India around December to get this fixed. Support for pixel in Singapore now is next to nothing since it wasn't launched here. I had no problem at all with the Nexus line up but this is kind of a disappointment.

Alaadragonfire said:
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
Click to expand...
Click to collapse
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround

MK1207 said:
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
Click to expand...
Click to collapse
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..

Alaadragonfire said:
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Click to expand...
Click to collapse
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?

MK1207 said:
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
Click to expand...
Click to collapse
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated

Alaadragonfire said:
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Click to expand...
Click to collapse
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?

MK1207 said:
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
Click to expand...
Click to collapse
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.

Alaadragonfire said:
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Click to expand...
Click to collapse
Planning to do just that....I may have better luck with a custom kernel...will post an update once I have flashed it.

I had been on the 8.0 beta for a while. Then got 8.0.
Though just 2 days ago, my mic was starting to have issues. Then yesterday, only my speaker phone would work.
Now I can't get any audio/mic except though Bluetooth (I've got a portable speaker with a mic, and Bluetooth on my car.
Contacted Google support. Will be getting a replacement on their warranty.
They didn't tell me this, but I did some searching, and apparently many of the pixels (mostly from the first 3 months of production) had an issue with the soldering of the audio codec. though usage, little bumps here and there, that soldering can get loose. Which explains why my audio and mic were spotty, and within an hour yesterday morning, all aspects of it stopped working.
So, it's a hardware issue.

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

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.