Jump to content

SignalCheck - Android app to monitor your Wi-Fi/2G/3G/4G LTE/5G-NR signal strengths


mikejeep

Recommended Posts

Actually I think I do recall you mentioning that bug shortly after I had noticed it myself. The only reason it slipped through the cracks on my end was because I didn't have a non-CDMA LTE device to test with. Nexus 5 FTW!

 

I went back and read the transcripts from last month, and I did not see that I specifically mentioned the -85 dBm readout bug.  I think I intended to include it in a follow up post that never happened.

 

AJ

Link to comment
Share on other sites

Hey Mike I have a traiterous question since it doesn't involve Sprint... :devil:

 

A friend of mine is planning on getting one of those new Tracfone android phones which supposedly operate on Verizon's CDMA system.  He spotted SignalCheck on my Sprint phone and wondered if it would work.  I've heard Verizon doesn't transmit site coordinates so that probably won't work but will the rest of the app work?  The phone he is looking at uses android 4.0. 

Link to comment
Share on other sites

Hey Mike I have a traiterous question since it doesn't involve Sprint... :devil:

 

A friend of mine is planning on getting one of those new Tracfone android phones which supposedly operate on Verizon's CDMA system. He spotted SignalCheck on my Sprint phone and wondered if it would work. I've heard Verizon doesn't transmit site coordinates so that probably won't work but will the rest of the app work? The phone he is looking at uses android 4.0.

No worries.. the app does not care who the wireless provider is, it will work on any device running Android 2.2 or newer. There is also an older version for Android 2.1, but it does not have as many features and will not receive any updates.

 

You already noted the one drawback for Verizon users.. other than that, everything else should work fine. And if Verizon changes their mind someday, SignalCheck will start showing a BSL for them too ;)

 

-Mike

Link to comment
Share on other sites

No worries.. the app does not care who the wireless provider is, it will work on any device running Android 2.2 or newer.

 

Wow, I think I remember Android 2.2 "Froyo" back when I was only 33.  I was just a kid.  Oh, those were the days...

 

;)

 

AJ

  • Like 5
Link to comment
Share on other sites

Wow, I think I remember Android 2.2 "Froyo" back when I was only 33.  I was just a kid.  Oh, those were the days...

 

Man, you're old. I think I was only 30 when that went down.. ah, memories. I remember rooting my EVO Shift (a Windows phone for those of you unfamiliar) to get a hacked-together version of Froyo on it. Even with its limited functionality, I remember thinking it was exactly what I hoped to see on phones someday. Still love it, many desserts later.

 

I have no problem supporting older devices, at least for now. They are actually easier, manufacturers didn't try as much funny business behind the scenes back then, and there was none of this crazy new-fangled LTE stuff to worry about!

 

-Mike

  • Like 1
Link to comment
Share on other sites

Man, you're old. I think I was only 30 when that went down.. ah, memories. I remember rooting my EVO Shift (a Windows phone for those of you unfamiliar) to get a hacked-together version of Froyo on it. Even with its limited functionality, I remember thinking it was exactly what I hoped to see on phones someday. Still love it, many desserts later.

 

I have no problem supporting older devices, at least for now. They are actually easier, manufacturers didn't try as much funny business behind the scenes back then, and there was none of this crazy new-fangled LTE stuff to worry about!

 

-Mike

Like getting the Sammies to show the serving cell......

Link to comment
Share on other sites

Like getting the Sammies to show the serving cell......

 

Well that's not really funny business.. prior to Android 4.2, there was no standard Android routine to get the LTE cell identity. So to get it, you need an alternate method, like SignalCheck uses to get it on HTC devices. Unfortunately, other manufacturers do not make access to this data very easy, and Samsung has security measures in place that complicate things even further. Making things worse, Samsung has been slow to add "standard" support in their devices running Android 4.2.

 

I'm still working on it though, because I know how valuable that data would be for my Samsung users. Until last month, Samsung and HTC devices were by far the most popular among SignalCheck users. Now the Nexus 5 and G2 have exploded onto the stat sheet, so I am trying to add more support for LG devices, but I am not abandoning my Samsung efforts.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Well that's not really funny business.. prior to Android 4.2, there was no standard Android routine to get the LTE cell identity. So to get it, you need an alternate method, like SignalCheck uses to get it on HTC devices. Unfortunately, other manufacturers do not make access to this data very easy, and Samsung has security measures in place that complicate things even further. Making things worse, Samsung has been slow to add "standard" support in their devices running Android 4.2.

 

I'm still working on it though, because I know how valuable that data would be for my Samsung users. Until last month, Samsung and HTC devices were by far the most popular among SignalCheck users. Now the Nexus 5 and G2 have exploded onto the stat sheet, so I am trying to add more support for LG devices, but I am not abandoning my Samsung efforts.

 

-Mike

Keep up the great work! Signal Check on my Nexus 5 is great, especially dropping the 1x signal indicator when the N5 is on LTE. Definitely clears things up.

  • Like 2
Link to comment
Share on other sites

Well that's not really funny business.. prior to Android 4.2, there was no standard Android routine to get the LTE cell identity. So to get it, you need an alternate method, like SignalCheck uses to get it on HTC devices. Unfortunately, other manufacturers do not make access to this data very easy, and Samsung has security measures in place that complicate things even further. Making things worse, Samsung has been slow to add "standard" support in their devices running Android 4.2.

 

I'm still working on it though, because I know how valuable that data would be for my Samsung users. Until last month, Samsung and HTC devices were by far the most popular among SignalCheck users. Now the Nexus 5 and G2 have exploded onto the stat sheet, so I am trying to add more support for LG devices, but I am not abandoning my Samsung efforts.

 

-Mike

Yea Samsung has always been broader on things they do with Android. I've used a Captivate, GNex, S3 & S4. I am the proud owner of Signal Check Pro. Its a great app. I know your doing everything you can and everyone appreciates it, but I'm ready for the day when you "crack their code" to be able to have the cell id display in your app on the Samsungs.

Link to comment
Share on other sites

Man, you're old. I think I was only 30 when that went down.. ah, memories. I remember rooting my EVO Shift (a Windows phone for those of you unfamiliar) to get a hacked-together version of Froyo on it. Even with its limited functionality, I remember thinking it was exactly what I hoped to see on phones someday. Still love it, many desserts later.

 

I have no problem supporting older devices, at least for now. They are actually easier, manufacturers didn't try as much funny business behind the scenes back then, and there was none of this crazy new-fangled LTE stuff to worry about!

 

-Mike

I think that was the Touch Pro, since the Evo Shift was also an Android phone :)

  • Like 1
Link to comment
Share on other sites

I think that was the Touch Pro, since the Evo Shift was also an Android phone :)

 

Right.  Mike must be getting senile in his married, old age.

 

AJ

  • Like 4
Link to comment
Share on other sites

I think that was the Touch Pro, since the Evo Shift was also an Android phone :)

Ha!! I knew that didn't sound right.. yep, it was the TP2. That's why you should sleep at 5am, not go S4GRUing. I still miss my physical keyboard!

 

-Mike

Link to comment
Share on other sites

Mike,

 

Got a bug, second or third time I've seen this where the app is not decoding the SID 4126 to be Sprint.

 

integration

 

It takes restarting the app for the Provider to be identified as Sprint.
Link to comment
Share on other sites

Got a bug, second or third time I've seen this where the app is not decoding the SID 4126 to be Sprint.

 

It takes restarting the app for the Provider to be identified as Sprint.

Nice screen shot collage there, thanks! Hmm.. that's new. Are you on 4.19? Are you able to see any logcat messages?

 

-Mike

Link to comment
Share on other sites

I have seen that once before as well where it said SID 4159 instead of Sprint. I hit reset data connection and it fixed it though.

I think the functions that query the provider database throw all errors to logcat, so if anyone sees the behavior and can catch the logcat message, please let me know. A lot of the database stuff is finicky but very tweakable.

 

Unrelated note: Can anyone with an LG G2 confirm if the new system shortcuts added in 4.19 work correctly?

 

-Mike

Link to comment
Share on other sites

Nice screen shot collage there, thanks! Hmm.. that's new. Are you on 4.19? Are you able to see any logcat messages?

 

-Mike

I'll check logcat next time it happens.

 

The collage was because all the sites on my drive to work and in town got new BIDs last night.  I made that for the West Michigan thread :)

  • Like 1
Link to comment
Share on other sites

Nice screen shot collage there, thanks!

He should have it made into a quilt.

 

:P

 

AJ

  • Like 4
Link to comment
Share on other sites

 

Unrelated note: Can anyone with an LG G2 confirm if the new system shortcuts added in 4.19 work correctly?

 

-Mike

Data and Debug do not. Stock Unrooted G2.

 

Sent from my LG-LS980 using Tapatalk

 

 

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


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