Jump to content
Sign in to follow this  
ToniCipriani

What is this clock? (EDIT: Solved.. I think?)

Recommended Posts

Posted (edited)

I can't figure out what this is. The time shown is also random. It's not my alarm, since I don't have one set right now, and that appears on the top left of the status bar with no time displayed if it is set.

When it collapses, the stopwatch appears next to the Wi-Fi and Battery Status.

iMarkup_20200610_174202.jpg

Edited by ToniCipriani

Share this post


Link to post
Share on other sites
42 minutes ago, ToniCipriani said:

I can't figure out what this is. The time shown is also random. It's not my alarm, since I don't have one set right now, and that appears on the top left of the status bar with no time displayed if it is set.

When it collapses, the stopwatch appears next to the Wi-Fi and Battery Status.

iMarkup_20200610_174202.jpg

That's an alarm (and so is the icon in the status bar when you collapse it.  Something has an an alarm set for 6:01 pm-- you can check alarm.  It might not produce an actual alarm, depending on what's doing it.  I used to use a calendar app called Pimlical and I would see an alarm for 2:00am jin that position (if there wasn't an actual alarm scheduled sooner) just because that was when the calendar app performed a daily housekeeping.

 

Something on your phone thinks it has an alarm scheduled.

 

  • Thanks 1

Share this post


Link to post
Share on other sites

Yeah that seems accurate. The time on the "alarm"  now changed to 7:45PM tomorrow, so I tried setting an alarm at 5:30AM tomorrow, and indeed it updated.

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

OK after a little digging in ADB, think I found the "culprit":

Batch{22232bc num=1 start=111828095 end=111828095 flgs=0x3}:
    RTC_WAKEUP #0: Alarm{5f09730 type 0 when 1591875900000 net.dinglisch.android.taskerm}
      tag=*walarm*:net.dinglisch.android.tasker.ALARUM
      type=0 expectedWhenElapsed=+12h33m31s60ms expectedMaxWhenElapsed=+12h33m31s60ms whenElapsed=+12h33m31s205ms maxWhenElapsed=+12h33m31s205ms when=2020-06-11 07:45:00.000
      window=0 repeatInterval=0 count=0 flags=0x3
      Alarm clock:
        triggerTime=2020-06-11 07:45:00.000
        showIntent=PendingIntent{4a12fa9: PendingIntentRecord{adcf92e net.dinglisch.android.taskerm broadcastIntent}}
      operation=PendingIntent{b964ccf: PendingIntentRecord{adcf92e net.dinglisch.android.taskerm broadcastIntent}}

Looks like it's Tasker causing it. owever, I now found something else that's interesting: in the lock screen, there is another alarm showing there, which seemingly is also caused by Tasker:

Batch{b0baea1 num=1 start=67373573 end=67373573 flgs=0x3}:
    RTC_WAKEUP #0: Alarm{4b498c6 type 0 when 1591831445478 net.dinglisch.android.taskerm}
      tag=*walarm*:net.dinglisch.android.tasker.ANOFFCHECKORUM
      type=0 expectedWhenElapsed=+9m53s992ms expectedMaxWhenElapsed=+9m53s992ms whenElapsed=+9m53s992ms maxWhenElapsed=+9m53s992ms when=2020-06-10 19:24:05.478
      window=0 repeatInterval=0 count=0 flags=0x3
      Alarm clock:
        triggerTime=2020-06-10 19:24:05.478
        showIntent=PendingIntent{6959087: PendingIntentRecord{f21dbb4 net.dinglisch.android.taskerm broadcastIntent}}
      operation=PendingIntent{39393dd: PendingIntentRecord{f21dbb4 net.dinglisch.android.taskerm broadcastIntent}}

I wonder why the discrepancy here, the two seemingly similar functionality is picking up different ones. Possible bug with the lock screen?

Found some more about this as well: https://groups.google.com/forum/#!searchin/tasker/alarm$20clock|sort:date/tasker/vaC9Ubq88zQ/xXJX500yAwAJ

Edited by ToniCipriani

Share this post


Link to post
Share on other sites
7 hours ago, ToniCipriani said:

I wonder why the discrepancy here, the two seemingly similar functionality is picking up different ones. Possible bug with the lock screen?

In your second dump i see ... ANOFFCHECKORUM (and in the first ALARUM) So my guess would be that the second is only active when the device is sleeping / the screen off, that is to wake the device to do something??
See also e.g. this https://groups.google.com/forum/#!topic/tasker/sms3Kt2inzY

So these really are questions belonging in the Tasker forum not the Pro1 ;)

 

Share this post


Link to post
Share on other sites
12 hours ago, EskeRahn said:

In your second dump i see ... ANOFFCHECKORUM (and in the first ALARUM) So my guess would be that the second is only active when the device is sleeping / the screen off, that is to wake the device to do something??
See also e.g. this https://groups.google.com/forum/#!topic/tasker/sms3Kt2inzY

So these really are questions belonging in the Tasker forum not the Pro1 ;)

 

Actually I was referring to the fact that the lock screen alarm and the pulldown alarm has discrepancies.

Share this post


Link to post
Share on other sites

Hehe, I love Tasker but sometimes it ends up being a, "Magician's Apprentice" with code experience more than I'd like to admit. 

Share this post


Link to post
Share on other sites

That's what I love about Lineage vs Stock... most of the workarounds are no longer needed and instead integrated into the OS.  😉

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

Terms