Jump to content

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


mikejeep

Recommended Posts

There is no major bugs so I don't think Mikejeep needs to comment to much if mikejeep is busy.

 

List of bugs I have seen mentioned.

 

WCDMA not being displayed on TMobile S7. Not sure the problem.

 

Notes need to match the exact sector first before looking for a matching the site GCI.

 

Samsung 03 not showing B25 2nd carrier.

If(0x76 <market GCI && market GCI < 0xB9) // it is samsung market.

 

Possible 3rd carrier ALU 41,42,43 this needs confirmed correct first. Only one site in New Haven Connecticut so far.

 

Clear conversion nokia is B25 market GCI and 3x sector.

Link to comment
Share on other sites

There is no major bugs so I don't think Mikejeep needs to comment to much if mikejeep is busy.

 

 

 

Any new feature requests? I haven't followed the thread enough.

 

The issue i ran into with the system short cuts would be a nice enhancement maybe with some device detection or a model selection.

Link to comment
Share on other sites

Just to let everyone know, I talked to Mike and he definitely has not abandoned the app. He's just been busy (in a good way!) and hasn't really had time to update it or get on s4gru. He said he'll try to find some time to catch up on everything in the next few days.

  • Like 9
Link to comment
Share on other sites

Possible 3rd carrier ALU 41,42,43 this needs confirmed correct first. Only one site in New Haven Connecticut so far.

 

New Orleans looks like it launched third carrier with 41,42, and 43. http://s4gru.com/index.php?/topic/7559-4x4-mimo-phones-sprint-lte/?p=492454 Many many sites with the 41,42, and 43.

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Mike,

 

I just upgraded to Nougat and looking at the diagnostics, it looks like the phone is now providing the EARFCN via the API.  As soon as you get that going, I'll have it made!

 

- Trip

  • Like 10
Link to comment
Share on other sites

Did anyone ever figure out the dev/smd code for the Nexus 6 to show the EARFCN/Frequency data?  It pains me that I cannot use this on the N6 in Cellmapper nor SignalCheck.   :twitch:

 

Robert

  • Like 4
Link to comment
Share on other sites

Did anyone ever figure out the dev/smd code for the Nexus 6 to show the EARFCN/Frequency data? It pains me that I cannot use this on the N6 in Cellmapper nor SignalCheck. :twitch:

 

Robert

Is the N6 using Android 7? If so, cell mapper uses the new API and doesn't need root anymore to get the earfcn. Signal Check hasn't been updated yet for that.

 

Sent from my Pixel XL

  • Like 3
Link to comment
Share on other sites

Is the N6 using Android 7? If so, cell mapper uses the new API and doesn't need root anymore to get the earfcn. Signal Check hasn't been updated yet for that.

 

Sent from my Pixel XL

Not yet. Project Fi N6's haven't been updated, yet. Glad to know the end is nigh.

 

Using Tapatalk on Note 8.0

  • Like 1
Link to comment
Share on other sites

Not yet. Project Fi N6's haven't been updated, yet. Glad to know the end is nigh.

 

Using Tapatalk on Note 8.0

Ahh. If you enable full logging for SuperSU for CellMapper (while it's closed), then run CellMapper for a minute and exit, then go to SuperSU, it should have logs. Look for the lines saying "cat /dev/______". Whatever that _____ is is the appropriate device name to give SCP.

 

Sent from my Pixel XL

Link to comment
Share on other sites

Ahh. If you enable full logging for SuperSU for CellMapper (while it's closed), then run CellMapper for a minute and exit, then go to SuperSU, it should have logs. Look for the lines saying "cat /dev/______". Whatever that _____ is is the appropriate device name to give SCP.

 

Sent from my Pixel XL

Doesn't work that way unfortunately on my N6 with Nougat. b1650dffbae57cd9fdf13fcf0d5c0d8a.jpg

 

Sent from my SM-G935V using Tapatalk

Link to comment
Share on other sites

Doesn't work that way unfortunately on my N6 with Nougat. b1650dffbae57cd9fdf13fcf0d5c0d8a.jpg

 

Sent from my SM-G935V using Tapatalk

Because of Nougat you can disable the option to use root and it'll work (I'm guessing it doesn't show the earfcn for you if you have root mode enabled?). If CellMapper shows the earfcn with root on Marshmallow, then whatever device it's using must be working.

 

Sent from my Pixel XL

Link to comment
Share on other sites

Is the N6 using Android 7? If so, cell mapper uses the new API and doesn't need root anymore to get the earfcn. Signal Check hasn't been updated yet for that.

 

Sent from my Pixel XL

Oooh, a reason to upgrade to 7! (I refuse to use the stupid names).

  • Like 2
Link to comment
Share on other sites

Is the N6 using Android 7? If so, cell mapper uses the new API and doesn't need root anymore to get the earfcn. Signal Check hasn't been updated yet for that.

 

Sent from my Pixel XL

I just went ahead and installed the PureNexus Android 7 ROM that works with Project Fi. Doesn't help SCP, but now Cellmapper shows EARFCN and band. Thanks.

 

Sent from my Nexus 6P using Tapatalk

Link to comment
Share on other sites

I just went ahead and installed the PureNexus Android 7 ROM that works with Project Fi. Doesn't help SCP, but now Cellmapper shows EARFCN and band. Thanks.

 

Sent from my Nexus 6P using Tapatalk

LTE Discovery also uses the new API and can get earfcn data on 7.

 

Sent from my Pixel XL

Link to comment
Share on other sites

I just went ahead and installed the PureNexus Android 7 ROM that works with Project Fi. Doesn't help SCP, but now Cellmapper shows EARFCN and band. Thanks.

 

Sent from my Nexus 6P using Tapatalk

 

Huh.  If I used the Nexus 5 version of Pure Nexus, do you think the API would work?

 

- Trip

  • Like 1
Link to comment
Share on other sites

Huh. If I used the Nexus 5 version of Pure Nexus, do you think the API would work?

 

- Trip

If it's based on Android 7, there's a good possibility. The API specifies it can return a value for the earfcn though that basically means "I don't know". Try it and see (after making a TWRP backup! I prefer to use a USB OTG cable with a flash drive or SD card for this)

 

Sent from my Pixel XL

Link to comment
Share on other sites

If it's based on Android 7, there's a good possibility. The API specifies it can return a value for the earfcn though that basically means "I don't know". Try it and see (after making a TWRP backup! I prefer to use a USB OTG cable with a flash drive or SD card for this)

 

Sent from my Pixel XL

 

If time permits, I intend to try it this evening.  I'll back up my Nexus 5 and see if I can update it to Nougat and get out EARFCN from the API.

 

- Trip

  • Like 1
Link to comment
Share on other sites

By the way, I think that mikejeep may be done with SignalCheck Pro.  It has not been updated in six months.  And he no longer maintains a presence in this thread.

 

Hello strangers!!! SURPRISE! I'm not done.. :)

 

I am *way* behind on my e-mail and S4GRU threads, and have not had much time to work on the app over the past several months. But I'm lurking. And have been (slowly) working on an update to include the new API features. As I've privately told a few of you, I'm just crazy busy with other things in life and at work. Everything is great, just not enough time in the day.

 

Looking forward to being as active as I used to be. Sincere apologies for giving anyone the impression that the app was dead and I appreciate your patience. SignalCheck had hit a point of stability where I felt like I could let it simmer for a bit without a huge impact to users. Not because I don't enjoy working on it, just because I was burning the candle at both ends and real life takes priority sometimes. Maintaining the app could probably be a (terrible-paying) full-time job but it's still a fun hobby to me.

 

I'm slowly but surely working through all the e-mails and posts. It's all good!

 

-Mike

  • Like 27
Link to comment
Share on other sites

If it's based on Android 7, there's a good possibility. The API specifies it can return a value for the earfcn though that basically means "I don't know". Try it and see (after making a TWRP backup! I prefer to use a USB OTG cable with a flash drive or SD card for this)

 

Sent from my Pixel XL

 

It was a bad idea.  After the update, I lost LTE and once I got it back, I now do not get PCI, TAC, SNR, or most other information aside from GCI and RSRP.  I think I'll be rolling back.

 

EDIT: Rolled back successfully.  Apparently the N5 never reported the SNR to begin with.  In any case, it now correctly shows PCI and TAC again.

 

- Trip

  • Like 1
Link to comment
Share on other sites

It was a bad idea. After the update, I lost LTE and once I got it back, I now do not get PCI, TAC, SNR, or most other information aside from GCI and RSRP. I think I'll be rolling back.

 

EDIT: Rolled back successfully. Apparently the N5 never reported the SNR to begin with. In any case, it now correctly shows PCI and TAC again.

 

- Trip

My 6P never displayed the SNR correctly. It was never less than 20, but would sometimes go above that. The Pixel doesn't show SNR at all. Losing the other info though is a deal breaker, especially for logging purposes.

 

Sent from my Pixel XL

Link to comment
Share on other sites

Hello strangers!!! SURPRISE! I'm not done.. :)

 

I am *way* behind on my e-mail and S4GRU threads, and have not had much time to work on the app over the past several months. But I'm lurking. And have been (slowly) working on an update to include the new API features. As I've privately told a few of you, I'm just crazy busy with other things in life and at work. Everything is great, just not enough time in the day.

 

Looking forward to being as active as I used to be. Sincere apologies for giving anyone the impression that the app was dead and I appreciate your patience. SignalCheck had hit a point of stability where I felt like I could let it simmer for a bit without a huge impact to users. Not because I don't enjoy working on it, just because I was burning the candle at both ends and real life takes priority sometimes. Maintaining the app could probably be a (terrible-paying) full-time job but it's still a fun hobby to me.

 

I'm slowly but surely working through all the e-mails and posts. It's all good!

 

-Mike

I'm looking forward to the updates. Welcome back!

 

Using Tapatalk on Note 8.0

  • Like 7
Link to comment
Share on other sites

I'm looking forward to the updates. Welcome back!

 

Bring the fatted chicken, and let us feast.

 

AJ

  • Like 4
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

    • I've now seen 100 MHz n77 from SoftBank and 100 MHz n78 from NTT. NTT seems to be a bit better south of Osaka, though in some cases it drops down to B19 LTE as some areas around here are pretty rural. SoftBank has n77 around, but it's flakey enough that I switched eSIMs earlier this morning.
    • I'm currently typing this from a bullet train headed from Tokyo to Osaka. Using a roaming eSIM rather than T-Mobile as it's a lot cheaper, but I'll start with T-Mobile's roaming experience. Since I have a business line, I can't add data packs online, so I'm just using the 256 kbps baseline service you get by default. That service runs on Softank 4G. SoftBank has a well-built-out LTE network though, with plenty of B41, falling back to B1/3/8 as needed. 5G roaming from T-Mobile doesn't appear to exist though. I've seen 20+10 MHz B41 when I've looked, generally speaking. WiFi calling works well, and voice calls over LTE work fine too (I forgot to turn WiFi back on after doing some testing, so I expect my bill to be a dollar more next month). I want to say I even got HD voice over the cell network for the VoLTE call I did. I have a bunch of eSIMs and a couple of physical SIMs to try out. I've gotten the eSIMs up and running, but last I checked the physical SIM wasn't working even after activation so I'll run through eSIMs for the moment and update this thread with pSIM info and details on not-Tokyo in the coming days. First off, there's US Mobile's complimentary East Asia eSIM (5GB) that I grabbed before my unlimited plan Stateside expired. That SIM uses SIM Club, routing through Singapore, running on SoftBank LTE and 5G. I've seen 40 MHz n77, as well as 10x10 n28, and have seen download speeds in excess of 200 Mbps with uploads of more than 50 Mbps, though typical speeds are slower. Routing is via Equinix/Packet.net. 5G coverage is rather spotty, but LTE is plenty fast enough; either my phone doesn't want to use the 5G band combos that have more coverage or 5G coverage is just spottier here than in the US (at least on T-Mibile). Latency is as low as 95ms to sites in Singapore (usually closer to 120ms), which is pretty great considering the 3300 mi between Tokyo and Singapore. Next there's Ubigi. It also routes through Singapore via Transatel (despite being owned by NTT), and sites on top of NTT docomo's network. I didn't see NTT 5G in Tokyo when I tested it, but since then I've seen 10x10 n28, and have seen B1/B3/B19 on the LTE side. So far it's not the fastest thing out there, but I'm guessing coverage will be a little better...or maybe not. This was $17 for 10GB. Latency is a bit higher to Singapore, but still under 150ms it seems. Then there's Airalo, which was the cheapest when I bought it at $9 for 10GB. It also routes through Singapore (on Singtel), but on my S24 I have my pick of KDDI (au) or SoftBank. KDDI has extensive B41 coverage and I've seen 20+20 with UL CA. While waiting for the train at HND Terminal 3 (Keikyu line) I hit 250+ Mbps down and 10+ Mbps up...over LTE...with pretty respectable latency numbers (not much above 100ms). This is in adition to supporting SoftBank, also on LTE (my S24 defaulted to KDDI, while my wife's Pixel 8 defaulted to SoftBank and didn't seem to want to connect to KDDI). Of the various carriers mentioned, I'd say this was the best pick, though prices have bumped back up to $18 for the 10GB plan...but it's probably still what I'd pick if I had to pick just one carrier. Then there's Saily, which uses Truphone out of Hong Kong. I haven't used this as much, as I only grabbed 3GB for $7. It runs on NTT but doesn't seem to have 5G access and doesn't seem to have as good speeds. Yes, Hong Kong is way closer to Japan, but latency didn't seem to be any better, at ~150ms. In all cases, I've had reception even in train tunnels and even at high speed on the bullet train, on all three carriers I've tried (I don't think I'll be able to play with a Rakuten SIM, which is rather disappointing). There have been cases where service has degraded, but it looks like you'd have reasonable cell service no matter which of the big three carriers you picked...and since T-Mobile roams on one of them, that's good enough if you're content to buy day passes.
    • https://www.phonearena.com/news/t-mobile-older-rate-plan-prices-june_id157821 We're on Sprint Max for our seven phone/two Apple Watch (with Cellular) family plan... Because it doesn't make sense to switch to anything else, especially if we can't even finance all of our devices. Some of you may recall that T-Mobile suddenly cut our credit limit to $1,500 (which is barely more than one iPhone 15 Pro) with no notice at all. I escalated it to the Office of the CEO and was told to pound sand, even though I have 800+ Credit as a longtime customer and was suddenly being treated as a deadbeat. I ultimately upgraded my three iPhone lines directly through Apple and they're Unlocked. I haven't bothered to check on whether my Credit Limit has updated, but I don't plan on upgrading them through T-Mobile again. I guess we'll find out if "Sprint Max" counts as "older" soon enough.
    • From just under a week ago: https://www.t-mobile.com/news/network/t-mobile-announces-163-million-in-completed-network-upgrades-for-arkansas Progress!
  • Recently Browsing

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