Ask / Submit

[BUG] Clock stopped working when in call application [duplicate]

asked 2018-03-22 16:50:36 +0300

Mottel gravatar image

updated 2018-03-22 16:51:27 +0300

Yesterday I recognized a Bug while I was calling a friend.

Started to call him @ 18:24

I have had a meeting @ 18:30

Checked my Phone Clock @ the top right corner in the call application...

the clock was still @18:24 even when it was 18:30 already.

I am able to reproduce this bug.

edit retag flag offensive reopen delete

The question has been closed for the following reason "duplicate question" by nthn
close date 2018-03-24 18:16:01.006586

3 Answers

Sort by » oldest newest most voted

answered 2018-03-24 12:53:40 +0300

updated 2018-03-24 12:54:25 +0300

It's not a bug, it's by design. Upon looking in the file responsible for displaying this 'time'. I can see it is a timestamp, that being the time the call got connected. If you wish to see this for yourself, head to this file destination and look at the code;

at line 91, (Formatter.TimepointRelativeCurrentDay)


This file is also responsible for displaying the relevant time in the call log as well as in the call dialog.

Also, for those interested, for different 'Formatter' types, have a look here;

Starts at line 258


DeclarativeFormatter Types

    Component {
    name: "DeclarativeFormatter"
    prototype: "QObject"
    exports: [
        "Sailfish.Silica/Format 1.0",
        "Sailfish.Silica/Formatter 1.0"
    isCreatable: false
    isSingleton: true
    exportMetaObjectRevisions: [0, 0]
    Enum {
        name: "FormatType"
        values: {
            "Timepoint": 0,
            "TimepointRelative": 1,
            "TimepointRelativeCurrentDay": 2,
            "TimepointRelativeCurrentDayDetailed": 3,
            "TimepointSectionRelative": 4,
            "TimepointSectionHistorical": 5,
            "WeekdayNameStandalone": 6,
            "DurationElapsed": 7,
            "DurationElapsedShort": 8,
            "TimeValueTwelveHours": 9,
            "TimeValueTwentyFourHours": 10,
            "TimeValue": 11,
            "DurationShort": 12,
            "DurationLong": 13,
            "DateFull": 14,
            "DateLong": 15,
            "MonthNameStandalone": 16,
            "MonthNameStandaloneShort": 17,
            "DateMedium": 18,
            "DateMediumWithoutYear": 19
edit flag offensive delete publish link more


Of course there is a reason in the code for this behaviour. This is no proof that this is the intentionally designed behaviour and not a bug. To proof that this is a "feature" it should be documented somewhere in a user manual. Otherwise, I see this as a rather confusing behaviour and would call it a bug.

Stefanix ( 2018-03-30 05:09:55 +0300 )edit

I would put money on it being a timestamp and not a clock, but you are entitled to call 'bug', but stating it's not proof based on it not being documented is a weak argument. However, I never cited my answer as proof and having nothing to prove to you. Do your own research, edit the said file and learn for yourself, but hey, most people are lazy and prefer to sit in their armchairs and shout 'bug' when it suits. If you think it is a frozen clock, then edit the said file and change "Formatter.TimePointRelativeCurrentDay" for any one of the other options laid out above and then show me your call log, which with the right option will show a live clock, no?, I know you cannot, because I've already tried every Formatter option there is and not one of the tests revealed a working clock - how would the timestamps in call log have different times if it were a real clock?, don't forget, call log and the calling view share the same file for this 'timestamp/clock' to appear in the first place! You are of course, entitled to your own opinion, but that is all it is. I just see another confused punter calling bug because he doesn't understand what it is he is looking, documented indeed!, Jolla don't exactly keep up with documentation in case you haven't noticed in the 5 years you've been with this community.

PlasmaMover ( 2018-04-02 14:49:27 +0300 )edit

Technical research is needed to find the root cause and possibly to apply a correction, but not to judge if the behaviour is by design or a bug. What counts is the effect to the user. Not sure why you obviously feel insulted by my comment. Probably you expected some praise for your effort, which you certainly put on this case, and your contribution is certainly valuable to the community. But user reactions show that the current behaviour is confusing and lead to 2 questions here. Looks like bug, which I am certain will disappear with SFOS 3.

Stefanix ( 2018-04-02 16:29:14 +0300 )edit

answered 2018-03-22 22:04:08 +0300

Bart S gravatar image

I just tested making a call. Started the call at 21:00 and indeed the time in the call screen stays at 21:00

I am not sure if this time is meant as a clock, or as a time that you started the call. In the first case it must be a bug that it is not updating during the call. In the latter case, I think it is showing correct.

Intex Aqua Fish - SailfishOS

edit flag offensive delete publish link more



Thats right. It can be a feature.

But the time I called somebody is for me a useless information when my phone is not showing me the actual time on the display. Indeed I can swipe out of the phone App and check the right clock time.

It make only sense for me when I am wearing a physical clock to compare the time I called somebody and the actual time.

I would prefer a working clock in my phone App and a additional phone-time-counter that starts at 00:00

Mottel ( 2018-03-22 22:24:09 +0300 )edit

I agree with your last sentence. The phone time counter is there already, so the quesion is ... is it a but or is it a feature ?

Bart S ( 2018-03-22 23:31:30 +0300 )edit

Its a feature to train the users menthal calculation.

Mottel ( 2018-03-23 01:16:18 +0300 )edit

answered 2018-03-24 14:20:29 +0300

Cmdr_Zod gravatar image

This is a duplicate of

edit flag offensive delete publish link more



Hence see there for a resolution for this.

olf ( 2018-03-26 02:26:47 +0300 )edit

Question tools

1 follower


Asked: 2018-03-22 16:50:36 +0300

Seen: 269 times

Last updated: Mar 24 '18