Odd problem with only some ROM's and Radio. - Galaxy S 5 Q&A, Help & Troubleshooting

I am currently own and use a T-Mobile S5, unlocked on the AT&T network.
I have installed several roms and I am having issues with the radio. Here is what I am getting, on most cases in some areas my phone is stuck on H+ and not LTE, but when I start moving around, LTE shows up (observation), other ROMS will show LTE almost all the time. The ROMS that show H+ a lot of the times, also seems to loose signal a lot. just go NO SERVICE for some reason, and then come back 30-60 seconds later?
I thought the modem was separate from the ROM, am I incorrect? is there a way to extract the good modem from the ROM, OR better yet, is there a depo for Modems that will work for this T-Mo phone?
so far the only ROM that seems to work correctly is Bliss pop? Any idea?
Thank you

Related

3G signal problems with certain CIDs

Hi, I have a problem that I suspect is an isolated situation, nevertheless, it has been bugging me for over a month now. Hopefully the community will have some insight.
I will try to report the problem in it's entirety:
I do have a shortcut on my desktop to Phone Info (*#*#4636#*#*). From here, the thing I note of interest is the CID, which I guess is the tower ID that my phone is currently connected to. Also of note here are the ASUs, which I'm not quite sure what they are, but they seem to correlate with the number of bars being reported (ie more asu = more bars).
I also use Hello IM (AIM app from the market) heavily, and I have "Show notification icon" enabled, so it works fairly well as a visual indicator of connectivity, or lack thereof.
Ever since I upgraded from Super D to an Eclair rom, I've had problems with 3G handoffs on Tmo. Basically, whenever my phone switches from Edge to 3G, or one 3G tower to another 3G tower (different CID in Phone Info), the connection times out. I see the infamous "up arrow but no down arrow" activity on the 3G icon in the notification bar. This happened just about everywhere I went.
About a month ago, I decided to upgrade the phone radio, from 2.22.19.26I to 2.22.23.02. For one reason or another, this completely solved my problem. I had no problems with handoffs, 3G just started working again.
A couple weeks ago, I downloaded CM6 and tried out Froyo. The first thing I notice is the weak signal on my radio. Before flashing the rom, I did a nandroid backup, and I know I had 3 bars of 3G signal where I set the phone down. After the flash, my phone had no 3G signal, and for some reason refuses to switch to edge; so my signal indicator is sitting there with an X over it. After some time, it finally does pick up a 3G signal--this is where it begins to get weird...
My 3G works right now, for the most part. There seems to be 2 very specific locations where it does not work. As mentioned earlier, I am able to check CID's through the Phone Info menu. I notice 2 CIDs where my 3G connection times out. By time out, I mean an apparent loss of data (ping doesn't work in Phone Info). This happens every time I am connected to these 2 towers. As soon as the phone switches off to another tower, data works fine again. The strange part is, even though I am not getting data, the asu and signal bars continue to move up and down as if I have a normal signal. The phone also makes no effort to switch back to Edge, even though 3G data is completely stalled (Hello IM shows as disconnected, ping fails).
This started happening since the CM6 update, and have persisted since then. Even after I did a nandroid restore back to my previous rom (Super E 1.02), the radio problem remains. Before CM6 and after I updated my radio, I had no problem connecting to these same towers.
In a nutshell:
3G does not work when I am connected to 2 specific towers since CM6 update
Phone makes no effort to switch to other 3G towers or Edge when connected to these 2 towers
When connected to these towers, signal strength continues to go up and down as normal; usually hovers at a consistent 2 to 3 bars with the stock signal indicator (4 bars max).
Currently I have tried flashing all the Eclair roms available, as well as my old Super D rom (still using 2.22.23.02 radio). Problem remains.
Does anyone have any idea what's going on?

[Q] Roaming when on Custom rom

When I'm on stock (d80020k) 4.4.2 I get nearly excellent (4-5 bars) 4g data performance. However, when I try any custom rom, my bars always show "R" which I believe is roaming by them. I'm currently on Mahdi rom with the d800 patch. When I go back to stock using the twrp backup, everything works fine again. Can anyone help me as I'd really like to stay on a custom rom. My Sim card is for a T-Mobile mvno called lycamobile. My phone is unlocked so it should be working. I have a speculation that this might be because of my service provider.
No one wants to shed some light on this? This didn't work on jellybean and Kitkat, both being different devices on the same provider.
Update: My provider says that on some devices, it shows that it's roaming on it's own network, and for that reason, roaming is the same price as regular. However, I don't yet understand why it doesn't show roaming and works fine on stock, yet always, always roams on aosp/cm. However, I'm terribly confused why It roams on aosp/cm. I tried changing network operator to Lycamobile, still roaming. I found out that the roaming "R" is completely cosmetic, as I can make and receive calls, make and receive texts, and use data. Is there any mods to replace the R with like 4g lte or something? It really bugs me when I can't see the speed of data when I'm using it.

All of a sudden I've lost 4G reception! HELP!!

Hi All,
First time poster with an unusual problem. I live in Australia and have a Samsung Galaxy S5 SM-G900F which is the European model. Up and till recently I was getting Telstra 4G reception. Now all of a sudden I'm only getting constant 3G reception. I have confirmed that there are no 4G network repair/maintenance/upgrade issues in my area. It was only in the last week that I noticed the constant 3G reception so I can't really pinpoint a specific incident or exact date as to when it actually started happening. Here is what I have tried thus far:
Phone restarts, changing network settings and switching to flight mode.
I've confirmed that the phone network is set to LTE/WCDMA/GSM (auto connect).
I have done numerous hard resets, cache wipes, Dalvik cache wipes, drive wipes, etc.
I have rooted and unrooted the phone numerous times.
I have tried several different stock and custom ROMS.
I have tried 4G SIM cards from other phones.
Tried numerous network switching apps.
NOTHING WORKS!
I always love to tinker with my phone so I'm always looking for ways to improve the phone's performance. It may be that an app (battery improvement/tweaking type apps) I installed somehow changed the network settings but I would have thought a million hard resets would have sorted that all out but apparently not. At the moment I'm running a rooted stock Android 5.1 ROM. I've tried stock Android 4 and 6 as well with no joy.
Here is the unusual thing. When I put in another 4G SIM card into my phone the network still remains on 3G but as soon as I put my SIM card back in 4G magically reappears. It's bizarre. At least I know my phone can still get 4G. You would think that would solve the problem but it doesn't. When I am in an area where the 4G signal is weak the stronger 3G signal kicks in as it is supposed to. When I get back into an area with strong 4G reception the phone remains stuck on 3G and no matter what I do it won't go back to 4G unless I go through the convoluted process described above.
I am all out of ideas. I think I have tried everything possible. I've trawled the web and I appear to be the only person in the world with this problem. I don't know if it is a software or hardware problem with my phone. My SIM card works in other 4G phones so I don't think it is part of the problem. At the end of the day it's not a big deal as 3G is fine but I'm just one of these people that has to fix a problem. Worst case scenario I'll probably upgrade the phone in the next 6 months.
Any suggestions or tips other than what I have listed above would be greatly appreciated. Thanks in advance.
Bulky

Moto X Pure (XT1575) drops connections and data

Okay, so I really like my Moto X Pure. I used it in Florida with no problem with network or data or text or anything. The instant I left Florida my data dropped (couldn't load anything anywhere), I would get 1 text every 5 minutes, and phone calls couldn't be completed.
If I run speed test it'll take about a minute to find a server, my ping will be 500+, and my speed might get up to 0.9MBps for a split second, then drop to zero for a few seconds, then a spike of 0.9 again, etc.
I can watch the network bars go from full, to nothing, to full, to nothing, to 1 bar, switching from LTE, to H+, to 3G, to 2G, and all back over again. On every ROM, with every carrier, rooted, unrooted, stock, modified, updated radio, OTA radio, everything.
I've tried EVERYTHING
Revert back to completely stock (was running CM13.1)
Tried other ROMs
updated radio/modem
downgraded to 5.1
SWITCHED CARRIERS from Verizon to AT&T, tried T-Mobile sims....
EVERYTHING gives me the same issue! If I plop the sim cars into my nexus 6 or my G3 then I get connectivity and speeds no problem.
Unfortunately since I have unlocked the bootloader, I don't believe I can get warranty on this phone.....
But why would it work PERFECT in Florida, but nowhere else in the entire United States? I mean, NOWHERE. I did an across the country road trip.
Yep same here
Sent from my XT1575 using XDA-Developers mobile app
Huhuhu I guess it's time to sell.
I got the G5 and didn't care for it. I think I'm actually just going to get a G4.
I'm in the same boat. It seems my LTE speeds are fairly good here in Canada on Rogers. Sometimes I get decent 3G speeds but mostly it just fails entirely. Completely stock. No problems with SIM on other devices. Phone is 2 months old but it's been doing this since the beginning.

Issue with Oreo radios for US?

Installed the Beta Oreo (stock and AOSP) on my Axon 7. After erasing and flashing with the U variant radios (my device is US) the phone initially receives full cell and data service. However, when entering a highly intermittent area like tunneled Public Transit, for some reason the radios stop working....and never come back. I simply would not receive signal any longer. Searching for data networks manually would find towers, but connecting to them does not restore service. Reflashing the bootloader and U radios does not regain signal. I would need to reinstall the entire ROM including bootloader and radio. Again, I would receive service fine until I reach an area with very low levels of service. This happened on the stock B12 ROM and the AOSP ROM. It's something to do with this Beta but I'm not sure what exactly. I'm on T-Mobile in the US.
Anyone else had the same issue?
I'm on AT&T and never had this issue.
Did you try to toggle airplane mode?
Did you check the APN settings? Maybe they changed?
Did you try setting the network mode (GSM/CDMA/LTE etc...)?
mozillameister said:
Installed the Beta Oreo (stock and AOSP) on my Axon 7. After erasing and flashing with the U variant radios (my device is US) the phone initially receives full cell and data service. However, when entering a highly intermittent area like tunneled Public Transit, for some reason the radios stop working....and never come back. I simply would not receive signal any longer. Searching for data networks manually would find towers, but connecting to them does not restore service. Reflashing the bootloader and U radios does not regain signal. I would need to reinstall the entire ROM including bootloader and radio. Again, I would receive service fine until I reach an area with very low levels of service. This happened on the stock B12 ROM and the AOSP ROM. It's something to do with this Beta but I'm not sure what exactly. I'm on T-Mobile in the US.
Anyone else had the same issue?
Click to expand...
Click to collapse
Yes, I saw this with B12 on my A2017U on TMO in low LTE signal areas. Trying to fix this LTE performance issue, I ended up getting stuck in DFU mode.
3 weeks ago, I actually had to send my A2017U back to ZTE for warranty replacement. New unit does not exhibit this issue. I think I may have had a bad radio in my phone.

Categories

Resources