Jump to content

Recommended Posts

I have a question about how my device (Galaxy Note II) decides what network to connect to. When connected to 3G, obviously it doesn't constantly scan for 4G at all times. I've noticed a few posts on S4GRU mention a half-hour scanning period. Does this mean that conceivably the device could unsuccessfully scan for 4G at 4:00 pm, and then you enter a 4G area at 4:01 pm, but the device won't switch to 4G until 4:30? I feel like I'm misunderstanding, since this doesn't make sense.

 

Thanks.

Link to comment
Share on other sites

Not really.. It's one of those unknowns. I believe on the latest update in the note2 though that the next LTE scan timer was lowered to 5. Is it 5 minutes? Not sure. What's the LTE available file for? Why does the phone track the 1x basestation IDs where it picked up LTE. Does it scan more often in those areas where it learned where LTE was? Maybe.

 

One of those assumption things since we don't have the baseband code to look over.

Link to comment
Share on other sites

I have a question about how my device (Galaxy Note II) decides what network to connect to. When connected to 3G, obviously it doesn't constantly scan for 4G at all times. I've noticed a few posts on S4GRU mention a half-hour scanning period. Does this mean that conceivably the device could unsuccessfully scan for 4G at 4:00 pm, and then you enter a 4G area at 4:01 pm, but the device won't switch to 4G until 4:30? I feel like I'm misunderstanding, since this doesn't make sense.

 

Thanks.

Good question, but next time try to refer to each respective cellular system with their proper name and not the generic 3g and 4g labels. Don't want AJ to go on a tirade if it can be avoided.

 

Not really.. It's one of those unknowns. I believe on the latest update in the note2 though that the next LTE scan timer was lowered to 5. Is it 5 minutes? Not sure. What's the LTE available file for? Why does the phone track the 1x basestation IDs where it picked up LTE. Does it scan more often in those areas where it learned where LTE was? Maybe.

 

One of those assumption things since we don't have the baseband code to look over.

Notice digiblur's use of LTE and 1x instead of 4g and 3g.

  • Like 2
Link to comment
Share on other sites

Not really.. It's one of those unknowns. I believe on the latest update in the note2 though that the next LTE scan timer was lowered to 5. Is it 5 minutes? Not sure. What's the LTE available file for? Why does the phone track the 1x basestation IDs where it picked up LTE. Does it scan more often in those areas where it learned where LTE was? Maybe.

 

One of those assumption things since we don't have the baseband code to look over.

On my Stock GS3, it'd take around 5-15 minutes on average to connect to LTE.  This is without toggling anything.  When I'm on an AOSP-based ROM, I usually get it within 5 minutes.  I want to say it's in the RIL, rather than the baseband, since the baseband doesn't change going from Touchwiz to AOSP.

Link to comment
Share on other sites

i know that once you know your MSL number and press ##DATA# on the number pad, it directs you to data programming. if you want to edit, you need your MSL number and there are some apps that will get you the number. if you have the access to it then you go to BSR, then TIMER MENU. and choose NEXT LTE SCAN TIMER and i think lowest is now 1 minute. i set mine to 1. 

Link to comment
Share on other sites

i know that once you know your MSL number and press ##DATA# on the number pad, it directs you to data programming. if you want to edit, you need your MSL number and there are some apps that will get you the number. if you have the access to it then you go to BSR, then TIMER MENU. and choose NEXT LTE SCAN TIMER and i think lowest is now 1 minute. i set mine to 1. 

 

I have done this as well and I believe it has made a difference as I pick up LTE very quickly in areas now without having to toggle airplane.

Link to comment
Share on other sites

Not really.. It's one of those unknowns. I believe on the latest update in the note2 though that the next LTE scan timer was lowered to 5. Is it 5 minutes? Not sure. What's the LTE available file for? Why does the phone track the 1x basestation IDs where it picked up LTE. Does it scan more often in those areas where it learned where LTE was? Maybe.

 

One of those assumption things since we don't have the baseband code to look over.

Seems like it's more complicated than scanning once every "x' minutes... Which I guess is a good thing because hopefully its more intelligent than that.

 

i know that once you know your MSL number and press ##DATA# on the number pad, it directs you to data programming. if you want to edit, you need your MSL number and there are some apps that will get you the number. if you have the access to it then you go to BSR, then TIMER MENU. and choose NEXT LTE SCAN TIMER and i think lowest is now 1 minute. i set mine to 1. 

Thanks, I also set mine to 1, I'm going to eventually go to a LTE area and see how long it takes to connect. Hopefully this won't hurt my battery too badly.

 

By default the nextLTEScan timer is set to 5, so I assume that the current software on the Note II scans once every five minutes, if in a new area.

Link to comment
Share on other sites

My understanding is (and I may be way off), your phone is converging battery power by not scanning for LTE all the time. However if it finds LTE, it stores data about the connection for future and faster connects.

 

For example, and again this is just a guess, it scans every 15 minutes. This time, it gets lucky and finds a LTE signal and connects. Once it connects, it takes information from the tower (site I'D or something) and stores it in a table along with the 1x information about that tower. Then, in the future, if your phone connects to that tower's 1x, it knows that in the past there was LTE at that location, and scans quicker to see if it can get LTE.

 

Maybe this is why when you go to a new area, it takes forever to get LTE (without toggling anything), but once you find LTE, it's much quicker on future connects.

 

Sent from my HTCONE using Tapatalk 4 Beta

 

 

  • Like 2
Link to comment
Share on other sites

My understanding is (and I may be way off), your phone is converging battery power by not scanning for LTE all the time. However if it finds LTE, it stores data about the connection for future and faster connects.

 

For example, and again this is just a guess, it scans every 15 minutes. This time, it gets lucky and finds a LTE signal and connects. Once it connects, it takes information from the tower (site I'D or something) and stores it in a table along with the 1x information about that tower. Then, in the future, if your phone connects to that tower's 1x, it knows that in the past there was LTE at that location, and scans quicker to see if it can get LTE.

 

Maybe this is why when you go to a new area, it takes forever to get LTE (without toggling anything), but once you find LTE, it's much quicker on future connects.

 

Sent from my HTCONE using Tapatalk 4 Beta

i kind of agree with this because same place where you set the TIMER MENU to scan LTE signals, there is LTE data history log and it seems to save all the LTE towers that you have connected to. I have not felt it was taking longer or shorter but the device is definitely keeping a log of which LTE site you have connected to. 

Link to comment
Share on other sites

  • 3 weeks later...

i kind of agree with this because same place where you set the TIMER MENU to scan LTE signals, there is LTE data history log and it seems to save all the LTE towers that you have connected to. I have not felt it was taking longer or shorter but the device is definitely keeping a log of which LTE site you have connected to.

It's actually logging which 1x site you were connected to while on LTE in that log.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

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

    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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