Jump to content

Sensorly reporting wrong signal


TheForce627
 Share

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Update just showed up for both of my phones. So far I don't notice any difference, LTE TA is still reporting as 0, I was hoping the new routine might fix that. I sent a diag report from both phones in case you need any of that info. I'll let you know in a day or so if its crashing as frequently or not. 
    • A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes: New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this. New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working. Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing. Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact. Feedback welcome as always!
    • Another converted keep site: Sprint eNB 9436 -> T-Mobile eNB 895067 (40.60777246698788,-74.16199692361377) Looks like they're using the FFVV-65A-R2-V1 here, as well!   Edit: Also, I know this technically isn't NYC, but here's a Jersey City conversion. Not 100% sure on either eNB. Sprint eNB 105863 -> T-Mobile eNB 876452 (40.72265196811989,-74.08804945021805)
    • More confirmations incoming! T-Mobile eNB 880561 (40.74176835140717, -73.88364207139453)   Sprint eNB 6191 / T-Mobile eNB 880065 (40.71339007010928, -73.85695387371624) Confirmed this site but was unable to get a photo because the antennas are set back from the edge of the building. I could see them from super far away but there wasn't a good area for me to pull over and snap a pic.   Sprint eNB 6189 / T-Mobile eNB 877995 (40.71183894845567, -73.83529788316665)   Sprint eNB 253741 / T-Mobile eNB 875537/875538 (40.70170960850086,-73.83302208208359)   Sprint eNB 79912 / T-Mobile eNB 875989 (40.86349197342981, -73.923456682535) — — — — — T-Mobile eNB 880536 in the Bronx isn't a Sprint conversion but rather, T-Mobile changed the eNB when they upgraded the site. The nearest Sprint site at 40.8150405321864, -73.93010756429787 still has all of its antennas up and is literally within spitting distance of two other T-Mobile sites in an area that's very industrial as opposed to residential or commercial so a keep site isn't particularly necessary. You can see on Cellmapper that the old eNB stopped broadcasting about two days after the new eNB went live.  — — — — — Also wanted to add that I spotted AT&T C-band antennas quite a bit in both Queens and the Bronx. I would expect a summer C-band launch announcement from them because they're moving FAST. At least in my area, it seem like they're upgrading at a faster pace than Verizon is. Some more pics: AT&T eNB 116408 / T-Mobile eNB 42887 in Woodhaven. This one is interesting because T-Mobile upgraded this site but in the process didn't put any Ericsson n41 antennas. There are just two of the RFS antennas that we normally get.   AT&T eNB 112047, bad pic but the arrows on the billboard are pointing right at the C-band antenna lol   — — — — — Last edit I promise: I noticed T-Mobile submit a permit to convert the keep site I found in Staten Island (Sprint eNB 75141). I 100% guessed it's location since I connected to it literally 4.5 miles across the water while inside a building. Glad to see I was right!
    • Support for the -1 TAC is good to go now, so I'm ready whenever you are!
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...