Jump to content

What is LTE Record?


Recommended Posts

I was playing around with my EVO 4G LTE and I found the following in ##DATA# >EPST >View Mode >LTE Record. There I find the following options:

 

LTE available fIle

 

LTE clear file

 

LTE scan Timer

 

BSR Max Timer

 

When I access the LTE Record it looks like a log example:

0. SID:xxxx NID:x BSID:xxxx

 

The file has 15 separate entries. I have noticed the SID and the NID are the same in all 15 entries but the BSID # are all different. Are these settings to access LTE and if modified will it provide access to LTE?

Link to comment
Share on other sites

I was playing around with my EVO 4G LTE and I found the following in ##DATA# >EPST >View Mode >LTE Record. There I find the following options:

 

LTE available fIle

 

LTE clear file

 

LTE scan Timer

 

BSR Max Timer

 

When I access the LTE Record it looks like a log example:

0. SID:xxxx NID:x BSID:xxxx

 

The file has 15 separate entries. I have noticed the SID and the NID are the same in all 15 entries but the BSID # are all different. Are these settings to access LTE and if modified will it provide access to LTE?

 

AJ and I were going over that last night. The LTE Record appears to tell every LTE site your device has connected to. Apparently, even blocked sites.

 

So even though your device may not be getting a LTE signal, we may be able to verify a blocked and rejected LTE connection from this screen.

 

The one thing we have not been able to determine yet is if eHRPD connections also end up getting populated on this list.

 

Robert via Kindle Fire using Forum Runner

Link to comment
Share on other sites

The one thing we have not been able to determine yet is if eHRPD connections also end up getting populated on this list.

 

I have had eHRPD connections everywhere I have traveled in NID 41, NID 42, and NID 43 (and that would include hundreds of different sites/sectors). But I have LTE record entries only for NID 41, which includes the southern suburbs of KC and is where LTE deployment in the market is most prevalent. So, I have to to conclude that the list entries are more than just eHRPD.

 

AJ

  • Like 1
Link to comment
Share on other sites

I have had eHRPD connections everywhere I have traveled in NID 41, NID 42, and NID 43 (and that would include hundreds of different sites/sectors). But I have LTE record entries only for NID 41, which includes the southern suburbs of KC and is where LTE deployment in the market is most prevalent. So, I have to to conclude that the list entries are more than just eHRPD.

 

AJ

 

How do you determine what NID is what area?

Link to comment
Share on other sites

How do you determine what NID is what area?

 

Being a consummate debug/engineering screen watcher, I have manually tracked NIDs for better than a decade, have even noted as Sprint has shifted NID boundaries. But, basically, NIDs correspond to switches (i.e. MSCs). For example, SID 4139 NID 41 (which you could say is the home SID/NID pair for Sprint, as it includes the world HQ in Overland Park) is backhauled to Lenexa MSC_1.

 

Robert has graciously mapped these site by site MSC associations in the Interactive S4GRU Maps sub forum. The site entries do not indicate NIDs, but they do indicate MSCs. So, if you note a change in MSCs between adjacent sites, then you can expect a concomitant change in NIDs between those adjacent sites. In other words, the NID boundary exists between those sites.

 

AJ

  • Like 1
Link to comment
Share on other sites

I wondered to myself whether AJ uses the word concomitant in real life speaking. Myself answered and said; "Yes. Yes he does."

  • Like 2
Link to comment
Share on other sites

The different NIDs between Baton Rouge and New Orleans doesn't mean a switch change unless I am looking at things wrong on the data.

 

I presume that the NID boundary between Baton Rouge and New Orleans coincides with the old affiliate/corporate network boundary. In that case, all bets are off. In my neck of the woods, the Alamosa PCS affiliate NID 1 was absorbed into Sprint corporate NID 43. And if Alamosa operated its own switch, then backhaul was rerouted to Independence MSC_1. In other areas, though, affiliate NIDs may remain as vestiges of a bygone era in Sprint history.

 

AJ

Link to comment
Share on other sites

I have cleared the file, and currently connected eHRPD. The file is empty and has been that way for the last 5 minutes. I will check it again when I get back to overland park where I know there it's lte and let you know what happens.

  • Like 1
Link to comment
Share on other sites

Does this menu exsist on the galaxy nexus?

 

Not so far as I have found.

 

Robert via Kindle Fire using Forum Runner

Link to comment
Share on other sites

I have cleared the file, and currently connected eHRPD. The file is empty and has been that way for the last 5 minutes. I will check it again when I get back to overland park where I know there it's lte and let you know what happens.

 

File is still empty this morning. I will drive by the location where I made the LTE connection, and see what happens then.

  • Like 1
Link to comment
Share on other sites

 

I presume that the NID boundary between Baton Rouge and New Orleans coincides with the old affiliate/corporate network boundary. In that case, all bets are off. In my neck of the woods, the Alamosa PCS affiliate NID 1 was absorbed into Sprint corporate NID 43. And if Alamosa operated its own switch, then backhaul was rerouted to Independence MSC_1. In other areas, though, affiliate NIDs may remain as vestiges of a bygone era in Sprint history.

 

AJ

 

Sounds about right.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

Went back to the area where I picked up LTE, It only connected 3G, and there is still no entries in the file. I suspect you have to actually connect to get a record inserted in the file.

Link to comment
Share on other sites

  • 2 weeks later...

After today's OTA update, I looked in the LTE Available file, which had been empty since I cleared it, and it now has a record.

 

0. SID:4139 NID:42 BSID:785

 

Has the top always said CDMA List?

Link to comment
Share on other sites

Has the top always said CDMA List?

 

Yes. SID/NID pairs are basically a cdmaOne and CDMA2000 thing. LTE does not use SID/NID divisions.

 

AJ

Link to comment
Share on other sites

  • 2 weeks later...

Just found this menu after getting my MSL from Sprint to force my HTC E4GLE to LTE per Robert's post.

 

Most of the SID/NID pairs I have are 4622/5 which has to be Houston. Yesterday I went up to the Woodlands for the Chicago/Doobie Bros concert and I see I know have three entries under 4120/94.

 

I did manage to get an LTE connection at the Pavilion and got my fastest LTE speeds yet: 5.7Mbps down and 7.8Mbps up per the Speedtest.net app.

Link to comment
Share on other sites

  • 2 months later...

So can anyone confirm if changing any values on LTE scan timer or even bsr max timer helps at all... The reason why I'm asking is is seen a post on xda saying people found stronger signal changing the scan timer value to 60.

 

Link to comment
Share on other sites

So can anyone confirm if changing any values on LTE scan timer or even bsr max timer helps at all... The reason why I'm asking is is seen a post on xda saying people found stronger signal changing the scan timer value to 60.

 

I found no difference whatsoever. And stronger signal? That is preposterous. How on earth do they figure the scan timer settings could result in a stronger signal?

 

Robert

  • Like 1
Link to comment
Share on other sites

I found no difference whatsoever. And stronger signal? That is preposterous. How on earth do they figure the scan timer settings could result in a stronger signal?

 

Robert

 

The same way they figure a PRL update gives them better 3G PCS speeds and coverage since they believe it's a list of towers ;)

  • Like 4
Link to comment
Share on other sites

The same way they figure a PRL update gives them better 3G PCS speeds and coverage since they believe it's a list of towers ;)

 

You want a list of towers? I got your list of towers right here.

 

http://en.wikipedia.org/wiki/List_of_tallest_towers_in_the_world

 

AJ

  • Like 4
Link to comment
Share on other sites

  • 4 weeks later...
  • 2 months later...

So can anyone confirm if changing any values on LTE scan timer or even bsr max timer helps at all... The reason why I'm asking is is seen a post on xda saying people found stronger signal changing the scan timer value to 60.

 

I went through the whole "lte connection drama" and as of right now I've been running lte for at least 30mins without any disruptions. My profile is set at 1, scan time at 2, and max timer at 30. It's been the longest I've had lte working without disconnecting...

post-9557-0-83879700-1357744601_thumb.png

Link to comment
Share on other sites

  • 2 months later...

I know I am a little late to this thread (Possibly reviving it?!?!), but I am assuming that the BSR menu will change a few settings inasmuchas LTE scan/connect times?

 

I have changed my timer menu settings under BSR to

 

nextLTEScan Timer 1

BSR timer 1

BSR Max Timer 30

 

 

Theoretically, this should hold an available LTE signal longer and connect quicker, correct? Or am I sadly mistaken? I will let everyone know if it yields any fruitful results as I have not run across many in depth teardowns of ##DIAG# settings (or at least BSR in particular)

 

 

Trying this on the faithful (and replaced/refurbished/who knows, finally) Note 2.

Link to comment
Share on other sites

I know I am a little late to this thread (Possibly reviving it?!?!), but I am assuming that the BSR menu will change a few settings inasmuchas LTE scan/connect times?

 

I have changed my timer menu settings under BSR to

 

nextLTEScan Timer 1

BSR timer 1

BSR Max Timer 30

 

 

Theoretically, this should hold an available LTE signal longer and connect quicker, correct? Or am I sadly mistaken? I will let everyone know if it yields any fruitful results as I have not run across many in depth teardowns of ##DIAG# settings (or at least BSR in particular)

 

 

Trying this on the faithful (and replaced/refurbished/who knows, finally) Note 2.

 

It's usefulness seems to vary by device. It seemed to work in the LGOG, but caused battery life to plummet outside of an LTE area. On my Samsungs and EVO, it did not seem to help catch an LTE signal any faster, nor had any effect on battery life as it should.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

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

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...