![]() ![]() ![]() ![]() |
|
sbiddle:Ragnor: As per title I am curious why Vodafone NZ still not do not support carrier time / NITZ?
It seems the majority of carriers around the world support it now:
http://en.wikipedia.org/wiki/NITZ
ClockSync on my Android on Vodafone is good workaround but it would be nice if it wasn't needed
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=en
https://play.google.com/store/apps/details?id=ru.org.amip.timezoneservice
NITZ is still deployed by a small % of carriers globally and is still the exception rather than the norm.
I don't know VF's official reasons for not having it but I would take a stab and say the licencing costs for such a feature will be big (like most NSN licencing charges) and in a country with a single timezone it's argueably far less useful than countries with multiple timezones.
Batwing: Gave my old xperia mini pro to the girlfriend, had network time for me on 2degrees but not for her on Vodafone. Are they implemented differently?
Ragnor:sbiddle:Ragnor: As per title I am curious why Vodafone NZ still not do not support carrier time / NITZ?
It seems the majority of carriers around the world support it now:
http://en.wikipedia.org/wiki/NITZ
ClockSync on my Android on Vodafone is good workaround but it would be nice if it wasn't needed
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=en
https://play.google.com/store/apps/details?id=ru.org.amip.timezoneservice
NITZ is still deployed by a small % of carriers globally and is still the exception rather than the norm.
I don't know VF's official reasons for not having it but I would take a stab and say the licencing costs for such a feature will be big (like most NSN licencing charges) and in a country with a single timezone it's argueably far less useful than countries with multiple timezones.
26 supporting vs 6 not listed in the wikipedia article I linked, how many carriers are missing from that list?
johnr: We don't provide mobile coverage for crayfish either
Twitter: ajobbins
NOTE: Universal time indicates the time at which this information element (see 3GPP TS 24.008 [2]) may have
been sent by the network. Thus it can be assumed that the accuracy of the time information when it
arrives at the MS is usually within a couple minutes.
#include <standard.disclaimer>
alexx: Why do we need this?
My phone knows the time and never seems to need adjusting. Within a minute is close enough for me and the specification for NITZ (from etsi.org) states:
NOTE: Universal time indicates the time at which this information element (see 3GPP TS 24.008 [2]) may have
been sent by the network. Thus it can be assumed that the accuracy of the time information when it
arrives at the MS is usually within a couple minutes.
That doesn't seem like an improvement to me.
johnr: Grant it's not realted to " can't be bothered " as you put it, The feature was enabled for a short time frame a little while back but then had to be disabled due to a reason I can't say sorry
As advised above Vodafone NZ have paid for the feaure and would like it enabled
NITZ is the perfect solution, and my observations are that it is accurate to within a few seconds when running on 2D or Telecom. If it's good enough for them to offer this service to their customers around NZ, I don't see why Vodafone can't be bothered to implement it.
oxnsox:
I'd have thought any network would simply reference a GPS clock. Most accurate for price, and often co-located at sites it seems.
Hmmmm
|
![]() ![]() ![]() ![]() |