Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,269

  • Joined

  • Last visited

  • Days Won

    188

 Content Type 

Everything posted by mikejeep

  1. mikejeep
    Another SignalCheck Pro beta release is rolling out now! It actually has a lot of changes.. the only action necessary would be that anyone experiencing issues with the location service getting "stuck" should go to Preferences > Beta Crew and enable the location timestamp - this will let you see the frequency of updates live on your screen. I did make some adjustments to the location service itself that *may* have resolved the problem, but of course I won't be certain without testing by all of you. Here is the 4.673b changelog.. some nice improvements on this list.. Added 5G-NR neighbor cell display. Added location service debugging and option to display location timestamp. Adjusted RSRP threshold for web entries to be stronger than -118 dB. Changed site note & icon lock option to be two separate options. Improved 5G-NR information on some devices. Resolved additional force closes on some Android 10 devices. Resolved issue with old web entries being re-uploaded after a log import. Resolved issue with web entries that failed validation not being exported for inspection. Resolved issue with web entries that failed validation not being removed from the upload queue. Updated internal crash reporting library. Please provide feedback when you can, especially about the location bug. If you experience an issue, please send a diagnostic report as soon after the issue as possible. If the app is restarted (or crashes), some information could be lost. More feedback = better chance I can resolve things. Thanks!
  2. mikejeep
    I am a Sprint customer, and the phone came with a Sprint SIM pre-installed but a brand new T-Mobile SIM kit in the box. Wanting to use it as a native T-Mobile device, I installed the TMO SIM before I powered it up to ensure it didn't get activated as Sprint/TNA (which I believe cannot do standalone).
  3. mikejeep
    My A32 does have standalone 5G support. I have a T-Mobile SIM installed. Not rooted/modified/hacked at all. Not sure how literally you mean "out of the box", so I will mention that mine did some software updates shortly after I activated it. No idea what features might have been added/fixed. Might have just been catching up on the standard monthly Android rollouts.
  4. mikejeep
    If anyone has taken advantage of the new T-Mobile 5G upgrade program to get a Samsung Galaxy A32, you will notice that SignalCheck does not show consistent 5G-NR information (most notably, no RSRP values). It is an issue with the Samsung firmware and I am working with their support to get it resolved in a future Samsung update. The next SCP update will have some improvements to show more information on the A32 (and possibly other devices if they have similar issues), but a fix from Samsung will be needed for full compatibility.
  5. mikejeep
    Haha!! That is great news, I am happy you got it working. Cheers!!
  6. mikejeep
    Yes, a return kit with prepaid label was included in my package.
  7. mikejeep
    Unfortunately no errors are on any reports or crash submissions from you or anyone else. I'm going to have to add some temporary extra logging to try debugging the issue. I've been slammed with other stuff the past couple of weeks, sorry for not being able to devote much time to this issue lately. I will get to it.. and several other things filling up my inbox!
  8. mikejeep
    I am still a Sprint account, and did the 5G Trade-In on both of my lines online without any trouble on the 18th.. arrived today. No idea about the Trade-Up portion though.
  9. mikejeep
    Ugh.. mdob07 your report did not show any problems. I am stumped at the moment, as I can't replicate this. I will do some research to see if I can figure out what might be causing this. What devices is everyone seeing this problem with? Also, what Android version? Sorry for the trouble!
  10. mikejeep
    Anyone with previous crashing issues seeing any improvement with latest SCP beta? Eerily quiet on the feedback front, hopefully that's a good thing..
  11. mikejeep
    I have a SCP user who reached out to me with what appeared to be valid T-Mobile standalone n66 in use in New Jersey.
  12. mikejeep
    From the official T-Mobile press release: "The Great Free 5G Phone Upgrade and Great Unlimited Trade-Up start April 18 and last all year long."
  13. mikejeep
    A new SCP release for the Beta Crew is rolling out now, version 4.672b. No new features; it is all bugfixes and internal improvements -- those of you experiencing various crashes and freezes, please let me know if this update is better, worse, or about the same. Thanks!
  14. mikejeep
    I'd actually prefer to switch that line to TNX so I can get a different experience from my Pixel 5 on TNA, especially since it's just a testing/logging/backup device.. but I also don't want to lose my free line or SWAC. I'm sure it will be a headache no matter what, but we'll see.
  15. mikejeep
    It works great.. it's my "how does SCP work on older phones" test device, although it is so slow I don't use it for anything else. Would be far more beneficial to have a newer Samsung in the testbed. Next hurdle, would I have to give up my SWAC account..
  16. mikejeep
    Soooo they will take my HTC EVO 4G I have on a free line (not kidding), and give me the Samsung..?!
  17. mikejeep
    I received your diagnostic reports, thanks! Unfortunately they do not show anything out of the ordinary, and I have no automated crash reports either. Do you have battery optimization for SCP disabled? Some others have reported that improves their stability on newer Samsung devices. I am not sure what to suggest other than an app uninstall/reinstall, since I don't have other reports of this or an error message to look into. If you do that, make sure you back up your log database before uninstalling, and then restore it on the new install.
  18. mikejeep
    As long as you've previously saved your username on a report, try a long-press on the "Connected to LTE" text... 😉
  19. mikejeep
    When it freezes, does the screen keep updating? Can you send a diagnostic next time you notice it happens please.. thanks!
  20. mikejeep
    A new SignalCheck Pro update is now available for download, version 4.67. It includes the following changes: Added one-time popup to comply with Google Play background location policy. This popup is a policy mandate, there are no changes to existing app behavior. The popup will only display on first launch after a brand new installation. Changed location accuracy precision to one decimal place. Changed location accuracy to display in feet if metric units are not enabled. Improved PLMN ID validation. Resolved force closes on some devices when connected to GSM/WCDMA networks. These should be self-explanatory but feel free to reach out if you have any questions. Thanks for your support, feedback is always welcome!
  21. mikejeep
    Another SignalCheck beta is rolling out now. There was a bug that had location accuracy being improperly saved as feet instead of meters in logs. Please do not upload any web data with version 4.66, or data points with accuracy worse than 75 feet (instead of 75 meters, approximately 3x more forgiving) will be excluded! This version also changes location accuracy precision to one decimal place, and aligns with a public release rolling out now. Thanks for all of your testing and feedback!
  22. mikejeep
    Another SignalCheck Pro beta was released this morning! The most visible change is a message displayed at startup explaining the app's use of your location. It will only appear once per app install; you will never see it again unless you uninstall/reinstall. This is to comply with Google Play policies; there are no functional changes to the location features. Location accuracy will now be displayed in either feet or meters, depending on your app settings. There are also some bugfixes in this release. Invalid PLMN entries in logs should be reduced, and a frequent cause of crashes when connected to WCDMA/GSM networks should be resolved. Feedback always appreciated!!
  23. mikejeep
    Thanks! Unfortunately Google Play doesn't pass on any user info or comments, so it's difficult to pinpoint those.. but one of my other crash reporting libraries caught it (the username from diagnostic reports is included on those). That crash is something I've been working on, it just recently started over the past couple of months and only impacts GSM/WCDMA connections. Looks like you were on HSPA at the time of the crash. I added some additional error tracking in this version so your report was very helpful.. hopefully I can squash it.
  24. mikejeep
    That is great news.. but do those of us with a Sprint SIM but on the T-Mobile network (TNA) not already benefit from it? That page doesn't mention anything specific about Sprint customers on the network.
  25. mikejeep
    The accuracy is in meters (m) because that's what Google refers to in all of its location setting descriptions. Miles would not be terribly useful, but I do plan to add feet as an option.
×
×
  • Create New...