Database Info

[Q] DTMF problem when dialing D2G GSM

I have a D2G that I'm using an AT&T SIM in for GSM use only. The phone stays in GSM mode all the time.
I'm having an interesting issue with the way the phone detects that it has completed a call.
On a normal CDMA phone (my DX) after you dial a number and hit send, the "call timer" starts counting up as soon as the phone has connected to the network and the call starts ringing. If you want (though there would be little reason to do so) you can bring the dialpad back up and start sending DTMF tones even while the other end is still ringing (hasn't answered yet).
On the D2G in GSM mode (don't know about CDMA mode because I've not used this phone in CDMA mode) when you dial a call, the call timer doesn't start counting up until the phone senses that the other end has actually answered (receives a connect signal). While the line is ringing (before anybody answers) you can bring up the dialpad, but pressing keys does not send any tones. Once the called party answers, pressing keys then sends tones.
The problem comes when trying to dial into a conference bridge where you have to enter the bridgeline passcode, or while trying to use a calling card. Both these systems appear to not send the "connected" signal when they first answer. They wait until you get connected to the desired conference call, or until you've entered all the calling card information and are rung through to your ultimate target before sending the connected signal.
Since the D2G in GSM mode is actually waiting for this "connected" signal before starting the call timer, and since it won't allow you to send DTMF tones until the call timer starts, it is basically impossible to use a conference bridge or calling card.
I have tried numerous add-on dialers, but all hand off to the OEM phone/dialer app after initial dialing. I've tried add-on DTMF generators, but of course they just generate the tones locally (speaker) and not onto the ongoing call. I've been all through build.prop, etc. looking for a setting that would tell it not to wait for a connect signal to enable the "connected" behavior and not found anything.
Putting pauses or waits in the dial string doesn't work either because the phone doesn't even start "pausing" or "waiting" until it senses that it has connected (which doesn't happen before the other end gives up waiting for me to enter the code).
That's the really irritating part. When the conference bridge or calling card system gives up waiting and connects me to the thing that tells me my time to enter the codes has expired and it is going to hang up on me, then it sends the "connected" signal and I can enter all the tones I want on top of the "please call back when you can figure out how to use a phone" message.
I've had someone running a newer firmware test to see if they have this same behavior and they do. If anyone wants to see if they have the issue, they could call the Sprint calling card access number (800-366-2255) and you should find you can't enter any tones once it has answered. Again, this is on a D2G in GSM mode. I'd expect in CDMA mode it would work fine.
Possible avenues of resolution:
Make the phone treat the call as connected immediately instead of waiting for the other end to answer
Have an external app that can send DTMF tones on an active call (Google says that is a common desire that is generally not possible)
Somehow make the built-in dialer allow number presses to generate tones even if it doesn't think the other end has answered yet
Thanks in advance for any suggestions.

Are you trying to say you use the phone on AT&T in USA?
Try switching phone to GSM/UMTS in settings instead of 'global' I remember having some issues with ring back tone while in global mode using GSM network which went away once I switched to GSM/UMTS only.
Sent from my DROID2 GLOBAL

leobg said:
Are you trying to say you use the phone on AT&T in USA?
Click to expand...
Click to collapse
Yep. Other than the undesirable behavior of the call progress timer, it works perfect. Although the data works great, I keep data disabled because on AT&T prepaid data costs like 1 cent per kilobyte. That doesn't seem like much until you think about 1024 kilobytes in a megabyte which means you're paying $10.24 per megabyte which is insane. Fortunately I can bring up 3G Mobile Hotspot on my DX (which has unlimited data) and tether my D2G through my DX and have full Internet. It sounds retarded, but the only time I use this setup is when I need my DX to do mobile VPN for work, and then use my D2G for voice calls. AT&T prepaid is only like $1.99 a day for unlimited voice and text, and you only pay on the days you use it (which is almost never for me).
leobg said:
Try switching phone to GSM/UMTS in settings instead of 'global' I remember having some issues with ring back tone while in global mode using GSM network which went away once I switched to GSM/UMTS only.
Click to expand...
Click to collapse
Thanks for the suggestion. Actually I was already in GSM/UMTS mode but tried switching it to "Global" mode. Unfortunately the behavior was the same.
Somehow I imagine if I trot down to the Verizon store to ask them about it they won't really be super inclined to help. I have considered trotting down to the AT&T store where I bought the prepaid SIM and seeing what they think. But I don't imagine it would be good for much other than the amusement of their confusion.

Droid 2 Global is configured so it doesn't get service with any GSM/UMTS provider located on the teritory of the United States of America. How is yours working on AT&T is really a huge surprise to me and many other members of this and other online forums.
This so called "band lock" (google for Droid 2 global band lock) can reportedly be circumvented, but there is no publicly available method to do it. Unless you got yours 'band unlocked', it is not supposed to get any service from neither AT&T nor T-Mobile. Or maybe you bought it from someone who was working on this 'band lock'
Could you share more info with us?

leobg said:
Droid 2 Global is configured so it doesn't get service with any GSM/UMTS provider located on the teritory of the United States of America. How is yours working on AT&T is really a huge surprise to me and many other members of this and other online forums.
This so called "band lock" (google for Droid 2 global band lock) can reportedly be circumvented, but there is no publicly available method to do it. Unless you got yours 'band unlocked', it is not supposed to get any service from neither AT&T nor T-Mobile. Or maybe you bought it from someone who was working on this 'band lock'
Could you share more info with us?
Click to expand...
Click to collapse
The phone has been unlocked with the TBH/DBU unlock. It is running 2.4.29 firmware and has to stay on 2.4.29 for the unlock to be preserved. The unwanted call progress behavior (the purpose of my original post) has been tested and confirmed on another phone running 2.4.330 so it's not a 2.4.29 issue. I'd bet that all of the Blur dialers probably do the same thing (disable tones after Send and until the call progress timer starts running). Just in CDMA mode the call progress timer starts running as soon as the call starts ringing and in GSM it waits for an actual connect signal. The D2G is truly like two complete phones in one, so seeing this type of disparity in behavior between the two different modes (I assume when in CDMA mode it would work just like all other CDMA models and not have the issue) isn't really surprising at all. I would expect that anybody who is using the GSM mode of their D2G would have this issue when dialing into a conference bridge or calling card provider where the "connect" signal is not given until after all of the secondary dialing has been completed. It would seem however that this issue would have come up before since I can't be the only person that works for a huge company and spends most of his day dialed into conference bridges for meetings (and might just want to dial into those meetings from his spiffy GSM phone).
I've been though the AOSP source for the phone/dialer before (when troubleshooting something else), so when I get a chance, I'll go through again and find the section where it enables and disables the tone sending. I'd guess it would be trivial to remove the part that disables tones during the period between Send and call-progress-timer-start, compile it, and just replace the dialer on the phone. I've been through all the build.prop and everything else hoping a setting would jump out at me, but no luck.
About the TBH/DBU unlock -- after the unlock there's nothing special about sticking an AT&T, TMobile, etc. SIM in there, but I only have first hand experience with the AT&T. I just went into the local AT&T store and told them I wanted to buy a prepaid SIM. They asked what kind of phone and I think I told them I had a Samsung Captivate (not that it really matters). The SIM was basically free and I put $25 on it. Stuck it in the phone, changed to GSM/UMTS mode, phone blurred while it was changing modes, and now has AT&T banner on the lock screen. Pretty much a non-event.
I didn't get a chance to go down to the AT&T store yet, but I plan to. If nothing else I'd like to test calling into the same Sprint calling card number from another GSM phone -- especially an Android phone if they have a working model there -- and see if it too has a problem.
Sorry for rambling. I hope I addressed your questions.

My friend MotoCache1 is the "other" member of TBH, just an FYI!
We haven't discussed the status of the band unlock on XDA out of respect for the rules here regarding paid services.

Well, that explains the things
Btw- mine is on Rogers Canada, i can use comma to add pause to dial extensions conference bridges without issues.
However, when I try my Telus Canada sim in, when I dial number, dialer says hang up, 00:00, then connects the outgoing call, sort of like a call back service, but without ringing back - hang up, then the very next second call connects and phone issues ring back tone. But this "hangup" on the middle prevents me from dialing extensions or conference bridges bu using pause in the number dialed. Everything else is fine (data, messaging/etc). So it is kind of crippled on Telus. Wonder if it is the same thing you get on AT&T.
Sent from my DROID2 GLOBAL

Hmmm. Interesting. Forgive the ignorance, when using Rogers is that CDMA? Or are you using GSM for both carriers?
I tried the same scheme, using commas in the dial string, but unfortunately the phone doesn't ever get to the part after the commas because it waits for connect before continuing the dial string. I don't get the hang up behavior you describe though. I'm a complete newb to GSM, so what I'm about to suggest may be stupid, but I wonder if the carriers have any sort of call handling parameters that are stored on the SIM?
I happened to be in a VZW store to get an extended battery for my DX and asked them if they had a demonstrator D2G in GSM mode so I "could test a bug I read about on the Internet". Moments after the question left my mouth I realized I was stupid for asking it, and he confirmed that by saying "no, we can't use the phones in GSM mode because GSM on that phone doesn't work in the US". Oops, duh.
He asked what the bug was and I told him. He said that he hadn't heard of that, but it sounded like something that would be fixed in a software release. He looked to see if any such releases were listed for the D2G, but found none. Surprisingly (to me anyway) there is a recent release listed for the D1 to fix an "unwanted recipients" problem (for messages), and some other thing (I don't recall).
I'm at Bike Week right now (sitting in the bath tub typing this on my DX -- yay Swype) but will give the AT&T store a shot when I get back. I'll also borrow a buddy's Tmobile SIM and see if it behaves any differently. He has an actual Tmobile branded android phone, (a Samsung, but I don't remember which one right off) so I can do the conference bridge test on his phone too.

Both Rogers and Telus now sport GSM/UMTS (Telus only UMTS) networks. Gone are the days when Rogers had CDMA network, almost 10 years now. Telus still has CDMA alive, but they are phasing that out. My CDMA radio is sleeping, until I get to the States next time I guess (my D2G is active on a pay-go plan) I will be doing some travelling in May/Jun across Europe, so I will try with european sims too.
Sent from my DROID2 GLOBAL

leobg said:
Both Rogers and Telus now sport GSM/UMTS (Telus only UMTS) networks. Gone are the days when Rogers had CDMA network, almost 10 years now. Telus still has CDMA alive, but they are phasing that out. My CDMA radio is sleeping, until I get to the States next time I guess (my D2G is active on a pay-go plan) I will be doing some travelling in May/Jun across Europe, so I will try with european sims
Click to expand...
Click to collapse
Thanks for the details. Interesting that you see two completely different behaviors just by changing the SIM. That leaves the question of whether the difference is due to the way each network is handling the call progress, or if it is some sort of information on the SIM itself that makes the difference.
I looked into SIM editors to see what sorts of things the various editors claimed to be able to read/edit on the SIM. I haven't seen anything along the lines of call processing characteristic parameters, etc., so I'm leaning toward the difference being in the signaling received from the network. I'll be able to get a better idea of what's going on when I get back home and can experiment with a Tmobile SIM, and/or put my AT&T SIM in another phone and see what it does.

OK, back from Bike Week (last week actually) and grabbed a T-Mobile SIM. Really odd results. The very first call I dialed on the T-Mobile SIM, the call timer started immediately, and I could send DTMF tones immediately. Every call since then has exhibited the same behavior I was seeing with the AT&T SIM -- the call timer doesn't start until a formal connect happens (which the calling card and conference bridge sites don't send upon initial connect -- thereby preventing sending the tones to access the service).
I spent just a little time going through the source code of: [platform/packages/apps/Phone.git]/src/com/android/phone/CallTime.java and found the spot where the call gets switched to "active":
Code:
/**
* Sets the call timer to "active call" mode, where the timer will
* periodically update the UI to show how long the specified call
* has been active.
*
* After calling this you should also call reset() and
* periodicUpdateTimer() to get the timer started.
*/
/* package */ void setActiveCallMode(Call call) {
if (DBG) log("setActiveCallMode(" + call + ")...");
mCall = call;
// How frequently should we update the UI?
mInterval = 1000; // once per second
}
I started looking around to see "who" all calls that and right off I only see CallCard.java calling it. I was expecting to see it called somewhere in PhoneApp.java (after observing a connect or something), but it's not called there.
There's lots of hunting yet to do, but I wanted to post progress in case anybody out there cares.
In some hunting I happened to stumble on a pretty detailed page outlining the exact same problem on an iPhone. It's understandable that this type of problem might exist and persist on a closed source device like an iPhone. Fortunately, something like this should be very solvable on an open source device.
I haven't had my buddy with a T-Mobile issued Android phone (Samsung Vibrant) test this yet. That's on the "to do" list.
More updates as I have them.

So what I've figured out on this is that you pretty much just can't use conference bridges or calling cards on a GSM phone. I've used my Tmobile and AT&T SIMs in a bunch of phones now:
1. Droid 2 Global
2. Droid Pro Global
3. Motorola Napoleon
They all do the same thing. Heck, the Napoleon isn't even Android - it's Windows Mobile. I also tried with my friend's Samsung Vibrant (which he has on Tmobile) and it does the same thing -- call timer never starts running and if the call timer isn't running you can't generate tones to put in your access code for the conference bridge, etc. Apparently the AT&T iPhones do the same thing, so again, this is a GSM thing.
Which begs the question again -- doesn't anybody with a GSM phone need to call into conference calls? I was under the impression that most big companies used conference bridges for most of their meetings.
Anyway, when I get some time I'll get back to taking a stab at hacking on the dialer -- just no free cycles to tackle it right now.

It must be something with that conference bridge you are trying it on. I know many phone switches do not connect the call while you are in the IVR/menu trees - it is usually done in order to avoid inaccurate call metrics on the receiving end. We are running a contact centre in our company and I know how important this is (and we do it to - we don't connect the call until operator answers the call). Billing is not supposed to start until call is connected on the receiving end. Apparently GSM operators like T-Mobile and AT&T care about call connect parametter and Verizon is simply ignoring it, I guess.

help!! samsung captivate acts weird on switching the network mode to wcdma

My phone acts weird on the network mode 'gsm/wcdma(automode)'
It works perfectly when I select 'GSM only'. This means that I have the APNs right
But as soon as I select the automode so that I can use 3g, phone starts acting weird. For starters the internet does not work. I also lose my voice service. The bars show that I do have voice service, but on making any call the call doesn't go through, and on ending the call the call remains on the notification bar. But if I dont end the call, then it does eventually shut by itself (~15secs) and then the bars disappear and I lose service. At this point my phone has automatically gone into flight mode. On turning flight mode off... the cycle repeats (with some exceptions):
1.notification shows service coming back: 3G, full bars for voice service. (Sometimes 3g doesn't appear at all, and at this point internet does not work but I can make calls)
2.but internet does not work (but if I keep trying it might work for a few seconds. Noticed that because network mode is on auto. Notification bar shows switching to GSM, and then back to WDCMA. On repeating this the internet lasted longer ~a min or two)... and then doesn't start at all (basically its very random)
3.make a phone call and call doesn't got through, lose service and goes into flight mode
I use an unlocked rogers samsung captivate on fido network (unlocked phone on network that share the same bandwidth). I also use a custom ROM: firefly 3.0. Specs are:
model number: samsung sgh-I897
fireware version: 2.2
basband bersion: I9000UGJK4
kernel version: 2.6.32.9
I have gone back to stock rom, and even back to the custom rom I upgraded from (pheonix 4~). I have tried different modems and a lot of ROMS. I am willing to repeat it all if its necessary

Please help. I've spent over a month trying to figure this out. And relying on gsm just doesn't cut it. It would be great if someone could even point me in the right direction.
Is this a phone, sim card, or service provider issue?

I believe this is a service provider issue...do you know what bandwidths their 3g is broadcast on? The captivate can only pick up 850 and 1900 if the frequency is outside those it will not connect.

studacris said:
I believe this is a service provider issue...do you know what bandwidths their 3g is broadcast on? The captivate can only pick up 850 and 1900 if the frequency is outside those it will not connect.
Click to expand...
Click to collapse
I use fido in canada which broadcasts on 850 and 1900. I do connect to 3g, but it is only briefly. But then I lose 3g and also my voice connection.And my phone goes into airplane mode automatically! My voice service (bars are full) is consistent when I am on GSM. This is independent of the ROM I use. Why does this happen? What is the connection between 3G and voice service.
based on *#0011#
ECIO on 1900 ~ -8
ECIO on 850 ~ -12

biharibong said:
Why does this happen? What is the connection between 3G and voice service.
based on *#0011#
ECIO on 1900 ~ -8
ECIO on 850 ~ -12
Click to expand...
Click to collapse
When the phone is on 3G, voice will also use the WCDMA signal instead of GSM. So, if your phone is on 3G and it can't connect, you will likely lose the voice as well.
Some Canandian carriers have separate APN for 3G and GSM. So, just because your phone works fine in GSM mode, doesn't mean your APN is correct on 3G.
Then, some custom ROMs based on EU i9000 ROMs can't handle 850 band at all. So, you need to be careful with what kind of modem is loaded with your custom ROM.

Looks like a kernel issue. Firefly is supposed to include Speedmod kernel and it looks like you have the stock Captivate kernel which I recall does not play well with anything other than a i897 modem. I use to run across the same problem (no voice in calls even though I had signal) when I first started messing with modems/kernels. Flash the latest speedmod kernel and see if that works.

tysj said:
Looks like a kernel issue. Firefly is supposed to include Speedmod kernel and it looks like you have the stock Captivate kernel which I recall does not play well with anything other than a i897 modem. I use to run across the same problem (no voice in calls even though I had signal) when I first started messing with modems/kernels. Flash the latest speedmod kernel and see if that works.
Click to expand...
Click to collapse
+1
make sure that your modem and kernel are compatible. The KB1 modem will not play well with a I9000 based kernel.

tysj said:
Looks like a kernel issue. Firefly is supposed to include Speedmod kernel and it looks like you have the stock Captivate kernel which I recall does not play well with anything other than a i897 modem. I use to run across the same problem (no voice in calls even though I had signal) when I first started messing with modems/kernels. Flash the latest speedmod kernel and see if that works.
Click to expand...
Click to collapse
I made some assumptions and just included the kernel version. Ive never messed around with kernels. I am using the one that came with firefly:
2.6.32.9 [email protected]#32 tue apr 12

This is really odd. But my phone is fixed. 3G is working and I have no idea how. I went through my usual application download and install cycles. The only system apps that I incorporated were a cache cleaner called 'history eraser' and a service starting app called 'autostarts'. And my phone is back to normal. Something to do with freeing system resources. Anyone have any ideas? I would think Samsung would need to fix this.
Hopefully Im not speaking too soon. But in the past two months this is the only time when my 3g has worked more than 10 mins

like I thought. I spoke too soon. After a reboot, the 3g stopped working. But it does not act as oddly as before: going automatically to flight mode and my voice service works even when the setting is on gsm/wcdma(auto).
Please help. Anyone have any ideas?
If this doesn't miraculously fix itself again, I am going to reinstall everything for troubleshooting puposes. I have to figure out if this is random or if autostarts,cache cleaner and any other app makes a difference

voodoo lagfix
I read somewhere that the voodoo lagfix changes the file system and the kernel. Could this be the reason why I cant connect to 3g

Please help! No 3G or GSM, can't call, but LTE works fine.

I really need help with my device, I searched all over XDA and no-one seems to have the same issue as me.
Here is some information:
1) Nexus 6P (H1511)
2) 6.0.1 Absolute stock, no rom, no root, no custom recovery. Build number MMB29P.
Recently got a new Nexus 6P and imported to Russia. All of the major bands here are supported. And the phone worked excellent for a few weeks, but then it lost all 3G or GSM connectivity. Just randomly,didn't do anything with it, the only thing I did is move to another city but than I got back, the issue didn't resolve. LTE works perfectly but can't call or receive calls, can receive sms though. Reseting network settings and factory reset changed nothing. Tried manualy set network to WCDMA or GSM with *#*#4636#*#* command, the moment I switch to anything besides LTE the connection is lost. Contacted the provider, no problem on their side, my SIM works good in other phones, my phone with other SIMs - no.
I don't think it is a hardware issue because a few times I managed to get everything working after an hour of switching networks and bands with no particular order in the *#*#4636#*#* testing mode.
After a while I figured that if I set phone to "GSM only" on USA bands in testing mode, but at the same time set it to "LTE prefered" in the normal network settings menu. I am able to set phone to Band mode 7 and set the network back to 2G in network settings keeping it on " GSM only" the whole time and only after this compicated algorithm and after a reboot 2G and 3G starts working. But any reboot after that revertes everything back to only LTE stage. Also if I get everything working but than reset network settings everything stops working again.
I have no idea what caused such an issue, I really hope someone can help.
Sorry couldn't post screenshots because of the "10 posts rule".

Note Edge 915T Wont let me call while on LTE - Help needed :(

Hello all..
I have this issue with my Note Edge 915T (T-Mobile Variant). It is unlocked and I use it in Venezuela with Digitel (LTE BAND 3: 1800) and the phone DOES connect to LTE with no issues (I get the 4G/LTE icon), and I can browse with no problems, but no one can call me, nor can I make any calls or text. In other phones, when I call, data drops and I can call and when I finish, data comes back up. HEre, LTE stays up and my call does not get through. Then after some tries, it drops to EDGE and won't pick up LTE until I reboot or something.
If I try a different operator, it goes to HDSPA (3.5G) and I get voice and data (data drops while calling, but it ir normal), but I want to use my operator with LTE.
Im running MM and I deactivated VoLTE as my carrier does not support it, but is there something else I'm missing?

This may sound stupid, but have you set your APNs? You can also try resetting your network. Dial ##72786#. Also Does your carrier require any certain apps. Example FreedomPop requires a specific app for getting/making calls, as they are mainly VOIP MVNO...

unimatrix725 said:
This may sound stupid, but have you set your APNs? You can also try resetting your network. Dial ##72786#. Also Does your carrier require any certain apps. Example FreedomPop requires a specific app for getting/making calls, as they are mainly VOIP MVNO...
Click to expand...
Click to collapse
Hi! thank you but yes, the APNs are perfect, I can use Data, the issue is that I cant call as the data signal stays in 4G/LTE and with my carrier, when calling, it drops data signal and it calls, here I can't. Im starting to think it has to do with CSC being with TMO, and I should use another one either from my country or a general One (BTU) for example. Will try to flash a rom from a different carrier to see if it works.

The only other option might be *#BAND# (2263),which could be dangerous, if you do not note original settings. Sometimes a complete ODIN can restore.
I normally use Nova Launcher - Widget- Activities- Somewhere under phone or settings. Shortcut Called PhoneInfo or DeviceInfo, which is much safer&consistently works! The app w/ same name no longer works. It took me forever & I always export my desktop, so I have that shortcut. The last option is an app called Samsung Phone Info+, but is paid or free if u know.... I really hate paid apps. It has under menu secret codes as well.

How to enable VoLTE for LG V50 (Korean U+)

How to enable VoLTE on the korean U+? I've checked with my carrier and they confirmed that VoLTE service is active on my SIM. However I can't find any option to enable VoLTE in phone settings. I've only seen a VoLTE call quality option in phone settings - not sure if this means that it's already active. The status bag logo also shows just LTE when mobile data is enabled - no indication of VoLTE.

If you have mobile data showing LTE and it does not change to 3G (or something else) when you make or receive a call, then you are on VoLTE. That is my general understanding of it.

lallolu said:
If you have mobile data showing LTE and it does not change to 3G (or something else) when you make or receive a call, then you are on VoLTE. That is my general understanding of it.
Click to expand...
Click to collapse
Yes. It is changing to 3G when I'm making a call.

Sykander said:
Yes. It is changing to 3G when I'm making a call.
Click to expand...
Click to collapse
Ah ok. It seems you are not on VoLTE then. Sorry, I don't know how to activate it though.

i have the sprint version but am currently on tmobile network which (was switching me to 3g) during voice call or txt msg.
now that tmobile has been taking down 3g (and they are working on a tower in my area) i do not even see 3g symbol in notifications anymore. i can complete the call and there is no lte symbol or 3g symbol but call completes but can not use data still.
when i hang up i see lte and can use data (browse the web)
the funny thing is before i went to tmobile i had metro pcs in this area which uses tmobile network and i never had a volte problem so you know this is software and they just want us to buy more phones.
this exact phone worked on metropcs with volte no problem.