Jump to content

Sensorly reporting wrong signal


TheForce627

Recommended Posts

Idk if this has been brought up or I'm just wrong but I've noticed sensorly reporting whatever you 1x signal is when mapping LTE. In an area connected to smr I had full bars but a weak LTE signal around -115, sensorly reported this as full bars LTE. I believe this is the reason a site in the dc area was mislabeled as having 4g complete. For reference this is site WA23XC308

Link to comment
Share on other sites

Idk if this has been brought up or I'm just wrong but I've noticed sensorly reporting whatever you 1x signal is when mapping LTE. In an area connected to smr I had full bars but a weak LTE signal around -115, sensorly reported this as full bars LTE. I believe this is the reason a site in the dc area was mislabeled as having 4g complete. For reference this is site WA23XC308

Maybe that tower was on for testing then taken down after it. Thus why one might be higher than the other

Link to comment
Share on other sites

Idk if this has been brought up or I'm just wrong but I've noticed sensorly reporting whatever you 1x signal is when mapping LTE. In an area connected to smr I had full bars but a weak LTE signal around -115, sensorly reported this as full bars LTE. I believe this is the reason a site in the dc area was mislabeled as having 4g complete. For reference this is site WA23XC308

 

I have never had this problem. In my Wichita Falls and Waco mapping it only shows LTE signals. In Waco, I always had full bars of 1x signal because it is a CDMA 800 market, and yet it clearly shows all over that market the LTE signal strength very clearly and separate from my 1x.

 

It is also clear to me looking at my Wichita Falls mapping that it shows LTE signal strength very well, also. There are four sites that have not received LTE around the city, where I encounter very strong 1x signals and very weak LTE signals, and these are all shown as weak LTE signals.

 

I did once receive a PM from a member in Puerto Rico who has a Galaxy Nexus that he had a custom MOD on and he said all his Sensorly reporting around the San Juan area was coming in at full strength, no matter what his 1x and LTE signals actually were.

 

Are you using a custom MOD? If not, then perhaps you are mistaken? I guarantee you that Sensorly IS NOT harvesting 1x data as LTE signal data. However, your device may be mistakenly providing that.

 

Robert

Link to comment
Share on other sites

Gnex running a custom rom. Maybe that's it. For me it's been reporting my 1x signal. I can confirm that tower I listed in my first post isn't broadcasting LTE although dark purple is around it.

 

Yeah, definitely stop reporting on Sensorly until you figure out the problem.

 

Robert

Link to comment
Share on other sites

Oh, Darn. I was just about to flash nitroglycerine33's Eclipse 2.1 ROM. Guess I'll have to flash back to stock to run Sensorly when I go to LA.

I ran eclipse on my Gnex with no issues.

 

Sent from a phone using an application. That's pretty cool.

 

 

Link to comment
Share on other sites

I'm running Frankenstein ROM on my Samsung Galaxy S III and have done so for the past month. It must be this specific ROM not allowing Sensorly app to record the LTE signal from my phone. Just this afternoon I had tracked LTE from on PCH starting around highway 103 to Vermont Avenue. Then from Vermont Avenue to Gaffey Street to Westmont. I even ran speed tests via Speedtest app at a few red lights showing strong LTE signal.

 

Damn. I love this ROM, but I also enjoy tracking when I find LTE in an unrecorded area. What a dilemma.

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

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