[Q] CM7 Nightly (build 261) randomly pauses on Google Music - Desire Q&A, Help & Troubleshooting

All of a sudden, whenever I listen to any music now, every now and again it will randomly pause.
I noticed as I was on my 50 minute walk to sixth form, suddenly it paused. I assumed I had accidentally pressed a button, but it kept happening again and again. I haven't changed anything about my phone, I haven't installed any new software between now and before it started happening...
I've tried the stock Music app and it seems to happen on that too.
Please help, this is a very frustrating problem as it will pause about 4-8 times in that 50 minute walk!
I was going to move to the alpha ICS ROM but it doesn't work with Google Music
EDIT: I don't have Google Listen installed

You can try this,there is also an app on the market which does the same.

erklat said:
You can try this, there is also an app on the market which does the same.
Click to expand...
Click to collapse
It's only just started happening though, I'll try that though just in case.

Also nightlies are EXPERIMENTAL and UNSUPPORTED releases of cyanogenmod... you should expect something to be wrong with them

bortak said:
Also nightlies are EXPERIMENTAL and UNSUPPORTED releases of cyanogenmod... you should expect something to be wrong with them
Click to expand...
Click to collapse
Yes I do know that.
That does not mean I cannot ask questions and try to understand the problem.
After all it may present a solution that could work for many other people...

Okay well the SD thing didn't work, and neither did doing a full wipe and flashing a new rom...

This isn't a CM7 issue; my stock galaxy nexus does this.

silverkiller said:
This isn't a CM7 issue; my stock galaxy nexus does this.
Click to expand...
Click to collapse
I did not want to hear this! I get my GNex in 3 days!

Related

[Fixed] No sound on CM7.1 RC

Hello there,
I've just installed RC1 on another Wildfire than mine (I've already installed it on mine) and I can't make that phone ringing when calling it. I checked all profiles (it's set on default and I enabled everything in that default profile ; I deleted other 'pre-installed' profiles such as "work", etc.), all sound settings but I don't see what I missed there
I can't even play songs with the default "Music" apps!
Any idea please?
Try restarting your phone.
I restarted it. Sound is now working but... if I wanna choose any of the default ringtones, it's always the same sound. I also retried the "Music" app, and I only have some beeps going on and off, the songs don't play.
Do you think a reinstallation of the ROM will solve it for good?
Yes, try reinstalling after a full wipe. I distinctly remember someone else having similar issues, but I am unable to locate that post anymore. It's buried somewhere within the hundreds of pages of the CM thread :/
All right, I reinstalled the ROM and it's all working again! Thank you both for your help!
It works
Just rebooting worked for me. :]
Not to resurrect a dead thread, but I am having this issue intermittently. Once every few days the sound will just stop. No music, no ringers… A reboot fixes it for a while though.
This is 7.1 stable on a Dinc.
BloodBlight said:
Not to resurrect a dead thread, but I am having this issue intermittently. Once every few days the sound will just stop. No music, no ringers… A reboot fixes it for a while though.
This is 7.1 stable on a Dinc.
Click to expand...
Click to collapse
As previously advised Please flash a fresh install and then report....
BloodBlight said:
Not to resurrect a dead thread, but I am having this issue intermittently. Once every few days the sound will just stop. No music, no ringers… A reboot fixes it for a while though.
This is 7.1 stable on a Dinc.
Click to expand...
Click to collapse
Have you tried turning camera shutter sound off?
That was an old problem we had on wildfire.
Sent from my Wildfire using xda premium

[Q] No haptic feedback ("vibrate on touch") in Galaxy Nexus

Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...

4.2.2: Bluetooth won't turn on

OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...

[Q] Broken Sound? [WORKAROUND FOUND]

NOT SOLVED YET
Recently I have been having a problem with my gs3 (d2att version). For some reason whenever I have headphones plugged in and I play music, my sound stops for a brief second whenever I touch the screen. It sort of turns off back on very briefly but its incredibly annoying. It first happened on Carbon ROM 1.5 and then I installed CyanogenMod Nightlies and it happened right after the fresh boot, now I tried Liquid Smooth Stable. They all are doing it. It happens whenever I open apps or like the app drawer or anything in the browser. It doesn't always happen, like when I press the keys on the keyboard it doesn't do it.
Is this a 4.2.2 problem? I feel I would have seen more if that's it. Also I have tried multiple music apps (apollo Google music and one more) and multiple head phones and aux cables.
Please let me know if anyone has any way to fix this or needs more information to solve this. Thanks.
aeppacher said:
Recently I have been having a problem with my gs3 (d2att version). For some reason whenever I have headphones plugged in and I play music, my sound stops for a brief second whenever I touch the screen. It sort of turns off back on very briefly but its incredibly annoying. It first happened on Carbon ROM 1.5 and then I installed CyanogenMod Nightlies and it happened right after the fresh boot, now I tried Liquid Smooth Stable. They all are doing it. It happens whenever I open apps or like the app drawer or anything in the browser. It doesn't always happen, like when I press the keys on the keyboard it doesn't do it.
Is this a 4.2.2 problem? I feel I would have seen more if that's it. Also I have tried multiple music apps (apollo Google music and one more) and multiple head phones and aux cables.
Please let me know if anyone has any way to fix this or needs more information to solve this. Thanks.
Click to expand...
Click to collapse
Does it happen out of fresh/clean flash? Before you restore anything that is.
BWolf56 said:
Does it happen out of fresh/clean flash? Before you restore anything that is.
Click to expand...
Click to collapse
Yes, I can download any old app from the play store the moment I finish the flash and it does it
aeppacher said:
Yes, I can download any old app from the play store the moment I finish the flash and it does it
Click to expand...
Click to collapse
Umm, it's a really odd issue. Perhaps try changing your gov/scheduler. I think it needs a little bit more performance to work fine.
BWolf56 said:
Umm, it's a really odd issue. Perhaps try changing your gov/scheduler. I think it needs a little bit more performance to work fine.
Click to expand...
Click to collapse
I tried changing clock, governor, and IO scheduler, no change :/
Re: [Q] Broken Sound?
I've been having the same issues with CyanogenMod and AOKP, but I am on liquid and it seems to be working fine right now. Not sure why it is happening.
Sent from my SGH-I747 using Tapatalk 2
HBSN11 said:
I've been having the same issues with CyanogenMod and AOKP, but I am on liquid and it seems to be working fine right now. Not sure why it is happening.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
So i tried flashing stock ROM which fixed it, but when I went back to a 4.2.2 ROM it broke it. Can anyone else confirm they are having his crackle/pop sound on 4.2.2 ROMs? Also what Liquid are you running?
Re: [Q] Broken Sound? [NOT SOLVED YET]
aeppacher said:
So i tried flashing stock ROM which fixed it, but when I went back to a 4.2.2 ROM it broke it. Can anyone else confirm they are having his crackle/pop sound on 4.2.2 ROMs? Also what Liquid are you running?
Click to expand...
Click to collapse
It was working before. But it just started cracking again. Its weird. I have tried a bunch if different music players too and am still having the problem.
Sent from my SGH-I747 using Tapatalk 2
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
A quick fix for now is to just turn off touch sounds in Settings/Sound. Seems to work okay right now.
Sent from my SGH-I747 using Tapatalk 2
Re: [Q] Broken Sound? [NOT SOLVED YET]
I had this problem too on the 3.17.13 aokp. Just turned off touch sounds like someone suggested and it works fine.
Sent from my SGH-I747 using xda app-developers app
Andrew9mb said:
I had this problem too on the 3.17.13 aokp. Just turned off touch sounds like someone suggested and it works fine.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Was just about to post this, thanks.
Turning off your touch sound fixes it.
BWolf56 said:
Was just about to post this, thanks.
Turning off your touch sound fixes it.
Click to expand...
Click to collapse
Not entirely. If you have touch sounds and play certain sounds like volume changing and notifications still cause it to crack. Even if you disable every sound under the sound menu you will hit the crackle every now and then.
EDIT: it works on tasks AOKP of you disable touch sound, doesn't work on Cyanogenmod

Urgent and Serious issue with audio! HELP needed. please!

Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
this thread can be referred for more details on this issue:
http://forum.cyanogenmod.org/topic/81373-audio-stops-working-from-time-to-time/
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
s.vivekananda007 said:
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
Click to expand...
Click to collapse
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
BWolf56 said:
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
Click to expand...
Click to collapse
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
s.vivekananda007 said:
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
Click to expand...
Click to collapse
I don't suggest ROM to avoid flaming but you can look in my sig
BWolf56 said:
I don't suggest ROM to avoid flaming but you can look in my sig
Click to expand...
Click to collapse
Hey it got fixed in the latest nightly ( cm-11-20140721-NIGHTLY ). I had put it in cyanogenmod forum, I guess they read the issue and fixed it. Audio is perfectly fine now! Feels so great to use cyanogenmod again.
Thank you cyanogenmod!
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
gsm22 said:
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
Click to expand...
Click to collapse
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
s.vivekananda007 said:
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
Click to expand...
Click to collapse
Thanks for the suggestion, I may as well give it a try since most everything else I've tried has had the same issue.
edit:
Clean flashed latest CM nightly, sound worked for around 2 minutes, then stopped when I plugged headphones in. Rebooted, got it to work via speakers again but then DSP manager force closed and left me without sound.
Rebooted into recovery, cleared cache, still no dice.
Going to try another clean flash to see if I can get sound to last a while longer.
edit 2: It seems to be screwed completely now, no sound after install + reboot.
Same logcat lines as in http://forum.xda-developers.com/galaxy-s3-att/help/audio-wide-custom-roms-t2825135

Categories

Resources