So before i rooted my droid incredible my service was perfectly fine and after i put 2.1/3.0 rom on my phone, my service started to fall back and function when it wants to. I was wondering if the reason behind this was because i rooted my phone before Verizon came up with their 4g service and maybe it has made some sort of interference. Any help? thanks.
It would help to know which ROM you flashed...
Im almost positive an RUU would do you wonders.
If you used an EVO based 2.1/3.0 ROM and did a *228 that might be your culprit.
I would make a nandroid and then perform an RUU.
Hope this helps.
humm im running an evo 3d based rom and radio and i did a *228 it runs without issue. And i have checked on someone running a phone on stock and on a inc based rom/radio mine actualy has better signal than they do...
There have been many reports of people getting this kind of issues poping up it is due to several factors many areas had altell/cellular one towers that now belong to verizon and had to be given to at&t per the terms of the fcc laid down. Add to that a nation wide upgrade for all towers and there are some wonky issues poping up. Best thing to do would be to call verizon and report the issue of getting a bad signal in an area you previously got better signal. They could be unaware of damage to a tower or someone might be operating illegal equipment in the area...
Why would AT&T want Verizon's towers? One is GSM one is cdma.
That was part of the deal verizon had to make to buy altell. Towers with certain criteria had to be sold to at&t some were altell towers some were verizon towers. But at&t gained them and had to retrofit them to run gsm. Customers of altell in the areas that had to be sold to at&t got sold to at&t as well. Though the merger did give them an out if they did not want to go to at&t or verizon.
I currently am running an optimized shift rom. I did a *228 and the same issue is occurring but i have noticed my calls and text messages seem to go through just fine but when i surf the browser, it will not connect 98% of the time.
jazy123 said:
I currently am running an optimized shift rom. I did a *228 and the same issue is occurring but i have noticed my calls and text messages seem to go through just fine but when i surf the browser, it will not connect 98% of the time.
Click to expand...
Click to collapse
You might have better luck with an AOSP ROM or a non-3.0 Sense ROM.
3.0 are probably the heaviest/loaded ROM's.
The issue seems like your regular signal is fine but 3G is lacking? Try downloading speedtest.com and see the results.
Also 4G in no way interferes with 3G unless they are doing work on a nearby tower, that may temporarily degrade your 3G performance.
Hi,
I just received an unlocked International Galaxy Note II in the US. Ordered from Handtec in the UK, and the phone appears to be the French model. I have observed what I think is a problem when trying to use the phone on T-Mobile USA.
I put my T-Mobile USA SIM card in the phone, and the phone thinks I am roaming. Uhhhh no. It's a T-Mobile USA SIM card on the T-Mobile USA network. It is NOT roaming. Now, it probably doesn't have any impact beyond the "R" notifier, and a "Roaming" page which shows up on TouchWiz, but it DOES make me feel very uneasy. I have to enable "Data use while roaming" to be able to use data while on my home network!! It's crazy!
To those who will point out, yes, I know that T-Mobile USA has their 3G currently on the AWS 1700/2100 band, which the Note II does not support. I am therefore using EDGE with this phone. (Yes the data speeds suck, but T-Mobile's refarming will make this problem go away in the next few months). Even though I am on EDGE, I am not "roaming" unless the Note II's definition of roaming is different from mine. I am still on the home network, regardless of whether I am on 2G or 3G.
Has anyone else seen a problem like this?
If I can't figure this out in the next day or two, I may return the Note II and just wait another month or so for the T-Mobile US version. (Probably that's what I should do anyway, but I figured the GT-N7100 would get more developer support).
Hope someone can help!
Thanks!
Edit: I forgot to add - I also have and unlocked international Note 1 GT-N7000 and an unlocked iPhone 4. Neither possess the T-Mobile USA 3G band, and neither of which show roaming when I'm using T-Mobile USA. So, either T-Mobile did some funky network work today which changed something, or there is something different (and possibly a bug) about how the Galaxy Note II determines if it's roaming.
Unfortunately I cannot be of any assistance to your issue, just wanted to comment however. I find it very odd that ALL Note II's don't work on every frequency. Bear with me, I'm under the impression that they are identical hardware wise, every version. So, maybe it's a simple matter of flashing a different radio.img? Not that there are any available currently, but there will be shortly. I hope (think) it will be similar to the ATT Note on Tmo. Hopefully it works out better though. We still don't know if the Tmo Note II will be HSPA+42 or not, but it will support next years Tmo LTE.
So, as of now, this is a little bit of a disappointment for Tmo customers looking for the N7100. Hope you can find a workaround for at least HSPA+21 soon :good:
ccampbell1 said:
Hi,
I just received an unlocked International Galaxy Note II in the US. Ordered from Handtec in the UK, and the phone appears to be the French model. I have observed what I think is a problem when trying to use the phone on T-Mobile USA.
I put my T-Mobile USA SIM card in the phone, and the phone thinks I am roaming. Uhhhh no. It's a T-Mobile USA SIM card on the T-Mobile USA network. It is NOT roaming. Now, it probably doesn't have any impact beyond the "R" notifier, and a "Roaming" page which shows up on TouchWiz, but it DOES make me feel very uneasy. I have to enable "Data use while roaming" to be able to use data while on my home network!! It's crazy!
To those who will point out, yes, I know that T-Mobile USA has their 3G currently on the AWS 1700/2100 band, which the Note II does not support. I am therefore using EDGE with this phone. (Yes the data speeds suck, but T-Mobile's refarming will make this problem go away in the next few months). Even though I am on EDGE, I am not "roaming" unless the Note II's definition of roaming is different from mine. I am still on the home network, regardless of whether I am on 2G or 3G.
Has anyone else seen a problem like this?
If I can't figure this out in the next day or two, I may return the Note II and just wait another month or so for the T-Mobile US version. (Probably that's what I should do anyway, but I figured the GT-N7100 would get more developer support).
Hope someone can help!
Thanks!
Edit: I forgot to add - I also have and unlocked international Note 1 GT-N7000 and an unlocked iPhone 4. Neither possess the T-Mobile USA 3G band, and neither of which show roaming when I'm using T-Mobile USA. So, either T-Mobile did some funky network work today which changed something, or there is something different (and possibly a bug) about how the Galaxy Note II determines if it's roaming.
Click to expand...
Click to collapse
That happened to me as well using my International Galaxy S3, I dug into it for about a month and trust me, it's something with the phone detecting that it can't connect to the HSPA+ bands it supports, and when it "defaults" down to EDGE it considers it "Roaming". Stop digging for answers, I was at it for weeks, this is the reason.
You wont get charged for roaming or anything though, so use EDGE until T-Mobile's refarming finally happens; I waited for 2 months and nothing, so I jumped ship and got Straight Talk. I use over 15 GB of data a month, no throttling, $45 bucks. :good:
Hope this helps, because NO ONE gave me a straight answer, Dont even bother calling T-Mobile, they're of absolutely no help. I flashed all sorts of custom ROMs, Kernels, Network Tools, Diagnostics, etc. trying to figure it out. It's just the way these Samsung phones (GT-I9300 and N7100 by the looks of it) work when their 3G/HSPA+ bands are not supported.
Cheers!
farfromovin said:
Unfortunately I cannot be of any assistance to your issue, just wanted to comment however. I find it very odd that ALL Note II's don't work on every frequency. Bear with me, I'm under the impression that they are identical hardware wise, every version. So, maybe it's a simple matter of flashing a different radio.img? Not that there are any available currently, but there will be shortly. I hope (think) it will be similar to the ATT Note on Tmo. Hopefully it works out better though. We still don't know if the Tmo Note II will be HSPA+42 or not, but it will support next years Tmo LTE.
So, as of now, this is a little bit of a disappointment for Tmo customers looking for the N7100. Hope you can find a workaround for at least HSPA+21 soon :good:
Click to expand...
Click to collapse
farfromovin,
I agree it's a complete pain why one model can't work worldwide - or even between carriers in one country, the US!! I'm not sure that all the revisions are the exact same hardware though. Certainly the different revisions will support different LTE bands from one another, different 3G bands (ie T-Mobile USA) and even different technologies (VZW, Sprint, US Cellular CDMA). Whether there is one uber radio chip that's the same in all versions, with different bits enabled here and there, I don't know. I would doubt that a chip currently exists to support all GSM, UMTS, LTE and CDMA bands in the one, but you never know.
I really cannot wait (getting super sick of it) until T-Mobile's 1900MHz refarming, and finally all UMTS/HSPA phones will work on pretty much any UMTS/HSPA network worldwide. But just as we finally get 3G harmony, LTE comes along with a zillion different bands, and we're back to where we were at the start of GSM, and the start of UMTS - all over again.
As far as getting the GT-N7100 to work on T-Mobile AWS bands - unless the radio supports that band somewhere, and can be enabled by some hacky flashing, I don't think there's much chance. I followed a thread for a while which was trying to do that for the original GT-N7000 and it ended up nowhere unfortunately.
I'd be very, very surprised if the T-Mobile US official Note II did not support DC-HSPA +42. Given how TMO pushes that, I don't think they'd sell a phone without it these days. I'm kind of surprised the GT-N7100 doesn't have it, to be honest, but I guess it's not yet that widespread, and most carriers will bypass it to go to LTE.
Cheers!
Ars-Hexis said:
That happened to me as well using my International Galaxy S3, I dug into it for about a month and trust me, it's something with the phone detecting that it can't connect to the HSPA+ bands it supports, and when it "defaults" down to EDGE it considers it "Roaming". Stop digging for answers, I was at it for weeks, this is the reason.
You wont get charged for roaming or anything though, so use EDGE until T-Mobile's refarming finally happens; I waited for 2 months and nothing, so I jumped ship and got Straight Talk. I use over 15 GB of data a month, no throttling, $45 bucks. :good:
Hope this helps, because NO ONE gave me a straight answer, Dont even bother calling T-Mobile, they're of absolutely no help. I flashed all sorts of custom ROMs, Kernels, Network Tools, Diagnostics, etc. trying to figure it out. It's just the way these Samsung phones (GT-I9300 and N7100 by the looks of it) work when their 3G/HSPA+ bands are not supported.
Cheers!
Click to expand...
Click to collapse
Hey Ars-Hexis,
Thanks so much for the reply. I googled about the same issue on the i9300 as you mentioned - and sure enough a couple of threads on androidcentral, and tmobile support - and all with pretty much a bunch of people going "what?" I think you're right, and this is either some crazy change which Samsung has made to the "S3" generation of phones, or it's an unintended bug which was introduced. I contacted Samsung support on twitter but I'm sure they'll tell me to go away since this is an international model and not sold or supported in the US.
I would love to have this properly reported to Samsung though because it is NOT correct behaviour, and I'm sure it does not meet the 3GPP standard behaviour. These phones' definition of "roaming" is frankly wrong. It's possible they know about the bug but don't care about it too much, because it only affects the minority of importers or travelers, and then only on the very few networks which use AWS band for 3G.
The phone and data works fine of course, so it's really a cosmetic annoyance. However, if I was actually outside TMO's network without knowing it (maybe camping on to some network on the Canadian border or something) then I'd never know if I was actually roaming or not. So the phone's roaming indicator, by being permanently false, is useless in the times when I'm actually roaming. Since this is not a likely scenario for me to be on the Canadian border and roaming onto an AWS-only network any time soon, I'll not worry too much about it.
Yes, I'm really sick waiting on this refarming. It's a huge undertaking of course, so I understand why. I do have a Straight Talk AT&T SIM which I got for my Galaxy Note 1, however I don't use it often for several reasons: haven't ported my number to it, am wary about data throttling or cut-off, and I find the data hit or miss on Straight Talk anyway. I heard stories about people being warned or cut off after 100MB in any day, but if you're saying 15GB and no throttling, it may be something I want to put to the test!
Thanks a lot for your reply! It's nice to know I'm not crazy!
Cheers!
ccampbell1 said:
Hey Ars-Hexis,
Thanks so much for the reply. I googled about the same issue on the i9300 as you mentioned - and sure enough a couple of threads on androidcentral, and tmobile support - and all with pretty much a bunch of people going "what?" I think you're right, and this is either some crazy change which Samsung has made to the "S3" generation of phones, or it's an unintended bug which was introduced. I contacted Samsung support on twitter but I'm sure they'll tell me to go away since this is an international model and not sold or supported in the US.
I would love to have this properly reported to Samsung though because it is NOT correct behaviour, and I'm sure it does not meet the 3GPP standard behaviour. These phones' definition of "roaming" is frankly wrong. It's possible they know about the bug but don't care about it too much, because it only affects the minority of importers or travelers, and then only on the very few networks which use AWS band for 3G.
The phone and data works fine of course, so it's really a cosmetic annoyance. However, if I was actually outside TMO's network without knowing it (maybe camping on to some network on the Canadian border or something) then I'd never know if I was actually roaming or not. So the phone's roaming indicator, by being permanently false, is useless in the times when I'm actually roaming. Since this is not a likely scenario for me to be on the Canadian border and roaming onto an AWS-only network any time soon, I'll not worry too much about it.
Yes, I'm really sick waiting on this refarming. It's a huge undertaking of course, so I understand why. I do have a Straight Talk AT&T SIM which I got for my Galaxy Note 1, however I don't use it often for several reasons: haven't ported my number to it, am wary about data throttling or cut-off, and I find the data hit or miss on Straight Talk anyway. I heard stories about people being warned or cut off after 100MB in any day, but if you're saying 15GB and no throttling, it may be something I want to put to the test!
Thanks a lot for your reply! It's nice to know I'm not crazy!
Cheers!
Click to expand...
Click to collapse
Hey there! Sorry I hadn't answered in such a long time. We'll actually I've found that the S3 (sold it) and the Note 2 (own it) some how cannot be tracked for data usage correctly by straight talk. It's quite interesting... I ported my number over from T-Mobile, so if you have an S3 with a T-mobile prepaid sim... I think you have nothing to lose! I'm in Dallas and regularly get around 3-4Mbits/S during high usage hours and 6-7Mbits/S after 7 pm when network usage goes down.
There have been 2 occasions over the past 2 months where I'm throttled for like an hour and suddenly it gets uncapped on its own (?!?!?) lol. Last month I used about 25 GB... It's insane. Btw, if you if get throttled for real (happened to me once), you can just call them and say your "Internets is slow" (act technologically challenged) and they'll reset it.
Ah 1 last thing: I got the at&T ST sim card when I switched.
Cheers!
Sent from my GT-N7100 using XDA Premium HD app
I just got my International Note 2 today, and I am using it on the T-Mobile network also. I am seeing that I am roaming but my data is off and I am just using wifi. I have turned off my phone and back on again and its still showing. But after reading this whole thread I am getting that is a bug or something along those lines is that correct? Thanks.
I really need to know
Sent from my Nexus 4 using Tapatalk 2
roaming
I am on prepaid tmobile and I have Roaming sign only in areas where I used to loose signal with my old phone . Basically when I go in Garage underground my signal starts getting weaker and weaker and then roaming kiks in and signal is up all the way . T-mobile does not charges for local roaming . If you use USA tmobile and you are in usa you are fine . My texts and voice are still the same rate for me . When I had Chinese rom it was showing all the time , now I flashed German t-mobile and R shows only sometime , but it does not bother me .
Hope this helps .
I too have a Note II (GT-N7100) I purchased in Thailand in December. I use it on the T-Mobile network and have the same issues with the "R" symbol. I am located in Tampa Bay area, Florida.
T-Mobile was indicating to me in January that this was an issue in weaker signal areas for their data network as they prepare to refarm it. Don't know if this explanation is entirely accurate, but I find in my local area that the R symbol goes away in certain areas and it behaves "normally". This includes the area where my T-Mobile office is located. It seems to be somewhat of a patchwork network, and for some reasons certain areas cause it to go into the Roaming mode.
I was just on a trip with stops in Los Amgeles, San Francisco, and Philadelphia and noted the same behavior in some of those cities: Getting normal signal indications in some places, and Roaming in others.
Hello, Just changed from Tmobile to ATT. I already unlocked it, and am running it on 4G. Sad part is, download is only like 1-3 Mbps it seems. While my Iphone 5 can get close to 7 Mbps (Now this is just 4G band, NOT LTE)
So I am wondering if there are some tweaks I need to adjust in the build.prop or anything else. Atm I just use the stock rom thats rooted. (Since it seems nice enough for JB and honestly, I havent figured out which custom rom beats the stock rom 100% without losing any features.
Also noticed I cant install the ATT Visual voicemail as it claims device isnt compatible. (Which that I am sure I can use a build.prop edit for the model. Question is, which model and items do I need to adjust and to what value?)
Anyways, if anyone has some good advice about using the tmobile S3 on ATT and getting it tweaked to be the best it can be, or a rom that is perfect for switching between ATT and Tmobile (should I use my prepay tmo sim in it again) and provide high data speed. Would be great.
Oh also.. just so I know. Can I use the ROMs posted in this ATT section of XDA for the t999 tmo s3 or do I need to still only use roms from the tmo s3 section of xda? Thanks. =)
Probably you are better off posting this in TMo section too... cos there would be higher chances for finding someone who already tried putting the AT&T version of ROM on his TMo phone.
Posted there too, not much luck on responses yet. So figured maybe this side knows more. I dont even know if one can use the ATT Xda rom side for the tmo s3 for example. Was there any hardware differences (aside from the radio since I know tmos doesnt have LTE) Also what is the model for ATT s3 for the build.prop?
Anyone least know if the roms in ATT section would even work on the Tmobile model? Kinda thinking I should switch out and have all the setups and apps for ATT.
Hi,
I have a T-Mobile S4 and have seen several threads about installing a TMo ROM and kernel on an AT&T S4, but I just switched to AT&T and wondered about installing a stock 4.4.4 At&t ROM and kernel on my TMo S4. It's unlocked and I run Pacman on it now but for some reason, it very rarely gets an LTE signal and seems to choose "H" when my wife's at&t phone uses LTE. I've tried different combinations of Preferred Network Modes and nothing helps. I was hoping a stock at&t would run better. Is this possible or can anyone lead me in the right direction?
Thanks
First thing to do is check the APN. Make sure the settings match ATT stock, as shown here in the APN section.
Running an ATT ROM wouldn't actually give you better reception. However, it's well known that TouchWiz ROMS report higher signal strength than AOSP ROMs or iPhone for that matter. It's not that Touchwiz actually gets better reception, they just report it in terms of bars biased more highly. I did a study on this by reading signal strength (in db) on my M919 phone running an AOSP based ROM, next to an actual ATT I337, and an iPhone 5S. Actually the M919 got the best reception (in terms of db, by a small margin) but the reported bars were lower than the other two. Here is a link.
It's possible that the way your ROM/Kernel are set up, the threshold to switch to H+ instead is different than in TouchWiz. You could try running the M919 stock firmware for a while, and see how it does. You could also just try updating to the latest LTE modem (which requires bringing your bootloader up to current as well).
Good luck and let us know what you find.
Marc
Thanks for the awesome help. That's exactly what I wanted to know. I ended up deleting all of the extra APNs except for the necessary ATT phone one and its been working great. For some reason it would randomly switch to a worse APN when it had choices.
Glad I ran across this thread. I am running Net10 and deleting all extra apns changed my phone from unusable indoors, to always having 2 or 3 bars . I can't believe it took me this long to try it. Thanks for the help.
Hi all,
I checked the forums and while I did find a link to the radios available, I'm a bit cautious as I know the incorrect one could potentially brick my phone.
I have a fairly new international M8 unlocked(S-Off). I purchased Metro(which I know piggy backs off of Tmo) prepaid plan and all works great EXCEPT the data speeds are very sluggish..like 2-3mb in an area that should be giving me much more based on friends who have Tmo as well as their coverage maps. If it was CLOSE I wouldnt mind- but its not.
My question is - what do I need to do to ensure that I get the absolute right radio to flash? I have a custom rom but I know its got nothing to do w that- my understanding is its the phone and the service provider... but, I saw a few different tmobile radios (I'm assuming since I'm using Metro that should be acceptable?) I just dont know which to choose.
I am out of ideas, otherwise, for the data speeds, as I've tried both Metros and Tmobiles APN settings, and neither made a difference.
Thoughts?
For starters, you're in the wrong forum. This is the m7 forum c:
Wonderful. Any way to move it? I dont know how that happened. Sorry guys.
A moderator will move it in some time. Don't worry, it happens to the best of us.
Indeed, moved...
Thanks much. Any help would be appreciated. Also if there are any other suggestions besides updating the radio I'd be happy to try them but I don't see much else outside of APN settings which I've tried w no success.
Anyone?