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.
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.
Using the SynergyROM for AT&T, we all seem to be getting the "+" sign prefixed to all of our incoming calls. This is a huge PIA to an otherwise very well done ROM. I recall having this problem months ago with a different ROM, but I can't for the life of me remember which one it was and what the fix ended up being. Can anyone remember any of the other ROMs they have seen this issue with? I know Task650s build had this problem, but it seems it's fixed in his ROM now.
Would love to know the answer to this as well. I tried SynergyROM and liked it quite a bit but this among some other annoyances pushed me to finding other ROMs.
I had this issue with one of Task's first 4.2.1 builds. Been fixed for a long time there.
I used a combination of contactscleanup and prefixer in the interim to handle the +.
It was one of the stock builds that had this problem, just wish I could remember which one.
I am also having this issue. I am on AT&T, GalaxyMod RLS16 ROM, KT Kernel(2/7 version). Android version 4.1.1.
The "+" sign is causing problems for me when my allowed contacts are not ringing through to me when the phone is in Call Block mode (I keep it this way while I am at work).
If anyone has any suggestions has a solution that I may have missed while searching, it would be appreciated if you would share. Thanks!
Yesterday I reverted to latest AT&T stock firmware (JSS15J.I747UCUEMJB - Android 4.3).
Now I am suffering from the following (reproducible!) problem:
Once the phone is in LTE, it stays in LTE mode (icon "4G LTE") ... until I make a phone call! After the call is established, the data connection drops completely and after hangup, I am just online with 2G!
When I dial *#*#4636#*#*, and use "Device Information" I see very shortly network type: EDGE. But tapping on "Device information" is enough that the phone completely restores its 4G connection and I immideately see again "Network type: LTE:14" and the "4G LTE" icon appears.
This is so frustrating, I can't do this after each call
Anyone knows whats going wrong here?
dy/dx said:
Yesterday I reverted to latest AT&T stock firmware (JSS15J.I747UCUEMJB - Android 4.3).
Now I am suffering from the following (reproducible!) problem:
Once the phone is in LTE, it stays in LTE mode (icon "4G LTE") ... until I make a phone call! After the call is established, the data connection drops completely and after hangup, I am just online with 2G!
When I dial *#*#4636#*#*, and use "Device Information" I see very shortly network type: EDGE. But tapping on "Device information" is enough that the phone completely restores its 4G connection and I immideately see again "Network type: LTE:14" and the "4G LTE" icon appears.
This is so frustrating, I can't do this after each call
Anyone knows whats going wrong here?
Click to expand...
Click to collapse
Hello my friend, All I can say is stock 4.3 is having major problems on my end and if you do a quick search you will find many problems like crazy battery drains, crazy random resets, and crashes like your self. I suggest rooting and flashing CM or something other than stock... It seems are trying to make us throw away our phones and upgrade and buy a new one sorry i could not be of any help !
sg3love said:
Hello my friend, All I can say is stock 4.3 is having major problems on my end and if you do a quick search you will find many problems like crazy battery drains, crazy random resets, and crashes like your self. I suggest rooting and flashing CM or something other than stock... It seems are trying to make us throw away our phones and upgrade and buy a new one sorry i could not be of any help !
Click to expand...
Click to collapse
Sad - thanks
CM is where I come from.
I had troubles from the beginning on with this I747.
Eventually I went on to CM. But this also sucks - cm-11 is far from out and even they deem cm-10 "stable" it is not, even worse: They do not even fix errors although heavy ones exist and could be fixed (see bug tracker).
I have big troubles with CM mainly with device encryption (boot freezes) but also camera does not work well and eventually LTE did not work any more. That was my motivation to go back to stock ...
Which ROM do you have currently?
dy/dx said:
Sad - thanks
CM is where I come from.
I had troubles from the beginning on with this I747.
Eventually I went on to CM. But this also sucks - cm-11 is far from out and even they deem cm-10 "stable" it is not, even worse: They do not even fix errors although heavy ones exist and could be fixed (see bug tracker).
I have big troubles with CM mainly with device encryption (boot freezes) but also camera does not work well and eventually LTE did not work any more. That was my motivation to go back to stock ...
Which ROM do you have currently?
Click to expand...
Click to collapse
Damn sorry to hear that, I have been having many problems with I747 as well sadly. I just hopped off CM because of that reason, camera, bugs, and not really stable lol.. I've been running Dandroid 5.4 for 48 hours now and so far so good! It looks hybrid like half touchwiz/half CM but NOT really CM just looks themed like it its really touchwiz which i like because I love the touchwiz camera. give it a shot ! Let me know if it help with your problem!
here a quick link for the rom
http://forum.xda-developers.com/showthread.php?t=2121506
Hello, all! Long time lurker, but given this great new tablet I got, and the nice, tight nit community here, I thought I would try to ask some questions and perhaps get involved a little bit more.
I am not new to custom ROMs, as I used to do them heavily with my T-Mobile G2 (Desire Z) and my older tablet, the Asus Transformer TF101. I am new to the G Pad, though, having had it less than a week. Now, to the questions...
I started with using the stock ROM, and it's actually not bad, but some of the flakiness with the SD card, along with Amazon Appstore unexpectedly flaking out on me, was impetus to get me to try some ROMs.
First I tried the AICP nightly, then I tried Infected's CM nightly. In both cases, there was the brightness issue (which can be fixed once it's booted up, but it is annoying at first). That's not the end of the world.
What really did bug me though was that none of my 5GHz wifi bands were showing up, and especially with AICP, the wireless in general seems flaky. Can anyone speak to this, or perhaps am I doing something wrong?
In the meantime, can someone recommend a stock-based rom that easily installs with TWRP 2.7.0.1? I could not get a previous version to work properly, and LRS G Pad would not install without rebooting in the middle on 2.7.0.1. I had a heck of a time attempting to install 2.6.3.2... so no, that is not an option. I rewiped my tablet dozens of times trying to get it to work.
Thank you for your help!
Have you checked the country setting under advanced wifi settings? I think that influences which wifi bands will work.
That makes sense! Thank you! I should have known this also, since I was setting up my laptop a few weeks ago and had to set the country code there also.
Thanks again - I'll give it a shot later once I run another nandroid.
To my surprise, 5GHz just worked on the latest 5/22 CM11 build. I ended up going to LRS for other reasons, but not that one.
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