hi,
I'm on day 2 of trying to sort out my wife's new Captivate, so would appreciate any help at all. Phone is rooted, unlocked and has decent signal, but I cannot connect to 3g.
I'm on Optus network via TPG (Aussie network). I've tried many APN settings, and I'm at the point where I don't think this is the issue (yes, I know this is normally the issue).
I tried going into *#*#4696#*#* and doing WCDMA preferred, and WCDMA only, made sure AUS radio band was selected and did 'Enable data'.... also no help
I've also made sure data is enabled on the sim/account. If I insert the sim into another phone, it works with 3G. So it's something to do with the phone for sure.
Optus' 3g info says "2100MHz frequency band. Enabled with High Speed Packet Access technology (HSPA)". So WCDMA is the correct setting I think.
To be clear, I've never gotted the little 3G symbol at all (or an 'H' symbol that I've seen someone mention). I first tried emulating my own Vibrant's settings exactly, which didn't help.
Any ideas would be great.
thanks.
I'm completely out of options ... is there a chance this is an issue with bad contacts? I fixed my Vibrant's GPS by prying up one of the contacts...
All fixed. If anyone else has this trouble - flash back to stock, following this guide http://forum.xda-developers.com/showthread.php?t=884364
Note - I already had stock, so no idea what the hell was going on, but whatever.
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.
Has anyone been able to use the "Video Call" app that Samsung provides, on the i667? It's supposed to enable standard 3G-324M video telephony calls over networks that supports it, as long as the phone has a front facing camera. At least, that's what it claims. Anyhow, I'm trying it on my network to no avail. Same SIM in a different device, no issues. It's an older UMTS phone, not a smartphone. Somehow, I can't seem to find any device that this app works on, nor any network. Any clue anyone? And please don't suggest using a data solution, that's not what I'm looking for, I am looking for a ITU standard, 3G-324M video telephony solution on Windows Phone 7.
thanks.
Hello. I have a problem with my phone, which i did not faced before on other Windows Mobile devices (this is my firs 6.5 one).
Samsung Customer support, lighlty saying, did not helped me redirecting me to my carrier, which i do know is not faulty.
So, when phone have established 3G data connection (neverthless is it internet or mms) i cannot send text messages. Phone acts like there is no range or number was invalid.
When i switch band from WCDMA to GSM, full duplex works like charm. In my opinion i've paid (it's second hand device, but who cares) for fully featured phone and switching band does not solve my problem (in my place only WCDMA works, on GSM band voice calls are choppy and signal still gets lost).
I would me more that gratefull is someone can help me with this strange problem. Phone is used in Polish network Play Mobile (260 04), is sim unlocked (don't know was is locked at all earlier).
What i've done: i've changed sim card to other provider (T-Mobile), did hard reset, upgraded to latest ROM (upgrade_tool_for_sph-i350_ver.1.4.1.0), and lurked in registry searching 3g-, data-, duplex- related keys and values.
Someone faced similiar problem in this device or system?
edit. After checking some settings on SGH-i600 i've found that there's setting to change SMS sending method. It's called 'Send SMS Option' in Connections,and it has 'Network seletion' (not selection ;p) with options 'PS preferred' and 'CS preferred'. In my opinion it's Nokia's coresponding option 'sms over GPRS', which makes on Nokia device to send messages faster.
Anyways, changing this option to PS changes value in HKLM/Comm/Cellular/SMS/Router/ServiceOption from 4 to 8. Changing this value on target device (i350) does make smses not to send at all, regardless if data connection is on or off.
Does*anyone know how to get rid of the Vodafone WiFi calling notification? It appears at the top of notification bar and also on my lock screen, when I have poor signal and it connects to WiFi calling mode. I can only mute it for 2 hours at a time. In the notification settings it comes under "IMS service" which is a system app that it is*greyed out so can't be switched off. I never had any notifications when WiFi*calling*was connected with O2 but I do since changing to the N20 and my new carrier Vodafone. I find this irritating.
Did you ever find any joy with this problem?
I'm having the same issue on my Z Fold 2, I've just switched provider to Vodafone from Three and the IMS Service/WiFi calling notification is unable to be disabled.
It must be Vodafone related as I used WiFi calling on three and never had this issue!
No it's still there! I've just got used to it now
Hey,
I'm having the same problem too. As far as I can tell this seems to be an issue unique to Vodafone users - indeed in the Vodafone's network options menu, the ability to turn off these notifications is greyed out. Same sim card into a friend's phone = same problem. My friend's O2 sim card or another friend's EE sim in my phone = no problem. I've raised this with Vodafone repeatedly and the consistent response from their technical support team has been that a) this isn't a problem that has been raised before; b) that it's something that needs to be fixed across the whole network's standard SIM functionality and they can only do that for widespread issues. Both of these answers are entirely untrue. I keep raising it and I've now formally complained about it.
In the meantime, I use an app called BuzzKill, which although isn't free and for me isn't always 100% effective at muting the Vodafone WiFi Calling notifications, it certainly catches most of them so the £2ish was well worth it. Easy set up too (and no, I don't work for them ).
I found out by enter info then enable wifi calling then disable it goes away.