I recently updated to nougat on my s7 edge and noticed "disable absolute volume control" under developer options. As far as I can tell this feature never worked with any of my BT devices. Is this disabled by Verizon or just broken on my phone?
It's not just about your device, it's a widespread problem of Nougat. I'm facing same problem on Xperia Z5C. Try looking for some patches|fixes on github for any Nougat ROM.
nobody else has this issue with my phone? still not working for me...
does anyone have it working and can prove it?
Related
So when I bought my Nexus 6P I knew I was going to get the latest updates as soon as Google released them. I also expected to find minor bugs because we are getting updates much faster as well.
What I was not expecting is to both, bugs that make for a nearly unusable device and minor annoying ones. For my device the bugs that hit me hard are;
Max Volume Bluetooth Speaker Bug - Most bluetooth speakers are stuck in max volume mode and can't be turned down. Distorts the audio and creates a situation were you could blow out the speaker. Not all speakers are effected.
No LTE On Boot - Annoying to have but "fixable" by putting the device in Airplane mode. Otherwise no Data or SMS until you do and hope your phone doesn't reboot in you pocket while waiting for an important message.
No Phone Calls - You can't make or receive calls. As a result you can't check VM either. No amount of Airplane mode or rebooting will fix it. Neither will the phone service menu.
My concern here is that Google hasn't patched these bugs yet, even after releasing another update to 6.0.1 M. For now I'm fine with downgrading to 6.0.0M but I'm missing out on updates.
To add to insult any ROM build with the 6.0.1 source is effected by these bugs, so I can't even use most ROMs unless I find an older version.
I guess my main question here is this:
Is this normal? Does Google usually go so long without patching the bugs?
Seems really silly to have a phone, but not be allowed to make or receive calls at all and not be able to send SMS or email unless you do a few tricks first. It's a phone. Don't they test these things?
Disclaimer: I already know not all 6P or Nexus devices are effected. That does add to my confusion as they all should be the same exact device.
EDIT: I also wanted to add that when I got the device I could do all these things however even downgrading will no longer allow phone calls. Something is retaining.
Well that's weird mate. I'm on 6.0.1 and have none of these problems.
I was experiencing awful battery life after the latest update but clearing the cache has made a huge difference
Have you tried reaching out to Google? It would be helpful if you could share how you upgraded to 6.0.1? As mentioned above did you clear cache? The more info you can provide; the faster someone can help you.
The Bluetooth volume issue is the only one I have and only on one of my speakers. The others with fine.
Huh, ya 6.0.1 here too and none of these issues are present.
After playing Pokemon Go for a while my Nexus 6P accelerometer/gyroscope stops working. The phone doesn't auto rotate anymore and I can't use the AR option on the app for compass. The only way to fix this is by rebooting the phone. Anyone else having the same problem? I've found people with the same issue (Pokemon Go + Nexus 6P) on this thread on Google forums:
https://productforums.google.com/forum/#!topic/nexus/ytCwNnOJEaM
EDIT
I'm currently using the latest 7.0 Nougat Preview
Yes, but it's a Nougat problem. It's fine on MM and it'll probably be fixed for the release version.
Should be fixed in a future build
https://code.google.com/p/android/issues/detail?id=217918
ammmze said:
Should be fixed in a future build
https://code.google.com/p/android/issues/detail?id=217918
Click to expand...
Click to collapse
That's awesome! Thanks for the answer.
Not quite Pokémon Go related, but with the new August Security patch update from Google, anyone else experience Auto Rotate being slow to respond? As with previous patch updates, I didn't have this problem.
Looking at the 7.1.1 leak post, it seems that a few people have experienced this too but after both clean flashing and dirty flashing 7.1.1 over 7.0.0 I've noticed Dolby Atmos has stopped functioning correctly. I can turn it on and hear a difference but none of the in-app settings appear to work (although I can toggle them) and the equalizer doesn't move at all.
Has anyone had this problem and managed to fix it?
Kind regards
James
mvortex3710 said:
Looking at the 7.1.1 leak post, it seems that a few people have experienced this too but after both clean flashing and dirty flashing 7.1.1 over 7.0.0 I've noticed Dolby Atmos has stopped functioning correctly. I can turn it on and hear a difference but none of the in-app settings appear to work (although I can toggle them) and the equalizer doesn't move at all.
Has anyone had this problem and managed to fix it?
Kind regards
James
Click to expand...
Click to collapse
I had the exact same thing. I just flashed back to 6.0, mainly because of battery life which is slightly better. Atmos works again.
I also had the Wi-Fi icon in quick settings that would not turn off even though Wi-Fi was off.
A few too many weird things that indicated that 7.1.1 is not big free.
Neither is 6.0 of course. No battery stats? How did they screw that up?
Has anyone noticed this? I haven't messed with any power settings, is stamina doing this? I like to just keep Bluetooth on.
Thanks!
I have been having this issue too, and it seems related to either updating to 7.1.1 (which seems to have borked other phones bluetooth also) or setting up my LG Watch Urbane on it. The most annoying part is using a headset and having it drop in the middle of a call.
Since I have this phone stock and locked I can't update to 7.1.2 to see if that fixes it. Anyone with 7.1.2 having this issue?
@damage98 do you have a watch connected to it?
silentheero said:
I have been having this issue too, and it seems related to either updating to 7.1.1 (which seems to have borked other phones bluetooth also) or setting up my LG Watch Urbane on it. The most annoying part is using a headset and having it drop in the middle of a call.
Since I have this phone stock and locked I can't update to 7.1.2 to see if that fixes it. Anyone with 7.1.2 having this issue?
@damage98 do you have a watch connected to it?
Click to expand...
Click to collapse
@silenthero I do have a watch connected. Moto sport...
Super annoying to have bt just stop
damage98 said:
Has anyone noticed this? I haven't messed with any power settings, is stamina doing this? I like to just keep Bluetooth on.
Thanks!
Click to expand...
Click to collapse
I´ve started a thread in the sony mobile forum, maybe it could help if you would also give feedback on that thread...
https://talk.sonymobile.com/t5/Xper...act-even-in-latest-firmware/m-p/1211177#M1463
It seems that this known bug is fixed in android 7.1.2 but i´m not sure if we get that update...for me, sony service says that it´s a hardware fault but as far as i know a replacement device would also have that problem...
Not, rooted, located in US.
Before I did the OTA update to 8.1 last night, my external speaker worked fine, both for speakerphone calls, and media playback.
During my first use of 8.1 today, the external speaker is now so quiet (on full volume) that it's useless in all but the quietest rooms.
Calls on speakerphone are barely louder than if I just shut the speaker off. Watching Youtube on full blast is barely discernible in an average noise environment, and forget listening to music outside or in the car.
Anyone else experiencing this?
Same problem here
It's a official software bug. Most of the people who updated Oreo got this issue. If you want to use your phone use any other custom ROM available here. Otherwise need to downgrade to Nougat. If you can wait for another update from Moto to rectify this bug means bare with this volume issue untill Moto releases new update to fix this.
kingmari said:
It's a official software bug. Most of the people who updated Oreo got this issue. If you want to use your phone use any other custom ROM available here. Otherwise need to downgrade to Nougat. If you can wait for another update from Moto to rectify this bug means bare with this volume issue untill Moto releases new update to fix this.
Click to expand...
Click to collapse
Thanks for the feedback. Unfortunately I doubt Moto will ever release a fix for this.
I never bothered rooting this phone, I guess I am going to find out if its even possible, now that it has Oreo on it.
slimbobaggins said:
Thanks for the feedback. Unfortunately I doubt Moto will ever release a fix for this.
I never bothered rooting this phone, I guess I am going to find out if its even possible, now that it has Oreo on it.
Click to expand...
Click to collapse
Rooting stock Oreo is even easier compared to Nougat, because you don't need a custom kernel anymore. Still I would advise to use the new Loony Kernel or ElementalX for being able to use different RGB values if your device has screen retention problems.
Other observations from this OS "upgrade:"
My phone now struggles to stream Youtube to Chromecast... video/sound sometimes is choppy... previously no issues at all.
Sometimes the phone randomly decides Wifi wont work. Can flip the switch to the on position, but it still says "Wifi is off." Only recourse is to restart the phone.
Overall very disappointed. Can't wait until I get a chance to root and ditch this OTA update.