CHAPTER 16: The Future of Android: The 64-Bit Android 5.0 OS 629was not going to give permission to the Android SDK installer to create, move, or delete folders,
as it was trying to do, and that I should have probably started IntelliJ IDEA using a trusty Run as
Administrator work process before invoking these SDK updates.
Who knew? Clearly I was not thinking far enough ahead and I was not anticipating this problem.
So I acquiesced to this current failure and clicked the No button. This allowed the Android SDK
package installer to finish the package installations, which did not involve file or folder creation,
deletion, or movement.
Figure 16-40. Monitor an SDK Manager Log (left) for problems (right), such as the “failed to install” warning dialog
I have thus created some more updater problems, but I can fortunately show you the work process
I used to fix them, if you inadvertently do the same thing at some point in the future. As you can
see in Figure 16-41, the installs continue and the Android Support Library (API 20) and Google USB
Driver (r10) install successfully. However, the Android Wear SDK packages (System Image emulators
for ARM and Intel hardware) fail because Android 4.4W (Wear) API 20 failed to install, and these
packages are predicated on that package installing successfully, so you are going to have to go
back and run IntelliJ as an administrator (some operating systems call this mode superuser) at some
point in time after you finish taking a look at what did install successfully.
Figure 16-41. An SDK Manager Log tells you that the Android Wear system images are not installed due to the previous error