IFE: Time to destination

[albatross710]

Has anyone ever noticed the display of "Time to Destination" that is displayed in the hand controller of the IFE?

I've noticed on overnight flights that if I check it after I've been asleep it seems to be locked in the past. For instance, it might say Time to Destination 7 hours but after I actually turn on the screen again and check the Flight Map, it quickly updates to the same time.

It seems ot stay up to date when I'm awake and active with the IFE.

Is it just me, have I imagined this? I admit it is usually when I've just woken and asking myself "Are we there yet?"

Alby

 

[elbarto]

The system might go to sleep when it's not active.

 

[samh004]

The system might go to sleep when it's not active.

If it does, seems like a flaw as you'd expect the whole point of it being on the controller is so the IFE doesn't need to be on to check?

 

[albatross710]

If it does, seems like a flaw as you'd expect the whole point of it being on the controller is so the IFE doesn't need to be on to check?

Exactly, so first I just want to know if others have noticed.

 

[lovestotravel]

I noticed it, yes!

 

[albatross710]

I noticed it, yes!

I feel better now, i thought it was just my weird dream state.

 

[Danger UXB]

Yep me too. Hate that it freezes Sewell. Defeats the purpose grrrrr!!!!!

 

[Paddy55]

Off topic, but I wish they'd only start showing shows on the communal screens on communal screens that have a fair chance of finishing before landing

Coming back from ADL to SYD on Sunday and we got 3/4 through Grand Designs and I didn't get to see how they pulled the rabbit out of the hat! :shock:

 

[albatross710]

I'm wondering if it is worth logging the freeze/update issue to SQ.

I know I've noticed the problem over at least the last twelve months so I'm sure it must be in their system of improvements by now.

Will send some feedback via their website.

ALby

 

[lovestotravel]

I'm wondering if it is worth logging the freeze/update issue to SQ.

I know I've noticed the problem over at least the last twelve months so I'm sure it must be in their system of improvements by now.

Definitely worth it!

I first noticed the problem back in Feb 2011 though