<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Fix on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/fix/</link>
        <description>Recent content in Fix on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Tue, 07 Feb 2017 09:00:37 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/fix/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Lineage OS Fix: After reboot phone not usable anymore (Only back button/statusbar visible)</title>
            <link>https://www.nico-maas.de/posts/2017-02-07-lineage-os-fix-after-reboot-phone-not-usable-anymore-only-back-buttonstatusbar-visible/</link>
            <pubDate>Tue, 07 Feb 2017 09:00:37 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-02-07-lineage-os-fix-after-reboot-phone-not-usable-anymore-only-back-buttonstatusbar-visible/</guid>
            <description>&lt;p&gt;Sadly, my Nexus 4 (mako) had a rough experience after upgrading to Lineage OS: After a reboot, I ended up with this screen:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img class=&#34;gallery-image&#34; data-flex-basis=&#34;144px&#34; data-flex-grow=&#34;60&#34; height=&#34;1280&#34; loading=&#34;lazy&#34; sizes=&#34;(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px&#34; src=&#34;https://www.nico-maas.de/posts/2017-02-07-lineage-os-fix-after-reboot-phone-not-usable-anymore-only-back-buttonstatusbar-visible/lineageos_broken.png&#34; width=&#34;768&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;As you can see, only the back button and status bar are visible anymore, I can drag down the status bar and enable / disable stuff but cannot launch the settings or anything else - brick&amp;rsquo;d :(. I had to reinstall that thing several times, but then came to the conclusion what caused the error: I had enabled a screenlock (does not matter which kind :)) and played with the System Profile under Settings. I created a second System Profile which - as soon as it connected to my Home Wifi, removed the screenlock. And that was the problem. After two additional reboots, the error as seen manifested.&lt;/p&gt;</description>
        </item></channel>
</rss>
