Jump to content

mikejeep

Honored Premier Sponsor
  • Content Count

    2,487
  • Joined

  • Last visited

  • Days Won

    34

mikejeep last won the day on January 10

mikejeep had the most liked content!

Community Reputation

4,275 Wireless Expert

About mikejeep

  • Rank
    The SignalCheck Guy

Contact Methods

  • Website URL
    https://signalcheck.app

Profile Information

  • Phones/Devices
    Pixel 3
  • 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,972 profile views
  1. mikejeep

    Google Pixel 3 / Pixel 3 XL User Thread

    About a month ago, I started noticing my Pixel 3 (non-XL) wouldn't reconnect to LTE after it had dropped to 3G but only in certain areas. I haven't noticed a pattern other than it definitely doesn't happen in some areas. For example, near my home, I have poor signal and it drops to 3G often, but it always goes back to LTE as soon as it should. -Mike
  2. That is odd. I'll have to do some digging and testing to see where that is coming from. Regarding TAC 0, I have it flagged to log if TAC is between 0 and 65535. I can have it ignore TAC 0 if that's truly invalid, but I assumed that about PCI when I wrote the app, which turned out to be wrong (PCI 0 is valid and in use). If TAC 0 is legitimate I could look into making it a user option. That's the long-standing issue where the PLMN doesn't update in sync with the other data. It's very annoying. I *may* have overcome that in the current beta, albeit accidentally.. it's taking awhile to iron out some other bugs that have popped up but I'm still plugging away at it. -Mike
  3. No, that's odd! In most instances, the app overrides the provider name that is being broadcast (because many SCP users want to know the true identity of the network they are on, i.e. Project Fi). SCP uses "US".. perhaps the network uses periods in the name and for some reason it's falling back to that. Where in the app are you seeing "U.S."? -Mike
  4. It's indicating you are connected to a second carrier on either a small cell or a Mini Macro. Both have similar GCI patterns; the app can't distinguish between them, that's why it displays both. -Mike
  5. mikejeep

    SignalCheck Beta Crew Forum

    New beta has been uploaded, should become available within the hour.. added LTE timing advance and hopefully squashed some big juicy bugs.. let me know! Please try enabling some notifications and changing the sounds too.. -Mike
  6. mikejeep

    Google Pixel 3 / Pixel 3 XL User Thread

    I am loving the Wi-Fi Calling as well. Works great for me, where I have poor signal at home and sometimes have trouble connecting to my Airave 3 because it's hanging onto 1X800. I should have clarified that the problem I mentioned is not exclusive to Wi-Fi Calling -- it's happening to people on every call, on many different mobile providers worldwide. Shocked that Google's only response so far is to provide warranty replacements (which aren't fixing the issue). Sources: Android Police, Reddit, Google Forums -Mike
  7. mikejeep

    Google Pixel 3 / Pixel 3 XL User Thread

    I've noticed the HD icon on the dialer screen as well. Doesn't appear to matter if you're on Wi-Fi Calling or not, just when HD Voice is active. On another note.. anyone here having the issue with callers hearing you severely muffled and they hear their own echo? Looks like a widespread issue online. I noticed it only occurs on non-HD calls so it's likely a software issue. It's a serious problem though. -Mike
  8. I loaded an old version myself after I posted, the issue appears to be related to the change in October that I suspected.. thanks! I think I've already got a fix working. -Mike
  9. I managed to get my old HTC EVO LTE test device to duplicate the multiple instances bug. I can't figure out why it's not impacting my Pixel 3, but I guess that doesn't matter. I think I see what is causing the issue.. can anyone confirm that this behavior started with version 4.49 (released October 2018)? Or did it not appear until the most recent release from last month, 4.51? -Mike
  10. Hey it doesn't bother me, you're the one wasting battery for no reason.. 😉 -Mike
  11. Hmm.. just dug out your report too, I don't see anything specific that might cause multiple instances. Any recollection which version this started with? Regarding your Wi-Fi Calling icon, at the time of your report your device was reporting the voice side was connected to the 1X macro site, not Wi-Fi Calling. I have discovered that many phones do not reliably report Wi-Fi Calling status to the OS in the only manner I can access it. As you have seen, in certain instances it shows properly, but sometimes it does not. I'm still trying to find better ways to access this info. Also, I do see you have the root EARFCN method enabled, perhaps unnecessarily? It's logging lot of errors, are you seeing any error messages on your end? You can turn that off under Preferences > General > Enable Modem Commands if you're not using it; it would save some system resources. -Mike
  12. I was trying it without using the back button.. I tried exactly what you suggested, as well as many variations of that, using the recent tasks, home button, back button, notification icon, widget, etc.. I could not duplicate it. Please try it with Xposed and/or GravityBox disabled. I just checked out your diagnostic reports; the only errors I see are these, neither of which are being generated by SignalCheck; the third one referencing Xposed repeats numerous times over several minutes: 01-09 10:41:48.200 E/SpellCheckerSession(28997): ignoring processOrEnqueueTask due to unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE 01-09 10:41:48.200 E/SpellCheckerSession(28997): ignoring processOrEnqueueTask due to unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE 01-09 10:41:53.642 W/zygote64(29404): ClassLoaderContext size mismatch. expected=1, actual=2 (PCL[] | PCL[];PCL[/data/dalvik-cache/xposed_XResourcesSuperClass.dex*2802528989:/data/dalvik-cache/xposed_XTypedArraySuperClass.dex*708326108]) Let me know how it goes! Send diagnostics if you have issues, before and after are great -- you never know where an obscure error is going to get flagged and point me in the right direction. Thanks, -Mike
  13. Huh.. very strange -- I'm not able to reproduce this on my Pixel 3. One other person reported it to me a few months ago (I don't think it was you) but I was not able to reproduce that on my original Pixel. Do you have a custom launcher, memory management app, or anything else installed that you can think of that might play a role? -Mike
  14. Significant changes were introduced with Android 6.0 that limited what cell and Wi-Fi info would be accessible without Location access. I believe the theory behind it was that you could use that information to deduce your location. I held off implementing those APIs in SignalCheck as long as possible because I knew it would create headaches, but they have been in place since version 4.43 of the app, which was released in June 2017. Perhaps Samsung didn't fully implement those changes in it's flavor of the OS until the new update you just applied. -Mike
  15. It looks like you didn't grant SignalCheck the Location permission it would have requested. If you permanently declined it, go to your device's Settings menu and selecting Apps > SignalCheck Pro > Permissions and granting it there. All 3 of the requested permissions (Phone, Location, Storage) needed to be granted for full app functionality. -Mike
×