Jump to content

mikejeep

Honored Premier Sponsor
 View Profile  See their activity

  • Posts

    3,284

  • Joined

  • Last visited

  • Days Won

    197

 Content Type 

Everything posted by mikejeep

  1. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    Mine seemed to be better too, but I wasn't sure if I was paying close enough attention.. it would be awesome if it was resolved.
  2. mikejeep
    Interesting.. if the timestamp is updating, that means SignalCheck is getting an update from the OS, and 3-10 seconds between updates is very normal. However, the information not changing when the timestamp changes is obviously an issue. If anyone experiencing this could submit a diagnostic report from within the app, I'd appreciate it -- want to see if it's limited to certain makes/models/builds. I am not able to replicate it with a Pixel 3 on AT&T or Pixel 4 on Sprint.
  3. mikejeep
    Thanks for the info.. unfortunately it does seem to be a change in Android 10. I'm trying to see if there's anything I can do about it. What device do you have? I don't experience it with my Pixel 3 or Pixel 4.
  4. mikejeep
    There's no signal or cell ID info being reported, but I found a different approach to try.. unfortunately it doesn't give anything useful other than a status flag. Not convinced it's entirely accurate yet, but that's where you guys come in!
  5. mikejeep
    Your report was on time, but there's no 5G data showing other than that status flag I made up. Keep an eye on it if you can.. let me know if that seems to appear and disappear with the 5G status bar icon or not..
  6. mikejeep
    1) Did this just start with the latest update, 4.58? 2) If you enable the timestamp display, does it appear to be refreshing even if the data stays the same? 3) When moving at a decent speed/distance (traveling in a vehicle), does the behavior change at all?
  7. mikejeep
    Glad to hear it is fixed, thank you! On the beta, you can now more clearly see any raw 5G info on various sections of the diagnostic mode screen, although in the current implementation you should see it on the main screen if there was anything there. I intentionally don't have a lot of filtering in place yet.. it's very basic until I can see how it behaves in the real world.
  8. mikejeep
    I may have found a band-aid fix that will resolve the import/export issue temporarily. New beta release is processing and should be available on Google Play within the next hour or so. I also decided to unveil some very basic 5G data, although I do not expect many devices to see it yet. It will appear below the LTE information if there is any data available; please send a diagnostic report if you see it!
  9. mikejeep
    I discovered the problem and will be working on it, but it will likely be several days before I have something ready for beta testing.
  10. mikejeep
    As I mentioned previously, if your device is not moving and the signal is stable, newer versions of Android will not update the signal strength as frequently in order to conserve power usage. The latest app update moved the target API to Android 10, which implements this behavior stronger than previous versions. Next time you are moving around at a faster speed and longer distance (car, bus, train, etc), see if the updates are more frequent. I often have to hop in my car and drive around to test, because sitting at my house the updates are as infrequent as you describe -- it's just how Android behaves now.
  11. mikejeep
    There is an issue impacting some Android 10 devices where log files cannot be imported or exported despite the appropriate permissions being granted. Users will see an error message about files not found or permission denied. I am looking into the matter, but if you experience it and have not already been in touch with me, send a diagnostic report from within the app. That is the best way for me to see all of the pertinent information about your device as well as any error messages or permissions issues in the background. Thanks! EDIT: I discovered the problem and will be working on it, but it will likely be several days before I can get it finished. Thanks for your patience!
  12. mikejeep
    Thank you for all the detailed info.. I'm suddenly getting a lot of messages like this, and I don't know why. The diagnostic reports aren't showing any crashes and all appropriate permissions are granted. The issue appears to be limited to some Android 10 devices but not all, but I can't figure out why. I'll keep digging into it and hopefully have some answers soon.
  13. mikejeep
    Grabber is correct. Support for 5G information was added in Android 10, but I have yet to see a device reporting 5G information via the API so far. Once I get an example of that, I'll be able to do something useful with it in SCP. Devices showing the "5G" icon in the status bar are using something the mobile provider has baked into their software. Users can help me out by submitting a diagnostic report while connected to 5G (About > Send Diagnostics). I don't need multiple reports from each user, but each time you get a software update it could be useful.
  14. mikejeep
    The information displayed on system screens like what you see with *#0011# often comes from proprietary methods that third-party apps do not have access to. SignalCheck is only able to display what the OS reports. When you say "the rsrp updates just as same" do you mean that LTE RSRP is updating frequently in SCP but nothing else is? The lack of SNR would be because your device is not reporting SNR. Many devices do not report it unfortunately, or sometimes it will be available on certain software updates but not others. As I asked previously -- do you see the same lack of updates when you're watching the app while driving in a car? Or does it update more frequently?
  15. mikejeep
    Apologies for a delayed post, but another update to SignalCheck was released a few days ago, version 4.58. Here are a summary of the changes: Changed exported logs to use preferred LTE Cell ID display format. (Pro) When exporting log files, the "gci" column will now format the cell ID to match the user's setting under Preferences. Updated permissions to require ACCESS_FINE_LOCATION for all functions. Android has changed the requirements to obtain signal information from "coarse" access to "fine" access. This mandatory change is beyond the control of third-party developers. SignalCheck Lite brought up-to-date. The Lite version was old but stable, however an update became a priority when it failed to work properly on Android 10. Pro will continue to receive priority updates, but Lite will remain functional and be maintained as necessary. Long-term goal is to combine the two apps into one, with Pro-level features limited to users who have purchased it. Other less-significant, self-explanatory changes: Improved compatibility with accessibility services. Resolved force close when attempting to send diagnostics on some devices. Resolved internal exception when notification sounds are missing. (Pro) Resolved issue with all WCDMA neighbor cells reporting -120 dBm on some devices. (Pro) Resolved issue with missing information when connected to Wi-Fi Calling on some devices. Updated external libraries for root functions. (Pro) Updated target API to Android 10. As always, thank you for your support!
  16. mikejeep
    I reviewed your diagnostic report, nothing appeared to be out of the ordinary. Are you sure it is frozen, or are there just long delays between data updates? If your device is not moving and the signal is stable, newer versions of Android will not update the signal strength as frequently in order to conserve power usage. The latest app update moved the target API to Android 10, which implements this behavior stronger than previous versions. Do you see the same behavior when you're watching the app while driving in a car?
  17. mikejeep
    Thank you very much! Definitely didn't notice the Pro at the top, so used to seeing that.. I'm still wrestling with the best approach for BW, CA, and TA, since they can be quirky and are more "bonus" features good to keep on the Pro side. But it's also nice to not frustrate users who upgrade expecting it to be flawless. Debating between an explanatory pop-up and adding a limited Preferences menu on Lite so users won't see it until they enable it, where I can out explanatory text like I do for Pro.
  18. mikejeep
    No worries! I kind of jumped the gun by posting before it was published and should have been more clear, sorry about that. It's completely separate from SignalCheck Pro, so most of you won't have it installed already. EDIT: It should be live now, but ensure you're enrolled in the beta and see version 4.572Lb.
  19. mikejeep
    Thanks! Is that the new version released today? I'm not sure if it became available yet.. should be version 4.572Lb? Please send me a diagnostic report if it is.
  20. mikejeep
    Slightly different request for help today.. I have finally(!!!) updated SignalCheck Lite, after several years of dormancy. It was stable and didn't need a lot of changes until Android 10 made it completely unusable. Anyone on the SCP Beta Crew is automatically able to opt-in for the Lite Beta as well. The update (version 4.572Lb) should be available shortly.. could you please take a few minutes to install and test it, to make sure it is stable? https://play.google.com/apps/testing/com.blueline.signalchecklite (edited link) The code is nearly identical to Pro, but with many components removed. Once you verify it is working, you can uninstall Lite to minimize confusion. Please send me a brief comment (here, PM, email, whatever) after you give it a try and let me know how it looks. I do not expect any issues, but I want to make sure it is stable before it goes out. Thanks!
  21. mikejeep
    On recent versions of Android, you are not likely to see it update every second except for in specific scenarios, but I'm glad it's updating regularly for you! For the benefit of whoever is interested.. signal updates from the OS are likely to be more frequent (but not guaranteed) if your device is moving fairly quickly (ie in a vehicle), and you are actively transferring data over the mobile network. When the connection is idle (including when you are using another connection method, like Wi-Fi), some things are not updated as frequently. Android does not publicly state anything much more specific than that. In reality, the signal strength is constantly changing, every millisecond, faster than the screen can even update.. but there's no reason for any mobile device to monitor it that intensely, the CPU and power impacts would be crazy. An overwhelming majority of mobile users don't even need it updating even every 10 seconds. As of last year, over 314 million Americans had mobile phones.. with some quick math, SCP is on less than 0.0032% of them 😆
  22. mikejeep
    That's no fun. Unfortunately it sounds like something with your device? I don't have any control over the speed at which the OS provides data updates.. the OS tries to balance power usage with the likelihood of changed data being available, and I can't do anything to force it to refresh any faster. Even if I put a manual "refresh" button to re-query the API (as many people have asked for), it would simply show the same data already present. SCP automatically refreshes the screen when the OS reports there is new data.
  23. mikejeep
    Already pushed out a new beta this afternoon! When exporting logs, the LTE cell ID will now be formatted to match whatever your preference is (hex/decimal/hybrid). Also fixed WCDMA neighbor cells not reporting valid signal strength. The biggest changes were behind the scenes and not visible to end users, but were fairly significant in terms of potential impact.. I wanted to share it fairly quickly so I can make sure I didn't break anything before I continued working on other things.. if anything appears to have gotten worse, let me know.. I'll be watching for automated crash reports too. Thanks!
  24. mikejeep
    An update to SignalCheck Pro is rolling out shortly and should be available on Google Play within the next several hours! This version includes many bugfixes; the full changelog is below with some details added about the most significant changes. Still working on full dual-SIM support; not sure when that is going to be ready. Thank you for all of your support! Added option to choose LTE cell ID display format: GCI, ECI, or hybrid. Based on user feedback, there is a new option under Preferences > Display to determine how LTE cell IDs are displayed. The default method is still "GCI", which is the hex ID most users are used to. "ECI" is a decimal version of the hex ID that some users asked for in the past; those who had previously enabled this option with a checkbox will need to re-select their choice. The new "hybrid" option displays the decimal ECI with a hexadecimal sector. This may be useful for AT&T and Verizon users because of the cell ID patterns implemented by those providers. (In my own testing, hex still appears to be the most useful for Sprint users). Resolved issue with missing CDMA data on some Android 10+ devices. This should resolve issues for Samsung users who recently updated to Android 10. Added option to display WCDMA neighbor cell PSC as hex. Resolved issue with PSC failing to be logged for WCDMA connections. The long-standing bugs with non-CDMA site logging should finally be resolved! Also, WCDMA PSC appears to be most useful as a hexadecimal value, so an option has been added under Preferences > Neighbor Cells to display neighbor IDs as hex. Moved Neighbor Cells preferences to separate menu. Trying to improve the Preferences menu organization; some of the screens are getting very long. Other less significant changes: Added additional indicators for AT&T LTE iDAS and small cells. Improved efficiency and stability of internal databases. Minor adjustments to action bar menu icons. Removed outdated references to nTelos. Resolved force closes related to missing resources on some devices. Resolved force closes when accessing Purchase menu with background service disabled. Resolved issue with invalid CDMA Ec/Io values displayed. Resolved issue with LTE band alerts not triggering when band changes. Resolved issue with LTE band alerts triggering for invalid bands. Resolved issue with some AT&T LTE band 66 connections displaying as band 4. Updated Shentel LTE indicators.
  25. mikejeep
    New beta update will become available shortly.. only notable change from the last beta is that the cell information displayed on the popup when editing a site note is more useful. A public update is also rolling out tonight that will include all of the fixes from the last two beta versions thanks to all of your help. I appreciate it!
×
×
  • Create New...