Related
Hi All -
Sorry for a weird (simple) question:
I am used to GSM / At&T - where if you had a 3G connection you could talk on the phone and be on the internet at the same time.
Is CDMA / VZW different? I just talked to a tech and she said it wasn't possible.
Confused...
-Daniel
According to what I have read on this forum and experienced, with CDMA, you cannot be on the internet and on the phone at the same time.
If I am incorrect, I am sure someone will correct me!
KD8FRE
that is correct. It's not possible on CDMA.
Wow. Interesting.
I guess there's a map for that in AT&T's future.
Thanks all - appreciate it.
-D
I never really noticed any kind of problems with it. I can make a phone call while my phone is tethered and I can still also receive calls, I think it probably temporally boots you off 3G during the phone call but put you back on right after.
Yeah EVDO is "1x Evolution Data Only/Optimized" which means that once a voice call comes in you are switched to 1X mode.
The latest SVDO specification (recently released) allows carriers to quadruple their voice calls and also allows data and voice at the same time. However nobody has implemented this yet.
I believe no one will implement this.... Because all providers are going HSPA or right to LTE... Where we will be able to have data and voice at the same time.
3G - voice and data
You can talk and surf the internet but only if you establish a Wifi connection
relicsoul said:
You can talk and surf the internet but only if you establish a Wifi connection
Click to expand...
Click to collapse
or if you use VoIP
Seriously though, what's the benefit of having an internet connection going at the same times as making a phone call? Please note, I'm not trying to be rude about this, I'm just curious about it.
Doesn't navigation(on sprint) use the internet? Im able to talk on the phone and still use navigation
There are some "live caller id" services which will do an online 411 lookup for any number that calls you, plus it's nice to be able to browse the internet to look something up while talking with someone (usually handsfree) for example if we're trying to decide on a movie or dinner or where to go out - all very handy to have a simultaneous internet and voice connection.
AstarteSV said:
Seriously though, what's the benefit of having an internet connection going at the same times as making a phone call? Please note, I'm not trying to be rude about this, I'm just curious about it.
Click to expand...
Click to collapse
Two big ones:
1. Conference calls with email coming in. Like - your next meeting has been moved (exchange, push).
2. On phone call - someone asks a question that needs internet connection (I found it this way - they asked what the weather would be like on Sat (it was Monday). I said... hold on a sec... I'll find out... then realized that there is no internet... so I pulled my iPhone out of my pocket and checked it instead. Again - this is something that AT&T does today - just didn't think CDMA was behind the curve on it...
-Daniel
Cool, thanks for showing me the light
My problem (with Sprint) when I had to have a CDMA device is that there is a difference in signal between EVDO and 1X. For instance, I had full signal for EV, but hardly any for 1X... Thus I could be on data all I want, but I had troubles with phone calls....
AstarteSV said:
Seriously though, what's the benefit of having an internet connection going at the same times as making a phone call? Please note, I'm not trying to be rude about this, I'm just curious about it.
Click to expand...
Click to collapse
yeah honey, i'll meet you ... where was that? let me punch it in my google maps... o wait CDMA FAIL
First this only happens where I work in the basement where only certain providers (eg Verizon) have some signal in only part of the room. I did not get signal on AT&T or T-Mobile Pay as you Go down here.
I noticed especially after I flashed the new radio which gives me better service overall that I get phone signal down in the basement, but it is GPRS of Unknown Network and says emergency calls only. I get up to 3 bars. If I scan for available networks I get the name 31064.
Does anyone know what network that is or what is going on?
Anyone have any ideas? (I will take wild speculation as well)
i wouldn't be alarmed by it. I experience this at my office since I work in the basement...haha
It's possible your basement just won't read a signal like mine. install a window by your desk, maybe that'll help, but there shouldn't be anything wrong with your handset.
Sounds reasonable. I would agree with no problems with my handset. I do get better signal than my nokia e51, so maybe it's picking up a slight signal where the nokia could not.
From what I've noticed, my Nexus S acts this way whenever T-Mobile (my provider) does not have coverage wherever I am, but AT&T (not my provider) does. You can check this by going into "settings" -> "wireless & network settings" -> "mobile networks" -> "network operators" .....it will then search for & tell you what network has coverage where you are. Every time I've had bars & it says "emergency calls only" & I've checked the above, it's always been when I had coverage from AT&T but not T-Mobile.
Thus, it seems to me like an "enable roaming for emergency calls only" kinda thing.
Emergency calls only
ha ha....lol... i also have the same issue on my brand new i747M S3. im confused.
i try the all methods for resetting phone.
i noticed when im on long way, i dont know my handset is goning emergency calls only. but when im restsart phone its fine.
i do everything but not fixed it. firmware update, downgrade, rom change,and unroot. but not fixed, and also try factory reset the rom by falllowing the samsung secret code *#197328640# > UMTS>COMMON>NV REBUILD and restart and do again CDMA>COMMON>NEXTPAGE>REBUILD and restart., thhis is the code of full factory reset the rom and EFS. but not solve........
i change the hand set to international i9305 brandnew one. i used it 2 sady without issue.... day after morning when i wakeup, i see the massege,,,,emergency calls only,,im confused becouse this is a brandnew one...after i called the friend he also got the i9305. i asked about this issue. he said me he didnt face to this type of issue.. im confused he said me try sim change.. i do it... problem solved....:victory:
problem is the SIM card......i changed it to new one... and used i week no emergency calls issue... when im going to low signals areas.. its show no network and automaticallly change to the network....im very happy for fixing this problem.....:laugh::laugh::laugh:
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.
I have this crazy issue with my D2G. I have had a similar issue in the past with all my android phones. It was worst with my SG2. It has not really been an issue up to now with my D2G but it is getting worse.
What happens?
When I call certain numbers there is no Audio in either direction, the call timer counts up and the call is in progress, just no sound in either direction. If the affected number calls me back, the same thing happens.
Which numbers are affected?
Only other mobile numbers. Always the same numbers. Always the same result. It was just an occasional mobile number, perhaps one in a hundred, but in the last couple of days BOTH of my gfs numbers are doing this and she has 2 separate numbers one attached to a D2G and one on a Samsung flip phone.
What have I tried?
Switch between Clean stock Froyo & Stock Gingerbread. Factory Reset, Wipe Cache, Wipe Dalvik Cache. Power Off Phone. Pull Battery. Nothing makes any difference.
If I pull my SIM from my D2G and place it in any other phone, the SAME thing still happens! If I swap the SIMS between 2 affected phones and try, it still happens.
**If I pull the SIM from my D2G and place it in an old Hermes I have lying around calls work perfectly in both directions.**
What works?
Calls to all landlines and most mobiles. Calling a number from the phone using GV or Skype.
Is there any pattern to the destination numbers?
Affected phones are all different brands and carriers, no pattern identified.
Thoughts so far:
It can not be the SIM card as it works in some phones.
It can not be the System version or Radio Firmware version as I get the same issue with Gingerbread and Froyo.
It can not be the cache or any settings specific to my phone.
One of the phones must be an android device.
***Ok, in testing now I just found the problem. If I have the phone set to UTMS then there is no Audio if the other phone is also a UTMS device, but it works fine if the other phone is GSM. If I have the phone set to GSM all calls work all the time to all devices.
The issue is calls between UTMS phones.
At least now I know i can always make/receive calls if I select GSM, I still want to find a solution though.
I am on the Telstra 850Mhz UTMS network in Australia.
I have had the exact same problem with 3 D2Gs. My first phone started after the last Verizon update to GB. That phone was replaced to to a failed dust seal and the first replacement had a failed BT chip. My third phone is now having the same problem, sadly. Of course I'm on Verizon on CDMA. Wish I knew what it was!!
Intermittent No Sound
I have a friend also with a Droid 2 Global
with this same issue.
Seems like leaving Bluetooth turned off altogether
has resolved this issue.
Seems like some sort of confusion when audio is
directed - perhaps audio is intermittently directed to
bluetooth when it should not be...
Any other info suggestions out there ?
Try using ShakeCall from the Market.
It should fix the "silent bug call".
It worked for me and rarely happens. Hope that works.
Please read the detailed post I made and don't post unless you understand what it implies. If you are having no sound problems because you have the volume turned down or mute enabled or you have a bluetooth bug, this has nothing to do with the issue that I have.
I have some kind of low level issue, my guess is that it is something to do with the codec selection based on the network transport type. The fact that the issue is there between 2 phones, then just changing to new Sim cards to identical carrier cards with different phone numbers, removes the issue suggests that the network is storing some information about the numbers. The fact that switching the D2G to GSM makes it work, suggests that the GSM codec is not affected.
I have my phone in GSM mode and now I can make and send all calls, but my data is so slow.
Is there a way I can force the phone to use a specific codec and stay on UTMS?
Ok, so I suspect it is the codec.
I found how to access the programming menu
On the phone's dail pad, enter:
##PROGRAM
Passcode is 000000
Most of the settings are for CDMA, under Test I can change the codec, I'll try some tests.
If anyone knows how to change the default codec let me know!
OK, I found the instructions on Droid Forums..
Pull up the dialer on your phone
Dial ##PROGRAM (##7764726)
Hit Send (the call button)
The password is 000000 (six zeros)
Select "Option 6 - Test Mode"
Hit "Next" until you come to the "Field test screen"
Under "Service Option" (top most), select EVRC-B
Hit "Back"
The phone should then reboot and you'll be all set.
OK, it seems all these settings are for CDMA, I can't find a way to access the GSM settings yet.
Thanks, mactherapy! I've made this change and will report back on whether it helps or not. Good find!! Too bad it won't help you, though.
Sent from my HTC Flyer P510e using xda premium
Well... so far the problem hasn't happened again. This is starting to look promising!!!
Sent from my HTC Flyer P510e using xda premium
Thanks. This works on Droid 3 as well.
mactherapy said:
OK, I found the instructions on Droid Forums..
Pull up the dialer on your phone
Dial ##PROGRAM (##7764726)
Hit Send (the call button)
The password is 000000 (six zeros)
Select "Option 6 - Test Mode"
Hit "Next" until you come to the "Field test screen"
Under "Service Option" (top most), select EVRC-B
Hit "Back"
The phone should then reboot and you'll be all set.
Click to expand...
Click to collapse
I have recently started having this exact same problem on telstra and it is driving me absolutely insane!
If anybody has ANY idea how to fix it on GSM/UTMS please let us all know.
Ok, I am still working on this issue. I figure that if there is some way of changing the default UTMS codec to be the same as the GSM that might work. I am still trying to find the setting for this. However I was looking through the build.prop and I found some settings that seem to have an effect on other issues that I notice.
If you edit build.prop and change the line
ro.mot.phonemode.vzwglobalphone=1
to
ro.mot.phonemode.vzwglobalphone=0
then reboot the phone
The phone behaves slightly differently, the signal strength indicators are more accurate for a start.
Also from what I can see the following options are set to Verizon defaults and are only useful for people on the USA and so should be changed for overseas users..
ro.telephony.gsm-routes-us-smsc=0
ro.cdma.home.operator.isnam=0
ro.telephony.default_network= (set to 7 for global, change to 3 for Gsm/UMTS or 4 for CDMA only)
ro.cdma.nbpcd
keygaurd.no_require_sim=false
These have been discussed a few times (especially .vzwglobalphone).
.gsm-routes-us-smsc is only applicable for Vodafone NL users; for all other carriers, SMS routing is done via local carrier's SMSC.
.default_network doesn't matter at all; it determines the mode the phone starts after a factory reset.
Hey there,
Through the search forum feature I found this issue,
My phone started to do it too, i'm using GSM/UMTS, I've been using the phone since last august and untill 2 weeks ago I didn't have problems.
What I tried was>
Change simcard,
change carrier,
I was on 2.3 I SBF back to 2.2
all without succes.
I only can call one mobile number properly all others are silen,t mobile and landlines alike.
Has there been more succes to get closer to resolve this? I don't mind helping finding it.
I love my D2G and i would get separation problems if I need to change phone
In the end there was nothing anybody could do.
Fault finders at my network provider were just as stumped as me. No amount of reflashing would change anything, the handset was cursed.
I ended up having to give up on it.
The problem continues to get worse. More and more numbers get no audio either when they call me or when I call them. It only happens on the WCDMA 850mhz Telstra network.
The phone behaves normally on any other network or on the GSM Telstra network.
Re-flashing the phone with Miui or CM7 or CM9 or any of the official Motorola firmware's makes no difference. It is a truly crazy problem.
I am going to buy another android phone from Telstra and see if that behaves normally with my sim card. A non android phone I have behaves normally.
The behaviour is still the same, if I am on 3G WCDMA 850mhz on the Telstra network, someone calls me or I call them, it shows the call is connected, neither of us gets any audio, no hash, just silence. Rebooting the phone, changing the rom, factory resets, changing the Telstra SIM, nothing makes any difference. Switch to GSM only and suddenly the issue goes away.
My GF also has a D2G and has exactly the same issue and it is getting worse for her too.
I am guessing that the network is storing something like the phones IMEI on the WCDMA network and then forcing an incompatible audio codec. I don't know enough about the operation of the network to be able to prove anything.
I would like to find some way to force or change the audio codec that gets used when I make calls, is there any way to see what the phone is using for each call?
Ok, another update. I have been doing some more testing. I have discovered that DTMF tones go through to a non Android Telstra phone . Any key presses on the D2G can be heard as DTMF tones on the other phone. DTMF tones do not register on the D2G.
Between two D2G phones on the 850mhz wcdma network there is no audio in either direction and the DTMF tones do not come through either.
As usual switch either phone to GSM and everything works perfectly again.
Right, here we go.
I got a call back a couple of days ago from a tel$tra tech.
This was a long time coming and I have since stopped using the phone altogether anyway.
Basically what you need to do is call telstra tech support and go through the Indian rigmarole with technical support.
These guys will eventually escalate your problem and an Australian tech will call you back.
This person too will be completely useless but do not give up hope.
What you need to do is this: gather data.
Sit down with an internet clock in front of you and log a series of phone calls to numbers that you know the fault exists with and record the details of each failed, no-volume call and weather it was incoming or outgoing, duration of call, type of handsets connected etc etc.
Even though I have given up on the D2G on telstra and moved on, the tech assured me that he would have been able to help with this issue as he had seen it before.
Long time no post, but I found something (I think atleast)
The no sound error occurred only when I make call over the 3G UMTS netwerk. When I forced my Droid on GSM only it worked again.
Has anyone tried this too?
My carrier (KPN Netherlands) has introduced "HD Voice" for it's voice calls over the UMTS netwerk.
Might this be something? Because my Droid started to get the problem around the time the pilot of "HD Voice" was rolled out.
[Not Fixed] see bottom of this post.
It is fairly easy to install a new D6603 to work completly on the AT&T network. It is not so easy to find the answer of how to do it in the threads and posts. I tried many suggestions and wasted a lot of time. Hopefully this will save you from that fate.
First you must know that you can't use the IMEI number of your new phone if you want it to work completly as it should. If you use the Z3 IMEI you will have trouble with data of various sorts and the phone will go off line when on LTE after 20 or 30 minutes and you will not receive calls or SMS messages. I do not know why but it has been suggested that the AT&T network does not recognise this phone so it causes trouble.
If you have an AT&T nano-sim from your old phone then just put it in the phone. (Cut downs work but can cause other problems some say.) When the SIM is inserted for the first time into a new phone there is a prompt that asks if you want to download the APN. Hit 'yes' and the phone downloads the APN itself.
If it does not ask then go to Settings>More>Mobile Networks>Prefered Network Type and be sure LTE (Preferred) is selected. Then connect your phone to the internet and then go to Settings>More>Internet Settings and select AT&T. You should be good to go.
If you need to get a nano-sim then go to the AT&T store or call and they will give you one or send you one for free. You will need to use the IMEI number from a LTE phone that is already on the AT&T system. You can use your old phone or borrow the number from someone. If the rep installs the sim in the Z3 with the 6603 IMEI don't worry. Just call support later and tell them you sent your new phone back and want to go back to your old IMEI or have a new IMEI (from an existing AT&T phone). They will enter it and off you go. The phone from the IMEI will show in the picture on your account page. Big deal!
Update: This worked for hours last night but this morning it is back to not receiving calls. Simply turning wifi off and it began to receive calls as GPRS was switched back on. My wifi was on which has been said to cause problems. I will test with wifi off and report back. Had "no service" instead of AT&T on upper left of lock screen. A full shut down for several minutes than re-boot solved that.
YMMV. I've been on ATT with a Z3 purchased from Sony store for several months and it was registered in an ATT store by scanning the IMEI off the box followed by updating Internet settings in Setup. ATT online shows unknown model but everything works including LTE and MMS. There is something else involved when problems like this occur probably some setting not getting reset. I registered the Z3 on a new line with a new Sim card because I wanted to take my time moving stuff off my old phone--this may have avoided the problems.
JudH said:
YMMV. I've been on ATT with a Z3 purchased from Sony store for several months and it was registered in an ATT store by scanning the IMEI off the box followed by updating Internet settings in Setup. ATT online shows unknown model but everything works including LTE and MMS. There is something else involved when problems like this occur probably some setting not getting reset. I registered the Z3 on a new line with a new Sim card because I wanted to take my time moving stuff off my old phone--this may have avoided the problems.
Click to expand...
Click to collapse
I've also had no problems with my Z3 on AT&T. Works great, receives sms/mms immediately, etc..
esheesle said:
I've also had no problems with my Z3 on AT&T. Works great, receives sms/mms immediately, etc..
Click to expand...
Click to collapse
AT&T's system sometimes takes a while to get updated with new IMEIs that trigger LTE provisioning for a users' account.
Once your account is provisioned for LTE you never have to worry about it again, but sometimes if you have a phone the system doesn't recognize, it is a pain to get AT&T to properly provision your account. Supposedly properly trained in-store reps can do it - the key being "properly trained" - Never try to do anything "unusual" by calling AT&T customer service, and NEVER use a franchise/kiosk in-person for service - make sure you're at a corporate-owned store! Even then, some stores might have incompetent staff. I've been lucky that all of my local corporate stores are pretty well staffed.
So you are saying that your Z3's with wifi and LTE on with AT&T are working as they should?
With LTE off my phone responds normally with wifi on. With LTE and wifi on it will not respond to calls after a 30 minute sleep. It does not show missed calls. Calls go straight to voice mail after 2 rings. Could you tell me what level your LTE dBm's are? Thanks!
I was told not to give them my imie# but, after recvng the minisim I had to call them in order to 'provision' it to work at all and they needed that #. I have never had any problems personally and am assuming this may be because you gave them the wrong #. Again I am only guessing. Oth, if I had had a different imie to give, I would have done so myself.
It is very strange and I am feeling it is more signal strength related than how you provision your phone. (Once it is provisioned correctly.) It seems that more people have less problems when they already have a nano-sim and just plunk it in the new phone. This might indicate that they already had a strong signal from the get go. My old HTC One + get's a better signal than the Sony in the same locations with the same (new) SIM. With the Devilcase bumper on it gets 5% less. My very limited tests yesterday seemed to indicate that it was signal strength related. I am not enough of a conspiracy theorist to imagine that AT&T would program their system to not function correctly with sims that are provisioned with these Sony phones which they are obviously ignoring for some reason. Or am I?
I had all kinds of problems with the Z3 on AT&T. The IMEI caused an issue since AT&T linked it to a flip phone and therefore couldn't provision LTE. I changed it to an old AT&T LTE device and then I was able to get LTE but was having the same issue with calls going directly to voicemail and texts showing up hours later in bunches. I found the solution was to switch off LTE in the quick settings menu. All calls and texts came through and on time while LTE was off. If I needed a data boost to stream, I turned it back on until I was finished streaming. This was while on KitKat. After upgrading to Lollipop, I was able to keep LTE turned on and calls and texts still arrived on time.
I use data rarely. Mostly wifi. If I don't leave LTE on, my phone reverts to wcdma preferred. And why can't LTE just work without me having to constantly turn it back on? What bugs me is having the APN settings greyed out. I want to be able to turn it off. If anything it seems the phone itself is preventing me from accessing the sim. It feels like I'm borrowing something which contains lots of MY private data. I know my phonebook is stored locally but I also noticed there is no option of specifying the sim or not. Anybody know how to switch APN on and off? In fact, overall even rooted, I still feel like I have almost no power over it. I can't even disable the cellular connection without going full on airplane mode and I do not trust that. I don't even fly so that needs work for sure. Dumb question but could I buy a working nanosim from say 7-eleven that my apn switch will work with?
"Anybody know how to switch APN on and off?"
On my Z3 on OTA stock Lollypop I have an icon in quick settings to turn LTE on and off. Drag two fingers down from the top of the screen. If no LTE icon then select the pencil icon at the top and select the LTE icon. There is also a mobile data icon switch there.
To turn off your radio completly you can get the Advanced Signal Status app and select additional info at the bottom and click phone information and turn off radio. Probably a number of ways to do it but that is one.
Sim contact storage was a way to move information from phone to phone. You can still do it but not really necessary with cloud backup and storage. Google does it for me without me having to do anything which I like. I still save contacts to the sim just because I can. Export and import in your contacts app menu.
johnboatcat said:
So you are saying that your Z3's with wifi and LTE on with AT&T are working as they should?
With LTE off my phone responds normally with wifi on. With LTE and wifi on it will not respond to calls after a 30 minute sleep. It does not show missed calls. Calls go straight to voice mail after 2 rings. Could you tell me what level your LTE dBm's are? Thanks!
Click to expand...
Click to collapse
Works fine here. I don't pay attention to the dBm estimates since these aren't measured with calibrated test equipment and vary widely. Those numbers are basically worthless.
The only valid comparison is data performance in a given environment (ideally a difficult weak-signal one) - and at my desk with very weak signal, every phone I've ever used performs similarly to the Z3.
"Those numbers are basically worthless."
True, but we have narrowed this down to the possibility that it might be signal related so it is worth a shot. If people whose phones are working fine would measure the LTE dBm on Advanced Signal Status at the location where their phone sits and works well the most we might possibly see some measure of difference in the phones that are not working. Most of the non-working phones seem to work sometimes so signal strength is the next best parameter to rule out. Thanks!
Here are the screen shots of my phone with LTE on, LTE and wi-fi and LTE off and wi-fi.
How do the working phones compare? Does your CDMA (voice) also go to 0% when LTE is on and GSM = n/a?
Thanks. I think adv sig nfo actually works. I'm amazed actually. I can't find the phone's native greyed out apn switch anyways which really makes no sense.