Has anyone else experienced stutter in music playback when browsing the web? Seems that the Desire can't handle both playing music from Spotify while I browse pages. As this never was a problem with my old Nokia N82, I'm guessing the problem is with either the browser or Spotify client?
Yes, I have experienced this issue as well. I found that if I'm trying to browse the web or send text messages it kills Spotify, in the sense of making it stutter like hell!
I found the best way to avoid this is to try minimise the amount of applications you have open in the background.
Due to the Desire's high spec, and way of dealing with multiple processes, I imagine that this is a Spotify issue, rather than a Desire issue.
might be cause after all the tracks in spotify are not stored as mp3 files but are (iirc) encrypted, meaning spotify could use quite some cpu.
Having almost the same problem.
I tried using spotify and Sportypal at the same time and that didn't work that well
Related
I have never been able to get my music tab functioning correctly on my device. Whenever I try to play a music file, it will play for about 1-2 minutes and then it just stops playing. It usually seems to happen around 1:45. It isn't just that it loses sound, the time stops counting up and everything. The only way to get it to start playing again is to actually stop the playback and start it over again. The problem only occurs when I try
to use the music tab. WMP, TCPMP, MortPlayer, etc are all fine.
This issue has gone on pretty much since I got my phone last year. I believe that at one time in the past it DID seem to get resolved but I have no idea what was different or what ROM I was running at the time.
Preventing the phone from turning the screen off (my first thought) does not appear to extend the time before it stops. Having the phone plugged in also has no effect. It happens using BT audio as well as the phone's speakers. This issue has persisted across multiple ROM versions and cooks. I have been running mostly EnergyROM lately but have also encountered it with Valkyrie and others.
If anyone has any good ideas on how to fix this I would be grateful. It has gotten to the point that I just ignore the music tab entirely if I don't actively remove it from Sense, but it would be nice to be able to use it.
I'm assuming you're playing your music off of the SD card? Does it behave the same when you play files from the onboard memory?
same here and yeah im running it off the SD card. help please
I too am having the exact same problem.
I have had the problem, but I found out that Opera was also always open when this happens, and I just assumed that the system was running out of memory, so I just play music when Im doing NOTHING else when using the Sense player, but the Alternative is to just use WMplayer or TCMP or Nitrogen
well sense the new cht has the music player on the homescreen i find it very nice and usefull and wmp does take up any memory while the htc sense doesnt..so yeah =/
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)
Hello,
There's one function on Android crucial to me that I have yet to find a perfect solution for, and that's variable speed audio playback. I'm a big audio podcast fan (using the excellent Pocket Casts app), and to get through hours upon hours of podcasts I like to play them back at a faster speed than normal. 2x speed, for example, sounds absolutely fine (not quite Alvin-and-the-Chipmunks fast) and as you would surmise cuts the normal podcast play time in half.
Pocket Casts uses an external app called Presto Sound Library to accomplish variable speed functionality, but this app appears to have been abandoned. The user forum, for example, hasn't been posted to since August, and the developer hasn't got back to my emails. Basically, the problem is that if you get a phone call when listening to something in Pocket Casts/Presto, upon completion of the call Pocket Casts force closes (although sometimes the audio just keeps on going uncontrollable). I've figured out via a helpful Play Store comment that force-closing Presto saves you from having to reboot, but needless to say this bug is extremely annoying. Problem started in Ice Cream Sandwich as I recall having it also on my CM9 Galaxy S II.
Anyone else out there have an alternative app for variable playback that works better on Jellybean? Cheers
kitecarl said:
Hello,
There's one function on Android crucial to me that I have yet to find a perfect solution for, and that's variable speed audio playback. I'm a big audio podcast fan (using the excellent Pocket Casts app), and to get through hours upon hours of podcasts I like to play them back at a faster speed than normal. 2x speed, for example, sounds absolutely fine (not quite Alvin-and-the-Chipmunks fast) and as you would surmise cuts the normal podcast play time in half.
Pocket Casts uses an external app called Presto Sound Library to accomplish variable speed functionality, but this app appears to have been abandoned. The user forum, for example, hasn't been posted to since August, and the developer hasn't got back to my emails. Basically, the problem is that if you get a phone call when listening to something in Pocket Casts/Presto, upon completion of the call Pocket Casts force closes (although sometimes the audio just keeps on going uncontrollable). I've figured out via a helpful Play Store comment that force-closing Presto saves you from having to reboot, but needless to say this bug is extremely annoying. Problem started in Ice Cream Sandwich as I recall having it also on my CM9 Galaxy S II.
Anyone else out there have an alternative app for variable playback that works better on Jellybean? Cheers
Click to expand...
Click to collapse
I'm having the same problem!!
Have you found a better alternative? I especially have the problem when listening to my bluetooth headphones, lots of times the podcast just keeps playing uncontrollably. I've started rejecting calls just to quit the podcast, and then call people back, which is terrible! The whole program is quite glitchy and seems to freeze at the end of every podcast--for me at least.
I love the program interface, etc. I just wish it worked better.
I haven't been able to find anything else really. What was the tip about force quitting presto? It doesn't show up in my task manager, am I missing something?
Thanks!
I use Dice Player https://play.google.com/store/apps/details?id=com.inisoft.mediaplayer.a to play lectures at increased playback speed. Works great for that purpose. I dont think it has a podcast downloader ability though, but if you have the files on your phone, this app works great for variable playback
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
I have the same problem, running stock 4.2.2 on my Galaxy Nexus. I think it's a device problem, not an app/background process problem.
I don't use TuneIn so I can't speak to the quality of its streams, but I have used Rdio, Slacker, Pandora and Google Play Music and they all play flawlessly.
ONLY Spotify plays audios with occasional snaps, crackles and pops, like a bowl of Rice Krispies. Some songs will play without a blip, some with a few, some with many. The songs are not interrupted...just marred by this defect. And it's never the same way twice with the same song.
It happens whether the song is streaming, or playing locally.
My guess is that the Nexus has difficulty playing Ogg Vorbis files, which is the format for Spotify streams and downloads. As far as I know, the other services I mentioned stream in AAC or MP3. While the Nexus supports Ogg Vorbis, it appears it does not support it very well. I'm going to test this theory by transcoding one of my Apple Lossless audio files to Ogg and then uploading it to the Nexus. My hunch is that it will demonstrate the same issues.
I guess we should consider ourselves lucky; before Jelly Bean the Nexus suffered from more dramatic playback problems. Do a Google search on "Music Stutters when playing long files and screen off: Galaxy Nexus" and read through it. There are a couple of posts that deal specifically with Ogg playback.
I've decided to live with it. I've been hopping from music service to music service trying to find the right one, and I always come back to Spotify. As long as the issue doesn't become more severe, I think I can re-program my brain to tolerate it.
Skyh said:
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
Click to expand...
Click to collapse
---------- Post added at 11:20 AM ---------- Previous post was at 11:02 AM ----------
My theory was incorrect. I used XLD to transcode Boston's "Hitch A Ride" from Apple Lossless to Ogg Vorbis (VBR, quality 4.0), then put the file on my phone. I used Winamp to play the file and it played beautifully.
So I'm thinking there's something specific with Spotify's encoding that the Nexus doesn't like.
What's odd is that I have run Spotify on other mobile devices and have never had an issue. That's why I have trouble putting the blame on them.
OP, after checking many Google leads, posts, etc. I believe--for Spotify anyway--I have found a way to stop (or at least greatly reduce) the Rice Krispies.
If you have Google Play Music on your phone, make sure it's fully updated and then launch it.
Within Play Music, go to Settings, then select Equalizer.
Turn the equalizer on, select the Normal preset, and move the Bass Boost and 3D Effect sliders all the way to the left to turn them off...unless you like them on.
Back out of Google Play Music to the home screen, then launch Spotify.
Go to Settings within Spotify, choose Audio Effects and verify the Equalizer is OFF in that app.
Using this combination of settings/conditions, I have heard just a couple of pops over a string of a half-dozen songs. I'm keeping my fingers crossed that it lasts.
I'm guessing that having the Google Play Music equalizer on, some additional processing is taking place that alleviates whatever is causing the popping to occur.
Good luck!
So ever since the 4.3 update I've found that all services are dying more and more often. I know this is due to them being killed on low memory (which also seems to be constantly incredibly low for no reason - I don't have loads of apps) but it's so frequent and includes things like Play Music which causes music to stop, restart songs, skip songs, or the app to close without resetting. Is anyone else experiencing this or have suggestions as to what I can do even if just for Play Music, it barely makes it through a song