Loaded the CM 4.4 update from today and now I can't hear any voice when calling. The call connects and dials fine just can not hear anything. Anyone else have this issue?
Thanks in advance.
seriously guys, 4.4 is new and buggy. its going to be buggy for quite some time. it hasnt even hit release candidate status with cyanogenmod, and you guys expect it to work perfectly? go back to 4.3 if you expect a stable rom, because 4.4 roms are not what you want if you want stability at the moment.
Also, you would probably get more help posting this is the respective roms thread, instead of here. Just saying
Related
Hell everyone,
I recently rooted my phone and installed LiquidSmooth on my AT&T Samsung S3. About three days into using the ROM, I notice some connection problem between my phone and AT&T's network. The problem I experienced was I wouldn't receive texts or calls from other people even though the phone is connected to the network. When I do receive the texts, they come all at once at the same exact moment. Which means my notification ringtone going off like crazy.
This problem usually occurs at night around 9-12PM. I also experienced the same exact problem when I first started using CM10, the stable build. The one thing I also noticed after installing both ROM's is there's no voicemail number. I had to manually add a voicemail number, which is my own number, right?
I decided to unroot my phone and run Samsung's newly released JB update, which totally blows besides the battery life. As of right now with the unrooted phone and Sammy's updates, everything is running fine.
Thanks very much, I appreciate any help I get from you guys. And, I do want to apologize in advance if this question had already been asked. I tried searching, but couldn't find anything on the subject. If you guys need anymore details, please do not hesitate to ask. I will try my best to provide as much detail as possible. Thanks once again.
I have seen some threads before where they discuss running Viber on CM or CM based ROMs but to no conclusion.
There was one post from a Viber rep as well and he/she basically said that they cannot support custom ROMs.
So I just wanted to find out if you were able to make/receive a Viber call on your custom CM 10.* or CM 10.* based ROMs.
On Viber(version 4.2.1) every time I try and make a call or receive a call, it fails. Resetting/Re-installing did not help either.
Chat is fine but voice call fails.
All help from users who were able to use it successfully will be great and much appreciated.
I have tried to find some definitive info on it in vain so far, hence this thread, feel free to close/remove this thread if its already discussed
somewhere else and also do post a link to the thread as well, if so.
meletios said:
I have seen some threads before where they discuss running Viber on CM or CM based ROMs but to no conclusion.
There was one post from a Viber rep as well and he/she basically said that they cannot support custom ROMs.
So I just wanted to find out if you were able to make/receive a Viber call on your custom CM 10.* or CM 10.* based ROMs.
On Viber(version 4.2.1) every time I try and make a call or receive a call, it fails. Resetting/Re-installing did not help either.
Chat is fine but voice call fails.
All help from users who were able to use it successfully will be great and much appreciated.
I have tried to find some definitive info on it in vain so far, hence this thread, feel free to close/remove this thread if its already discussed
somewhere else and also do post a link to the thread as well, if so.
Click to expand...
Click to collapse
Hi! Even though Custom Rom's are not fully supported we'd like to try to help.
Can you please elaborate? What do you mean by fail? Do you use 3G WiFi? Where are you from?
Viber Team said:
Hi! Even though Custom Rom's are not fully supported we'd like to try to help.
Can you please elaborate? What do you mean by fail? Do you use 3G WiFi? Where are you from?
Click to expand...
Click to collapse
Sure, when I make a call, I can see the green call button and also hear the call ring,
then when the receiver picks up the call, the screen flashes once, I get a standard (white on black) notification that its connecting and then
the call ends and I am back on the chat screen.
I have since moved to a sense based ROM so unfortunately cannot get the screenshots now.
I was on CM 10.1.
Hope this helps.
Location - UK, via Wifi or Data Connection (H)
I have tried installing multiple different custom rom's and I have also had the stock JB rom.
I don't know why, I really don't, but Custom rom's that are 4.3 or above mess around with my t989.
The calling never works, so say I just turned on my phone, it's just booted, I can make a few calls and everything is fine, the minute I hang up, and wana call another person within the next 3-5 Minutes, it's gone. It doesn't work anymore.
I don't get why the calling does not work on any KITKAT ROM.
It doesn't work on CM 10.1.3, 10.2, 11, Liquid smooth and now hellkat... it's a shame.
After a while, when you try to make a call or when you receive one, You can't hear the other side and the other side cannot hear you either.
I have had this problem with custom roms, specially 4.3 and above. Hellkat seems to be worse than CM11 calling wise, even though as I see, they have the same dialer and hellkat uses most of CM builds but still.. this sucks. I feel like it's either a software/rom problem or something disabled maybe, i'm not sure. I know, I have great connection (T-mobile) Data working, full signal and everything seems to be fine. However, I don't know what to do to even try to solve/fix it. I hope someone here know's though or someone here can help.
FYI; This doesn't happen on the stock rom (JB 4.1.2) At all. It never happens on stock, just on custom rom's and the only custom rom it doesn't do this on and works fine is ( CM 9.1)
Any solutions anyone knows of?
Thank you.
Replied to you in the other thread. Unless you've played around with different radios, I'm near 90% sure it's snapchat. I don't know why it borks the roms, someone smarter than I will have to answer that. All I do know is that several people with the exact same symptoms uninstalled snapchat and everything went back to normal.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
First off, before getting into anything, let me just say that yes, I do fully realize that I am posting this in the wrong section. The reason why I'm posting this thread here is to fully ensure that this issue gets the most attention as possible, as I've already posted for help if the Q&A section of the G2 forums and various other help threads, to no avail. This is kind of my last resort here.
Whenever I'm on an AOSP ROM, using either basebands ZV8 (From my understanding, some LS980 ROMs only work with JB/ZV8 modem) or ZVD (The modem zip is named KK_BASEBAND.zip by Cloudy, so I'm ASSUMING that's either ZVD or ZVC), data, outbound calls, texts, everything works, EXCEPT for incoming calls. Just goes straight to voicemail. And this is only with AOSP ROMs. Stock ROMs perform with no problem. I've been trying to get to the bottom of this issue, but I just can't seem to get a finger on it. So I'm currently in stock until I can get some insight on this. Has anybody had any experience with this, or know what's going on? Any and all help would be greatly appreciated. And, for what its worth, I rooted using towelroot+AutoRec.
zv8 baseband works for me on incoming calls, (texting wise i have to use a 3rd party app) *currently running cm 12 at the moment*
jcwxguy said:
zv8 baseband works for me on incoming calls, (texting wise i have to use a 3rd party app) *currently running cm 12 at the moment*
Click to expand...
Click to collapse
ZV8 works for me for a little while, too, and then it seems like a day later or so, all incoming calls go straight to voicemail. I usually call myself at least once or twice a day just to make sure everything still works, and calls get blocked sooner or later. Is there a dialer code I could use to upgrade PRL on AOSP? Going back to stock > upgrading PRL seems to do nothing, so I'm wondering if it'd be better to do it on AOSP, rather than going back to stock.
no way to update profile or prl on aosp unfortunately
iamterence said:
ZV8 works for me for a little while, too, and then it seems like a day later or so, all incoming calls go straight to voicemail. I usually call myself at least once or twice a day just to make sure everything still works, and calls get blocked sooner or later. Is there a dialer code I could use to upgrade PRL on AOSP? Going back to stock > upgrading PRL seems to do nothing, so I'm wondering if it'd be better to do it on AOSP, rather than going back to stock.
Click to expand...
Click to collapse
I was having this issue on stock and aosp turns out sprint was working on towers here upgrading them... And it only affected incoming calls... Might want to call sprint and see...had something to do with spark bands in our phone...next time you try aosp put it on CDMA and see what happens... That was my experience
goast said:
I was having this issue on stock and aosp turns out sprint was working on towers here upgrading them... And it only affected incoming calls... Might want to call sprint and see...had something to do with spark bands in our phone...next time you try aosp put it on CDMA and see what happens... That was my experience
Click to expand...
Click to collapse
I may, or may not have finally found a solution for this. I was on Super G2 ROM with ZVC modem, PRL/Profile updated and everything, and instead of downgrading modem to flash certain AOSP ROMs, I flashed last Mahdi build (which is on KK modem) and just left the radio alone. So far, everything seems to be okay. So far. I've been getting calls and calling myself randomly from Google Dialer to make sure everything is good, and all remains well for the moment. We'll see how this turns out.
Im having this same problem, on Sprint using a G3 on AOSP rom.. its kind of annoying, especially since all my calls go straight to vmail.. is there a fix?
You can also try the ZV7 modem
I installed CM12.1 on my d851 and I cannot disconnect calls. I tap the red button to hang up and the phone app hangs on "hanging up" but does not actually disconnect. Has anyone successfully gotten the CM12.1 dialer to work on the T-Mobile G3?
I have the same issue when I install other custom roms based on CM.
Any help would be appreciated.
Re: dialer will not hang up
Hi,
Did you ever work this out as I'm also having issues with CM
12.1 not hanging up on galaxy s3 Verizon.
Thanks
David
Having the same issue as well 2 i605 on cm 12.1 just switched from rip off VZW to T-Mobile and this bug started. Phones worked fine on Verizon... Can someone please get this fixed?
i don't have a solution for cm12.1 but maybe if i share the (quick) solution that was used in cm11, some smart person here can figure it out--hopefully, once and for all.
in cm11, all you had to do was add a single character to a field in build.prop, which was something like:
ro.telephony.ril.v3=newDriverCall
to get:
ro.telephony.ril.v3=newDriverCallU
in cm12.1, the rom is presumably already shipped with the correct settings:
ro.telephony.ril.config=newDriverCallU,newDialCode
but does not work (for those of us using sph-720, especially). someone who understands android can maybe port the old (and simple) fix to the new one(?)
also, i appreciate the work guys do to get us these builds, but it'd be nice not to reintroduce big issues like these as it basically forces a potential user not use the rom, which then wastes the hard work of porting it to a particular device in the first place. i can live without data since i use wifi heavily, but not being able to receive calls is a no-no.