Jump to content
mikejeep

SignalCheck - Android app to monitor your 2G/3G/4G LTE signal strengths

Recommended Posts

56 minutes ago, Flompholph said:

Triband.

Triband antenas have been found where sprint puts what we guess could be their 4th carrier GCI ending. 

 

Didn't though they were doing that here.  So that's good

Share this post


Link to post
Share on other sites
5 minutes ago, jthawks said:

Didn't though they were doing that here.  So that's good

So should I investigate this? 

Share this post


Link to post
Share on other sites
51 minutes ago, jthawks said:

Didn't though they were doing that here.  So that's good

 

45 minutes ago, jthawks said:

So should I investigate this? 

This is standard second carrier for Samsung tri-band sites. As Denver is a Samsung market, it is to be expected.

Share this post


Link to post
Share on other sites
On 4/9/2018 at 4:25 PM, Dkoellerwx said:

This is standard second carrier for Samsung tri-band sites. As Denver is a Samsung market, it is to be expected.

I don't know if it's definitely the second carrier (that should be 03/04/05), but it is an additional carrier that varies by market.

-Mike

Share this post


Link to post
Share on other sites
6 minutes ago, mikejeep said:

I don't know if it's definitely the second carrier (that should be 03/04/05), but it is an additional carrier that varies by market.

-Mike

Based on the EARFCN and it's from the Denver area, it is the second carrier. As far as I've seen, that is the typical ending for a second carrier tri-band antenna site in a Samsung market?

Share this post


Link to post
Share on other sites

I have received a lot of messages over the past 3 weeks regarding improper LTE band identification for T-Mobile users. There is an Android bug that causes EARFCNs assigned to newer LTE bands (>46) to be reported incorrectly, such as Band 66 and Band 71. SignalCheck is showing Band 2/3/5/6/7/etc. because that is what the OS is reporting.

For more details, please see this bug report; I encourage everyone to 'star' it and/or adding your own report to try getting it more attention: https://issuetracker.google.com/issues/37136986

I am trying to implement a workaround that will at least help T-Mobile users until Android fixes the issue.

-Mike

 
  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, Dkoellerwx said:

Based on the EARFCN and it's from the Denver area, it is the second carrier. As far as I've seen, that is the typical ending for a second carrier tri-band antenna site in a Samsung market?

I have Samsung B41 second carriers as 03/04/05, but perhaps things changed? The "TB" indicator was implemented (and has been discussed a few times) because it wasn't consistently deployed as a specific carrier.

-Mike

Share this post


Link to post
Share on other sites
2 minutes ago, mikejeep said:

I have Samsung B41 second carriers as 03/04/05, but perhaps things changed? The "TB" indicator was implemented (and has been discussed a few times) because it wasn't consistently deployed as a specific carrier.

-Mike

Yes, on a normal 8T8R site, 03/04/05 is the normal second carrier. On 4T4R tri-band antennas in Samsung markets, 09/0A/0B has been used fairly regularly. I do not know off the top of my head what is done with the 3rd carrier on the tri-band antenna sites (normal 8T8R being 06/07/08, which is already covered).

Share this post


Link to post
Share on other sites

Mike,

1) As indicated previously, in my area (DC) which I believe is a Samsung Clear market, 03/04/05 are third carrier, but SCP currently doesn't note it as anything other than standard B41.

2) Yesterday, I finally managed to send you diagnostics showing "LTE" without a band indicator while connected to a Clear site.  I sent it having watched it not have a band indicator for more than 30 seconds.  Hopefully you got it and maybe it'll tell you something you didn't already know about the issue.

3) I don't yet have a B71 phone, though once a cheap Motorola one comes out, I plan to replace my T-Mobile 700 phone with one.  What kind of work-around are you considering?  Perhaps it could make sense to allow people to select which bands their phone actually supports or which bands they expect to see so you could work around obviously-incorrect data, even if it were in some kind of hidden menu.  (In my ideal world, there would be a hidden menu with lots of advanced functions to tweak the behavior of SCP in ways the average user may find unhelpful or confusing.  Like forcing all LTE to be identified as LTE 700 on my phone that is locked to 700.)

4) Is there any chance you could add a third mode to the neighbor cell notes beyond matching to PLMN and not matching to PLMN?  I'd like to merge my four SCP databases together (Verizon, AT&T, T-Mobile, and Sprint/USCC) but if I do that, then on my Sprint/USCC phones with the PLMN matching disabled, I'll get a bunch of neighbor cell notes that are clearly not correct since they'll match non-Sprint values.  And, of course, if I enable PLMN matching, then if I'm on Sprint, I'll miss Clear notes, etc.  It would be nice if there were a "Sprint" mode that matched only to PLMNs associated with Sprint when connected to a Sprint-associated network.  For example, if connected to PLMN 310120, have it match also PCI values for 311870 and other Clear PLMNs, but not to other PLMNs.  Or if connected to 311870, match to 310120, etc.

- Trip

Share this post


Link to post
Share on other sites



Yes, on a normal 8T8R site, 03/04/05 is the normal second carrier. On 4T4R tri-band antennas in Samsung markets, 09/0A/0B has been used fairly regularly. I do not know off the top of my head what is done with the 3rd carrier on the tri-band antenna sites (normal 8T8R being 06/07/08, which is already covered).


Third carrier on triband sites (that use triband endings) has second carrier GCI endings. So:

Non-triband:
2nd carrier - 03, 04, 05
3rd carrier - 06, 07, 08

Triband:
2nd carrier - 09, 0A, 0B
3rd carrier - 03, 04, 05

I define second carrier as the middle earfcn, and third carrier as the highest earfcn.

Sent from my Pixel 2 XL using Tapatalk

  • Like 2

Share this post


Link to post
Share on other sites
On 4/11/2018 at 9:14 PM, Trip said:

1) As indicated previously, in my area (DC) which I believe is a Samsung Clear market, 03/04/05 are third carrier, but SCP currently doesn't note it as anything other than standard B41.

2) Yesterday, I finally managed to send you diagnostics showing "LTE" without a band indicator while connected to a Clear site.  I sent it having watched it not have a band indicator for more than 30 seconds.  Hopefully you got it and maybe it'll tell you something you didn't already know about the issue.

03/04/05 are coded as third carrier, and your report showed sector 00 which should have showed you regular B41. You are likely getting victimized by the bug that has been driving me insane for a couple of years where things go south when the PLMN changes on the fly. Some devices suffer more than others. Essentially the band stops appearing until the PLMN changes again.. something is getting hung up momentarily on the OS side, and SCP chokes on it. It's related to the glitch that causes the PLMN and GCI to fall out of sync when switching cells, which also wreaks havoc and creates duplicate (bogus) database entries. It's maddening and I have tried all sorts of hacks i in the background to address it -- and I will continue to try, because it's a priority.

 

On 4/11/2018 at 9:14 PM, Trip said:

3) I don't yet have a B71 phone, though once a cheap Motorola one comes out, I plan to replace my T-Mobile 700 phone with one.  What kind of work-around are you considering?  Perhaps it could make sense to allow people to select which bands their phone actually supports or which bands they expect to see so you could work around obviously-incorrect data, even if it were in some kind of hidden menu.  (In my ideal world, there would be a hidden menu with lots of advanced functions to tweak the behavior of SCP in ways the average user may find unhelpful or confusing.  Like forcing all LTE to be identified as LTE 700 on my phone that is locked to 700.)

I'm hoping to keep it simple.. essentially by checking if it's a T-Mobile connection, and if so, checking if it's a band that T-Mobile actually uses. If not, assume it's a glitch and add 65536 to the EARFCN. I've spent the past few weeks trying to bring SignalCheck Lite up to speed and I have to finish that first, but it's not going well since it's been 3 years since that was updated and a lot has changed since then.

 

On 4/11/2018 at 9:14 PM, Trip said:

4) Is there any chance you could add a third mode to the neighbor cell notes beyond matching to PLMN and not matching to PLMN?  I'd like to merge my four SCP databases together (Verizon, AT&T, T-Mobile, and Sprint/USCC) but if I do that, then on my Sprint/USCC phones with the PLMN matching disabled, I'll get a bunch of neighbor cell notes that are clearly not correct since they'll match non-Sprint values.  And, of course, if I enable PLMN matching, then if I'm on Sprint, I'll miss Clear notes, etc.  It would be nice if there were a "Sprint" mode that matched only to PLMNs associated with Sprint when connected to a Sprint-associated network.  For example, if connected to PLMN 310120, have it match also PCI values for 311870 and other Clear PLMNs, but not to other PLMNs.  Or if connected to 311870, match to 310120, etc.

Hmm, that's an interesting thought. It would only make sense for Sprint, since most other major providers stick with one PLMN.. I'll look into seeing how feasible that is. What device do you see Clear neighbors when connected to Sprint, and vice versa? My Pixel doesn't do that.

-Mike

  • Like 1

Share this post


Link to post
Share on other sites
On 4/15/2018 at 8:31 PM, mikejeep said:

03/04/05 are coded as third carrier, and your report showed sector 00 which should have showed you regular B41. You are likely getting victimized by the bug that has been driving me insane for a couple of years where things go south when the PLMN changes on the fly. Some devices suffer more than others. Essentially the band stops appearing until the PLMN changes again.. something is getting hung up momentarily on the OS side, and SCP chokes on it. It's related to the glitch that causes the PLMN and GCI to fall out of sync when switching cells, which also wreaks havoc and creates duplicate (bogus) database entries. It's maddening and I have tried all sorts of hacks i in the background to address it -- and I will continue to try, because it's a priority.

 

I'm hoping to keep it simple.. essentially by checking if it's a T-Mobile connection, and if so, checking if it's a band that T-Mobile actually uses. If not, assume it's a glitch and add 65536 to the EARFCN. I've spent the past few weeks trying to bring SignalCheck Lite up to speed and I have to finish that first, but it's not going well since it's been 3 years since that was updated and a lot has changed since then.

 

Hmm, that's an interesting thought. It would only make sense for Sprint, since most other major providers stick with one PLMN.. I'll look into seeing how feasible that is. What device do you see Clear neighbors when connected to Sprint, and vice versa? My Pixel doesn't do that.

-Mike

Mike,

I didn't mean to conflate the first two items.  In the first, when I'm connected to Clear B41 third carrier on sectors 03/04/05, I'm not seeing the "3" next to it.  That's what I was trying to say.  I would love if this could be corrected, since it's hopefully a small change.  I'll try to send you a diagnostic showing it, but here's a picture from my log:  https://imgur.com/a/7zw72

I separately sent you the data on the missing band indicator because you said it was causing you a problem that you were having trouble tracking down, but I had been unable to send you diagnostic data on it previously.  I finally tried and successfully sent you the data without getting an error message.  I was hoping it helped you track down the issue, as it was sitting there for a very long time with no band indicator.  Same thing happened yesterday, actually, on a different site.  In that case, it lasted for a long time, measured in minutes.

Sounds like an interesting fix, though I suspect you'll have some Band 66/Band 2 overlap.  For example, if T-Mobile held AWS-1 A-block, that would be EARFCN 66586, and 66586-65536=1050, a valid Band 2 EARFCN.  Not sure what you would do about that.

Yes, I agree it would have to be Sprint-only.  I think most of the phones I've had since moving to Sprint would show Clear and Sprint B41 in neighbor cells at the same time.  (LG G6, LG G5, Samsung S5.)  They do/did not, however, show PCI values for US Cellular or other networks.  I'll confirm and let you know for certain.

- Trip

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Trip said:

Yes, I agree it would have to be Sprint-only.  I think most of the phones I've had since moving to Sprint would show Clear and Sprint B41 in neighbor cells at the same time.  (LG G6, LG G5, Samsung S5.)  They do/did not, however, show PCI values for US Cellular or other networks.  I'll confirm and let you know for certain.

Mike,

Confirmed via picture.  https://imgur.com/a/ZWewf  I'm connected to a Clear site with two 8T8R sites appearing in the neighbor cells.  Couldn't get diagnostics before it dropped back to B26 on the DAS though.  I'm in too much pain to walk back to the window and try again for diagnostics.

- Trip

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
On 4/11/2018 at 8:22 PM, mikejeep said:

I have received a lot of messages over the past 3 weeks regarding improper LTE band identification for T-Mobile users. There is an Android bug that causes EARFCNs assigned to newer LTE bands (>46) to be reported incorrectly, such as Band 66 and Band 71. SignalCheck is showing Band 2/3/5/6/7/etc. because that is what the OS is reporting.

For more details, please see this bug report; I encourage everyone to 'star' it and/or adding your own report to try getting it more attention: https://issuetracker.google.com/issues/37136986

I am trying to implement a workaround that will at least help T-Mobile users until Android fixes the issue.

-Mike

 

Yeah mine is reporting B3 for T-mobile. I am definitely in the US and it should be reporting B2.

Edited by bigsnake49

Share this post


Link to post
Share on other sites
6 minutes ago, bigsnake49 said:

Yeah mine is reporting B3 for T-mobile. I am definitely in the US and it should be reporting B2.

You're probably getting Band 66 instead of Band 2 but see Band 3 instead.

  • Like 2

Share this post


Link to post
Share on other sites
4 minutes ago, greenbastard said:

You're probably getting Band 66 instead of Band 2 but see Band 3 instead.

Very possibly! My phone supports Band 66.

  • Like 1

Share this post


Link to post
Share on other sites

My phone when it attaches to B66 here in Cincinnati, it shows up as B3 (1800mhz) as well. The only app that gives an accurate reading is Cellmapper at the moment.

Very possibly! My phone supports Band 66.


Sent from my SM-G965U using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites

I won't speak for Mike, but it sounds like they're specifically talking about network traffic, as in what websites you're connecting to, rather than which cell tower you're connected to.  That information comes from an actual Android API which requests permissions, and what they're talking about here is direct access to /proc/net in the file system, which apparently does not.

That said, it's vague enough that I, too, would like to hear more information on it. 

- Trip

  • Thanks 1

Share this post


Link to post
Share on other sites
9 hours ago, jefbal99 said:

I saw that article as well and I probably turned white as a ghost for a few moments of panic.. but after reading it, and poking around a bit more, I do not think this will impact SCP at all. As Trip stated it looks like it's closing off direct access to /proc/net, which isn't anything I use. But, we won't be certain until P gets closer to release.

-Mike

  • Like 2

Share this post


Link to post
Share on other sites

On my Essential running Android P. Seems to have some extra info.

a0a8dfc6d322320ef2d53fd081d5f16c.jpg

 

b8249cd9d63611addf671191298b8c5e.jpg

 

Sent from my PH-1 using Tapatalk

 

 

 

 

  • Thanks 1

Share this post


Link to post
Share on other sites
9 minutes ago, bakedc4 said:

On my Essential running Android P. Seems to have some extra info.

 

Sent from my PH-1 using Tapatalk

That looks like the normal amount of info?

Share this post


Link to post
Share on other sites
That looks like the normal amount of info?
Unless I'm having serious memory issues (entirely possible, way too much work and not enough sleep) the neighbor cells only showed up if they were in the same band and all others showed as unknown on 8.1

Sent from my PH-1 using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, bakedc4 said:

Unless I'm having serious memory issues (entirely possible, way too much work and not enough sleep) the neighbor cells only showed up if they were in the same band and all others showed as unknown on 8.1

Sent from my PH-1 using Tapatalk
 

Ah, depends on device. Some changes have been made that now shows other bands in the neighboring cells, even for devices on Oreo. 

  • Like 2

Share this post


Link to post
Share on other sites
2 hours ago, Dkoellerwx said:

Ah, depends on device. Some changes have been made that now shows other bands in the neighboring cells, even for devices on Oreo. 

Yeah I am seeing two B41 and one B25 on my neighboring cells S9+ here.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

    • By Paynefanbro
      I recently went on an 8 day cruise from NYC to the Caribbean that stopped in Turks and Caicos, Puerto Rico, and the Dominican Republic. My first stop was Grand Turk and there I opted for the free roaming. My S9+ automatically connected to Flow's (Cable & Wireless) LTE network where I received speeds of around 120kbps on average with boosts of up to 150kbps. Something worth noting is that on speed tests, the server prefers to default to Sprint's Miami server as opposed to local servers. Speeds were more than adequate for any amount of web browsing and honestly felt much faster than in reality. It helps that using Chrome will save you data by not loading pictures on certain sites unless you click them.
      In Puerto Rico, I connected to Band 13 on the way into the port in San Juan but once I was in the city, my phone never left Band 41. While the phone was usable, speeds remained significantly lower than what I've come to expect from 3xCA in the mainland U.S. Data speeds peaked at around 25-30Mbos but on average were in the 5-10 Mbps range even on LTE+. Signal remained strong everywhere though. 
      Finally in the Dominican Republic, I entered in Amber Cover which is in Puerto Plata. My phone latched onto a weak Band 2 LTE signal in the port from Altice (called Orange Dominicana in SignalCheck). I had trouble loading pages though. Once off of the ship and out in the open, I had a much stronger signal which allowed me to browse the internet without a hitch. Because it was the last day of my trip, while at the beach I decided to purchase the 24 hour high speed pass for $5. My speeds went from 120kbps to 65Mbps in less than 5 seconds. In some areas speeds were slower, particularly at the port where it struggled to break 2Mbps. Now, back on the boat my phone is flipping between weak Band 4 LTE and overloaded Band 5 HSPA+ from Claro (called Verizon Dominicana in SignalCheck Pro). Here is the difference in speed from before and after purchasing the high speed pass. 
    • By S4GRU
      by Jeff Foster
      Sprint 4G Rollout Updates
      Tuesday, January 31, 2012 - 7:46 PM MST
       
      Since last fall, there had been talk of a Samsung Galaxy Nexus launching on American carriers other than Big Red. Sprint has finally announced several weeks ago that it is the another vendor slated for release in the U.S. Suffice to say, many of us out there, especially those adverse to heading to Verizon and paying its premium prices, are excited about the impending release.
      The good news is that Google could be working on an updated version of the Galaxy Nexus. It has unofficially been dubbed the Galaxy Nexus Plus. There is much anticipation that it will be released before Sprint turns on LTE this summer. It’s not the first time an OEM has refreshed a device and re-released it to the market place, which works to our advantage. It’s rumored that the new Galaxy Nexus will have either a 1.5 or 1.8 GHz Texas Instrument OMAP4670 dual core processor. This would be a significant upgrade from the 1.2 GHz dual core processor found in the current Verizon version.
      We don’t know anything about official specs, but it’s also rumored to have an 8 MP camera. This is a noteworthy upgrade to the 5 MP shooter on the Verizon model (which has been lauded by many techies). We already know that the Sprint model will come installed with Google Wallet, per previous announcements. Some rumors also point to a beefier battery as well. The phone should have all the other features that’s on the current Galaxy Nexus, so now all we have to do is wait.
       
       
      Source: http://androidandme....era-on-the-way/
    • By S4GRU
      by Rick Layton
      Sprint 4G Rollout Updates
      Monday, June 25, 2012 - 4:27 PM MDT
       
      As technologies advance, the equipment to use the technology must advance as well. With the upcoming release of 4G LTE in our area (Houston), new equipment will be required to be able to use it. Although Sprint will have numerous data devices to handle the usage by the end of the year, only the Sprint Tri-Band Modem will be available at the rollout of the 4G LTE service.
      Due to the enormous dependence my business has on accessing data in a mobile environment, plus the great increases in data speed available with 4G LTE, this makes getting access to 4G LTE imperative to me. I depended heavily on the Sierra Wireless data devices when I started this business 7 years ago for my source of a reliable method of mobile data transmission. This relationship continued on until the release of the original Hotspot with the 4G service in my area.
      At one point, I was so displeased with past models, that I had sworn I would never buy another Sierra Wireless device as long as I live. This conclusion was reached after having numerous issues with previous hotspot models. There were so many problems that it seemed as if the device was never even tested on the networks it was to be used on. Also Sprint actively blocked reviews of the device, likely to not hinder sales in spite of the problems.
      My need for a new device with both WiMax and LTE capability outweighed my outright dislike of Sierra Wireless products. I proceeded against better judgment, and the Tri-Band modem was ordered even though the possibility of getting a substandard unit once again was always at the forefront of my mind.
       
      On with the show
       

      The official part number of the Tri-Band Modem is 803S. Along with the modem, I also ordered the SSX7077-V desktop cradle. I had to dig through a lot sites to find the information necessary to make this decision for my business. Much to my surprise, even though I was told the cradle was not available yet, I got a Sprint telesales person who was able to use the part number and find they had it in stock.
      Upon arrival I unpacked the unit and cradle...while holding my breath. The device that came out of the box was a pleasant departure from the previous Hotspots I had owned. Above is a picture of the device as it was shipped with all components. There was a small user guide as well but to get the real instructions the user guide must be downloaded from Sprint.
       
      Gone was the one piece blow molded plastic case which allowed no air circulation and caused the prior Hotspots to overheat quickly. Although the display is still too small for my aging eyes (it is actually the same display size as prior units) the change to the case makes it much easier to see in the interior of my van where the device will mostly be used.
      In this picture of the front you can see that there is a new button arrangement as compared to the older Hotspots. Also in the picture is the USB cable for use with the charger or to connect a computer, the AC to USB adapter, the battery and the battery cover. I opened the cradle, which was surprisingly inexpensive, and was delighted to find an additional AC to USB adapter which meant the cradle could be left in place without having to move the adapter around.
      As you look at the modem from the side you can see the antenna ports (the covers are open), the USB connector in the middle and the slot for the memory card. The round hole just right of the left antenna port is the reset button for the unit.

      Here is the same view with the battery and cover installed. Notice that the SD card slot is covered by the
      battery cover.
       

      The opposite side has two switches. The one on the left is a WPS setup button while the one on the right is a slider to mute the unit.
       

       
      The unit sits nicely in the cradle and looks to me to be a solution to help keep the USB port for the charger/interface cable from failing. This has been a major issue with the prior Hotspots. The case of the unit also helps support the USB port to take some of the load off of the circuit board.
      It took quite a bit of digging on the Sierra Wireless site to find out that the antenna ports are for the 4G WiMax band only. The cradle contains 2 5dbi omnidirectional antennas to allow full use of the WiMax network architecture.
       
      Initial testing

      The initial testing of the unit looks promising. The antennas in the cradle for 4G WiMax actually seem to get 3 – 5dBm gain in all conditions tested. The new unit has the ability to search the other bands for signals while staying connected. This allows less downtime between band changes. I notice a lot less disruption when switching bands.
      This unit has better reception on 3G and 4G WiMax than the previous hotspots and even the U600 USB modem I use as well. 4G WiMax is able to connect quickly even at 10% and the cradle has improved stability of WiMax and decreased ping times. For a short time I had access to Sprint 4G LTE as they were testing the towers in my area. The speeds were incredilbly faster. A 10% 4G LTE signal averaged 8.12Mbps download and 1.85Mbps upload. An 80% signal was able to get 35.8Mbps down on my best test and 22.1Mbps up.
      The upload speeds was very unexpected, and much higher than Sprint LTE smartphone devices have reported. This is likely due to much stronger transmit capabilities of the hotspot. I also discovered that when the modem is tethered the cable limits the bandwidth to approximately 20Mbps total speed. It will be interesting to see how it works in the 12 to 14 hour days of hot Houston Weather.
       
      First week in the field
      The Tri Band Modem got pressed into service a little quicker than planned, as my main unit went down with a bad transmission and the U600 USB modem with a Cradlepoint that was in this unit appears to have been damaged by the wrecker’s radio which runs on the edge of the WiMax frequency at 5 watts. The units have been sent in to determine cause of failure and for repairs but I think next time I will make sure all electronics are powered off before getting that close to a transmitter (OUCH!!).
      I am running the same routes in a rental van with the Tri-Band Modem that I normally use the other units on. There is less downtime in the signal gaps I am familiar with and areas where I have had signal problems in both 3G and 4G WiMax are much improved. I have yet to encounter any more 4G LTE signals but am looking forward to the service coming online soon. The unit seems to be running hotter than I would like with a fully charged battery but is actually cooler that the previous Hotspots. The temperature is supposed to soar over the next few days without the cloudiness we have had this past week. So it will be interesting to see if the overheating problems of previous models still occur.
       
      Week 2 – The True test
      The unit is getting worked really hard this week with temperatures outside up near 100 degrees. The GPS is useless with this kind of sun load as the unit will overheat if left in direct sunlight (as the instructions state) in about 20 minutes. The good news is that this is about twice as long as my original Hotspot will last. How anyone can make a unit that requires a clear view of the sky for GPS but can’t handle sunlight is beyond comprehension. A quick check of the Tri-Band’s temperature specs shows that the unit is only rated for 95 degrees. The prior Hotspot was rated well above the century mark but couldn’t even handle 90 degrees for any length of time. The crappiest laptop on the market will handle 105 degrees plus all day long. The true test will be my afternoon calls when the temperatures are high. Battery life has been about 8 to 9 hours which is far better than the prior Hotspots.
      The unit started overheating one afternoon. I can’t say I’m a bit surprised at that, but what is surprising is that it will run steadily as long as the air temp is below 98 degrees. This is a first for Hotspots as they always overheated well before the rated temperature spec. The bad news is the crappy overheat shutdown doesn’t turn off the unit before damage starts to occur, nor does it turn the unit off completely.
      Removing the battery cover seems to help air circulation and overheating some. The button lights are flickering after one overheating but the unit seems to be working fine other than this. It will be interesting to see what happens when it really gets hot here.
      According to the specs 4G LTE takes the least amount of wattage to run so it may not overheat as fast when using 4G LTE. I had the chance to try the modem in the old school 3G EVDO mode as one of my locations is 40 feet underground and that is all that is available at this location. I shut the unit down after 30 minutes as the unit was so hot you could barely handle it even though the temperature underground is around 70 degrees. I would not recommend trying to use this for any length of time if you want the Tri-Band to not overheat!!
       
      My Opinion
      Although Sierra Wireless has made some major improvement in the 3rd generation Hotspot, this is still a unit for the casual user. It is not designed to handle heavy use or outdoor summer temperatures for any length of time. It will be going in my climate controlled cabinet to protect it from the heat next week. I will let you know how it works when the temperature stays below 85 degrees. The improvements in connectivity, reception and stability are worth the investment. As long as you know and adjust your usage for the limitations of the unit.
    • By pyroscott
      Sprint Nextel revealed their second quarter 2012 corporate earnings in a conference call to their investors today and S4GRU was covering for news on Network Vision.
      Network thinning of the iDEN network is complete, taking 1/3 of Nextel towers off air. The Nextel network was built to support 20 million subscribers, but was only supporting 4.4 million subscribers, so it could easily be thinned without [much] noticeable change in street coverage. Sprint also converted 60% of the Nextel subscriber loss into their Sprint subscriber base. Interestingly, they stated that Verizon has been the biggest poacher of subscribers leaving Nextel, grabbing 50% of former subscribers in the last 4 1/2 years. In that same timeframe, Sprint has grabbed 25%, AT&T 20% and T-Mobile 5%.
       
       
      On the Network Vision topic:
      4 additional cities will launch, including Baltimore, by the end of August.*Edit* Cities were disclosed VIA press release following the conference call. They are:
      Baltimore, MD Gainesville, GA Manhattan/Junction City, KS Sherman-Denison, TX  
      Over 2,000 sites are currently online with 12,000 sites to be online by the end of the year
      Network Vision towers are seeing 10-20% additional voice minutes usage per tower, overnight after activating Network Vision. This will equal roaming savings for Sprint, and ESMR will only increase that savings.
      CEO Dan Hesse confirmed that Sprint will be releasing the Motorola Photon Q "in the very near future." It will be a QWERTY slider "with robust business and consumer features." It will also be sporting world phone capability.
      Several hundred Network Vision sites are waiting for backhaul, and will turn on when the backhaul is installed, several hundred more sites have birds nesting on them and Sprint won't be able to turn them on until the birds leave, according to the conference call.
      Sprint sold 1.5 million iPhones during the quarter, even though other carriers saw slowing of sales with rumors ramping up that the new iPhone would support LTE. 40% of the iPhone sales were to new customers. They also stated that iPhone customers require less customer support and are expected to churn less than customers on other phones.
      Mr. Hesse confirmed that Sprint is not looking to change plans in the near future.
      Things are looking up for Sprint. This quarter saw their highest ARPU and their lowest churn rate to date. They posted a larger loss than Q1, but beat their revenue goals for Q2. For more detailed financial information, check the source link below.
       
      Source: http://investors.spr...spx?iid=4057219
      http://finance.yahoo...-141200985.html -Thanks to S4GRU sponsor marioc21 for finding this link!
    • By lilotimz
      Ericsson RRUS31 B25 + RRUS11 B26
      These are the newest and greatest remote radio units to come from Ericsson. 

      The new Ericsson RRUS31  B25 should be fairly distinctive compared to the earlier RRUS11s and now the RRUS12s being deployed by ATT and Verizon. One of these new RRUS31s can do the job of two earlier RRUS11s thus reducing deployment costs for Sprint and complexity in deploying new sites and making it easier for users to spot as there are now 4 jumpers coming out of one RRUS31 rather than two from each RRUS11 that Ericsson originally deployed. 

      All future deployments will be utilizing the new Ericsson RRUS31s. In addition Ericsson are sending crews to their original deployments and swapping out older RRUS11s for these new RRUS31s due to the aforementioned fact that one RRUS31 can do the job of 2 RRUS11s. Weight savings will be significant at sites where there are 4 or 5 RRUS11 B25s that can be replaced by one or 2 RRUS31s. The Ericsson RRUS31 deployment project is known as the 65 Mhz Project. 

       

      Ericsson RRUS11 B26 top and RRUS31 B25 bottom

       

       
      Ericsson High Capacity / 4x4/2 MIMO Deployment
      Note the additional antenna + PCS radio.
      Previously Ericsson utilized additional PCS radios and used RF combiners for high capacity setups where they utilized three or more PCS radios. This new setup will utilize a completey new antenna + radio set just like Samsung and run 4x2 MIMO on the LTE antenna / radio set. 
       

       

       

       
      Ericsson RRUS11 B25 [EOL'd] and B26
      A standard Ericsson Network Vision 1.0 site with 3 RRUS11s where two are dedicated to PCS and one to SMR.  

      This type of setup is no longer deployed or utilized in new sites. Existing sites will be slowly converted to newer RRUS31 B25 via the Sprint 65 mhz project. 


       
      Ericsson NV high capacity site [EOL'd]
      3 or 4 PCS RRUs are present for a total of 4 or 5 RRUS11s per antenna. 


       

       

       
      Close up of Antennas
       

       
      Ericsson cabinets 
      (center)



      All credit to those who took the photographs. They know who they are!
       
  • Posts

    • As you guys are all excited to find a 10mhz carrier, I found a small cell popping up in the storage room at my office. They replaced the power panel the other day and brought in fiber. Today they are putting the hole in the roof (and patching the leak around the boiler.)






      Sent from my iPhone using Tapatalk
    • Yesterday evening I had a notification that I had an update to "Carrier Services" in the Google Play store.  Any idea what this might be for, given that Google doesnt exactly give great descriptions of these sort of things.  I figured it must be something vaguely Sprint related, but wanted to see if anyone here had any insights.   Thanks!
    • So, this thread isn't very active... How is the radio on this bad boy?  The 3 XL will be delivered on Wednesday, :D.  Wish it had VoLTE out of the box, here's to hoping it will at least get it 🤞🤞🤞🤞🤞.
    • Here's AT&T Band 5 in Prince William County:  https://imgur.com/a/A6x70Xe I tried locking to Band 5 in other places a few times along the way and did not see any additional Band 5.  This site also has Band 14, on top of the displayed 17/2/4/30.  I wonder if it has Band 66 as well.  (Didn't think to check.) Couldn't get a good look at the antenna as it was getting dark and it was cloudy and I was on I-66.  Sorry. - Trip
  • Recently Browsing

    No registered users viewing this page.

×