Jump to content
mikejeep

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

Recommended Posts

It's been out for awhile. I've used it several times overnight full brightness. And my screen still looks like this

 

6f6e8fdf823cd7584023f9cafc0ac398.jpg

 

Sent from my LGLK430 using Tapatalk

Share this post


Link to post
Share on other sites

It's been out for awhile. I've used it several times overnight full brightness. And my screen still looks like this

 

AMOLED!  Hello, AMOLED...

 

 

AJ

Share this post


Link to post
Share on other sites

Signal check had issues identifying some 10x10 I hit in central IL.

 

d7ad3032ca7048fd4e3deeb83d1fc1d6.jpg

 

46fb02a6789c2d65fcda3fc213207f6a.jpg

 

17034ee2e1cc88f396c8fa612a543c45.jpg

Share this post


Link to post
Share on other sites

I'm seeing something new in my neighborhood and not sure what to make of what SignalCheck says it is. It's reporting it as 1xRTT which historically would mean horrible performance in the pre NV 2.0 days but my speed test is decent. What am I seeing here?

 

fba37ad41fff5e2fbb765c0436ac6324.jpg

 

609cdad5d8c71ae7fab12e57ff2f7cd8.jpg

Share this post


Link to post
Share on other sites

I'm seeing something new in my neighborhood and not sure what to make of what SignalCheck says it is. It's reporting it as 1xRTT which historically would mean horrible performance in the pre NV 2.0 days but my speed test is decent. What am I seeing here?

 

fba37ad41fff5e2fbb765c0436ac6324.jpg

 

609cdad5d8c71ae7fab12e57ff2f7cd8.jpg

That's the infamous android bug. Theres a lot of info on it earlier in this thread. You are truly on LTE, not 1x.

 

Sent from my Note 4

  • Like 1

Share this post


Link to post
Share on other sites

An update to CellMapper just came out, and it added a new root feature for Qualcomm devices to fetch the band information directly from the modem. No need to deduce it from the GCI. As a result, it also shows the band info for neighbor cells. It works using the "default" device on my Nexus 6P,  /dev/smd11

 

Might be worth investigating to see if this can be used to get more detailed information than what is provided by the Android API. And also to perhaps get around the 1x + LTE bug or stale data. 

  • Like 2

Share this post


Link to post
Share on other sites

 

 

Might be worth investigating to see if this can be used to get more detailed information than what is provided by the Android API. And also to perhaps get around the 1x + LTE bug or stale data.

I'm sure it can provide more detailed data, but since root is required to read it, I doubt it's worth the time and effort for Mike to implement. I doubt most people who use signal check have rooted devices.

  • Like 2

Share this post


Link to post
Share on other sites

I'm sure it can provide more detailed data, but since root is required to read it, I doubt it's worth the time and effort for Mike to implement. I doubt most people who use signal check have rooted devices.

 

That depends on the devices being used. For Nexus devices, it's easy to root, and you can even still accept OTAs while rooted using FlashFire.

 

Using /dev/smd11 also allows looking up the EARFCN, which is huge! The Nexus 6P for example doesn't have a functioning engineering screen, but using CellMapper I can now finally lookup the EARFCN (I verified it is reporting the correct values). I suspect CA status may also be available. If so, that would certainly be a valuable addition to SCP. I think a decent number of users would root to be able to have the EARFCN and CA status in their SCP logs. Especially those of us without functioning engineering screens.

 

Screenshot showing some of the data available: https://plus.google.com/+IvanZupan/posts/3aXM3Y6QCC2

 

EDIT: I watched that interface while CellMapper was running, and it appears to be issuing a standard modem AT command ("AT$QCRSRP?"). It looks like it returns a list of neighboring cells and their EARFCN:

root@angler:/ # dd if=/dev/smd11 bs=10000 count=100                            

$QCRSRP: 018,8763,"-095.20",117,8763,"-090.50",025,8763,"-099.20",000,8665,"000.00",000,8665,"000.00",057,40056,"-140.00",000,40056,"000.00"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.50",018,8763,"-095.80",025,8763,"-102.70",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.40",018,8763,"-094.80",025,8763,"-109.60",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.40",018,8763,"-095.80",025,8763,"-100.50",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.50",018,8763,"-094.70",025,8763,"-108.00",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.70",018,8763,"-094.40",025,8763,"-108.20",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.60",018,8763,"-095.70",025,8763,"-107.80",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.90",018,8763,"-094.00",025,8763,"-099.50",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.50",018,8763,"-094.70",025,8763,"-099.90",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-093.80",018,8763,"-094.30",025,8763,"-101.30",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-093.50",018,8763,"-095.50",025,8763,"-097.40",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.90",018,8763,"-093.30",025,8763,"-101.80",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-094.00",018,8763,"-094.30",025,8763,"-108.80",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
AT$QCRSRP?
$QCRSRP: 117,8763,"-092.90",018,8763,"-095.00",025,8763,"-096.00",465,8665,"-097.70",223,8665,"-107.60",000,8665,"000.00",000,8665,"000.00",156,40056,"-102.90"

OK
^C0+28 records in
0+28 records out
2501 bytes transferred in 34.785 secs (71 bytes/sec)

Each response appears to be PCI, EARFCN, RSRP, PCI, EARFCN, RSRP, PCI, EARFCN, RSRP, etc. I THINK the first one in the list is the site that it's currently connected to. This should be pretty easy to add into SCP. Now, the question is if there are other modem commands that would return CA status... The full list of AT commands can be found at the bottom of this post, including the Qualcomm specific additions: http://forum.xda-developers.com/showpost.php?p=53508236&postcount=268 There may be new commands that have been added since that was posted.

  • Like 3

Share this post


Link to post
Share on other sites

That's the infamous android bug. Theres a lot of info on it earlier in this thread. You are truly on LTE, not 1x.

 

Sent from my Note 4

I see. Thank you. Some of these threads get so long it's hard to sort through. Am I on a particular band when this bug occurs?

Share this post


Link to post
Share on other sites

I'm sure it can provide more detailed data, but since root is required to read it, I doubt it's worth the time and effort for Mike to implement. I doubt most people who use signal check have rooted devices.

 

I just rooted my LG Leon LTE (T-Mobile) to test it and it does work.  He already has airplane mode toggle, a root-only function, in the software.  And for T-Mobile with its complete lack of consistency on the sector ID with respect to Band, this would be a huge help.

 

I'm another vote in favor.

 

Now to see if I can root the Moto E I have for Verizon...

 

- Trip

  • Like 1

Share this post


Link to post
Share on other sites

I see. Thank you. Some of these threads get so long it's hard to sort through. Am I on a particular band when this bug occurs?

Nope. When you briefly lose them reacquire LTE, many devices running Android 5.1+ will indicate a simultaneous 1x and LTE connection for a time. Whether this is actually a bug or not is unclear. It's theorized this has something to do eCSFB issues while connected to a weak LTE signal. While this is happening, SCP is not able to pull current GCI, PCI or TAC values so the band indicator does not work.

 

Sent from my Nexus 5 using Tapatalk

Share this post


Link to post
Share on other sites

Nope. When you briefly lose them reacquire LTE, many device running Android 5.1+ will indicate a simultaneous 1x and LTE connection for a time. Whether this is actually a bug or not is unclear. It's theorized this has something to do eCSFB issues while connected to a weak LTE signal. While this is happening, SCP is not able to pull current GCI, PCI or TAC values so the band indicator does not work.

 

Sent from my Nexus 5 using Tapatalk

That makes a lot of sense. This just started a couple of days ago in a location that I am at every day and has had a very solid 2xCA service for a while. The last couple of days the service has been bouncing all over the place between different bands and even back to 3G so they must be doing something in the area.

Share this post


Link to post
Share on other sites

Random feature idea that popped into my head: option to automatically turn on the location service only when connected to a new GCI/site. And when strongest_RSRP/RSSI for the connected site is more than 5dBm stronger than the previous recorded entry the app could temporarily enable location for a set (but adjustable) minimum amount of time to allow for an accurate lock. Could save battery life significantly by keeping location off while a user is connected to their usual sites but still maintain very high log accuracy and capture new sites etc. You could even make the dBm cutoff adjustable.

 

I don't know if something like this is feasible but it would be pretty cool.

Share this post


Link to post
Share on other sites

Updated my Sprint M9 to latest MM build this weekend. The "Reset Mobile Connection" button appears to no longer function. It did prompt for root access which I granted of course, adjusted the delay time to 8000ms (from the default 4000). Checked SuperSU root has been granted just isn't working. Worked fine on previous build. Is this a known issue? I actually used it on a some what regular basis.

 

Everything else seems to be working fine, I mainly use the Widget on my home screen. I do block the notification in the status bar as the settings don't let me turn it off. I like to keep my status bar clean.

Share this post


Link to post
Share on other sites

An update to CellMapper just came out, and it added a new root feature for Qualcomm devices to fetch the band information directly from the modem. No need to deduce it from the GCI. As a result, it also shows the band info for neighbor cells. It works using the "default" device on my Nexus 6P,  /dev/smd11

 

Might be worth investigating to see if this can be used to get more detailed information than what is provided by the Android API. And also to perhaps get around the 1x + LTE bug or stale data. 

 

That is huge! I'm struggling to find time to dig into app-related things lately (life is good, that's all!), but I'll look into it. I would LOVE to get something like this implemented, even if it's only for a limited subset of devices.

 

I'm sure it can provide more detailed data, but since root is required to read it, I doubt it's worth the time and effort for Mike to implement. I doubt most people who use signal check have rooted devices.

 

Not necessarily true. SignalCheck users tend to be on the nerdier side, and many of us just happen to be rooted as well. I don't mind implementing features that require root because it's better than not implementing them at all (i.e. the "Reset" feature and a few other goodies, like direct PRL Updates for some Nexus users).

 

Random feature idea that popped into my head: option to automatically turn on the location service only when connected to a new GCI/site. And when strongest_RSRP/RSSI for the connected site is more than 5dBm stronger than the previous recorded entry the app could temporarily enable location for a set (but adjustable) minimum amount of time to allow for an accurate lock. Could save battery life significantly by keeping location off while a user is connected to their usual sites but still maintain very high log accuracy and capture new sites etc. You could even make the dBm cutoff adjustable.

 

I've been testing out some options to turn on location/logging when plugged in, so this is along the same lines. There are a lot of half-working features like this I'm testing on my own devices. Progress is slow because I'm learning how to code as I go! ;)

 

-Mike

  • Like 5

Share this post


Link to post
Share on other sites

Updated my Sprint M9 to latest MM build this weekend. The "Reset Mobile Connection" button appears to no longer function. It did prompt for root access which I granted of course, adjusted the delay time to 8000ms (from the default 4000). Checked SuperSU root has been granted just isn't working. Worked fine on previous build. Is this a known issue? I actually used it on a some what regular basis.

 

Everything else seems to be working fine, I mainly use the Widget on my home screen. I do block the notification in the status bar as the settings don't let me turn it off. I like to keep my status bar clean.

 

Hmm I'm not sure why this would be happening. My Nexus 5X is running 6.0.1 and has no issues. Have you tried clearing SCP's permission out of SuperSU and then re-adding it when prompted?

 

-Mike

  • Like 1

Share this post


Link to post
Share on other sites

That is huge! I'm struggling to find time to dig into app-related things lately (life is good, that's all!), but I'll look into it. I would LOVE to get something like this implemented, even if it's only for a limited subset of devices.

 

 

Not necessarily true. SignalCheck users tend to be on the nerdier side, and many of us just happen to be rooted as well. I don't mind implementing features that require root because it's better than not implementing them at all (i.e. the "Reset" feature and a few other goodies, like direct PRL Updates for some Nexus users).

 

 

I've been testing out some options to turn on location/logging when plugged in, so this is along the same lines. There are a lot of half-working features like this I'm testing on my own devices. Progress is slow because I'm learning how to code as I go! ;)

 

-Mike

Just saw this post after I replied to your post in the LTE Discovery thread. I'd be happy to help you implement the feature if you want. As I said in that post, feel free to take the code I submitted on github to Signal Detector. It's hopefully commented well enough that you'll be able to follow it. I just threw out the earfcn data for neighbor cells in that implementation because it was more a proof of concept and a little tricky to match up to the PCIs from the Android API (ie B25 and B26 show the same PCI, so you have to guess based on reported signal strength which one to assign the earfcn to)

 

Sent from my Nexus 6P

  • Like 3

Share this post


Link to post
Share on other sites

Just saw this post after I replied to your post in the LTE Discovery thread. I'd be happy to help you implement the feature if you want. As I said in that post, feel free to take the code I submitted on github to Signal Detector. It's hopefully commented well enough that you'll be able to follow it. I just threw out the earfcn data for neighbor cells in that implementation because it was more a proof of concept and a little tricky to match up to the PCIs from the Android API (ie B25 and B26 show the same PCI, so you have to guess based on reported signal strength which one to assign the earfcn to)

 

My hero! I would have killed to have read your posts about 8 hours ago.. I've been working on implementing this all day. I have tackled a majority of the issues, but it literally took all morning. Figuring out the exact modem command had me hung up for a bit (escape characters tripped me up but I figured it out after I finished my Cheerios) and I was struggling to figure out the best way to read the response from the appropriate device without choking the phone. Your code takes a slightly different approach than my implementation, but I think there's enough there to get me over the hump. Shame on me for not looking at S4GRU earlier.. I would be done by now. THANK YOU!

 

-Mike

  • Like 8

Share this post


Link to post
Share on other sites

My hero! I would have killed to have read your posts about 8 hours ago.. I've been working on implementing this all day. I have tackled a majority of the issues, but it literally took all morning. Figuring out the exact modem command had me hung up for a bit (escape characters tripped me up but I figured it out after I finished my Cheerios) and I was struggling to figure out the best way to read the response from the appropriate device without choking the phone. Your code takes a slightly different approach than my implementation, but I think there's enough there to get me over the hump. Shame on me for not looking at S4GRU earlier.. I would be done by now. THANK YOU!

 

-Mike

You're definitely welcome! I initially tried using read commands and doing it all with 1 root shell session, but it kept choking and getting out of sync. The only way I could reliably get it to work was using 2 root sessions, one reading the output of cat line by line looking for one that has the info we want, and the other using echo to issue the commands. If you use cat, remember to call kill() on destruction rather than close(), otherwise it will hang waiting for the shell to be idle which it never will unless you figured out how to terminate the cat command :-) I kept wondering why it would hang then crash any time I tried to disable the feature from the app preferences

 

Sent from my Nexus 6P

Share this post


Link to post
Share on other sites

does this work on the Nexus 5X with cell Mapper?

Share this post


Link to post
Share on other sites

From the list of devices on this post (https://plus.google.com/+IvanZupan/posts/3aXM3Y6QCC2), it appears to work on the Snapdragon 801, 810, and 410. Reported not working with the Nexus 6 (Snapdragon 805) and Nexus 5 (Snapdragon 800). I find it odd that it works with the 801 but not the 800 or 805. I'm going to have a friend with my old Nexus 6 double check for me and will report back. 

 

Mike, the comments on that post give some more information about the different smd devices used on various phones and might help you out. I particularly found the comment about mknod interesting (learned something new about Linux there!). For what it's worth, on my Nexus 6P /dev/smd11 has major number 224 and minor number 11. Not sure where he came up with major number 245 to test for the Nexus 5... We might have to try to comb through the Android source code for device specific information. The major number should correspond to the kernel driver being used.

 

I did notice though that after running "ls -l /dev/smd*" that /dev/smd11 is the only smd## style file owned by "radio". That might be a good way to determine which file to use on a given device, ie:

ls -l /dev/smd[0-9] /dev/smd[0-9][0-9] | grep radio | grep -oE '[^ ]+$'

Btw, ls -l also shows the major and minor numbers for each file in /dev.

Share this post


Link to post
Share on other sites

i cant seem to get it to work on my nexus 5x but i could be doing it wrong i suppose.

Share this post


Link to post
Share on other sites

i cant seem to get it to work on my nexus 5x but i could be doing it wrong i suppose.

Can you enable full logging in SuperSU, try it again, and then look at the 2 recent log entries in SuperSU and see if one of them lists an error? 

 

Or, preferably, open a root adb shell and type: 

ls -l /dev/smd*

and post the output? It's possible CellMapper is just using the wrong file by default on the 5X, which you can change in the CellMapper settings. The above output will tell us which file it should be using.

Share this post


Link to post
Share on other sites

On my N6

 

crw-rw---- 1 system    system       230,   0 1970-03-21 05:14 /dev/smd0
crw------- 1 root      root         230,   1 1970-03-21 05:14 /dev/smd1
crw------- 1 root      root         230,  11 1970-03-21 05:14 /dev/smd11
crw------- 1 root      root         230,   2 1970-03-21 05:14 /dev/smd2
crw------- 1 root      root         230,  21 1970-03-21 05:14 /dev/smd21
crw------- 1 root      root         229,  11 1970-03-21 05:14 /dev/smd22
crw------- 1 root      root         230,  27 1970-03-21 05:14 /dev/smd27
crw------- 1 root      root         230,   3 1970-03-21 05:14 /dev/smd3
crw------- 1 root      root         230,  36 1970-03-21 05:14 /dev/smd36
crw-rw---- 1 system    system       230,   4 1970-03-21 05:14 /dev/smd4
crw-rw---- 1 system    system       230,   5 1970-03-21 05:14 /dev/smd5
crw-rw---- 1 system    system       230,   6 1970-03-21 05:14 /dev/smd6
crw-rw---- 1 bluetooth net_bt_stack 230,   7 1970-03-21 05:14 /dev/smd7
crw------- 1 root      root         230,   8 1970-03-21 05:14 /dev/smd8
Edited by RyanThaDude

Share this post


Link to post
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

  • 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

  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...