Music stops after text message

[Lamar720]

When I get a text while listen to music, the music stops and I have to restart my phone to get the music to play again

I have seen a few post with the same problem but, they were told to wipe and reflash. I have tried that 3 times.

Another post said, use Meltus Increase max volume post and I have tried that with version 2.

I'm running Cyan's 3.4 with app2sd ext3.

Thanks

I have posted this question in a few other spots and no one answered it.

[DeadPhoenix]

Instead of Creating a entirely new thread for this issue you should have posted in the Cyanogen Rom thread. Now I have to make fun of you and Report your thread to the mods.


USE SEARCH. POST DEVELOPMENT THREADS IN DEVELOPMENT and MAKE SURE YOU DON'T MAKE DUPLICATE THREADS.


P.S. Reported to merge in appropriate thread.

[Persata]

I'm also having the same problem, however it happens when any other sound plays from a notification. I was originally using Cyan's build too, but moved to TheDudes to see if it made a difference but no dice. Even killing the media process from terminal doesn't help, seems to require a complete reboot.

If anyone has any help it'd be greatly appreciated!

[Lamar720]

Instead of Creating a entirely new thread for this issue you should have posted in the Cyanogen Rom thread. Now I have to make fun of you and Report your thread to the mods.


USE SEARCH. POST DEVELOPMENT THREADS IN DEVELOPMENT and MAKE SURE YOU DON'T MAKE DUPLICATE THREADS.


P.S. Reported to merge in appropriate thread.

Thanks for nothing and wasting pp's time, it has been posted in Cyan thread more than once by myself and others I have also seen it posted in dude's thread. Should I just double post it over on and over. So it don't get pushed back 25 pages?

P.s. I have done searches b4 I posted, that is where I was I read the above solutions that did works.

My search terms were music, music stops, music stops text.

Trying reading the post b4 getting stuff moved

[Lamar720]

I'm also having the same problem, however it happens when any other sound plays from a notification. I was originally using Cyan's build too, but moved to TheDudes to see if it made a difference but no dice. Even killing the media process from terminal doesn't help, seems to require a complete reboot.

If anyone has any help it'd be greatly appreciated!

DEADPhx, this person has dude are you going move his post to dudes? Fake mod
As we can see its not just a Cyans problem.

Thanks again

[gottifour]

I had this problem on JAChero1.4 but now I have switched to Super HERO v.2 and I am not having that problem anymore. Not sure why though.

[blueheeler]

Earlier this week, I gave up on all "Cupcake" releases and flashed back to JFrc33 because of this issue alone.

Then yesterday, I gave Dude's rc2 a try, and everything worked !

I can't tell you what is different about it, but I can tell you the exact steps I took this time because I decided to keep a log so I could replicate the issues and report them if the problem persisted.

Anywayz, here are the steps that worked for me:

NOTE: Instead of using possible corrupted files, I re-downloaded all images and files first. I also erased all partitions on my sdcard and started completely fresh with that too (FAT32 and EXT3 partitions created using Paragon, split script)

1. Flashed back using the original DREAIMG image.
2. Rooted
3. Flashed new HTC radio.
4. Installed Dude's rc version #1 WIPED this time.
5. Logged in. Set ALL appropriate settings for the phone (including the sounds I wanted)
6. NOTED: the problem of an incoming msg or call notification DID stop the music. Almost gave up again but didn't.
7. DID NOT WIPE.
8. Installed Dude's rc2 directly on top of rc1. NO WIPE this time.
9. REBOOTED DIRECTLY INTO RECOVERY and UPDATED RADIO AGAIN !
9. Rebooted my phone, immediately checked the notification/sound problem, and to my surprise, ALL IS WORKING FINE !

Could all of my audio problems for the past 2 weeks have been caused by ...
··· kernel ?
··· different audio script in the rom ?
··· the old bluetooth fixes messing with the radio ?
··· corrupt images/files I used to flash or upgrade ?
··· dirty partitions ?
··· wrong permissions carrying over from flashing different builds ?
··· user (me) error somewhere along the way ?

I can't pinpoint it down. If I could, I wouldn't have had these problems :)

What I can tell you is it's my logical conclusion that MY problems were a combination of user (me) error and a radio issue. I think during all my attempts to fix this on my own by flashing, re-flashing, switching roms, restoring, wiping (and accidently forgeting to not wipe), etc..., it all boils down to the radio! Although I upgraded the radio about a week ago, I think either one of the flashings or one of the recoveries I did overwrote the new radio with the old one. And being the idiot that I am, I never bothered to check to that during my week my flashing hell !

Final summations:
It's all good now + I'm a dumbass for not checking the simple things first=
USER (ME) ERROR

[Lamar720]

Earlier this week, I gave up on all "Cupcake" releases and flashed back to JFrc33 because of this issue alone.

Then yesterday, I gave Dude's rc2 a try, and everything worked !

I can't tell you what is different about it, but I can tell you the exact steps I took this time because I decided to keep a log so I could replicate the issues and report them if the problem persisted.

Anywayz, here are the steps that worked for me:

NOTE: Instead of using possible corrupted files, I re-downloaded all images and files first. I also erased all partitions on my sdcard and started completely fresh with that too (FAT32 and EXT3 partitions created using Paragon, split script)

1. Flashed back using the original DREAIMG image.
2. Rooted
3. Flashed new HTC radio.
4. Installed Dude's rc version #1 WIPED this time.
5. Logged in. Set ALL appropriate settings for the phone (including the sounds I wanted)
6. NOTED: the problem of an incoming msg or call notification DID stop the music. Almost gave up again but didn't.
7. DID NOT WIPE.
8. Installed Dude's rc2 directly on top of rc1. NO WIPE this time.
9. REBOOTED DIRECTLY INTO RECOVERY and UPDATED RADIO AGAIN !
9. Rebooted my phone, immediately checked the notification/sound problem, and to my surprise, ALL IS WORKING FINE !

Could all of my audio problems for the past 2 weeks have been caused by ...
··· kernel ?
··· different audio script in the rom ?
··· the old bluetooth fixes messing with the radio ?
··· corrupt images/files I used to flash or upgrade ?
··· dirty partitions ?
··· wrong permissions carrying over from flashing different builds ?
··· user (me) error somewhere along the way ?

I can't pinpoint it down. If I could, I wouldn't have had these problems :)

What I can tell you is it's my logical conclusion that MY problems were a combination of user (me) error and a radio issue. I think during all my attempts to fix this on my own by flashing, re-flashing, switching roms, restoring, wiping (and accidently forgeting to not wipe), etc..., it all boils down to the radio! Although I upgraded the radio about a week ago, I think either one of the flashings or one of the recoveries I did overwrote the new radio with the old one. And being the idiot that I am, I never bothered to check to that during my week my flashing hell !

Final summations:
It's all good now + I'm a dumbass for not checking the simple things first=
USER (ME) ERROR

Man, thanks for taken the time out to help. Many of us have had this problem for sometime now. I was hoping to Stay with Cyan's Rom (Just got it a few weeks ago)

[Lamar720]

Well, guess what after flashing the new radio to times. I got it to work now. :)

Without having to change my Rom again.

The Newest HTC radio can be found here

http://www.htc.com/www/support/android/adp.html#s3

[DeadPhoenix]

You all seem to be missing the point. If there is a issue that requires technical support You post it in THE DREAM sub section NOT development UNLESS it's about feedback to a particular ROM. YOU do not create a NEW thread to track a issue that is for ROM(S) Unless your planning on Tackling the issue your self AS the DEVELOPER. The Developer Subsection has been overrun with technical support and Threads that are suitable for existing threads. If you don't get a response in the thread TRY PM'ing the Rom Cooker and maybe he can give you a personalized response.

Again I have reported this thread as it does not conform to the FORUM guidelines for posting a new thread.

[blueheeler]

[QUOTE=DeadPhoenix;3993942]You all seem to be missing the point. [QUOTE]


You see, DeadPhoenix, I believe you are missing the point as well.

I realize this is the Developer's sub-forum and it's not for broad technical support, but the problem with that is, sometimes issues arise that need the attention of all the different rom cookers. If we post our questions or problems to each of the different roms that are affected, we would be accused of spamming the board with crossposts. If we post over in the broader Dream (help) sub-forum, then the developers likely won't see that there are issues cropping up with their rom releases.

If you look at the list of possible scenarios I believe might have been causing MY particular problem, you'll see that, at least for me, I was convinced (in the beginning) that it had something to do with either the cooked roms or the audio script that most of the developers have decided to incorporate into the releases. There were other possibilities as well. What resolved this particular issue, I'm not sure. It could have been my error, or it could have been any number of things. But for whatever reason, it's gotten fixed. If, for example, it was the audio script that's been causing a fairly large number of us to have this same problem across different roms, then it does warrant being in this forum because all rom developers need to know that something is breaking.

You need to realize that most of us are not rom or application developers. When we've followed the instructions for flashing and such, when we've searched for answers to no avail, when we've started from scratch and still ended up with the same issue, then our next logical conclusion is the problem lies with the developers and, thus, belongs in the developers sub-forum.

You also need to realize that, like I stated in the beginning of this post, if it is an issue that spans different roms or sources, then it needs to be it's own topic, otherwise it will get posted under 3, 4 or 5 different topics and every time one person replies to that topic, the reply moves the main topic to the top of the list. Would you rather see this one single topic about the audio issue or 7 different main topics getting raised to the top of the list?

I understand the need to keep the board in logical order, uncluttered and on-topic. Don't get me wrong about that. Rules are here for a reason. However, you also have to apply some common sense to the rules as well...

But you are not being of any help at all in any of this. In fact, I dare so you are creating half of the problem, at least for today. At least these are technical issues that are easily moved to another forum or merged with the appropriate topic if it's so required. But you sir are being of no help whatsoever. Furthermore, at least in my opinion, you're the one helping to make the mess out the developer's forum today. If you feel a post is inappropriate, report it to a moderator as a such. They are our thought police around here.