Related
So I've discovered a pretty nasty bug that seriously affects my listening pleasure.
I should start by saying that I am a recent Android convert, the GN beeing my first foray into the realm of Android devices.
Having used an iPhone for the past 3 years (and mostly for rocking out to my favourite music on my daily commute) I was initially really excited with the quality of the audio on the GN, even when using the stock iPhone earbuds. This issue however, has nothing to do with the earphones, it happens even when the phones are disconnected
I noticed however that my music had a tendency to start clipping (clicking horribly while playing HQ files in most supported formats). My first step was to download pretty much every decent player I could find - right now, I have WinAmp and PowerAmp installed.
I eventually narrowed the problem down to the lock screen, more specifically when the screen blacks out after being idle for nn minutes. s
o long story short, if I play my music with the phone unlocked it all sounds really good, as soon as I lock the screen (clicking the power button at top right to switch to black screen) the music starts clipping horribly at very irregular intervals.
I've asked a mate to try the same steps on is GN and he says he can't hear any difference, so wanted to put this to the community to see if anyone else has experienced anything similar. Does this sound like a return job?
Being an android noob, I have no idea of any methods of providing debug info, so any input is welcome.
Thanks
Sky
i think all android phones do this...... at least my desire did this as well. Thats if you mean a very slight break when the screen goes black ?
wilbur-force said:
i think all android phones do this...... at least my desire did this as well. Thats if you mean a very slight break when the screen goes black ?
Click to expand...
Click to collapse
I have not experienced this on my Nexus S and I listen to music a lot with my screen locked.
ruthlesset said:
I have not experienced this on my Nexus S and I listen to music a lot with my screen locked.
Click to expand...
Click to collapse
Its just one fraction of a second blip as the screen locks in my experience.....
NO, in my case it's constant, like every few seconds... sounds like a case for replacement imo
Skysurfer69 said:
NO, in my case it's constant, like every few seconds... sounds like a case for replacement imo
Click to expand...
Click to collapse
Ya that's not a usual problem. Sounds defective. What file types are the music?
Skysurfer69 said:
So I've discovered a pretty nasty bug that seriously affects my listening pleasure.
I should start by saying that I am a recent Android convert, the GN beeing my first foray into the realm of Android devices.
Having used an iPhone for the past 3 years (and mostly for rocking out to my favourite music on my daily commute) I was initially really excited with the quality of the audio on the GN, even when using the stock iPhone earbuds. This issue however, has nothing to do with the earphones, it happens even when the phones are disconnected
I noticed however that my music had a tendency to start clipping (clicking horribly while playing HQ files in most supported formats). My first step was to download pretty much every decent player I could find - right now, I have WinAmp and PowerAmp installed.
I eventually narrowed the problem down to the lock screen, more specifically when the screen blacks out after being idle for nn minutes. s
o long story short, if I play my music with the phone unlocked it all sounds really good, as soon as I lock the screen (clicking the power button at top right to switch to black screen) the music starts clipping horribly at very irregular intervals.
I've asked a mate to try the same steps on is GN and he says he can't hear any difference, so wanted to put this to the community to see if anyone else has experienced anything similar. Does this sound like a return job?
Being an android noob, I have no idea of any methods of providing debug info, so any input is welcome.
Thanks
Sky
Click to expand...
Click to collapse
when the screen is locked on any Android phone, the CPU is underclocked to save power.
what you're experiencing is audio buffer underruns due to the CPU slowing down. this is normal.
have you tried playing the music using the default music player? you shouldn't experience the problem using the default music player.
Try changing the encoding of your music. The phone is probably struggling to decode your current format in the underclocked state.
Sent from my Galaxy Nexus using XDA App
I know where you are coming from but I don't experience this issue on my GN.
Go to power amp. Settings, audio engine, advanced tweaks and set the buffer to huge. I don't think it will work as it seems to me its when your device goes into sleep. Like the CPU is being undervolted too much. If it happens on the stock music app (Google music) I would send it back as defective.
OR - Maybe Google don't want you to use ****ty iPhone headphones after all.
Sent from my Galaxy Nexus using xda premium
NatTheCat said:
I know where you are coming from but I don't experience this issue on my GN.
Go to power amp. Settings, audio engine, advanced tweaks and set the buffer to huge. I don't think it will work as it seems to me its when your device goes into sleep. Like the CPU is being undervolted too much. If it happens on the stock music app (Google music) I would send it back as defective.
OR - Maybe Google don't want you to use ****ty iPhone headphones after all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
it is more likely going to be related to the third party apps he is using to listen to music, that don't know how to keep the CPU alive in a higher state while the screen is locked. I had the same problem on my Nexus S with Skype for a while, where I couldn't actually put the screen to sleep using the power button while in a call - the audio would buffer underrun like crazy. Skype eventually pushed an update and it fixed the problem.
oscillik said:
it is more likely going to be related to the third party apps he is using to listen to music, that don't know how to keep the CPU alive in a higher state while the screen is locked. I had the same problem on my Nexus S with Skype for a while, where I couldn't actually put the screen to sleep using the power button while in a call - the audio would buffer underrun like crazy. Skype eventually pushed an update and it fixed the problem.
Click to expand...
Click to collapse
I was thinking the same. My GS2 had the same issue with power amp. But the stock app was fine. Crazy android phones but we love ya.
Sent from my Galaxy Nexus using xda premium
oscillik said:
it is more likely going to be related to the third party apps he is using to listen to music, that don't know how to keep the CPU alive in a higher state while the screen is locked. I had the same problem on my Nexus S with Skype for a while, where I couldn't actually put the screen to sleep using the power button while in a call - the audio would buffer underrun like crazy. Skype eventually pushed an update and it fixed the problem.
Click to expand...
Click to collapse
Not related to the ****ty iPhone headphones (lol thanks for that Nat) or the 3rd party apps I'm afraid... the same issue happens when I use the built in speaker, the GN issued earphones, and also regardless of whether I use the default music app or poweramp/winamp.
Changing the encoding of my music is going to be an extensive task if I have to do this for my entire library (30K+ tunes) I'll be here til next year.
Skysurfer69 said:
Not related to the ****ty iPhone headphones (lol thanks for that Nat) or the 3rd party apps I'm afraid... the same issue happens when I use the built in speaker, the GN issued earphones, and also regardless of whether I use the default music app or poweramp/winamp.
Changing the encoding of my music is going to be an extensive task if I have to do this for my entire library (30K+ tunes) I'll be here til next year.
Click to expand...
Click to collapse
what format is your music in, what sample rate and bit depth is it?
ie: FLAC 24bit / 192KHz
not sure oscillik, a range of formats (mainly MP3, some AAC) and bitrates (nothing less than 192k and mostly 320k) again not sure of the samplerate either, would have to check my library which I have no access to for now as I'm on the road
Skysurfer69 said:
not sure oscillik, a range of formats (mainly MP3, some AAC) and bitrates (nothing less than 192k and mostly 320k) again not sure of the samplerate either, would have to check my library which I have no access to for now as I'm on the road
Click to expand...
Click to collapse
those formats and bit rates should be just fine. just to let you know, bitdepth and bit rate (emphasis on the space also) are completely different things. i think it's safe to assume that the sample rate for your music is likely to be 44.1KHz (which is standard).
you may have a faulty handset, I would demonstrate the problem to the store you bought it from and get a replacement handset.
I get the clipping too but only with Power amp and not the stock player.
Never had this on any phone before.
Might have to get rid! Anyone want to buy a GN 2 days old?
Spewy1 said:
I get the clipping too but only with Power amp and not the stock player.
Never had this on any phone before.
Might have to get rid! Anyone want to buy a GN 2 days old?
Click to expand...
Click to collapse
Yus.
10char
NatTheCat said:
OR - Maybe Google don't want you to use ****ty iPhone headphones after all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1
10char.
@spewy check NatTheCats post about settings in power amp, they did the trick on my device and strangely enough I'm no longer having the problem in the default player either. Thanks to Oscillix and Nat for your help.
Sent from my Galaxy Nexus using XDA App
*Oscillik
Sent from my Galaxy Nexus using XDA App
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.
There are several threads now detailing a problem with playing music, mainly reported when using the Google Music app. To be more specific here are some examples:
When playing music and then multitasking, the phone crashes and requires a battery pull and reboot.
Another is when playing music and then turning the screen off, the music is jerky and stutters.
People have reported this happening with apps other than Google Music, so it would appear that this isn't a problem with the Music app, but either the phone or ICS.
I wanted to start a poll to gauge how many people have this problem and establish whether it's everyone or not.
Here are some links to what I'm referring to:
http://forum.xda-developers.com/showthread.php?t=1381413
http://forum.xda-developers.com/showthread.php?t=1380773
http://forum.xda-developers.com/showthread.php?t=1379600
http://code.google.com/p/android/issues/detail?id=22669
Your poll is a bit flawed. My experience so far is that these crashes are a bit more random than being attributed to any specific apps right now. I've experienced the crash, but long story short, I am not convinced it was related to the exact app that I was using at the time.
Well just because you have experienced an unrelated crash it doesn't mean my poll is flawed, just that you have a separate issue
People have spoken of this happening repeatedly when trying to use Music and multitask so I think it is definitely an issue of it's own. Usually it is said that the sound/screen goes corrupt and then requires a battery pull. Are you not referring to a random reboot or something?
i have a couple of problems with PowerAmp, no problems with google music though.
1. PowerAmp can't see playlists that were created in google music
2. PowerAmp stutters when the screen goes to sleep. (does the clock speed lower when the screen goes off?)
i've read that increasing the buffer size in poweramp options fixes no. 2. I havent tried it due to no.1.
i'm just using google music at the moment.
WinAmp i found would often have slight cracks in the music (i.e. stop and start again quickly, almost like it was being disturbed/cpu high).
doubletwist is fine though, as is Music player
This is such a huge problem I can't believe more people haven't responded :S
I've had Google Music, Rhapsody, and Pandora all crash at one time or another.
str355 said:
i have a couple of problems with PowerAmp, no problems with google music though.
1. PowerAmp can't see playlists that were created in google music
2. PowerAmp stutters when the screen goes to sleep. (does the clock speed lower when the screen goes off?)
i've read that increasing the buffer size in poweramp options fixes no. 2. I havent tried it due to no.1.
i'm just using google music at the moment.
Click to expand...
Click to collapse
increasing the buffer size in power amp fixes no.2
Sent from Mobile..
problem number 2 here for me. songs with high bit rates tends to trigger the stutter problem after the phone goes to sleep. tried on google music and playerpro
Google Music 4.0.1 (ICS stock) often crashes within a minute after I reboot the phone - without me actually using it.
Obviously it's trying to do something in the background on start-up and fails. Miserably.
Did not crash while I was using it so far, but I didn't run it for any lengths of time either. No problems with other apps crashing, just Music.
rayvioli said:
problem number 2 here for me. songs with high bit rates tends to trigger the stutter problem after the phone goes to sleep. tried on google music and playerpro
Click to expand...
Click to collapse
Yes I notice it too, it's very annoying especially since I payed so much for this phone and a good set of headphones just for my high bit-rate music to constantly stutter; hopefully google fixes this. I seem to only notice this on the stock music player, but I prefer to use it over others due to its integration with the lockscreen and notification pulldown bar, especially considering the nice visuals it now has.
my 2 cents:
i can recreate the crash consistently by doing the following:
1. reboot the phone and connect a pair of headphones
2. stream a song (i.e., a song that's not already saved to the phone) using google music
3. use the home button to leave the google music app and return to the homescreen
4. while the song is playing, try to increase or decrease the volume of the music with the volume buttons and then almost immediately the phone reboots automatically.
i haven't been able to recreate the issue once with the headphones disconnected. also, the issue doesn't seem to occur if you connect the headphones after you start playing the music. i need to test that theory some more though.
I noticed this right away when I got my phone (launch day)
Since I constantly stream music from google music, I noticed pops and weird noises all the time. Very weird and SUPER annoying
The stock music app is not able to find my music at all. I use PowerAMP now and that works fine.
Music also crashes when not actively in use at all. When I open a lot of apps, i.e. multi-task a lot, Music often just force closes after a while.
I'm using PowerAmp now to listen to music stored in either .flac or the highest quality .mp3 files lame could produce. Some are 320kbps cbr others are vbr. In PowerAmp I set the process to the highest priority possible but left the buffer on auto.
I have never had any reboots or studering when locking the screen and I've been listening to music for over 3 hours now while doing some home work. Just to test it I put on one of my flac files and quickly locked and unlocked the screen. The phone took it like and champ with no studers at all.
No problems with music apps crashing, or needing to pull the battery. The only issue I have is with music or podcasts played through the native music player or Google Listen stopping at random intervals. Happens using wired speaker/headphones or bluetooth audio.
Frustrating, but not a dealbreaker yet.
I called Verizon for no other reason other than trying to create a record of the issue... They claimed to have not heard of this... Is there any way to let Samsung know directly? I know there is a google code ticket open, but Google hasn't "owned" the issue yet... I'd also say if you have the issue to let VZW know so they can get things in motion on their side as well.
kptkill said:
I called Verizon for no other reason other than trying to create a record of the issue... They claimed to have not heard of this... Is there any way to let Samsung know directly? I know there is a google code ticket open, but Google hasn't "owned" the issue yet... I'd also say if you have the issue to let VZW know so they can get things in motion on their side as well.
Click to expand...
Click to collapse
It seems they don't give a ****, unfortunately. Just have to live with it..
WinAMP - today while playing an album with the screen off paused (twice). I had to turn on the display, and hit the play button to continue. There was a bit of a lag (I got the FC screen, but when i hit wait the app returned a few seconds later)
Does anyone have this problem? I'm on the latest version of AOKP with Franco Kernal...Everytime I listen to music, it will randomly stop and I would have to press play again. This happens at random times, (seconds, minutes, hours). I'm using Google Music (Play Music). I have tried PowerAMP and other players, but they seem too all do it.
It's kind of bugging me
ogxjason15 said:
Does anyone have this problem? I'm on the latest version of AOKP with Franco Kernal...Everytime I listen to music, it will randomly stop and I would have to press play again. This happens at random times, (seconds, minutes, hours). I'm using Google Music (Play Music). I have tried PowerAMP and other players, but they seem too all do it.
It's kind of bugging me
Click to expand...
Click to collapse
It could be a bug with Franco's sound hacks he implements in his kernels. Perhaps try using a different kernel?
anton2009 said:
It could be a bug with Franco's sound hacks he implements in his kernels. Perhaps try using a different kernel?
Click to expand...
Click to collapse
hmmm...can anyone else confirm this that's also using Franco's Kernal....
I get this on stock. I thought it was related to another piece of software (pocketcasts) that I installed about the same time the problems started. Seem that the first song is played, then it pauses or stops.
Could be a buggy headphone connector (in the phone), where it send a faulty signal telling the system that you have unplugged the headphones. Does it only happen while using headphones?
My connector does that as well, but opposite. When not using headpones it sometimes signals that something has been plugged in, and all audio is routed to the non-existing headphones.
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
It's not a Franco's kernel only problem. I have the same issue on Stock 4.0.2 (GSM, unlocked, unrooted).
It is not the headphone connector that is buggy either since i'm experiencing this with bluetooth headset as well (A2DP headset).
The music app is not crashing either since it doesn't require a full "load" when i select the app. Press play again and all is good until next time.
It happens to me on stock as well. With both the music and listen apps. Seems to happen if I'm playing music for a half hour or so without using the phone.
Sent from my Galaxy Nexus using xda premium
I am running AOKP M3 and Franco's kernel and am experiencing the exact same thing.
Benxter said:
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
Click to expand...
Click to collapse
I have noticed this. When i turn down the volume it stops doing it. But when i turn it up to max it will start doing it again
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I experience this on google listen on stock 4.0.1. I thought it was a bug with the app losing audio focus. But then they updated and claimed an audio focus fix, yet it still happens. I can force this bug to happen by multitasking moderately. So i truly think this bug is related to the over aggressive memory management on this phone.
Yea I'm using Axi0m and I notice this. I think its an issue with the headphone jack. When I installed power amp, one of the features is to detect connection to the headphones... then the phone started to randomly start and stop playing music completely random.
I updated and it seems to be fixed. Still stops occasionally but at least I can listen for an extended period.
Sent from my Galaxy Nexus using xda premium
Franco Kernel updater
I'm running Lean Kernel and I get this all the time when I have the volume set to MAX on the device itself, I find if I turn it down just a bump then the problem goes away. This may be some type of fail safe for the phone itself. ??? But just turn your vol down one click and you're good to go.
I always had issues playing music with franco.kernel, it did me just like you are talking about. That **** used to drive me crazy! Anyways, no issues with CM10 M2. Also using the built in CM kernel.
yup, had this thing on both stock and codename android. google music app
Just gotta wake up this thread.
I'm having this issue on CM10.2... I had this same thing on stock JB some time ago when I connected to my BT headset..
Is there any fix for this?
Btw.
I don't use any custom kernels and this is not caused by any kernel and I don't think this to be caused by BLE.
Benxter said:
this bug definitively occurs on francoKernel!
Try flashing another kernel (Popcorn for example) and the bug is gone.
Seems to have something to do with the sound limit. If it's too loud it stops automatically. Try reducing the volume to 60% with the hard buttons and you'll see that it stops acting like that.
Click to expand...
Click to collapse
^^This
I had the same issue and realized I had the volume up too loud with the mods I had installed. Keep the volume below 80% and the problem will disappear.
Possible solution
I used to have this issue as well, where after a certain period of not actually using the phone, the music playback would just pause itself.
I discovered that I had Play music "Greenified" which is basically a hibernating task manager. That was killing the background process of any music players I had open.
Wether or not you have the Greenify app, check for any automatic task killers and get rid of them.. Maybe that will help one of you guys, it sure helped me.
Only had this happen using headphone volume boost... don't use it
Sent from my Galaxy Nexus using Tapatalk 2
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