[Q] What's up with my ROM?? - EVO 4G Q&A, Help & Troubleshooting

Alright so I have been rooted for over 6 months and I've tried out all the ROMs there are. I finally decided on Deck's 1.3 for it's smoothness and lack of bloat. Here is how I have it set up:
Timat 4.1 + SBC kernel
Car-o-dopes tweaking
launcherpro
underclocked to about 850 mhz
No crazy themes or anything as I like speed over anything. BUT... I have been getting two problems lately: When I listen to music it will stop there will be some harsh static sound, then it will play again. This happens all the time, but more often when I'm multitasking. And the other problem is after I leave my phone for awhile it won't turn on! This happens if I leave it for more then an hour, or if I am watching youtube vids on it where I haven't touched the phone in awhile.
I have wiped both caches and fixed apk mismatches. Can't figure out what else to do. Any ideas??

I just flashed to Salvaged-Zen, and it now only makes the music stutter when I'm downloading large files at the same time. The wake issue is fixed however!

what app are you using to listen to music?
i ask because i use Power Amp, and i have noticed the same behavior only when i listen to certain files, i determined that the files were some how corrupted. i replaced the files with new rips off my CD and they do not do it anymore.

I haven't noticed a difference from songs gotten from iTunes or the market or ripped CDs. So I don't know if that's it. I use the stock music player

got it!
Finally figured it out. I flashed a CFS kernel (I was using a BFS). It stopped all the problems with the music. Makes totally sense because music is a background task

Related

Sense Music tab stops playing after a short time

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 =/

[Q] All non-CM6 users - did today's Pandora update fix your sound quality?

Pandora pushed out an update today. I haven't been able to test it yet, but supposedly it resolved sound quality issues on 2.2. If you never noticed the sound quality issue before, please don't reply, but for those people who have been going nuts about this, have you been able to test it yet? And if so, what rom are you on, and what results did you get?
And the reason I'm leaving out CM6 users, is because Cyanogen implemented the official google fix in his latest nightly build (which only works on AOSP builds)
I have an hour commute to work everyday. I usually use Pandora during the drive. Lately Froyo totaly screwed this adventure up. Until totay's update by Pandora. I don't think its quite 128k however its a lot better than it was. Big ups to the Devs at Pandora for the improvement. Now as far as any other music set ups, ie mp3's and other streaming audio, I dont know.
DGS-07 said:
I have an hour commute to work everyday. I usually use Pandora during the drive. Lately Froyo totaly screwed this adventure up. Until totay's update by Pandora. I don't think its quite 128k however its a lot better than it was. Big ups to the Devs at Pandora for the improvement. Now as far as any other music set ups, ie mp3's and other streaming audio, I dont know.
Click to expand...
Click to collapse
Awesome! Thanks - on my end I only heard the snap, crackle, and pops during some songs, and I wasn't sure if it was fixed, or if I just hadn't gotten to a song where I would have been able to tell the difference. The rom I'm using had a temp fix (set to true), so Pandora wasn't as bad for me as it was for some.
Thanks again!

[Q] Google music (v4.0.9) stutters when phone asleep

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.

[Q] Do you have problems with Google Music/other Music apps?

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)

Music skipping, choppy etc

Hey everyone I recently flashed miuiv4 beta 1 I believe it was last night and I liked it (too much) so I made a nandroid back up of it and restored the nandroid I had for the people's rom v2 mtd I was running before. This isn't too big of a deal but I wanted to see if there were anything I could do to remedy it. I've been playing music and it'll start skipping and my entire phone will start getting all choppy when I'm trying to type or click on something etc.. it doesn't do it constantly but I think it's starting to do it more frequently. Again not a huge thing just a Tad annoying. The apps I'm using for music are mostly the modded Pandora I found somewhere on here and playerpro. Sorry if this is beyond noobish lol and thanks in advance for any help.
Sent from my SPH-D700 using XDA
Don't worry I had the same problem when I flashed MiuiV4 as well
Sent from my SPH-D700 using XDA Premium App
My music skips as well, i'd like to know if there is a fix, or just the downside of having a AOSP rom, currenly running MIUI, I haven't had a TW rom in awhile..
Sent from my SPH-D700 using xda premium
power amp?
if you willing to spend the money power amp is by far the most powerful user friendly music app and in the settings you can change the audio buffer and the music thread priority i recommend leaving that one alone and raising the audio buffer to large.
I thought this was a problem with all ICS Roms. I use Spotify and my music gets choppy whenever my radios change. For example at home it will work well on wifi, as soon as I leave the house and am out of wifi range it switches to 3G and the music gets choppy. Whenever I'm out and the radio switches to 4G the music gets choppy as well. I thought it was fixed in CM9 beta 2 but I started getting it a lot more after 2 days of flashing it.

Categories

Resources