Jeffrey_J

Maybe but not likely.

...

That would leave a remaining 500 MHz for guard bands, which would have to be divided six ways.  Probably not sufficient guard bands.

...

AJ

AJ, I thought you were better than that you meant kHz.

out-take

Is this one of the first Radio Shack to Sprint store?

Note that there are two different stores in this folder.

https://drive.google.com/folder/d/0BwjoW3wFn2LrYkhZUDIxSVZBRU0/edit

Alright, I hope someone can help me understand these bandwidth numbers.

 

On Sprint B25 and B26, it reports the bandwidth as "25".

On Sprint B41 it reports "100".

On Verizon B13 it reports "50".

On T-Mobile B4 it also reports "50".

 

Currently I'm just taking the square root of these numbers, and that's what's displayed (that's why 7 x 7 is shown for VZW and T-Mo 10x10). Any ideas on how else to interpret these numbers?

This may work.

25BW / 5MHz = 5

50BW / 10MHz = 5

100BW / 20MHz = 5

Mike have you found what the issue is with the Vibrate and Sound Alerts on Lollipop 5.0?

No, you get a $15 credit if you sign up for a $20 lease.

 

Sent from my Sprint LG G3

Ok thanks.

What does "$15 service credit eligible lines" mean?

We are on ED1500 and my number is out of contract with a Nexus 5 and it shows the service credit on the letter they sent by FedFx.

Does it mean we get $15 credit each month on my line without changing anything?

Before 5.0 update

I got about 2:30 to 4:30 of SOT

After 5.0 update

I get about 3 to almost 5 of SOT

Different usage patterns, but overall I get better battery life from Lollipop.

The only problem I have is the GPS. I would advise not to do mapping in a big area like Dallas, TX

Mike - 

 

From your testing/coding of the neighboring cell feature, how confident are you that every signal/PCI that shows up in the neighbor cell list is an actual live signal and the PCI for it is accurate?

 

the reason i'm asking is i have seen quite a few PCI show up in the neighbor cell list that don't match any PCI that we have recorded. I've spent the last 3 weeks driving around re-logging the PCI of the towers in my area to make sure they were accurate and hadn't changed since we first logged them. after doing this i'm still seeing PCI that don't exist in our spreadsheet.

...

PCI 496 is not in our spreadsheet, and not only is it not in our spreadsheet but at the -99 signal its showing any tower that would be close enough to show that signal i've reconfirmed the PCI for.

 

and its not just a one time thing either, i've seen that PCI show back up driving through the same area on a different day.

 

See this post

I have found a total of 14 sites that is not in our spreadsheet for about 40 miles.

Like Tim said, the app reports what the phone is seeing. I have all of my nearby sites noted, and still see a "rogue" PCI on occasion. It could be that you haven't yet connected to that specific sector on that specific band, so you don't have that specific PCI recorded yet. Or your device can see it, but for whatever reason it is not accepting connections. Many possibilities. Again, as Tim said -- it's showing you what the phone sees. Just because you've never hit it doesn't mean it's not out there.

 

As far as GCI goes, it might not be an Android limitation, it might be by design; I have no idea if the LTE neighbor cell protocol includes any more information than Android is offering. It's a moot point though, I can only show what Android decides to collect.

 

-Mike

Mike, I am starting to question the accuracy of the neighbor cells on my Nexus 5.

Because it is showing several different towers I have no idea where they are unless they are 15 to 30 miles away.

 

With two days of watching the neighbor cells I have found 14 different towers. 13 of which are unknown and 6 are possibly known 25 to 50 miles away.

(74), 243, (412)    known

7, 176, (345)        possibly

111, (280), (449)  possibly

(42), 211, (380)

(81), 250, (419)

167, (336), (505)

(26), (195), 364

(136), (305), 474

(22), 191, 360      possibly

89?, (258), (427) possibly

(116), 285, (454) possibly

142, (311), (480)

128, (297), (466) possibly

(16), 185, (354), (523)

And to add some info there is 2 towers in about 30 miles I do not have the PCIs for.

Mike, I am starting to question the accuracy of the neighbor cells on my Nexus 5.

Because it is showing several different towers I have no idea where they are unless they are 15 to 30 miles away.

If only Android would report the GCI.

I love the neighbor cells I could run the battery down watching it.

Now if SCP could know the difference between B25 and B26 sites in the neighbor list.

Can you tell that there is no optimization done yet?

Done.

Email from ARRL about ATT WCS band.

In comments filed in response to an AT&T Mobility Petition for Rule
Making seeking a new air-to-ground communications system on 2.3 GHz
Wireless Communications Service (WCS) spectrum, the ARRL has once
again asked the FCC to elevate the Amateur Service allocation at
2300 to 2305 MHz from secondary to primary. The Petition (RM-11731)
asked the Commission to authorize an LTE-based in-flight
connectivity service in the WCS "C" and "D" blocks (2305-2315 MHz
and 2350-2360 MHz, respectively) for airlines and airline
passengers. AT&T has asserted that restrictions on out-of-band
emission and power limits to protect adjacent-band users make the
use of the C and D blocks problematic. The wireless provider asked
the FCC for rule changes to permit deployment of its service "using
currently fallow spectrum" while also "preserving adequate
interference protection to users of adjacent bands."

"Notwithstanding this broad and nebulous claim, there is no showing
anywhere in the four corners of the Petition that the proposed rule
changes would permit any continued Amateur Radio operations on a
secondary basis in the shared A block (2305-2310 MHz)," the ARRL
commented on September 22. More to the point, the League said, there
is no showing in the Petition that Amateur Radio operations in the
adjacent 2300-2350 MHz band would be protected from increased
out-of-band emissions, if the FCC were to implement the changes
requested.

The League asserted in its comments that the FCC has, to date,
"failed to protect Amateur Radio operations at 2300-2305 MHz from
WCS out-of-band emissions." The ARRL said the band is "regularly and
substantially utilized by radio amateurs" for weak-signal,
long-distance communication and, only by circumstances - a lack of a
primary occupant - has it been able to enjoy that segment as a de
facto primary user.

"The Commission's rules are quite clear that WCS licensees enjoy no
entitlement to disrupt adjacent-band radio service operations," the
ARRL commented. But, the League pointed out, previous FCC actions to
expand mobile broadband devices left 2300-2305 MHz vulnerable to
increased out-of-band interference that would be difficult or
impossible to mitigate. The ARRL said amateur stations operating in
the 2300-2305 MHz band would be unable to avoid interference from AT
and T Mobility's proposed system, and that the FCC has refused to
clarify the obligation of WCS mobile providers to avoid interference
to Amateur Radio operations there.

The ARRL objected to what it called the FCC's "practice of making
allocation decisions which place incompatible uses in close
proximity to amateur stations and then place on the amateur
licensees the burden of avoiding the interference."

"It is obvious that the result of the AT&T Petition will be a
virtual preclusion of amateur access to the 2305-2310 MHz segment,"
the ARRL's comments continued. "A ubiquitous air-to-ground system
which operates at and above 2305 MHz will clearly render the
secondary allocation status of that segment a virtual nullity."

The ARRL asked the FCC to recognize Amateur Radio's "de facto
primary status" at 2300-2305 MHz and to elevate that segment from
secondary to primary for amateurs. It further called on the
Commission to "clarify the obligation of WCS licensees in all
contexts to protect the adjacent-band Amateur Service operations at
2300-2305 MHz from harmful interference." Finally, the League
requested that AT&T provide "a complete technical compatibility
showing and interference analysis" that would demonstrate
compatibility between its proposed service and amateur operations at
2300-2305 MHz.

 

Hey guys so I am trying to figure out where a certain tac is located at.  ...

 I think its from Seattle though because its TAC is different from any others over here on the Kitsap side.

 

The tac is 23323

Western Washington Market.

 

I will be listing my TAC's that I've found here later tonight.  Thanks for the help.

Market: West Washington

 

City: Seattle (white center neighborhood)

 

Band:25

 

TAC:23323

 

Thanks for the info EmeraldReporter!

I updated the sheet with the city info.

Include the infrastructure vendor:  Alcatel-Lucent, Ericsson, Samsung, or Nokia.  The 50 offset between band 25 and band 26 seems to be consistent only within Ericsson markets, if that.

 

AJ

Is Alcatel-Lucent and Samsung doing their own B41 upgrades and Nokia doing Ericsson markets?

I am working on a spreadsheet for all TACs.  It is a work in progress.

Trying to figure out the best way to show all markets.

Please PM me any ideas to improve it and I will do the best I can.

Mike, I would hate to keep you busy with SCP but with Google I/O you may have to add Android Wear  notifications to your app.

Still waiting for the OTA here as well. I thought the rollout was to be completed by today. In that case I guess I just might be last on the list. Story of my life!

Don't feel bad, I'm still waiting too.

Do not give up hope I just got the update.

I was in Mesquite, TX on 6/7 and connected to B41 with the 4.4.2 / .23 radio.

I think the only reason I connected to B41 is because I lost LTE and my band priority (B41 1, B25 2, B26 3).

SignalCheck LTE log B41 is near the bottom of the log.

After watching my phone's behavior on .13, I think I have a theory as to what is going on with the radio, and it has to do with ecfsb and Band 26 (and possibly Band 41). I believe what is happening is that our phones connect fine to Band 25, which doesn't have a csfb problem.  However, in scanning other bands and measuring capacity, it switches over to Band 26, either after a few minutes, or 30 minutes. When trying to connect to Band 26, it encounters the csfb problem with that particular band, and goes to 3G and stays there, which is consistent with what I've seen with csfb issues on Band 25.

 

This would explain why we don't see the "3g camping" on .15, the radio that is much more tolerant of csfb issues. This would also explain why we didn't see the issue on .23, which never could connect to Band 26. 

 

This would further explain why the "3g camping" is sporadic and not that predictable, because it only occurs when the phone attempts to connect to Band 26 after measuring capacity.

 

EDIT: this would also explain why some folks who used to have the problem, are not having the problem any more, because Sprint has fixed the csfb issue.

 

Am I way off base?

 

Also, and perhaps this is a question for the csfb thread, but does Sprint have a way of detecting csfb problems other than manually testing every tower? Or do I need to alert Sprint to my problems? (of course a low level CSR will have no idea what the problem is).

I have had the B26 CSFB issue on my home site for 1 month now on 4.4.2 / .23 radio. So for about 1 month I have been on 3G 99.8% of the time when at home.

I do not have any problems with B25/B26 on 3 other sites.

I get B25 and B26 on the .23 radio at most sites.

But my home site has B26 with eCSFB issues(Ericsson market) and no issues with B25. My phone connects to B25 for 1 to 5 secs some times for 2 min then it will go back to 3G it depends on where the phone is.

If it has to go to B26 for any reason it will go back to 3G.

So most issues with .13 radio is B26 eCSFB. I am not saying all is due to eCSFB but some/most are.

Same for me in East Texas on one site that has B25 and B26 since early April. If you do not have B26 do a PRL Update and it will search for B26.

 

After a reboot do a PRL Update again.

If I don't do a PRL Update my phone never connects to B26.

My phone is not modified in any way.

I'm in new Orleans and I get b26 all over with the 23 radio. And a prl update always gets it scanning for b26 if I need to give it a jump start.

 

Sent from my Nexus 5 using Tapatalk

Same for me in East Texas on one site that has B25 and B26 since early April. If you do not have B26 do a PRL Update and it will search for B26.

After a reboot do a PRL Update again.

I think you are reading more into the Site Hint feature than is really there. The only difference between Sprint 1 and Sprint 3 is what character position the sector is derived from; either position "1" (the last character of the hex BID) or "3" (the 3rd-to-last character of the hex BID). So 1299, 129A, and 129B will all show "Sector 2" if you have Sprint 3 selected, or "Sector 9/A/B" if you have Sprint 1 selected.

 

The site note feature is completely separate from the site hint display. Every unique SID+NID+BID trio has its own note. There is no way for the app to know if BIDs are located at the same site, so you will have to save a note for each sector. This also means you need to duplicate the efforts for 800 SMR, although I'd like to find a solution for that, since I believe the NID+BID are the same for PCS and SMR.

 

Each market assigns BIDs differently; for example, in my area, sectors on the same site have wildly different BIDs, with no identifiable pattern. Unlike the LTE GCI, where the first 6 characters indicate the site, there is no similar identifier for 1X or GSM.

 

Hopefully that clears things up for you.. or if I totally misunderstood your question, let me know.

 

-Mike

Ok.

The BID is different for PCS and SMR here.