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] BT wakelock - Z3 never deep sleep

Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.

I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.

abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.

Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.

I thought im the only one having this bluetooth issues..

If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk

abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.

I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?

I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)

colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.

I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!

vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.

Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.

vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.

colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.

I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.

vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)

Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?

Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF

Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.

Us version of the Mate 9 start receiving Oreo

As per phonearena.com Mate 9 is starting to get update to Oreo
https://www.phonearena.com/news/Unlocked-Huawei-Mate-9-receiving-Android-8.0-Oreo-in-the-US_id102104
Wait is over

Android Central is reporting it too. Anyone get it?
I have checked mine several times and nothing yet

it's approved for update in Firmware Finder
Edit: nevermind, jumped the gun...only approved if you check without the imei.

As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.

dscline said:
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
Click to expand...
Click to collapse
What issues are you having?

audioman42 said:
What issues are you having?
Click to expand...
Click to collapse
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.

dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
Same here with bluetooth inconsistencies when connected to my car. I have resynched several times and sometimes it helps for a short while and other times no improvement. Sometimes I can control songs and other times not. Sometimes it shows songs and other times it shows connecting. Sometimes it shows the correct name of song and other times it freezes on a song title that is long gone. Even when deleting and resynching my phone, an old song title is displayed and not the same as being played. Total bummer as I use bluetooth music every time I get into my car. On recent update (360) which appears to be the same one they are releasing as OTA.

hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....

Still waiting. To be honest though, it's not even Oreo I want, I just want the dang security updates. April 2017 is wayyy too old.

dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
I've noticed similar Bluetooth problems. I stream in my car pretty often and through headphones at work, and at times I won't be able to skip songs via the receiver/headset. Since a reboot always fixes it, I've been doing preemptive reboots as I walk to my car in the morning to circumvent the issue.
I've had zero issues with Textra. If anything, it's working even better now than it did before - all of my MMS sending issues are gone. Apparently, though, this was less of a Huawei problem and more of a Nougat problem.
cross1989 said:
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Click to expand...
Click to collapse
Which region did you rebrand to? I was on 432 running a custom ROM for a while, but went back to 567 thinking that would solve my MMS sending issues. I want to rebrand, but I've heard that rebranded phones don't receive OTA updates because the IMEI doesn't match the region.
Thanks

I did not rebrand any thing, as I stated I don't buy state side phones, I buy original unlock phones directly from company (Amazon).. I have international version, MHA-L29C185... Now on oreo from Ota... Yea you loose Ota on those rebranding systems most of those require to unlock bootloader and twrp... That alter the system... If you want a good Huawei phone, buy international or China version off Amazon, yes both work in the states.

Just got my ota update today

Can someone who got Ota update check to see if any of the files on the FF app are giving an imei approval?
Mine still isn't and I didn't get Ota yet, so if it does for you and u got the Ota it may shed some light on whether the server shown on FF is directly linked to Ota files...

I just got the OTA update...downloading it now

kullum79 said:
I just got the OTA update...downloading it now
Click to expand...
Click to collapse
Where are you located??

shae23 said:
Where are you located??
Click to expand...
Click to collapse
I am in Chicago Central Standard Time... playing with the camera as we speak....

kullum79 said:
I am in Chicago Central Standard Time... playing with the camera as we speak....
Click to expand...
Click to collapse
Lool same location, no update, man Huawei is funny, oh well, guess it'll get here in its own time

It doesn't matter about the area it's being done in Bach's by imei .
---------- Post added at 09:11 AM ---------- Previous post was at 09:02 AM ----------
U can download it in ff but when it finishes download and install it won't verify because the it's has the imei in the download bricked one phone so I will wait for the ota I called huwaei to c about unbricking and the told me the date and time of the forced update voided the warranty

I got my Oreo update just a few hours ago, bought off Amazon, in KY, on T-Mobile

Oreo Update
I got my OTA update late yesterday. Haven't had it long enough to see if the battery life is better.

Bluetooth audio streaming problems after Oreo Update

Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?

When im paired up with the stereo in my work truck i noticed a pop every now and then.

stefilie said:
Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?
Click to expand...
Click to collapse
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?

ScottOverly said:
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?
Click to expand...
Click to collapse
Try factory reset, it worked for me. Good luck!

Yes, I'm having the same issue with bluetooth connection and the same Blue Tiger Elite. Just got off the phone with Verizon tech person he is thinking my headset is old enough technology that it won't stay connected.
Steve Phillips

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