The clock is not updated during a call. [not relevant]

asked 2014-01-02 15:04:42 +0300

mato
531 ●4 ●5 ●7

updated 2018-03-26 16:59:19 +0300

jiit

2678 ●32 ●58 ●59

admin

The clock freezes to the value it has when a call is started. It should show current time instead of time when the call has started.

Also, initially (when you select a person from the list of recent calls) the clock actually displays the time of the previous call. The call time itself does not even belong to the caller.

###Example

Check the times against the last two calls you have made, call the 2nd most recent. Note that the time in the small clock is the one from the most recent call. Hang up, go back to the list. Now the most recent and 2nd most recent switched places (obviously), the time calls were made however stayed at the old positions.

I would like to add that this is still present in 1.0.8.19

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by Spam Hunter
close date 2018-03-27 12:27:59.285655

Comments

3

To add more details to this bug report, only the small clock in the upper right corner of the phone application is not being updated. The main clock is updated during a call (reproduced this with an incoming call).

Cmdr_Zod ( 2014-01-02 16:14:37 +0300 )edit

I just noticed this bug as well today.

Cristian ( 2014-01-02 20:52:46 +0300 )edit

I noticed this too, and checked the clock on the lock screen which was updated as Cmdr_Zod also notes, so I thought: Maybe this is meant to be this way...?

So You're able to see WHEN You RECEIVED the call...?

Not sure in any way, but I thought that maybe that was the idea...?

DrWilken ( 2014-01-08 18:59:31 +0300 )edit

2

If what DrWilken speculated was the idea, it certainly should rather have the current time also visible, because at least I don't want to calculate the current time from the call duration counter.

This behavior seems to be unchanged in 1.0.5.16.

AnonUser3396 ( 2014-04-22 18:20:38 +0300 )edit

I also have the small clock freezing at time call commences and call list displays the wrong times until it is refreshed when the correct times are then displayed.

richardski ( 2014-09-09 09:25:49 +0300 )edit

4

answered 2018-03-25 13:18:59 +0300

Spam Hunter

11677 ●187 ●289 ●324

This question is now 4 years old and got asked again recently, see here;

https://together.jolla.com/question/181933/bug-clock-stopped-working-when-in-call-application/ - to which @PlasmaMover has answered and is marked as correct/closed.

@too - the problem does not persist purely because it is not a problem, nor is it a bug, it is a feature, or at very least, is intentional.

The digits that are displayed at the top right of the in-call screen, is a timestamp, meaning it was that time when the call started/got connected. The very same timestamp is also shared by the 'call log'.

To look at the time while in a call, you need to peek, by sliding the current view slightly to one side, the real time can then be seen top centre, then let go of the swipe and you're back to the in-call screen - but again, the 'time' you think you are seeing is not the time, it is a timestamp.

edit flag offensive delete publish link

Comments

3

@Edz Thx for clarifying this. If its not a bug, it's at least bad UI design. When in a call, I couldn't think of a reason why I'd want to know at which time the call was connected. I might want to know how long it lasts, but that's clearly shown below. Also, I might want to know the current time ("When shall we meet? Wait, what time is it now, I'll check ..."). If I want to check the current time during a call, I'll take the first value that looks like it on my display... an unfortunately that's this "time-stamp". If there were no such time-stamp, I'd peek. But as I already think I know the current time... I wonder who came up with this idea. :)

ossi1967 ( 2018-03-25 13:48:42 +0300 )edit

I agree with @ossi1967, this bug report could be changed into a request for improvement. The time a call was started is useful, but so is the current time, and it's a bit strange to not display it.

nthn ( 2018-03-25 15:03:31 +0300 )edit

Just my thoughts in above comments, UX with this misleading time information is awful. If it just had current time nearby (and current elapsed time) one could understand the times seen on display. currently the few times I come across the time information during call it is first confusing, then irritating...

too ( 2018-03-25 20:24:40 +0300 )edit

@Edz: elapsed time seems to be missing. That's usually the most important information. Timestamp (when did the call start) isn't necessary and just adds confusion.

ossi1967 ( 2018-03-26 00:36:55 +0300 )edit

2

Best you get patching then @ossi1967

I didn't take a screenshot of it while the timer was showing, instead, you're seeing the result of me pushing numbers/characters to keep the call alive. But what you are saying is; remove the timestamp in the call view and replace it with the current time, yes?

image description

Spam Hunter ( 2018-03-26 00:48:52 +0300 )edit

1

answered 2018-03-26 02:24:14 +0300

olf
10393 ●104 ●201 ●158

Markkyboy resolved this by creating a Patch: Clock in call view.

edit flag offensive delete publish link

Comments

2

@olf let @markkyboy have the credit then. @Edz I do want to upvote you :)

lakutalo ( 2018-03-26 11:27:18 +0300 )edit

1

I wouldn't go as far to say it is resolved, rather, it has evolved and should continually evolve...I don't actually care for the boldness applied to this 'first patch', so changes are already happening - let me see how much detail I can cram into Call View - perhaps to add weather and calendar as well :D

Spam Hunter ( 2018-03-26 19:00:55 +0300 )edit

1

Cui honorem, honorem! ;) Add a language indicator for polyglots. :D

lakutalo ( 2018-03-27 00:11:04 +0300 )edit

@lakutalo,

@olf let @markkyboy have the credit then. [...]

That was my intention.
Note, that the nicknames "Markkyboy" and "markkyboy" do not exist on TJC (checked before posting the answer).

olf ( 2018-03-27 01:01:45 +0300 )edit

rofl ;)

lakutalo ( 2018-03-27 08:47:11 +0300 )edit

0

answered 2018-03-27 12:27:43 +0300

Spam Hunter

11677 ●187 ●289 ●324

I'm closing this question for several reasons mainly because the question is not relevant.

It is not relevant, because the digits in question are not representing the time, it is a timestamp showing the time the call takes from the point of connection to the end of call.

The question is also 4 years old and not ONE dev from Jolla has interjected to say either way, what is or what isn't.

edit flag offensive delete publish link

Comments

1

well, i personally think this issue is very relevant, the fact that the screen shows time.that is not current causes confusion what the.time.is and.causes problems. how does one express the relevance of this if things gets dismissed like this ?

too ( 2018-03-27 17:49:00 +0300 )edit

@too - If you think it is still relevant, then reopen the question. I don't care either way, it's not relevant in the scheme of things with SFOS, but that of course is my opinion.

You are in a minority. I see no confusion and seemingly most others don't either, but there will always be differences of opinions, so do what you like, we all run TJC. I certainly will pay no more attention to the subject as I see it as a waste of my time.

So in your eyes, it is a bad design - good luck with getting Jolla to change anything where this is concerned, it is very unlikely to happen. This is why we have a plethora of patches, to try and keep everyone happy.

Spam Hunter ( 2018-03-27 18:21:30 +0300 )edit

The clock is not updated during a call. [not relevant]

The question has been closed for the following reason "question is not relevant or outdated" by Spam Hunter
close date 2018-03-27 12:27:59.285655

Comments

3 Answers

Comments

Comments

Comments

Question tools

Stats

Related questions

The clock is not updated during a call. [not relevant]

The question has been closed for the following reason "question is not relevant or outdated" by Spam Hunter close date 2018-03-27 12:27:59.285655

Comments

3 Answers

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "question is not relevant or outdated" by Spam Hunter
close date 2018-03-27 12:27:59.285655