Jump to content

Recommended Posts

I'm not talking about 3G drops but staying on 3G long after I'm in an area with known good LTE.

 

Sent from my Nexus 5 using Tapatalk

 

That sounds like a scan timer issue. A number of factors can affect that, including if a data session is active. 

 

I tested that a couple weeks ago on a drive to KC. Drove from 3G only area to full LTE coverage with Spotify streaming. It took 45 minutes to switch to LTE. The next week I had no data active. It switched within 3 minutes. 

  • Like 1
Link to post
Share on other sites
  • Replies 9.8k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I had a Sprint product development employee reach out to me this morning after reading this thread. His message says:   Robert via Samsung Note 8.0 using Tapatalk Pro

I am now the proud owner of a Nexus 5!       Sent from Josh's iPhone 5 using Tapatalk 2

Mine just arrived!!!  

Posted Images

If the whole 'network controls the connection' thing worked, the network should request and/or force the device to switch to LTE as soon as it hits a tower that has lte enabled.

 

In other words;

 

If a device connects via 3g to a tower with known LTE service, the network should tell/request/force that device to hand off to the applicable LTE service, regardless. and *especially* if there is an active data session.

 

there is *zero* reason why the network should allow an active data session to monopolize/camp on 3g when the network *knows* there is LTE available.

Link to post
Share on other sites

If the whole 'network controls the connection' thing worked, the network should request and/or force the device to switch to LTE as soon as it hits a tower that has lte enabled.

 

In other words;

 

If a device connects via 3g to a tower with known LTE service, the network should tell/request/force that device to hand off to the applicable LTE service, regardless. and *especially* if there is an active data session.

 

there is *zero* reason why the network should allow an active data session to monopolize/camp on 3g when the network *knows* there is LTE available.

That's not how it works. Currently, the tower doors not tell your device what networks are available. Your device tells the network what it is picking up with its scans. If it hasn't had an opportunity to scan, it can't change bands because it didn't know it's there.

 

Once the device reports what technologies it is picking up, the network can then move it around on different bands.

 

Sent from my LG G3

Link to post
Share on other sites

right, that fact is why that is part of the problem.

 

The device should not be required to spend it's limited power and time scanning for lte, when the network should automatically know and direct the device to the most appropriate tower(s) and/or band(s).

 

Now in instances where the device is in the process of connecting to the network or moving out of signal range before the network can react, then it should fall back to device-based scanning and connect as needed.

 

The way it currently is, is a failure on the part of the network.

Link to post
Share on other sites

right, that fact is why that is part of the problem.

 

The device should not be required to spend it's limited power and time scanning for lte, when the network should automatically know and direct the device to the most appropriate tower(s) and/or band(s).

 

Now in instances where the device is in the process of connecting to the network or moving out of signal range before the network can react, then it should fall back to device-based scanning and connect as needed.

 

The way it currently is, is a failure on the part of the network.

 

As far as I know, no network operates in the fashion you describe. I'm not sure, but I don't think it can be done that way.

Link to post
Share on other sites

That sounds like a scan timer issue. A number of factors can affect that, including if a data session is active.

 

I tested that a couple weeks ago on a drive to KC. Drove from 3G only area to full LTE coverage with Spotify streaming. It took 45 minutes to switch to LTE. The next week I had no data active. It switched within 3 minutes.

Understood. I have most push/pull apps turned to manual. I pay for every drop of data I use since I'm with Ting. I know that I still have a few apps that do poll automatically but my feeling is that since I've gone back to the stock radio for 4.4.4 my N5 is camping on 3G much more than with other radios I've tried.

 

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites

Understood. I have most push/pull apps turned to manual. I pay for every drop of data I use since I'm with Ting. I know that I still have a few apps that do poll automatically but my feeling is that since I've gone back to the stock radio for 4.4.4 my N5 is camping on 3G much more than with other radios I've tried.

 

Sent from my Nexus 5 using Tapatalk

 

Is it specific areas this happens or is it random? Based on the last report we got, a lot of the urban STL sites are still lacking CSFB on Band 26, or are otherwise undiscoverable which can cause problems with tri-band devices. Band 41 can also cause similar issues if it's provisioned incorrectly. If it's random, not sure what the issue could be.

Link to post
Share on other sites

It doesn't feel random but I haven't been specifically tracking it. So far the worst seems to be I44 until I cross into Illinois. Once I'm on 255 driving North I do not drop LTE. Again this could point to what you were saying about tower spacing and scan time. Since my phone usage pretty much has stayed the same but I have noticed enough of a difference in how often my phone shows 3g versus LTE in areas where I have previously had good and/or usable LTE the new radio appears to be the culprit.

 

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites

It doesn't feel random but I haven't been specifically tracking it. So far the worst seems to be I44 until I cross into Illinois. Once I'm on 255 driving North I do not drop LTE. Again this could point to what you were saying about tower spacing and scan time. Since my phone usage pretty much has stayed the same but I have noticed enough of a difference in how often my phone shows 3g versus LTE in areas where I have previously had good and/or usable LTE the new radio appears to be the culprit.

 

Sent from my Nexus 5 using Tapatalk

I don't agree with the new radio being the culprit. I think the old radios were ignoring network CFSB issues where the new radio seems to place you on the band with the best service making sure you receive calls. A usable LTE band is not "really" usable if it has CFSB problems. Unless you are not concern with receiving calls then I guess the 4.4.4 radio is not the one for you.
Link to post
Share on other sites

I I had strange issue last night where I had my phone plugged in overnight but woke up to 77% battery life. Here is what the battery graph looks like with all kinds of spikes overnight. The phone was on wifi overnight. I don't see any evidence that we have the power outage in the house.

 

What I thought was weird is that the mobile network signal color bar ends and never comes back including now where I've been off wifi and on a mobile signal for over 2 hours. Any idea what's going on with having no continuation of the mobile network signal bar?

 

urehe9az.jpg

Link to post
Share on other sites

 

 

I I had strange issue last night where I had my phone plugged in overnight but woke up to 77% battery life. Here is what the battery graph looks like with all kinds of spikes overnight. The phone was on wifi overnight. I don't see any evidence that we have the power outage in the house.

 

What I thought was weird is that the mobile network signal color bar ends and never comes back including now where I've been off wifi and on a mobile signal for over 2 hours. Any idea what's going on with having no continuation of the mobile network signal bar?

-picture-

Do you have another charging cable? It looks like your cable is faulty, or possibly any extension cord/power strip you have it plugged into at night. My original cable started doing that where it'd only charge occasionally because I normally have it sitting a few off the ground on a desk and then the cable angles down towards the ground. Now I got a new cable and everything works fine, I just use the old one for transferring files because my new one doesn't seem to work for that. As for the bar not showing up it's possible that the random stopping and starting of charging(I'm assuming it has happened more than the pictures show, they're just so small you can't see them) has caused the reporting to just go funky. I'd try a reboot first and if that still doesn't work you can either completely discharge the battery and recharge, or factory reset.

Link to post
Share on other sites

I had a similar thing happen last night and had a significant "time without service" issue.

 

Sent from my Nexus 5 using Tapatalk

Tower work maybe? Don't they have to shut existing equipment off when they're adding new panels (like 8t8r)?
Link to post
Share on other sites

Ya I'm hoping that's the reason, the closet tower to me has antenna I have never seen before, and I'm pretty sure it's sprint but I haven't had a chance to go get a picture.

 

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites

Ya I'm hoping that's the reason, the closet tower to me has antenna I have never seen before, and I'm pretty sure it's sprint but I haven't had a chance to go get a picture.

 

Sent from my Nexus 5 using Tapatalk

 

Can you PM in me the location?

Link to post
Share on other sites

Anyone heard if the Nexus 5 will get updated for wifi calling?

It is assumed by many that the Nexus 5 will not get WiFi calling.

 

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites

Anyone heard if the Nexus 5 will get updated for wifi calling?

Google would have to add it to stock android which is unlikely.
Link to post
Share on other sites

Google would have to add it to stock android which is unlikely.

Someone already mentioned on this thread that Wi-Fil calling is already built into android.  I think the greater question is whether or not it would work Sprint's current setup, and if it did work with it, would sprint invest the time to implement it to a phone that probably has a pretty low adoption rate on their network?

Link to post
Share on other sites

Someone already mentioned on this thread that Wi-Fil calling is already built into android. I think the greater question is whether or not it would work Sprint's current setup, and if it did work with it, would sprint invest the time to implement it to a phone that probably has a pretty low adoption rate on their network?

I don't see carrier specific changes coming to the Nexus. You can achieve Wi-Fi calling via Google voice, but I doubt it will ever get official Sprint support. Never know though.

 

Sent from my LG G3

Link to post
Share on other sites

Someone already mentioned on this thread that Wi-Fil calling is already built into android. I think the greater question is whether or not it would work Sprint's current setup, and if it did work with it, would sprint invest the time to implement it to a phone that probably has a pretty low adoption rate on their network?

Android doesn't have Wifi calling. Google voice is the closest you'll get to that.
Link to post
Share on other sites

Android doesn't have Wifi calling. Google voice is the closest you'll get to that.

 

eh?

 

dialer > settings > call settings > internet call settings

 

its not 'sprint wifi' calling, but can and does work over sprint data or wifi service, assuming you have a valid sip server/account.

  • Like 1
Link to post
Share on other sites

eh?

 

dialer > settings > call settings > internet call settings

 

its not 'sprint wifi' calling, but can and does work over sprint data or wifi service, assuming you have a valid sip server/account.

Yep, been there since Gingerbread.

 

Sent from my Nexus 7 using Tapatalk

Link to post
Share on other sites

eh?

 

dialer > settings > call settings > internet call settings

 

its not 'sprint wifi' calling, but can and does work over sprint data or wifi service, assuming you have a valid sip server/account.

Yep, been there since Gingerbread.

 

Sent from my Nexus 7 using Tapatalk

SIP is not considered WiFi calling. None of the carriers use SIP for WiFi calling. Whatever the reason for that may be, it must be a good one. I presume it's due to the integration of SIP into the core network. Also, SIP doesn't support text messaging, something WiFi calling does support (at least on sprint).
Link to post
Share on other sites
  • S4GRU changed the title to Google Nexus 5 by LG Users Thread!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

    • By danlodish345
      Even though Sprint doesn't have the best coverage in my area. I do have lots of memories and nostalgia with the company. I wonder who else here will miss Sprint besides me?
    • By nexgencpu
      First Pixel device im somewhat excited about in a quite a while..
       
    • By vanko987
      I'm new to this forum, and I've seen people mention cell sites with specific ID's (for example, SF33XC664). Is there any significance to these ID's, and is there a way to decode them? Also, how do I figure out what the cell site ID's are for towers near me?
      Thanks! I'm excited to start talking on this site more 😀
    • By lilotimz
      Samsung Network Vision equipment are highly distinct and fairly easy to spot compared to the equipment that other vendors are deploying. Sprint is Samsung's first extremely massive American contract (baring Clearwire) so there  should be no issues in confusing these equipment for another carrier which happens often with Ericsson NV equipment.

      Below are images of Samsung equipment which includes antennas, remote radio units, base stations, and their mounting configurations. 
       
      Samsung antenna with eSMR 800 RRU & PCS 1900 RRU

      A close look at a Samsung setup





      Next Generation Samsung Configuration
      RRH-P4 4T4R 1.9 GHz  | RRH-C4 4T4R 800 MHz| RRH-V3 2.5 GHz

      Next Generation 8 Port Dual Band Antenna Setup 
      4 port 800 MHz RRH-C4 800

      (source: dkyeager)

      (source: dkyeager)
      Narrow beam setup

      High Capacity Site with 2 Antennas & 3 RRUs (2x PCS & 1x SMR).
      Second antenna is PCS only for now.


      Canadian IBEZ (NO SMR)

      Special Case PCS Only Setup for Canadian IBEZ




      Close up of standard antenna connectors 

      Samsung Cabinets

       
       
      Powerpoint slides from Samsung / Sprint
      *disclaimer - all  powerpoint diagrams and images were found through public municipality online databases and is by no means misappropriated through malicious means*
      *Credit goes to those whom took pictures of these equipment. You know who you are*
  • Posts

    • Initially T-Mobile was simply slapping n41 panels onto existing sites which meant that NR+LTE aggregation aggregated all available LTE bands with NR. Now, T-Mobile seems to be replacing 600/700MHz antennas every time they add n41 and as a result, the city is getting covered in split eNB IDs. On a local (legacy) 600MHz site by my home, when I connect to n71 it's n71 + Band 2 + Band 66 + Band 71 or Band 12 for a combined total of 50MHz of spectrum. However on my home site, because of the split eNB, when I force my phone to connect to n71 it only aggregates n71 + Band 2 + Band 66 for a total of 45MHz of spectrum. It seems weird that T-Mobile is allowing this to happen instead of fixing it so that they can squeeze as much performance out of their network as possible. 5MHz of LTE is not much but it's still an extra ~37Mbps of speed and capacity that could be provided in NSA mode. Interestingly this problem is not something I experience in LTE-only mode much anymore. My phone seems to have no issue aggregating LTE bands across the split most of the time.   Another thing that has been bothering me is that according to the FCC dashboard T-Mobile has 400MHz of spectrum in the 39GHz band here in NYC that they won in December of 2019 but they haven't done any upgrades to actually use that spectrum here. Instead they've been relying on the two 50MHz blocks aggregated together in the 28GHz band which performs worse than n41 on average.
    • Betting VZW trades that B12 to TMo for B66 eventually.
    • Confirmed that AT&T is running dedicated n5 here, at 10 MHz, by process of elimination. LTE is 10x10, and H+ is 5x5. They might be running DSS or n2 or n66 but I kinda doubt it. Guessing they aren't running H+ on every site anymore either; signal appeared a good bit weaker than the B5 LTE signal when I band selected to it. Also, B14 is pretty obviously not on every site here; signal levels at my place are comparable to B2 and, well, 700 should be a lot better than that. Explains why I wasn't seeing B14 aggregated normally. Though apparently they have 25 MHz of B66...one 15 MHz carrier, one 10 MHz.
    • I DM”d him on the 16th, no reply yet. Guessing he’s just too busy lately.
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...