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
    Yes, I will be adding full 5G support.. but at the moment that is third in line behind finishing Dual-SIM support (I have to re-write all of the cell routines, rather do that first) and major bugfixes (GSM notes/logging broken, Sprint B41 +1450 offset fixes, etc). Also, if Android follows its history, API support will be mediocre to start and only limited devices (none of which I physically have for simple testing) and areas (not mine yet) will utilize it. I do intend to get at least basic/crude 5G functionality implemented in the near future. -Mike
  2. mikejeep
    Another SCP beta release is rolling out on Google Play.. lots and lots (LOTS) of behind-the-scenes changes and bugfixes -- there shouldn't be any obvious impacts, but please keep an eye out for crashes/problems. Groundwork for dual-SIM support is getting there but not ready to be unveiled quite yet.. soon.. -Mike
  3. mikejeep
    Do you have the TA correction option enabled under Preferences? What I really need to do is get a decent sample size of B41 TA reports without the correction factor enabled, and record what the app shows and what the correct distance is. That would allow me to calculate what the proper correction value would be. TA is a funny beast on TD-LTE, I have always had a correction factor applied to the raw value.. so with the option enabled it's applying a correction to the correction.. 🤯
  4. mikejeep
    Rolled out another SCP update few hours ago, should be available to everyone on the Beta Crew by now.. finally finished several things I've been working on for quite some time: Added system shortcut for app system settings (easier access to permissions) Internal code enhancements to Location Service (aka it was completely overhauled to adopt newer best practices) Removed persistent prompts/warnings that appeared when a user denied background location permission but had the background service disabled, or requested not to be prompted again (it's a fine line between educating and annoying) Resolved internal exception when installing/updating the app (hopefully??) Resolved issue with incorrect signal strength notification icon when connected to LTE & Wi-Fi Calling The biggest things to watch for are issues with Location Service failing/crashing/etc or if anyone still sees the wrong signal strength in the notification bar when you are on Wi-Fi Calling. This is more related to the last update, but does anyone have feedback on how LTE TA distances are looking? Mostly curious how accurate B41 appears to be, with and without the correction factor applied.
  5. mikejeep
    So you are seeing the same BSL on 1xRTT that you saw with your Airave? Is that BSL the same one you see when on 1x800 now? If you submit a diagnostic report (About > Send Diagnostics within the app) the next time you're on 1xRTT, I can see if there's anything giving any indications behind the scenes. Make sure you out your username on the report. -Mike
  6. mikejeep
    Another update to SignalCheck Pro is rolling out on Google Play now for all users (4.551), it should resolve the issues with missing information on Android 10 devices that started with the update a few days ago (4.55). It will become available as soon as Google finishes processing it, likely within the hour. If you have not updated to 4.55 yet, you would be better off waiting a few minutes for 4.551. -Mike
  7. mikejeep
    Thanks for the quick reply, I appreciate it! I just took a 50-mile drive just to test the app out and I'm also seeing a huge improvement. Going to push it out to the public right now.. it's definitely an improvement if not a complete fix fixed. -Mike
  8. mikejeep
    A new beta update went live about an hour ago.. please give it a try and let me know if it fixed anything. Thanks! -Mike
  9. mikejeep
    Anyone from the Beta Crew seeing obvious problems with the latest SCP update? Likely on Android 10? Many (including myself) are seeing no cell data, or data that suddenly stops updating or appearing. I've been flooded with reports but I didn't notice any from this group. I'm likely going to be pushing out an update shortly that makes one adjustment that I think is causing the major problem -- setting the compiler target to API 29 (Android 10). I'm going to try rolling it back to API 28 and see if things return to normal. From a developer standpoint, the Android 10 network routines appear to be a disaster. Several long-established parts of the API are simply not working as designed. My best guess is they went too far trying to limit background processes to save power, but that's pure speculation on my part at the moment. Reporting bugs to the Android development team is a long, slow process but once I can narrow things down a bit I will do my best. This may be a bumpy road. -Mike
  10. mikejeep
    I am aware of issues with the latest update inconsistently showing data in certain circumstances. It appears to be limited to LTE connections on some Android 10 devices. I'm looking into it.. a diagnostic report (About > Send Diagnostics) including your email and a brief description of the issue when it's happening is the most helpful way to report this. Thanks! -Mike
  11. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    I was apprehensive about losing the fingerprint reader but after a few weeks I've forgotten about it. Face unlock is very fast. If my phone is on my dash mount and I glance over at it, it unlocks immediately. It's almost too sensitive for my preference.. I adjusted my settings so it will not unlock or wake up unless I tap the screen first. Sent from my Pixel 4 using Tapatalk
  12. mikejeep
    The latest update to SignalCheck Pro will be available on Google Play within the hour! Here is a summary of the notable changes: Added limited recognition of 802.11ax Wi-Fi connections. Added option to add padding to the left and right borders of the main screen. Added prompt to warn users if background location permissions have been denied. Changed optional correction factor on LTE Timing Advance (TA) value to also apply to TD-LTE connections. Improved Android 10 compatibility. Resolved force closes on Samsung Android 10 devices. Resolved force closes related to exiting the app. Resolved issue with duplicate notification channel entries. Resolved issue with missing WCDMA data on certain devices. As always, thank you for your support. I hope everyone has an enjoyable Thanksgiving weekend! -Mike
  13. mikejeep
    New SCP beta just pushed out, should be available within the hour! Some major bugfixes.. please pass along any negative feedback as soon as possible, I would like to push it out publicly very soon. Here's the changelog: Added limited recognition of 802.11ax Wi-Fi connections. Added prompt to warn users if background location permissions have been denied. Optional correction factor on LTE Timing Advance (TA) value now also applies to TD-LTE connections. Resolved issue with duplicate notification channel entries. (*this may take a couple of app restarts to totally clear out, and your notification settings may be reset. This will not happen again in future releases.) Resolved issue with missing WCDMA data on certain devices. Thanks.. and Happy Thanksgiving! -Mike
  14. mikejeep
    My apologies for this. I have been spending a ton of time working on the next update, but I was not aware that the Android 10 crashing issue was so widespread until the past week. There are still some other outstanding issues I really wanted to resolve for the next public release, but I intend to push an update out later today or tomorrow that should at least get the app back to a usable state. -Mike
  15. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    Same exact things are happening to me here in the Boston area. It's becoming very annoying. I resisted from toggling airplane mode the other day and remained roaming for over 6 hours in an area I know Sprint has had good LTE coverage for years. It also seems to struggle to pick LTE back up on its own once it drops back to 3G.. even when in areas of extremely strong LTE signal. Airplane toggle usually grabs LTE immediately, but we shouldn't need to do that. Hopefully it's a software issue that can be resolved quickly. I have been trying to remember to report it through the My Sprint app, but not sure how helpful that really is.
  16. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    Is anyone else unable to disable the Hotspot once you turn it on? I am on the November update. Sent from my Pixel 4 using Tapatalk
  17. mikejeep
    What device? It's tested to be working great on several devices so far. Can you send me a diagnostic and share a screenshot? Sent from my Pixel 4 using Tapatalk
  18. mikejeep
    New beta finally rolling out right now on Google Play! No dramatic changes this time: Added option to add padding to the left and right borders of the main screen. Improved Android 10 compatibility. Resolved force closes on Samsung Android 10 devices. Resolved force closes related to exiting the app. I know there are a lot of outstanding bugs and requests; I am doing my best to prioritize my efforts on what is having the biggest impact on the largest number of users, and also squeeze in as many "quick" fixes/improvements that I can along the way. I am not dead, SignalCheck is not dead, everything is good -- just takes me awhile to piece together enough free time to produce a finished product worthy of release, even to the Beta Crew. I appreciate all of your support! -Mike
  19. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    The official release date is Thursday 10/24.. shipping labels might be printing, but I don't think anyone will receive a device before that date. -Mike
  20. mikejeep

    Pixel 4/4XL

    mikejeep replied to nexgencpu's topic in Google

    I pre-ordered from Google within the first few minutes it was on their site. Used my $50 credit from my P3 purchase, earned another $100 credit with this purchase. Should arrive by the end of the month, I picked free shipping despite my strong urge to get it a few days sooner. Happy it has more RAM than the P3 and happy the price stayed the same (with double the ordering bonus). Disappointed it's not 8GB RAM and disappointed it's not 5G.. I had almost no expectation of either of those things but it would've been a fantastic surprise. -Mike
  21. mikejeep
    Oh, I didn't know the A3 actually had one.. it definitely never really worked. To clarify further for others -- toggling airplane mode (or clicking the Reset Connection button in SCP) does *not* force the 1x radio to re-scan. Changing options under the band menu I referenced earlier does. -Mike
  22. mikejeep
    It is a menu option off the Radio Info system screen. The dialer code to bring that up without the app is *#*#4636*#*# -- it's also available as a SCP shortcut as well. -Mike
  23. mikejeep
    The issue with devices holding onto fringe 1x800 connections instead of the strong 1X connection from the Airave is common and incredibly frustrating. The Airave 2.5 had a 1x800 beacon that your phone would "see" and know to flip to it. There is no comparable feature in the A3 or A4, so until your device scans other 1X bands, it never lets go of the macro 1x800. The solution I have found works best for me is to force 1X to only use Sprint's 1900 MHz PCS network -- although that may not be in everyone's best interest, depending on the coverage in the areas you frequent. There is a shortcut in SCP to change this, go to System Shortcuts > Voice Band Mode and select "PCS". Understand that you will no longer connect to 1x800 and I believe 1X roaming will also be impacted unless the roaming partner uses PCS bands. To change back to factory behavior, simply go to that menu and choose "Automatic". You could also choose PCS each time you get home, and switch back to Automatic once it connects to the A4. -Mike
  24. mikejeep
    As Trip mentioned, the database is local to the device. You can use the database menu options within the app to backup/import/export logs. If you look at a populated log database, the format should be clear if you wanted to use your own data externally. All data from community databases needs to remain restricted to Premier areas only. No exceptions. -Mike
  25. mikejeep
    I replied in the main SignalCheck thread, but wanted to reply in both places so others can be aware -- I am working on an option for users to disable the offset. It's starting to get ugly behind the scenes with all these caveats, but can't really do much about it. I'd like to ultimately allow users to use filters or manual offsets to keep things up to date, but that opens up a lot of other issues. The information I had to this point was that B41 didn't need a correction, so it is not applied regardless of your setting -- my uneducated guess was that it had something to do with FDD vs TDD. More and more evidence seems to point to the need for a correction factor on all connections, regardless of device or band -- but I do have some users who are insisting it is more accurate without it. The issue is going to be when the Android devs fix this bug, everyone will suddenly have wrong readings again.. but I'm not holding my breath anyway. -Mike
×
×
  • Create New...