Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,255
  • Joined

  • Last visited

  • Days Won

    183

Everything posted by mikejeep

  1. That's not good. Please back up your log databases in case an app bug is doing something to erase your existing notes.. with the changes made in that version, I suspect it's more of a search query issue, but it can't hurt to be safe. Strangely I'm not seeing the same issue myself. Could you send me 1) screenshots of instances where notes are missing, a 2) backups of your log databases? PM or email is fine.
  2. No, the beta is completely independent of that.. Google Play's review processes are just unpredictable. I don't see any specifics, other than the time I submitted it and the "In Review" status. This release took longer than usual to be approved, but it was not out of the normal range. New beta is rolling out now with some more adjustments to the NR band correction algorithm as well as some other NR bug fixes.. please let me know if it resolves this issue.
  3. Depends on if you are in the standard Beta group or the Internal Test group. I roll all releases out to both groups simultaneously, but Beta releases get screened/analyzed/reviewed by Google Play first, in the same manner that production releases are. Internal Test releases become available immediately. When they came out with the Internal Test option (which has a limit on number of users), I offered it with the caveat that they're slightly riskier because of the lack of review and let users decide which group to be in.
  4. Looks like the standard beta hasn't cleared Google Play's review process yet. Sometimes it clears within an hour, sometimes it takes over a day.
  5. A new SignalCheck beta is rolling out now and should be available on Google Play shortly. It includes some new user-suggested features and several bug fixes. One change that should be noted is that secondary SIM cells are no longer logged by default; there is a new option under the Beta Crew menu to re-enable it if you prefer. I have not been able to get Dual SIM logging to be reliable yet, random entries mix and match the provider details and SIM number. Hoping this at least resolves the issue with inaccurate log entries for the primary SIM. Will continue to work on that.. it remains the final hurdle to open up Dual SIM support for all users.
  6. I have workarounds that essentially do this, but it has taken some time to catch every instance in the code where things need to be adjusted, especially with dual SIMs in play. I have been making further improvements in a soon-to-be-released beta. I see this frequently as well on my Pixel 8.. unfortunately, I have yet to come up with a workaround because the OS is still reporting it as a valid connection; at least the timestamp freezes so you have a clue that something is up. I'm still trying to find the best way to handle this. I overhauled the site note editing/saving/querying functions in the aforementioned beta in progress.. "coming soon" Appreciate all of your feedback as always!!
  7. Sorry for the delayed reply, I missed the notification.. SignalCheck doesn't really 'control' how quickly the information refreshes. To oversimplify it, the app listens for signal changes, and displays them as soon as they happen. The rate depends on many variables, including device configuration, power status, radio programming, etc. The biggest driver of updates is flowing data -- if your device is idle and also not moving, not much will change because it's not going to "waste" effort updating signal metrics. But if you are sending/receiving data (streaming audio or video is a big trigger), or your location is significantly changing (drive faster for more frequent updates.. just kidding), you should see more frequent updates. I don't know the inner workings of Cellmapper, but it's likely designed in a similar fashion; there is no native accessible "force the modem to refresh the information" command that I am aware of, but there could be. If you notice quicker updates when you have Cellmapper running, it could be because Cellmapper is sending/receiving data (I know there is an auto-upload function), or Cellmapper is configured to use more precise location information, so your device is more sensitive to smaller movement. You can adjust SCP location settings under Preferences > Location Settings; if you increase the priority or decrease the update interval, you will get more accurate and more frequent location updates, but be aware that this may increase battery usage. Hope all that makes sense! Feel free to let me know if I can clarify anything further.
  8. I've been very busy with other priorities lately, but I'm still keeping an eye on things!
  9. I immediately noticed their subtle dig at the "second most iconic" venue.. presumably they are saying #1 is, of course, T-Mobile Arena down the street. 😆
  10. A server update impacted SignalCheck diagnostic reports that were sent from 12/30/23 until a few minutes ago. If you sent something of value, please re-send it when you can -- it was never received. Sorry for the inconvenience!
  11. An update to SignalCheck Pro is rolling out now to all users, and should be available on Google Play shortly! Here are the highlights of version 4.83: Added option to control LTE/NR TA display when reported value is 0. Added option to control LTE-TDD TA correction. Adjusted Dish Wireless 5G-NR site notes to be unique per sector (instead of per site) until proper site note linking can be implemented. Previously logged Dish Wireless note entries may be incorrect. Improved identification of unregistered 5G-NR cells. Improved permission request handling. Resolved issue with blank display on devices with restricted permissions. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with invalid LTE/NR data displayed on some Motorola Edge devices. Resolved numerous force closes, mostly related to permissions that were not granted by the user. The full changelog can also be viewed here. I appreciate everyone's feedback and support!
  12. Updates to SCP are rolling out now, including a new beta with some minor bugfixes. An update to the public app version that aligns with this beta is also being released today. Thank you for all of your support!
  13. Another minor beta update rolling out now.. a few more bugfixes, mostly further adjustments to permissions requirements. Hopefully this resolves all of the remaining permission-related issues..
  14. Another SCP beta update is rolling out now with a few more bugfixes. If this version proves to be stable, non-beta users can expect to receive it later this week. Thanks for all of the feedback and support!
  15. Thank you for the detailed testing results and for sending diagnostics! I was able to identify what was causing those crashes, the fix will be included in the next update.
  16. Thanks! There have been some recent changes to Android permissions requirements that were not documented very well and caused a tremendous amount of problems, especially for users who recently updated to Android 14. Thankfully I have some decent monitoring and diagnostics in place so I was eventually able to figure out what was going on. I'm basically looking for testers to mess around with revoking/denying/granting permissions to make sure the app doesn't crash and the workflow/warnings are reasonably clear. I do know that if you revoke/grant permissions while the app is in use, the app sometimes requires a restart (or at least as swipe out and back in) to get the proper prompting, but it's difficult to control 100% of the scenarios with the amount of background work SCP does with methods that require special permission.
  17. A new SignalCheck beta release is rolling out now.. this includes several bugfixes, notably issues on Android 10+ devices when Location permission was not granted, and on Android 14 devices when "Allow all the time" Location permission was not granted but the app was configured to launch at device boot. Please test this version by temporarily revoking permissions for SCP and ensure the app does not crash -- it will not work very well due to Android security requirements, but that's the point..
  18. Thanks, this bug was brought up in the beta thread and there is an open ticket on the issue tracker for it -- your Reddit post is part of the discussion! I have a temporary workaround in testing getting rolled out soon, and will be working on a full solution.
  19. I saw someone in the Reddit thread mentioned that disabling 2G under network settings made an improvement. My 2G setting is disabled, FWIW.
  20. I have not experienced this on my Pixel 8 with T-Mobile eSIM. That thread appears to mostly be P8 Pro users, although I believe they both have the same radio hardware.
  21. A SignalCheck beta update is rolling out now. It includes additional temporary adjustments to resolve improper site note linking for Dish Wireless 5G-NR connections, as well as a (potential) improvement in 5G-NR cell identification, specifically for cells that the system is reporting as "unregistered" for various reasons; this may resolve issues several users have seen with delayed 5G information
  22. If you are still experiencing this issue, could you please send a diagnostic report (from within the app, select Help > Send Diagostics) and include a brief note about the issue so I can dig into it further? Thanks!
  23. Thank you for the detailed info on this! A fresh beta update is rolling out now that temporarily changes how site notes are saved on Dish Wireless 5G-NR connections. Dish site notes will now only be updated on the specific NCI you are connected to, so other sectors at the same site will need to be saved independently -- but at least that stops further bad data collecting in your logs. I will work on restoring normal site note functionality using the formula you shared, just going to take some time.
  24. Hmm.. my primary daily device is a Pixel 8 (and was a Pixel 7 for the year prior) and I have not seen this. Do you have any sort of memory optimization app running? Do you have timestamps enabled for the individual network types (not at the very top of the screen, but within each "block" of signal information) and are they updating at all?
  25. They were getting crushed over it.. I struggled to reach T-Mobile customer service on Monday to activate a new phone. Dialing 611 did not work, calling the 800 number went to a recording saying they were currently experiencing technical difficulties and could not take calls, app chat went unanswered, and it took 2 hours and a public tweet to get a Twitter DM to go through; usually you at least get an automated response with a link to verify your account immediately, that wasn't even happening. The representative acknowledged it and basically said they were overwhelmed.
×
×
  • Create New...