Related
Today for at least 2 hours from my living room, my E4GT had no service but didn't display the dreaded LOS signal. I found out about this by receiving an email telling me "your phone is going directly to voicemail for the last 2 hours, what gives?" Furious, I called this person immediately which went through as it normally should. While on the call I received 3 text messages, all delayed at least an hour.
I called sprint and they said there was no network outage, and that there is a known issue with LOS for this phone which has been discussed in this forum quite a bit. That said, I asked her what to do when your phone shows no LOS issue at all, and isn't receiving calls or texts. She had no solution other than "wait for samsung to release the fix."
Curious about my cell signal with E4GT, I used an app called "Network Signal Info" to log my phone's signal for 7 minutes just sitting on my coffee table. Astoundingly, my signal strength bounced around all the way from -106db (0 bars) to 5 bars (-76db). At one point, it even dropped from 5 bars to 0 bars. WTF!!!
I parsed the logs and created a crude graph which I am attaching. It covers 7 minutes of signal strength, logged every 10 seconds.
Has anyone else seen this happen? On my evo4g I never witnessed such a thing. I am wondering if my phone is effectively not receiving incoming calls every time it goes to 0 bars or -106db. Maybe someone else or multiple others can log what you see too? I hope this isn't normal for samsung devices....
A kmsg and logcat to go with this data would be even more enlightening.
I've had this happen as often as I've had the LOS circle show up. It will actually show full bars but no 3g signal, and when I try to send a text it just fails. It takes a reboot just as if the LOS circle was showing. I believe it's the same problem.
I've contacted Samsung and they blame it on Sprint, going so far as to say "you're carrier is known for bad coverage." It seems Sprint blames it on Samsung. Just what we need for a fast fix..... more BS from Sprint and Samsung.
k0nane said:
A kmsg and logcat to go with this data would be even more enlightening.
Click to expand...
Click to collapse
Googling this issue apparently samsung phones have a higher variability in cell signal than htc and motorola phones. However, dropping to -106db seems quite ridiculous when moments prior it was -76db.
I mostly posted to see if anyone else is experiencing this issue. Anyone, anyone?
jirafabo said:
I've had this happen as often as I've had the LOS circle show up. It will actually show full bars but no 3g signal, and when I try to send a text it just fails. It takes a reboot just as if the LOS circle was showing. I believe it's the same problem.
I've contacted Samsung and they blame it on Sprint, going so far as to say "you're carrier is known for bad coverage." It seems Sprint blames it on Samsung. Just what we need for a fast fix..... more BS from Sprint and Samsung.
Click to expand...
Click to collapse
See the thing is though, I didn't reboot or do anything. I just placed the call and the call went through just fine. I even had my gf call me 2 mins later and I received the call.
Its almost as if the cell signal is going to sleep and isn't being woken up when needed.
LxMxFxD said:
Curious about my cell signal with E4GT, I used an app called "Network Signal Info" to log my phone's signal for 7 minutes just sitting on my coffee table. Astoundingly, my signal strength bounced around all the way from -106db (0 bars) to 5 bars (-76db). At one point, it even dropped from 5 bars to 0 bars. WTF!!!
Click to expand...
Click to collapse
This happens to me all the time on my ET4G and two Nexus S 4g's I have. Sometimes they'll drop to -106 dBm and jump up to -76 dBm. It seems...weird. Sometimes they'll switch to roaming and jump up to -76 dBm too. Bars go from 0 to 5 seemingly randomly.
strung said:
This happens to me all the time on my ET4G and two Nexus S 4g's I have. Sometimes they'll drop to -106 dBm and jump up to -76 dBm. It seems...weird. Sometimes they'll switch to roaming and jump up to -76 dBm too. Bars go from 0 to 5 seemingly randomly.
Click to expand...
Click to collapse
Have you ever experienced what I posted about calls going straight to voicemail, possibly because your phone is at -106db when call is placed?
LxMxFxD said:
Have you ever experienced what I posted about calls going straight to voicemail, possibly because your phone is at -106db when call is placed?
Click to expand...
Click to collapse
Not that I'm aware of. I once had a call disconnect when I was on my Nexus S 4g and signal went to -110dB (usually it doesn't go that low...only -106). But that person was on AT&T and I get dropped calls with that person a lot, and I never had a dropped call with anybody else with that phone.
The only time ET4G has lost connection for me is twice randomly, and it showed the circle with the line through it in the signal bar.
I'm in Minnesota BTW.
EDIT: Just saw my nexus s go to -65dBm and then 1 second later -96dBm.
Happens all the time to me..and it happened all the time with my Evo 3D :/
Yeah. I've had the Los circle, couldn't make an outgoing call, then had a call come in. Who knows. They need to fix this crap.
Sent from my SPH-D710 using xda premium
Happens to me too. All we can do is wait for an official fix, it's not ROM/root/kernel related.
Transmission sent from a Galaxy
S II on XDA Premium.
Pheno.menon said:
Happens to me too. All we can do is wait for an official fix, it's not ROM/root/kernel related.
Transmission sent from a Galaxy
S II on XDA Premium.
Click to expand...
Click to collapse
Real question is: how long are we willing to wait?
Real problem is....many of us are already past the 14 day return.
It was much nicer when it was 30 days.
jfenton57 said:
Real problem is....many of us are already past the 14 day return.
It was much nicer when it was 30 days.
Click to expand...
Click to collapse
Just got mine last week. Had no idea this was an issue. Had it happen to me yesterday twice. Initially thought it was due to the ROM i just loaded. Now I find out that it isn't it at all. Now looking at the 3D or Photon. The lack of signal no matter the frequency will drive me insane. That is why I left T-Mo to begin with.
bradspace said:
Just got mine last week. Had no idea this was an issue. Had it happen to me yesterday twice. Initially thought it was due to the ROM i just loaded. Now I find out that it isn't it at all. Now looking at the 3D or Photon. The lack of signal no matter the frequency will drive me insane. That is why I left T-Mo to begin with.
Click to expand...
Click to collapse
No doubt. Im late to this party so i have till the 12th to return it. If this isnt fixed by then, its going back.
Sent from my SPH-D710 using XDA App
Pheno.menon said:
Happens to me too. All we can do is wait for an official fix, it's not ROM/root/kernel related.
Transmission sent from a Galaxy
S II on XDA Premium.
Click to expand...
Click to collapse
I know that I'm going to get flamed for this bit I beg to differ. I have had my e4gt since launch day without so much as a problem. I rooted it on 10-2 and had the LOS problem within 30 minutes of rooting my phone. I have also had the issue discussed in this thread.
Sent from my SPH-D710 using xda premium
Based on reading a lot of posts, IMO the bug is in the stock Samsung software but is triggered under a smaller set of circumstances like having poor signal and or switching to/from roaming (even if it didn't happen at your current location, but in transit)
IMO something changed in the custom kernels that exacerbates the problem so it happens in more circumstances than before. Just for illustrative purposes let's say it would have been triggered for 5% of peoples' situations with the stock kernel, with a custom kernel it might be triggered for 30 or 40% of the situations. I'm just totally making up those numbers of course.
Also the only real "stock" you can be assured of once you start flashing is this one:
http://forum.xda-developers.com/showthread.php?t=1273647
All the other ones, there is a chance it is a custom kernel even if you see the word "stock" because sometimes folks use the word lightly and it is really "stock+" or stock Android with a custom kernel. I'm not saying every release is using a custom kernel as I haven't tested every one. However, there are some releases I thought were stock, but when I unpacked the initramfs from the zImage, realized it wasn't. Coming from a different platform where recovery and os were kept completely separate, I didn't realize at first but the CWM Recovery actually uses a custom kernel and if you install CWM, you also end up getting that custom kernel for Android as well.
sfhub said:
Based on reading a lot of posts, IMO the bug is in the stock Samsung software but is triggered under a smaller set of circumstances like having poor signal and or switching to/from roaming (even if it didn't happen at your current location, but in transit)
IMO something changed in the custom kernels that exacerbates the problem so it happens in more circumstances than before. Just for illustrative purposes let's say it would have been triggered for 5% of peoples' situations with the stock kernel, with a custom kernel it might be triggered for 30 or 40% of the situations. I'm just totally making up those numbers of course.
Also the only real "stock" you can be assured of once you start flashing is this one:
http://forum.xda-developers.com/showthread.php?t=1273647
All the other ones, there is a chance it is a custom kernel even if you see the word "stock" because sometimes folks use the word lightly and it is really "stock+" or stock Android with a custom kernel. I'm not saying every release is using a custom kernel as I haven't tested every one. However, there are some releases I thought were stock, but when I unpacked the initramfs from the zImage, realized it wasn't. Coming from a different platform where recovery and os were kept completely separate, I didn't realize at first but the CWM Recovery actually uses a custom kernel and if you install CWM, you also end up getting that custom kernel for Android as well.
Click to expand...
Click to collapse
You make some valid points but this issue is not exclusively related to rooted/custom roms. That fact points to it being a software or hardware problem.
On top of that, I guess i'm the ONLY one that gets this issue without even seeing the LOS red circle icon. I wonder why this is.
LxMxFxD said:
You make some valid points but this issue is not exclusively related to rooted/custom roms. That fact points to it being a software or hardware problem.
On top of that, I guess i'm the ONLY one that gets this issue without even seeing the LOS red circle icon. I wonder why this is.
Click to expand...
Click to collapse
Red circle? Mines is white. But no, a few other people have mentioned having the problem without seeing the icon. I did on the first page of posts in this thread actually. I believe that it just hasn't switched over to the icon yet. That is what worries me more, it can be LOS for two hours and not have the icon, then the icon will appear. I've also RECEIVED A CALL while the icon for LOS was showing. Couldn't make an outgoing call about 10 seconds before that.
The bug obviously doesn't have anything to do with current service, but more switching. I believe when it makes that switch, from no service, or wifi, or 4g, etc, back to 4g, it hangs somehow. In fact, the phone is still getting fine service, it just shows the LOS icon, which makes the phone THINK it can't receive or send calls.
I don't know anything and these are just my hypothesii, but I'm past my 14 days now and the worse part about it is Sprint acts like they've never heard of the problem and so does Samsung! That's scary.
jirafabo said:
Red circle? Mines is white. But no, a few other people have mentioned having the problem without seeing the icon. I did on the first page of posts in this thread actually. I believe that it just hasn't switched over to the icon yet. That is what worries me more, it can be LOS for two hours and not have the icon, then the icon will appear. I've also RECEIVED A CALL while the icon for LOS was showing. Couldn't make an outgoing call about 10 seconds before that.
The bug obviously doesn't have anything to do with current service, but more switching. I believe when it makes that switch, from no service, or wifi, or 4g, etc, back to 4g, it hangs somehow. In fact, the phone is still getting fine service, it just shows the LOS icon, which makes the phone THINK it can't receive or send calls.
I don't know anything and these are just my hypothesii, but I'm past my 14 days now and the worse part about it is Sprint acts like they've never heard of the problem and so does Samsung! That's scary.
Click to expand...
Click to collapse
I don't know how customer service at sprint works or whatever, but when I called sprint yesterday about this issue the woman I spoke with told me within 15 seconds that there is a "known issue for a minority of these devices." She suggested exchanging it but since I got this phone from amazon for a reduced price, not really an option (I may never do that again). I was impressed that sprint was very upfront and at least offered a solution instead of saying "no, theres no problem at all" like others have reported. When I told her I would be returning the phone within the 14 day period if it isn't fixed by then she said she'd do the same thing, and that there was "no option" to extend the 14 day period to 30 days despite my offer for me to put up with this problem for a full 30 days.
In the end sprint's new policies are all for the iphone launch and hurting existing customers.
I am currently tethering over a 4g connection, and my internet is working fine, BUT I have a complete LOS for the cell signal. I think this could be a very important fact because we should be able to know some things by the fact that WiMax is working while the cell signal is altogether lost.
Hopefully, with this info, a solution is a little closer at hand.
Ok...when people say LOS do they mean Loss Of Service? Or Loss Of Signal?
Because if its the latter, that sht aint that bad. But if its the former...I'm glad I don't have it.
ms79723 said:
Ok...when people say LOS do they mean Loss Of Service? Or Loss Of Signal?
Because if its the latter, that sht aint that bad. But if its the former...I'm glad I don't have it.
Click to expand...
Click to collapse
It is bad. People that get it have to reboot phone for it to come back and it kills battery life. Nit to mention missed calls and texts. It is a complete loss of service.
Sent From My Evo Killer!!!
Its 2 separate radios..
I had pandora going over 4g earlier for hours...but lost signal with a crossed out circle after about an hour. Pandora kept going but u couldn't make a phone call, ths.falls in line with the other poster. Im running eg30plus over latest 2.1 midnight.
Sent from my SPH-D710 using xda premium
As WhiteWidows stated, it's 2 different radios. The LOS people have posted over and over about is the ability to make/receive calls (which is what the OP posted about). The Wimax radio (4G) doesn't transmit phone calls. That's why you can do data on 4G and still make a call at the same time.
.....
Hi guys, this is one of my first posts but I've been a long time reader coming from the Evo 4G forums. I'm rooter using Zedomax v3 and experienced multiple LOS as well.
Last night I tried limiting the clock speed to 1ghz and setting the min at 400mhz. Strangly I now get slightly better reception and never had a LOS yet. Will continue to test out this theory and see if it's clock speed related.
I came about testing this since I ran mine at 1.6 for a while and not only would I get more LOS occurances, I would also get phone freezes lol. I tether and stream music a lot so wanted to keep it slightly underclocked to keep the temps down. Hope this helps as a temporary band aid for the LOS bug
It definitely makes sense that the two radios are separate...the point of my post was just to offer some more information to help figure out a fix.
If one radio fails while the other stays working, do we know that the problem is phone-related? Many posters have speculated that the issue may be on Sprint's end, so I wasn't sure if this info did anything to challenge or support that theory. Maybe it does nothing, though -- just throwing it out there!
Someone posted a log cat of a LOS. There's still some coding in the radio files that thinks there is a sim card. Says sim disconnected and result radio off
sent from my DAMN ET4G!!!!
Hopefully a solution is found soon, I've seen similar issues posted on various android forums. Androidforums, Sprint community and here. Wish I waited a bit to hear more user experiences....
Success100 said:
Someone posted a log cat of a LOS. There's still some coding in the radio files that thinks there is a sim card. Says sim disconnected and result radio off
sent from my DAMN ET4G!!!!
Click to expand...
Click to collapse
Has anyone tried editing the build prop to manually change the preferred network from wcdma to CDMA auto? Maybe that'd fix that issue
I have been on my current SGS2 stock out of the box for over a week now and have not had any LOS issues, or missing texts, or data not working, or missing phone calls, etc.....
I have been using wi-fi, 4G, 3G, have an Airaive, went to an area where there is no Sprint service and phone roamed fine and then went back to Sprint service when available.
I have been unable to replicate the LOS issue on my current phone through all possible ways of using it.
My first SGS2 was also fine until I rooted it which then gave me an LOS within 12 hours of doing so.
If someone has a another sure way to get an LOS, I am willing to try it on my stock, never rooted phone but I don't think there are any other situations I can try that I haven't already......
Time.I have went 3 days without a los then 2 in same day.It is all random
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.
Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working
did you check your apn?
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up
Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!
I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.
Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)
i have 12.01
will try reflashing the latest radios
tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?
unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal
Any updates? I'm having the same problem
Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?
It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.
PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.
I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.
OK so I've searched this a lot and really didn't want to make a thread but it's driving me crazy. My WiFi calling is rock solid all day and then from 6, 7, or 8pm till around midnight it constantly drops and comes back. I've gotten the red invalid certificate thing and reg99 (or 09). Whichever one IS NOT the 911 one, my address is up to date.
Is it network traffic at night or what?? My house has 0 cell coverage so WiFi calling is important. It's getting really frustrating having it drop and come back every few minutes.
I'm on frostyjb, but I think that's probably irrelevant. From the tmo forums it sounds like these issues have been around for a year or so. Does anyone have any advice, or tips or tricks?
Thanks.
Most likely its due to increased traffic on your isp. They probably don't have a very good uplink making it easier to run into these type problems.
That's my best guess seeing as it always happens at the times known for heaviest traffic.
Sent from my SGH-T999 using xda app-developers app
I've been using Wi-Fi calling since it was first released on Blackberry, haven't noticed a specific time when it fails, seems to be random.
I will say each phone has had its own "quirks". the HTC Sensation wouldn't like to re-register to Wi-Fi Calling until it established a mobile network connection, pretty annoying
but I will say without a doubt this is the worst phone for Wi-Fi calling I've had to date. Samsung really needs to fix it. generally my issues include:
- One way audio (10% of the time, or more)
- "Digitized" voice calls
- Red certificate error
- WiFi calling just shuts down, in the menus it says "enabling calling", typically takes 3 - 4 minutes to come back up
- Dropped calls, typically due to above
- Wi-Fi signal drops, I have my router on my desk and I can watch the Wi-Fi connection bar randomly drop to 1 / 2 bars for a few mins then go back up, why? no idea. Doesn't happen on my Tab 10.1 or other devices
OVerall its an awesome phone if you have signal, but the wi-fi calling is trash
psykhotic said:
OK so I've searched this a lot and really didn't want to make a thread but it's driving me crazy. My WiFi calling is rock solid all day and then from 6, 7, or 8pm till around midnight it constantly drops and comes back. I've gotten the red invalid certificate thing and reg99 (or 09). Whichever one IS NOT the 911 one, my address is up to date.
Is it network traffic at night or what?? My house has 0 cell coverage so WiFi calling is important. It's getting really frustrating having it drop and come back every few minutes.
I'm on frostyjb, but I think that's probably irrelevant. From the tmo forums it sounds like these issues have been around for a year or so. Does anyone have any advice, or tips or tricks?
Thanks.
Click to expand...
Click to collapse
I am in the same situation and I assumed it was just my phone losing wifi coverage at least now I know im not crazy. I would assume its just something to do with the date turnover because it seems to happen at around 9pm for me which is midnight on the east coast.
I had the same problem, So first i would try updating the firmware for your router. If that doesnt work, Check to see if your router is a single or dual band. I had a single band Linksys,which gave me terrible reception, so I upgraded to a dual band and the problem is much better now.
I have a dual band router but I don't use 5g because its range is pretty bad. It has drop outs when I go in the bathroom and that's a big time use for me lol.
When wifi calling drops I still have full wifi signal and the Internet works. It really sucks because I have 0 bars in my house. I've seen 2 bars but as soon as I touch the phone I get the do not enter circle.
I'll try updating the fw to see if it helps tonight. I've read something about the security used can mess with it? I just think it's weird that its usually at a specific time. Ie the security settings is a cop out.
Yeah, I read that having mac filtering enabled or a hidden ssid can cause issues too. Check that out while youre updating your firmware. Edit: I also tried a factory reset, which you might want to look into. Also, try testing other kernals/modems!. Thats all I got for ya though. Best of luck
Sent from my SGH-T999 using xda app-developers app
I blame tmo...
I ran a speedtest immediately to see if anything was suspicious. I still need to play with the router
psykhotic said:
I blame tmo...
I ran a speedtest immediately to see if anything was suspicious. I still need to play with the router
Click to expand...
Click to collapse
I plan on flashing FrostyJB and Xquizit tomorrow. I'll let you know if I can replicate the issue on either rom.
Is it possible that having Comcast voice is somehow screwing up the internet? Like if tmo and Comcast are sending similar packets??
Not Only Me
Its nice to know I'm not the only one with this problem.
I updated the firmware on the phone, bought a new router; still have the problem... The little blue phone icon comes and goes, turns red. Seems to do what ever it feels like doing.
Will follow the thread for a solution.
Thanks to all for the effort.:good:
The last few nights have been a little better. With it usually coming back after leaving the phone on for a minute or so but it's still dropping every night. It really sucks for me because my house has 0 bars.
Im also having same problem where I live. I have no bars. I use Grove ip to make calls when wifi calling dosent work but I need wifi calling to send and receive mms thats the only down fall to grove ip
Sent from my SGH-T999 using xda app-developers app
I have been having the same issues too. Not necesarilly at specific times, pretty much all times of the day. Specifically random disconnects in the wifi calling (losing the symbol all together, then it comes back spontaniously whenever it wants). Probably the most irriating is the one way audio which has occured EVERY PHONE CALL RECIEVED OR PLACED for the 1st time after about 10 minutes of inactivity (meaning everytime I make or recieve a call the one way audio happens and I have to call back or the other party must blah blah blah). And digitized calling is almost a guarantee on every call. All is well with router and wifi settings, no data/cell service inside the building at all.
This is my second GSIII (this is a refurb POS they sent me after my new one had a screen crack). After 2 week back and fourth they are replacing it Ill have a new one tomorrow (prob another dumb refurb) and Ill let you all know if the issue is resolved. My first GSIII (the brand new one I purchased when they came out) had no issues like this at all. Hopefully they replacement will shed light.
No one can hear me when I use it (8 of 10 times). I also never hear a ring. People are just on the line all the sudden. Sooooo frustrating.
Does everyone have this problem? If not maybe it's a router setting? Would be interesting to know.
jjlean said:
No one can hear me when I use it (8 of 10 times). I also never hear a ring. People are just on the line all the sudden. Sooooo frustrating.
Does everyone have this problem? If not maybe it's a router setting? Would be interesting to know.
Click to expand...
Click to collapse
I've had this. I was calling someone on Verizon and after some silence they picked up. Also if I call my phone from my Comcast landline there's no indication it's going through on the landline but my phone rings. I think these issues have been around awhile and tmo hasn't done anything. I wonder how we can get them to actually look into it...
Flood the support forums maybe?
Sent from my SGH-T999 using xda app-developers app
Yeah I think we need to bring this to t-mobile attention because most of all that i've read on here, i'm experiencing the same. I've tried different router settings as well but, nothing has worked.
Sent from my SGH-T999 using Tapatalk 2
I tried dmz and opening ports that tmo has on their forums. Nothing worked.
Sent from my SGS3 Stock Rooted & Odexed
I love this thing!
I've been troubleshooting as well. Looking into my router settings, I had my channel set to 11. I changed it to 1 and so far so good. I'll update as I go.
I'm just sayin!
Hey folks,
Just a quick question I was hoping to get some clarification on:
Like many, I got the 4.2.2 OTA on Tuesday evening and everything went fine with the download and install. That being said, I'm having some signal issues that are a bit strange. For the most part the signal quality is fine. Not really having any connection issues, but I've noticed lower bars being shown overall. After doing some digging though I've determined that apparently 4.2.2 reports signal quality differently than 4.1.1 did... representing a much truer value based on dBm and not overly inflating things for constant 3-4 bars. Essentially it's like I remember way back with 4.0.2. I still find it a little odd that I can show -85dBm and only have 1 bar, but if that's how things are reported in 4.2.2 then so be it.
The thing that's bothering me though is this: at times my signal will read 0dBm 99asu. I'll have zero bars showing, but it will still show 4g in the notification bar and will say connected to the network in status. I can make calls, text, surf the web, download apps, even run speed tests without any problem (although not great numbers, they're not horrific either) Eventually bars and dBm "come back", but the amount of time for that to happen varies. Again, nothing seems to be affected by this, but it's just a little disconcerting to have happen.
So, has anyone else experienced this? Google searches show some talk of it but otherwise haven't turned up much. I've done a battery/SIM pull and that didn't change things. Is it possible something may have gone a bit sideways in the ota download? Was thinking a factory reset may help too but not looking forward to wiping my device only to find out this is pretty normal.
Any help would be greatly appreciated. Thanks in advance.
It's possible that the OTA updated the baseband, please look into that as I'm not entirely sure. If that's the case, then it might just be that the new baseband is not suitable for your coverage area in which case I'd suggest you flash a previous release.
iLeopard said:
It's possible that the OTA updated the baseband, please look into that as I'm not entirely sure. If that's the case, then it might just be that the new baseband is not suitable for your coverage area in which case I'd suggest you flash a previous release.
Click to expand...
Click to collapse
Thanks for the reply. I'll fully admit I'm not as up to snuff on this as others, so please correct me if I'm wrong... but the 4.2.2 OTA did in fact contain new radios from VZW, so shouldn't the baseband have been updated for everyone who took it?
Mine is: I515.10 V.FK01/I515.FK02
As I understand it that breaks down to phone model (I515), HW rev 10, with the new radios being FK01/FK02
Wouldn't every VZW GNex that was on the 4.2.2 OTA have the same baseband; outside of having either HW rev 9 or 10?
Currently I'm locked, stock, not rooted... yeah, probably one of the last Thinking I may unlock and root and try the 4.1.1 radios again. Do I need TWRP or CWM to flash those or can that be done if I keep stock recovery?
As always thanks for all input, much appreciated.
My Gnexus is the same . but despite that it actually performs better oddly enough
Do/can you update roaming (*228) with the Verizon nexus? Or is that just something I could do with my old fascinate (yes, a fascinate and then nexus... I am a glutton for VZW punishment).
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Do/can you update roaming (*228) with the Verizon nexus? Or is that just something I could do with my old fascinate (yes, a fascinate and then nexus... I am a glutton for VZW punishment).
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You can, but as far as I know you'll then have what is considered a 3G PRL pushed to your phone, something beginning with "5"... if you just let the PRL update and push on it's own like it's supposed to you'll have a 4g PRL, and will begin with a "1" Both work the same and pick up both 3G/4G signals...not sure what the true difference is honestly. I've been on 15192 for ages now and it's been fine up to this point... Think I'd just as soon keep it. Thanks for the suggestion though.
I Read some where online. That if you take out the Sim card let it for like a minute or so. Slap it back in and there you go. It work for me
ironside2011 said:
I Read some where online. That if you take out the Sim card let it for like a minute or so. Slap it back in and there you go. It work for me
Click to expand...
Click to collapse
Yeah, did that... battery pull and sim card pull... left it out for 30 min then back in... no difference. Like I said, it's not that I'm having a huge problem with my data connection, it's just acting... strange... kind of all over the place. Lots of fluxuation, odd readings/bar equivalents, and the whole 0dbm 99asu thing with still being connected. However I've also now started seeing higher than normal "time without signal" percentages... Just flakey. And frustrating... no issues at all until the 4.2.2 ota.
mine is not really a problem but I had way more bars of coverage in a multitude of places (work, home, gym, etc) on the old radios. I havent looked at the dbm's but visually it's different. might be something for someone interested to look into.
btw, im in fresno, ca.
bubarub said:
mine is not really a problem but I had way more bars of coverage in a multitude of places (work, home, gym, etc) on the old radios. I havent looked at the dbm's but visually it's different. might be something for someone interested to look into.
btw, im in fresno, ca.
Click to expand...
Click to collapse
Well Google changed how the signal is read visually through the bars to provide a more accurate reading. You should look at dbm
Toro | Xylon | Diamond
Having the same experience here (Whidbey Island, Washington) where the 4g signal clings on until it absolutely had to fall back to 3g. New radios may be contributing, but the change in coding to report lower signals may have improved the ability to hang on to a 4g signal. Hand off seems pretty slick too, but that's likely a function of the new radios that came in the OTA.
Sent from my Xoom using xda premium