Hello guys,
Seems like my N6 started to fry earpads, already lost 2 pair, one was completely new and after i connected it the second time, it started working bad.
The speakers i connect, shut down and i have to reconnect power. after few attempts it connects well.
Also, when connecting earpads, it always recognizes as an aux device.
But when i connect speakers, i must insert it realy realy slow, and before getting to the end, get the icon as for connected Aux device, and then push all the way in (takes about 5-10 attempts and overall atleast half a minute or a minute to connect), which is weird, beacause it works, it just doesn't recognize any speakers as an Aux device so easily, and earpads are recognized just fine?
Related
Hello everyone! I picked up a Nexus 6 the other day, and I have ran into a very interesting audio problem with it. I like to use it in my car to listen to Spotify. However, for some reason, when I plug in the cable, it does not always detect that the cable is plugged in, and still outputs sound through the phone speakers. I originally thought this was the aux cable I was using, and I replaced it, but it was still happening. I was messing with it a bit more today and it seems that if I plug it in slowly, it will play out of my car just fine. However, if I plug it in normally, it is like it doesn't see the cable at all. This does not happen at all with other systems at all, be it other cars or home audio gear. It also does not happen with my deck and a different phone (I tested it with my old One M8). Currently, I am using SoundAbout to force it to output to the headphone jack before getting in the car, but this is getting to be a bit of a pain to remember to disable it each time I take my phone out. Has anyone else ran into a similar issue? Does anyone have any suggestions?
My phone seems to have touchy connection with the 3.5mm Jack. When I plug it in in my truck it won't hold a connection. If I'm using headphones when I bump the phone or set it down it pauses and if I tap the back near the top again it'll play. Sometimes with the cord in Google Now opens when the back gets tapped. I hear a small rattle around the area too. Not sure if it's related. Is this some stupid accessibility feature? Help? I just got this phone yesterday
smithy31698 said:
My phone seems to have touchy connection with the 3.5mm Jack. When I plug it in in my truck it won't hold a connection. If I'm using headphones when I bump the phone or set it down it pauses and if I tap the back near the top again it'll play. Sometimes with the cord in Google Now opens when the back gets tapped. I hear a small rattle around the area too. Not sure if it's related. Is this some stupid accessibility feature? Help? I just got this phone yesterday
Click to expand...
Click to collapse
I know this thread is kind of old but did you ever get this issue figured out? I'm experiencing the same thing. I even disabled the Google search app hoping it would fix it, and the Google voice search prompt no longer pops up, but it still pauses and skips tracks with any light bump (at least while using Spotify).
It's very annoying and even kind of dangerous that I have to keep messing with it while I drive. Thanks for your time.
Sent from my HTC Desire 626s using Tapatalk
Surj138 said:
I know this thread is kind of old but did you ever get this issue figured out? I'm experiencing the same thing. I even disabled the Google search app hoping it would fix it, and the Google voice search prompt no longer pops up, but it still pauses and skips tracks with any light bump (at least while using Spotify).
It's very annoying and even kind of dangerous that I have to keep messing with it while I drive. Thanks for your time.
Sent from my HTC Desire 626s using Tapatalk
Click to expand...
Click to collapse
It is very annoying and no I really haven't found a solution. I now only use headphones when I'm sitting still. I have found that some cords seem not to be effected by this problem but I'm not sure why. I have tried different brands and styles to no avail. The only thing I ever read about this was that on M8s people put rubber o- rings on their headphone jacks because it was shorting on the metal housing. Obviously not the issue here because the 626s is plastic, but perhaps worth a try? Let me know if you find a solution
I can tell you I don't have this issue. I am using some headphones that came with my LG 8 years ago lol and an aux from the dollar store. Haven't tried anything else.
I have some trouble with my headphone/aux port too, but not quite like what you all are describing. I'm also using one of the AdvancedStock images from Sandix, so I wasn't certain if that had something to do with it (although I doubted it). I have a cheap but sturdy aux cable in my car that connects to my phone (this cable worked flawlessly with my last phone). When I plug it in, the phone recognizes a cable is plugged in, displays the right icon in the notification bar on the top and the sound works properly (going to the car) for a few seconds. During this time I hear some clicks passed through from the phone. After a few seconds the clicks stop and the phone changes back to as if no cable is plugged in (no icon, sound goes out phone speakers). I then have to unplug the cable and re-plug it back in to repeat the process. Finally after 2-4 tries it sticks and the aux cable stays working. At no point is the connection touchy; in that if I move the phone, shake the cable, whatever, the connection stays the same. I recently learned if I plug the cable in slowly, the phone things I have a headset with a microphone plugged in (this is not that kind of cable; it does not have the third microphone connection). It still does the clicks thing, but when it stops, the aux connection is still working fine, every time. I have not tried it with a normal set of headphones/earbuds yet or an actual earbud-with-mic set.
Noticed with case seems to not do it as much. With mine I have to twist cable to get it to work. There seems to be certain spots that it stays playing but sometimes finicky
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
My XZ1 Compact's headphone jack suddenly stopped detecting any connection. I've tried cleaning out the port, shaking in case there's any dust, and blowing into the port with an air compressor to try removing the dust. Restarting the phone does nothing. Beforehand all I did was unplug my headphones. This is the third time it's happened to my phone since I got it in January. The previous two times it happened it fixed itself after about ten minutes. This has been ongoing for over twelve hours.
Any help would be greatly appreciated.
https://streamable.com/d2c1i
CMT 1412-4444 'Fours' said:
My XZ1 Compact's headphone jack suddenly stopped detecting any connection. I've tried cleaning out the port, shaking in case there's any dust, and blowing into the port with an air compressor to try removing the dust. Restarting the phone does nothing. Beforehand all I did was unplug my headphones. This is the third time it's happened to my phone since I got it in January. The previous two times it happened it fixed itself after about ten minutes. This has been ongoing for over twelve hours.
Any help would be greatly appreciated.
https://streamable.com/d2c1i
Click to expand...
Click to collapse
Make sure that you have registered you phone with Sony, then call support and they will get you to try some fixes. They will ask you to repair it with PC compainion. Call them back and say that's not fixed it and they will give you an address to send the phone to. The last time I sent a phone back it was with me again in 5 days all fixed and cost me nothing.
I had the same problem in my Z3.
The Sound About app gives you a workaround, it let's you manually change output.
seanp25 said:
I had the same problem in my Z3.
The Sound About app gives you a workaround, it let's you manually change output.
Click to expand...
Click to collapse
I have the same issue as OP, but if I use other ear/headphones or use a 3.5 extension cable and original earphones that's having issues, the audio routes to the headset.
I couldn't run the "Sound About" app, it just constantly crashed on me on after installing it. I used another app called "audio router" and it does the same functionality. I can get audio to route to my original headset that wouldn't work but my microphone does not work and then making phone calls the phone's speaker wouldn't work but the headset would get audio but the phone uses the mic on the phone instead the headset.
Is this hardware issue? It sounds like software to me, because the phone does work with other headset/headphones at least the ones I've been testing, like the Sony headset that came with the phone and a broken headset where the right channel didn't work these two work just fine.
hi guys
I'd like to ask, if you got some idea what could have happened. Out of the sudden, my wired ear plugs/head set stopped working. Tried with other devices, with the adaptor -> working. When I plug in using the adapter, there is no head phone shown on the display. BT was ff, connecting to a computer works, charging too. ONLY the ear plugs are not working with the Oppo... strange somehow, right ?
ANY ideas ?thanks in advance, FrankOppo