<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Weird clock app behavior]]></title><description><![CDATA[<p dir="auto">This happened to me a number of times now on ut16.04 stable. When setting up an alarm, the activating switch grays out and I can't undo it. Nonetheless, the alarm doesn't ring at the given time. From the moment it starts, this behavior won't stop. I tried cleaning the app cache, wiping its user data, restarting unity and even the phone... to no avail. It renders the app unusable and last time it did happen I had to reflash the whole os. Is anyone having the same issue ?</p>
<p dir="auto"><img src="https://www.hostpic.org/images/2005011350290091.png" alt="alttext" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forums.ubports.com/topic/4186/weird-clock-app-behavior</link><generator>RSS for Node</generator><lastBuildDate>Sun, 15 Mar 2026 10:56:44 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/4186.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 01 May 2020 08:23:01 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 03 Jul 2020 16:00:32 GMT]]></title><description><![CDATA[<p dir="auto">Got a similar issue 3 days ago when activated alarm for work the next day.<br />
Button not stayed grey, green ok.<br />
But alarm didn't poped on the notification bar, and time untill it rings was about 30 days later, and not next morning.<br />
Tried all presetted alarms, all broken.<br />
Tried lot of things to resolve it, but only setting up a new alarm with same settings worked.<br />
Then i deleted the first broken one i had, and all the others now work again.</p>
<p dir="auto">First time in five years using uTouch that i have issue with alarm, it's the only one i have to not be late to work...</p>
]]></description><link>https://forums.ubports.com/post/36136</link><guid isPermaLink="true">https://forums.ubports.com/post/36136</guid><dc:creator><![CDATA[Keneda]]></dc:creator><pubDate>Fri, 03 Jul 2020 16:00:32 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Thu, 02 Jul 2020 20:04:55 GMT]]></title><description><![CDATA[<p dir="auto">Same kind of problem on Nexus 5 OTA-12. Alarms and buttons suddenly got grayed out. Restart did not change this. It was not possible to swipe and access the delete checkbox. Solved this by creating a new alarm. Then I could swipe this new alarm, select all alarms and delete all alarms.<br />
Never had any problems with the alarms before.</p>
]]></description><link>https://forums.ubports.com/post/36086</link><guid isPermaLink="true">https://forums.ubports.com/post/36086</guid><dc:creator><![CDATA[ut]]></dc:creator><pubDate>Thu, 02 Jul 2020 20:04:55 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Sun, 03 May 2020 13:25:00 GMT]]></title><description><![CDATA[<p dir="auto">Looks like it's an "old" bug:</p>
<p dir="auto"><a href="https://gitlab.com/ubports/apps/clock-app/-/issues/140" rel="nofollow ugc">https://gitlab.com/ubports/apps/clock-app/-/issues/140</a></p>
<p dir="auto">Looking further into this I found two <strong>task.ics</strong> files, in two folders named <strong>~/.local/share/evolution/tasks/xxxxxxxxxx.xxxx.x@ubuntu-phablet/</strong>. I removed the older one. Now there is just one file, <strong>~/.local/share/evolution/tasks/1514137684.3458.0@ubuntu-phablet/tasks.ics</strong><br />
looks like this has taken care of the problem.</p>
<p dir="auto">I'll play around with it, and check on the BQ m10, too...</p>
]]></description><link>https://forums.ubports.com/post/32407</link><guid isPermaLink="true">https://forums.ubports.com/post/32407</guid><dc:creator><![CDATA[hankschwie]]></dc:creator><pubDate>Sun, 03 May 2020 13:25:00 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 01 May 2020 20:33:15 GMT]]></title><description><![CDATA[<p dir="auto">I get this too on my OPO running RC, I've been trying to reproduce the issue for some time now to no avail, I haven't gone into it in-depth yet though.</p>
]]></description><link>https://forums.ubports.com/post/32348</link><guid isPermaLink="true">https://forums.ubports.com/post/32348</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Fri, 01 May 2020 20:33:15 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 01 May 2020 10:11:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/hankschwie" aria-label="Profile: hankschwie">@<bdi>hankschwie</bdi></a> Yes I agree ! "Inconsistent" pretty much sums up my phone nowadays ^^ The worst part being the totally chaotic behavior of MMS and attachments. Anyway, it works ! Cheers.</p>
]]></description><link>https://forums.ubports.com/post/32334</link><guid isPermaLink="true">https://forums.ubports.com/post/32334</guid><dc:creator><![CDATA[Emphrath]]></dc:creator><pubDate>Fri, 01 May 2020 10:11:19 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Sun, 03 May 2020 07:25:02 GMT]]></title><description><![CDATA[<p dir="auto">Yes, I am experimenting with this feature right now. But it does not seem to be consistent - sometimes all old entries are unusable, and  when activated cannot be deleted -  after  a restart I am able to delete those, when not activated. Something's really buggy here...</p>
<p dir="auto">EDIT: Checked with my BQ m10 HD - same issue... Never noticed before!</p>
]]></description><link>https://forums.ubports.com/post/32332</link><guid isPermaLink="true">https://forums.ubports.com/post/32332</guid><dc:creator><![CDATA[hankschwie]]></dc:creator><pubDate>Sun, 03 May 2020 07:25:02 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 01 May 2020 09:22:08 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/hankschwie" aria-label="Profile: hankschwie">@<bdi>hankschwie</bdi></a> Thanks for the tip ! let me return the favor: did you know you can swipe a set alarm to the right to delete it ? i just did that with the "dead" alarm, and it went away !</p>
]]></description><link>https://forums.ubports.com/post/32331</link><guid isPermaLink="true">https://forums.ubports.com/post/32331</guid><dc:creator><![CDATA[Emphrath]]></dc:creator><pubDate>Fri, 01 May 2020 09:22:08 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 01 May 2020 09:10:08 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">Yes, I have a similar problems with my FP2. I solved it setting another alarm for the same time; but the unusable entry is still there. I didn't try to reflash, since I am able to use other alarm times with no trouble. I'm on RC, will add this to the OTA12-thread.</p>
]]></description><link>https://forums.ubports.com/post/32329</link><guid isPermaLink="true">https://forums.ubports.com/post/32329</guid><dc:creator><![CDATA[hankschwie]]></dc:creator><pubDate>Fri, 01 May 2020 09:10:08 GMT</pubDate></item><item><title><![CDATA[Reply to Weird clock app behavior on Fri, 01 May 2020 08:37:46 GMT]]></title><description><![CDATA[<p dir="auto">On FP2,btw.</p>
]]></description><link>https://forums.ubports.com/post/32328</link><guid isPermaLink="true">https://forums.ubports.com/post/32328</guid><dc:creator><![CDATA[Emphrath]]></dc:creator><pubDate>Fri, 01 May 2020 08:37:46 GMT</pubDate></item></channel></rss>