Jump to content

mikejeep

Honored Premier Sponsor
  • Content count

    2,438
  • Joined

  • Last visited

  • Days Won

    27

mikejeep last won the day on May 12

mikejeep had the most liked content!

Community Reputation

4,166 Wireless Expert

About mikejeep

  • Rank
    The SignalCheck Guy

Contact Methods

  • Website URL
    http://www.bluelinepc.com/signalcheck

Profile Information

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

Recent Profile Visitors

15,862 profile views
  1. I appreciate the feedback, but I'm not inclined to change the defaults at the moment. I will consider an option to "lock" the screen to prevent inadvertent edits though. I believe app preferences should be automatically restored when you're installing from the same Google account? -Mike
  2. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    I wipe the phone of everything but my user data and put on a fresh install of each month's Android update, and I swap SIMs more often than the average person because I test SCP on multiple networks. And I've done every #*#* code imaginable, often at Customer Care's request. Gremlins! -Mike
  3. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    It never rings.. I use Google Voice for my voicemail, so I get missed call notifications from that service even if the phone never realizes a call was coming in. The solution I've found that works best is to disable BC10 and disable LTE when I get home.. that typically gets the Pixel to grab onto the Airave within a few minutes of arriving home, but still not immediate. Seems odd that it doesn't search quicker when it's camped on a 1X connection from the macro site that is usually around -108 dB. I've talked to Sprint numerous times and all they want to do is have me update my profile and PRL, then they say my Pixel must be broken. When I was trying to work through the Airave/1X800 issue I was never really able to get anyone on the phone who understood what I was trying to say. One thing I noticed playing around with NSG was that the macro 1X uses channel 650, and the Airave is on channel 500. Are they intentionally different? I'm guessing channel assignment varies by region; would it make more sense for them to use the same channel, theoretically allowing for quicker discovery of the Airave? Or does that have no bearing on anything? -Mike
  4. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    Swapping back to a 2.5 has crossed my mind.. for my needs it was great. No camping on fringe 1X800 mostly. I only dumped my 2.5 because it died and I had to wait for a 3. If they would get some flavor of WiFi calling going on the Pixel, I wouldn't need anything.. -Mike
  5. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    Is there a way to disable the B41 signal on an Airave 3? My Pixel just has a heck of a time dropping back to CDMA for calls.. I've resorted to forcing 3G mode when I get home, but if I could kill the Airave LTE signal that would solve it. I don't need it since I'm on WiFi anyway. Didn't see anything on the web interface. -Mike
  6. mikejeep

    SITE UPGRADE WARNING

    My Fios IP is blocked again. Consistently happens when I use Tapatalk to browse the board.. if I stay logged in for notifications but use the mobile website, it doesn't seem to happen. -Mike
  7. mikejeep

    Google Voice voicemail question

    I don't think so, I have used GV voicemail for a few years and have never come across an option to configure that. But mine definitely doesn't go 20-30 seconds beyond the phone ringing. -Mike
  8. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    Correct. Airave uses an existing internet connection on site. Magic Box uses Sprint signal from a macro site (and does not help with the CDMA voice network). Not every location will qualify for a MB. -Mike
  9. mikejeep

    Official Airave 3 LTE / S1000 NSC Thread

    If your main internet goes down, any Airave(s) will become useless too.. -Mike
  10. 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
  11. 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
  12. 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
  13. No idea, you should ask Samsung.. 😂😂 -Mike 😘
  14. Some OEMs have fixed it on their end.. OnePlus devices have been reporting properly for awhile. -Mike
  15. 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
×