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.

[Q] FIDO voice mail question

Did a quick search and cant seem to find what the number is for FIDO voicemail.
When i try to get into my voice mail it asks me for an access code or something?
Im currently on an iphone 3gs plan with fido. Just bought a nexus S from koodo since its 75$ cheaper then fido
If someone knows the number can you please post it up?
Thanks.

I'm on Fido as well and I haven't gotten around to setting this up yet. Ill call them tomorrow and ask. Will post back when I get an answer.

fido VM #:
1-604-618-1123
this is the number found in my phone automatically so it should work for you

i threw that number into the VW settings, i also tried dialing it straight up but when it answers it asks me for an access code.
Any ideas?

from my understanding that number is used for accessing fido VM when you dont use a fido exclusive handset. It will ask you for your access PIN, something that you setup while you initialized your VM service. Theres really no other way to access VM otherwise unless you have an iphone with virtual VM.

I'm with Fido (Vancouver, BC). The number that I have for VM is 1-778-317-5607
If it asks for an access code it means the VM service was set up at some point. If you call Fido (#611 from handset). They can help you reset it so you can input a new access code.

the voicemail # is your own phone number when dialed from your device.
To test it, try dialing your own number manually on the phone to see if you get in.
If it worked, go into your phone status and make sure it shows your phone number listed there. If it's not you will need to call Fido (Not from your cell phone) to have your SIM card re-pushed. Once the phone number shows up, voicemail will work fine.

Matridom said:
the voicemail # is your own phone number when dialed from your device.
To test it, try dialing your own number manually on the phone to see if you get in.
If it worked, go into your phone status and make sure it shows your phone number listed there. If it's not you will need to call Fido (Not from your cell phone) to have your SIM card re-pushed. Once the phone number shows up, voicemail will work fine.
Click to expand...
Click to collapse
old thread, yes, but -- calling your own # from your device? .... wrong!

SPN override no longer working?

On other phones I've always modified the /system/etc/spn-conf.xml file in order to change the carrier name on screen. The file is there on this phone as before but it doesn't have any effect. My APN shows the same numbers as before (even though my phone is LTE but I'm not using LTE).
I'm all debloated and unbranded except for the ugly carrier name. Anyone know what's different now?

Yes some other people have asked the same question but so far I don't see any clue to how this is different on this phone. The traditional ways clearly don't work on this phone. Something else is setting the carrier name and the spnoverride doesn't work.

[HOW TO] Fix SMS Sending Issue

I was having an issue on sending SMS messages, but I have fixed it. Here is how:
SMSC Number Update for CyanogenMod
SMS (Short Message Service) is specified by the ETSI (standards GSM 03.401 and 03.382 ). It can contain up to 160 characters, where each character is written according to the 7-bits GSM default alphabet.
SMS also contains some meta-data, e.g.
Info about the senders ( Service center number, sender number)
Protocol information (Protocol identifier, Data coding scheme)
Timestamp
There are 2 ways to receive and send SMS messages, PDU (protocol discription unit) and Text mode. In this page we focus on PDU mode, which is what Android 2.3 and higher recognize. The SMS messages travel through the SMSC gateway to send and receive. A common symptom of a badly configured SMSC is your device is able to receive SMS' but not send (usually reporting as sent, but without reception on the receiving end).
First, you will need your carrier's SMSC gateway number. Below are the numbers for major US carriers, (Google for your carrier's number if not covered here):
Sprint: +17044100000
Verizon: +316540951000
AT&T: +13123149810
T-Mobile: +12063130004
Rogers Wireless (Canada): +17057969300
Notice the numbers include the +, this matters for the next steps
Converting to PDU format
Take your number, including the + and go to http://www.twit88.com/home/utility/sms-pdu-encode-decode
Towards the bottom of the page, there is a spot to enter SMSC, Receiver and Message
Enter your full SMSC number (including the +)
Leave Receiver and message box blank
Select Alphabet 7
Hit Convert
You will get an output in the box on the right side
Take the first 16 digits from the second line (examples for above carriers listed)
Sprint: +17044100000 = 07917140140000F0
Verizon: +316540951000 = 0791135604590100
AT&T: +13123149810 = 07913121139418f0
T-Mobile: +12063130004 = 07912160130300f4
Rogers Wireless (Canada): +17057969300 = 07917150979603f0
Your SMSC number is now in PDU format, now to update your phone:
Open Dialer
Type the following sequence '*#*#4636#*#*'
Open Phone Information
Scroll down to SMSC
Optional: Hit Refresh to see current SMSC number used
Enter in your PDU formatted SMSC number
Press Update
Once entered, it can take up to 10 minutes for the phone to 'handshake' with the new gateway. A reboot is also suggested to power cycle the radio, {this step is unnecessary if you follow steps 9 through 12).
Turn off radio
Turn on radio
Hit Refresh to see current SMSC number used
Send a test SMS
Assuming everything worked, you should now be able to send and receive SMS' properly.
Note: MMS is controlled by the APN in Android. If MMS is failing, double check your APN information

Just to add info, Rogers Wireless Canada SMSC #: 07917150979603f0

j.smith said:
Just to add info, Rogers Wireless Canada SMSC #: 07917150979603f0
Click to expand...
Click to collapse
Thanks. Added.

Hi
I'm in Holland and I have the Galaxy Note running CM10
Should I change something on that encode procedure?
Like alphabet code or something?
Thanks

Canadian SMSC codes
For those needing Canadian SMSC codes...found out what the Fido, Bell and Telus call forwarding numbers were, and converted them (not tested).
Fido: +15149931123 = 07915141991321F3
Bell: +16473832355 = 07916174832353F5
Telus/Nextel: +15148210053 = 07915141280150F3
Wind: +16135009000 = 07916131059000F0 (taken from here)
Vidéotron: +15144240053 = 07915141240450F3
Also, since I'm with Mobilicity, their SMSC code (according to tech support) for Android 4.x is 0791617480001f6 (tested and works).
Got the UK ones right here:
Network, Number, SMSC to type in
Vodafone (Monthly), +447785016005, 0791447758100650
O2 (Monthly), +447802000332, 0791448720003023
O2 (Pay & Go), +447802092035, 0791448720900253
Orange, +447973100973, 0791449737019037
Orange, +447973100974, 0791449737019047
T-Mobile, +447958879879, 0791449785788997
Tesco, +447802092035, 0791448720900253
Virgin, +447958879890, 0791449785788909
Three, +447782000800, 0791447728008000
ASDA, +447785014315, 0791447758103451
GiffGaff, +447802002606, 0791448720006260

AIO smsc number
Just in case if somebody need it here is AIO's smsc number: +19703769830.,and you have to use it just like that do not convert it!I tried it and it works perfect!

steve86713 said:
Just in case if somebody need it here is AIO's smsc number: +19703769830.,and you have to use it just like that do not convert it!I tried it and it works perfect!
Click to expand...
Click to collapse
If this fails, my on my N5 I hit "refresh" and it showed up with
"+19703769830",145
Click to expand...
Click to collapse
that works perfectly for me. Again, this is for AIO Wireless.

Oddly enough i hit refresh on my infuse 4g running beanstalk 4.4 and it said 0180.

Thank you!!!! Ive been searching for this SMSC number all day and now realizing why it took so long was because I was searching Cricket Wireless instead of AIO who recently took over Cricket. Anywho, Thanks again.
Ginger

Aio Wireless SMSC number is +19703769830
Will you please add that to the initial post #1 @k-semler

If you came here searching for cricket, AIO wireless SMSC works for Cricket as mentioned by a few posters above. Just highlighting this

Issue updating pdu
I have followed the steps I am with Fido on Nexus 4 phone. When I put PDF number I get update error any suggestions does the pdu have to be in wuatation marks? I tested both, both update error.
Currently, when I refresh I have this format "+15149931123",145
Any help appreciated, I can't send sms for a week now, and tec not good, I can send mms no problem, everything else works sms receiving, data, internet, phone dialing.
Additionally, I noticed when I put *5005*7602* it says USSD running but it does not show me Fido gateway. When I tried to update through phone keypad the gateway by doing **5005*7602*15149931123# again says USSD running but than when I check hidden menu *#*#4636#*#* the smcs is not updated same format with ,145 at the end. I am having issue described here, any smart people out there to help me figure it out?

HELP there isn't a message center number option in the message app. And dialing *#*#4636#*#* in my dialer dont do anything, even pressing call the ussd code give error or connection problem as all other ussd codes do. Was on the phone with my service provider for over 2 hours they did all the can. The asked me to change the center number. Which I already thought of that. Factory reset wireless reset the whole shabang... nothing worked. Is there another method ? Using galaxy note 8 n950u updated to latest firmware no root sadly, tmobile variant, unlocked.

Unfortunately it doesnt seem to work with Sprint...

Can't get my SIM card to work

Hello everyone, i have a sim-free Xperia Z3 (D6643)
However, i can't use it with my main carrier (strangely enough it came with that same carrier ROM/bloatware pre-installed). Signal pops up, mobile data connects and let me uses it just fine, but when i try to make calls/send texts or recieve those, it doesn't.
"Conditional call forwarding enabled" is the message i recieve, then it disconnects the call.
I'm using an alternative carrier that works just fine '-'
Question for the advanced users of flashtools (if this have something to do with my issue).
i flashed a already packed .tft ROM.
Read in a tutorial that i must exclud all the ".ta" files before make a .tft, analyzing the files before making a .tft i've foun a "SIM Lock.ta" let it out of the process and build my .tft just fine, but i haven't flashed this ROM because i'm not sure if i'll be able to use my usual carrier after the process.
Can anyone confirm that?
Right now i'm sitting at 23.4.A.1.232 for the D6603 model.
I know someone must know a way out for this :fingers-crossed:

Which network provider do you use? Try disabling ALL call forwarding through call settings.

robogo1982 said:
Which network provider do you use? Try disabling ALL call forwarding through call settings.
Click to expand...
Click to collapse
Hello sir, i looked up to call forwarding settings and it's all disabled already... Yet, when i try to change any settings there a message says that network isn't responding, something like that.
My country has four major carriers, it just works properly with only one!!
Really strange, given the fact that we don't have carrier locked or exclusive devices plus all the things i've spotted in my first post (signal is full, 4g conneceted).