Jump to content
mikejeep

SignalCheck Beta Crew Forum

Recommended Posts

Mike, for the "-Added LTE bandwidth (BW) value on Android 9+ devices." I'm not seeing anything on either of my S9+'s. Is this supposed to show the channel width? If so that would be awesome for devices like my Verizon S9+ where they lock out the engineering screens. Both are running Android 9, one has the March 1st security update and the other has February 1st update if it matters. 

ioGZGl1.jpg

I'm also still seeing no connection when on anything other than LTE with my AT&T S9+. 

Vwiho3d.jpg

I've also noticed with my Verizon phone that while on B4 the 2nd carrier notation works, but when connected with B66 MFBI to the same sector it doesn't. Not sure if that is something you want to carry over to B66. oDAS and iDAS notations also have this issue with AT&T B66. They are using the same GCI pattern just broadcasting with B66 EARFCN. Sometimes I'll be on B4 and sometimes I'll get B66 from the same site. 

N1Izeyw.jpg

One more thing, any plans to add the TA value to the log with the closet value saved with coordinates like how RSRP is done now? This would be very helpful when identifying sites using my log files. For instance, I was almost passing under the site from the below screenshot, but RSRP level is still in the -90's. I think adding the TA value would be helpful to identify sites especially when not getting all the way up to a site. From what I've seen by watching it on both my AT&T and Verizon phones its been usually spot on for distance. 

   x6dRgr9.jpg

  • Like 1

Share this post


Link to post
Share on other sites
15 hours ago, mikejeep said:

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

Nvm!

Share this post


Link to post
Share on other sites
On 4/4/2019 at 11:17 PM, mdob07 said:

Mike, for the "-Added LTE bandwidth (BW) value on Android 9+ devices." I'm not seeing anything on either of my S9+'s. Is this supposed to show the channel width? If so that would be awesome for devices like my Verizon S9+ where they lock out the engineering screens. Both are running Android 9, one has the March 1st security update and the other has February 1st update if it matters. 

It is supposed to show the channel width, but unfortunately it does not appear to be reliably implemented yet. Much like when EARFCN routines were added to Android 7, I think it may take a few releases before it becomes reliable. On my Pixel 3, it shows about 75% of the time when connected to a macro site. Never shows on my Airave or when I'm on a MB. Feedback from other beta testers is similar, with some devices never reporting it and others showing it sporadically. It has also been wrong on occasion. Because of all this, I may change it to be an option that is disabled by default, and I can note the caveats on the Preferences screen.

 

On 4/4/2019 at 11:17 PM, mdob07 said:

I'm also still seeing no connection when on anything other than LTE with my AT&T S9+. 

Ugh, sorry I thought I had that fixed. I'll continue working on it, it's a known issue.

 

On 4/4/2019 at 11:17 PM, mdob07 said:

I've also noticed with my Verizon phone that while on B4 the 2nd carrier notation works, but when connected with B66 MFBI to the same sector it doesn't. Not sure if that is something you want to carry over to B66. oDAS and iDAS notations also have this issue with AT&T B66. They are using the same GCI pattern just broadcasting with B66 EARFCN. Sometimes I'll be on B4 and sometimes I'll get B66 from the same site. 

 

Ah, that's something I did not take into account. I'll work on that as well.

 

On 4/4/2019 at 11:17 PM, mdob07 said:

One more thing, any plans to add the TA value to the log with the closet value saved with coordinates like how RSRP is done now? This would be very helpful when identifying sites using my log files. For instance, I was almost passing under the site from the below screenshot, but RSRP level is still in the -90's. I think adding the TA value would be helpful to identify sites especially when not getting all the way up to a site. From what I've seen by watching it on both my AT&T and Verizon phones its been usually spot on for distance.

I do plan on adding both TA and BW to the database. TA has appeared to be very reliable in my experience as well, but I'm not going to change the logic on saving the coordinates just yet. It's still a fairly new addition and not all devices report it, so I don't think I want to open that can of worms yet. I do see how it will be more valuable so it will be a good idea.

-Mike

  • Like 1

Share this post


Link to post
Share on other sites

I had some SCP repeated crashes yesterday on a couple of LG G2s.  I sent in a few error logs. 

I have a small herd of rooted phones that I use Network Signal Guru to limit to one LTE Band then use SCP to record what I find.  I have been doing this for years without issues until this beta.

Thanks

  • Thanks 1

Share this post


Link to post
Share on other sites
8 hours ago, dkyeager said:

I had some SCP repeated crashes yesterday on a couple of LG G2s.  I sent in a few error logs. 

I have a small herd of rooted phones that I use Network Signal Guru to limit to one LTE Band then use SCP to record what I find.  I have been doing this for years without issues until this beta.

Thanks, I saw those this morning.. looks like on pre-Oreo devices there is an issue with how the app was compiled. I'm looking into it!

-Mike

  • Like 1

Share this post


Link to post
Share on other sites

I sent a few reports for my Moto G4 Play on US Cellular with what I assume to be the same repeated crashing issue.

- Trip

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

I believe I have resolved the force closes on pre-Oreo devices as well as the force closes with the custom LTE alert. Need to do a bit more testing but I should be all set with additional reports about those, thank you to all who have sent crash reports--it is very difficult to fix anything without that data, I appreciate it!

Has anyone (@jefbal99?) tried using SCP with Android Q Beta 2 yet? Curious to see if anything has improved yet. If you can get it to run at all, please send me a diagnostic report so I can see how it's doing.

-Mike

Share this post


Link to post
Share on other sites
4 minutes ago, mikejeep said:

I believe I have resolved the force closes on pre-Oreo devices as well as the force closes with the custom LTE alert. Need to do a bit more testing but I should be all set with additional reports about those, thank you to all who have sent crash reports--it is very difficult to fix anything without that data, I appreciate it!

Has anyone (@jefbal99?) tried using SCP with Android Q Beta 2 yet? Curious to see if anything has improved yet. If you can get it to run at all, please send me a diagnostic report so I can see how it's doing.

-Mike

Same errors still, not sure if Google actually fixed the issue.  Sending you a new log

  • Thanks 1

Share this post


Link to post
Share on other sites
25 minutes ago, jefbal99 said:

Same errors still, not sure if Google actually fixed the issue.  Sending you a new log

Blah.. thanks. I starred your new issue report and added a comment. Did your original report on the issue tracker from a few weeks ago disappear? I haven't seen any diagnostic or crash reports from you yet today.

-Mike

Share this post


Link to post
Share on other sites
40 minutes ago, mikejeep said:

Blah.. thanks. I starred your new issue report and added a comment. Did your original report on the issue tracker from a few weeks ago disappear? I haven't seen any diagnostic or crash reports from you yet today.

-Mike

Sent it about an hour ago. I'll send another right now

  • Thanks 1

Share this post


Link to post
Share on other sites
On 4/6/2019 at 8:02 AM, mikejeep said:

I do plan on adding both TA and BW to the database. TA has appeared to be very reliable in my experience as well, but I'm not going to change the logic on saving the coordinates just yet. It's still a fairly new addition and not all devices report it, so I don't think I want to open that can of worms yet. I do see how it will be more valuable so it will be a good idea.

What's weird is that I only see TA sometimes.  I'm not sure it could be depended on, at least in my experience.

- Trip

Share this post


Link to post
Share on other sites
What's weird is that I only see TA sometimes.  I'm not sure it could be depended on, at least in my experience.


My non-scientific observations lead me to believe that TA only appears when data is actively flowing. When the connection goes idle, TA disappears.

-Mike

Share this post


Link to post
Share on other sites

That would actually explain it pretty well.  Thanks.

- Trip

  • Like 1

Share this post


Link to post
Share on other sites
17 hours ago, jefbal99 said:

starred.  Now up to 6.  Need a lot more people to star it since Google is numbers driven on what it chooses to fix.

  • Like 1

Share this post


Link to post
Share on other sites
starred.  Now up to 6.  Need a lot more people to star it since Google is numbers driven on what it chooses to fix.


Q Beta 2 might be reporting enough info for me to work with. I have to implement workarounds in to ignore the some of the invalid information that it is reporting and see what's left. Another complication is that Q is identifying itself as API 28, which is the same as Pie. I'm working on it..

-Mike
  • Like 1

Share this post


Link to post
Share on other sites
6 hours ago, dkyeager said:

starred.  Now up to 6.  Need a lot more people to star it since Google is numbers driven on what it chooses to fix.

 

2 hours ago, mikejeep said:

 


Q Beta 2 might be reporting enough info for me to work with. I have to implement workarounds in to ignore the some of the invalid information that it is reporting and see what's left. Another complication is that Q is identifying itself as API 28, which is the same as Pie. I'm working on it..

-Mike

 

Up to 7 now and its been assigned in the tracker

Share this post


Link to post
Share on other sites

New beta just uploaded, should be available within the hour! Hopefully will fix the custom trigger crashes, pre-Oreo crashes, missing WCDMA/GSM data, and missing Android Q data.. please pass along any improvements you notice!

-Mike

  • Like 3

Share this post


Link to post
Share on other sites
51 minutes ago, mikejeep said:

New beta just uploaded, should be available within the hour! Hopefully will fix the custom trigger crashes, pre-Oreo crashes, missing WCDMA/GSM data, and missing Android Q data.. please pass along any improvements you notice!

-Mike

Woot, have data!!!

  • Love 1

Share this post


Link to post
Share on other sites

Just sent a diagnostic report, still getting no connection when on HSPA+.

Edit: I'm also no longer seeing SNR reported on either my AT&T or Verizon S9+.

  • Sad 1

Share this post


Link to post
Share on other sites
5 hours ago, jefbal99 said:

Woot, have data!!!

One step forward...

1 hour ago, mdob07 said:

Just sent a diagnostic report, still getting no connection when on HSPA+.

Edit: I'm also no longer seeing SNR reported on either my AT&T or Verizon S9+.

...one step back!

Thank you both for sending diagnostics, it is very helpful. I see a few things I can improve on for Q to minimize unnecessary errors in the background, but overall it looks good. Let me know if anything seems missing. I'm definitely closer to getting the HSPA/WCDMA stuff working; I have a hunch what the last flaw might be that is keeping it from displaying. Please send diagnostics from the AT&T and Verizon devices when you have a chance so I can dig into that.

Thanks,
-Mike

  • Like 1

Share this post


Link to post
Share on other sites

New oddity, when SCP is in the background, it seems to lose its data from the OS.  The status bar changes to LTE -- even though there is an active connection.  Once you open the app, then it refreshes the data and all is good.

Screenshots at https://photos.app.goo.gl/VCf9nE3s6XRjPfPy7

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, jefbal99 said:

New oddity, when SCP is in the background, it seems to lose its data from the OS.  The status bar changes to LTE -- even though there is an active connection.  Once you open the app, then it refreshes the data and all is good.

Screenshots at https://photos.app.goo.gl/VCf9nE3s6XRjPfPy7

Not seen that on LG V20 with Android 8.0.0 or LG G2 with Android 5.0.2 (rooted).

Share this post


Link to post
Share on other sites
Just now, dkyeager said:

Not seen that on LG V20 with Android 8.0.0 or LG G2 with Android 5.0.2 (rooted).

My gut is that this is due to Android Q

  • Like 2

Share this post


Link to post
Share on other sites

Hey Mike, Looks like your changes worked. On 4.514b I'm now seeing W-CDMA info and SNR is back on both of my devices. Don't worry about the status bar icon in the GSM shot, I think I took the screen shot a soon as I cycled airplane mode. I'm 99.9% sure it was populated as I was watching it switch from GSM to HSPA. 

cjcDGlI.jpg

x6t76BF.jpg

I've also got a question on the custom alerts, I have one set for 67086 to get an alert when I connect to J Block AWS as the primary carrier since AT&T is just starting to open it up here for uplink connections. I hadn't gotten an alert for it all day until after I installed 4.514b. Now I'm getting the alert everytime I connect to the Shepherdsville tower even though I don't show that I have ever connected to it yet except as downlink with CA. Is that the way it is supposed to work? If so that's fine, I just wanted to know. It shows up in the neighbor cell list. 

  • Like 2
  • Thanks 1

Share this post


Link to post
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

    • Sorry, I wasn't clear, the Evergreen Hospital MM setup I already located a while ago. The eNBs for those were: B6BD7, B6BD9, B6BDB. I meant for the cluster of MM which I can't locate in Kirkland. Just like Totem Lake and the John Muir school, there are three MM nearby with their eNB separated by 2 digits and one reports as an MM/SC. As expected, SE03XC353 tends to overwhelm them in most normal areas, making location more difficult. It seems that their job is to fill in the "shadows" for SE03XC353. My guess is all three are located at the aforementioned Clear site in Kirkland, but I am not 100% certain on that yet. I will drive around to see if I can collect better data on CellMapper. As an aside, it seems like it is common in a cluster of three for one of them to report as an MM/SC on SignalCheck. Even the one I found which had the last eNB off by one, instead of two, still had one of them as an MM/SC. 
    • Yes, Sprint was required by the US government to decommission all Huawei equipment due to security concerns.  Sprint has historically had issues with the property owner of that Motel 6. It was one of the last sites upgraded to LTE, and it will probably be one of the last sites upgraded to triband.  That permit is for the Clear site by Kirkland marina. There is a mini-macro setup on the roof of Evergreen Hospital by Totem Lake. 
    • Sent from my iPhone using Tapatalk
    • That makes sense, I said "loves" strictly because I have encountered so many of them near me. I didn't know about the Huawei aspect of things. They are very well located normally, providing coverage for weak spots from the "main" tower.   As for Evergreen, that would make sense, it's a high location in what has become a VERY busy area. I am guessing that is why the tower over on the Motel 6 nearby has not been upgraded. Also, that is good to know about all of the MM clusters. That combined with this permit makes me think that I am correct on the location. The only thing I need to determine if all three eNB are at the same site.    
    • Robot Woman Sent from my SM-G975U1 using Tapatalk
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...