- Badly configured basebands (for example lack of summer/winter time change flag!)
- Broken PTP
- Stations that take time from NTP which does not exist or does not have route to.
- I don't know the name for it, but getting time from local Nodeb is an feature - and sometimes features are not active or licensed[1].
- Station setup with GPS instead PTP/NTP (let's say for 2G or some slower HDSPA modes) with broken GPS module itself
- Software error [basebands have multiple versions of software, same goes for APG's, SCU'S, RRU's and dozen other black boxes. Even cabinet itself have some software. This is big pain in the ass to keep them all updated in large network - as upgrade process can be disruptive and sometimes it is better to not upgrade [cases of some really wacky stations]...
- Problem with software in terms of PTP implemetation. For example there are some discrepancies between Huawei and Ericsson software when it comes to PTP.
[1]. This is big shocker for Open Source Software community:
- EVERY SINGLE FEATURE in base station is not only NOT free, but Telecoms needs to pay them every single month[all manufactures: Nokia, Ericsson, HUA do that]. We are talking here in about 100-200 licenses for various features per site alone. If you don't buy new license every 28 days - your base station will turn off and it's nothing you can do.
- Hardware provider can also refuse to give you new licenses in theory...
- This is real hell of SaS world that NO ONE is talking about.
The problem i had is, that the time in my case was in the future, so when i called someone (personA) from within that cell, the call was made sometime in 2025... this wouldn't bother me in general, but when you use the redial function in your headset (double tap on the button), the phone would call the last dialed number (which means max(timestamp), not the actual last call), and instead of ringing the last person dialed (eg. personB), it would redial the personA I called from the affected cell, and after misdialing them by accident, a couple of times, I had to manual remove that call from the calllog, to get the redial to work again... until I entered that cell again and called someone from there again.
Eventually somebody figured out that he wasn’t going away, and a couple of very pleasant guys popped in and dropped off their business cards. They told him it wouldn’t be a problem anymore and to give them a call if it became a problem again.
End of the day, if someone is creating interference, they need to stop. If you have the time and inclination, complain and they will.
Since it took me a minute to parse: the guy on the team, not the university police, was the one who walked the hierarchy?
> End of the day, if someone is creating interference, they need to stop.
I'm not sure which way to interpret this, your username might check out after all.
During the summer Utah is on daylight savings time, Arizona does NOT observe daylight savings time but the Navajo Nation within Arizona DOES observe daylight savings time.
Antelope Canyon is on Navajo Nation land and requires a tour guide from a licensed tour guide company. The canyon and tour guides DO observe daylight savings time.
The canyon is only about 5 miles from the Utah border and many people are traveling from Utah. Because of all the competing cell phone towers you end up with people that show up at the wrong time.
I purposely brought an old school watch for my trip.
edit: it is West Wendover NV
They probably want to stay on Mountain time because 99% of their visitors/customers are from Salt Lake City on mountain time and their TV stations are also probably from Salt Lake City
Since then, I've not trusted that automatic network time adjustment, and I leave it disabled. Periodically, I check if it's drifted too much, and if it has, I quickly enable and then disable the network time adjustment (in a place far from the misconfigured tower).
But not if it is a stingray as that's not managed by the network.
This was when SMS were still widely used, so that made for very messed up chats since received messages carried the correct timestamp