Jump to content

mikejeep

Honored Premier Sponsor
  • Posts

    3,255
  • Joined

  • Last visited

  • Days Won

    183

Everything posted by mikejeep

  1. Neither.. it's unfortunately an Android 13 bug that still has not been addressed. Please go here and "+1" the issue to help attract attention to it: https://issuetracker.google.com/issues/244063666 In the interim, you can select a different icon type in the app.. band, network type, or signal strength all still work properly. Icons that have more than one dynamic element are the only ones impacted by the bug.
  2. That's exactly why everyone has the option to change it to their liking It's probably worth repeating.. all [modern] apps utilize the same core location methods, so any data that is obtained is made available to any other app looking for it. So if you're running a navigation app whenever you drive (or even if you're just plugged into Android Auto but have a navigation app available to it), you're going to get updates about as fast as possible, regardless of your SCP settings. Essentially, only the "most aggressive" app running is actually controlling the refresh rate.
  3. I do not want to change the default location accuracy because that has a negative impact on battery, which is one of the most frequent complaints I already get with it defaulting to balanced. The option is there so a user can explicitly change if it they would like, and thus accept that they may see increased battery usage. Using high accuracy is not really necessary for most users. The location update interval doesn't guarantee an update every X number of seconds, it just sets the minimum threshold at which SCP will request an update. The actual frequency of location updates is based on various factors controlled by the OS, including if the device is in motion or not. The device must move at least 10 meters before it will ask for an updated location as well. If the user has another app running that uses location features that have higher settings enabled (for example, a navigation app), SCP (and any other app requesting location information) receives those same updates, which may be more frequent than the interval set in SCP. The current default is 4 seconds, but I'm willing to change it to 3, that seems like it is still a reasonable balance of power/accuracy that should not have a huge impact. I've always changed my own devices to 3. This default will only impact new installs and installs where the user never adjusted their settings.
  4. The impact of battery optimization settings varies significantly by device. My personal experience with Pixel devices is that SCP generally does everything you want it to even with battery optimization enabled; I have many reports of it performing notably better on other devices with it disabled. However, the other possibility might be that she didn't have at least moderate GPS accuracy during the trip. The app may have been humming along and recording all the data points in the trail log, but they are not uploaded to the map unless the accuracy of the point was 75 meters or better. If you have a navigation app running or set the SCP Location Service priority to high accuracy (which will use more battery), you won't have a problem. I probably have usable accuracy outdoors on the balanced setting approximately 85% of the time, but that can vary widely based on device/terrain/signal/wifi/movement/etc.
  5. Just working my way though all the bugs and diagnostic reports.. have come a long way with Dual SIM support this week too.. actually had it working briefly, but it still needs some work. Going to get back at it tonight. A heads up to all beta testers -- dual SIM support will likely be in the next update, and it will be a massive change. I would advise against updating immediately if you critically need the app -- I'm sure there will be some adjustments needed. I will make that clear in the release notes.
  6. A new SignalCheck beta is rolling out now.. bugfixes for Dish Wireless, pending web count display, and n2/n25 identification improvements.
  7. When you are uploading, a notification should appear with a progress bar while it's uploading, and then indicate it has completed as soon as its done, with a percentage showing how many of the data points were accepted. If you have a notification tone or vibration enabled, you'll get alerted when the process begins and when it ends. If you have the upload counter on the screen, it will refresh once another point is recorded or you can swipe out of and back into the app for an update. The counter isn't kept in real-time because it was such a drain on resources that it was causing crashes; it now updates passively. It should also update when you swipe down to refresh, but I know that is not working -- it's a bug I'm currently working on. That is already in the future plans, stay tuned..
  8. Here's a better thread for this: https://s4gru.com/forums/topic/8297-signalchecknet
  9. I have been doing some testing, and while manually entering *#2263# on my A32 works, trying to launch it from within SCP does not. Like most similar screens these days, a security exception is thrown and permission to launch the activity is denied. I tried to find another method, but it looks like others who have tried to do similar things have run into the same issue. It's probably locked down by Samsung and/or the OS. Sorry!
  10. Could you try again when you have a chance? I don't see any recent reports from you or any on AT&T n2 (or n25, ha).. thanks.
  11. Ah, this is what I was afraid of. There are so many glitches with the NR API, I have too many workarounds working around each other. The n25/n41 workaround is only supposed to kick in when connected to T-Mobile, but I did have to add some extra logic because the PLMN is also not properly reported consistently. Could you please send me a diagnostic report when connected to AT&T n2 when you have a chance?
  12. That is an OS screen.. what was SCP reporting at the time? n25 is live in many areas but the NR band reporting is not always reliable.
  13. Android no longer allows apps to fire off dialer codes, but if I can figure out the app package names and associated intents, I can work with that. This is a long shot, but if you happen to know them, feel free to share or send me a PM. I'll check my Galaxy A32 and see if it has those menus also.
  14. Another SignalCheck Pro update is rolling out to all users right now, Happy Holidays! It should be available on Google Play within the hour. This update includes several bugfixes and one notable new feature, a customizable shortcut button on the action bar along the top of the screen. The icon is a lightning bolt. It is configurable via Preferences > Colors and Styles > Custom Action Bar Icon; there is an option to hide it if you do not want it. I am open to suggestions for additional options to choose from, along with any other feedback as always.
  15. Another beta update is rolling out now, in conjunction with a public update. One new feature is live -- a customizable shortcut button on the action bar along the top of the screen. The icon is a lightning bolt. It is configurable via Preferences > Colors and Styles > Custom Action Bar Icon; there is an option to hide it if you do not want it. I am open to suggestions for additional options to choose from, but one-click data uploads will not be added as an option right now. I don't want anyone tempted to hit the button every 2 minutes quite yet..
  16. Not in the same way the Android Issue Tracker does.. my presumption is that these vendors would rather hear issues from the manufacturers that use their products, not end users. If I have an issue with my Cheerios, I don't complain to the wheat farmer, I go to the grocery store.. we'll see what happens. Another developer (Cellmapper dev I believe) has already chimed in with a counter-argument, hopefully it's productive.
  17. Disappointing news, the Android developer team just closed out the bug for incorrect NR bands as "won't fix" and blamed chipset manufacturers. This will make it much more challenging to get resolved. Please continue to let me know if you see incorrect band info and I'll implement as many workarounds as needed.. it's a hack I don't like, but there isn't really any other option.
  18. Oh I have diagnostics from others with a OnePlus that is reporting n25 but at 2600 MHz. Because of the Android band reporting bug and all of the other evidence in the wild, I trust the ARFCN more than the reported band so I implemented a workaround.
  19. Any that were reporting bogus info before.. 😁 Somehow some OnePlus devices are natively reporting n25 instead of n41. Totally different spectrum blocks, so I can't even figure out how the OS would get confused with that.. but it is happening..
  20. A beta update is rolling out now, includes bugfixes that I hope to release publicly this week.
  21. 47 is pretty good.. but there is no set number. It just "helps".. allegedly.. 🤞
  22. It's a known Android 13 bug.. not the app, and can't do much about it other than select a different icon type: https://github.com/bluelinepc/signalcheck/issues/18 Please give it a +1 on the Android Issue Tracker to help get it some attention: https://issuetracker.google.com/issues/244063666
  23. I have discovered a bug in the latest release that is causing force closes for users who have not granted proper Location permissions to the app. I hope to have a fix implemented soon, and will get it rolled out after a brief testing window. In the meantime, impacted users can avoid the crashes by granting precise location permission to SignalCheck (the app is severely limited without it anyway, although it should not crash).
  24. Haha yes it was.. but that's ok! I should've handled that scenario, it just never crossed my mind that a "Back to the Future" situation might come up.. 😁 Nice catches. I try testing all the possible scenarios and handle them gracefully, but it's tricky to plan for everything (see above). Did you happen to send a diagnostic when you got the funky error message? If you can make it happen again, that would help me identify exactly what I need to catch. Yes, this is something I know needs to be improved. I have it display the toast message that it's connecting to the server to let users know something is happening, because that was the quickest implementation I could get working. My goal is to display the login dialog box first, then some sort of animation placeholder while the network connection is working.
  25. Rolling out a minor beta update right now.. will hopefully resolve issues for users who imported databases from newer versions of the app than they were running at the time.
×
×
  • Create New...