SanDisk’s Connect Drive app and screen overlay error on Android Marshmallow

Yesterday I installed and attempted to run the SanDisk’s Connect Drive app so I could access my wireless flash drive from my Android smartphone. However, the app refused to run, trowing an notification explaining that the ‘screen overlay settings‘ must be turned off, or else access permissions could not be set. This problem persisted until, after launching the ‘recent application menu‘ (with the square button), I noticed a ‘ES file explorer’ window appeared, signaling that this app was running. However, I did not open this app. I realized then, that maybe this app caused the problem by actively drawing over other apps. As soon as I uninstalled ES file explorer, Connect Drive let me set permissions and my wireless flash drive worked flawlessly.


Personal setup by December 2017

debian_strechFor school work I use MS Windows 10. However, for personal and hobby work I prefer Debian Linux. As of December, 2017 I’m using Debian 9 Stretch and Ubuntu Xenial on two different systems. I also use the NetBSD system where I host my Portfolio. By 2018 I expect to expand my use of system, practice embedded programming with a Beaglebone black, prepare a simple Raspberry Pi Zero server and publish more projects on Github.


Fedora linux, VirtualBox and secure-boot

Today after installing and trying to run Virtual Box on Fedora 25, I noticed that since secure-boot prevents unsigned kernel modules from running, it can be disabled as an easy solution to running VirtualBox on Fedora 25.

Two explanations from this fedora forum link :

Ok it won’t work, as I said above…

Then I had a look in the bios, and I saw that the Secure Boot is enable (there was Windows 8 on this computer before…) I disabled it just in case, and then it works


Yes, secure boot could have a definite impact if the virtualbox kernel module isn’t signed. That is exactly what secure boot is supposed to prevent.

With secure boot, your kernel and all kernel modules have to be signed.

Now this is where things get tricky or flat out painful.

You kernel is signed by Fedora using their key. Fedora isn’t going to sign the virtualbox drivers, especially since it goes against their FOSS policy. Oracle can’t sign virtualbox using Fedora’s key.

So, you are pretty much left with 2 options.

1: Disable secure boot


2: get your own key and sign everything yourself.