Jump to content
mikejeep

SignalCheck Beta Crew Forum

Recommended Posts

4 hours ago, mdob07 said:

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. 

Excellent, thanks for the detailed testing and screen shots! At the time of your GSM screenshot, the connection hadn't stabilized yet so the network type still shows "Connecting..." -- that intentionally causes the status bar icon to blank out. Funny that it comes up now, earlier today I was looking at it and considering changing that behavior. Displaying an icon with the dB reading but no connection type might not be a bad thing, since the reading itself is valid in my experience; I see it on my deactivated test devices that never get a true network connection but measure accurate signal strength.)

 

4 hours ago, mdob07 said:

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. 

Ha, this is an interesting side effect that I had not considered. You are tripping that alert because it's seeing 67086 in your neighbor cell list. In this latest update you received, it searches the entire LTE "text block"; in previous versions, it only searched a few selected fields I chose. But this is by design.. someone might want neighbor cells included. The easy fix is to adjust your trigger to be "EARFCN: 67086" -- because that would only trip when you actually connect to it, since the neighbor cells aren't displayed with that prefix.

-Mike

  • Like 1

Share this post


Link to post
Share on other sites
17 hours 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

Is this still occurring with the Alpha update I sent you last night?

-Mike

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, mikejeep said:

Is this still occurring with the Alpha update I sent you last night?

-Mike

Yes, the second diagnostic I sent I tried to get with no data before it refreshed

 

I added a video to the album of it happening

Edited by jefbal99
Video

Share this post


Link to post
Share on other sites
11 hours ago, mdob07 said:

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. 

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. 

 

7 hours ago, mikejeep said:

Is this still occurring with the Alpha update I sent you last night?

-Mike

Ahh - there's an alpha update.  I left the Android world for iOS for a couple years.  Makes sense.  I thought i was going crazy earlier this morning because I couldn't get my beta version to update to 4.514b from 4.513b - ha.  

Glad to hear the HSPA signal values and SNR are back.  

Mike - any update on when we might see the LTE bandwidth feature on more 9.0 devices?  I'm currently also using an AT&T S9+ like mdob07, I believe.  

Share this post


Link to post
Share on other sites
46 minutes ago, uecker87 said:

Mike - any update on when we might see the LTE bandwidth feature on more 9.0 devices?  I'm currently also using an AT&T S9+ like mdob07, I believe.  

I wonder if Samsung has a place to point out issues like android does? I'd love to get that working on my Verizon s9+ since Verizon locks out the engineering screens. Hopefully we'll see it in one of the upcoming patches. 

Share this post


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

Excellent, thanks for the detailed testing and screen shots! At the time of your GSM screenshot, the connection hadn't stabilized yet so the network type still shows "Connecting..." -- that intentionally causes the status bar icon to blank out. Funny that it comes up now, earlier today I was looking at it and considering changing that behavior. Displaying an icon with the dB reading but no connection type might not be a bad thing, since the reading itself is valid in my experience; I see it on my deactivated test devices that never get a true network connection but measure accurate signal strength.)

 

Ha, this is an interesting side effect that I had not considered. You are tripping that alert because it's seeing 67086 in your neighbor cell list. In this latest update you received, it searches the entire LTE "text block"; in previous versions, it only searched a few selected fields I chose. But this is by design.. someone might want neighbor cells included. The easy fix is to adjust your trigger to be "EARFCN: 67086" -- because that would only trip when you actually connect to it, since the neighbor cells aren't displayed with that prefix.

-Mike

4.514b has been stable all day on both of my phones. I haven't seen any issues out of either of them all day. Also I got the alerts setup the way I want and thats working great too!

  • Thanks 1

Share this post


Link to post
Share on other sites
On 4/11/2019 at 9:44 AM, uecker87 said:

Ahh - there's an alpha update.  I left the Android world for iOS for a couple years.  Makes sense.  I thought i was going crazy earlier this morning because I couldn't get my beta version to update to 4.514b from 4.513b - ha.

Haha sorry to disappoint, there were some bugs I was working on resolving with a few specific users and I expected it to take several updates, so I limited it to just them. Things seem good so when I have a chance I intend to get one final beta out to make sure it's ready for full release.

 

Quote

Mike - any update on when we might see the LTE bandwidth feature on more 9.0 devices?  I'm currently also using an AT&T S9+ like mdob07, I believe.  

That's up to device manufacturers.. SCP will reliably display whatever bandwidth info is being reported. It's part of the standard Android API now, they just need to take advantage of it. Similar to when the major LTE routines were added in Android 4.2 but it took awhile for that data to be consistently and accurately reported.

-Mike 

  • Like 2

Share this post


Link to post
Share on other sites

Another beta just released! Many more fixes.. hopefully this will take care of everything I was aware of.. let me know! Hopefully this version can go public later this week.....

-Mike

  • Like 6

Share this post


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

Another beta just released! Many more fixes.. hopefully this will take care of everything I was aware of.. let me know! Hopefully this version can go public later this week.....

-Mike

Q beta 2, still getting the no data when in background. Sending another diagnostics

Share this post


Link to post
Share on other sites
On 4/15/2019 at 8:42 PM, jefbal99 said:

Q beta 2, still getting the no data when in background. Sending another diagnostics

Hmm, no errors showing up, everything looks ok. Does it happen immediately upon it going into the background? Does it happen when you clear it out of recent apps? Any difference when you use the back button vs the home button vs choosing a different app from the recent apps list? Trying to narrow down where I should look for behavior changes first. It might be intentional or it might be a Q glitch.

-Mike

  • Like 2

Share this post


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

Hmm, no errors showing up, everything looks ok. Does it happen immediately upon it going into the background? Does it happen when you clear it out of recent apps? Any difference when you use the back button vs the home button vs choosing a different app from the recent apps list? Trying to narrow down where I should look for behavior changes first. It might be intentional or it might be a Q glitch.

-Mike

It varies, sometimes it goes blank immediately, others it will keep updating for a few minutes.  The same is true for going back in, sometimes it populates immediately, other times it takes 15-30 seconds.

I don't ever clear SCP from recent apps

Doesn't matter home button vs back button.

My gut is that it's Qs new security features, not providing data when the app is in the background.

  • Like 1

Share this post


Link to post
Share on other sites
It varies, sometimes it goes blank immediately, others it will keep updating for a few minutes.  The same is true for going back in, sometimes it populates immediately, other times it takes 15-30 seconds.
I don't ever clear SCP from recent apps
Doesn't matter home button vs back button.
My gut is that it's Qs new security features, not providing data when the app is in the background.
Have you tried exempting SCP from battery optimization?

Sent from my Pixel 3 XL using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, ingenium said:

Have you tried exempting SCP from battery optimization?

Sent from my Pixel 3 XL using Tapatalk
 

I did that and no change

  • Like 1

Share this post


Link to post
Share on other sites
I did that and no change
Hmm. Try plugging the phone in and see if it still does it.

It is possible that Q actually breaks this for background apps. P broke wifi scanning. It can scan for 3 or 5 seconds, then returns the same data for 30 or 60 seconds, then scans for 3 or 5, and repeat. It breaks all the wifi analysis apps that you use to figure out the optional channel, etc. Ironically, it also breaks the wifi rtt feature that Google touted in P.

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Share on other sites

New beta should be available within the hour, because a public update is rolling out now too.. only significant change for beta users is that LTE bandwidth display is controlled by an option that is disabled by default. Go to Preferences > Display Settings to enable it if you want it. This way users have to read a little blurb warning that it may not be reliable.

Thanks to all for helping test this release out, there were a lot of hiccups to iron out. Now, back to work on the new carrier aggregation stuff I discovered....

-Mike

  • Like 1
  • Love 1

Share this post


Link to post
Share on other sites
On 4/17/2019 at 5:08 PM, ingenium said:

Hmm. Try plugging the phone in and see if it still does it.

It is possible that Q actually breaks this for background apps. P broke wifi scanning. It can scan for 3 or 5 seconds, then returns the same data for 30 or 60 seconds, then scans for 3 or 5, and repeat. It breaks all the wifi analysis apps that you use to figure out the optional channel, etc. Ironically, it also breaks the wifi rtt feature that Google touted in P.

Sent from my Pixel 3 XL using Tapatalk
 

No change, plugged in or on battery

On 4/18/2019 at 5:59 AM, mikejeep said:

New beta should be available within the hour, because a public update is rolling out now too.. only significant change for beta users is that LTE bandwidth display is controlled by an option that is disabled by default. Go to Preferences > Display Settings to enable it if you want it. This way users have to read a little blurb warning that it may not be reliable.

Thanks to all for helping test this release out, there were a lot of hiccups to iron out. Now, back to work on the new carrier aggregation stuff I discovered....

-Mike

Q beta 2 Pixel 2XL, I enabled the Bandwidth setting, but nothing is displayed.  I sent in a diagnostic

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

    • So I figured out there is a way to check if a phone is using Calling+ or VoLTE without root. If engineering (not SCP) reports the PLMN as 310120, then it is not VoLTE. VoLTE only runs on 312530. That being said, a phone can be on 312530 but not use VoLTE (Pixel 2 for example). So being on 312530 is not sufficient to say that it is using VoLTE, but being on 310120 IS sufficient to rule out VoLTE being used. As for the "flag" Sprint uses to enable/disable it on supported devices, I suspect that they use the TAC. I think there is a hardcoded whitelist of TACs where it will be enabled. So they can change the TACs for a market to "enable" it, but by default it's "disabled". If this is the case, then Magic Box TACs are simply not whitelisted yet, even though it works fine on them. I've verified that VoLTE works on a Magic Box with at least the 440a firmware, and possibly earlier versions as well. Sent from my Pixel 3 XL using Tapatalk
    • You're referring to this: https://arstechnica.com/tech-policy/2019/04/lawsuit-atts-directv-now-is-a-flop-and-att-lied-to-investors-about-it/ That's not beyond the realm of possibility for Sprint... especially given how any lawsuit would occur subsequent to the alleged "lying". Sprint's FCC Filing is supported by empirical and highly confidential data on its adds/losses, churn, etc. throughout the report. I believe it shows a serious situation. Even more so, Sprint says in the Filing that its investor statements noting certain accomplishments shouldn't detract from the seriousness of its current predicament. See Pages 36-42 of the FCC Filing, which includes this: "The recent improvements in some financial metrics simply cannot, and do not, overcome these fundamental challenges:" On balance, I'm more willing to believe the information in the FCC Filing which specifically references and dismisses the investor statements than in the investor statements alone. If the redacted "highly confidential" information in the Filing was made available to investors, I believe Sprint stock would be substantially impacted... as that information reflects the ground truth of what's happening with Sprint.
    • Then I hope whoever gets Sprint buys Dishes spectrum hell even uscc or New TMO Sent from my SM-G965U1 using Tapatalk
    • Dish does not have any money.They spent it all on spectrum.
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...