Hey guys,
I'm having issues connecting my to network provider (AT&T) every time I restart my phone. Every time I restart, I'm greeted with a limited signal notification and reseating the sim card does not help. Toggling airport mode on and off will, however, reacquire my cell signal and LTE from AT&T. This is a problem that has occurred with sense based roms - I've had this issue with HD android, scott's rom, nocturnal, trickdroid, insert coin.
My baseband is 4A.16.3250.24_10.38.1150.03L
I'm using the AT&T HTC ONE.
I've checked the APN settings and they are correct.
I do not have this issue with non sense based roms (CM 10, AOKP).
Has anybody encountered this issue as well?
Related
I got a device swap today on my Nexus One, so I rooted the replacement phone and restored a nandroid backup of my previous setup with CM6.1 RC1. No problem so far.
Within a few hours of doing this, I noticed my phone still had the FRF91 (4.06) radio. On my previous N1 I'd flashed the 5.12 radio and it was working well, so I flashed it using the appropriate update.zip.
I should point out that I always keep my phone in 3G mode because my provider, WIND Mobile, does not have a 2G network, and any time it's on 2G it is roaming on a partner network at a higher cost to me. I also have data roaming disabled.
After the phone restarted, I noticed within a few minutes that it was connected to the roaming network (WIND Away) and using EDGE data - even though it was set to 3G-only mode *and* no data roaming! I quickly disabled data and flashed back to the 4.06 radio. I didn't see the problem again.
But now upon further testing, I'm still seeing something disturbing. If I flip it to EDGE mode it connects to WIND Away, but the signal indicator doesn't have the roaming "R". Somehow the phone does not recognize that it's roaming anymore. This is incredibly dangerous because it could rack me up huge data charges. Prior to the device swap, any time it was on Wind AWAY I would get the "R". And when I put in my T-Mobile SIM while in Canada, I do get the "R" as well.
Any thoughts on what to do?
I'm having the same problem. I don't think it's related to the radio, but rather 6.1 rc (or in my case nightly ver 245). I'm using radio 5.12.00.8, and when I restore a nandroid backup of cm 6.0, using the same radio the roaming indicator works as it should. Looks like it might not confined to NexusOne http://forum.cyanogenmod.com/topic/9065-is-cm61-rc1-better-than-cm6-stable-for-you/page__view__findpost__p__83991 Hopefully it's not some Wind quirk with cm 6.1
Hammy
hammies said:
I'm having the same problem. I don't think it's related to the radio, but rather 6.1 rc (or in my case nightly ver 245). I'm using radio 5.12.00.8, and when I restore a nandroid backup of cm 6.0, using the same radio the roaming indicator works as it should. Looks like it might not confined to NexusOne http://forum.cyanogenmod.com/topic/9065-is-cm61-rc1-better-than-cm6-stable-for-you/page__view__findpost__p__83991 Hopefully it's not some Wind quirk with cm 6.1
Hammy
Click to expand...
Click to collapse
Yikes, glad to hear I'm not the only one. Let me summarize:
- WIND SIM roaming on T-Mobile: Roaming symbol.
- T-Mobile SIM roaming on Rogers 2G: Roaming symbol.
- T-Mobile SIM roaming on WIND 3G: Roaming symbol.
- WIND SIM roaming on Rogers 2G: No roaming symbol, tries to access EDGE data (OUCH! expensive).
This should probably get its own topic at the CyanogenMod forum.
The Testing screen (*#*#4636#*#*) also has an entry for "Roaming", and when I'm on WIND Away it says "Not roaming" - boo.
I created a thread about this on the Cyanogen forum :
forum.cyanogenmod.com/topic/10193-cm61-rc1-and-roaming-indicator/
But so far it's mainly me :/
Sent from my Nexus One using XDA App
Just an update, the problem has been resolved for future builds of CM. Read the link to the CM forums for more detail.
For quite some time now, my phone has been having some terrible 3G connectivity issues.
It just drops from HDSPA to UMTS and gives me no data for chunks of time. And every now and then, the entire 3G turns off(as if the APN has been switched).
This has been occurring with MIUI 2.2, MIUI 2.3, CM6 and CM7.
Im using 5.12.00.08 radio (latest i think). Im unsure what HBOOT I'm running, but the full baseband version is "32.50.99.32U_5.12.00.08". So i think I'm running HBOOT 32 but im not sure. With the CM and MIUI roms the problem was occurring on stock kernels and monk's.
Any ideas on what could be causing the issues? If you would like me to send logcats i can(i haven't seen anything in there to indicate any issues)...
Also i found a post:
http://forum.xda-developers.com/showthread.php?t=931728
Not sure if thats related.
Seemingly the problem started occouring after i was using alot with WiFi Tethering with Wireless Tether by Lemons and co.
I'm using Virgin Mobile AU as carrier.
Also, the problems occurs before installing ANY apps as well(and afterwards obviously).
32.50.99.32U_5.12.00.08
mine is only 32.50.00.32U... IMO just try flashing a new radio, start with 5.08 instead of 5.12 and see if that works then if you are content then leave it... else flash 5.12 after and try to root out the problem...
cheers!
The default setting in nexus one is WCDMA preferred... i.e. it connects to 3G if available.
If the signal strength of the 3G network is lower than than 2G network,
it switches to 2G rather than connecting via 3G.
However, Its a known limitation that Nexus one 3G reception is comparatively less due to physical properties of the antenna.
I have SPRINT HTC ONE M8, unlocked for GSM network in Croatia, Europe. Stock ROM.
Ever since day 1 I am having data connectivity issues; sudden drop of mobile data connection for couple of minutes every now and then. If I am not mistaken it was a big series bug on SPRINT HTC ONE M8 phones which was quickly addresed by Sprint via the software update. I can download the software update (I couldn't do it on a custom ROM) but I can not install it, I get a message saying; "The operation is not allow under GSM network, please switch to CDMA network".
Does anyone have experience with similiar mobile data issues?
Will any other custom ROM sort this thing out?
Many thanks
Hi guys!
Around 2 months ago I started having some issues when connected to the 3G network. Most of the times, it didn't transfer at all and my network icon was with the "!" sign.. I was on PAC LP and I blamed it (or some software-related cause). However, if I marked "Use only 2G networks", it did work...
I flashed the phone yesterday. A clean, fresh and quite deep install (wipes, .228 FTF, new kernel, new ROM -eXistenZ-, etc etc). The surprise was that I still have it... If I try to connect to 3G networks I might get a couple of seconds of connection, but then it just disconnects and stays like that until I change back to 2G networks... Just in case I reflashed again, same procedure, and it's still there, even on stock .228...
I bought the phone 2 years ago (in Europe, that's why I can't use LTE here), and never had a problem like this. Of course, I'm at the same place with 3G coverage (other phones do work), I've already tried different APNs, providers, etc, so I hope not, but I'm starting to think this could be related to a hardware issue...
Does anyone have an idea? Is there any software part that is not changed during a flash and could be responsible? Or maybe how to rule out hardware or software issues? This happened while I was on PAC LP, stock .228 and eXistenZ...
Thanks in advance!
It could be many factors involved - one of them could be that the operator you are currently connected (ex. Vodafone, At&t) maybe changed all their antennas in your area from 3g to 4g, and that would result in your lack of connecting to 3g.
I once changed my operator because it had better offer and then I regretted it since the connectivity was worse with the second operator and would constantly switch from 2g to 3g to 4g, all this with a major impact on battery life.
It could be also hardware related, but I wouldn't bet on it. Try checking with another phone with the same sim in the same areas to get an idea what it might be.
aaronkatrini said:
It could be many factors involved - one of them could be that the operator you are currently connected (ex. Vodafone, At&t) maybe changed all their antennas in your area from 3g to 4g, and that would result in your lack of connecting to 3g.
I once changed my operator because it had better offer and then I regretted it since the connectivity was worse with the second operator and would constantly switch from 2g to 3g to 4g, all this with a major impact on battery life.
It could be also hardware related, but I wouldn't bet on it. Try checking with another phone with the same sim in the same areas to get an idea what it might be.
Click to expand...
Click to collapse
Hi aaronkatrini.
Thanks for your answer! However, it's not my operator's fault:
- All other phones in the same area do work.
- Other operators (other SIM cards) in my phone have the same issue, so I guess it's related to my phone, software or hardware...
I haven't checked yet another phone with my SIM card, I could try that to rule completely out the SIM card/operator's fault.
Thanks again!
Greetings folks. I own a Nexus 6 XT1103 Unlocked. I'm on MetroPCS currently (piggybacks off T-Mobile LTE).
On Android 6.0.1 ROMs the device connects to LTE networks with no issue whatsoever. The real issue arises when I flash an Android 7.x ROM. The device connects to 3G (UMTS/HSDPA) and remains there even though the network setting is on LTE.
The phone momentarily connects to LTE when I reset the radio from LTE Discovery app and then reverts to 3G (the LTE signal detected just drops off to N/A). Also when the device is momentarily connected to LTE, the carrier label changes to 'No Service' even though network is available and LTE data works for those few moments. After those few moments it's back to UMTS and the carrier label returns to 'MetroPCS'
I've tried the following things to fix this (all in vain)
1. Flashed different radios (05.32, 05.34, 05.42) and bootloaders
2. Flash Android N stock image and then flash custom 7.x ROM
3. Go to the *#*#4636#*#* menu and set LTE only.
4. Resetting APN to default and manually adding APNs (both MetroPCS and T-Mobile)
I know the LTE network in the area is fine otherwise and anyway the moment I'm back on MM the issue the device connects to LTE properly (with a valid MetroPCS carrier label). This issue occurs on any Android 7.x ROM but it didn't happen as often in the Dev Preview, if I remember right.
I request all of you folks to help out if you've seen something like this or have any solutions. Cheers.
PS: Google Connectivity Services installed/uninstalled/disabled doesn't fix it
Have you tried a network settings reset? This worked for me when I lost LTE connectivity.
Settings>Backup & reset>Network settings reset.
Make sure you select network settings reset and not factory reset. They're right next to each other, so if your finger slips and you select the wrong one you'll be very unhappy.
Fixed it!! Flashing the 05.39 radio on fastboot before flashing the ROM seems to do it. Now LTE works with the proper carrier label too. I'd forgotten about the 05.39 radio as it was the one bundled with the N Dev Previews.
Cheers!