SignalCheck Beta Crew Forum

[mdob07 1,212]

SCP is crashing several times a day now on the newest Android update. I've been hitting the send info button when it crashes. Hopefully there's something helpful.

[mikejeep 5,001]

10 hours ago, mdob07 said:

SCP is crashing several times a day now on the newest Android update. I've been hitting the send info button when it crashes. Hopefully there's something helpful.

Send a diagnostic when you get a chance if you haven't already? Would like to compare firmware versions with others reporting issues..

[Flompholph 1,217]

14 hours ago, mdob07 said:

SCP is crashing several times a day now on the newest Android update. I've been hitting the send info button when it crashes. Hopefully there's something helpful.

I would be one of the others sending reports in. Maybe we can trade notes on when the crashes happen. 

For me the crashes happen about 5-10 seconds after I unlock my phone. The lock screen does not show SCP notification not sure if it is connected. When the crash happens the popup comes up but SCP doesn't seem to care and keeps the notification up. I have started to notice SCP notification starting to disappear but not doing a crash report but that has only happened twice yesterday. No idea how it links to my updating software cycle.

[mikejeep 5,001]

On 1/28/2021 at 9:48 AM, Flompholph said:

I would be one of the others sending reports in. Maybe we can trade notes on when the crashes happen. 

For me the crashes happen about 5-10 seconds after I unlock my phone. The lock screen does not show SCP notification not sure if it is connected. When the crash happens the popup comes up but SCP doesn't seem to care and keeps the notification up. I have started to notice SCP notification starting to disappear but not doing a crash report but that has only happened twice yesterday. No idea how it links to my updating software cycle.

I saw your most recent diagnostic report, unfortunately still no crash logs or any relevant information is attached. I'm kind of stumped on this one, but that's not the first (or last) time it's happened. At some point we will get this figured out -- or it's an OS software issue that will be resolved in a future update and we'll never know what it was.....

[Rickie546 1,278]

On 2/1/2021 at 4:41 AM, mikejeep said:

I saw your most recent diagnostic report, unfortunately still no crash logs or any relevant information is attached. I'm kind of stumped on this one, but that's not the first (or last) time it's happened. At some point we will get this figured out -- or it's an OS software issue that will be resolved in a future update and we'll never know what it was.....

Yea crashing for me the last week, sent report

[mikejeep 5,001]

8 hours ago, Rickie546 said:

Yea crashing for me the last week, sent report

Ugh.. new beta coming very soon, not sure if I've solved anything but who knows.. still no crash info coming in.

[mdob07 1,212]

53 minutes ago, mikejeep said:

Ugh.. new beta coming very soon, not sure if I've solved anything but who knows.. still no crash info coming in.

Both my phones stopped crashing after I turned off battery optimization for SCP. Haven't had an issue in a couple weeks now and my AT&T phone had been crashing multiple times a day before that. I don't think I ever came back and reported that.

[mikejeep 5,001]

A new beta release of SignalCheck Pro is rolling out to the Beta Crew now! It should become available within the next few hours. Opening/closing the app or checking Google Play should prompt you to update.

Lots of bugfixes and some new features. Check the changelog for full details.. looking forward to your feedback!

[RAvirani 2,290]

Make sure to run your trail logger and upload data from the log menu everyone!

More to come soon 😉. 

[Trip 3,003]

Tried to do the upload from my oldest phone, a G3 with a T-Mobile SIM, which I believe still uses modem commands to get the EARFCN, and got this.

https://imgur.com/a/vuP7CHQ

This is actually the last thing I'm doing with that phone before permanently retiring it as the screen appears to be failing.  I got my mom's old phone from her over the weekend as we upgraded her at Christmas.  Her old E4 Plus has now been rooted and will replace my G3 going forward.

I used the upload function on my Verizon E5 Play, AT&T E5 Play, and my main Sprint G8X without issue.  I need to upgrade and upload with the others, and will do so probably later today or tomorrow.  I'll let you know if I encounter any other problems.

EDIT:  Here are two of my E5 Plays for T-Mobile giving messages:

https://imgur.com/a/0AiAMMv

I'm saving copies of the database files that give messages if you want to review them.

- Trip

[RAvirani 2,290]

29 minutes ago, Trip said:

EDIT:  Here are two of my E5 Plays for T-Mobile giving messages:

https://imgur.com/a/0AiAMMv

I'm saving copies of the database files that give messages if you want to review them.

Those upload errors come from me.

I verify each recorded datapoint's band against the carrier and drop datapoints that look funky. For example, we shouldn't see an AT&T PLMN paired with B13 or a Verizon PLMN paired with B41. You might have had a suspicious looking band because SCP didn't update the PLMN quickly enough.

The unsupported carrier message probably refers to your phone briefly roaming on/band scanning a rural carrier. I only support AT&T, Verizon, T-Mobile, Sprint and US Cellular right now. Other PLMNs are dropped. If you have a PLMN/carrier you would like me to add, I can take a look at getting it spun up in my database. 

[Trip 3,003]

2 minutes ago, RAvirani said:

Those upload errors come from me.

I verify each recorded datapoint's band against the carrier and drop datapoints that look funky. For example, we shouldn't see an AT&T PLMN paired with B13 or a Verizon PLMN paired with B41. You might have had a suspicious looking band because SCP didn't update the PLMN quickly enough.

The unsupported carrier message probably refers to your phone briefly roaming on/band scanning a rural carrier. I only support AT&T, Verizon, T-Mobile, Sprint and US Cellular right now. Other PLMNs are dropped. If you have a PLMN/carrier you would like me to add, I can take a look at getting it spun up in my database. 

I figured out the unsupported carriers bit.  Now and then my phones will see PLMNs that aren't supported, like 313100 for FirstNet.  I doubt those need to be included, and there are sometimes garbage PLMNs that sneak in as well. 

The band versus carrier thing though, it seems like it's dropping more than an individual row; it said "Cluster #2" for example, which seems to be 512 rows.  Is that expected behavior? 

- Trip

[RAvirani 2,290]

13 minutes ago, Trip said:

I figured out the unsupported carriers bit.  Now and then my phones will see PLMNs that aren't supported, like 313100 for FirstNet.  I doubt those need to be included, and there are sometimes garbage PLMNs that sneak in as well. 

Yup. Now that I think about it, I should probably add the FirstNet PLMN to the AT&T map...

14 minutes ago, Trip said:

The band versus carrier thing though, it seems like it's dropping more than an individual row; it said "Cluster #2" for example, which seems to be 512 rows.  Is that expected behavior? 

- Trip

Sorry - I read the error message wrong. You're right - it dropped the entire 512-point cluster. That should only happen if I detect a band that's not numeric (as that looks suspiciously like foul play/attempted hacking). Can you shoot me the file? I'd like to take a look at what's going on there. 

[Trip 3,003]

5 hours ago, RAvirani said:

Yup. Now that I think about it, I should probably add the FirstNet PLMN to the AT&T map...

Sorry - I read the error message wrong. You're right - it dropped the entire 512-point cluster. That should only happen if I detect a band that's not numeric (as that looks suspiciously like foul play/attempted hacking). Can you shoot me the file? I'd like to take a look at what's going on there. 

I picked one of the db files with both messages, and will PM you the link.

- Trip

[mdob07 1,212]

Mike, I'm getting this error when I try to restore any of my older logs to one of my phones. This particular one is my Verizon log last exported in 2019. Has the DB structure changed since then so that this can't be imported anymore? Is there anything in the DB I can manually change to get it to import? This has all of my Verizon site notes for my area so I really don't want to start back from scratch. 

[mikejeep 5,001]

2 hours ago, mdob07 said:

Mike, I'm getting this error when I try to restore any of my older logs to one of my phones. This particular one is my Verizon log last exported in 2019. Has the DB structure changed since then so that this can't be imported anymore? Is there anything in the DB I can manually change to get it to import? This has all of my Verizon site notes for my area so I really don't want to start back from scratch.

Even if the structure changed, it should still import -- can you try again and then send me a diagnostic report? That should capture the error details. I can take a look at the file as well if you e-mail it to me, but the diagnostic will be most helpful.

[mdob07 1,212]

2 hours ago, mikejeep said:

Even if the structure changed, it should still import -- can you try again and then send me a diagnostic report? That should capture the error details. I can take a look at the file as well if you e-mail it to me, but the diagnostic will be most helpful.

Report sent. For what its worth I was able to reimport the current log with no issues. Every time I try to import it creates a backup of the current, so I tried one of those and it worked. But none of my older ones will successfully import. I don't usually switch things around on my phones very often so its been awhile since I've done this. This particular S9+ was used to map Sprint/T-Mobile data previously but since they finally killed my inactive Sprint SIM I'm going to keep it on Verizon full time (at least until they kill that SIM).

I'm able to open the Verizon DB on my laptop and see the data so I don't think its corrupt. 

[mikejeep 5,001]

8 hours ago, mdob07 said:

Report sent. For what its worth I was able to reimport the current log with no issues. Every time I try to import it creates a backup of the current, so I tried one of those and it worked. But none of my older ones will successfully import. I don't usually switch things around on my phones very often so its been awhile since I've done this. This particular S9+ was used to map Sprint/T-Mobile data previously but since they finally killed my inactive Sprint SIM I'm going to keep it on Verizon full time (at least until they kill that SIM).

I'm able to open the Verizon DB on my laptop and see the data so I don't think its corrupt. 

I found the issue -- the nr_sites table is missing (because it didn't exist back then, of course) so the import fails -- so it is another bug! I'll work on fixing that, but if you have the ability to add that table (it might need the same column structure, I haven't run into this so not positive), that might fix your issue. Or you can send it to me and I can.

[mikejeep 5,001]

New beta rolling out now, should become available shortly.. fixes some bugs reported this week, as well as improvements to the data uploader status display. Full changelog in the app or on the website as always. Thanks for the feedback!

[mdob07 1,212]

On 3/10/2021 at 8:46 PM, mdob07 said:

Mike, I'm getting this error when I try to restore any of my older logs to one of my phones. This particular one is my Verizon log last exported in 2019. Has the DB structure changed since then so that this can't be imported anymore? Is there anything in the DB I can manually change to get it to import? This has all of my Verizon site notes for my area so I really don't want to start back from scratch. 

 

23 hours ago, mikejeep said:

I found the issue -- the nr_sites table is missing (because it didn't exist back then, of course) so the import fails -- so it is another bug! I'll work on fixing that, but if you have the ability to add that table (it might need the same column structure, I haven't run into this so not positive), that might fix your issue. Or you can send it to me and I can.

Mike, I'm still getting this error on the newest beta. Change log indicates a fix was in the new beta. I sent a diagnostic report. 

[mikejeep 5,001]

1 hour ago, mdob07 said:

Mike, I'm still getting this error on the newest beta. Change log indicates a fix was in the new beta. I sent a diagnostic report. 

Hmm, I did implement a fix for the NR table error in the overnight update, but maybe there's something else too. Is it the same exact error on your screen? Your diagnostic report didn't have anything logged, can you try the import again and then send a diagnostic shortly after?

[mdob07 1,212]

16 minutes ago, mikejeep said:

Hmm, I did implement a fix for the NR table error in the overnight update, but maybe there's something else too. Is it the same exact error on your screen? Your diagnostic report didn't have anything logged, can you try the import again and then send a diagnostic shortly after?

Done. And it is the same error. 

[mikejeep 5,001]

2 hours ago, mdob07 said:

Done. And it is the same error. 

Hmmm.. it's not throwing any errors in logcat at all. Can you send me that file so I can try it myself and see what's going on?

[gr8nuguy 2,178]

Happens to me to Mike 

[mikejeep 5,001]

1 minute ago, gr8nuguy said:

Happens to me to Mike 

E-mail me the file (support [at] signalcheck.app), happy to take a look and get it fixed!