Hi!
When listening to music with my earphones connected, my milestone sometimes stops playing. Just like when you pull out the earphones. But they are connected, it just stops playing. I can resume by pressing the headset button. It cant be a problem with my earphones since ive already tried several different ones.
Does this problem occure to someone else? Solution?
Ty!
Well, it's going off becasue it looses contact with earphones.
Mine does the same thing, my guess is screwed up jack in milestone.
It happens only in the pocket/when phone can be touched by something, right?
yes.
so it seems like a hardware issue, right?
I had an issue with a New Potato Tunelink and choppy audio (I have a thread in here somewhere).
I bought a Kinivo BTC450 Bluetooth Hands-Free Car Kit and it does not suffer from the same audio problems, it sounds great... when my phone isn't rebooting.
The only time my phone reboots is in the car. I've disabled Active thinking it might have something to do with that, but no. If I turn off BT the phone doesn't reboot. There is something with my VZW MX and this Kinivo paired together that creates a situation where it unexpected and randomly reboots.
This morning it rebooted almost immediately after connecting. Sometimes I can manipulate the controls, pick a song and start playing it and it will reboot shortly thereafter. Other times it won't reboot and will start working until I go to skip to a song or something. There is no pattern other than BT and this phone hate eachother.
It's frustrating because I don't know when it will reboot. There are no options that I can see to try at this point other than look for something else or plug a stereo miniplug into the MX, which I'm not a fan of doing.
I've not done a factory reset due to the time and inconvenience of getting it all setup again. I've not tried to have VZW replace it.
Any ideas?
Well, a factory reset did not fix this problem.
ShanMan14 said:
I had an issue with a New Potato Tunelink and choppy audio (I have a thread in here somewhere).
I bought a Kinivo BTC450 Bluetooth Hands-Free Car Kit and it does not suffer from the same audio problems, it sounds great... when my phone isn't rebooting.
The only time my phone reboots is in the car. I've disabled Active thinking it might have something to do with that, but no. If I turn off BT the phone doesn't reboot. There is something with my VZW MX and this Kinivo paired together that creates a situation where it unexpected and randomly reboots.
This morning it rebooted almost immediately after connecting. Sometimes I can manipulate the controls, pick a song and start playing it and it will reboot shortly thereafter. Other times it won't reboot and will start working until I go to skip to a song or something. There is no pattern other than BT and this phone hate eachother.
It's frustrating because I don't know when it will reboot. There are no options that I can see to try at this point other than look for something else or plug a stereo miniplug into the MX, which I'm not a fan of doing.
I've not done a factory reset due to the time and inconvenience of getting it all setup again. I've not tried to have VZW replace it.
Any ideas?
Click to expand...
Click to collapse
I've experienced the same thing, but only twice and I connect to bluetooth multiple times per day in both the car and a standalone headset. I can't see any pattern, but it would certainly be nice to know how to prevent it.
I was having trouble with random reboots and I think it was the Updater app running in the background that may have been causing it. I saw that app running, went to Settings and checked for updates (obviously no updates yet). Ever since then, no random reboots. I use Bluetooth every day with a headset and Car audio device. BT working way better than any CM ROM I ran on prior devices.
Sent from my Moto X using xda app-developers app
Hi,
After last update I got problem with listening music through bluetooth devices speaker/headphones. Everything plays fine until got my screen on, turn screen off and music stutter, pause. It's not joy to listen any more. No problem when on 4.1.2 so thing new software problem.
Does anyone struggling as well with that?
I can't be the only one experiencing this. So here's the issue, I connect my phone to any Bluetooth speaker and it plays fine. After some time of course the screen locks. I go to wake my phone and it stops playing on the speakers and instead starts playing on the phone instead. Meanwhile, radio in the car still shows it's connected. Even pushing next on the player moves to the next track. JBL Flip, wake up phone audio stops on speaker continues on phone. Motorola Bluetooth headset, same thing, wake up phone audio comes out of phone.
Why in the world would it do that?! Didn't do that with the Note 3.
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.