[Bug] Next Alarm complication about smartspacer HOT 12 CLOSED

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work? (Sorry for my late reply, I fell asleep after my last comment)

It shows whatever the system reports. If there's an alarm that isn't showing, there's nothing I can do.

Ah I see, is this issue present on your side? Or is it just a device specific issue? And if it is device specific, is there anything I can do on my side to possibly fix this?

It seems to be device specific.

Hey, after a few reboots it suddenly works but I don't know why it shows the alarm an hour too early? Any idea why?

Again, the time is provided by the system. If it's wrong, there is nothing I can do.

It's pretty clear this API is extremely unreliable on your device and the OEM has pretty much broken it entirely. There is unfortunately no alternative, so I cannot fix it.

from smartspacer.

Are you using Tasker at all?

from smartspacer.

Are you using Tasker at all?

Nope, never used it

from smartspacer.

Usually this is caused by another app abusing the alarm feature (Tasker does this by default). The alarm time comes from the system, so if the Complication says midnight then an app has an alarm at that time. If you tap the Complication, what app does it open?

from smartspacer.

Usually this is caused by another app abusing the alarm feature (Tasker does this by default). The alarm time comes from the system, so if the Complication says midnight then an app has an alarm at that time. If you tap the Complication, what app does it open?

I've tested it and the complication does nothing, but if there is a valid alarm (as in within 12 hours of the same day) it will open the clock app.

As demonstrated here (watch white spot indicating tap):

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work?
(Sorry for my late reply, I fell asleep after my last comment)

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work? (Sorry for my late reply, I fell asleep after my last comment)

It shows whatever the system reports. If there's an alarm that isn't showing, there's nothing I can do.

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work? (Sorry for my late reply, I fell asleep after my last comment)

It shows whatever the system reports. If there's an alarm that isn't showing, there's nothing I can do.

Ah I see, is this issue present on your side? Or is it just a device specific issue? And if it is device specific, is there anything I can do on my side to possibly fix this?

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work? (Sorry for my late reply, I fell asleep after my last comment)

It shows whatever the system reports. If there's an alarm that isn't showing, there's nothing I can do.

Ah I see, is this issue present on your side? Or is it just a device specific issue? And if it is device specific, is there anything I can do on my side to possibly fix this?

It seems to be device specific.

from smartspacer.

Hmm maybe the Complication should ignore an alarm without anything to open then, though the Android documentation doesn't require this to be set so it may cause some false positives for apps who are genuinely using alarms.

I see, so is the other issue of not showing the next alarm within 12 hours if it's the next day related or it's just the way it's supposed to work? (Sorry for my late reply, I fell asleep after my last comment)

It shows whatever the system reports. If there's an alarm that isn't showing, there's nothing I can do.

Ah I see, is this issue present on your side? Or is it just a device specific issue? And if it is device specific, is there anything I can do on my side to possibly fix this?

It seems to be device specific.

Hey, after a few reboots it suddenly works but I don't know why it shows the alarm an hour too early? Any idea why?

from smartspacer.

1.3.2 no longer shows alarms without a launch intent, which is as far as I'm willing to go to fix OEM shit.

from smartspacer.