I've the following issue with CM on my SII and wanted to ask if anyone else has run into a similar issue. I have to connect to conference calls on a regular basis. I call a number and then I have to enter the conference code using the keypad. Both with CM10 and CM11, the numbers I entered are different to what the conference system hears. Even though I see the correct numbers on my phone, the conference system gets a different response. Sometimes digits are repeated, and sometimes digits are missing.
Has anyone else run into this issue?
Note that the same issue with OmniRom on a Samsung Galaxy Note GT-N7000 was described here: http://forum.xda-developers.com/showthread.php?t=2592102 but nobody offered any solution.
I just found this post http://forum.xda-developers.com/showthread.php?t=1712256 (from 2012 with CM 7.2) which suggests that this problem only happens when the headphones are connected. I can confirm that this issue is gone when I disconnect the headphones.
Might this be a hardware issue or is this a problem with CM? Unfortunately, I cannot test with the original Android from Samsung.
Related
Hello
I've just upgraded my phone from native sense 2.2 to CM10 Beta 1, and faced an issue of phone rejecting incoming call without any action appearing on my screen, except adding call data to typed number logs, I mean if i've called to some number before and it is in typed numbers list and that numbers tries to call, he receives rejected phone sound and call information is being added to memory...I think someone else would face this issue but i wasnt able to find any solution through forum...resetting device etc don't help. Upgrade to 10.1 alpha 3 don't help either
I have a Galaxy Nexus (GT-I9250) and a Galaxy S4 Google Edition (GT-I9505G). Both unlocked and rooted.
With JB 4.2.2, the native SIP dialer has always worked very well and I could place and receive calls (using my own Asterisk PBX server) without problems.
With the new JB 4.3 OTAs now, whenever I place or receive a call, the incoming audio is perfect but the outgoing voice sounds terrible: choppy and noisy to a point where the people on the other side can hardly understand what I'm saying.
I flashed both units back to JB 4.2.2 and the problem went away, no matter the configuration or the apps installed.
Conversely, I can always replicate the problem with JB 4.3, clean setup, no additional apps or services.
Anybody else experiencing the same problem? Any idea what might be causing the problem? I cannot believe 4.3 has such a glaring bug, must be me doing something wrong.
Thank you in advance!
Bump
Having the same issue, also using a Galaxy S4 Google Edition (GT-I9505G) on rooted stock 4.3.
If anyone has any info. Thanks!
I opened a ticket with Google 3 weeks ago. Every time I check they keep telling me that they forwarded the issue to the development team but so far I have not heard back from them.
I'm almost certain this has nothing to do with the Samsung Galaxy S4 GPE, and everything to do with the new Android 4.3, since I can replicate the same issue on my old Galaxy Nexus. With 4.2.2 both phones were working fine.
Anybody else experiencing the same issue?
---Mirco.
The same problem is also happening with CSipSimple, so I'm guessing it's not something strictly related to the native Android Sip dialer.
And it has nothing to do with the Sip account either. I can replicate the same problem with my own Asterisk server, but also using a callcentric.com and pbxes.org
Is Android generating a system/debug log every time i place a call?
If so, does anybody know where it's saved?
Hi... Got my one and it is amazing....
But I was aware of this issue - it is not in The One... but in Cyanogenmod
I have Galaxy Note N7000 and have put a lot of custom ROMs on it.
But any ROM that was based on Cyanogenmod.... I could never dial into a conference or an IVR
With any other ROM that was not Cyanogenmod based... it worked fine
e.g. try dialing to any of the banks IVR... when they ask you to press 1 to got to X... 2 to go to Y
Or try dialing to a conference bridge. When they ask for your passcode - even when I enter the correct passcode - it is picked as something else... If I enter 23234589... it is randomly picked as some number... 223349 or something.
Anyone else facing this issue.
I recently rooted my HTC One (m7) and I'm now running ViperOne 7.0.1. I do a lot of conference calls throughout the day and use the app MobileDay to automatically dial the number and conference code. It extracts the 800 number and the PIN conference code from the invitation and separates them by commas (pauses) and dials something like 1-800-555-5555,,,12345.
Since rooting, I've noticed that it dials the conference code (i.e. 12345 after the pause) too fast for each numbers to be registered. I then have to manually enter the PIN. These codes can be 4 to 10 digits long so I have to quickly memorize them and sometimes input them while driving. Clearly this isn't ideal. There is generally no problem dialing the call in number. The only issue is with the pin code. I had this problem when I had CM11 installed as well.
Has anyone else experienced this or have a suggestion as to how I might be able to "tweak" the dialer settings?
bump
No help huh?
I'm not familiar with the app but am fairly solid at troubleshooting. It's hard to think it's an issue with root or a custom rom if it happens on both Sense and CM, being that they are very different, yet the app still has the same issue. Have you tried uninstalling that version and possibly finding an older version of the app to see if it exhibits the same behaviors?
Yeah I have the same issue on CM 12.1
For me, it seems to lose the last few digits of the conference code -- This is pretty infurating
Hi,
my dad brought me his i9100 with some strange problem.
Outgoing calls work fine - everybody can hear the other one
Incoming calls are completly silent - connections is on, timer is running but noone can hear each other.
Tests with different phones (Galaxy s7 edge, Wiko Rainbow Jam) and even my landline telephone - always the same problem
Happens with different firmwares
Now i am at Stock and it is still present.
Tried some 6.0.1, 5.1.1 and 4.4.4 Roms.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-11-t2686887
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-t3356498
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-slimlp-aplha1-t3032958
http://forum.xda-developers.com/gal...dirtyunicorns-v9-3-unofficial-builds-t3111998
i really can't figure it out.
One flash went bad and deleted the IMEI but i fixed it with the EFS Backup but the problem was there before.
Has anyone a solution or idea?
Thanks guys
## edit
after talking to my provider they told me, that is some hardware problem in my area... so it's not phone related