[Q] Native SIP dialer in Android 4.3 - Android Q&A, Help & Troubleshooting

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?

Related

Problems with google voice on CM7 Droid Incredible

My gf's phone has been having some issues with google voice for awhile now. She's always wanted the stock incredible VVM back, but no one's ever been able to find it on other forums. If anyone has the stock VVM for the phone, I think she would like that better.
If not...
Her issue is that whenever someone calls her phone it always has different responses. Some people call and say the number is unavailable, others say it asks for her subscriber number. I've called three times now and i've had those two errors along with one that actually got through. The problem is that she isn't receiving all her calls, which anyone on this forum can attest that this is a MAJOR issue, especially while she hunts for jobs. If ANYONE can figure out a solution to this problem it would be awesome. I've searched the web for weeks trying to find a solution or even an alternate VVM, but I haven't had any luck.
I just need to figure out one of the following:
- how to get back stock Incredible VVM
- how to fix or permanently get rid of google voice
- find an alternative VVM that works decently and can get past this google voice issue.
Any help would be appreciated...
Phone is Verizon Droid Incredible running CM7 version 7.0.3-inc

Android JB 4.1.2 snyc problems with screen off

I'm having a little (and simple to reproduce) problem with my Samsung Galaxy S2.
When on 3G data connection, about 5-6 minutes after the phone locks with the screen going off it will stop synching any kind of data. It won't receive any incoming messages from Google Talk, Gmail, Heytell or any other similars. Randomly after several minutes it's like the phone wakes up, checks, and receives all incoming messages all at once.
Also it will receive it all when I unlock the phone and I have noticed a little pattern in the antenna signal icons where they go from blu to white to blu again and then the magic happens.
Do you have any hints on how to fix this or make at least more bearable?
When on wifi there is no problem at all and all messages are synched instantly.
I have used a few custom roms (resurrection remix and revolt both with android 4.1.2). I have tried to change modems and kernels with no luck.
I believe it is a problem with jb 4.1.
Is anybody having the same experience or could give it a try?
Thanks in advance.

[Q] AOSP Group Messaging

i have noticed and tested that the verizon note 2 upon receiving a message from a samsung device like a stock note 2 or stock sgs3 that i do not receive their messages in the group thread. my dad is the stock note 2 and my moms is the sgs3 my wife has a stock bionic. i have sat with all the phones and tested it myself.
my wifes phone receives group messages from them just fine but i do not. so i was curious if it was just aosp and i knew a guy my dad works with that as aosp running on a sgs2 and he receives my dads messages just fine in group texting.
so that leaves it to be this phone on aosp causing the issue it has happened in cm, aokp, carbon rom so that did not differentiate either. i stay on 3g 100% of the time. and i have tested with both gosms and handcent (whith the group messaging option check on both)
and i also should note it is just other samsung phones group messages that have given me this problem thus far. iphone and motorola are the only ones i know that my phone can receive in the group thread
i was just curious if anyone else had this problem also
edit: now on 4g and problem still occurs.
You sure LTE is enabled in settings?
Aosp messaging isn't perfect iirc. There are issues with group and vzw.
kimdoocheol said:
You sure LTE is enabled in settings?
Aosp messaging isn't perfect iirc. There are issues with group and vzw.
Click to expand...
Click to collapse
im sorry i should have been more clear i meant i was on 3g because i only live in a 3g area
Im on a Galaxy Nexus on verizon running carbon rom and have noticed I was having the same MMS/group messaging issues. Mine seemed to be from iPhones and I would get the message and get a notification. When I then went to the thread/list, there was no message and it was gone. I THOUGHT maybe it had to do with updating to the latest radio?? If I flashed another rom sometimes later a random MMS/group message gets pushed through (sometimes from days before). I know someone on a S3 with he same issue. All my group messages are from verizon iphones except 1 verizon s3 that has never been an issue. Ive tried turning off wifi too but doesnt seem to be the issue. Right now i have auto retrieve off, but id never know if it was a message i wouldnt have received.
friguy3 said:
Im on a Galaxy Nexus on verizon running carbon rom and have noticed I was having the same MMS/group messaging issues. Mine seemed to be from iPhones and I would get the message and get a notification. When I then went to the thread/list, there was no message and it was gone. I THOUGHT maybe it had to do with updating to the latest radio?? If I flashed another rom sometimes later a random MMS/group message gets pushed through (sometimes from days before). I know someone on a S3 with he same issue. All my group messages are from verizon iphones except 1 verizon s3 that has never been an issue. Ive tried turning off wifi too but doesnt seem to be the issue. Right now i have auto retrieve off, but id never know if it was a message i wouldnt have received.
Click to expand...
Click to collapse
Also running Carbon, HTC One on Verizon (m7vzw).
I also have the issue of a notification appearing and my being unable to read it. It doesn't show up in my messages list.
anyone found a solution yet? I'm going to try downloading the sense 5 messenger apk, because it worked for me with a previous rom.

[Q] Unable to send Text Messages but can receive them?

I'm currently flashed with the latest nightly of CyanogenMod 10.2 which is 9/5. I'm not really sure when it started but a bit after I installed 10.1 I was unable to send text messages out. However was able to receive messages just fine. I've searched around quite a bit, and checked the same issues on various forums, none which have a good solution to what the problem is. Wondering if there is any insight as to what the probably cause to this would be? I never really had an issue with CM10.1 when I used it on my Samsung Captivate. Now that I switched over to the i777 I don't really see why I'm having this issue.
killerxtreme said:
I'm currently flashed with the latest nightly of CyanogenMod 10.2 which is 9/5. I'm not really sure when it started but a bit after I installed 10.1 I was unable to send text messages out. However was able to receive messages just fine. I've searched around quite a bit, and checked the same issues on various forums, none which have a good solution to what the problem is. Wondering if there is any insight as to what the probably cause to this would be? I never really had an issue with CM10.1 when I used it on my Samsung Captivate. Now that I switched over to the i777 I don't really see why I'm having this issue.
Click to expand...
Click to collapse
Could be a few things:
APN issue. Check that what you have under the 3 MMS fields match those of your carrier.
Are you using the stock messaging app or a 3rd party one? If it's the latter that's likely the culprit as well.
Or it could simply be a nightly problem, which is why it's generally best to use RC's. Nightlies rarely offer real upgrades, and often cause problems due to constant dirty flashing/carryovers from previous builds.
Sent from the i777
I'm using the stock messaging app. My APN is correct. I'll try the RC version.
EDIT: Nope the RC didn't change anything, I've looked around and I havn't been able to figure out anything. I'm able to send MMS messages, just not SMS. If I switch the chip back into my captivate it can send texts just fine.
killerxtreme said:
I'm using the stock messaging app. My APN is correct. I'll try the RC version.
EDIT: Nope the RC didn't change anything, I've looked around and I havn't been able to figure out anything. I'm able to send MMS messages, just not SMS. If I switch the chip back into my captivate it can send texts just fine.
Click to expand...
Click to collapse
Bump?

[Attachment(s) text_0.txt removed] Error

You guys are my last hope. I've Googled and searched and talked to Verizon and I can't find a solution.
When texting specific iPhone users on att I constantly get a message
"Attachment(s) text_0.txt removed] Attachment(s) removed]"
They, on the other end sometimes get a text from my number or it will switch to "myphonenumber"@vtext.com creating a new conversation on their phone. I can find no correlation other than if they send me an mms it always comes through.
Any suggestions? Your help would be greatly appreciated by my mother[emoji1].
Rooted stock sch-i545 on nc5
Never touched apn settings.
-Edit to get error to appear
Sent from my Verizon NC5 Galaxy S4 w/ GEL and Xposed
Also wanted to add that this isn't exclusive to my stock rooted nc5. This was happening on Jellybean as well.
Sent from my Verizon NC5 Galaxy S4 w/ GEL and Xposed
Will happen no matter what if you've got a current iPhone working through Verizon. For whatever reason, their 'sms' to mail gateway at Verizon is creating MMS of every text. That happens no matter how short the message is (could be a single character) and occurs even when we're talking vanilla ASCII text. It's a Verizon problem with Apple phones, evidently starting with iOS6. It's also not a problem unique to Android clients. The same thing happens to many users of Outlook and other client software.
ecanderson said:
Will happen no matter what if you've got a current iPhone working through Verizon. For whatever reason, their 'sms' to mail gateway at Verizon is creating MMS of every text. That happens no matter how short the message is (could be a single character) and occurs even when we're talking vanilla ASCII text. It's a Verizon problem with Apple phones, evidently starting with iOS6. It's also not a problem unique to Android clients. The same thing happens to many users of Outlook and other client software.
Click to expand...
Click to collapse
Governments have risen and fallen since I last posted in this thread haha.
Her and I are both 2 phones past this problem but it disappeared when she upgraded to a newer iPhone. Hopefully if anyone else is still having this problem they'll know it's a Verizon issue. Thanks

Categories

Resources