I know that this is unlikely the correct place to ask, but I don't know where I should.
So I have a normal macbook from 2016.
I had Android studio installed a couple of months and worked with it just fine for a long time.
Now upgrading to Mojave, Android Studio doesn't open anymore.
I reinstalled it already 5 times, tried everything I found in the internet but still not able to start it.
After installing and moving it to applications It asks me to open it, I accept and then it starts to bounce but never opens.
I have restarted my Mac as well, tried different accounts.
Any one with same issue who solved it or has any idea how it could be solved?
I am having the same issue and according to Android Studio's website, it seems like it only supports up to High Sierra. Scroll to the bottom of this page and look into the system requirements-> https://developer.android.com/studio/
Try to delete (or fix) your custom studio.vmoptions file (if it exists). I had the same problem, until i've noticed, that studio runnable file writes to log, that my studio.vmoptions (in my Users/myusername/Librery/Preferences/AndroidStudio directory) has wrong parameter. Then I just delete this custom studio.vmoptions - and android studio starts normally.
Related
I just updated my Android Studio and since the update, it will load to about 80% and then just freeze. It won't give an error and it will just never load no matter how long you wait. I have tried uninstalling and redownloading along with other various things but nothing seems to be working any ideas?
enter image description here
try deleting the folder for windows
C:\Users\USERNAME\.AndroidStudio4.0
and for MAC
/Users/YOURNAME/Library/Preferences/AndroidStudio4.0
Disconnect your phone if it is connected to the computer.
It may sound strange, but I had a similar situation.
Also, you can have a look at this post: Android Studio freezes on startup
I've been developing an Android app for a week using Android Studio. I've noticed my disk space has been dropping and I don't know why. It seems that each time I run the app (99% of the time I use a test device, not an emulator), I lose disk space on my computer's hard drive. I have no idea why. Does anyone else know why and how I can fix it?
Update 2021: I had forgotten that I asked this question but someone else is having the same problem. I never figured this out on my old laptop. I ended up only working on my desktop (which didn't have this problem). Sorry I can't be more help :/
Try doing Build->Clean Project and then Build->Rebuild Project, it will reduce the space occupied by your project folder.
As for the rest, a good portion of the space occupied by Android Studio comes from the packages you have downloaded within the SDK manager. Try uninstalling those you don't currently need to free some space on your HD. See if it helps.
I am using ubuntu 12.04,and Eclipse Platform Version: 3.7.2, I have one issue which i observed occasionally on my system I dont know whether this issue is common and did't find any related question so asked.. problem is - "when I tried to launch android application using emulator(API level 17 Nexus 4),it runs fine no problem and emulator is in front of me, But the moment i open other window like browser,editor it hides and i am not able to see it.." Log says that emulator is ruuning but dont know where it hide.
If someone else is facing this problem, it could be due to memory overwhelming. To solve, in Ubuntu, go to Home/.android/avd/Pixel_X_API_XX.avd
and delete the *lock files, then Run the emulator as usually.
Where I wrote Pixel_X_API_XX.avd it means, for example : Pixel_2_API_32.avd
Bye bye
The title pretty much says it all. I was making a simple Hello-world app and after having recompiled it a few times the newest versioned stopped showing upp in the avd. It was stuck with the same version no matter how many times i tried recompiling. After having uninstalled the app in the avd, relauched the avd a couple times, etc it started working normally again and updated for each recompile.
Now i just started a new project, added a few buttons and stuff to it and this problem appears again. No matter what I do, it just shows the state of a newly-created project without any editing. I.e with a textfield saying something like "hello*name*activity"
Edit: After playing around a bit more i.e. uninstalled the app in the avd, wiped userdata in the avd, restarted the avd, restarted eclipse, it still just showed the helloactivity-text instead of my app. Finally i rebooted my computer which "solved" it. Very annoying. I can especially imagine this being frstrating when you're not even sure if it's the new or the old version of the app shwing upp, like when trying to fix a bug.
Any idea as how to fix this issue?
Thanks in advance!
I have run into this with Eclipse's incremental updates, try a clean build, uninstall the app (I see you already tried this) from the avd and finally file a bug report.
I am trying to test my app on android emulator. So as soon as, i am choosing run the application, a new window pops up on the screen and after taking 1-2 minutes, it goes not responding.
I also tried running the emulator separately using AVD manager. Using this, i am able to start the emulator; but after 3-4 minutes - it goes "not responding".
OS- Windows 7 32 bit [ intel pentium 3.00 GHZ + 2GB RAM]
Java - 1.6
Android SDK - i have the latest SDK with 3.0 OS
IDE - eclipse Helios Service Release 2.
Plz help, i am unable to do anything.
Update: can you guys point me towards other 3rd party emulators which i can use?
Update2: My emulator is taking too much time in launching now. Can this be a cause? If yes, then how do i decrease the boot time?
(This isn't so much of an answer, but might go some way to figuring out the source of the problem; I'd comment on the original question instead but don't have enough rep to do so)
I keep having this problem too. I have an app with a few activities, one of which contains a layout with a Canvas which runs its own thread to do drawing processing. All of the activities run fine except for this Canvas activity which seems to crash the emulator in the way the OP described (the emulator .exe itself crashes rather than the application within the emulator) if left to run for a few minutes. As far as I can tell I'm not doing anything unusual with the thread - I copied the Lunar Landar example in the SDK and worked from that so I'm doing everything "by the book". The app runs fine on real devices.
So, while I realise the OP may be long gone, could anyone else with a similar problem confirm that the affected Activity is using a Canvas, drawing Thread, or anything like that? This problem is a real pain and I can't find any other discussions/solutions for the matter.
EDIT: I recently did a complete, clean re-install of the most recent versions of Eclipse and the Android SDK with all the updates and that seemed to solve the problem. Guess there was a bug in an older version of the emulator that was fixed in a more recent release.
Have you enabled snapshots. If you enabled it then you can be trying to open a incorrectly saved snapshot. If so, while starting the emulator with launch options, uncheck launch from startup
#mudit:remember Android 3.0(Honeycomb) is dedicated entirely to only tablets and not the mobile phones..
Does the emulator prompts you "not responding" in your app or when you just start the emulator without launching an app, too?
A strong advice: you don't need to restart the emulator for every app launch, just keep him running (maybe you already do that).
Does the logcat show some errors prior to the "not responding"? Have you tried creating another AVD?