{"id":822,"date":"2017-03-30T19:24:38","date_gmt":"2017-03-30T17:24:38","guid":{"rendered":"http:\/\/mattiesworld.gotdns.org\/weblog\/?p=822"},"modified":"2017-03-30T19:58:49","modified_gmt":"2017-03-30T17:58:49","slug":"onscreenclock-back-to-1-app","status":"publish","type":"post","link":"https:\/\/mattiesworld.gotdns.org\/weblog\/2017\/03\/30\/onscreenclock-back-to-1-app\/","title":{"rendered":"OnScreenClock: back to 1 app"},"content":{"rendered":"<p>When google released Android Marshmallow, they introduced a new permission model. I jumped on the band wagon too eagerly and as a result, the OnScreenClock app had become unusable on Marshmallow and up due to an unimplemented feature on Android TV. <a href=\"https:\/\/code.google.com\/p\/android\/issues\/detail?id=224286\">Complaining to google<\/a> did not help.<\/p>\n<p>So I did the only thing I could do: <a href=\"https:\/\/mattiesworld.gotdns.org\/weblog\/2016\/04\/26\/android-tv-marshmallow-and-overlay-permission\/\">release a new app<\/a> targeting an older api. This app is known as &#8220;OnScreenClock Marshmallow&#8221; (a bit of a paradox, i know \ud83d\ude09 ). Recently, however, just when I was about to migrate all users of the old app to the new one, I discovered Google has relaxed their policy, so now the &#8220;old&#8221; app is good to go again! I guess it was causing too much trouble for users everywhere.. This is undocumented so I guess Google wants to keep that change low profile. \ud83d\ude09 This also means the future is uncertain, but that&#8217;s life, right?<\/p>\n<p>To all users using the\u00a0&#8220;OnScreenClock Marshmallow&#8221; app, please migrate to the &#8220;<a href=\"https:\/\/play.google.com\/store\/apps\/details?id=mattiesworld.gotdns.org.onscreenclock\">OnScreenClock<\/a>&#8221; app as I will not be further developing the &#8220;OnScreenClock Marshmallow&#8221; app anymore.<\/p>\n<p>Apologies for the inconvience.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When google released Android Marshmallow, they introduced a new permission model. I jumped on the band wagon too eagerly and as a result, the OnScreenClock app had become unusable on Marshmallow and up due to an unimplemented feature on Android TV. Complaining to google did not help. So I did the only thing I could &hellip; <a href=\"https:\/\/mattiesworld.gotdns.org\/weblog\/2017\/03\/30\/onscreenclock-back-to-1-app\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">OnScreenClock: back to 1 app<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40],"tags":[],"class_list":["post-822","post","type-post","status-publish","format-standard","hentry","category-onscreenclock"],"_links":{"self":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/comments?post=822"}],"version-history":[{"count":3,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/822\/revisions"}],"predecessor-version":[{"id":825,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/822\/revisions\/825"}],"wp:attachment":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/media?parent=822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/categories?post=822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/tags?post=822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}