Mobiles Nokia 6.1 Plus Finally Receives the ‘Hide Notch’ Feature in Android 9 Pie Update By Somnath Brahma Posted on 5 days ago Share on Facebook Share on Twitter Share on Google+ Share on Reddit Share on Pinterest Share on Linkedin Share on Tumblr The Nokia 6.1 Plus was launched back in August this year with a display notch just like the Apple iPhone X introduced last year. However, users who did not like the feature was able to hide the notch from the Settings menu. Once the notch was disabled, the space on the top was filled with a black strip leaving no traces of a notch on the screen. The Nokia 6.1 Plus However, this feature was reportedly removed by an update that was rolled out in September. This update also brought the Android security patch for the month of August along with a bunch of other new features. But the removal of the ‘hide notch’ feature did not go down too well with many of the users and they took to various forums and social media sites to complain about the same. Taking note of this glitch, the company later announced that the feature would be rolled out again at a later stage with a subsequent update. Now after two months, the company seems to have kept its promise as the latest Android 9 Pie update rolled out for the Nokia 6.1 Plus has reintroduced the ability to hide the notch. Alongside this ability, the update also brings a host of other features primarily seen on the latest version of Android, that is Android 9 Pie. While the ability to hide the notch has been enabled, it can only be activated from the developer options. In order to enable this feature, the users have to first enable the Developer Options by heading to Settings> About Phone> System and tap on the build number seven times. Now, the users have to head to Developer Options from System Settings and look for the “Full Bezel” option. Once found, they can tap on it to enable the hide notch feature. The ability to hide the notch feature was reportedly removed to stick to the guidelines imposed by Google. HMD Global earlier said that they had to remove this feature because Google did not allow this feature.