We Keep Coding

Can't get gradle compatibility in Android Studio on Windows 10

I am new to Android Studio, and thanks to my dog knocking water on my Mac, I am using my PC with Windows 10 for the foreseeable future. Since I'm trying to learn Android Studio while also trying to pinpoint all the bs Windows is doing in the background, I have been beating my head against the wall for several days. To start, the PC I'm using has a 128GB SSD and a 1TB HDD, and since Windows is busy filling up my C: drive (the SSD), I am trying to keep everything else on the HDD. I originally installed Android Studio and went with the defaults, which put it on the C: drive, but when I realized what happened I uninstalled it and re-installed it on the D: drive. I also installed all the SDK tools and API versions on the D: drive.
The problem I am running into is every time I try to import a project from a tutorial, it says the project isn't synced with Gradle (these tutorials are all using older APIs and Gradle versions) and won't even give me the option to build. Originally, I set the GRADLE_HOME environment variable for the Gradle version installed on my D: drive to D:\Program Files\Gradle\gradle-4.8-bin\gradle-4.8\bin and then I could at least run the gradle command without getting "command not recognized...". At that point, the new projects I had created were running fine, but any project that used an older version would not sync. I guessed that I might need to install the older Gradle versions in order to be compatible with older projects, so I installed all of them and put them in the same D:\Program Files\Gradle directory, then set that to my environment variable. That broke everything since the variable was no longer pointing to a bin folder I assume. Now when I try to import a project using Gradle external model, it doesn't matter if I select the specific Gradle path to the /bin folder on the D: drive, or if I set it to C:\Users\brand.gradle, it says 'Gradle location is incorrect'. The only way I can make the gradle command work is if I go to the /bin folder for any one of the versions I have installed, and run it from inside the directory.
I know that when Android Studio installed it put the gradle configuration in C:Users\brand.gradle, part of the reason why I thought changing the GRADLE_HOME variable might fix it. Currently, the gradle command will not work if I am in the C:\Users\brand.gradle directory. I have researched a lot but can't seem to find clear answers, especially in regards to the newest versions of everything, so here are my primary questions:
Where does AS store and look for the gradle configuration on Windows by default (not for an individual project, but for Android Studio itself), and how can I get it to store and look for things on the correct drive?
Do I need every gradle version installed to be able to run projects that use older versions, and if so, is there a way that Android Studio can automatically find the appropriate version if they are in the right location?
In short, I want AS to do everything on my HDD, where all of the SDKs and gradle versions are installed, but I think it is looking in the wrong places by default, and perhaps even changing things back to default values after I change them. I want this to stop, but can't figure out what it's doing.

If you are running android Studio version 4.1.2 then go to Files -> Setting -> to
Build, Execution, Deployment, click on Gradle and it will show you the Gradle user home, it is here that you can change the directory. But make sure you copy over the Gradle files first to the external drive.

Eclipse (Oxygen) Stops Responding When Accessing EGit?

I can't seem to access eGit or use any related features in Eclipse Oxygen.
I have tried everything, and even wiped the meta, pool, and eclipse information to a complete re-install but still end up with the same issue.
For your information, I have 2 versions of Eclipse installed, Java and Java EE (if that might be a problem). I also have GitHub for Windows installed.
Some symptoms (i.e. when Eclipse stops responding):
Opening eGit perspective (it is possible if I don't have any projects in explorer, and open it from start after deleting metadata folder). Then it works until I open git projects.
Importing git & eclipse projects. Auto share git projects does not complete (or takes a long time - I stop it after 5-10 minutes).
Importing git project as Git Project (from import screen).
Importing git project from eGit perspective.
Edit: Additional symptoms:
Clone external git repository.
Load got project without git autoshare, and share project...then no response.
Accessing Team->Git->Configuration in Preferences.
Attempt to share new project.
Edit: I have now discovered (after installing previous Eclipse Neon version) that EGit still fails to work. Which may mean there is something deeper wrong with my setup/system. I hope I don't have to reinstall Windows on my system with a clean wipe. :(
I have tried just about everything. Any suggestions are greatly appreciated.

EDIT: As suggested, here is another fix to a similar (or same?) issue:
Eclipse not respond when try to configure GIT
As I was working on my project, an exclamation point popped up. Attempting to resolve this issue, I came across this solution from here:
Right click on your project -> Close Project. it will Close your project and all opened file(s) of the project
Right click on your project -> Open Project. it will Open your project and rebuild your project, Hopefully it will fix red exclamation mark
This not only fixed my project, but finally granted me access to eGit features in Eclipse.

Why I can't remove this Eclipse plugin after failed installation?

I am using Eclipse Mars and I have the following problem.
After the installation of a plugin, the Adoe Flash Builder plugin, it is a plugin that is installed outside Eclipse (executing an installer and selecting the Eclipse folder) I have some problem.
The plugin installation failed (because this plugin is supported only on the 32 bit version of Eclipse). So the plugin was not completly installed.
When I start Eclipse I obtain a lot of error messages caused by this failed installation and it is impossible to me work.
So I have tried to disinstall this plugin but it doesn't give me the possibility to uninstall it (the Uninstall button is disabled).
Here the screenshot where you can see that, selecting the plugin that I want to uninstall, the Uninstall button is disabled:
Why? Can I manually delete this plugin in some way? (I have not directory related to it into my Eclipse folder). It seems that in some way Eclipse have the information of this plugin but that this is not effectively present. How can I remove it? Or is faster reinstall and configure again my environment (Eclipse + SVN plugin + project configuration)

I have tried sometimes to get rid of "messed up" eclipse configurations.
In the end, it just didn't work out. I always ended up throwing away everything.
Besides: Eclipse Neon R2a was released already; so just download that and say goodbye to Mars.
And the real answer (in my opinionated eyes): I decided at some point to enable myself to install eclipse "from scratch" as quickly as possible (for example by having automation where possible; and "checklists" to follow where manual interaction is required). Simply because "installing from scratch" helps avoiding a lot of problems over time.
And while we are talking about eclipse best practices: if your OS is Linux, consider to switch to git-svn instead of SVN. Your machine still talks SVN to the remote SVN server, but you can enjoy the full beauty of git locally. No more SVN plugins, no more hours of waiting for that SVN plugin doing refresh ... I can't tell you how much time that simply change saved for me.

Eclipse doesn't start in Ubuntu 14.04

I have a problem trying to launch Eclipse in Ubuntu 14.04. Splash picture pops up, then blinks, turns white - and nothing happens until kingdom come.
I have tried Luna, Kepler and 3.8 (from Ubuntu repository). EE and SE editions - both the same. I have also tried to launch them with different (oracle) vm - 1.7 and 1.8.
And yes, I have tried the -clean and simple workspace removal.
This is the only thing it says in console:
org.eclipse.m2e.logback.configuration: The
org.eclipse.m2e.logback.configuration bundle was activated before the
state location was initialized. Will retry after the state location
is initialized.
Java VM works fine - I can launch (for example) IDEA or java\javac commands.
Any suggestions?

The answer is already here, but it's in the comments. So I re-post it as answer:
check your 2nd screen. Workspace dialogue may be there.

Try this:
1) Remove .snap from:
.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
If you can't find it manually try this:
find /.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;

It Generally happen when eclipse is closed unexpectedly.
Heres things you can do.!
1)Save and Delete .metadata from workspace folder.
2) Try Re-installing Eclipse.
This solution worked for me. :)

If you don't have any pending changes and have pushed your project already on your repo, you can also try deleting the project folder where eclipse opens a project path automatically.
When you run eclipse again, it will work again.
Unfortunately, deleting metadata didnt work for me. Also I don't have any extra monitor so deleting my project folder was my last resort.

Correct Java dependencies installed for eclipse ADT development

I have eclipse and the ADT bundle correctly installed on my home PC, and tried to install it on my laptop so I can work on my projects on the go. However, I either didn't set the java paths correctly, or installed them in the wrong place, because I can't get a default project to load without errors.
I have correctly:
-Installed the ADT bundle and launched eclipse without errors
-Created a workspace
-Correctly Installed both the jre8 and jdk1.8.0_05 in the location C:\Program Files\Java
I am very new to Android development, and I feel like I was lucky to set up the Java dependencies correctly on my home PC, no such luck this time from what the error look like...
However, when I try to make a basic "Hello world" project, I immediately get the following error:
The container 'Android Dependencies' references non existing library 'C:\Users\userName\workspace\appcompat_v7_3\bin\appcompat_v7_3.jar'
I have tried adding the library, by checking build configurations, but I don't understand fully whats going on to correctly solve the problem. Here is my workspace:
And lastly, I tried checking the build configurations to see that the libraries are, in fact, missing. Or something like that. I am not sure if I should just try to reinstall java and the jdk.
Build configuration:
Anyway, I'm not sure what I deleted, misplaced, uninstalled, or didn't install, but if anyone could point me to a solution I would be very grateful. If anyone has any other questions on my setup I will try and be as thorough as possible. Thank you!

In my experience I have had issues like this if not running eclipse as Administrator. Make sure that you aren't being blocked here.
EDIT: Please note Chris Stratton's concers regarding running an IDE as Administrator, as seen in the comments below.
EDIT 2: In my more recent experience, I have noticed that if I installed the SDK by copying and pasting the contents of the downloaded, compressed, folder to a destination rather than extracting it first, I would be required to run as Administrator. If this is the case, delete the SDK that you copied out of the compressed folder and simply extract the contents of the downloaded compressed folder. I am running Windows 7 so it is likely that this applies to all Windows 7 and 8 OS's.
In another case, I have also seen issues like this if the JRE is installed second rather than first. In this case, a reinstall of the SDK is probably all that is required.