My Moto G4 Play (XT1607) Finally got Android Nougat (7.1.1)

I have a carrier unlocked Moto G4 Play (XT1607) which I purchased about a year ago. I've enjoyed the phone. I've really only had two issues: 1) an issue with speaker after a drop which I posted about here and 2) an issue with the GPS which seems generally sub-par, but was notably terrible on my last phone until I requested a replacement a few months ago, which I tweeted about.

This phone is notably better than the one it replaced, a Moto G LTE with 1GB memory and only two cpu cores, I think. The screen is bigger and the quality is similar or better. The extra ram and double internal storage really make a difference, as does the newer OS version.

The problem is that the phone was "promised" an update long ago...pretty much when I first got it. I actually considered the OS update potential before purchasing...so was pretty bummed when the update didn't roll out promptly. Not that Marshmallow (6.x) cause me any trouble, really. And, with Google decoupling much of their software from the OS so that search and assistant can get updates, I didn't really feel I was missing out on anything dire...but the update was promised! Each time I looked it up, someone in another country on another carrier had started rolling out the updates...but my version was carrier-unlocked and should get updates pretty soon...certainly before something with the additional bloat of Verizon, right?

Well, the day has arrived. My update finally came through. Aside a few changed icons and the option to split-window or use "on-body detection" to keep my phone unlocked (which I will probably at least try), it will probably not change my day to day use. It will probably allow me to continue considering Motorola/Lenovo products in the future, though. I'll take a late update over a lie, even though I hope this lax schedule doesn't become the norm. I'm tolerant of delays, but they should be the exception.

GIMP Export As Takes Forever! [Fix]

Also applies to Save As, and Open.

I use GIMP and (since 2.8, maybe, on Windows 10?) File > Save As causes an obnoxiously long wait before the "where to, bud" dialog pops up.  I tried to resolve this a few times...poked around in settings and saw nothing.  Of course, I Googled it...but it is such a vague query that (surprise!) the answer didn't exactly jump out at me.

Eventually, with some persistence, I came across this Super User post which gives lots of great information about the problem and the path one user took to diagnose the issue.  For those wanting to fix it, though, and not understand it tons better, you can disable your Floppy Drive in BIOS or (like I did) do it in your Device Manager by [Windows 10] right-clicking the Start Menu > selecting Device Manager > expanding Floppy Drive Controllers > right-clicking and disabling the Standard Floppy Disk Controller.

Another guy said a slow SD card seemed to be causing him to have similar issues he corrected by simply removing the SD card.  I didn't even have a floppy drive installed, though the motherboard does support it.

Hope this helps!