Jump to content

SignalCheck - Android app to monitor your Wi-Fi/2G/3G/4G LTE/5G-NR signal strengths


mikejeep

Recommended Posts

Wow, over 8200 units made since they have hit 0EE.

 

Sent from my LG-LS997 using Tapatalk

  • Like 2
Link to comment
Share on other sites

SignalCheck is reporting my Magic Box as Band 25.

I wonder where the Magic box range will end. 0ED magic boxes show correct at least in the logs.

 

That's the issue.. the previously known ranges for Magic Boxes was 0EC-0ED. I'll add 0EE for the next update!

 

-Mike

  • Like 6
Link to comment
Share on other sites

I've realized I only get bad battery drain after a restart, it will consume between 1-2% within a few hours. If I kill the process and restart virtually no drain. Hope that helps maybe, S8+ here.

 

Battery usage is a common question on this thread and in my inbox.. I understand why some people raise concern, but a lot of it has proven to be due to misunderstandings. If you leave the app running on the screen for 2 hours, will it impact your battery? Of course. The screen eats a tremendous portion of power, but also the Logger, Location Service, background process, Alerts, etc.

 

This is tricky to explain clearly, but hopefully sums everything up. I need to fine tune and put this somewhere permanently to reference..

 

Please remember that the Android battery usage stats do not show the percentage of your battery that SignalCheck has used; they show the percentage of your overall power consumption since last full charge that SignalCheck is responsible for. (In previous Android versions, it may measure back to your last reboot, but I am not certain.)

 

For example: Charge your phone to 100%, turn it on, and immediately launch SignalCheck. Leave it on screen for 20 minutes, but don't interact with any other apps. If you look at your battery stats, SignalCheck will appear to have a very high battery use. If it says 20%, that is not indicating that SignalCheck has used 20% of your battery; it has used 20% of whatever battery usage has occurred. This is expected, because other than some system and background processes, you haven't used any other apps on your device during that time period.

 

If your battery charge is down to 95%, and SignalCheck shows 20% usage, that means the app was responsible for 20% of 5% -- aka 1% of your total battery usage.

 

In addition, some devices attribute battery usage by the display to individual apps. I have observed that this varies by device. Of course, leaving your display on will consume battery power; some devices report that under the "Screen" category, while others do not. Same for location/GPS functions; sometimes those are separated, other times the usage is attributed to the individual app requesting location information. It varies by device, OS version, and battery optimization settings.

 

None of this is meant to claim that SignalCheck is infallible. It's definitely not. But the core functions of the app have not changed in quite some time, nor will they. Any perceived spikes in power usage are likely due to usage patterns (you take a 50 mile drive and leave the app running in the foreground) or specific circumstances (you increase the location accuracy to the maximum setting while lingering in a basement or somewhere else with poor GPS and mobile signal). 

 

Hope this helps shed some light on things!

 

-Mike

  • Like 2
Link to comment
Share on other sites

The CFO of Sprint said on Thursday they will be making hundreds of thousands of Magic Boxes. That would take at least 25 hex primary GCI, so I would extend it to 0EF and then we will have to see what ranges they use after that.  He noted that it costs them about the same as a smartphone and they may report MagicBox tonnage with the next quarterly report.
Link to comment
Share on other sites

Just now, lilotimz said:

@mikejeep It seems that the engineering / debug menu shortcut does not work with the latest Android  8.0 update on the Pixel. Putting in the dialer code works though. 

I was just about to post this, myself. Too funny. 

Using Pixel XL on S4GRU Mobile Site

  • Thanks 1
Link to comment
Share on other sites

On 9/9/2017 at 10:21 AM, dkyeager said:
The CFO of Sprint said on Thursday they will be making hundreds of thousands of Magic Boxes. That would take at least 25 hex primary GCI, so I would extend it to 0EF and then we will have to see what ranges they use after that.  He noted that it costs them about the same as a smartphone and they may report MagicBox tonnage with the next quarterly report.

I was out of town this past weekend and saw a funky B41 GCI starting with 0E8; I was parked in front of a Sprint store. I just looked through my SCP logs and found another 0E8.. coordinates were right in front of my local Sprint store. Do Sprint stores deploy Magic Boxes?

 

6 hours ago, lilotimz said:

@mikejeep It seems that the engineering / debug menu shortcut does not work with the latest Android  8.0 update on the Pixel. Putting in the dialer code works though. 

Hmm, I hadn't noticed that, thank you. Looks like most of the system shortcuts fail with a security rejection. Apparently Oreo does not let third-party apps trigger dialer codes, rats. I'll see what I can do.

-Mike

Link to comment
Share on other sites

11 minutes ago, mikejeep said:

I was out of town this past weekend and saw a funky B41 GCI starting with 0E8; I was parked in front of a Sprint store. I just looked through my SCP logs and found another 0E8.. coordinates were right in front of my local Sprint store. Do Sprint stores deploy Magic Boxes?

 

Hmm, I hadn't noticed that, thank you. Looks like most of the system shortcuts fail with a security rejection. Apparently Oreo does not let third-party apps trigger dialer codes, rats. I'll see what I can do.

-Mike

1) Yep. A lot of em had Gen1 MBs for a while and a lot are now getting Gen 2s.

2) Ugh. Android 8.0 ... sigh. Google giveth google taketh. 

  • Like 1
Link to comment
Share on other sites

11 minutes ago, lilotimz said:

1) Yep. A lot of em had Gen1 MBs for a while and a lot are now getting Gen 2s.

2) Ugh. Android 8.0 ... sigh. Google giveth google taketh. 

1) Got it, thank you; I will add 0E8 and 0EF for now then. I suspect this will continue to evolve as MBs start spreading, but I don't want to speculate without confirmation in the wild. My code is sloppy enough as it is..

2) It's driving me insane. From SCP's standpoint, 8.0 has brought no improvements, only setbacks. Logcat is a mess now.. lat/long on BSLs is swapped.. some permissions are now out of reach.. annoying. Some of these bugs they were aware of in beta testing too, they just didn't fix them.

-Mike

  • Sad 1
Link to comment
Share on other sites

  Here is 0EE for a Magic Box [credit BluesRulez]:

4807745224640505127%253Faccount_id%253D1

  • Like 1
Link to comment
Share on other sites

Yes as I mentioned in a few earlier posts, I'll be adding 0E8, 0EE, and 0EF to the Magic Box list. A public update with those changes and a couple other minor tweaks should be ready by tonight sometime this weekend. I don't need more examples of those, but if anything else is spotted in the wild, please let me know.

-Mike

Edited by mikejeep
Update not quite ready yet!
  • Like 2
Link to comment
Share on other sites

SignalCheck Pro update is finally out! Should be available on Google Play within the hour. I believe most of the changes should be self-explanatory. 0E8 appears to be for Airave 3's, not Magic Boxes. The biggest difference is Airave 3 or S1000 B41 connections will now show as "Airave/S1000" because I have not identified a way to differentiate between the two yet.

  • Added additional indicators for Sprint LTE band 41 Airave/S1000 cells.
  • Added additional indicators for Sprint LTE band 41 Magic Box cells.
  • Added indicators for T-Mobile LTE band 4 Cellspot and In-Store Pico cells.
  • Added support for LTE band 71.
  • Improved identification of mobile network type on IWLAN connections.
  • Resolved issue with invalid GSM neighbor cell PLMN/CID/LAC information displayed.
  • Resolved issue with IWLAN signal strength missing from notification icon. (Pro)
  • Updated provider database.

Thanks for everyone's support! Holler with questions anytime..

-Mike

  • Like 3
  • Love 1
  • Thanks 3
Link to comment
Share on other sites

1 hour ago, mikejeep said:

SignalCheck Pro update is finally out! 

-Mike

As of today LTE band isn't showing up in the status bar, instead Android system icon is showing saying SignalCheck Pro is running in the background. Is there a setting that I should enable? On Android 8.0.

Link to comment
Share on other sites

1 hour ago, njjdnt said:

As of today LTE band isn't showing up in the status bar, instead Android system icon is showing saying SignalCheck Pro is running in the background. Is there a setting that I should enable? On Android 8.0.

You probably need to raise the status bar icon priority within the app. Preferences > Status Bar Icons > Notification Icon Priority.. if you select Minimum, it will never show on the status bar, only in the notification pulldown. Other than that, the higher priority you select, the less likely it will get bumped off the status bar by another icon. This setting does not change what the app does in the background, it only changes where the icon(s) will land in the notification list.

-Mike

Link to comment
Share on other sites

It appears that Oreo is not reporting valid Wi-Fi frequency information when DFS is enabled (thanks @ingenium). Please 'star' this issue if you feel inclined, and add any comments with your device and exact OS version so hopefully it gets some attention:

https://issuetracker.google.com/issues/66697994

Thanks,
-Mike

  • Like 2
Link to comment
Share on other sites

It could also be 4th carrier. The GCI is where the predicted 4th carrier is located(only one 4th carrier believed to be active) but where Triband antennas are found. If you could investigate which it (triband or 4th carrier) that would be great.

  • Like 2
Link to comment
Share on other sites

6 hours ago, Dkoellerwx said:

I believe tri-band antenna. Only identifiable in Samsung markets pretty sure. 

When you say tri-band antenna, is that an antenna on the tower that does B25, B26 and B41 all in one?  If so, is there a pic of one of those?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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