call volume in liquidsmooth rom - Sprint Samsung Galaxy S III

To start off I apologize for posting this here instead of the development thread. I don't have 10 posts so I am unable to do it. I recently flashed Liquid smooth ROM onto my S3 only issue I have aside from voice not working which I can tolerate but in call volume is rather quiet and can't be adjusted what so ever. The issue was mentioned in the development thread but wasn't responded to at all. If anyone can help me it would be appreciated

try this
Lieblos said:
To start off I apologize for posting this here instead of the development thread. I don't have 10 posts so I am unable to do it. I recently flashed Liquid smooth ROM onto my S3 only issue I have aside from voice not working which I can tolerate but in call volume is rather quiet and can't be adjusted what so ever. The issue was mentioned in the development thread but wasn't responded to at all. If anyone can help me it would be appreciated
Click to expand...
Click to collapse
Have you tried going into settings => Advanced => Sound => and check off extra gain in voice calls?

sandman795 said:
Have you tried going into settings => Advanced => Sound => and check off extra gain in voice calls?
Click to expand...
Click to collapse
Yes the call volume is not adjustable what so ever. I tried lowering all the volumes then back up but nothing.

Was running it today and noticed that as well. I'll see if I can find anything about it.
Sent from my SPH-L710 using xda app-developers app

I talked to the Dev and he said it's a common problem with d2.

I believe the latest CM10.1 nightly just fixed this. Give the dev some time to incorporate all the audio fixes from CM10.1 into his ROM.

Related

Cyanogenmod 10.1 i747 Bug List (Updated Daily)

Please post any bugs you experienced and what nightly they are found in. This is going to be updated daily starting with the 1/06 nightly. PLEASE check if someone already posted the bug so repeats are minimal. This thread is also intended to be a place to discuss workarounds and fixes for bugs.
Nightly: 2/21
Confirmed Bugs:
-Bluetooth issues (media streaming and calls)
-random bug where everything is taken as a long press
-Occasional flickering (very rare)
.........-FIX: Ktoonsez 4.2.1 Kernel 1/1 Build. Download link: goo(dawt)gl(slash)xUrML
........ -FIX2: disable HW overlay in developer options
-terminal emulator and movie studio force close
......... -FIX: delete then install from Play Store
-Hotspot issues
......... -FIX: use SVTP
-Visual voicemail issues
-Pandora keyboard issue
Unconfirmed Bugs:
-MMS issues (works on and off)
-First few seconds of songs in Apollo are louder than normal.
-screen mirroring
-dock audio
-WiFi stability problems
-Notification light does not work with unread text messages once the screen has timed out.
-When pressing the power button to turn screen off, there is a delay.
Resolved Bugs
-echo when calling using speakerphone
-Quiet in-call volume
-ringtone is distorted when on full volume
-screen flickers when changing volume in YouTube, Google Music, browsers, and some other apps
-delay for the other person to hear you when your answer the phone call
Add This One
Bug:
1) EXTREMELY quiet in-call volume, both with the front facing speaker and the rear speaker phone. This affects all 4.2 AOSP ROMs.
And just so the people who don't search can see it as well :
2) Bluetooth does not work for streaming media, and is flaky for calls
3) Screen flickering in Gallery - hard to recreate on-demand but is definitely there in the Gallery and some other apps. Can be fixed (mostly) by using Ktoonsz's 4.2.1 kernel ( I have had the best results with the 1/1 test release and can provide a link if needed). Disabling HW Overlay on Developer Options can help most cases of this
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jakew02 said:
Add This One
Bug:
1) EXTREMELY quiet in-call volume, both with the front facing speaker and the rear speaker phone. This affects all 4.2 AOSP ROMs.
And just so the people who don't search can see it as well :
2) Bluetooth does not work for streaming media, and is flaky for calls
3) Screen flickering in Gallery - hard to recreate on-demand but is definitely there in the Gallery and some other apps. Can be fixed (mostly) by using Ktoonsz's 4.2.1 kernel ( I have had the best results with the 1/1 test release and can provide a link if needed). Disabling HW Overlay on Developer Options can help most cases of this
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I appreciate your help.
farice said:
Thanks, I appreciate your help.
Click to expand...
Click to collapse
I run the CM nightlies and update every morning before , so I'll keep updating that post for ya as I find new stuff to report
Also, here is a link to ktoonsez's post with the 1/1 experimental kernel
http://forum.xda-developers.com/showthread.php?p=36156163
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jakew02 said:
I run the CM nightlies and update every morning before , so I'll keep updating that post for ya as I find new stuff to report
Also, here is a link to ktoonsez's post with the 1/1 experimental kernel
http://forum.xda-developers.com/showthread.php?p=36156163
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I can't post links yet because I just made this XDA account, but I will add it ASAP.
of wsnouk
I have encountered the unconfirmed screen flicker when using google music, also have encountered the delayed time for answering a call. I've also encountered a couple random restarts not too sure what its from but happened earlier today when using facebook messenger the app just froze then device restarted I'm on 01.04/13 build with stock kernel
Can someone elaborate on the quiet in call volume? Is it quiet for send or receive or both? Does it effect earphones?
Does MTP work?
I switched from a cm10 daily to cm10.1 (01/3) and when I plugged my phone into my computer nothing happened, but the phone started charging.
Also, when I went into recovery because the SD card had changed locations, I could not restore to my cm10 back up. Anyone else have these problems?
Penguyen said:
Can someone elaborate on the quiet in call volume? Is it quiet for send or receive or both? Does it effect earphones?
Click to expand...
Click to collapse
The low volume only affects you, not the person on the other end. It happens with both the front facing speaker and the speaker phone on the back next to the camera. However, while your on speakerphone the mic sensitivity is not very good so the other person will find it harder to hear you unless you have your mouth right next to the mic. It'll be worked out soon enough.
buckfritzl said:
Does MTP work?
I switched from a cm10 daily to cm10.1 (01/3) and when I plugged my phone into my computer nothing happened, but the phone started charging.
Also, when I went into recovery because the SD card had changed locations, I could not restore to my cm10 back up. Anyone else have these problems?
Click to expand...
Click to collapse
Android 4.2.1 creates an "emulated" storage system to help manage the multiple user idea. Being the main user (user 0) will have their files stored in /0. User 1 will be in /1. It really isn't practical for a cell phone it was more designed for multi user tablets and I'd not fully incorporated yet as far as I know. However, you will need to boot back into the ROM and move any backup files to your /0 directory and then you'll be able to see them. I'd recommend copying instead of moving them there just so you have more than one place to check while in recovery. Regardless your files are all there they just have to be moved to the proper directory on the SD card.
Also, switch to the latest TWRP recovery so you don't end up with multiple /0 folders within themselves
2nd topic on your post. No 4.2.1 or touch wiz ROMs support UMS , or USB mass storage. The only ones that did were CM / AOSP 4.1.s based
farice said:
Unconfirmed Bugs:
-ringtone is distorted when on full volume
-screen flickers when changing volume in YouTube and some other apps
-delay for the other person to hear you when your answer the phone call
Click to expand...
Click to collapse
I can confirm, along with many others running CM10.1 nightlies, Tasks AOKP builds, and all the other 4.2.1 ROMs that the ringtone is distorted when on full volume for music/videos/media and ringtones. And there is a delay after answering for about 5 seconds.
---------------------------------
This thread is good. We need to get into contact with one of the d2 device maintainers for CM to check this out once we get a few more into the confirmed category. They didn't know about the mobile data issue that was present until the 12/29-12/30ish nightlies for a while because I don't think anyone had been reporting anything to the CM team other than posting in the thread here
jakew02 said:
This thread is good. We need to get into contact with one of the d2 device maintainers for CM to check this out once we get a few more into the confirmed category. They didn't know about the mobile data issue that was present until the 12/29-12/30ish nightlies for a while because I don't think anyone had been reporting anything to the CM team other than posting in the thread here
Click to expand...
Click to collapse
I agree, we should definitely do that. I think this will be a very helpful resource for CM developers and modders eventually.
a. when using the speakerphone my voice echoes to the person on the line
b. terminal emulator force closes. have to remove and install from market
farice said:
Please post any bugs you experienced and what nightly they are found in. This is going to be updated daily starting with the 1/06 nightly. PLEASE check if someone already posted the bug so repeats are minimal. This thread is also intended to be a place to discuss workarounds and fixes for bugs.
Nightly: 1/06
Confirmed Bugs:
-Quiet in-call volume
-Bluetooth issues (media streaming and calls)
-Occasional flickering (much rarer than in previous builds)
.........-FIX: Ktoonsez 4.2.1 Kernel 1/1 Build. Download link: goo(dawt)gl(slash)xUrML
........ -FIX2: disable HW overlay in developer options
-ringtone is distorted when on full volume
-sound distortion/low sound quality on full volume for all media
-screen flickers when changing volume in YouTube, Google Music, and some other apps
-delay for the other person to hear you when your answer the phone call
Unconfirmed Bugs:
Click to expand...
Click to collapse
I get the flicker when changing volumes in browser apps.
1/07 Nightly is up. Are all of these bugs still present? I'm in the airport about to leave, so I can't confirm myself until tomorrow. Thanks everyone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
For those using the latest nightly, was the data bug fixed?
I'm on an ATT S3 and switched a few days ago because the data drops were driving me nuts.
inkblaze said:
For those using the latest nightly, was the data bug fixed?
I'm on an ATT S3 and switched a few days ago because the data drops were driving me nuts.
Click to expand...
Click to collapse
I don't have any data issues
Randomly missing Group MMS.
Sometimes I get them and sometimes I don't. Sometimes I get a notification and no message, sometimes I get the message fine, and sometimes I get no notification or message.
Edit: Ignore sig, I need to fix that...
Home button randomly bugs out and starts going to the app switcher rather than homescreen. Annoying, but restarting phone fixes it.
I've noticed the same problem, but I also find that the menu soft key bugs out and opens up Google Search/Now without long press. Might be like something is turning the behavior of one touch on these keys into automatic long presses? And its not just the specific launchers (I'm using Apex)...I tested with others. Really annoying, but restarting the phone does provide a temporary fix.
1.Sometimes when playing music using Apollo, the first 3 seconds of the song ,after song change, would be louder than normal. (Happens with YouTube too)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Alright everyone the 1/9 nightly is up. There were several fixes merged to correct in-call volume all, and call echo while on speakerphone. If a majority rules saying it is now fixed, let's move that bug to the "resolved" section
Sent from my SGH-I747 using Tapatalk 2

problems with aokp 4.2.1

hello I am having some problems with 4.2.1 I am under rogers and when I flash the aokp it works but when I make calls and I use the speaker phone it is quiet I cant hear ppl at all and when I put the stock one in its louders on the speaker phone and the head speaker is there a fix or am I doing something wrong
I believe it is a 4.2 issue, so no matter what rom you are running, volume will be low. Sounds like it might be fixed shortly. Will just need our wonderful developers to incorporate into their roms.
ed20910 said:
I believe it is a 4.2 issue, so no matter what rom you are running, volume will be low. Sounds like it might be fixed shortly. Will just need our wonderful developers to incorporate into their roms.
Click to expand...
Click to collapse
okay thanks
is there away to downgrade something to make it work my buddy has it it works better then mine
mobflight101 said:
is there away to downgrade something to make it work my buddy has it it works better then mine
Click to expand...
Click to collapse
You should try and read the OP of my thread. You would then realize that that issue was fixed.
Update to today's latest build. The low, in call volume has been fixed. Also, please read the change logs that accompany each release as they often address issues, such as the one you've mentioned.
now how about the led to flash I turned it all on and it doesn't flash at all and I cant seem o get the lte to work

AOSP CM10 DTMF issue ie touch tone menus

Noticed on CM10.1 4.2.1 4.2.2 ROM's that when you call into voicemail or banking menu that requires you to press the dial pad to enter in menus options and account number info doesn't work.
I was able to fix it by turning dial tone touch sounds off in the dialer options. Just thought I'd let you all know in cause someone else is having this issue since a Google search brought up really vague results.
Hope I posted in the right place. Move if needed.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Actually, they work with the tones on. You just need to press and hold the keys a little longer to allow the other end to capture the tone.
BlackPhantomX said:
Actually, they work with the tones on. You just need to press and hold the keys a little longer to allow the other end to capture the tone.
Click to expand...
Click to collapse
That was the first thing I tried.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I had same problem with liquidsmooth 2.1 RC2, and disabling touch sounds fixed the problem. However now that I upgraded to liquidsmooth 2.1 stable, the workaround does not work anymore. Neither does holding button, it's a set DTMF tone length. my voicemail is useless now. anyone have any idea on how to solve this problem?
UPDATE:
I did some more research, and the only thing I can think is the standard aosp phone.apk is used in both roms. I did find a feature request for it. (URL Below) So let me get this straight, my new phone cant dial a voicemail? or use a touch tone menu for calling tech support?
I would post this in developer forums, as there has been many questions lately about this problem, but I'm not allowed because I'm a noob. Guess I won't find a solution to this problem anytime soon. Seems I cant post links either......
***ttps://code.google.com/p/android/issues/detail?id=1428
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] Very Loud In-Call Volume - Please Help!

Hello everyone,
I've been a member of XDA for many years, but since I don't post much, I have to ask my question here, so I apologize in advance.
I am currently using the AOSP ROM - 4.2.2][OFFICIAL] LiquidSmooth v2.8 - d2spr - 07|01|13. Great ROM, I love it. But since the v2.7 build, the in-call volume has been SO LOUD. And trying the fix of maxing out the in-volume, then turning it all the way back down doesn't help either. I did a full wipe yesterday when I upgraded to v2.8, but unfortunately the issue continued. All of the other previous versions of this ROM never had this issue, so I can't figure out why all of a sudden with the last two, it's starting now?? I know this isn't a new issue with AOSP ROMs, and I've had this issue sometimes on other ROMs in the past, and the volume up/down fix worked, but like I said, I can't figure out why it started up again all of a sudden.
ANY HELP WOULD BE GREATLY APPRECIATED. Thank you in advance!
PS - And yes, I have searched that specific ROM thread, and other threads, and the Internet as well. Never found anyone with my exact issue of it happening later on in the same ROM.
Have you tried something like Volume Control from the market?
jdelano said:
Have you tried something like Volume control from the market?
Click to expand...
Click to collapse
Hi, thank you for your reply and suggestion, but yes, I have, & that didn't do anything. It didn't/couldn't lower the in call volume lower than the system default.
Do you have any other suggestions please?
dj84 said:
Hi, thank you for your reply and suggestion, but yes, I have, & that didn't do anything. It didn't/couldn't lower the in call volume lower than the system default.
Do you have any other suggestions please?
Click to expand...
Click to collapse
here is a post in the ROM thread talking about this issue
http://forum.xda-developers.com/showpost.php?p=43500992&postcount=2738
they switched kernels and then back again and that seemed to rectify their problem
good luck

[Q] Problem with proximity sensor L900 with CarbonROM

Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
thaittnguyen said:
Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
Click to expand...
Click to collapse
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
tx_dbs_tx said:
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
Click to expand...
Click to collapse
No I didn't find any fixes for it. I talked to one of the developers and they are looking into it BC when I entered the live chat I asked the same question and they responded with "let me guess, note 2?"they're not sure what's going on with the notes that is causing the bug. But I've been looking at the change logs hoping they fix it and my phone volume is really low when I'm talking to someone as well. Sometimes I can't even hear the caller so I have to switch to speaker :/
Thanks for the reply. As for the low volume during calls. You may already know this but try lowering the volume then raise it back up and that should increase the volume a lot. It's a bug in some AOSP ROMS.
I have tried that and sometimes it works and sometimes it doesn't, unfortunately.
Sent from my SPH-L900 using xda app-developers app
The proximity sensor issue has been fixed in the latest nightly build 4-23. Although now I can't sync my browser in Google account sync settings. All others seem to sync except browser. Could be another bug...

Categories

Resources