Jump to content

SignalCheck Beta Crew Forum


mikejeep

Recommended Posts

On LG V20 removing 1x, donating, show external IP address all seem to work. Shouldn't show external ip address also show IPv6? I will report on logs and other phones later.

Thanks! Right now it forces IPv4 but I can tweak that if there's a desire for IPv6. Also, I am still working on optimizing that function; right now it pings my server every time the screen updates. It's a very small amount of data, but I am cognizant that it adds up over time.

 

-Mike

  • Like 1
Link to comment
Share on other sites

New beta is out! Please check out the updates from the change log and try to break it. Any feedback is welcome.

 

The improved diagnostic reports seem to be solid, I'm mostly interested in making sure the UI makes sense. If it says they sent, they did -- if it says they didn't, they will be saved (I'll disregard any reports I come across that look like you're testing). They will be attempted again when another new report is attempted to be sent, or by going to the Send Diagnostics screen and clicking "Send Saved Only".

 

Hiding 1X and configuring where the Reset button appears are significant new options.

 

Thanks!

-Mike

 

Very cool!  I'll take my Verizon phone out with me tomorrow and try to do a diagnostic while I'm out and about.  Then, when I get home, I'll try to submit it via Wi-Fi.

 

- Trip

  • Like 2
Link to comment
Share on other sites

In this latest beta update, the icon for Verizon's Band 5 is broken. It just has a regular "LTE" icon now without "B5" on it.

 

EDIT: Actually, reporting on it seems to just be broken. This is with the old build, an old screenshot I had lying around:

 

0KYMetvl.png

 

And here is what it currently looks like on the latest beta build:

 

6iRcyXul.png

 

Bands 2, 4 and 13 work just fine, however.

Link to comment
Share on other sites

In this latest beta update, the icon for Verizon's Band 5 is broken. It just has a regular "LTE" icon now without "B5" on it.

 

EDIT: Actually, reporting on it seems to just be broken. This is with the old build, an old screenshot I had lying around:

 

Bands 2, 4 and 13 work just fine, however.

 

Hmm.. I just double-checked the code and graphics, and it all seems to be ok. It worked fine on the previous release (4.43)? Send me diagnostics when you see it again if you can. Got me stumped for the moment.

 

-Mike

Link to comment
Share on other sites

Very cool!  I'll take my Verizon phone out with me tomorrow and try to do a diagnostic while I'm out and about.  Then, when I get home, I'll try to submit it via Wi-Fi.

 

- Trip

 

Sent it in.  Let me know if it worked. 

 

- Trip

  • Like 1
Link to comment
Share on other sites

Hmm.. I just double-checked the code and graphics, and it all seems to be ok. It worked fine on the previous release (4.43)? Send me diagnostics when you see it again if you can. Got me stumped for the moment.

 

-Mike

I'll get a diagnostic but it did work in the last release. The only word thing I could think of is that my work has a repeater which covers B5 since we're in a basement. Does that seem like it would affect anything? I'm in a big city so it's extremely difficult to willingly get B5/B13 besides near the repeater. (I'm pretty sure it was fine before, though.)
Link to comment
Share on other sites

Sent it in.  Let me know if it worked. 

 

Moto G Play, saved around 1:45PM? Received it around 6PM! I did notice some unrelated errors related to getEarfcn() routine, but they are timestamped 6/20.. have you not rebooted that device in awhile?

 

-Mike

Link to comment
Share on other sites

I'll get a diagnostic but it did work in the last release. The only word thing I could think of is that my work has a repeater which covers B5 since we're in a basement. Does that seem like it would affect anything? I'm in a big city so it's extremely difficult to willingly get B5/B13 besides near the repeater. (I'm pretty sure it was fine before, though.)

 

At first I thought that shouldn't impact anything, it's the same GCI in both screenshots so that rules anything like that out.. but I just got a report from @lilotimz showing a similar icon issue on T-Mobile Band 4. Then I noticed your Verizon GCI ended in 1D, which isn't pre-identified by the app; you're seeing a band indicator from the Android 7 routine. So I think I know where to start looking.. send that report if you have a chance though.

 

-Mike

  • Like 1
Link to comment
Share on other sites

At first I thought that shouldn't impact anything, it's the same GCI in both screenshots so that rules anything like that out.. but I just got a report from @lilotimz showing a similar icon issue on T-Mobile Band 4. Then I noticed your Verizon GCI ended in 1D, which isn't pre-identified by the app; you're seeing a band indicator from the Android 7 routine. So I think I know where to start looking.. send that report if you have a chance though.

 

-Mike

Same issue on 12/4/2. I've been sending you reports since Sunday.... Did you get thosel

 

Sent from my Pixel using Tapatalk

Link to comment
Share on other sites

At first I thought that shouldn't impact anything, it's the same GCI in both screenshots so that rules anything like that out.. but I just got a report from @lilotimz showing a similar icon issue on T-Mobile Band 4. Then I noticed your Verizon GCI ended in 1D, which isn't pre-identified by the app; you're seeing a band indicator from the Android 7 routine. So I think I know where to start looking.. send that report if you have a chance though.

 

-Mike

You know what, something that I bet caused it was that I moved from the latest Android O Preview 3 back to Android 7.1.2. Sorry, totally should have mentioned that. Is the O codepath different?

Link to comment
Share on other sites

Moto G Play, saved around 1:45PM? Received it around 6PM! I did notice some unrelated errors related to getEarfcn() routine, but they are timestamped 6/20.. have you not rebooted that device in awhile?

 

-Mike

 

Yep, that's it.  I wasn't reporting anything in particular, just wanted to be sure you had at least one outside test of the saved submission functionality.  :)

 

And I don't reboot my devices unless it's necessary.  The last time I rebooted that phone was probably in May when I turned it off for the flight back from Denver.

 

- Trip

  • Like 1
Link to comment
Share on other sites

Same issue on 12/4/2. I've been sending you reports since Sunday.... Did you get those

 

After I caught up on S4GRU and saw littlejth's post, I went through the reports and saw a few from you since Monday morning with the same issue -- your reports are what helped clue me in what I had broken..

 

 

You know what, something that I bet caused it was that I moved from the latest Android O Preview 3 back to Android 7.1.2. Sorry, totally should have mentioned that. Is the O codepath different?

 

Nope, that should not matter in this case. But, good news.. I think I found the bug, I think I squashed it, and I just pushed out another beta update. Resolved a separate minor bug with the LTE title on the main screen as well, I don't think that was updating immediately in certain scenarios. Try it out and let me know!

 

Thanks,

-Mike

  • Like 4
Link to comment
Share on other sites

After I caught up on S4GRU and saw littlejth's post, I went through the reports and saw a few from you since Monday morning with the same issue -- your reports are what helped clue me in what I had broken..

 

 

 

Nope, that should not matter in this case. But, good news.. I think I found the bug, I think I squashed it, and I just pushed out another beta update. Resolved a separate minor bug with the LTE title on the main screen as well, I don't think that was updating immediately in certain scenarios. Try it out and let me know!

 

Thanks,

-Mike

 

App doesn't even open now. Force closes on start. 

Link to comment
Share on other sites

App doesn't even open now. Force closes on start. 

 

Got that warning from Google's pre-launch testing service several minutes after I uploaded. Can't figure out why, compiles fine on my end.. was hoping it was a glitch on their end. I'll update shortly..

 

EDIT: I have no idea what the issue was.. I resaved, recompiled, and re-uploaded it, and suddenly the APK is 900kb larger. Google didn't throw any testing errors this time, so give it a try.

 

-Mike

Edited by mikejeep
  • Like 3
Link to comment
Share on other sites

Got that warning from Google's pre-launch testing service several minutes after I uploaded. Can't figure out why, compiles fine on my end.. was hoping it was a glitch on their end. I'll update shortly..

 

EDIT: I have no idea what the issue was.. I resaved, recompiled, and re-uploaded it, and suddenly the APK is 900kb larger. Google didn't throw any testing errors this time, so give it a try.

 

-Mike

SCP does load correctly on a LG V20.

 

With more screen space with the 1x with LTE toggle, I have noticed the long list of unknown neighbors. If there is no usefull data such as PCI or EARFCN, I don't see the value of displaying them.

 

I was excited at first reading about adding location to notes thinking you were adding a site location column(s) so RSRP could be used for its original purpose (rather than setting it to -1 to fix the location to the site location). I do think the here button will be useful to many.

 

Sent from my LG-LS997 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Yep, that's it. I wasn't reporting anything in particular, just wanted to be sure you had at least one outside test of the saved submission functionality. :)

 

And I don't reboot my devices unless it's necessary. The last time I rebooted that phone was probably in May when I turned it off for the flight back from Denver.

 

- Trip

Too much bad memory management by the apps and OS to wait that long. I reboot every few weeks to a month at a minimum for a more stable phone experience. You can go longer on newer phones than before.

 

Sent from my LG-LS980 using Tapatalk

Link to comment
Share on other sites

Too much bad memory management by the apps and OS to wait that long. I reboot every few weeks to a month at a minimum for a more stable phone experience. You can go longer on newer phones than before.

 

Sent from my LG-LS980 using Tapatalk

 

Considering these phones are literally only used for SCP/NSG, I've rarely encountered such issues.  My bigger problem, actually, is the constant prompting for updates that I can't install because I've replaced the bootloader.  I can kill them, but on reboot, the prompts start right back up again.

 

- Trip

  • Like 1
Link to comment
Share on other sites

If rooted, did you try press and hold on these messages which then allows you to delete them? Or fotakill (beware of fakes).

 

Sent from my LG-LS997 using Tapatalk

Link to comment
Share on other sites

If rooted, did you try press and hold on these messages which then allows you to delete them? Or fotakill (beware of fakes).

 

Sent from my LG-LS997 using Tapatalk

 

Hard to press and hold a full-screen message that I need to update.  (Which then defeats the "keep screen on" in SCP...)

 

I'll check out fotakill.

 

- Trip

  • Like 1
Link to comment
Share on other sites

LTE 850 appears to be working fine now on the latest build on my Google Pixel.

 

Excellent! It wasn't band-specific, it was bad logic on my part. Only would have affected a relatively small percentage of users in very specific circumstances (as you noticed) so I'm glad you guys caught it, thank you!

 

Lurkers, good news.. I hope to make the current version the public release, as long as no more bugs pop in the next few days.

 

-Mike

  • Like 3
Link to comment
Share on other sites

Excellent! It wasn't band-specific, it was bad logic on my part. Only would have affected a relatively small percentage of users in very specific circumstances (as you noticed) so I'm glad you guys caught it, thank you!

 

Lurkers, good news.. I hope to make the current version the public release, as long as no more bugs pop in the next few days.

 

-Mike

 

Working fine now. Thanks. 

  • Like 1
Link to comment
Share on other sites

With more screen space with the 1x with LTE toggle, I have noticed the long list of unknown neighbors. If there is no usefull data such as PCI or EARFCN, I don't see the value of displaying them.

 

I was excited at first reading about adding location to notes thinking you were adding a site location column(s) so RSRP could be used for its original purpose (rather than setting it to -1 to fix the location to the site location). I do think the here button will be useful to many.

 

The "Unknown" neighbors are on almost always on a different EARFCN. Something broke in new versions Android with this; it worked rather well on Marshmallow. I thought there was a bug report already filed for this, but I can't find it so I just filed another.. please 'star' it to try helping it get attention: https://issuetracker.google.com/issues/63848701

 

I still intend to add some columns to the database, just trying to tackle the issues that impact the most users first. I know you and @Trip will do a little dance when that happens!

 

-Mike

  • Like 2
Link to comment
Share on other sites

Mike,

 

In the change log, you mention this:  Added feature to add current location to a site note.  I just now found it, having thought it meant something else.  But my first attempt at using it, sitting here in my office at work, said "Location unavailable!" even though I have GPS coordinates shown at the top of my screen.  (The GPS is not currently locked, however, since I'm indoors.)  Not sure there's a bug here, but wanted to point it out.

 

- Trip

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...