Jump to content


Honored Premier Sponsor
  • Content count

  • Joined

  • Last visited

  • Days Won


mikejeep last won the day on May 12

mikejeep had the most liked content!

Community Reputation

4,161 Wireless Expert

About mikejeep

  • Rank
    The SignalCheck Guy

Contact Methods

  • Website URL

Profile Information

  • Phones/Devices
  • Gender
  • Location
    New England
  • Here for...
    4G Information
  • Twitter Handle
  • Favorite Quotation
    "Sensorly or it didn't happen!" --digiblur

Recent Profile Visitors

15,779 profile views
  1. mikejeep

    SignalCheck Beta Crew Forum

    Minor development news for the Beta Crew.. because of where I was at in overhauling SignalCheck Lite when I discovered the EARFCN bug that impacts LTE band 66 (and 71, and potentially others), I implemented a workaround in Lite first. I launched a SignalCheck Lite alpha channel (no different than beta, it's just semantics based on how I had to set it up on the back end) to facilitate testing. Lite is missing a lot of features that Pro has, but you can test the EARFCN workaround right now if you're impatient -- I am in the process of implementing the same routines in Pro, and hope to have a beta out sometime this month depending on how much free time I have. To enroll in the SCL alpha, first opt-in here: https://play.google.com/apps/testing/com.blueline.signalchecklite Shortly thereafter, you should see the alpha version of Lite on Google Play. You'll know it's the alpha because the release notes say it, and it should be version 4.482Lb. If you see the old version (4.28L from 2015!!), give it a few minutes and try again. Pro and Lite are two independent apps so you can have both running on the same device and they have no impact on each other. Any and all feedback is appreciated! -Mike
  2. I am still finishing up the EARFCN workaround, among other things.. it's going well, just lots of code to pick through to make sure I'm not missing anything. I'll send you a PM. -Mike
  3. I enjoy the geek chatter but can we find another thread to continue it? A ton of people follow this one for app-related stuff, and it's long enough as it is. Thanks -Mike
  4. No idea, you should ask Samsung.. 😂😂 -Mike 😘
  5. Some OEMs have fixed it on their end.. OnePlus devices have been reporting properly for awhile. -Mike
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. Yep, it's been popping up on a lot of sites northwest of the city over the past few months. Nearly all of the sites in my area are now showing it and performance appears to have improved! -Mike
  12. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    My Pixel is refusing to drop fringe 1X800 and connect to my Airave 3 again. It was an issue when I first received it, but resolved itself and has been awesome for months.. all of a suddenly it's doing it again. I left it plugged in with SCP running for 6+ hours about 10 feet from the Airave tonight and 1X would not connect to it. EV-DO and LTE grab it almost immediately. I know wifi calling / VoLTE is coming, but in the meantime I hope they don't give up on the Airave, some of us need it! -Mike
  13. Band 41 on a high-capacity mini macro! I've yet to see that in the wild myself.. a rare bird, indeed.. -Mike
  14. mikejeep


    You can just log out of S4GRU in Tapatalk and that should stop the blocks. That worked for me. -Mike
  15. mikejeep

    SignalCheck Beta Crew Forum

    New update just pushed out.. no changes from yesterday's release other than the version number, necessary because otherwise beta users would end up getting the public release that went out today. I know some people like having the "Diagnostic Mode" screen that is exclusive to the beta version. Thanks for all of your help! -Mike