Jump to content

Sprint GPS Glitch Making Poor Guy's Life Hell


Recommended Posts





Sprint GPS Glitch Making Poor Guy's Life Hell

Everyone Thinks He Stole Their Phone -- Including Police


A Sprint network glitch is incorrectly directing users to the home of Wayne Dobson in North Las Vegas. According to the Las Vegas Review Journal, an unexplained location and GPS data glitch is sending victims of cellphone and tablet theft -- and the police looking for them -- to this poor guy's home at all hours of the day and night.


The problem only appears to be plaguing owners of Sprint phones, who Dobson says he's had no limit of unpleasant run ins with as he has to repeatedly explain to them that he hasn't stolen their devices. As you might expect, the quality of his sleep isn't the greatest:


The problem appears to be limited to some owners of Sprint phones. Company officials said they are researching the problem, which has forced Dobson to sleep near his front door on weekends so he can answer the door quickly at all hours. "It's a hell of a problem," he said. "It would be nice to be able to get a good night's sleep."Sprint insists they're researching the problem

Link to comment
Share on other sites

Wow… poor guy. This is probably made worse for him by the fact that he doesn’t sound particularly technically-inclined, so his ability to try to explain what’s going on to people who are already angry is limited. The fact that they’re mad and so sure that they’ve got hard evidence can really make for a dangerous situation.


What I want to know is whether whatever tracking service these victims are using show how accurate the reported location of their stolen phone is. For example, on Google Maps, if you don’t have your GPS on, it shows your location with an error circle which is based off of the surrounding towers. I can imagine this error circle being completely ignored by some (or even just missing in the tracking software) which leads the victims to go right to the center point. If some amount of error is displayed by the tracking software, then his nearest neighbor must be hundreds of feet away.


I wonder just how well the locations all of these victims’ phones match up. Some apps show your latitude and longitude coordinates to within several decimal places, and even with a small amount of error, two phones right next to each other might not show the exact same numbers. If it is a software glitch on Sprint’s side, I’m wondering if all of these numbers are the same, down to the last digit.

Link to comment
Share on other sites

I'm concerned for this man's safety. The wrong person thinks he stole their phone, they could attack him or shoot him. Sprint could be liable. They need to do something stat. Tomorrow is not good enough.



  • Like 4
Link to comment
Share on other sites

Instead of answering the door, he should just put a poster explaining the issue and a no trespassing sign.


He has put up a sign. Read the linked article.


Now, I wonder if Wayne Dobson is part of the Dobson family that sold out DCOC to AT&T. If so, this could be his comeuppance.





  • Like 2
Link to comment
Share on other sites

Okay, maybe this is just that vaunted "common sense" talking here, but, it seems like part of this is morons. Not to say that there couldn't be a serious issue here, but still. CriticalityEvent is on the money with that one - most tracking software gives you a pretty wide range of addresses when GPS is disabled or not working properly (most of the time when a phone is dead and they're going off of old info).


For the record, I just used Sprint's "The Protection App" phone locator, and after trying for three minutes, it simply came up with the name of my town. When I said "see on a map", it put me a couple doors down. My actual location was the faaar left edge of the (sizable) circle.


Edit: Ran it a second time, and it said:

Your phone has been located at:



Great, so it's somewhere in the state. Lovely.


Not only that, if your phone is in a place you do not recognize, why in God's holy name would you go there!? Calling the police should be the first step, not running up and banging on the door, or trespassing on his property! That's the definition of "not safe".

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

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

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