Hi, I recently bought a used i9103 on eBay that was imported from an overseas country (Still not sure which country), seeing as it was never sold in the US. After using it a few weeks, I notice that the signal jumps radically, even when the phone is stationary.
So my question is, which baseband/modem/radio would be best? (Specifically for T-Mobile USA)
As a note, I am in a major metro zone and other phones in this same area get a strong and consistent signal.
The baseband is currently XXLQ3.
Thanks.
You can try DDLP3 baseband from Indian ICS XWLP8 rom. That's the latest and that's why it should be the best one.
I flashed the modem alone from XWLP8. I'll report back in a few days if there's any difference. I guess I should also ask if there's any difference in hardware in the models shipped to different regions? Or is there only one model, just with different software?
There is only one model as far as we know, at least there weren't any others reported.
Just an update, flashing the Indian radio didn't seem to help at all. Signal still jumps up and down wildly. Turning on Data Roaming did not help either.
Hello,
I bought my Nexus 5 on the 11th of December 2013 and it had been working flawlessly ever since. Since last week, I started noticing the occasional signal drop and I'd be out of cell reception but would usually be back up within no time. However, yesterday, out of the blue I'm travelling on the highway and my signal strength disappears never to come back again. I've tried the following:
- Restore old backup (including EFS)
- Went back to stock from PA
- Upgraded to the latest radio
- Took back cover off to see if anything was wrong but found nothing.
- Tried another SIM card
Nothing worked. My SIM card works fine in another phone. Everything else such as WiFi and Bluetooth works flawlessly but I just don't get any reception.
This is very disappointing and I have my fingers crossed hoping someone can help me with this since I didn't plan on getting a new device for at least another year especially after paying $520 USD for my phone here in my country.
Thank you for looking.
im having a similar problem with the radio after the last few otas. im getting a lot of dropped calls on 3g aws...
im going to try to revert to an old radio as i don't think this is a hardware failing issue..
Sent from my Nexus 7 using Tapatalk
Flash stock firmware with fast boot. If its the same, its a carrier issue....call them to see. Or its hardware failure.
just wanted to post my fix for this issue - very disappointed with Google that i had to do this...my provider is mobilicity canada (3g aws band fyi)
flash krt01b radio from this thread...
http://forum.xda-developers.com/showthread.php?t=2514095
this is *not* a carrier or hardware issue (at least in my case)
seems others are having same issue
https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=70878
Then it is a carrier issue....cause on Telus in Canada....never had an issue with any radio version. ?
telus would have a stronger overall signal but uses AWS band for lte which is different than mobilicitiy 3g aws...
I'm not disagreeing.... Just saying its the carrier....not Google.
See my point?
KJ said:
I'm not disagreeing.... Just saying its the carrier....not Google.
See my point?
Click to expand...
Click to collapse
are you saying mobilicitiy is purposely weakening their cell signal cause they are almost bankrupt ?
i still blame google i had no issues with the radio before they borked it...
nolook said:
are you saying mobilicitiy is purposely weakening their cell signal cause they are almost bankrupt ?
i still blame google i had no issues with the radio before they borked it...
Click to expand...
Click to collapse
Just saying that unless many have the issue with the phone or radio, then its an issue.....if not, it isnt .
So in this case, it leaves hardware or carrier....assuming a stock flash didn't help.
If flashing another radio helps the OP...awesome!! But the new radio does work fine for the mass majority.
Hope it does work for him tho!
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
RoyJ said:
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
Click to expand...
Click to collapse
Sorry forget to mention I knew that was normal for the drop to H+, but yes the signal drop is not. Well it started out of the blue. IS there a thread on here with what should be the correct APN settings? Also my old nexus 5 started to do this before I returned it under warranty for refurbished, then I had a moto G lte for a month worked fine, got a refurbished (due to warranty) and started again.
Here is a graph of my network coverage to show that the signal just drops.
Sent from my Nexus 7 using XDA Free mobile app
same problem
jgr208 said:
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Click to expand...
Click to collapse
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
raptir said:
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Click to expand...
Click to collapse
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
cell radio fix
jgr208 said:
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
Click to expand...
Click to collapse
I found it here (just take away the spaces after .com and after 02/): ianmarmour.com /2014/02/02/ google-nexus-5-fixing-modemcellular-issues-on-34g-networks
It's an older post from February, but seems to have the best details and fixes. If you simply search nexus 5 cellular radio issues or nexus 5 4.4.4 call drops, you should find a lot of these recalls from lots of N5 users. I'm tempted to try it, but don't really feel like sorting all my files in case i brick my device. I'm also not sure if ota update will work if i tinker with cell radios. Otherwise that's the page containing all the details you'd need including links and step by step guides. And hey if it works for you, let me know, maybe I'll try it out if it goes well for you.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
Exactly, i know that's totally possible, but i wouldn't want a smartphone that has no lte and/or hspa+ service at this point in time. This seems to happen wherever lte isn't as strong or available but hspa+ is. I think the modem responsible for switching between lte and hspa+ causes calls to drop. I took note of it a couple hours ago when i attempted to make a few phone calls resulting in instant call drops. Seems to do it while switching from lte to hspa+ network. I just wish Google would stop burying their heads from the outside world like an ostrich, and get in top of this. I mean this is their flagship device until N6 goes on sale. They should seriously fix this issue or at least stop denying that they've never heard of any complaints with their N4 and N5 customers. I love this device, but a simple fix like this not being addressed by Google is not very professional, especially because it's primary function is to call people. I'm really tempted to flash those radios, but really want to see if Google addresses this issue with an official ota lollipop update.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Factor resetting it won't help, I've tried it already.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
simms22 said:
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
Click to expand...
Click to collapse
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
simms22 said:
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
Click to expand...
Click to collapse
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
anactoraaron said:
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
Click to expand...
Click to collapse
Def wasn't gonna try hardware and only software and great to hear! Did you try out lollipop yet?
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
simms22 said:
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
Click to expand...
Click to collapse
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
well, try the lollipop preview, it was working for the other guy, see if itll work for you. if it does, great.
Weird issue I'm having on a G920i. In Settings -> About Device -> Status, the signal strength is being reported incorrectly. When I first boot the device, it will show accurately and will vary from -90 dBm to -100 dBm when I am at my house, which is consistent with every device I've ever owned. However, after 30-45 seconds, it will start reporting at "-113 dBm 0 asu" and it will simply stay there and will never change, even as I move about. The number of bars in the signal strength icon on the status bar will even change, but in the Status menu, signal strength simply stays at "-113 dBm 0 asu" permanently. Connectivity seems to be fine--I have no problems making calls, browsing the web, etc. The signal strength in the Status menu simply seems to revert to and stick at 113 dBm 0 asu with no explanation or other impact on the phone.
For what it's worth, I've tried both the New Zealand and Singapore AOD1 firmwares from Sammobile.com. Same problem on both. I'm on AT&T in the U.S.
Anybody else seeing anything like this?
Yes it seems both the g920i and g920f all have this problem. Every single device. Please get in contact with Samsung about it, the more people that complain the more likely it will be fixed.
@mupet0000 & @phositadc I've seen you guys in a few forums talking about the Galaxy S6 SM-G920I signal issues... Mine is the same! Swapped 2 phones already and they have awful lte reception... I was hoping a different modem/baseband would help but it looks like it doesn't....plus a few soft reboots as well what's going on? Have you guys experienced any reboots? Can this be fixed with a software update?
OK checked mine and its yes your right. -113 in status however if you type *#0011# in your dialer you'll see the better reception reported. Interestingly this did not happen when I was on the Cricket towers(At&t). I just switched to T-Mobile and I now have the -113 status. My speeds are great but I can't side-by-side compare the radios to anything to know if there is a real problem.
Sent from my SM-G920I using XDA Free mobile app
Kjc99 said:
@mupet0000 & @phositadc I've seen you guys in a few forums talking about the Galaxy S6 SM-G920I signal issues... Mine is the same! Swapped 2 phones already and they have awful lte reception... I was hoping a different modem/baseband would help but it looks like it doesn't....plus a few soft reboots as well what's going on? Have you guys experienced any reboots? Can this be fixed with a software update?
Click to expand...
Click to collapse
No reboots here. I flashed the aod3 modem last night and things seem a little better on AT&T. On the aod1 modem, I was not getting LTE in a bunch of places that I've always had LTE before. I know the g920i has frequency support for AT&T LTE bands, and I do get LTE, but I must say so far the experience has not been as good as other LTE phones I've had. Not sure if that's the modem firmware to blame or the hardware itself. Probably firmware.
Sent from my SM-G920I
Hey all, I'm in the UK and I have the SGS6 edge on the 3 network here. I use my phone for tethering at all times as I do not have wifi in the house. with my SGS5 before this I could easily run my PC , Tablet my son mobi and his gaming PC all at the same time with no issue. The S5 would run a full signal and load very quickly HD content.
My brand new S6 is disapointing singnal wise from straight out the box. I noticed my signal level fluctuating up and down but very rare dose it show a full signal level. and as for teathering I am finding it very hard to live with.
I will be suprised if Samsung sort this out with firmware. I just had a 150 MB firmware update yesterday and my signal level is the same.
I remember my Nokia N96 having this same fault, and although it was all over the internet back then, Nokia did nothing in all the firmware updates I had. I was going to sell my pristine 7 month old S5..... but I think I will hang on to it for now.
Hey guys, I am on the latest OTA released by Samsung (AOE3 built May 7th) and the problem is still not resolved. LTE signal still awful and LTE signal strength still -113. So far so bad. I have contacted Samsung again, and tomorrow I have a phone call with their support where they will remotely access my phone so I can show them the problem. I will show them and see how it goes, and I'll report back here.
I will make it clear to them that the signal strength is worse than my 2 year old S4, and I will demonstrate the incorrect signal strength value to the support agent. If they tell me it's a non issue or they make some silly excuse instead of investigating, I will simply sell the S6 and get another phone.
This is a huge issue and I'm disappointed that there aren't many people noticing this or reporting it to Samsung. The more popular the S6 gets, the more people will notice that their old phone holds a better signal.
Loz1 said:
Hey all, I'm in the UK and I have the SGS6 edge on the 3 network here. I use my phone for tethering at all times as I do not have wifi in the house. with my SGS5 before this I could easily run my PC , Tablet my son mobi and his gaming PC all at the same time with no issue. The S5 would run a full signal and load very quickly HD content.
My brand new S6 is disapointing singnal wise from straight out the box. I noticed my signal level fluctuating up and down but very rare dose it show a full signal level. and as for teathering I am finding it very hard to live with.
I will be suprised if Samsung sort this out with firmware. I just had a 150 MB firmware update yesterday and my signal level is the same.
I remember my Nokia N96 having this same fault, and although it was all over the internet back then, Nokia did nothing in all the firmware updates I had. I was going to sell my pristine 7 month old S5..... but I think I will hang on to it for now.
Click to expand...
Click to collapse
I think it is a widespread issue... I always have 1 bar lte and under my signal status it say - 113dbm which is zero service... It never moves... I'm gonna try custom rom and see if that help but it obviously a antenna/modem baseband issue... Also someone mentioned it could be because the Galaxy S5 uses Cat 4 lte and the S6 uses Cat 6.....its very disappointing! Hopefully it gets fixed or I'll return to the S5...i really want to like this phone..... But Samsung is making it hard to
I don`t think there is anything wrong with the signal. even if I only have 1 bar the phone is perfect during calls and my LTE/4G download speed is even over the provided speed my carrier provides, I think it`s just a bug that it`s showing less signal then what it actualy has.
johanbiff said:
I don`t think there is anything wrong with the signal. even if I only have 1 bar the phone is perfect during calls and my LTE/4G download speed is even over the provided speed my carrier provides, I think it`s just a bug that it`s showing less signal then what it actualy has.
Click to expand...
Click to collapse
This is true. It's simply a bug that shows the wrong signal strength - mine shows -113 but I'll have 3 bars so that makes no sense. However, if you ARE getting a bad signal, that is a different issue altogether.
(btw I started a thread about this already several weeks back)
Spoke to Samsung on the phone, they didn't need to remote access my phone to see the issue. They had an S6 in their office and they told me they saw the signal at -113dBm just like mine. They say they have passed this onto the relevant team and hopefully it will be fixed in an OTA and I should stick to the United Kingdom BTU firmware (the correct firmware for my region).
We will see if this gets resolved. They definitely know about the problem now and have seen it with their own eyes, so I'm hopeful.
Japultra said:
This is true. It's simply a bug that shows the wrong signal strength - mine shows -113 but I'll have 3 bars so that makes no sense. However, if you ARE getting a bad signal, that is a different issue altogether.
(btw I started a thread about this already several weeks back)
Click to expand...
Click to collapse
You have a link to you'd thread?
Kjc99 said:
You have a link to you'd thread?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s6/help/lte-signal-indicator-issues-t3083001
Japultra said:
http://forum.xda-developers.com/galaxy-s6/help/lte-signal-indicator-issues-t3083001
Click to expand...
Click to collapse
Ok.. Thanks... I already read through that thread too... Been trying to figure out if it was just me or alot of people..... Seems like the 920f is getting more updates that us.... 920I......The latest is AOD3 right? Today I'm gonna flash a custom rom for 920f and see if there is any change....
*edit* just checked Samsung live update... AOE3 was just released for 920I for TTT I guess is a country called Trinidad and Tobago... But that is the firmware I've been using.... Hopefully this will help... Let Ya guys know
*edit #2*...ok guys just updated to AOE3.... Bars still show low but the signal status is working and it's showing that I have a better signal than with *#0011*... The - dbm and asu is now extremely close to my S5... So in conclusion the signal is strong it just doesn't show it in the bars like previous Galaxy's