Since moving to the CM 11 nightlies, I have have been experiencing an issue where randomly, notification/alarm audio will stop working completely until a reboot. This has obviously been a little troublesome since I use my phone as my alarm clock - and to not have the sound go off in the morning because the phone decided to stop making noise in the middle of the night is a pain (I've at least fixed this by setting the alarm to vibrate as well.)
Has anyone else experienced this issue, and does anyone have any recommendations on how to fix? This has persisted across multiple nightlies, both via updated and wiping/reflashing. Thanks.
Better Create a Bug on CM Website.
Demodokos said:
Since moving to the CM 11 nightlies, I have have been experiencing an issue where randomly, notification/alarm audio will stop working completely until a reboot. This has obviously been a little troublesome since I use my phone as my alarm clock - and to not have the sound go off in the morning because the phone decided to stop making noise in the middle of the night is a pain (I've at least fixed this by setting the alarm to vibrate as well.)
Has anyone else experienced this issue, and does anyone have any recommendations on how to fix? This has persisted across multiple nightlies, both via updated and wiping/reflashing. Thanks.
Click to expand...
Click to collapse
CM is known for audio issues, mainly on nightlies. Stable versions don't usually have those problems. I've never heard of this particular one though. Are you running any other mods or tweaks? Xposed, root apps, different kernel than the "stock" CM one? Or anything you have to flash via recovery?
NickWhit1992 said:
CM is known for audio issues, mainly on nightlies. Stable versions don't usually have those problems. I've never heard of this particular one though. Are you running any other mods or tweaks? Xposed, root apps, different kernel than the "stock" CM one? Or anything you have to flash via recovery?
Click to expand...
Click to collapse
Nothing special, only things I flash are the CM ROMs themselves and the appropriate gapps. In terms of root apps, just the usual (titanium, helium, superuser.) I'm going to do a complete wipe and reflash when the next stable Kitkat build is released and see if the issue persists. If it does at that point, then maybe I think a bug might need to be created.
Related
So i installed 7.2.0RC1 on my desire and it worked perfectly for 2 days but i've noticed this morning that when im getting calls or messages the phone isn't making a noise and notifying me of this.
I checked that I wasnt accidently on silent and I wasnt, so checked volumes, all ok, and then I decided to look at the ringtones and select a different one and where each one is supposed to give you a little preview of the tone im getting nothing.
Im really at a loss, has anyone else had this problem or knows how to solve it, its handy being made aware when someones trying to contact me
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
stankyou said:
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
Click to expand...
Click to collapse
Tried rebooting and still nothing off previews or anything, its just kinda weird for a RC for this to happen, might have to go back down to 7.1.0 until the bugs are ironed out, thank god for nandroid.
Still might have a solution pop up here before i get round to doing that
Did you modify the rom? Change or remove ringtone files you don't need?
Even I had same problem various times. Rebooting solves the issue everytime.
I didn't modify the rom at all and rebooting doesnt solve it, come to think about it, its happening since i used a pair of headphones for the first time
Do you use any Bluetooth headset? Usually when I use mine it happens what you have described and the only quick fix was to make a reboot. I didn't tested it yet on CM7.2 RC1 but the issue was present in CM7.1 Stable.
I use Rings Extended, it`s perfect
Today I tested the CM7.2 RC1 ROM with my Bluetooth headset and so far it is working with no problems (no sound issues like you mentioned). Now I just have to see if it would also stay this way in the few days.
I also found that some users had the problem described in the first post when they were using usual cord headphones but so far I hadn't experienced any problems with them although I'm suing them almost every day since the CM7.2 RC1 ROM release day.
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app
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
So I have a CM 10.2 on my T989 Hercules for a while, and since couple of days every time I pickup the call or try to call back I can't hear jack sh*t unless I reboot the phone. Is this something that can be fixed or should I be looking for a new ROM ? There is so many of them I'm getting confused :silly:
i have this issue as well, but i am using pa 4.6 beta 1. any fix to this?
same problem here on mine and my girlfriends phones (Hercules) on either CM10.2 or PA 4.6 beta. restarting didn't help for the CM but did on the PA rom. only thing is, I don't know whats causing it. my phone could ring and when I answer I hear nothing and they don't hear me and vice versa when I call out. yes, both were clean installs on both phones with double wipes before flash with either roms.
Same Issue!
I am actually getting the same exact issue, at times I cannot hear anything on either end and the only remedy is to reboot and it only fixes it for a little bit.
Anyone know anything about this?
I've no issue with PA 4.5 Beta 1 (most stable in my case) nor 4.4 Final. Ran into the same issue with 4.5 Beta 4 once tonight but I was playing with disabling google play services and install the new Hangout.
I am curious too...anybody have a working solution yet?
I feel I've run into this problem before on jb. I'm curious to know which BASEBAND in installed on your devices.
I think there is a newer radio (modem) needed for jellybean and odd sound/wifi/data issues arise if you're using an older radio.
I'm using UVMC6 on CM11.
http://direct.xda-developers.com/wiki/Samsung_Galaxy_S_II/SGH-T989/Radios
I just flashed CM11 ROM from Sultanxda on my 2 T989's I have. One is having this issue the other is not. They were purchased at the same time. Not sure why this is happening. I have also had this issue on the previous CM10.2 version.
I have updated the Radio on the one that didn't work, but alas it still does not fix it. If the phone is rebooted, it magically works for a while.
I'm hoping that @Sultanxda will have a look at this issue.