Does changing the date actually force the update check?

[slack04]

Can anyone confirm that changing the date actually forces a check? Though the idea has been tossed around here like truth for a couple of days, I have seen only one post where someone said it works. Everyone else has said something along the lines of: I came home and it was up.

Everyone knows that if you set the clock forward, it says that the system was checked under system updates. Sorry, but that's not proof that it checks. That's proof that update check clock changes. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:

1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.

Can someone who's gotten the update explain what it looks like? When you turned it on, did it come up right after the animation? If you did the date trick, did you click "set" and it popped up immediately on screen? I am starting to think that the date change thing is only slowing this down; it just resets the clock for the update, it doesn't actually force the check.

Anyone have any other ideas? I am supposed to be studying for a final which is certainly why I'm obsessing about this, but I really can't help it. Anything to take my mind off studying for that horrible class. This final is going to kill me. (Then again, it's the last one I will EVER take!!!)

 

[Coldheat1906]

No it hasn't worked for me.

 

[slack04]

No it hasn't worked for me.

Thanks. It hasn't worked for many people. I'm curious if anyone knows if it CAN work, or if it's just a myth.

 

[Brenardo]

the update will appear as a notification on the lower right hand of your Xoom kin a like a notification like you are downloading something from the market.

 

[laredo7mm]

Can anyone confirm that changing the date actually forces a check? ...

On my Wifi only Xoom it forces a check.

For example;

1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm

So it did force a check.

Whether or not an update is available for your Xoom is a different story.

The date change will force a check but not force the actual update.

 

[slack04]

On my Wifi only Xoom it forces a check.

For example;

1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm

So it did force a check.

Whether or not an update is available for your Xoom is a different story.

The date change will force a check but not force the actual update.

Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:
1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.

 

[vizir]

you can force an update check using these steps:
1. hold power+volup, the xoom will reboot
2. after reboot go to system settings and check for updates

 

[ruinah]

doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.

 

[nubsors]

doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.

Yesterday I re-imaged my xoom to stock but realized too late that I was using 3.0 instead of 3.0.1. I went in and changed the date and set it back to automatic. My Xoom immediately started downloading the 3.0.1 patch. That is about as much proof as I can provide.

 

[El Daddy]

Yes it does force a check

This is what shows up in the logcat after changing the date:

D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
D/Beautiful Widgets( 846): Received Weather refresh Intent
E/Beautiful Widgets( 846): Acquiring new WakeLock on an existing notheld instance
D/Beautiful Widgets( 846): Service for Weather started
V/Beautiful Widgets( 846): Service AccuWeather onStart()
D/Beautiful Widgets( 846): Service AccuWeather Thread started
I/Beautiful Widgets( 846): Provider is network
I/Beautiful Widgets( 846): Requesting location update
I/EventLogService( 247): Aggregate from 1307904746624 (log), 1307904746506 (data)
E/TelephonyManager( 247): Hidden constructor called more than once per process!
E/TelephonyManager( 247): Original: com.google.android.location, new: com.google.android.gsf
I/CheckinService( 247): Preparing to send checkin request
I/EventLogService( 247): Accumulating logs since 1307904965403
D/dalvikvm( 846): GC_CONCURRENT freed 867K, 13% free 8280K/9479K, paused 3ms+4ms
I/CheckinTask( 247): Sending checkin request (1486 bytes)
D/dalvikvm( 846): GC_CONCURRENT freed 561K, 12% free 8406K/9479K, paused 3ms+3ms
V/AlarmClock( 8642): AlarmInitReceiver finished
D/dalvikvm( 133): GC_CONCURRENT freed 3891K, 29% free 21271K/29639K, paused 4ms+10ms
D/CalendarWidget( 8547): Scheduled next update at [1307941200000] 00:00:00 (+603 mins)
D/dalvikvm( 846): GC_CONCURRENT freed 963K, 14% free 8177K/9479K, paused 5ms+7ms
D/dalvikvm( 846): GC_CONCURRENT freed 494K, 12% free 8348K/9479K, paused 4ms+3ms
D/dalvikvm( 227): GC_FOR_ALLOC freed 1629K, 3% free 124319K/127879K, paused 77ms
D/dalvikvm( 227): GC_CONCURRENT freed 519K, 3% free 124143K/127879K, paused 2ms+13ms
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }

As you can see I still haven't gotten 3.1

 

[laredo7mm]

This is what shows up in the logcat after changing the date:

D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
...
...
...
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }

Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post...

Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.

 

[slack04]

Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.

Excuse me? Yeah, I edited the post to make my question more clear.

Your post was not useful; in fact it showed that you hadn't really thought through the process before you posted. I wasn't rude to you, I just pointed out the error in your logic, which made me realize that I should go back and clarify my question. Who's the "d-bag" here?

 

[El Daddy]

Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.

Wtf?

Sent from my Xoom using XDA Premium App

 

[slack04]

Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.

Wtf?

Sent from my Xoom using XDA Premium App

Thanks dude, you answered the question. He was actually talking to me; I couldn't tell you what his problem is, though. In any case, you've answered the question, so I'm going to go back to clock-changing-update-checking right now! Thank you!

 

[RadDudeTommy]

well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.

For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.

Like the date on your xoom is only for creating time stamps on the xoom.

 

[MRCANNADY]

I explained how this works in my post below:

http://forum.xda-developers.com/showthread.php?t=1076295

 

[slack04]

well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.

For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.

Like the date on your xoom is only for creating time stamps on the xoom.

It's moot at this point, but it was when you wrote your post also. What I was suggesting was that, if it wasn't actually checking by changing the date, then we could be stopping the actual update check from happening by trying, therefore setting us back by 12 hours (about the frequency of the automatic checks) every time we tried to "cheat." Of course, now that it's shown that the check does actually query the server (and that makes very little difference to when you actually get your update) my original guess (not statement) is obviously incorrect.

 

[kyoteqwik]

Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.

+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.


Sent from my ADR6300 using XDA App

 

[rjoudrey]

well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.

For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.

Like the date on your xoom is only for creating time stamps on the xoom.

Suppose our entire solar system was contained in a drop of water abiut to get wiped by a windshield wiper?

 

[slack04]

+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.


Sent from my ADR6300 using XDA App

That's friendly.