Database Users

Turning of Roaming completely

Not sure if this is the correct forum but I want to be able to turn of roaming completely. I have a US G1 on the three UK network with the US RC33 installed and root. I have disabled data roaming. Here in the UK we're too small a country to want to roam! Coverage is usually good enough from a single network. However, I occasionally get the little 'R' symbol on the single strength icon and an annoying prompt saying I need to turn data roaming on because I lost connectivity. I have to go into the settings and manually select the "3" network again.
What I want is to either be connected to three UK or not connected to anything at all. Is there a config file I can edit to allow this? Would the UK RC8 firmware do this for me?
Thanks in advance for any help.

Doesn't a 3-UK SIM try to roam onto O2 though?
You could set the phone WCDMA only and NOT roam onto a GSM network.
Use AnyCut to shorcut Activity: Phone Info
From there under preferred Network Type; set to "WCDMA Only"

HELP!! Roaming signal won't go away
I have an unlocked G1, JF1.41 v 1.1 and i just updated to the RC33...but this also happened when i had RC30 , v 1.0...
I put in my canadian Fido sim card and everything works fine but i have that little "R" on top of my signal strength bar...
I think this means its data roaming? if this is the case...it should be okay (even though its going to bother me) because my service provider says my EDGE/Data is disabled (i do not have a data plan, NOR do i wish to incur any data charges.. i'm fine with my free WIFI ) .
However, if this means im roaming on another network, i dont want to be incuring any long distance charges on my phone EVEN when im using my own FIDO network..
I went to settings - about phone - status, and here are my specs (some of them):
Network: Fido
Network Type: EDGE
Service state: In service
Roaming: Roaming
Data Access: Disconnected
i'm pretty much just concerned about the ROAMING part of it... my other friends with G1's are with rogers, don't have that little R..
how do i get rid of that?? please and thanks!

Try manually changing the network in Settings>Wireless controls>Mobile networks>Operator selection
G1, like all GSM phones, will roam onto networks specified on the SIM if it can get a better signal. As long as the relevant operator has a roaming agreement in place, there's nothing to be concerned about, other than the R symbol in the status bar.
Mod: move this over to General discussion please.

I did change it and selected my Fido network (it's the only network available).

Thanks. I've set it to WCDMA only so I'll see how it goes.

Please help??? i still have that little R on top!

After I got home I found my phone had lost its connection. It didn't seem to be searching for the network. I had to go into settings, search for networks and then select three again. Is there any way to control if the phone does a search for networks automatically?

Looks like it reconnects to three on its own after a while. I still get the annoying popup about turning on data roaming though

footboydog said:
Looks like it reconnects to three on its own after a while. I still get the annoying popup about turning on data roaming though
Click to expand...
Click to collapse
As has been previously mentioned, Three will "roam" onto another network if it goes out of Three's own 3G network coverage because Three does not run its own 2G network.
However, it isn't O2 anymore, it is Orange as of late 2006/2007. I *believe* that you won't be charged any more if you use data whilst "roaming" on Orange, so whilst you are in the UK it is quite safe to allow data roaming, but I would be inclined to check this with Three.
Regards,
Dave

After filing a complaint with the FCC against Verizon, I got a call from a VZW rep

So, as some of you know, if you use the XT1060 with T-Mobile and connect to LTE, you'll have one of two issues: 1) it connects to LTE, but you can no longer call out (or receive calls) as the phone falls back to CDMA even when locked out in the network settings, or 2) it doesn't connect to LTE because it locks the T-Mobile 3G APN in even when a manual entry T-Mobile LTE APN is selected (my issue). My X absolutely REFUSED to move to fast.t-mobile.com and failed to connect to LTE and had absolutely no signal whatsoever (no HSPA or GSM even when on LTE/GSM/UMTS). The reason from the tower: APNfailed. Tried a million times to change the APN in the LTE area to no avail.
I've found it will only change to fast.t-mobile.com (manually entered) in a non-LTE area. Well that's a great inconvenience. I had to disable LTE completely and restart the phone to get it back on HSPA+ (or wait 5-10 minutes).
Anyway, the Verizon rep called me to "troubleshoot" my issues when connecting to T-Mobile LTE. I refused to go through the typical troubleshooting steps because none of it worked when I tried, so it's not magically going to change. I found that interesting (that they'd call me) even though I've had no direct contact with Verizon. Anyway, nothing was really resolved.
Both of these issues are violations of the C-block agreement. Also, if you select Global mode, it'll default to EDGE even though HSPA is available. It'll go to HSPA after selecting LTE/GSM/UMTS, UMTS only, then move back to Global. Interesting how they make you go through these hoops, eh?

Jason.DROID said:
So, as some of you know, if you use the XT1060 with T-Mobile and connect to LTE, you'll have one of two issues: 1) it connects to LTE, but you can no longer call out (or receive calls) as the phone falls back to CDMA even when locked out in the network settings, or 2) it doesn't connect to LTE because it locks the T-Mobile 3G APN in even when a manual entry T-Mobile LTE APN is selected (my issue). My X absolutely REFUSED to move to fast.t-mobile.com and failed to connect to LTE and had absolutely no signal whatsoever (no HSPA or GSM even when on LTE/GSM/UMTS). The reason from the tower: APNfailed. Tried a million times to change the APN in the LTE area to no avail.
I've found it will only change to fast.t-mobile.com (manually entered) in a non-LTE area. Well that's a great inconvenience. I had to disable LTE completely and restart the phone to get it back on HSPA+ (or wait 5-10 minutes).
Anyway, the Verizon rep called me to "troubleshoot" my issues when connecting to T-Mobile LTE. I refused to go through the typical troubleshooting steps because none of it worked when I tried, so it's not magically going to change. I found that interesting (that they'd call me) even though I've had no direct contact with Verizon. Anyway, nothing was really resolved.
Both of these issues are violations of the C-block agreement. Also, if you select Global mode, it'll default to EDGE even though HSPA is available. It'll go to HSPA after selecting LTE/GSM/UMTS, UMTS only, then move back to Global. Interesting how they make you go through these hoops, eh?
Click to expand...
Click to collapse
Wow. Hopefully something changes with Verizon and letting people use LTE on other carriers. I know almost all Verizon phones don't get LTE on any carrier other than Verizon even if the LTE bands are supported. Verizon is full of crap.

[Q] Stuck on "EDGE". How can I change the Network under "SIM Status" ?

[Q] Stuck on "EDGE". How can I change the Network under "SIM Status" ?
I'm running Dirty Unicorns 9.8 OFFICIAL (5.1.1) on my Nexus 4. The other day I noticed I had like one or two bars so went into Settings > About phone > Status > SIM Status and clicked "Network". Usually, there are a handful of providers to use there and sometimes changing to a different one improves my reception (This is a T-Mobile phone). I don't remember what I left it on.
Today the phone is stuck on "EDGE" under "Cellular Network Type". I tried to get back in the "Network" to check and see if I left it on something stupid, but I can't get back into the provider selection. No matter what I do, the device won't hook up to "LTE" (whatever HSPA/HSPA+ thing T-mo says is LTE). Everything worked fine last week. Haven't applied any patches or anything other than messing around with the Network settings. Any idea what I might try? Is there a magic dialpad entry to use to reset the Network?
Thanks

eris170 said:
I'm running Dirty Unicorns 9.8 OFFICIAL (5.1.1) on my Nexus 4. The other day I noticed I had like one or two bars so went into Settings > About phone > Status > SIM Status and clicked "Network". Usually, there are a handful of providers to use there and sometimes changing to a different one improves my reception (This is a T-Mobile phone). I don't remember what I left it on.
Today the phone is stuck on "EDGE" under "Cellular Network Type". I tried to get back in the "Network" to check and see if I left it on something stupid, but I can't get back into the provider selection. No matter what I do, the device won't hook up to "LTE" (whatever HSPA/HSPA+ thing T-mo says is LTE). Everything worked fine last week. Haven't applied any patches or anything other than messing around with the Network settings. Any idea what I might try? Is there a magic dialpad entry to use to reset the Network?
Thanks
Click to expand...
Click to collapse
Same problem here with metro pcs who uses T-mobile

After a few days of this, and several chats and calls to T-Mobile, it seems T-Mobile is "working on towers" in my area and things will be like this for a few days. The situation is this according to the last phone call with T-mobile:
* HSPA+ is no longer available on the towers in my area
* LTE and GSM (Edge) are the only supported modes
* LTE is not supported on the Nexus 4. tuff-shizz. buy a new phone.
Ok well this sucks... so here's what I did in the past couple days.
* Installed Chroma ROM and the the LTEEnable zip file thing floating around all the forums here.
* Found out Chroma was a rebranded AOSP ripoff so uninstalled it.
* flashed Dirty Unicorns 6.0.1 to my Nexus 4, bluetooth seemed funky so flashed the .33 radio from "dmitry" ROM that I found on several threads. Also flashed LTEEnable zip, not sure I needed it. LTE now working.
* dialed *#*#4636#*#* and went into "Phone Info"
* Network Type: "LTE"
* Set Preferred Network Type: LTE/GSM (PRL) -- originally had this set to "LTE only" but no voice calls could go out, or come in.
You would think this is the end of story, but wait. Voice calling takes 20 seconds to connect (even voice mail). With "LTE only" settings all incoming calls go directly to voice mail. never even rings the phone. Are you shizzing me?? With "LTE/GSM (PRL)" the phone waits for 20 seconds to drop from LTE back to "Edge" before the call finally hooks up.
Today, found out nexus 4 doesn't do VOLTE (Voice Over LTE). at least thats what google said. That would explain the Drop to "Edge" when dialing out.
Thing is, I tried this with a NEXUS 5 on my account, using two different sims , running stock Android Whatever on the N5 and it does the EXACT SAME THING. dropping calls to "Edge" before connecting. Takes 20 seconds to dial out. Incoming calls on LTE (which the n5 runs by default) all go to voicemail.
So it seems the workaround now is to dial the "magic number" above and set the "Preferred Network" to "GSM only" (Edge). That's the only way to get phone calls in or out of either device on T-Mobile's network today. Don't bother trying to Google anything though because it won't re-connect to LTE to do it. On either my hacked N4 or the stock ROM N5. You may as well be using a dial-up modem to get any data through either phone.
So, in the end, I don't have anything screwed up under "Network Settings". I'm stuck in "Edge" mode because Tmo is updating towers for LTE. It remains to be seen if I have to upgrade both and N4 and N5 to stay on T-Mobile however. The next few days will tell. I still think this is a bit of a ****-move on T-Mobile's part. Especially if I have to upgrade the N5. It's an expense I wasn't planning on. They could at least kick in some rebate to help out with the cost of new devices. No idea if it would save any money to switch carriers at this point.

935p unlocked and flashed to 935u but can't pick up cdma bands

So maybe this was a bad idea but I'm on boom mobile (verizon mvno) and thought I could save some money and picked up a sprint s7 edge on sale, I just had it unlocked and they flashed it to the 935u unlocked version. The problem is I can't connect to the verizon network, after playing around with it a bit I got it to connect to the verizon lte network but still no voice. In my meager attempts to troubleshoot I noticed I have the options under network mode of
LTE/3g/2g -->> this picks up all networks in my area (Verizon, Sprint, ATT, Tmobile, US Cellular)
3g/2g --> only shows ATT and Tmobile
3g --> only shows ATT and Tmobile
2g --> only Tmobile
So I'm thinking my phone isn't setup right to connect to cdma networks which I thought the 935u rom was supposed to do. Anyone have any tips on how i can further troubleshoot this?
Thanks in advance.
edit: Well I installed a program called 4g LTE switch and set it to cdma only and I was able to make a phone call (3g data also worked) like that but changing it to LTE/cdma wouldn't let me make a call but LTE data worked, if i leave it set to LTE/cdma and reboot it switches back to LTE only.
edit2: Maybe it's trying to connect to volte which isn't offered for Verizon MVNO's yet but i don't see any settings available to disable that.
edit3: When set to LTE/CDMA I could sometimes make outgoing calls, sometimes I would get the double dial prompt, it was very slow to switch between LTE and CDMA so I would miss incoming phone calls.
I threw in the towel and just flashed the latest Verizon rom and it's working properly.

Second Galaxy S10+ dropping signal when phone is locked for 2+ min

I bought a brand new factory unlocked Galaxy S10+. I popped in my Tmobile sim card but my calls goes to voice mail and I can't make any calls in following conditions.
I also tried Verizon sim and it acts the same way so not sure if network is the culprit.
1) When the wifi is on, my phone identifies network as I see 'Tmobile' in screen, signal strength is '-113 dBm 0 asu' but no actual incoming/outgoing call.
2) When the wifi is off, but screen is locked for 3-4 min, I still see 'T-mobile' but no incoming/outgoing call. Also, the service state changes 'In service' to 'Out of service' intermittently where I have to toggle aeroplane mode.
So, I have to toggle aeroplane mode on/off to get the network back while wifi is off, signal strength is '-81 dBm 59 asu' then everything works normally until I lock the screen as in step 2 or use wifi as in step 1.
This is my second replacement phone and it is behaving the same way as the first one. So, I am not sure if I am having bad luck with Samsung phones or if something is funky with my network. I also have a S9+ which has no issues at all with same sim cards and network coverage is excellent in my area.
Any idea or suggestion would be really helpful. Not sure if I should just change the firmware from U1 to Tmobile or something.

I would check your APN settings to verify that they are correct. I am on T-Mobile network with U1 firmware and have no issues with calls (I'm on MintSim which uses the T-Mobile network) but when I popped in my SIM no T-Mobile APN settings autopopulated--I had to enter the APN settings manually.
You should also make sure Volte is enabled in the network settings and WiFi Calling is enabled in the dialer settings.

jhs39 said:
I would check your APN settings to verify that they are correct. I am on T-Mobile network with U1 firmware and have no issues with calls (I'm on MintSim which uses the T-Mobile network) but when I popped in my SIM no T-Mobile APN settings autopopulated--I had to enter the APN settings manually.
You should also make sure Volte is enabled in the network settings and WiFi Calling is enabled in the dialer settings.
Click to expand...
Click to collapse
Thank you for your response. My T-mobile APN settings auto populated and looks fine as I have LTE connection. The issue is that the connections keeps dropping and all my calls goes to voicemail in above two scenarios.
If the LTE didn't work at all or if my calls went to voicemail all the time, I would understand that some settings are not setup properly. But it works intermittently. Since, this is the second Galaxy S10+ with same exact issue, I am not sure if there is a issue with device or carrier.