Jump to content

SignalCheck Beta Crew Forum


mikejeep

Recommended Posts

20 hours ago, Trip said:

I'm now also getting the [null] error.  Previously I was getting the null pointer exception.  Definitely seeing my device (multiple times) on the web page.

Yeah that change was a result of the null moving from one point in the code to another with the latest update, ha. I'm digging into it. Appreciate all the quick feedback from everyone! Hopefully can figure out what is going on and resolve it today.

  • Like 3
Link to comment
Share on other sites

Rolling out a new beta release now with some minor adjustments and additional logging. Please log out of the app (or remove your session(s) from the website if the app is not providing the log out option) and try to log in again. If you experience an issue, please submit a diagnostic report immediately after your attempt. Logs only capture a limited amount of information, and sometimes a delay causes the useful information to already be overwritten.

I also sent an e-mail to the beta crew offering a faster way to receive beta updates, please let me know if you have any questions.

  • Like 2
Link to comment
Share on other sites

16 minutes ago, mikejeep said:

Rolling out a new beta release now with some minor adjustments and additional logging. Please log out of the app (or remove your session(s) from the website if the app is not providing the log out option) and try to log in again. If you experience an issue, please submit a diagnostic report immediately after your attempt. Logs only capture a limited amount of information, and sometimes a delay causes the useful information to already be overwritten.

I also sent an e-mail to the beta crew offering a faster way to receive beta updates, please let me know if you have any questions.

Sent an immediate diagnostic report

  • Thanks 1
Link to comment
Share on other sites

Another beta update rolling out now, another attempted fix at the web login issues. As before, try to log in and please submit diagnostics if it fails. If logging in works properly, please attempt to upload your data, and also attempt to log out from within the app. Thank you!

  • Like 1
Link to comment
Share on other sites

4 minutes ago, Trip said:

Still no luck.  Diagnostics sent.

Ok, thanks (EDIT: I didn't get fresh diagnostics from you).. won't be able to get any other updates out tonight, but I'll be working on it again tomorrow. I would appreciate additional diagnostics from anyone who wants to try logging in and sending them.

Any logged is still saved, and your device(s) are actually logging in, there's just something weird going on with processing the login response.. if I can't get it fixed by tomorrow afternoon, I'll push out an update that will bypass some things as a temporary fix.

  • Like 3
Link to comment
Share on other sites

I believe I have finally tracked down the cause of the null pointer issue, it was a compiler issue -- which explains why I could not replicate it myself. New release is rolling out to Google Play now. Please test and submit diagnostics if you encounter any problems. Thanks for all of the help and feedback!

  • Like 1
  • Love 3
Link to comment
Share on other sites

27 minutes ago, mikejeep said:

I believe I have finally tracked down the cause of the null pointer issue, it was a compiler issue -- which explains why I could not replicate it myself. New release is rolling out to Google Play now. Please test and submit diagnostics if you encounter any problems. Thanks for all of the help and feedback!

Can confirm that this change fixed it. I was able to log-in successfully and finally update the 4.5k datapoints I had queued up. 

  • Like 3
  • Love 1
Link to comment
Share on other sites

One last beta update is rolling out now before it goes live for the public.. this includes minor code improvements and cleanup, and the removal of the [SCC] indicator on neighbor cells. For now, only the [PCC] indicator will appear (if applicable) on neighbor cells, as the SCC indicator is basically redundant. If anyone has seen the PCC indicator on their device (or sees it in the future), please let me know. This will likely only appear when you are in a dual SIM configuration and it should help me provide dual SIM support.

Absent any new bugs appearing with this update, a parallel release will finally go out to non-beta users soon!

  • Like 5
  • Love 1
Link to comment
Share on other sites

Another SignalCheck beta is rolling out now -- I was able to replicate an additional instance of n7/n38 appearing incorrectly and improved the workaround for that (hopefully that resolves it for you this time, @dkyeager).

This update is being pushed out as version 4.731b to the Beta Crew and version 4.73 to the public!

  • Like 2
  • Love 1
Link to comment
Share on other sites

7 hours ago, mikejeep said:

Another SignalCheck beta is rolling out now -- I was able to replicate an additional instance of n7/n38 appearing incorrectly and improved the workaround for that (hopefully that resolves it for you this time, @dkyeager).

This update is being pushed out as version 4.731b to the Beta Crew and version 4.73 to the public!

It works on the Samsung Galaxy A32 5g , which was one of the "free" T-Mobile 5g phones, and also the factory unlocked firmware.  Thanks for all your hard work Mike.

 

  • Like 3
Link to comment
Share on other sites

Mike, in case you are feeling lucky, I sent in diags when on n41 from my s21 ultra U1 (factory unlocked) which can still use samsung band selector app. Both *#0011* and cellmapper can see the n41.

The s22+ U1 has T-Mobile esim and USMobile (Verizon) psim. Cellmapper can see both, but often gets confused in the carrier display. The latest production SCP can not see the Verizon network.  Did notice no web update in production version so maybe other differences?  Thanks.

Edit: I also sent diags in on the s22+ with two networks.

Link to comment
Share on other sites

23 minutes ago, mikejeep said:

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.

Er, sorry.  I know this is my fault.  😅

Separately, I wanted to flag that the new log-in feature for uploading could probably use a bit of tweaking when it doesn't work properly.  I'm currently in my standard Poor Reception Area™ and I've had it prompt me to login when the connection was bad.  It even pops up a message indicating that it's an Unknown Host Exception or something along those lines.  Seems like it should just say "unable to connect" or something.

It also seems to hang the app while trying to figure that out, though I'm not sure there's much you can do there.

- Trip

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • A heavy n41 overlay as an acquisition condition would be a win for customers, and eventually a win for T-Mobile as that might be enough to preclude VZW/AT&T adding C-Band for FWA due to spreading the market too thinly (which means T-Mobile would just have local WISPs/wireline ISPs as competition). USCC spacing (which is likely for contiguous 700 MHz LTE coverage in rural areas) isn't going to be enough for contiguous n41 anyway, and I doubt they'll densify enough to get there.
    • Boost Infinite with a rainbow SIM (you can get it SIM-only) is the cheapest way, at $25/mo, to my knowledge; the cheaper Boost Mobile plans don't run on Dish native. Check Phonescoop for n70 support on a given phone; the Moto G 5G from last year may be the cheapest unlocked phone with n70 though data speeds aren't as good as something with an X70 or better modem.
    • Continuing the USCC discussion, if T-Mobile does a full equipment swap at all of USCC's sites, which they probably will for vendor consistency, and if they include 2.5 on all of those sites, which they probably will as they definitely have economies of scale on the base stations, that'll represent a massive capacity increase in those areas over what USCC had, and maybe a coverage increase since n71 will get deployed everywhere and B71 will get deployed any time T-Mobile has at least 25x25, and maybe where they have 20x20. Assuming this deal goes through (I'm betting it does), I figure I'll see contiguous coverage in the area of southern IL where I was attempting to roam on USCC the last time I was there, though it might be late next year before that switchover happens.
    • Forgot to post this, but a few weeks ago I got to visit these small cells myself! They're spread around Grant park and the surrounding areas, but unfortunately none of the mmwave cells made it outside of the parks along the lake into the rest of downtown. I did spot some n41 small cells around downtown, but they seemed to be older deployments limited to 100mhz and performed poorly.    
    • What is the cheapest way to try Dish's wireless network?  Over the past year I've seen them add their equipment to just about every cell site here, I'm assuming just go through Boost's website?  What phones are Dish native?  
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...