Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,264

  • Joined

  • Last visited

  • Days Won

    186

 Content Type 

Everything posted by mikejeep

  1. mikejeep
    Another SCP beta is rolling out now and should be available shortly. Lots of bugfixes, but also includes 2 notable changes. The existing site note lock option has been adjusted, and now locks the Location/Site/Trail icons so they can't be clicked accidentally. (Sorry @Trip, it's all one option.. for now!) A new option has also been added that allows you to change the "chunk" size of web data uploads. Hopefully this will be stable enough for public release.. let me know!
  2. mikejeep
    It's new in this beta round.. just realized this isn't the beta thread.. oops. Coming soon for everyone else! 😁
  3. mikejeep
    Sure! Sorry that feature made it worse for you.. didn't think of potential issues with curved screens. I'd like feedback from anyone interested: Would be appropriate to integrate it with the existing option that locks site notes (so accidental touches don't open the note prompt)? Or would it be better if locking out the buttons was separate? I try to keep it simple, but perhaps there's a case to be made for keeping the options separated. EDIT: In the meantime, you can add edge padding to (temporarily) resolve it now if you want.. see Preferences > Colors and Styles > Main Screen Layout Padding.
  4. mikejeep
    Short answer: I'm not smart enough to answer this with certainty. Long answer: Sent you a PM. 😁
  5. mikejeep
    Another SCP beta is rolling out now, should be available shortly! It took longer than I planned, but the bugs involving NR web data and importing log files have been squashed, and there are more improvements to the web data uploader. Keep the feedback coming.. thanks for all the support (and patience)!
  6. mikejeep
    E-mail me the file (support [at] signalcheck.app), happy to take a look and get it fixed!
  7. mikejeep
    Hmmm.. it's not throwing any errors in logcat at all. Can you send me that file so I can try it myself and see what's going on?
  8. mikejeep
    Hmm, I did implement a fix for the NR table error in the overnight update, but maybe there's something else too. Is it the same exact error on your screen? Your diagnostic report didn't have anything logged, can you try the import again and then send a diagnostic shortly after?
  9. mikejeep
    New beta rolling out now, should become available shortly.. fixes some bugs reported this week, as well as improvements to the data uploader status display. Full changelog in the app or on the website as always. Thanks for the feedback!
  10. mikejeep
    I found the issue -- the nr_sites table is missing (because it didn't exist back then, of course) so the import fails -- so it is another bug! I'll work on fixing that, but if you have the ability to add that table (it might need the same column structure, I haven't run into this so not positive), that might fix your issue. Or you can send it to me and I can.
  11. mikejeep
    "IWLAN" displays on some devices when Wi-Fi Calling is active; you can also see that it is active by the Wi-Fi Calling icon lit up in SCP (the handset with the radio beams). The -24 signal is an Android bug that appears on some devices when you're on a non-LTE, non-CDMA connection (HSPA/HSDPA/HSUPA/UMTS/etc) -- I'm trying to implement a workaround for it, but the other cell info displaying should be valid.
  12. mikejeep
    Even if the structure changed, it should still import -- can you try again and then send me a diagnostic report? That should capture the error details. I can take a look at the file as well if you e-mail it to me, but the diagnostic will be most helpful.
  13. mikejeep
    A new beta release of SignalCheck Pro is rolling out to the Beta Crew now! It should become available within the next few hours. Opening/closing the app or checking Google Play should prompt you to update. Lots of bugfixes and some new features. Check the changelog for full details.. looking forward to your feedback!
  14. mikejeep
    Interesting. Certainly could be an Android 11 hiccup.. please keep me updated if it keeps happening. Rebooting is always the quickest and most likely resolution when things are stuck on stupid!
  15. mikejeep
    Thinking a little more about this -- the geocoding feature that translates coordinates to a street address is separate from the actual location service that gets the coordinates. There are limits on geocoding requests (the specifics are not published), but I had never run into them and I expect if that was the issue, it would display an error instead of an address. Having one address constantly returned makes me think your coordinates are not changing, so the geocoder is working but not getting any new information. If it happens to pop up again, and you have the coordinates displayed on the main screen, try driving around to see if they change or if they are frozen. There are some minor improvements coming to the location service in the next update; not sure if it would be something that corrected an issue like this though.
  16. mikejeep
    Interesting.. the location is provided by an API that shares device location information between all apps that request it. What are your location settings in SignalCheck? Did you happen to try opening another app that uses location features (Google Maps, Waze, etc) when you were having that issue?
  17. mikejeep
    Others are having issues with recent S20 updates and SCP as well. Unfortunately I'm not getting any crash reports at all about it. If you disable battery optimization for SCP, others have said that resolves it. Have you tried that? What error does it show when you try sending a report?
  18. mikejeep
    Hmm that looks like NSA 5G with LTE information missing, since there is no 5G cell identity info.. but who knows. Send a diagnostic and I'll see if it's hiding anything good behind the scenes!
  19. mikejeep
    Ugh.. new beta coming very soon, not sure if I've solved anything but who knows.. still no crash info coming in.
  20. mikejeep
    I'm very interested in this too.. I thought this was the type of feature that would only be available with RCS -- which Textra can't support yet because the API hasn't been made available to third-party developers. The only RCS client I think is available right now is the Android Messages app. I'd love to know the reason behind this!
  21. mikejeep
    Hate to be a pest, but bumping in the hopes someone can resolve this. I really miss my S4GRU notifications.. as far as I know, Tapatalk is the only way to get those while mobile.
  22. mikejeep
    Android 7 is old, but it employs less aggressive power-saving measures so I don't think your issue is related to that particular factor. Not all devices reported full LTE info on Android 7, but if you're seeing all the information then you shouldn't have too many significant concerns. I sent you an e-mail about this: have you tried enabling the "Use Stale Data Workaround" option under Preferences > General?
  23. mikejeep
    That is solid troubleshooting, thank you very much! I am still perplexed as to what is causing this. Have you tried disabling the battery optimization option for SignalCheck in your system settings?
  24. mikejeep

    Google Pixel 5

    mikejeep replied to mikejeep's topic in Google

    My Pixel 5 behaves the exact same way.. I believe that is normal ROAMAHOME behavior. It rarely hits my Airave, only when it completely loses T-Mobile signal.
  25. mikejeep
    Those of you who are experiencing this issue -- is there a chance it is occurring when you are connecting to a non-LTE, non-CDMA cell such as HSDPA/HSPA/UMTS/etc?
×
×
  • Create New...