Okay guys so I have a Moto X and an HTC Stereoclip.
Upon first pairing everything is fine and dandy. Volume levels are as expected. Once I disconnect when I get to the parking lot at work and reconnect when I get inside work the volume is SUUUUUUPER LOW!!! The only way to fix this is to go to my bluetooth settings on my phone and "forget" the HTC Stereoclip. On the initial pairing everything is okay again. There is no way I'm going to keep re-pairing it the long way each time I want to use the stereoclip.
The problem is with the phone though. As I have a Galaxy Note 3 that I use with the stereoclip as well but it has no volume issues pairing and re-pairing.
Do I have a bad unit?
I've noticed on mine, occasionally, the volume will be super low when I get back in my car. As soon as the song changes, or any other notification sound happens, the volume immediately jumps back to where it was (full). I haven't figured out exactly how to reproduce the issue, but since it only happens very rarely, I haven't spent much time on it.
Had the same thing sometimes on my Note 2. I'm guessing it's a bug, but I'm not sure what causes it, nor have I ever been in a position to really troubleshoot it when it happens. By the time I could troubleshoot, I forget about it.
Related
My volume keeps getting set to silent. As a result, I get no notifications of anything going on with my phone.
A little background first:
This is my second HD2. I returned my first but decided I really liked this phone after all.
I do NOT have BsB tweaks installed. I think there is an option to kill ringer based on calendar with this app.
I installed PocketShield thinking it would lock the screen when placed in my pocket. The thought was that the volume rocker was getting hit before it locked if I forgot to manually lock the phone. Didn’t resolve my issue.
Last night I installed VolumeX. This allowed me to remap my volume rocker buttons. At least now I know it’s not the volume rocker getting bumped.
So this morning on my drive into work it happened again. I checked the phone before I left and it was in vibrate. When I got to work it was in silent. The only thing that happened on the drive was that it attached to my car Bluetooth. But I’ve had this happen on multiple occasions without the Bluetooth piece.
Any thoughts on why this might be happening or things to check would be appreciated.
You aren't hitting vibrate then setting the phone down immediately on it's face are you? I've found that setting it on it's face before it's locked launches things...
I do believe it's the bluetooth that'll be doing that. Connecting and disconnecting bluetooth headsets and car kits changes the sound profile - annoys me too, but I'm pretty sure it's standard for WinMosince my Omnia and Titan did the same thing IIRC.
Please tell me if this is the wrong place for this, but i figured I'd post my working, successful android setup on my HD2.
I am using Chucky's android ROM, 7/23 zimg, but i replaced his radio with 2.12.50.02 and whilst in windows i disabled the sleep timer after 1 min thing. I have had it on for 48 hours now, -amazing- battery life, even with a live wallpaper (mario ftw) never got a SoD, it did give me a gsod the first time i booted, but popped batt out, and rebooted just fine. Like i said been going a solid 48 hours now, great battery, no lag, no sod, phone calls are kind of quiet, which sucks for me, i work in a loud place. So take this how you will, but i'm extremely satisfied with this setup.
I have been having an issue with several builds, radios and wm roms, and now decided to try something.
The Lock/End key was not waking up the device on first touch, sometimes i had to press home, some other times pressing the End key several times, or slide down an imaginary lockscreen in order for the screen to come back and respond as it should.
So.....
I thought I should install AEB plus, or AE button, whatever... to unbind all hardkeys, rather than remap soemthing and reboot... the end key seems to be working now as it should, waking up the device immediately, rather than turning on the black screen. Yay!
Try it and let me know how you get on. Just tried it again, and feels great not having the annoying waking up issue. Hope it keeps this way.
Also, I can confirm that the annoying issue where people you call hear a lot of background noise (mic gain issue), is definately fixed for now using the wired headset that comes with the phone.
Tried connecting some other headphones without microphone and that didnt work. Havent tried using my bluetooth headset to make a call, but in theory it should work too. At least it works for music
Hope this helps some people out there.
Loving the Desire V5
Kudos for everyone involved.
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.
So this has happened maybe 3 times now. I did apply the latest OTA and did a hard reset so everything is fresh. I have had this phone lock up on a few occasions now. Last week I had the hardware keys quit responding. The power button and one of the volume rockers just didn't work. I had to download an app from the play store to get the reboot menu to pop up so I could reboot it. Keys were fine after reboot. The few times it has locked up, the phone makes a loud steady buzzer sound then will reboot and everything is fine. The screen will freeze along with the buzzing sound for maybe 10 seconds before rebooting itself. One time I was playing a game, the other was on an incoming wi-fi call it just locked up both times it played the buzzing sound through the speaker and did reboot itself. Starting to think it may be a hardware problem with maybe the PBA board. Only other thing I can think that might be messing it up, I do use adgaurd as a local VPN on this device.
Anyone else have such issues? I don't want to send it into Samsung just to have them tell me everything is fine if it's a software problem causing it. I have already hard reset so at this point I guess I could try to disable adgaurd to see if that helps. Anyone else have any similar problems with this phone?
Whenever I connect to one of my Bluetooth devices it shows that it's "Connected to xxxxx" in the secondary screen.
However, after I disconnect from the Bluetooth device it still says its connected in the secondary screen and the secondary screen just hangs there frozen saying its connected. I can only get rid of it by restarting the device.
Anyone else having this issue?
I'm experiencing this issue. I think it started happening after applying the latest update.
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
I have this and all kinds of BT issues with my car.
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
McNutnut said:
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
Click to expand...
Click to collapse
So it's not just me having bluetooth issues lately. I was getting ready to drop by AT&T because of all the problems it''s been giving me lately connecting to things on bluetooth...
Mine has recently started doing the same thing with second screen stuck on connected to vehicle Bluetooth. I do remember updating recently so I am unsure what cause this issue. I am using stock with ATT
peekeesh said:
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
Click to expand...
Click to collapse
I tried this trick and it only works temporarily. After an hour or so the same connection message will appear even though I'm not connected. So annoying. Come on LG! I like their devices but there is always some annoying issues with their phones.
Are you guys also experiencing general notification issues?
Example, I click on a Twitter or Kijiji notification and the app won't open or I can't respond within the notification shade any more.
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Ever since I upgraded to 10K from 10J on T-Mobile it has started doing this. Once I am connected I never have a problem with Bluetooth but connecting has been inconsistent ever since upgrading. My car stereo for example used to connect automatically now to get it to reconnect I have to turn off the stereo and the Bluetooth radio on my phone and then both back on @ same time otherwise I have to manually connect through the phone BT menu
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
McNutnut said:
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Click to expand...
Click to collapse
This seems to have fixed it for me! I had the same issue after updating my phone to the latest build.
thisisjason said:
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
Click to expand...
Click to collapse
Same exact issue. It only seems to happen to my car stereo since I upgraded to 10K. But my other speakers and headsets 99% of the time it will connect by itself.
Same issue here. Super annoying. Appears to have shown up around the same time that all my notifications stopped working.
I've been having the same issue. I use Car Home Ultra, and noticed that it was very delayed starting, and would start randomly even after leaving my car/disconnecting bluetooth. I thought it was a problem with that app, but now it appears it's that the phone is delayed in notifying of bluetooth connect/disconnect.
I constantly have the "connected" notification taking up the second screen until I reboot.
I am experiencing this aswell, and , when connecting to my SYNC 3 in my Ford Focus, it says connected, but it isn't. If someone rings me, the hand set rings.
It seems to be the initial handshake, if the phone's bluetooth is off when i turn car on, then i turn blutooth on and select "sync 3" it's all good, but if bluetooth is already on , and i switch car on , i get the message on the radio it's connected to my phone... but i cant access contacts or messages ( even though they are ticked in bluetooth menu )...
lucky for the 2 year warranty...
Disabling the Google app has fixed this issue and fixed my push notifications. Not ideal but doesn't appear any other answer exists.
Anybody have any updates on this issue? I have been having the connected message showing more frequently to my vehicles. I have been turning off second display and back on to remove. Thanks for the suggestion Adam about disabling Google app but like you said it is not ideal.
So on Verizon they just pushed a system update. Post update, I enabled Google app, and everything appears to be working great thus far.
I don't remember when but the issue just kind of went away without any action on my part. Maybe it was an update?