Jump to content

SignalCheck Beta Crew Forum


mikejeep

Recommended Posts

21 hours ago, mikejeep said:

 

 

Hmm, that's strange.. it works fine on my LG G2, Pixel 3, and Pixel 4. If anyone experiencing this not working could set a padding value, back out of the Preferences, and send me a diagnostic report with a note about the padding when you have a chance. Maybe there's an error being quietly thrown I can look at. Not sure if there will be anything there, but I'm not sure what else to try. Thanks!

Want some more interesting news?

So I activated my Google Fi eSIM to check out Sprint and USCC service upgrades in my area.  On my Pixel 4 XL, when connected to Sprint the padding works.  As soon as it switches to USCC or T-Mobile the padding is gone.

My main SIM is AT&T and it also does not have the padding.

Correction:  It works when on USCC too.  Not AT&T or T-Mobile though.

Link to comment
Share on other sites

On my Pixel 4 XL, when connected to Sprint the padding works.  As soon as it switches to USCC or T-Mobile the padding is gone. My main SIM is AT&T and it also does not have the padding.

Correction:  It works when on USCC too.  Not AT&T or T-Mobile though.

What the!? Haha.. that's interesting and should help me narrow down what's going on. I did see your reports, but there were no errors.

  • Like 1
Link to comment
Share on other sites

On 12/19/2019 at 12:29 PM, mikejeep said:

What the!? Haha.. that's interesting and should help me narrow down what's going on. I did see your reports, but there were no errors.

Works on Verizon too. Looks like your padding code doesn't like GSM carriers. Ha. 😆

  • Like 1
Link to comment
Share on other sites

10 hours ago, uecker87 said:

Works on Verizon too. Looks like your padding code doesn't like GSM carriers. Ha. 😆

Same for me. On my AT&T S9+ it does nothing, but on my Sprint S9+ it works fine.

Link to comment
Share on other sites

1 hour ago, nowerlater said:

I think it looks finebf873459c69f0cfc9839dab56c681060.jpg

Sent from my SM-N975U using Tapatalk
 

What was padding your set as?

Link to comment
Share on other sites

I believe I found the issue with the padding not working for some users -- it is related to GSM-based connections, that's why it worked for some users but not others. Thanks for the reports, would not have figured it out without help! The fix is in testing and should be rolled out in the next update.

-Mike

  • Like 7
Link to comment
Share on other sites

Hey Mike, I noticed recently that SCP is showing positive SNR even if Service Mode and engineering screen is showing negative SNR. I sent a couple of diagnostic reports yesterday. I've also noticed when I'm near my MB at my office and SNR is reported as 30 dBm in service mode SCP does not show SNR. Once it drops to 29.9 and lower it will show it. Not sure if that is by design or not. 

erzxMNRl.png

03LY3sVl.png

d05HE8ql.png

  • Thanks 1
Link to comment
Share on other sites

On 1/5/2020 at 12:46 AM, mdob07 said:

Hey Mike, I noticed recently that SCP is showing positive SNR even if Service Mode and engineering screen is showing negative SNR. I sent a couple of diagnostic reports yesterday. I've also noticed when I'm near my MB at my office and SNR is reported as 30 dBm in service mode SCP does not show SNR. Once it drops to 29.9 and lower it will show it. Not sure if that is by design or not.

Thanks! The missing negative sign was a bug that nobody had ever mentioned (probably never noticed); that was an easy fix and will be part of the next update. SNR "30" is hidden by design because that is what many devices report when SNR is invalid/missing; it's the maximum value possible. (For safety sake, I have "-20" hidden as well.) My P3 and P4 always report 30 whenever connected to Sprint, regardless of the signal quality.

-Mike

Link to comment
Share on other sites

A new SignalCheck Pro beta update is rolling out right now, should be available shortly! This will hopefully be the final update before a public release; the only changes users should notice since the last beta are the fixes for screen padding and negative LTE SNR values. Those of you who experienced these issues, please let me know if they are resolved after you update.

Once I get this release rolled out publicly, I will (eventually) be pushing out major changes to add Multi-SIM support.

Thanks,
-Mike

  • Like 4
Link to comment
Share on other sites

  • 2 weeks later...
On 1/11/2020 at 2:04 PM, mdob07 said:

I found some B2,B4/B66 small cells around Baltimore, the B2 is identified but the B4/B66 is not. f5e9b4df2a6ea3b6e6131e89761ac5e5.jpg

Sent from my SM-G965U using Tapatalk
 

Looking at CellMapper GCI ending 31 is the 3rd B4/B66 small cell sector. Looking around New York their small cells also have a 2nd B2 carrier thats B2, B3, and B4.

Link to comment
Share on other sites

On 1/11/2020 at 2:04 PM, mdob07 said:

I found some B2,B4/B66 small cells around Baltimore, the B2 is identified but the B4/B66 is not. f5e9b4df2a6ea3b6e6131e89761ac5e5.jpg

I already have "73" as a Band 4 small cell; I do need to do something so those carry over to B66 I guess. Are you certain that "4D" is a small cell? I have no entries in the database for that suffix right now.

 

21 hours ago, mdob07 said:

Looking at CellMapper GCI ending 31 is the 3rd B4/B66 small cell sector. Looking around New York their small cells also have a 2nd B2 carrier thats B2, B3, and B4.

So you can confirm that "31" should also be a B4/B66 SC? Just want to make sure I'm understanding you correctly.

I already have "B3" thru "B6" assigned as a Band 2 second carrier on macro sites -- are you sure they were small cells?

Link to comment
Share on other sites

New SignalCheck beta is rolling out now.. bugfix city! Slowly making progress with Dual-SIM support, but nothing to share yet. The new update should appear on Google Play within the hour. Thank you for all your support!

  • Like 2
Link to comment
Share on other sites

1 hour ago, mikejeep said:

I already have "73" as a Band 4 small cell; I do need to do something so those carry over to B66 I guess. Are you certain that "4D" is a small cell? I have no entries in the database for that suffix right now.

 

So you can confirm that "31" should also be a B4/B66 SC? Just want to make sure I'm understanding you correctly.

I already have "B3" thru "B6" assigned as a Band 2 second carrier on macro sites -- are you sure they were small cells?

Yeah, 31 corresponds with 23 sector, 4D corresponds with the 3F sector, and 73 corresponds with the 63 sector. 

mFA0DF4.png

For the B2 second carrier part, I've only seen that while looking through New York. Around here and everywhere I've seen it is a Macro ID. I've noticed with AT&T that 2nd carriers and any of the newer spectrum seems to use different GCI patterns in each market. 

  • Thanks 1
Link to comment
Share on other sites

I also found some new iDAS sectors at Rupp Arena. DAS typically has 3 sectors, but I only hit one each for the B30 and secordary B4/B66.

lDNukoW.png

Looking at various stadiums and arenas around CellMapper I've found B30 DAS using A3-A8. If I go back to Rupp Arena any time soon I'll lock my phone to B30 and see what I find.

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...

Mike, my AT&T S9+ finally upgraded to Android 10. I'm seeing the CA values populate now, but I've not yet ever seen "BW: x MHz" Both are turned on in my display settings. If it knows the channel size for the CA list should the BW be populating also? I can send a diagnostic report if you want. 

The first screenshot is an example of what I'm not seeing (from user kg4icg on the Signal Check thread):

mf2eIdum.png

This is what I'm seeing:

rQorgiem.jpg?1

Also, I like how Android 10 shows more info on the swipe down than 9 did. Other than the known Android CA accuracy issue everything seems to be working fine. 

bbN82S1l.png

  • Like 1
Link to comment
Share on other sites

On 1/25/2020 at 10:33 AM, mikejeep said:

Thank you @mdob07, I will get those additions in the next update!

Found another one, sector ending 6B on AT&T is B12 small cell. I also hit sector ending 2A on the small cells in Nashville but that is already identified. There should be a third B12 sector but I haven't found it yet.

pvD3dAO.png

  • Thanks 1
Link to comment
Share on other sites

Mike, my AT&T S9+ finally upgraded to Android 10. I'm seeing the CA values populate now, but I've not yet ever seen "BW: x MHz" Both are turned on in my display settings. If it knows the channel size for the CA list should the BW be populating also? I can send a diagnostic report if you want. 
The first screenshot is an example of what I'm not seeing (from user kg4icg on the Signal Check thread):
mf2eIdum.png
This is what I'm seeing:
rQorgiem.jpg?1
Also, I like how Android 10 shows more info on the swipe down than 9 did. Other than the known Android CA accuracy issue everything seems to be working fine. 
bbN82S1l.png
I'm still on Android 9 and I have the same issue since last update I believe. Miss the info

Sent from my SM-G970U using Tapatalk

Link to comment
Share on other sites

13 hours ago, mdob07 said:

Mike, my AT&T S9+ finally upgraded to Android 10. I'm seeing the CA values populate now, but I've not yet ever seen "BW: x MHz" Both are turned on in my display settings. If it knows the channel size for the CA list should the BW be populating also? I can send a diagnostic report if you want. 

The first screenshot is an example of what I'm not seeing (from user kg4icg on the Signal Check thread):

mf2eIdum.png

This is what I'm seeing:

rQorgiem.jpg?1

Also, I like how Android 10 shows more info on the swipe down than 9 did. Other than the known Android CA accuracy issue everything seems to be working fine. 

bbN82S1l.png

I just realized SNR is missing also. I've looked through multiple screenshots I've taken and haven't seen it at all.

  • Like 1
Link to comment
Share on other sites

2 hours ago, mdob07 said:

I just realized SNR is missing also. I've looked through multiple screenshots I've taken and haven't seen it at all.

Yep, I have basic UNLOCKED s9 on Sprint.  Upgraded to Android 10.  No SNR and no BW. Aggregation is showing but not always correct.

  • Like 2
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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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