We confirmed with the device manufacturer that the devices use NTP to sync the time with pool.ntp.org. After a bit of research of my own, I discovered that NTP is configured in /system/etc/gps.conf. You have to be root to edit this file, but I was at least able to confirm that the information given to us was correct.
We have opened the firewall to traffic ...
It should be under your system settings (the Settings "app"), in the "Date & Time" subsection (which is near the bottom). Uncheck the "Automatic time zone" option and then select the correct one manually:
And of course right after I finished writing this question, I figured out the answer. Go to Settings, Lock Screen and Security, Info and App Shortcuts, Dual Clock, and that has a "set home timezone" option. It would've made more sense to put it somewhere in the "Time and Date" Settings section, but oh well.
dotVezz has already commented that NTP is used.
If so, then you can use ClockSync, which lets you set the NTP server. HOWEVER, you need to sync manually. Automatic sync is supported only with ROOTED devices.
ClockSync synchronizes device system clock with atomic time from
Internet via NTP (Network Time Protocol). Useful if provider doesn't
Android has no option for NTP syncing – time synchronization takes place by other means (via your mobile carrier, see Where time information is received from the network? and What is the synchronization source for the internal clock). To enable time synchronization via NTP, you can e.g. use ClockSync – but without root powers, 3rd party tools are pretty much ...
Install WidgetLocker Lockscreen. It allows to add homescreen widgets on lockscreen.
HTC widgets can't be added to WidgetLocker, but third-party general widgets can be. So, install Beautiful Widgets app, first. It has exact HTC flip-clock alternative.
When I go to my Date & time settings, there is option that says: Automatic - Use network-provided values.
So, basing on this wording (also in other languages), I would say that automatic time is provided from your carrier.
There are apps, that can sync your clock with GPS satellites or NTP servers.
It's not possible to create a widget that updates that often, because it will suck your battery really quickly. There are many stopwatch apps available in the Play Store. Many of them have millisecond or decisecond accuracy, but I'm not aware of any that have an associated widget.
These kind of high precision timers should only be needed on a case-to-case ...
Android 6.0.1 apparently fixes the issue. I'm running it on my Nexus, so I can't say about custom ROMs, but it should be fixed in 6.0.1 based ROMs.
The bug was detected by me in 6.0 first because my alarm rang 21 minutes late. It was about a week after I bought the phone. A reboot fixed the time, and since I've upgraded to 6.0.1, I haven't seen an issue ...
You will need to research how to set this on Galaxy Nexus and Jelly Bean, but ..
You are currently using "GMT -03:00, Brasilia Time", and this does not include Daylight Savings by default.
You need to instead use (one of):
These all use UTC -2:00 for DST.
Wikipedia: Time in Brazil
I had a similar problem but on another device, though try if it can fix your problem this is the what I did:
I opened the Terminal Emulator and typed:
Then I held 'Volume down' (a.k.a. Ctrl) and 'c' to stop the output. I scrolled a bit up in the output and found a line that said:
E/SQLiteOpenHelper( 5231): Couldn't open alarms.db for ...
Looks like it's just/about to be fixed in Clock 4.0.1 as reported on AndroidPolice.
The new APK for the clock app from the Android M Developer Preview doesn't look very different from the one you'll find in Lollipop - most of the functions (alarms, world clock, timer, and countdown) are in the same place and operate in the same way. But there's one tiny ...
They use a Real-time clock, the same as just about any other electronic device that keeps time. Newer devices have largely begun to move to supercapacitors to power the RTC, but batteries are also used. The decision depends on a variety of factors, including space and relative cost of the components.
If you want some really in-depth details on how an RTC ...
This is a problem encountered by many that has upgraded into Android Pie or bought a new one with Android Pie. Luckily, this could be fixed but rooting the phone is necessary. Someone I know tried this and it worked. May this also help you,
Some launchers (Nova, Launcherpro) can create shortcut on home screen which can launch custom activity from any app. This may allow you to launch alarm settings directly.
Also you can create custom app to launch activity from another app.
I use Ovo timer: a minimalist app to set your timer by dragging an arc on your screen. Also, you can set time by voice (it needs Internet connection for this). It runs on Android 2.1 and up. The only con I've found is that it only supports times not greater than 1 hour.
About what you're asking for:
Just display the time (for example 14:28). Check.
It sounds like your clock is 4 minutes fast. Check to see if your phone is getting its time from the network (on Gingerbread, it's Settings/Date & Time, not sure about CM 7.2).
If you are getting time from the network, try disabling automatic updates and set the time manually to a source like time.gov or time.is.
You can DNS override the pool.ntp.org entry in your corporate DNS infrastructure, and make that an alias/CNAME to your own internal NTP source/service. That will allow the internally connected android devices to sync with NTP without modification of the device itself
Try disabling network time and set the clock manually. Network time relies on your mobile operator setting their clocks correctly, while it is usually a good bet, some misconfiguration on their side could mean that their clock is returning incorrect time. Another possibility is an issue in the database of time offsets in the device (this controls corrections ...
Until Android 4.2 there is no stock Countdown timer, with Android 4.2 there will be one.
Some alternative Interfaces like Touchwiz (Samsung Devices) have added a Countdown Timer for a long time, but stock Android (AOSP) had this first in 4.2.
I've got the same problem and the annoying sound can not be found in /System/media/audio/, but in /system/app/DeskClock.apk/assets/sounds/Timer_Expire.ogg. In any case, it seems difficult or impossible to change.
There is more info here: