Hey everyone,
Just flashed the newest CM7 RC2 and the in-call volume (from the earpiece) is just way too loud, even at the lowest volume setting. Not sure if it's something with this ROM (I've tried a bunch of the TW varieties and don't remember noticing it) or maybe just my phone?
Any advice or suggestions?
Thanks,
Do u use voodoo sound? And you mean bluetooth right? Or headphones..?
Sent from my SPH-D700 using XDA App
I tried installing voodoo but the CM7 kernel doesn't support it (or viceversa).
And bluetooth is fine, I'm having a problem with the earpiece on the phone itself. Just noticed it on a call today when my bluetooth died.
Same Issue
I am having the same issue with in call volume. Has anyone found a solution? Have reflashed onto the most recent nightly 06/03 of CM7 and have even done a factory reset with no change. Love this ROM as I can get almost 2 days of battery life with it, but the call volume is making my ears bleed.
trent1w said:
I am having the same issue with in call volume. Has anyone found a solution? Have reflashed onto the most recent nightly 06/03 of CM7 and have even done a factory reset with no change. Love this ROM as I can get almost 2 days of battery life with it, but the call volume is making my ears bleed.
Click to expand...
Click to collapse
Not sure if the new nightlies have the fix but according to the change log RC3 had the fix.
http://cm-7-nightlies.appspot.com/?device=epicmtd
http://forum.cyanogenmod.com/forum-545/announcement-23-cyanogenmod-72-rc3-released-2012-may-26/
Running the latest nightly, still same issue. Am I missing anything? I have wiped all and started over hoping that might solve it, but no change.
trent1w said:
Running the latest nightly, still same issue. Am I missing anything? I have wiped all and started over hoping that might solve it, but no change.
Click to expand...
Click to collapse
just try rc3 then you will know if they fixed it or not. my understanding is the nightly might not have the rc3 kernel. not sure how to tell.
tazfanatic said:
Not sure if the new nightlies have the fix but according to the change log RC3 had the fix.
http://cm-7-nightlies.appspot.com/?device=epicmtd
It didn't.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Related
Is anyone else having an issue where the phone mute does not work. I had the mute on earlier but the other person could still here me. I tried again to make sure and it was not working right for me.
Sent from my ADR6300 using Tapatalk
Zepman_us said:
Is anyone else having an issue where the phone mute does not work. I had the mute on earlier but the other person could still here me. I tried again to make sure and it was not working right for me.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I have not had this problem and I've been on multiple builds of MIUI since around April. What kernel and radio are you using?
I've ran incredikernel (the stable one), and both the inc stock radio and the evo radio 04.08 and have had no problems.
One thing I have seen is that you should turn on "Third-party access" in phone settings to alleviate some errors and quirks when it comes to phone. Let me know how it goes!
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...
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
People have been complaining about not being able to hear me during calls. I had someone call my home phone from my cell and the voice sounds extremely muffled and quiet; however, regular voice recorder through a separate apps works fine.
I'm running the latest radio (UVMC6). This problem started while using the ParanoidAndroid ROM. I have since switched to HellyBean but that has not fixed the problem. Toggling noise supression doesn't seem to fix the issue either...any ideas?
only thing i can recommend is try a clean install format system in mounts and storage, and wipe data factory reset, wipe cache/dalvik ,and try to flash the ROM again to see if the problem is still there you pretty much have tried everything which is good. do you remember any ROM where this issue was not occurring ???
krazierokz said:
only thing i can recommend is try a clean install format system in mounts and storage, and wipe data factory reset, wipe cache/dalvik ,and try to flash the ROM again to see if the problem is still there you pretty much have tried everything which is good. do you remember any ROM where this issue was not occurring ???
Click to expand...
Click to collapse
I was using SlimStar before PA and the first few build of PA seemed fine as well. Started happening about a month ago. I did a clean install going from PA to Helly. I'll try it again and see if it works.
Also the new PA roms have been using custom kernels , PAC is really picky the way it boots up and if you don't have the MC6 radio and a certain kernel sometimes wont boot i know this has nothing to do with your issue but just thought I'd let you know. and is just muffled or literally really low volume ??have you tried with headphones to see if this problem is there ??
Seems to happen randomly to some on 4.2.2 roms.
Only thing I can suggest is TW 4.1.2 roms.
Sent from my cell phone telephone
krazierokz said:
Also the new PA roms have been using custom kernels , PAC is really picky the way it boots up and if you don't have the MC6 radio and a certain kernel sometimes wont boot i know this has nothing to do with your issue but just thought I'd let you know. and is just muffled or literally really low volume ??have you tried with headphones to see if this problem is there ??
Click to expand...
Click to collapse
Yea I think its just really low volume. It works fine with heaphones that have a in-line mic I think...
kj2112 said:
Seems to happen randomly to some on 4.2.2 roms.
Only thing I can suggest is TW 4.1.2 roms.
Sent from my cell phone telephone
Click to expand...
Click to collapse
Ugh, TW is so ugly though haha
ThatAzianGuy said:
Yea I think its just really low volume. It works fine with heaphones that have a in-line mic I think...
Ugh, TW is so ugly though haha
Click to expand...
Click to collapse
So use apex and nova launcher to provide an aosp like feel.
sent from my xylonified phone....
kj2112 said:
Seems to happen randomly to some on 4.2.2 roms.
Only thing I can suggest is TW 4.1.2 roms.
Sent from my cell phone telephone
Click to expand...
Click to collapse
Still no dice... Currently running Shadow 1.4 ROM and call recipients still complain about my voice being too quiet/dropping in and out.
Could it be a hardware issue perhaps?
ThatAzianGuy said:
Still no dice... Currently running Shadow 1.4 ROM and call recipients still complain about my voice being too quiet/dropping in and out.
Could it be a hardware issue perhaps?
Click to expand...
Click to collapse
Yup. Bad microphone? Get any water in it? Or a carrier issue...bad signal? I assume you have newest radio...or it wouldn't work at all.
Did you try a couple 4.1.2 roms to be sure. Maybe even try stock....or ics even. Just to be sure.
Did you go into phone settings and check enable noise surpression.
Sent from my cell phone telephone using some sort of app...
Hello! Since I can't post this in Sprint Galaxy Note II Original Android Development until I posted ten times so this is really for CyanogenMod 11 nightlies ROM experts.
I'm using nightly CM11 2/22/14 with plasma kernel. This issue has to do with a headphone jack while plug in and using either Apollo or any other music player. If I open another app the sound goes off but when I close the app the sound comes on. This is also true with using the status bar, when I move the status bar down sound goes off and comes back on when status bar goes back up. The same is also true if the phone goes to sleep.. again sound goes off.
There is no problem with the sound system when I unplug the jack. I haven't had this problem in the past with the Official CM11 ROM. Does this has something to do with nightlies? I tried using Soundabout and other music players but still no luck.
Anyone out there experiencing the same or know how to fix this? Any help would be grateful! Thanks in advance.
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
jplecher said:
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
Click to expand...
Click to collapse
It was the nightly! Seemed to be working fine now! :good:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Sorry just back from vacation... yes still using CM latest nightly 2/24.
Has this problem been fixed in the latest cm11 builds?
Blabah said:
Has this problem been fixed in the latest cm11 builds?
Click to expand...
Click to collapse
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Google Play Music's volume cuts off when Google Hot word detection if ON...
I had the same issue... and have tried multiple CM nightlies with the same result. it was driving me nuts. As soon as i changed to another application Or checked the status bar the sound would mute. You are correct in turning OFF the Google "hot word" detection which turns off "OK Google" as the solution to the problem. Not sure if the problem is on Google's end OR in the CM's Team's ROM?
Thanks,
NH Apache said:
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Click to expand...
Click to collapse
Headphone sound issue fix CM11
I found a fix that worked for me. Install AGNI CM OC kernel. During install, check off the 2nd option for sound engine. Not the one that says '(recommended)'. Worked for me, all is good now.