I've just got a brand-new OP 6 last night. Everything works fine on this great phone. But there's this one glitch that's getting on my nerves:
I listen to music on Spotify with wired headphones (ATH-M50x). Songs either keep pausing or skipping to the next track while I'm walking. I've made sure to deactivate BT, activate pocket protection, and deactivate the equalizer, as some 5T users reportedly solved this issue in the same way. None of these methods have worked for me. Songs keep pausing and skipping to the next track like crazy. When that happens, I immediately take out my phone to see what's going on. Anyone with the same issue?
Related
I've noticed this since I bought my htc inspire 4G the phone (I had other issues before such as low battery life, vibration feedback simply not working, etc - I hard reset the phone and those went away, but this is back), and I'm wondering if it's my hardware, or the software.
Basically, if I'm listening to music (Pandora or the Music app), it'll randomly hit Next song - if it's the music app, it'll be a mish-mash of fast forward and next track. This is with the phone screen off or on. When it starts happening I turn the screen on and notice it jumping all over, and I've not touched anything. Additionally, while this is happening, voice dialer opens over and over after I close it, and sometimes it'll just start making a call to the last dialed/received number (which is making me a hit with all my friends).
Finally, I say possessed because this is not consistent. For example, I'm listening to Pandora now with no issues. However, the fact that I have to even worry about this happening again
You are using incompatible headphones. You didn't mention headphones but it explains everything. You need to use headphones that have a mic. These headphones have 4 gold contacts on the plug. Without a mic it only has 3. The big contact at the bottom is grounding out 2 connections causing your phone to switch tracks and make calls. Get correct headphones with a mic. You have to remember this is a phone and not a simple mp3 player.
I have been encountering this weird bug for the past few months across many different ROMs. When I walk to and from school, I'm usually listening to podcasts through my Meelectronics SP51P earbuds. After about 5-15 minutes of walking, I notice my podcast skipping forward. Sometimes, the currently-playing podcast will even change to a completely different podcast. Less frequently, my music player will begin playing music during the freak out.
Sometimes it stops after removing my headphones and blowing into the headphone jack, though the problem will start again about half the time.
I was using Google Listen for a while and just thought the program was crap, so I purchased Pocket Casts though I still had the problem. I have no idea what could be causing this...
Hitting various media controls on my smartwatch (previously Pebble, now Android Wear both via built-in media functions and Music Boss), my Bluetooth car stereo, or the lock screen, including play/pause, next, and back (or even turning off my car which should automatically pause playback) is incredibly unreliable for me.
I find that at MOST, half the time these buttons work as they're supposed to. The rest of the time there's a delay ranging from a couple of seconds to over a MINUTE. And they accumulate, so I can hit next, not hear any change, hit next again, and then a minute later my music will skip two tracks. Or I hit pause, think it didn't work, hit it again, give up, go to my app directly, pause it, and 30 seconds later it plays again, then pauses.
I find pretty much the only thing that tends to clear this up is restarting my phone, which is usually not convenient to do at the times I need this to work most (like while driving).
I didn't have this problem at all with Jelly Bean on my Nexus 4, and I feel like the problem was rare, if at all, on my 5 with 4.4 through 4.4.2. It was 4.4.3 that seemed to make it a severe and constant problem, and it's held through 4.4.4. And as noted, the problem transitioned from my Pebble to my Android Wear, and since the same thing happens with lockscreen controls, I feel confident it's my phone/OS and not the watch. I'm stock, rooted, FYI.
Any thoughts? I've done a ton of Googling and gotten surprisingly nowhere.
I've noticed this too. For me it seems to have started happen after I got my Android Wear watch, and didn't happen when I just had the phone connected to my car bluetooth. I wonder if having the phone connected to multiple bluetooth controllers at once is causing the issue ?
Interesting thought. Might explain why I was also experiencing it with my Pebble.
Tested this theory by connecting my car stereo through the aux jack instead of Bluetooth and disconnected my phone from its Bluetooth connection. No improvement. At first it was responding right away, which it does sometimes, and then the next time I tried to use it it took a good 30 seconds before my actions registered.
This has been happening to me for a few months. I find that the only reliable way to immediately adjust the playback controls is from within the app. Lockscreen, Bluetooth devices, notification controls, corded play/pause via headphones are all unreliable. But the attempts to play pause are all cumulative and with the aforementioned lag, even if I successfully pause from within the app. So I think I've paused the player, but a minute later it may start playing again. Really embarrassing at times. Not rooted, and switching default players hasn't helped.
Socold said:
This has been happening to me for a few months. I find that the only reliable way to immediately adjust the playback controls is from within the app. Lockscreen, Bluetooth devices, notification controls, corded play/pause via headphones are all unreliable. But the attempts to play pause are all cumulative and with the aforementioned lag, even if I successfully pause from within the app. So I think I've paused the player, but a minute later it may start playing again. Really embarrassing at times. Not rooted, and switching default players hasn't helped.
Click to expand...
Click to collapse
Glad I'm not alone, although disappointed you don't have a solution either. And yes, it's very embarrassing to try to show off this technology and have it fail, or worse have it fail at the wrong moment. Sometimes I get out of my car, walk into a building, and THEN the commands catch up and the music starts blaring from my pocket. Good thing I don't listen to Gangsta Rap.
I know Pixel 2 bluetooth problems have been discussed here and elsewhere ad nauseam, but I honestly haven't found anyone else experiencing the problem I'm having. Or really even close. None of this was an issue with my Nexus 6P, which I just replaced.
First problem: Audio programs mute between tracks. The phone thinks it's playing them, but it isn't. Take Pandora. A few songs will play fine, then one will end, and suddenly it'll go mute when the next song starts. I'll notice no sounds playing, and I'll look down to see it think it's playing, but with no sound. If I pause and hit play again, the sounds start up until the next song, when it does the same thing. This happens with every audio program I've tried EXCEPT Google Play Music, which works fine. It also sometimes works for 4-5 songs before tanking.
Second problem: notification noises suffer the same fate. I'll have Google Play Music going (which works), and it'll just cut out for a second). That's the notification buzz, which silences the music but doesn't actually play anything. Obviously I can't use the play/pause test to see if that fixes this.
I'm using Soundpeats Q16 true wireless. I unfortunately don't have much else with which to test this. I'd blame Soundpeats, but they worked great on my 6P, and the bluetooth problems with the P2 make me think it's not on Soundpeats here.
I've messed around with the Developer options, and I THINK that setting the Playback Quality to anything steady (330kbps, 660kpbs, or 990 kbps) fixes it. The problem is that that, and the other Bluetooth developer options, all reset on me almost immediately, so that's tough to prove. I have also tried messing around with Tasker, whose sounds also wind up muted.
So one question I'd have would be: is there a way to make those developer options stick?
Second question would be: anybody else in this boat?
I have tried both re-pairing and factory resetting the headphones, several times.
No, I'm not using the Oreo beta.
Yesterday I had the strangest issue happen. While I was driving (Ford Sync 3), I was streaming Spotify via bluetooth and all of a sudden the sound quit coming through my car and started playing through the phone speaker. I checked, bluetooth was still connected. I could still pause/play, skip songs, etc through my car, so I have absolutely no idea why it quit playing. I skipped a few more songs and eventually it decided to start coming through my head unit again. It's happening literally every time I get in the car now.
No issues with the gfs iPhone 7+. I did notice that while all of that was happening (I went to go record the issue) that my video record button in the camera app was greyed out and wouldn't allow me to take video. After the sound resumed through my car, it would let me record again.
Any ideas?
Just wanted to bump this to figure out if anyone had any input. I noticed that after I get out of the car, if I try to adjust ringer volume, it is changing "in call volume" rather than notification volume. This ONLY happens after the bluetooth issue happens. I'm not sure what's going on here.