Tuesday, April 17, 2018

Why Android Studio is a Nightmare.

I had a dream not that long ago. In my dream, I re-vamped the app that I include with all the ROMs that I build and that I'd use my CoH C framework to provide some interesting features and functions. Being inspired by that dream I formulated a plan. I'd download "Android Studio" and create an App and it would be GLORIOUS! I'd have to work on it when I was not online but that would not be a problem would it? Nah... On to the download of Android Studio!

This is when the dark clouds started to gather on the horizon. Android Studio, for Linux, comes in a big zip that you just extract and run from anywhere. I know it's just a small thing but can't we get some OS integration here. I mean, when you download Chrome for Ubuntu, it installs itself in an appropriate location and puts a launcher in the menu. With Android Studio, I got to extract the zip then "cd" to the location and "cd" to the bin dir and launch a shell script from the terminal. OK, I could create my own launcher and all but still. It's a small bummer and darkens my day but these dark clouds won't stick around will they? Na, surely the sun will shine!

Soooo, I've got Android Studio and I can start on this when in my "offline" time right? Well, when that time rolls around I setup my laptop and fire up Android Studio but low and behold, I can't do anything. There is some error about the sdk. You need the "sdk" of course. Can't do anything without the sdk! And oh, great, there are like 27 of them to choose from and Gigs upon gigs of sdk to download. YAY! Hope you caught the thick sarcasm. Suffice it to say, the time that I had set aside to begin this project was entirely wasted.

Example message similar to the one I was getting...

At my next opportunity, I remember that I must fire up Android Studio and allow it to get it's sdk. Of course half way through the HUGE download my connection dies and then reconnects. Android Studio hangs there like a deer staring at headlights. Now, of course, it's not Android Studio's fault that my connection dies but being able to resume a broken download is a common affair these days. Hell, "wget" can resume a broken download. You just kill and and resume with "wget -c $url". So I wasted a bunch of time restarting the same download over and over again until finally, I did just download it with "wget"( fortunately the SDK Manager lists the full url to the download) and looked up online how to set the sdk folder. OK. B.S. is done I'm all set up and I can work on this in my offline time right?

Is it getting darker around here? I'm getting cold. Is it just me? What was that? Did you hear that? So fired up the laptop, launched Android Studio and start a new project with "C++" support. Gradle sync failed!. UAGGGGGH! Yes if you want "C++" you need the NDK. Of course! The NDK! How the eff did I miss that! Now, I gotta wait till, I'm online AGAIN to download more Gigs of NDK. For effs sake, why can't Android Studio just come with everything it needs! I'll tell you why, cause if it did you'd be downloading like 10GB all at once!

Example message similar to what I got.

So now, its dark and cold everywhere and this crazy "Android Studio" clown is laughing at me and creepily saying "Download more addons! and oh and now that you've got the NDK downloaded, I'm ready to update to a new version. download... download... download..." AHHHHHHHHHHH!


  1. My sympathies. I have to teach using the beast and I have no other options. Can you believe this. Even the "Hello World" app fails the gradle sync test.

    1. "Hello World", more like "Hello Broken World". I guess Android Studio is not geared for beginners because all the complication and setup is very discouraging. I'd much rather build an app with the ROM.