tmassie / aospx

Automatically exported from code.google.com/p/aospx
0 stars 0 forks source link

Time gets stuck in status bar #36

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
I'm not sure how to reproduce this since it seems to happen randomly.  
Sometimes it happens multiple times a day, and some days I don't think it 
happens at all. I haven't been able to track down a sure-fire cause for it yet.

What is the expected output? What do you see instead?
Sometimes the time display in the status bar will get stuck and will lag behind 
actual system time. The live wallpaper I'm using displays the correct time, so 
the system doesn't have an internal time keeping issue, but the status bar for 
some reason will lag behind several hours now and again. 

What version of the product are you using?
AR26

Please provide logcat ouput and any additional information below.
(required)

Here's logcat output when I go into system settings > Date and time and uncheck 
and recheck "Automatic date & time." This seems to be the only reliable way of 
updating the status bar time display when it gets stuck.

I/GsmServiceStateTracker( 1708): Auto time state changed
D/dalvikvm( 2990): GC_CONCURRENT freed 873K, 13% free 9918K/11299K, paused 
4ms+7ms
I/GsmServiceStateTracker( 1708): Auto time state changed
D/SystemClock( 1708): Setting time of day to sec=1332801152
I/ActivityManager( 1378): Start proc com.google.android.calendar for broadcast 
com.google.android.calendar/com.android.calendar.widget.CalendarAppWidgetService
$CalendarFactory: pid=3248 uid=10005 gids={3003}
D/dalvikvm( 1234): GC_EXPLICIT freed 38K, 14% free 9024K/10399K, paused 2ms+2ms
D/dalvikvm( 1234): GC_EXPLICIT freed <1K, 14% free 9024K/10399K, paused 2ms+2ms
D/dalvikvm( 1234): GC_EXPLICIT freed <1K, 14% free 9024K/10399K, paused 3ms+2ms
I/ActivityThread( 3248): Pub 
com.google.android.calendar.CalendarRecentSuggestionsProvider: 
com.android.calendar.CalendarRecentSuggestionsProvider
I/ActivityManager( 1378): Start proc com.android.deskclock for broadcast 
com.android.deskclock/.AlarmInitReceiver: pid=3264 uid=10012 gids={}
I/ActivityManager( 1378): No longer want com.google.android.apps.uploader (pid 
2775): hidden #16
I/ActivityManager( 1378): Start proc com.android.providers.calendar for content 
provider com.android.providers.calendar/.CalendarProvider2: pid=3276 uid=10006 
gids={3003, 1015}
I/ActivityManager( 1378): No longer want com.facebook.katana (pid 2407): hidden 
#16
I/ActivityThread( 3276): Pub com.android.calendar: 
com.android.providers.calendar.CalendarProvider2
I/ActivityThread( 3264): Pub com.android.deskclock: 
com.android.deskclock.AlarmProvider
V/AlarmClock( 3264): AlarmInitReceiver finished
I/ActivityManager( 1378): No longer want com.fab (pid 2794): hidden #16
D/dalvikvm( 1378): GC_EXPLICIT freed 3742K, 25% free 19556K/25827K, paused 
3ms+12ms
I/CalendarProvider2( 3276): Sending notification intent: Intent { 
act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar }
W/ContentResolver( 3276): Failed to get type for: 
content://com.android.calendar (Unknown URL content://com.android.calendar)

Original issue reported on code.google.com by samuelgr...@gmail.com on 26 Mar 2012 at 10:49

GoogleCodeExporter commented 8 years ago
We had this issue awhile back (like with AR16), but a clean wipe and reinstall 
fixed the issue. I had tried reproducing it myself back then and never could, 
and have yet to still have this problem. But clearly it is an issue. I will 
look into this some more and see if there is any way to reproduce it, but also 
I suggest just trying a clean wipe data/factory reset for good measure, while 
only installing the apps you need/use and see if you can maybe track it down to 
a certain app thats conflicting with things. 

Not sure if it helps with anything or not, but heres the link to the old ticket 
on this issue.. Issue #9

http://code.google.com/p/aospx/issues/detail?id=9

Can you give me a list of the apps your currently have installed? That way i 
can atleast try to get things setup as close to yours as possible while trying 
to reproduce this.

Original comment by robbe...@gmail.com on 26 Mar 2012 at 11:11

GoogleCodeExporter commented 8 years ago
I take that back, I actually had this happen for the first time last night 
lol.. But like you said, its random and not quite sure what triggered it. But 
now that its atleast happened to me, I can try keeping a close eye on it and 
see if I notice what triggers it.

Original comment by robbe...@gmail.com on 27 Mar 2012 at 11:57

GoogleCodeExporter commented 8 years ago
Haha, glad I'm not the only one. :)

Apps I have installed:

Amazon
Amazon Appstore
Chrome Beta
SwiftKey X
Reddit is Fun lite
Twitter
Facebook
Weatherbug
Widgetsoid
Wikipedia
WP Clock
Evernote
Fab
Facebook Messenger
Pandora
Picplz
SoundHound
Wolfram Alpha
doubleTwist

Original comment by samuelgr...@gmail.com on 27 Mar 2012 at 10:41

GoogleCodeExporter commented 8 years ago
Theres a possible fix for this.. Will try it out and hopefully get this fixed 
once and for all. But since this issue is something random, and no real way to 
trigger it, it might be a little while to verify if it worked or not.

http://review.cyanogenmod.com/#/c/18410/

Original comment by robbe...@gmail.com on 9 Jul 2012 at 1:59

GoogleCodeExporter commented 8 years ago
In-Progress -> Fix Committed

Changes have been pushed to ics-devel on github. So far the status bar has been 
reporting the correct time, but only time will tell if its fully fixed. (no pun 
intended lol)

https://github.com/aospX/platform_frameworks_base/commit/80d76a43407c7716534eee9
cc6b4058955875247

Original comment by robbe...@gmail.com on 10 Jul 2012 at 6:42

GoogleCodeExporter commented 8 years ago
Issue seems to be resolved in BR4.. If this pops back up then I will re-open 
this ticket. But since adding the fix above I have not experienced this issue. 

Original comment by robbe...@gmail.com on 13 Jul 2012 at 9:16

GoogleCodeExporter commented 8 years ago
Hi,

I am experiencing this issue right now.
It is exactly the same problem as stated on the bug description here and I'm on 
BR4.
Unfortunately I currently have no access to my computer so I can't provide a 
log file but I can tell you that this bug seems not to be solved yet.
It also happened on other DHD ICS roms for me, for example in iceColdSandwich 
8.4.

Original comment by steckl...@gmail.com on 1 Aug 2012 at 12:34

GoogleCodeExporter commented 8 years ago
By the way turning your phone into landscape mode from portrait mode or vice 
versa will update the clock in the status bar for one time but it will 
immediately get stuck again.
You have to update the time in the Settings app as stated in post 1.

Original comment by steckl...@gmail.com on 1 Aug 2012 at 12:39

GoogleCodeExporter commented 8 years ago
this issue occurred again on BR5 today

Original comment by AlvaHu...@gmail.com on 13 Aug 2012 at 3:49

GoogleCodeExporter commented 8 years ago
I thought something is wiered with my time...status bar clock was behind while 
my widget clock was telling the correct time.Same problem here..i am on br5 as 
well..
it happened 2nd time today.had to adjust the time manually...

Original comment by saeedyas...@gmail.com on 13 Aug 2012 at 10:20

GoogleCodeExporter commented 8 years ago
Marking as pending for now

And everyone has done a complete full wipe , without restoring any data with 
BR4/BR5?  I have not had this issue since the above fix was added.. but I 
always full wipe

Original comment by robbe...@gmail.com on 13 Aug 2012 at 2:42

GoogleCodeExporter commented 8 years ago
Yes I did a full wipe and didn't restore any data on BR4.

Original comment by steckl...@gmail.com on 13 Aug 2012 at 2:46

GoogleCodeExporter commented 8 years ago
Anyone else able to verify after full wipe? That way I can mark this 'Verified'.

Original comment by robbe...@gmail.com on 16 Aug 2012 at 8:42

GoogleCodeExporter commented 8 years ago
It happened one time since BR5 flashed with full wipe, no before data restored.

Original comment by AlvaHu...@gmail.com on 17 Aug 2012 at 5:04

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have flashed the BR6 today, unfortunately it happened again at this night. 
And the lock screen time may be also stopped until the phone unlocked. It seems 
the lock screen time going slower than system time when I relock the phone 
everytime at this moment.
I restored datas with Titanium.

Original comment by AlvaHu...@gmail.com on 17 Aug 2012 at 6:46

GoogleCodeExporter commented 8 years ago
Well, I installed lumberjack now, so I could take a look at the logs in case 
this happens and provide you a logcat of the bug as it happened.

But now it just won't happen again...

Maybe everyone having this problem here should install lumberjack. When the 
clock gets stuck export the logcat and copy the relevant part and post it here.

This could help, couldn't it?

Original comment by steckl...@gmail.com on 17 Aug 2012 at 6:47

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago

Original comment by robbe...@gmail.com on 17 Aug 2012 at 9:09

GoogleCodeExporter commented 8 years ago
i am on B6 and did full wipe..still notification bar clock got stuck.
Screenshot attached here...

Original comment by saeedyas...@gmail.com on 18 Aug 2012 at 7:00

Attachments:

GoogleCodeExporter commented 8 years ago
installed Lumberjack for a logcat..
Will update as soon as clock gets stuck again

Original comment by saeedyas...@gmail.com on 18 Aug 2012 at 7:05

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
When i woke up today early,i saw my status bar clock stuck at 1:07am.
Ive attached the logcat.
That relevant portion in which the clock got stuck ie 1:1:30 till 1:10:28.
Clock details are missing in that portion.thats strange.

@Rob->Did full wipe and did not restore any data just to get a log for this 
issue.

Original comment by saeedyas...@gmail.com on 20 Aug 2012 at 7:26

Attachments:

GoogleCodeExporter commented 8 years ago
So here finally comes a logcat from me. Clock gets stuck at 15:48
Please note that I didn't manage to keep up with the updates and that I'm still 
at Br4 but I think that shouldn't matter.

Original comment by steckl...@gmail.com on 21 Aug 2012 at 2:36

Attachments:

GoogleCodeExporter commented 8 years ago
Here's another log from BR4:
As I already stated the clock updates for one time (but after that still stays 
stuck), when you turn the phone (for example from portrait in landscape mode).
In this example I turned it from Portrait mode into landscape mode and then 
again.into Portrait mode while the clock was stuck. It then updated and stayed 
stuck after that.

Original comment by steckl...@gmail.com on 21 Aug 2012 at 2:49

Attachments:

GoogleCodeExporter commented 8 years ago
So it looks like this is happening on stock Galaxy Nexus as well, or at least 
this sounds very similar to whats going on here..

http://code.google.com/p/android/issues/detail?id=36562

Original comment by robbe...@gmail.com on 22 Aug 2012 at 6:39

GoogleCodeExporter commented 8 years ago

Original comment by robbe...@gmail.com on 4 Oct 2012 at 6:55

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have the same problem, at the beginning happened less but now it happens 
every day! The clock, the network and the wifi are frozen in the status 
bar!Somebody knows how to solve it? Thanks

Original comment by jpgsalc...@gmail.com on 18 Mar 2013 at 10:07

Attachments:

GoogleCodeExporter commented 8 years ago
I had the same problem, starting 2days ago. When I looked at that app list the 
only thing I had in common that was installed recently was Shazam which is like 
SoundHound.  Also it was installed about 2 days ago. So I uninstalled and 
rebooted and so far so good.  Wonder if anyone else has found similar 
experiences with these types of apps.

Original comment by lishalin...@gmail.com on 17 Mar 2014 at 9:50

GoogleCodeExporter commented 8 years ago
Same problem here. CM11 M7 on a Samsung S4 Mini.

Original comment by hthdjeut...@googlemail.com on 13 Jul 2014 at 9:01

Attachments:

GoogleCodeExporter commented 8 years ago
Same for me: CM11 S4 Mini

Setting it to landscape mode and back refreshes it, and it gets stuck again as 
per #27

I've noticed this after installing Amazon AppStore and Dualingo, but it might 
be possible that it has been happening since I upgraded to 
'11-20140708-SNAPSHOT-M8-serranoltexx'. I was on the previous snapshot before 
the upgrade.

I tried removing Amazon AppStore and Dualingo + rebooting, but it did not help.

Model number: GT-I9195
CyanogenMod version: 11-20140708-SNAPSHOT-M8-serranoltexx
Android Version: 4.4.4
Kernel version: 3.4.0-cyanogenmod-gf108aba

Original comment by milos.ka...@gmail.com on 28 Jul 2014 at 5:25

GoogleCodeExporter commented 8 years ago
Well. I seem to have fixed it (it has been a couple of hours that it's 
working). This is what I did. Not sure which one of these steps fixed it:

Disable network time
reboot
Date was set to 1970. Set to appropriate date manually
reboot
Date was set to Jan. 2013 (it's July 2014 at the time of writing this).
Turn on network time
reboot
Working.

Original comment by milos.ka...@gmail.com on 28 Jul 2014 at 10:07

GoogleCodeExporter commented 8 years ago
"+1 me too!"

fixed after two reboots.

also affects countdown (it will just count negative but not make any sounds or 
anything).

S4 mini GT-I9195.

Original comment by a...@tulcod.com on 15 Oct 2014 at 11:11