IssueTracker

Fixed in upcoming release. Thanks for the report!

it's a stupid bug!

Android is full of those bugs :(
It's a pity :(

stupid bug,thanks for your report

how about controlling the scrollbarTrackHorizontal's width?

ummm. not sure if im just stupid, but in 5.0.1 im having the same problem, only for ScrollView, Herizontal works great.. can't set the scrollbar size

Android 5.1.1 - scrollbarSize XML property still ignored.

[Comment deleted]

Yes, I also found this bug. Its very unexpected. There is no way to set or reset seconds!
Please fix!

All these issues which are being reported and watched by so many users and not only, all these issues which are not getting fixed...well...made me buy an iPhone. Really.

I own Android phones for some time and I find this way to report and not being listened, humiliating. Google and Apple got accused they are tracking us, almost at the same time. Apple fixed it, Google doesn't even react.

There is no reaction from Google regarding this stupid issue too.

I had enough. Thank you Google, you're doing such a great job. Keep it up.

I am selling several Android phones, customers welcome. Starting with LG Optimus One, upgradeable to 2.3 some day. You tell me the price.

There are some problems with seconds even in case when you use root priveleges to setup seconds. With root it is works, but you will have +-1 second drift after each sleep. Probably milliseconds value is not readed from RTC chip on resume from phone sleep.

[Comment deleted]

The ability to set time to the second is crucial for many industries, so surely this is either a defect or a missing (basic) function.

Thanks for this feedback.

This issue has been fixed in our current tree. The date/time of the system is usually retrieved from the telephony network. One should rely on such an external time reference if a reliable time is needed.

@gilles.debunne@android.com

1. Please tell us how this has been fixed. Some details welcome.

2. No. Operator network time is NOT reliable. Not within Europe at least. Please check these (please read them all, they are very useful):

- http://code.google.com/p/android/issues/detail?id=18681 
- http://code.google.com/p/android/issues/detail?id=6434
- http://code.google.com/p/android/issues/detail?id=4581

"The date/time of the system is usually retrieved from the telephony network. "

I have been using many different networks in many countries in Europe. *None* has provided correct time. Using the 'set time according to network' feature will only lead to a very false and dangerous sense of security in time keeping.
Transit systems (for example) here depart on the 00 second, it is hard to understand how the Android system can not provide for a more exact time keeping when most people are using their phones for this today. I can only imagine it is designed somewhere where exact time is of less imoprtance?

my network send wrong time, I dont need it. I need to set time manual. But I cant set or reset seconds. This is biggest problem of android system. And this is reason why I thinking about change my android phone to iPhone.

This is a very basic bug and it's still present on my phone (Android 2.3.4). It basically makes Android unusable for any astronomical applications. I also second the other users here on telephony operator network providing unreliable time, in my experience it is commonly off by MINUTES here in Brazil.

Come on. This is very basic feature. Why can't I set the second manually without rooting the phone?
I'm not asking for setting the millisecond but 0-59 seconds different could be a big deal.

This is just pathetic. I wondered why my clock is 15 seconds ahead, went into the time setting dialog, set the time to the next minute, waited for it, pressed "set" just to see that the seconds did not change at all.
My network operator (T-Mobile Germany) does not provide time syncing (NITZ/Network Identity and Time Zone) and I cant even sync the time via NTP because android seems not to have this feature and neither allows an app to change the time. Wow, stone age...

What I've found via network monitor: My LG P970 with Android 2.3.4 does contact an NTP server after powering up (one of the nist.gov servers, not exactly a good choice from Europe but...) and ONLY adjusts the clock if the time is off by a year or something big. An hour behind will not be corrected. And then it DOES set the seconds pretty accurately, or as good as it gets with a time-server from half around the planet. So the solution for me is now, set my clock back 1 year, restart the phone, and viola.

Very strange behavior I must say. I mean if there is code for NTP syncing in there, why not include it in the settings, let me choose the server, and correct also if the deviation is only a minute???

Forlix: very good catch! I've tried your workaround (setting the date a few years back and then rebooting the phone) with my T-Mobile MyTouch4G Slide (aka HTC Glacier) running Android 2.3.4 and it works perfectly: after the reboot, the phone's clock is right to a fraction of a second.

Come on, Google Android developers: how hard can it be to include an UI for this? A simple button under "Settings / Time and Date" to activate that functionality would be enough... Or does Google want us all to root our phones so we can have a minimally correct clock without this time-resetting-and-rebooting aggravation? By simply ignoring such a seemingly simple-to-fix bug that's been open for almost two years, you Android developers are simply providing ammunition for the folks that say that Android is badly designed and maintained and that Google simply doesn't care...

@Durval, Forlix, Does the NTP hack work only for those with a data connection. Or does it also work over WiFi?

My phone gets its time from my GSM network and that is very accurate; so I can't test this hack myself (neither do I need it). I am asking for the benefit of my application's users.

As someone said in the other issue, GSM networks can be very inaccurate time sources. I haven't used mobile data at all with my phone, only WiFi. Thats also how I was able to determine if the phone does any NTP stuff - by monitoring my local network.

@Harshad: just tested the "set date back a few years and reboot" hack with my T-Mobile Mytouch4G Slide running Android 2.3.4 and I'm glad to report that it works with *both* mobile data AND WiFi.

I have been trying to find a way to set the time accurately on my xperia arc s and no matter what I did, I was always 26 seconds fast or slow. Eventually I came to the following solution: I switched the phone off and removed the battery. I waited for approx 3 minutes and waited until the reading on my laptop (time is-exact time) reached   58 seconds. Then I inserted the battery. Now my clock is accurate to 0.5 seconds

Check the comments above you, theres a more accurate way to do this without removing the battery - chances are it works for your device too.

[Comment deleted]

[Comment deleted]

SOLUTION
1. Switch android smartphone off and remove battery.
2. Insert battery at  the time seconds read 00 exactly. (Read from another device such as a laptop on www.time.is). It seems that the clock starts the moment you insert the battery.
3. Set the date and time.
Check time again. (I used Clock Sync to do that).

I have done above on my smartphone and ended up with 0.5 seconds accuracy.

Any other method of doing this without removing the battery is welcome.

SOLUTION 2 (for lazy readers)
1. Set the date 1 year to the past
2. Switch the phone off and then on again

Time will be automatically synced - accurate to the second - upon reboot (Internet connection required).

I'm very happy to report that the Android 4.3 Jelly Bean update on my Nexus4 phone has finally managed to fix this long-standing issue: now, when you use "set time", the seconds are automatically and simultaneously zeroed out.

Setting the time on a phone not equipped with Jelly Bean remains the same: Set the date one year to the past and restart the phone. I found that the same happens if you set the phone to airplane mode and then back again.

is there a specific Android versions where this is for sure fixed? Or does it differ from device to device no matter what Android version ?

Install Terminal Emulator for Android.
Then run in terminal:
su
date -s "20160516.182000"