dkyeager

Really excited by bands for the neighbor list. Could we get it to optionally display earfcns instead and also limit them to one earfcn? I am referring to small cell hunting, which has a unique earfcn where we have seen them. Else we will also need to find all magic boxes and airaves in our market to get their PCIs (we have most everything else). Magic Boxes also have there own earfcn.

Alternatively allow us to plug in the earfcn for SC, MB, and AR which would then appear in the neighbors list. The ability to truncate or change the font size for the neighbors list would also be great so we can fit more on the screen.

Failing to load on my rooted LG G2s.  Sent a report from each one.

Samsung devices not the network gear OEM, I'm in Ericsson market.

Sent from my LG-LS997 using Tapatalk

The latest update is not showing frequency band information for 800, 1900, 2500. I guess this is because it's a Samsung?

Screenshot_20170619-151119.png

Sent from my LG-LS997 using Tapatalk

Probably not, but we do things our own way here! The site I used for my LTE-related calculations is this one: http://niviuk.free.fr/lte_band.php

 

-Mike

Great site. I use the same one, plus there is another for cdma channels: http://niviuk.free.fr/cdma_band.php

Sent from my LG-LS980 using Tapatalk

Spotted the T-Mobile so was just hoping.

Sent from my LG-LS997 using Tapatalk

No 10x10 for Sprint Samsung 1st carrier LTE with earfcn.

Sent from my LG-LS980 using Tapatalk

Changed Wikipedia band 26 to LTE 800 from LTE 850.  We will see if it sticks.

I'm going to argue the opposite; I prefer LTE 800.  It allows at-a-glance differentiation between B5 (LTE 850) and B26 (LTE 800).

 

Thanks for the update!  I've downloaded it now, and can't wait to try it out, probably tomorrow on my way to/from work.

 

- Trip

Perhaps add SMR.  This change also may not be intentional as it is not listed in the release notes.

My general opinion is to go with how the carrier and their contractors refer to it.  For example, most Sprint contractors and a small sample of Sprint engineers do not know what GMO is (Ground Mount Option), but they do know GMR (Ground Mounted Radio).  I do not know the answer in this case.

LTE 850 shows up with API

Sent from my LG-LS980 using Tapatalk

On my LG V20 (android 7):

Feedback sent

Edit: works after reboot.

Sent from my LG-LS980 using Tapatalk

With today's beta:

I like calling it LTE 850, which occurs with modem enabled while rooted. Without modem enabled LTE frequency disappears ( used to say LTE 800 ). 1x800 should be consistent, ie 1x850.

Sent from my LG-LS980 using Tapatalk

Oops, forgot I was testing that. On Android 7+, it may become a necessity if you have an Alert enabled. If no text is displayed, an exception is occurring and the Alert does not fire. Still exploring this.

 

 

Are you saying the earfcn is not always accurate on these ALU sites in Samsung territory? Or in general? Are you seeing inaccuracies via the root method or the native Nougat routine?

 

-Mike

Both sometimes get in transition or erroneous earfcn. Also true with other apps. Other data items can also be in transition such as pci, plmn, or tac.

Of course CDMA has a host of inaccuracies. Ultimately the best way to display for known sites is BID and distance. Sprint also appears to tinker with them. Some phones much worse than others, especially with 1x800.

Of course I flag any exceptions in the data I analyze, so these things stand out for me. Fortunate we have many people logging so bad data gets corrected soon. Multiple phones also help, but not always.

Sent from my LG-LS980 using Tapatalk

So I've been removed from the group for awhile and I cannot remember. Was there anyone collecting logs to amass a database of site information? Or has that effort gone to the wayside? I remember some talk about it, but can't recall. Thanks!

Sent from my LG-LS997 using Tapatalk

Other than earfcn is not always accurate, no problems encountered on another trip with three phones running beta. 

Sprint market 07C, which is Samsung, also has ALU sites.  They appear to all start at 500hex and end before 2501dec based on analysis of others and what I am seeing in logs.

I haven't paid attention before the beta update but is the ASU measurement broken now on Samsung devices?  The reason I am asking is that my S8 is only showing (99 asu).

I saw it this morning on a LG G6 screen from imex99.

Any way to just turn off the "LTE connection found" message on the pull down screens?  Thanks

Boot in safe mode and see if it does the same thing. If not, then an app is to blame. If it stays the same, are you in a fringe signal area, including wifi?

Sent from my LG-LS997 using Tapatalk

Band 26 was spotted near Brooklyn, MI (sorry I don’t know how to upload a picture from my phone)

tap-a-talk app is the easiest method

I think we have to look at the MM carriers as being virtual, like the triband antennas. which currently use the second carrier at some sites and the third carrier at others.  It is useful for people to know how many possible carriers are at a site based soley on what carrier they are on.   So I would have MM, MM²,MM³,MM⁴ for these high capacity sites.  So many people assume that no new bands equals no new capacity.  This is an educational effort.

Ah.. but as far as SCP goes, is that something that warrants some sort of special indicator beyond "MM"?  Are these sectors confirmed by anyone else out there? I haven't seen any other reports of them besides what I observed at Fenway.

 

-Mike

There are rumors of another in New Orleans.  It would expect high capacity MM sites to increase as time goes on.  Based on what I have seen, they should have enough ports on the routers for the additional MMs to plug into. We have over 110 sites of MMs in Columbus, some with small cells nearby.

That is probably a swipe at me. The national DB uses the data from market spreadsheets to give a clearer image on how far you are in the neighbor cells. It uses -1 on known PCIs so it does not get wrote over. Unless you want to add tower location columns that are only used in the app to read and only used for neighbor cells distance. The big collection of SCP log is only 8.26MB with over 67,000 sectors. 

No swipe intended.   Weaker RSRPs on changed PCIs have much higher odds of being in error.  This is actually a function of how many times this particular sector and band are seen (know from Signal Detector) but I assume that counting that would be even more difficult.

Stock LG G4 with Android 6.0 works as it should, that is a typical SCP older phone (no earfcn).

Confirmed B25 10x10 earfcns are 8140, 8290, 8390, 8640.  Likely are 8090, 8140, 8240, 8290, 8390, 8440, 8490, 8540, 8590, 8640 assuming typical alignment [thanks to lilotimz for helping to finalize this list].   Messy situations would have to be identified per market.

Look at this further today, the GCI sector is not tied to carrier.  Instead they are very much like Triband Antennas where 09, 0A, 0B floats currently between second and third carrier.