{"id":896,"date":"2019-01-10T21:42:00","date_gmt":"2019-01-10T19:42:00","guid":{"rendered":"http:\/\/mattiesworld.gotdns.org\/weblog\/?p=896"},"modified":"2019-01-10T21:42:00","modified_gmt":"2019-01-10T19:42:00","slug":"onscreenclock-permission-problem","status":"publish","type":"post","link":"https:\/\/mattiesworld.gotdns.org\/weblog\/2019\/01\/10\/onscreenclock-permission-problem\/","title":{"rendered":"OnScreenClock: permission problem"},"content":{"rendered":"<p>Several users have brought to my attention that the clock app no longer works after a device factory reset due to a permission problem. The dreaded message appears:<\/p>\n<blockquote><p>Unfortunately, your device&#8217;s rom does not support a user interface for granting the overlay permission :\/<\/p><\/blockquote>\n<p>These are my findings so far:<\/p>\n<p><span style=\"text-decoration: underline;\">Not brand or model specific problem<br \/>\n<\/span>When I received the first report, I uninstalled the app on my Nexus Player (Oreo) and reinstalled it and guess what: same problem. In the meantime I received reports on Sony TV and Nvidia Shield TV.<\/p>\n<p><span style=\"text-decoration: underline;\">Android TV Marshmallow and higher<\/span><br \/>\nYes, all trouble started with Marshmallow. \ud83d\ude09 I received reports on Nougat and Oreo and tested the app also on a Nexus 7 tablet (KitKat) and Pie phone. Unsurprisingly on KitKat no problem since no permissions exist yet, on Pie my phone showed a permission dialog to grant the permission (which is good, but still abnormal).<\/p>\n<p>Unfortunately, I have not encountered an Android TV rom yet which provides a user interface for granting the overlay permission (it&#8217;s not in stock android TV and none of the vendors seem to care).<\/p>\n<p><span style=\"text-decoration: underline;\">Fresh installs<br \/>\n<\/span>All reports were due to device resets, but as I already pointed out: simply uninstalling and reinstalling the clock app will exhibit the problem. Updating the app is no problem since it will preserve the previously granted permission. By taking advantage of this, I can test out a fix without impacting existing users.<\/p>\n<p>&nbsp;<\/p>\n<p>I did a quick search on the interwebs but no luck so far, it&#8217;s kind of a niche topic after all. \ud83d\ude09 I suspect a google Play Services or Play store update is the culprit but didn&#8217;t find any news yet. If it&#8217;s part of a security fix, information will be sparse anyhow.<\/p>\n<p>I see several options:<\/p>\n<ul>\n<li>google did a small fuckup in the play services or store (as they did with the remote not responding, deep sleeping) and might fix it (can take several months)<\/li>\n<li>google intentionally changed the way the overlay permission is granted (and no longer wants to grant it automagically)<\/li>\n<li>the permission not being granted anymore might be a side effect of some other policy change<\/li>\n<\/ul>\n<p>Overlay permissions have always been tricky on android (tv), so let&#8217;s hope there is a solution possible.. (or a hack at least)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Several users have brought to my attention that the clock app no longer works after a device factory reset due to a permission problem. The dreaded message appears: Unfortunately, your device&#8217;s rom does not support a user interface for granting the overlay permission :\/ These are my findings so far: Not brand or model specific &hellip; <a href=\"https:\/\/mattiesworld.gotdns.org\/weblog\/2019\/01\/10\/onscreenclock-permission-problem\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">OnScreenClock: permission problem<\/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":[35,40],"tags":[],"class_list":["post-896","post","type-post","status-publish","format-standard","hentry","category-android","category-onscreenclock"],"_links":{"self":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/896","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=896"}],"version-history":[{"count":3,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/896\/revisions"}],"predecessor-version":[{"id":900,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/896\/revisions\/900"}],"wp:attachment":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/media?parent=896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/categories?post=896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/tags?post=896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}