Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,264
  • Joined

  • Last visited

  • Days Won

    186

Everything posted by mikejeep

  1. Another SCP update for the Beta Crew is rolling out now! All of the file operations have been overhauled, including import/export/backup routines as well as many things behind the scenes. Each user needs to click on Logs > Select Log Folder to configure their default folder for exported log files to reside in. It can be changed at any time, and this folder will not be deleted if you uninstall the app. Most existing users will probably be content with selecting the /SignalCheck folder from previous versions, but it's completely up to the user now. A new option has also been added for non-beta users to export data files to be manually processed on the mapping site. This is a temporary band-aid until beta testing of the mapping feature is complete (and I get password authentication working from within the app). Beta users do not have this option, as the much simpler Upload option replaces it. Any feedback would be appreciated! Thanks!
  2. I believe that /Android/data is only supposed to allow access to the app you are using; ie if you are using SCP, you should only be able to access the com.blueline.signalcheck folder. But while I can see most folders on my phone from within SCP, I can't see that one. Very odd. I am working on it!
  3. Sorry about this; I'm unable to replicate this issue, but it's certainly possible given the current state of things. I'm halfway through overhauling all of the file routines; when I'm done, my intent is to display the native Android file picker instead of the custom one in SCP. New Android security rules really limit what third-party apps have access to without explicit user input.
  4. Another update to the update already rolling out! Log import/export/backup was not working properly due to a permissions reconfiguration. You will likely need to re-approve storage permission the first time you attempt to import/export/backup again.
  5. A new release for the Beta Crew is rolling out now! Fixes for map uploads, 5G info improvements, and more. Android 5.0 is now the oldest version supported. Full change log is available in the app or on the website. Significant changes had to be made to the file system routines; CSV exports, database backups, and failed uploads are now saved in /Android/data/com.blueline.signalcheck due to Android security requirements. Please note -- this folder is deleted if the app is uninstalled, so be sure to copy important files elsewhere! If you have the previously-used /SignalCheck folder on your device, that will remain intact if you uninstall, but no new files will automatically be added there. I am working on an option to let the user choose where to save items, but for now that new folder must be used. Thanks!
  6. FYI -- I am aware that some users (including me) are unable to upload map data due to new Android security rules that were either implemented in the December Android update or some other OTA update. It also impacts the ability to import/export/backup logs. I am working on a fix..
  7. I finally got my hands on a Pixel 6 and started using it this week. I was able to get SCP working, but there are some issues beyond my control that will need to be resolved with future system updates. No LTE or NR neighbor cells are reported, and NR NCI appears to always be invalid. I will file a bug report with Google and update this post with a link for upvotes.
  8. I tried so many avenues.. kept getting different answers as to why I had to call a different number. Chat, Twitter, magic box, regular support.. finally got someone to open a tech support ticket for it. Apparently nobody knows what a CellSpot or an Airave is, and when I finally got someone who did, they couldn't access my account because it's SWAC. Supposedly I'm getting a callback eventually, but I'm not optimistic. They basically said the coverage map showed good service in my area (it's a farce.. can't even make calls driving through town) so there was nothing they could do besides troubleshoot my device. Nobody would listen to my claims that my indoor coverage got even worse when I switched to TNX. 1X800 wasn't great but at least MMS/SMS worked. Now I can't even get that. Wifi calling works, but SMS/MMS doesn't seem to work unless I have a mobile connection also. The texting issue is my only real problem at home.
  9. Are CellSpots still working/available? T-Mobile told me that was not an option for me when I called about my Airave deactivated.
  10. Most of the native API methods were added in Android 10, but not every manufacturer takes advantage of them immediately. Your report showed there was no cell info at all being reported by the standard methods at the time of your report. You should've seen NR signal strength because the app appeared to be catching that through a different method.
  11. I just have not had time to create all of the necessary icons and implement it yet. It's on the list!
  12. Others have explained it in better detail in this thread and various others, but manufacturers/providers have basically decided to display the 5G icon when you are connected to a 5G-capable site, regardless if you have an active 5G connection or not. To me, it is very misleading. You shouldn't need an app like SignalCheck to see the truth. As far as seeing the 5G band, yes it is because the device/OS is not reporting it. When on non-standalone 5G, it's rare to see much more information than what you had in your screenshot. If you had a standalone connection (no LTE anchor), you would see full information with band and site ID. Since updating my Pixel 5 to Android 12, it is frequently reporting band info on NSA -- but as a bogus neighbor cell. I'm working on recognizing that and getting it working for the next app update.
  13. Yes, over the summer, although it doesn't sound like customers were notified. I'm unhappy because Sprint MMS does not work over Wi-Fi and there is no replacement femtocell coming.
  14. This.. I'm currently working on changing the upload progress window to a pulldown notification instead. It'll stay out of the way but be visible if you want to see progress. And any errors/responses will be in your notification shade until you choose to clear it.
  15. After 7 months of beta testing, an updated version of SignalCheck Pro has finally been released! Version 4.68 is now live on Google Play for all users. It includes tons of bugfixes, significant 5G-NR improvements, and other things that will make your day better. The full changelog is available at https://signalcheck.app/change-log. Please feel free to post here or reach out with any questions. I appreciate everyone's support (and patience), thank you!
  16. Sorry, I missed this post earlier -- most mobile providers are now displaying a "5G" logo in the system bar when you are connected to a site that has 5G-NR capabilities, but it does not mean that you have an active 5G-NR connection. It's very misleading, but it seems like all of the major companies are doing it now. I looked at your reports, nothing indicates that you had a whiff of 5G at the time. Keep hunting..
  17. I experienced that myself a couple days ago, working on a resolution! I may move the uploading pop-up to an Android notification.. we'll see. For now, you should be able to get around it by clearing SCP from your recent apps and then reopening it.
  18. Those of you having issues with SCP -- how large are your log databases? Check Logs > Statistics.. maybe different size DBs are the reason for different stability levels?
  19. Another SignalCheck release for the Beta Crew is rolling out now! Fixed the stale location filtering (it didn't work in the last release), adjusted the scale of the graphical signal strength bars (15-35 dB stronger now required to max out), and some internal cleanup. Still not sure what's going on with those Samsung crashes. Please feel free to continue sharing any information you think may be relevant. Hopefully this release will be able to roll out to the public as well (web mapping data will still be limited to the Beta Crew for now). Thanks for all the help!
  20. I have not been able to nail down these issues.. nor can I replicate them. Not seeing crash reports that seem to correlate either. I'm hearing you and trying to figure it out, presumably something with the S21 stock firmware is wreaking havoc with something I'm doing. There are a couple of Samsung devices experiencing issues more frequently than I'm willing to accept, I just can't figure them out.. yet..
  21. I'm always interested in diagnostic reports, feel free to send! Are you only seeing the system 5G icon, or are you seeing 5G information displayed in SCP? If it's standalone (LTE+5G), you will only see signal strength information. 5G cell ID info is only reported with standalone connections.
  22. I will look into it; the method I implemented is not supposed to pester users, but I certainly could have done something wrong. I do not have an entry for 313690, so "T-Mobile" is what was being reported to the OS. I'll add an entry for that PLMN.. what would the most useful designation be? I intend to do it this week, with the version that went out to the Beta Crew a few days ago -- just need to ensure there are no lingering problems. So far it seems stable! It's still on the list!
  23. A fresh update for the Beta Crew is now live on Google Play! There are two significant changes, among some other smaller bugfixes: * If the device location is more than 10 seconds old, the accuracy will be recorded as "999" in the trail log. This will prevent entries with stale locations from being included in web uploads, and also be easy to quickly identify when looking at logs. * Fixed 5G-NR cell ID display; the values were previously wrong if the selected user preference was an option with sectors. A new hex cell - hex sector display option for IDs was also added. As always, any feedback is appreciated and thanks for your help!
×
×
  • Create New...