Jump to content

SignalCheck Beta Crew Forum

mikejeep

By mikejeep
in General Topics

 Share

Recommended Posts

mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted
On 12/9/2018 at 9:55 PM, mdob07 said:

Hey Mike,  would it be possible to change SCP to identify AT&T B14 by EARFCN vs GCI pattern? After doing some analysis on my log, looking the the B14 thread on Howard Forums and the netmapper map it appears to wildly vary by market what AT&T used for B14 sectors. The EARFCN should be consistent across the country. This would keep you from having to set several different patterns for B14.

The app already uses EARFCN as the primary means to identify the LTE band.. it will try to match a GCI pattern first, but if there are no matches or the "guessed" band does not match EARFCN data that appears to be valid, it uses the EARFCN instead. Since there are so many B14 sector possibilities right now, I don't think I will continue adding them beyond what is programmed now. Most newer devices on newer Android builds are properly reporting EARFCN, with some exceptions (issues with B66/B71 most notably). GCI pattern matching has become most useful to identify "special" cells (MM/SC/MB/Airave/etc) as well as multiple carriers.

 

3 hours ago, Jesito473 said:

Just noticed this today (MM2/SC2) anyone else?

I know this was answered elsewhere, but for the benefit of anyone who comes along later -- a small cell second carrier has been identified that follows the same GCI pattern as one sector of a Mini-Macro second carrier. Since the app has no way to know which one it is, it displays both indicators when this occurs.

-Mike

  • Like 2
Link to comment
Share on other sites
  • Replies 1.7k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

mikejeep
mikejeep

Beta crew.. assemble!   A new update is finally published.. if you're special   -Mike

mikejeep
mikejeep

Already started working on something along those lines, great minds think alike! I have a busy few days coming up but I should have another update ready by mid-week.   I appreciate everyone's feedba

mikejeep
mikejeep

Minor development news for the Beta Crew.. because of where I was at in overhauling SignalCheck Lite when I discovered the EARFCN bug that impacts LTE band 66 (and 71, and potentially others), I imple

Posted Images

Jesito473 Member Level: eHRPD

Jesito473

Posted
Posted
I know this was answered elsewhere, but for the benefit of anyone who comes along later -- a small cell second carrier has been identified that follows the same GCI pattern as one sector of a Mini-Macro second carrier. Since the app has no way to know which one it is, it displays both indicators when this occurs.
-Mike

Thank you Mike one of the guys clarified it. Good to know I wasn’t seeing things lol


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment
Share on other sites
dkyeager Member Level: LTE Advanced

dkyeager

Posted
Posted
35 minutes ago, mikejeep said:

 Since the app has no way to know which one it is, it displays both indicators when this occurs.

-Mike

At least in Samsung markets with AirHarmony small cells, the PCI of small cells is 450 or greater.  EARFCN would be another way, but that sometimes gets location specific. GCI  would be another way, but then you would need to know the MM cutoff point for each market (we have those for Ohio)

Link to comment
Share on other sites
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted
On 12/19/2018 at 10:20 PM, JWMaloney said:
Mike,
Can you add something to make T-Mobile (310260) notes show up when roaming from Sprint (311490)?

Not sure what you're asking.. could you clarify? Any saved notes should appear regardless if you're roaming or not. If you are referring to neighbor cells, there's already an option to ignore the PLMN for neighbor notes.

-Mike

Link to comment
Share on other sites
JWMaloney Member Level: eHRPD

JWMaloney

Posted
Posted
1 hour ago, mikejeep said:

Not sure what you're asking.. could you clarify? Any saved notes should appear regardless if you're roaming or not. If you are referring to neighbor cells, there's already an option to ignore the PLMN for neighbor notes.

-Mike

T-Mobile uses Clearwire 311490 as a secondary PLMN on their sites to enable Sprint roaming. I'm asking if you can make notes from 310260 show up for 311490, similar to what you are doing with 310120 and 312530.

 

Screenshot_20181218-220415.png

Link to comment
Share on other sites
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted
On 12/20/2018 at 5:52 AM, JWMaloney said:
T-Mobile uses Clearwire 311490 as a secondary PLMN on their sites to enable Sprint roaming. I'm asking if you can make notes from 310260 show up for 311490, similar to what you are doing with 310120 and 312530.

Ahh I see.. are you on the latest beta release, or the public one? (This is the beta thread.) I do not believe the beta will show 311490 any more. I'm trying to finish squashing a couple significant bugs so I can get a public update out with this improvement very soon.

-Mike

 

Link to comment
Share on other sites
JWMaloney Member Level: eHRPD

JWMaloney

Posted
Posted
6 hours ago, mikejeep said:

Ahh I see.. are you on the latest beta release, or the public one? (This is the beta thread.) I do not believe the beta will show 311490 any more. I'm trying to finish squashing a couple significant bugs so I can get a public update out with this improvement very soon.

Public channel. You're saying under the latest beta, if I'm a Sprint user, and I roam onto T-Mobile which presents itself as 311490 on the tower, and I already have a note saved for the same GCI under T-Mobile 310260, I'll be able to see that note?

Link to comment
Share on other sites
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted
On 12/20/2018 at 12:44 PM, JWMaloney said:
Public channel. You're saying under the latest beta, if I'm a Sprint user, and I roam onto T-Mobile which presents itself as 311490 on the tower, and I already have a note saved for the same GCI under T-Mobile 310260, I'll be able to see that note?

Correct! At least it should based on testing so far.. submit a diagnostic report (About > Send Diagnostics) next time you're on a 311490 TMo site and I should be able to confirm for you.

-Mike

Link to comment
Share on other sites
  • 2 weeks later...
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted

Some devices are reporting 311490 on T-Mobile no matter what I try, but most are not. I will continue looking to figure out a way to make those scenarios work better with "real" T-Mobile site notes logged under 310260.

A minor beta update is pushing out now, should be available shortly. It adds AT&T B2 small cells and fixes an issue with cached diagnostic reports not sending. More significantly, a public release is also going out that catches up all the changes the crew has been testing for the past 6-8 weeks. Thank you all for your help, I appreciate it!

-Mike

  • Like 6
Link to comment
Share on other sites
  • 2 weeks later...
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted

New beta has been uploaded, should become available within the hour.. added LTE timing advance and hopefully squashed some big juicy bugs.. let me know! Please try enabling some notifications and changing the sounds too..

-Mike

  • Like 4
Link to comment
Share on other sites
  • 3 weeks later...
  • 2 weeks later...
mdob07 Member Level: 4G WiMax

mdob07

Posted
Posted

Mike, just noticed on my S9+ that SCP showed no connection in both the app and task bar when connected to HSPA+. Cycled airplane mode and its showing everything for LTE with no issues. I'll try to get it back to HSPA+ to do more testing later.cbca8aef9c59c88d9431dee048db89d0.jpgbfe6266dd47fa625c5d456bb9c9c56e4.jpg

Sent from my SM-G965U using Tapatalk

Link to comment
Share on other sites
  • 1 month later...
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted
On 3/13/2019 at 8:24 PM, jefbal99 said:
Hoping for a new beta soon, just updated to the Android Q beta and SCP isn't displaying any data

I have spent a TON of time on it because I'm overhauling Alerts for Android 8+ users. They were broken and I don't want to push another update out without a fix. It's a lot of work but it's getting there.

Send me a diagnostic report from the Q Preview so I can get a peek at what's broken. Most early Preview builds have caused issues that were eventually resolved before the stable launch.

And thanks for the bday wishes!!

-Mike

  • Like 3
Link to comment
Share on other sites
jefbal99 Member Level: LTE Advanced

jefbal99

Posted
Posted
1 minute ago, mikejeep said:

 

I have spent a TON of time on it because I'm overhauling Alerts for Android 8+ users. They were broken and I don't want to push another update out without a fix. It's a lot of work but it's getting there.

 

Send me a diagnostic report from the Q Preview so I can get a peek at what's broken. Most early Preview builds have caused issues that were eventually resolved before the stable launch.

 

And thanks for the bday wishes!!

 

-Mike

 

I sent one in last night, let me know if you need another

  • Like 1
Link to comment
Share on other sites
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted

After looking at a handful of diagnostic and crash reports that I have received from Android Q Preview users, I can see that the connection data being reported by the OS is either missing or invalid on all devices so far. It's either broken or Android is taking a completely different approach and has not publicly shared that yet. Hopefully it's just broken, and they will resolve it in the next release.

Q users, please use whatever reporting channels are in place to report Preview bugs to inform them of this. You can mention that onSignalStrengthsChanged() is including header text with every value instead of just the raw data, and CellInfoLte.getCellIdentity() and related routines appear to be reporting no data.

-Mike

Link to comment
Share on other sites
jefbal99 Member Level: LTE Advanced

jefbal99

Posted
Posted
12 hours ago, mikejeep said:

After looking at a handful of diagnostic and crash reports that I have received from Android Q Preview users, I can see that the connection data being reported by the OS is either missing or invalid on all devices so far. It's either broken or Android is taking a completely different approach and has not publicly shared that yet. Hopefully it's just broken, and they will resolve it in the next release.

Q users, please use whatever reporting channels are in place to report Preview bugs to inform them of this. You can mention that onSignalStrengthsChanged() is including header text with every value instead of just the raw data, and CellInfoLte.getCellIdentity() and related routines appear to be reporting no data.

-Mike

It's on reddit now.  Please comment and upvote https://www.reddit.com/r/android_beta/comments/b2n6z5/connection_data_not_being_reported_from_q/

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
jefbal99 Member Level: LTE Advanced

jefbal99

Posted
Posted
16 hours ago, jefbal99 said:

It's on reddit now.  Please comment and upvote https://www.reddit.com/r/android_beta/comments/b2n6z5/connection_data_not_being_reported_from_q/

Google responded on reddit, looks like it will be addressed :)

  • Like 7
Link to comment
Share on other sites
  • 2 weeks later...
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted

Just a quick update for the Beta Crew, yes I am still hacking away at the new Alerts.. it is a lot of work trying to get everything working well on Oreo+ devices while not breaking pre-Oreo devices. I forgot how many ugly workarounds I needed to implement to keep everything working before. The new Android notification settings don't mesh well with my needs either, but it will get done. Just a tedious struggle.

Side note, I accidentally stumbled across something I either didn't know or forgot about.. Pie introduced a new method to get the channel bandwidth, so hopefully that will be an easy and very cool addition making this wait worth it.. stay tuned..

-Mike

  • Like 9
Link to comment
Share on other sites
mikejeep Member Level: LTE Advanced

mikejeep

Posted
  • Author
Posted

New beta is finally done brewing and has been uploaded to Google Play.. should be available within the hour! Lots of significant bugfixes and new LTE alerts that should make people very happy. Changelog: https://signalcheck.app/change-log

Thanks for your patience, and let me know what I broke..

-Mike

  • Like 7
  • Thanks 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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • topdownat4
      Keep a Word, Drop a Word #7

      By topdownat4 · Posted

      Fury Gran Coupe (My First Car - What a Boat...)
    • dkyeager
      Dish Network/Boost Mobile cell/5G buildout thread

      By dkyeager · Posted

      Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • dkyeager
      SignalCheck Beta Crew Forum

      By dkyeager · Posted

      Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • S4GRU
      Keep a Word, Drop a Word #7

      By S4GRU · Posted

      Nissan Coupe
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.

  • Recently Browsing

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