Related
Hey guys,
Have searched a while, but found no solutions for this, so here goes.
Have stock Galaxy Nexus with ICS 4.0.1, build ITL41F, installed Google Music v4.0.9 (with online sync).
Music is synced with google's online music service (even though I'm in UK, worked-around US-only restriction), and plays nicely when the screen is on. Once I switch the screen off (press power button), one of two things happen:
- if sampling rate of a song is below 48,000 Hz -- everything continues as normal.
- if sampling rate is 48,000Hz and up -- every one/couple of seconds music stutters, and jerks. Feels like I'm listening to dusty ol' record!
The 48kHz part is my theory, compared a few mp3s that stutter and some that don't. This seems to happen irrespective of bps rate and other parameters (albeit haven't checked all).
Few people on the forum with similar symptoms (on other phones) suggested it has something to do with cpu throttle during sleep, and that by forcing it to higher frequencies during sleep this could be solved.
Installed setCPU (which required rooting) and forced phone to 1,200MHz in sleep as a trial, and the songs still were stuttering.
Anyone with a similar experience?
Prime suspect would be google_music.apk which is in beta i believe, and... well, i guess then I'm out. What do you guys think? Any idea what might be causing this?
This is my first android phone, so I'm not sure even how I'd go about submitting a bug, if that's indeed the beta version of music at fault here. Any pointers?
Ta,
Dan
omgrtm said:
Hey guys,
Have searched a while, but found no solutions for this, so here goes.
Have stock Galaxy Nexus with ICS 4.0.1, build ITL41F, installed Google Music v4.0.9 (with online sync).
Music is synced with google's online music service (even though I'm in UK, worked-around US-only restriction), and plays nicely when the screen is on. Once I switch the screen off (press power button), one of two things happen:
- if sampling rate of a song is below 48,000 Hz -- everything continues as normal.
- if sampling rate is 48,000Hz and up -- every one/couple of seconds music stutters, and jerks. Feels like I'm listening to dusty ol' record!
The 48kHz part is my theory, compared a few mp3s that stutter and some that don't. This seems to happen irrespective of bps rate and other parameters (albeit haven't checked all).
Few people on the forum with similar symptoms (on other phones) suggested it has something to do with cpu throttle during sleep, and that by forcing it to higher frequencies during sleep this could be solved.
Installed setCPU (which required rooting) and forced phone to 1,200MHz in sleep as a trial, and the songs still were stuttering.
Anyone with a similar experience?
Prime suspect would be google_music.apk which is in beta i believe, and... well, i guess then I'm out. What do you guys think? Any idea what might be causing this?
This is my first android phone, so I'm not sure even how I'd go about submitting a bug, if that's indeed the beta version of music at fault here. Any pointers?
Ta,
Dan
Click to expand...
Click to collapse
That, is weird - because I am facing this with Winamp so I've switched to Google Music to play my music.
Does anyone else face something similar?
Can you do me a favor and play something you know that stutters, and then try it over a bluetooth connection.
I'm curious if this is also related to the static I get when the screen is off and output is analog outputs - digital (bluetooth) works fine.
same here with poweramp... switched to googlemusic... now i have only stutters over the phone speaker..
Same thing happen to me with google music and pandora. Thought it was the connection.
Sent from my Galaxy Nexus using xda premium
I get the same using the Music app (have WinAmp but doesn't seem to integrate with the lockscreen so don't use it) as soon as the screen goes off (either timeout or manual) you can hear the music slow down and start to stutter, tap the power button, screen comes on and music goes back to normal.
Have noticed it's not all songs, but have't looked into the differences between those that do and those that don't.
Are these locally stored songs that this is happening on? So far so good here but I have been streaming from the Google Music cloud.. I wonder if the CPU is struggling during the underclocked sleep condition with local files that are high bitrate...
Mine are local files, not tried from another source.
I've used both, streaming from Google cloud, and when songs are available offline in the music app -- still stuttering. Haven't tried any other method though.
As for trying to stream over Bluetooth, haven't got any speakers/earphones that could receive the stream at home. Going to try my luck with a local pcworld, if they let me.
I haven't had any problems with Google Music stuttering while the screen is off, but I have had it crash frequently while listening to music and multitasking. I experienced a similar problem with Rhapsody as well.
http://forum.xda-developers.com/showthread.php?t=1379600
Pyrotechnic said:
I get the same using the Music app (have WinAmp but doesn't seem to integrate with the lockscreen so don't use it) as soon as the screen goes off (either timeout or manual) you can hear the music slow down and start to stutter, tap the power button, screen comes on and music goes back to normal.
Have noticed it's not all songs, but have't looked into the differences between those that do and those that don't.
Click to expand...
Click to collapse
totally true! thought my phone was a lemon at first.luckily i didnt return it.
yep having the same exact issue. on speaker its just fine. when i plug in headphones or aux to car stereo and screen goes off it stutters / skips or whatever you want to call it.
Turn the screen on and its fine. However doesnt happen to all music. This was streaming from google music for me.
I'm pretty positive you guys have same exact problem as many other people. So far no one has take my suggestion of playing those same songs that stutter, and play them over bluetooth. I bet you don't get any more stutters. I think it has to do with analog outputs vs digital. To output analog, the phone has to use the DAC (digital to analog converter). When it outputs over bluetooth, there is no conversion, and the music is in digital form and transmitted in digital form
If someone can try this I would appreciate it. And you'd be helping everyone find a common denominator in this problem.
Also be sure to star this bug on google code http://code.google.com/p/android/issues/detail?id=22444#c6
Can someone post an mp3 this is happening to them with? I have a ton of them and I have not seen this problem yet.
Sent from my Galaxy Nexus using Tapatalk
[hfm] said:
Can someone post an mp3 this is happening to them with? I have a ton of them and I have not seen this problem yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Didn't I PM you a link the other day? I thought it was to you. I didn't click the box to save it to my sent box so I can't just look it up :[
Circling back. I recreated the problem with luxferro's 48KHz mp3. Seems whatever happens on this phone to play mp3 with the screen off cannot handle that sample rate. Any 44.1KHz mp3 works fine.
Sent from my Galaxy Nexus using Tapatalk
There was another thread like this. The current workaround is to enable the Equalizer for Google Music. You don't have to actually use it (leave it on default) but this solves the problem.
Sent from my Galaxy Nexus using XDA App
I guess with the eq on its forcing the CPU to get involved even when in low power mode. Unfortunately I believe that was causing other issues with crashing. Since I don't use 48KHz mp3 I'll leave it off.
Sent from my Galaxy Nexus using Tapatalk
For poweramp try settings... Audio engine.. Advanced tweets and change the audio buffer size.
Sent from my Galaxy Nexus using xda premium
Having the EQ turned on seems to work, just set it to flat and turned the 3d effect down. Guess it'll use less extra battery than using a 'keep awake' app like I was doing.
So I can't figure out for the life of me which one of these is really the problem. When I play google play music on my chrome cast it plays for a minute or two, then the screen times out, and then it stops. I've tried resetting my router, resetting the phone, resetting the chrome cast, but it seems like nothing works. On my galaxy s3 running cm 10 I had no issues what so ever. Is anyone else experiencing this issue? What suggestions do you have? I know that this is a software issue, I'm just trying to figure out from where and who. Thanks for your help.
EyeAndroid said:
So I can't figure out for the life of me which one of these is really the problem. When I play google play music on my chrome cast it plays for a minute or two, then the screen times out, and then it stops. I've tried resetting my router, resetting the phone, resetting the chrome cast, but it seems like nothing works. On my galaxy s3 running cm 10 I had no issues what so ever. Is anyone else experiencing this issue? What suggestions do you have? I know that this is a software issue, I'm just trying to figure out from where and who. Thanks for your help.
Click to expand...
Click to collapse
It's a Note3 WiFi issue afaik. It's solid on my S3 as well, as long as the WiFi's steady, but my Note3 can only play 5 to 10 songs on avg before dropping out of the playlist. This is probably due to the Note3 incorrectly thinking your WiFi is inconsistent (forgot what the actual dialog warning says). The next TouchWhiz is supposed to fix this along with WiFi calling.
The only way to fix it before the update is to have a WiFi AP in the same room as your TV so there's no question about signal strength.
Software, huh. Yea I figured. I haven't really used touchwiz ever and this is my first experience. Haha well great. What's weird is that my wife's note 3 doesn't have any issues with this? The other night I was successful in streaming multiple songs with the screen off.
Well either way, I really wish Samsung would fix these issues before they release the top of the line phone. Thanks for your input.
zmore said:
It's a Note3 WiFi issue afaik. It's solid on my S3 as well, as long as the WiFi's steady, but my Note3 can only play 5 to 10 songs on avg before dropping out of the playlist. This is probably due to the Note3 incorrectly thinking your WiFi is inconsistent (forgot what the actual dialog warning says). The next TouchWhiz is supposed to fix this along with WiFi calling.
The only way to fix it before the update is to have a WiFi AP in the same room as your TV so there's no question about signal strength.
Click to expand...
Click to collapse
I think I just had a major breakthrough!
Tonight I was looking at my wife's Galaxy Note and I wanted to see why hers was working and mine wasn't. So I went through all of her settings on her google play music and it looks like the difference was hers was on stream at normal quality and mine was on stream at high quality.
So I matched it to hers and my phone was playing all tracks flawlessly. I wish I could broadcast this to the community and everyone else has had this problem but I believe that would fix the issue.
My theory is the note 3 already has wifi issues, showing that it has a weak signal. If you stream music at a lower bandwidth it seems like it wouldn't struggle as much. So that's why I think it works. Hope this helps anyone else thats looking at this.
EyeAndroid said:
My theory is the note 3 already has wifi issues, showing that it has a weak signal. If you stream music at a lower bandwidth it seems like it wouldn't struggle as much. So that's why I think it works. Hope this helps anyone else thats looking at this.
Click to expand...
Click to collapse
That's nice, but... the difference in quality is noticeable. I always enable high quality too (for 320kbps)
Sent from my SM-N900T using Tapatalk
zmore said:
That's nice, but... the difference in quality is noticeable. I always enable high quality too (for 320kbps)
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Right, and most audiophiles like you and myself usually do that right out if the box and that's why it doesn't work. I'm OK with listening to a lower quality of music as long as it streams. I don't know about you but it's super frustrating for music to start & stop even if it is
high quality. I'm okay with compromises.
EyeAndroid said:
Right, and most audiophiles like you and myself usually do that right out if the box and that's why it doesn't work. I'm OK with listening to a lower quality of music as long as it streams. I don't know about you but it's super frustrating for music to start & stop even if it is
high quality. I'm okay with compromises.
Click to expand...
Click to collapse
That would be fine if it works, but I tried this and it still doesn't work without stopping. I tried all the wifi settings changes mentioned. It still stops on my Note 3 but not my OG Nexus 7. I think only a software update is truly going to fix this issue permanently.
EyeAndroid said:
Right, and most audiophiles like you and myself usually do that right out if the box and that's why it doesn't work. I'm OK with listening to a lower quality of music as long as it streams. I don't know about you but it's super frustrating for music to start & stop even if it is
high quality. I'm okay with compromises.
Click to expand...
Click to collapse
It's taking forever to get an aosp rom for this phone. Sadly I'm thinking the first one will be a buggy kit Kat rom.
I have noticed since I upgraded from GS3 to Note 3 that when I am streaming music to my car stereo the audio will skip or stutter. The song continues to play but the audio cuts out for anywhere up to a second or two. Has anyone else seen this or resolved it?
I have seen some posts that say turning off WiFi fixed it but I still get the skip, if a little less frequently with WiFi turned off.
It seems to go away if I set the developer options to keep the screen awake while charging. So it seems like the CPU clock may be too low during sleep to maintain everything else it is doing as well as audio streaming.
Any feedback is appreciated, thanks!
This happens to me too sometimes. It seems worse when I first start streaming & then it calms down a bit. But it still occasionally skips. I experienced this on my note 2 as well though, so I don't think its an exclusive issue to the N3.
This is happening 4 or 5 times per song, so it is quite annoying LOL
Zylograth said:
This is happening 4 or 5 times per song, so it is quite annoying LOL
Click to expand...
Click to collapse
Stock ROM? Stock Kernel? Need more info from both of you.
Sounds like the CPU might be dropping too low when the screen is off, causing the stuttering. You could try a custom kernel with a higher screen off frequency.
Used to happen on my S2 and this was the problem...
idtheftvictim said:
Stock ROM? Stock Kernel? Need more info from both of you.
Sounds like the CPU might be dropping too low when the screen is off, causing the stuttering. You could try a custom kernel with a higher screen off frequency.
Used to happen on my S2 and this was the problem...
Click to expand...
Click to collapse
Full stock, I believe that is the problem as it is pretty much resolved when I leave the screen on. Still testing this here and there to be sure.
This has happened to me on every rom & kernel I've tried. Which is pretty much all of them for the N3, and everything from stock to CM on the N2.
Zylograth said:
Full stock, I believe that is the problem as it is pretty much resolved when I leave the screen on. Still testing this here and there to be sure.
Click to expand...
Click to collapse
I have the same problem on my GN3 international version and yes leaving the screen on WILL solve it. However, that's not a practical solution.
Try this, download Poweramp, go into settings, audio, advanced tweaks, set the audio buffer size to Large (+250ms) and audio thread priority to +2
See if that works for you. If it does, then buy the full version even though I like the timbre effect and bass on the stock music player but this is the only solution, so far.
Zylograth said:
I have noticed since I upgraded from GS3 to Note 3 that when I am streaming music to my car stereo the audio will skip or stutter. The song continues to play but the audio cuts out for anywhere up to a second or two. Has anyone else seen this or resolved it?
I have seen some posts that say turning off WiFi fixed it but I still get the skip, if a little less frequently with WiFi turned off.
It seems to go away if I set the developer options to keep the screen awake while charging. So it seems like the CPU clock may be too low during sleep to maintain everything else it is doing as well as audio streaming.
Any feedback is appreciated, thanks!
Click to expand...
Click to collapse
What headunit? I run Kenwood KDC-X995, and never had an issue with it cutting out. THe headunit wouldn't display track info though. The way I fixed this is connecting via the Stock Samsung media player., Everything has been a dream since
I had this problem and it just went away after a few reboots and some time. ..
Sent from my SM-N900T using XDA Premium 4 mobile app
A2DP loss
Note 3 Owner here. Rooted with stock ROM and stock kernel. (T-Mobile)
Experiencing intermittent Bluetooth audio loss as well.
Just contributing to the list.
-Steven M
BTW, what player are y'all using? In power amp there is an option for keep service awake if music.stops while.playing with screen off. And there is also option to use a wake lock also. I am not having any problems nor have I ever so I can't help. The only other suggestion I have is maybe your radio Bluetooth sucks. I went through a period of testing many Bluetooth headset and receivers a couple years ago. Needed something good to listen to my music while I rode my bike. Many of the Bluetooth I tested were very sensitive to the bumps and vibration while riding hard on my mountain bike. The only solution for those were to put receiver right next to my phone. Being in my pocket was too far away or something. I ended up sticking with Sony mw600 as all purpose. It could take any headset, and I was able to use it as a receiver in my truck as it didn't have Bluetooth. Now I also have a Honda civic with built in Bluetooth and all is well. My Sony mw600 oled stopped working though so in on lookout for a nice apt x receiver.
sent from my sm-9005.
I am using a Sony DSX-S300BTX and have had no previous issues with my HTC Sensation 4G or my Galaxy S3. It only started when I got my Note 3. I use Google Play Music with the All Access service.
Just an update on this. Over the weekend I did a factory reset and this time I did not let it restore settings and apps from my Google account. I went through and installed all the same apps i was using before. And so far I have only noticed 1 stutter/cut out since then. And if I am correct, this only happened when I was leaving my house and it switched from Wifi to 4G LTE on the stream.
Will continue to monitor and see if the issue comes back. But so far I am rather happy.
Xupack said:
I have the same problem on my GN3 international version and yes leaving the screen on WILL solve it. However, that's not a practical solution.
Try this, download Poweramp, go into settings, audio, advanced tweaks, set the audio buffer size to Large (+250ms) and audio thread priority to +2
See if that works for you. If it does, then buy the full version even though I like the timbre effect and bass on the stock music player but this is the only solution, so far.
Click to expand...
Click to collapse
Trying this recommended app/setting combination, and hope that the skipping stops on the A2DP connection in the car. *crosses fingers*
hctimin said:
Trying this recommended app/setting combination, and hope that the skipping stops on the A2DP connection in the car. *crosses fingers*
Click to expand...
Click to collapse
I came from the Note 2 to the Note 3 and I'm fearing that it's 4.3 that is causing the bluetooth intermittent issue. Whether or not I stream from Pandora or my music player, I get the stutter. Doesn't matter what ROM I use between hyperdrive and beans too. Someone said it could be the adblock that is causing the stutter but I don't have that installed at all. Getting pretty frustrating.
Ended up not working for me,...but keeping the screen on did seem to eliminate the skipping.
Wonder if there's anyway to force Bluetooth not to sleep,....
Deekayy said:
I came from the Note 2 to the Note 3 and I'm fearing that it's 4.3 that is causing the bluetooth intermittent issue. Whether or not I stream from Pandora or my music player, I get the stutter. Doesn't matter what ROM I use between hyperdrive and beans too. Someone said it could be the adblock that is causing the stutter but I don't have that installed at all. Getting pretty frustrating.
Click to expand...
Click to collapse
I ONLY get the stutter when using the stock music player. It never happens when using, for example, TuneIn Radio.
I exchanged 2 Note 3's. The first one had the stutter problem so I returned it. The second one had NO stutter problems but overheated from time to time, exchanged as well. The third one doesn't over heat but, unfortunately, has the stutter problem. So, I just gave up. The PowerAmp solution works for me, though.
---------- Post added at 07:35 AM ---------- Previous post was at 07:19 AM ----------
hctimin said:
Ended up not working for me,...but keeping the screen on did seem to eliminate the skipping.
Wonder if there's anyway to force Bluetooth not to sleep,....
Click to expand...
Click to collapse
Sorry to hear it didn't work for you.
Someone mentioned increasing the minimum CPU frequency and that would solve it. Try upping it to 400Mhz see what happens but this will definitely drain your battery more than usual.
Deekayy said:
I came from the Note 2 to the Note 3 and I'm fearing that it's 4.3 that is causing the bluetooth intermittent issue. Whether or not I stream from Pandora or my music player, I get the stutter. Doesn't matter what ROM I use between hyperdrive and beans too. Someone said it could be the adblock that is causing the stutter but I don't have that installed at all. Getting pretty frustrating.
Click to expand...
Click to collapse
The same thing happened to me on the note 2.... actually the n3 isn't as bad as the n2 was. Fwiw
sent from my ??????? note 3?
SO I have started to notice that it isn't actually the stream stuttering, but a short disconnect of the bluetooth. I noticed that when the music cuts out, it also drops the media connection to my car stereo, in that the artist and song title disappear until the connection comes back. Seems like a bad bluetooth stack or something as I tested a Nexus 5 and do not have this issue at all. And I never had a problem on my GS3.
Hopefully the 4.4.2 update will resolve this issue. Whenever that may be...
I have this problem as well, (stock rom rooted, stock kernel) I use power amp. now however I cant stream my music through bluetooth at all, but when a call comes in, it streams. Doing a little digging into my phone, my N3 seems to think im in a call, and only plays my music through the speaker for your ear. it only started a few hours ago. even when I am not connected to bluetooth, it still plays music through the same speaker. tried uninstall reinstall. I did update apps earlier when I got home (ove wifi). once they were done, that seems to be when this issue started.
any help/suggestions?
I've searched the forums and found quite a bit of people saying they have experienced this, but I'm not sure if they were using notes or not.
For some reason, it doesnt matter what app I'm using, pandora, xm, or the stock players. They all studder just slightly, sometimes more so when the screen is off.
It's not a bluetooth specific thing, it happens over bluetooth as well as the speaker of the note3.
Is there a solution for this? It really drives me crazy and how can I host a party next weekend with this doing that
My girlfriend does not experience this on her nexus 5, is my problem specific to jellybean?
Thanks for your advice!
stokedcrf said:
I've searched the forums and found quite a bit of people saying they have experienced this, but I'm not sure if they were using notes or not.
For some reason, it doesnt matter what app I'm using, pandora, xm, or the stock players. They all studder just slightly, sometimes more so when the screen is off.
It's not a bluetooth specific thing, it happens over bluetooth as well as the speaker of the note3.
Is there a solution for this? It really drives me crazy and how can I host a party next weekend with this doing that
My girlfriend does not experience this on her nexus 5, is my problem specific to jellybean?
Thanks for your advice!
Click to expand...
Click to collapse
yep same problem.
i had it on nexus 4 - 4.3. but um, didn't start on my note 3 until after a few days of use. I'm not sure rebooting helps for long. i tried poweramp and jetaudio and stock player. Skips everywhere.
I tried setting decoder priority and buffer size to higher on Poweramp. Not sure if it'll help but we'll see.
I'm on N2 right now that has exact same problem, but BT only related. The micro pauses also differ between the receivers Sony Ericsson MW600 is so far the worst offender, the pauses last 1/2 second, on other receivers it's barely noticeable.
At least on N2 it's not related to the JB version, it was happening on 4.1.2 and 4.3. Changing kernel also doesn't affect the issue.
I suspect the cause is BT doesn't get enough priority and if lot's of apps running on the background it starts skipping. Usually I just reboot the phone then it works fine for a few hours, sometimes I use fast reboot app, that kills background processes it helps somewhat too.
svyr said:
I tried setting decoder priority and buffer size to higher on Poweramp. Not sure if it'll help but we'll see.
Click to expand...
Click to collapse
Using PowerAmp I went to Huge buffer and Highest priority and it seems to have fixed the stuttering for me. I'm on rooted stock.
>Using PowerAmp I went to Huge buffer and Highest priority and it seems to have fixed the stuttering for me. I'm on rooted stock.
yup. same. now wish they'd add the same features to jetaudio+ and other players D:
I get this problem often. Odd.
I'm not sure if this is a solution but I noticed the problem went away when I was using different roms/kernel combinations.
Currently I've been using the compulsion kernel with some international roms and the problem hasn't come back!
Is it the kernel or rom I can't be sure. But either way it's fixed.
If someone experiencing problems with their rom wants to try the compulsion kernel and see if the problem still exists maybe it can help a lot of people.
Sent from my SM-N9005 using Tapatalk
When I connect Bluetooth to my car and try to stream music it start stuttering/ skipping like crazy, every second or so. I've tried it with multiple apps, Spotify, play music and YouTube same effect. Seems like Bluetooth can't handle the bandwidth. Never had this problem with my Nexus 5.
Anyone else have this issue?
reddv1 said:
When I connect Bluetooth to my car and try to stream music it start stuttering/ skipping like crazy, every second or so. I've tried it with multiple apps, Spotify, play music and YouTube same effect. Seems like Bluetooth can't handle the bandwidth. Never had this problem with my Nexus 5.
Anyone else have this issue?
Click to expand...
Click to collapse
It's been working great for me. Tried it with my VW Passat, Bose Soundlink Mini, and another Bluetooth speaker. No skipping or audio delays noticed. Usually playing Play Music, YouTube, or iHeartRadio.
Sent from my Nexus 5X using Tapatalk
It hasn't been as bad a you describe but I have noticed some stuttering. Not enough to ruin my experience, though.
I got phone on 10-21. I stream Pandora all day in my work truck to a jbl change 2+ and have my bt ear piece for calls connected all day. I have not had one issue
Mine did it the first time I ever used it in my car, and it was unbearable. After day one though, the issue self resolved and I had no problems. I actually noticed it first using navigation over bt
Sent from my Nexus 5X using Tapatalk
Yep. I got this several times. Turning off/on Bluetooth was the only way to fix. Not ideal when doing 70 on the motorway.
Sent from my Nexus 5X using Tapatalk
Same problem here, it makes bluetooth unbearable in my car. ONLY my car, as I don't have any stuttering on other bluetooth devices. Never had a problem on my Nexus 5, only the 5X.
Edit:
For clarity, I am full stock, not rooted or unlocked
I'm having the same issues. It seems the worst when I have Waze running while beyondpod is playing. I don't have guidance enabled, so Waze shouldn't be playing audio.
After streaming for a few days, I don't have this problem anymore. Weird, but I'm glad it's working now. Try what someone posted earlier, just turn off and turn on Bluetooth.
reddv1 said:
After streaming for a few days, I don't have this problem anymore. Weird, but I'm glad it's working now. Try what someone posted earlier, just turn off and turn on Bluetooth.
Click to expand...
Click to collapse
That didn't solve my issue. Rebooting the phone did, however. There must be a memory leak.
There is a issue opened on the Google code page. I'm not skilled enough with adb to capture the logcat. I am not allowed to post links so just add
p/android/issues/detail?id=193085
To the end of the google code url
airplane888 said:
There is a issue opened on the Google code page. I'm not skilled enough with adb to capture the logcat. I am not allowed to post links so just add
p/android/issues/detail?id=193085
To the end of the google code url
Click to expand...
Click to collapse
I experienced some stuttering over bluetooth in my toyota camry. Will test it further.
I could not reproduce the stuttering issues again until today when I was streaming music it decided to stutter as I read an email. Rebooted phone and it was fine.
Up the thread.
I just bought bluetooth earphones, I thought they were defective, so I replace them, but i got always the same problem, the sound is stuttering. And after some seconds, it simply goes blank, no sound at all. :/
I tested them on other smartphones and tablet, and they are working great.
I also noticed that if i put the nexus 5x really closed to the earphones (1 cm), it's working nice.
I contact Google, but they kept saying i have to contact the earphones manufacturer (Aukey). But it's clearly a bug with the phone.
There is just one thing I didn't try yet. It's to wipe the phone and flash the last android image (i read somewhere some guys fixed their problem doing this, where ota updates didn't).
Anybody got information or solution?
Thanks