Related
The day I got my pure edition it got the update for lollipop, so I don't know if this happened in KitKat. When I stream music over Bluetooth and the moto active display kicks in, the music pauses for a split second. Kind of makes it useless for streaming. Anyone else? Stock, unrooted, locked boot loader
I have the same issue, didn't connect it to the active display tho. Works better after a recent reboot, but still will skip occasionally. I have noticed that it seems to be Google Play music that has the issue. Pocket casts hardly ever skips.
enochpc said:
I have the same issue, didn't connect it to the active display tho. Works better after a recent reboot, but still will skip occasionally. I have noticed that it seems to be Google Play music that has the issue. Pocket casts hardly ever skips.
Click to expand...
Click to collapse
i'm surprised no one else has noticed this. it happens with me on spotify.. its terrible in the car
I use Google play all access with the BT in my car with Dodge's Uconnect (2012 MY) and the only time I get skipping or stuttering with the music is if I connect, walk far enough away to loose connection while streaming music and then walk back in range. Like if I forgot something in the house. If I get a notification, the music volume will go down, but then I hear the notification though the speakers.
This is on a PE with 5.0
Interesting... I've used bluetooth to stream Google Music and Soundcloud a lot in my car, and I haven't noticed this issue (I'm really nit-picky on this stuff, so I'm not sure I would have missed it).
I'm also on Lollipop, updated back when I got my pure edition around new years.
I'm looking forward to 5.02 or 5.1, which ever we get next, as I have several annoying bugs (including bluetooth) that I hope are addressed. I am currently stock, 5.0, but am seriously ready to try cm12 now that they have bluetooth ironed out. Still love the active display tho, even tho it randomly goes off or won't work for no apparent reason.
Lot's of manual reboots on my phone, at least compared to my old M7, if it wasn't for the camera I would still have that phone.
I've only noticed skipping using Pandora. Google play music doesn't skip.
Hey All,
I just switched to a Galaxy S6 (Cricket version, which is apaprently an AIO rebrand, which is apparently an AT&T rebrand?). I'm enjoying it so far. However, the biggest issue I run into is that it is automatically closing Pocket Casts (or any podcast app I try) after I leave it paused during the day.
For more details on the scenario:
I listen to various podcasts on the drive to and from work. Pocket Casts automatically starts playing as soon as it's connected to my car. On both of my old phones (Sharp Aquos Crystal and LG Mach), I could go throughout the day, and the paused Pocket Casts notification would stay live. I've tested that this is still the case even with the most recent version on both phones. This means I don't even have to restart the app when I leave work for the day, I can just hit play on my car's audio controls and it'll keep playing.
However, with the Galaxy, it seems that it'll close Pocket Casts after it has been paused for an hour or so. I was wondering if this was something caused by the "Music" app (which they don't let you disable) also having similar functionality.
Is there anyway to change or stop this behavior? I've doublechecked that Pocket Casts is set up the same way on all 3 devices. I've also attempted Podkicker Pro on all 3 devices, and it has the same behavior (works on the prior 2, gets closed on the galaxy).
If it's a Music app issue, is there anyway to disable that at the system level?
Any and all help is appreciated.
Eujin said:
Hey All,
I just switched to a Galaxy S6 (Cricket version, which is apaprently an AIO rebrand, which is apparently an AT&T rebrand?). I'm enjoying it so far. However, the biggest issue I run into is that it is automatically closing Pocket Casts (or any podcast app I try) after I leave it paused during the day.
For more details on the scenario:
I listen to various podcasts on the drive to and from work. Pocket Casts automatically starts playing as soon as it's connected to my car. On both of my old phones (Sharp Aquos Crystal and LG Mach), I could go throughout the day, and the paused Pocket Casts notification would stay live. I've tested that this is still the case even with the most recent version on both phones. This means I don't even have to restart the app when I leave work for the day, I can just hit play on my car's audio controls and it'll keep playing.
However, with the Galaxy, it seems that it'll close Pocket Casts after it has been paused for an hour or so. I was wondering if this was something caused by the "Music" app (which they don't let you disable) also having similar functionality.
Is there anyway to change or stop this behavior? I've doublechecked that Pocket Casts is set up the same way on all 3 devices. I've also attempted Podkicker Pro on all 3 devices, and it has the same behavior (works on the prior 2, gets closed on the galaxy).
If it's a Music app issue, is there anyway to disable that at the system level?
Any and all help is appreciated.
Click to expand...
Click to collapse
Unfortunately you'll have to wait until the 5.1.1 update which will fix the ram issue which you are currently experiencing. I listen to a lot of music through Google Play Music on my S6 through my earphones and every time I pause it for a few minutes, the app seemingly gets killed due to the aggressive RAM management. I have to pull out my phone, unlock it, and replay my music from the app. For now there's not much you can do, except clear any other running apps before staring your podcasts.
Sent from my SM-P600 using Tapatalk
¿Will-it-Blend? said:
Unfortunately you'll have to wait until the 5.1.1 update which will fix the ram issue which you are currently experiencing. I listen to a lot of music through Google Play Music on my S6 through my earphones and every time I pause it for a few minutes, the app seemingly gets killed due to the aggressive RAM management. I have to pull out my phone, unlock it, and replay my music from the app. For now there's not much you can do, except clear any other running apps before staring your podcasts.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. So to clarify, this is a known issue currently in Lollipop, and it's already on the fix pipeline, correct? Is there somewhere I can see the planned fixes?
Eujin said:
Thanks for the response. So to clarify, this is a known issue currently in Lollipop, and it's already on the fix pipeline, correct? Is there somewhere I can see the planned fixes?
Click to expand...
Click to collapse
Known issue in lollipop and Samsung firmware.
http://forum.xda-developers.com/gal...-sammobile-t3126473/post61144150#post61144150
Sent from my SAMSUNG-SM-G920A using Tapatalk
I'm using an AT&T variant in a Chevy 2015 Equinox. The phone operates fine with calls but stutters and skips with streaming audio. Any app I use it does the same thing; Poweramp, Google Music, Pandora, etc. My wife's iPhone 6 Plus has no issues whatsoever. Is this a phone issue, an AT&T software issue or car issue? Anyone experience anything like this and can give me some direction? TIA
I had something like that happen before. Doesn't happen much anymore. I wasn't streaming though. Listening to podcast I downloaded. It would play fine for a while but then start to stutter. Would work fine after I woke up the phone so assume it had something to do with the processor dropping down too low like it was trying to go to sleep or just the use the low power cores maybe. Just a guess. Doesn't happen anymore though. I'm on t mobile.
Sent from my SM-N920T using Tapatalk
This is a widespread issue with Bluetooth on Android (since about KitKat, possibly earlier) that spans just about every possible combination of hardware and software. It is exactly like you said -- the phone's CPU is too slow to keep up with Bluetooth audio decoding and streaming when the screen is asleep. The CPU governor is too aggressive on saving every last microwatt of battery life, and would rather your experience suffer instead.
The issue is very well-documented, but Google refuses to fix it. See here for hundreds of complaints spanning every major manufacturer and just about every imaginable Bluetooth headphones, speakers, headset, earbuds, etc. etc.:
https://code.google.com/p/android/issues/detail?id=95294
its an easy fix, just download kernel adiutor, set the minimum to 500 and see. I personally set the min and max of little cpu to 900 and big to 1200mhz.
Hey everyone,
I've been battling this issue since Day 1, and its been a bumpy road. It seems as though this is a widespread issue across many Android devices, and fixes range but none of them seem to completely eliminate it.
When connected to Bluetooth audio, certain devices, the audio stutters or "skips". Ive noticed this extensively in KItKat. One fix for rooted devices was to increase the idle CPU frequency, I did so with Tasker and it definitely suppressed the stuttering, but did not completely eliminate it.
One of the most notable points of stuttering is when you answer a call via Bluetooth, then hang up. After hanging up, and music resuming, there is a solid ~10-20 seconds of constant stuttering and skipping until playback returns to normal.
Imagine my surprise when I upgraded to 6.0.1, and had absolutely no stuttering without increase CPU frequency or anything! Just buttery-smooth playback, all the way through, even after hanging up a call.
However, a couple of weeks after, the issue came back again. I had to re-enable my task to increase idle CPU frequency, and that horrible stutter after hanging up a call is back, strong as ever. To me this indicates perhaps something I modified after stock interfered., however nothing I can think of should come close to affecting it, other than XPOSED (however, XPOSED was installed prior to this issue coming back up, and no new modules were added)
Additionally, since Marshmallow, my phone won't reconnect automatically to my head unit. For example, when my car is on accessory mode and the stereo is on and BT connected. When I start the car, the system momentarily turns off for ~5 seconds at most, and turns back on. With Lollipop it would automatically reconnect, here is causes some serious problems as the only way to get them to reconnect after is to turn off the stereo and the phone, and turn both back on again. Sometimes I even have to do a couple of cycles.
Does anyone have any ideas?
i tried to do everything possible to fix the issue... I have a stuttering keyboard as well... anykeyboard I use seems to stutter, it lags a little, but most words that i type apear two times...
I have no issues at all like that, or stuttering throughout the system. It is specifically related to Bluetooth audio.
Anyone?
I've always thought kernel
unibomber said:
I've always thought kernel
Click to expand...
Click to collapse
If you do not have this problem, what kernel do you use? I just flashed BeastMode today, hoping that will bring me a bit of luck. However as it worked initially and a few weeks later broke down into the pathetic mess once again, I have my doubts
I use power amp and in advance I set thread priority to the highest and audio buffer to 750ms. I've used them all and haven't had skipping
unibomber said:
I use power amp and in advance I set thread priority to the highest and audio buffer to 750ms. I've used them all and haven't had skipping
Click to expand...
Click to collapse
Seems to have improved it, but reconnect issue is still present
The reconnect issue may be related to the stuttering.
The unit may be also trying to download contacts at the same time which causes the stutter.
Have you tried unpairing it from the unit, renaming your phone and then pairing it again?
Will Rickards said:
The reconnect issue may be related to the stuttering.
The unit may be also trying to download contacts at the same time which causes the stutter.
Have you tried unpairing it from the unit, renaming your phone and then pairing it again?
Click to expand...
Click to collapse
I have in fact tried to re-pair the unit many times, to no avail. Factory resets also yield no benefits. It is set to auto download contacts, I'll try to disable that option to see if it improves anything.
I have the stuttering almost removed, however it still sometimes occurs. On a recent long-distance road trip, it randomly started stuttering after playing flawlessly for 1.5 hours, it was incredibly frustrating. I rebooted the phone, and the stereo, reconnected and it started playing smoothly again. Keep in mind however this is with both raising idle CPU frequency, and changing the poweramp options mentioned in Post #7
Perhaps I should try a custom ROM?
You can also try stopping media scanning. I think there is a xposed plugin
I only notice this on a non-name-brand headset. (Also, after it happens, I disconnect and reconnect...and it works fine from there on out...until Power down) My other 3 don't have this problem. Music plays, get a call, hang up, music pick right up. Didn't read your post in detail to see if you've tried a different pair of BT receiver.
FWIW it's not just you, also use PowerAmp, have the buffer turned up, and also get stuttering. On pvsgh's stock rooted deodex'd debloated 5.1.1 with beast mode 1.92 + ZL fix and both my motorola s10 headset and sharkk speaker stutter from time to time. It does not seem to be universal. In the beast mode thread it bluetooth audio issue was brought up, but didn't really get much attention ::shrugs, palms up:: I even limited them to media only but still get the stuttering.
Like so many things it seems, it worked ok before the MM update (910t3 on dok2 ootb) and now doesn't. Kinda like my ability to sign into enterprise level (work - EAP login) routers...
CM12.1 didn't make a difference in my case. Been on several stockish 5.1.1 roms as well. It still happens. Swapping out roms doesn't appear to pay off. It hasn't for me anyway :-/
Interested to see if a solution (or a cause?) lands here...
Sent from my SM-N910T3 using XDA-Developers mobile app
After upgrading to 8.1 on my Pixel, I noticed that in Android Auto, when listening to Spotify, the music will intermittently have its volume lowered (like a notification or driving direction) for a few seconds. However its not related to receiving any actual notifications or driving directions (happens even when not navigating). Nothing is actually being read out, and I can't find any rhyme or reason - happens typically once a minute, and I can't correlate any pattern (e.g. coming up to lights? start or end of song? moving or stationary? its totally random).
Its only happening since 8.1 (pretty sure that's when it started happening - before I had a perfect experience) and its bloody annoying. Anyone experienced this and/or found a fix?
I have an OG Pixel XL, same sort of thing on mine, but it happens with both pocket casts and GPM as well, sometimes it mutes for a couple seconds for no reason, sometimes is outright pauses for no reason and I have to hit play again.