I've added ember-cordova to my ember app;
after that I've tried to open the project in android-studio but at startup it starts "Scanning files to index..." and never ends... While it'ìs doing that it's impossible to run the app in the emulator;
I've been googling a lot and tried many things like invalidating caches, but nothing worked;
I'm using android 2.2.2; is there a knowed solution to speed it up? I guess this is not normal, the project is not that big;
I can't even understand if it's just very slow (if in N hours it will come to an end) or if it's blocked and will never end
Related
I use Visual Studio for Mac on M1 MacBook Air, specifically targeting Android using Monogame.
The build gets stuck randomly and at any point in time, so the first time I build after opening VS, it works fine, the 2nd or 3rd gets stuck, and I can't cancel the build, so I have to close the application and reopen it and start again, and the cycle happens again. If anyone encountered something similar, please share any solution with me
I don't know what I should try to do, since VS get stuck at random during the build, and getting stuck happens randomly too
I managed to solve my problem, it turns out that I turned on some features in Project Properties which were supposed to be for release mode, that's why somethings took ages to build.
Utter Wits end. Tried all solutions: clean build, sync project files with gradle, build Bundles, Build APKs, disable and re-enable instant runs etc.
Followed Exact steps outlined in other threads/ posts but still couldn't get the app to run on my physical Samsung Galaxy S7 phone. It was working fine previously, but now couldn't get it to work. App still able to open on Emulators though.
Needed to test out gyroscope and accelerometer sensors on a physical phone which emulators can't achieve as intent.
Would like to seek help from the community regarding this matter. Any idea where it has gone wrong? I have already updated my compilesdkverison and targetsdkversion in the module:app build.gradle scripts. Tried almost everything that I can think of but to no avail. Hoping to see the light and receive enlightenment from the community as I'm a novice in Android Studio.
PS: By the way, how do people add actual iamges to the post, itseems like the only way i can show an image is in the form of a hyperlink away from current page. Is there a way to just put the image directly in the post here?
Looks like there is not enough space on your phone. Try making some space on your internal memory.
While researching this I was writing an answer to IntelliJ IDEA: Breakpoint not being hit, and is shown without the tick, just a red dot until I realised it is a completely different question. I have had this issue twice in the past 4 weeks, but my use-case is IntelliJ is no longer ticking the red breakpoints. I just watched the ticks fall away before my eyes.
First time it occurred was after unceremoniously ripping out the USB cable in a hurry. I don't appreciate the need for ceremony here. That broken project remains so.
I tried everything to fix it, and gave up on that particular project; it was largely complete. I tried adb kill-server and the general family of off-then-on-again solutions to no avail.
Fast forward a couple of weeks I'd forgotten about it and was delighted (I tell a lie, I was taking it for granted) to be able to test my new protocol with breakpoints on an Android device. First symptom was my icons messing up (I thought I must have had a trapped thread somewhere in the IDE but find it hard to believe I wouldn't have noticed that with just the single process being debugged). Next the breakpoint's tick just dissappeared and I had a blue message in the IDE's console, something about GDX and taking too long with the graphics (similar message appended at bottom of post). Foolishly I restarted the apk.
What haven't I tried? I'm thinking something drastic like persevering with Desktop only development, or ditching Windows. I thought about upgrading (contracting) Gradle but my other project was brand spanking new and recently diagnosed with specific Gradle version dependencies.
I can start the app from my dev machine but even pausing isn't able to find what it is doing because it will pick a (random) thread out of context with my app.
I can also hit breakpoints from the Desktop app
I suppose I should try Android Studio with this project but know that won't be an easy fix. I'm using Win10 Pro and on brand laptop and phone (nothing fancy mind). I'm using Gradle 2.1 (IIRC, I get a daily nag to upgrade to 4.1) but my other similarly fated project has specific dependencies on Gradle versions so I want to leave well enough alone.
I don't know if it's the answer or not, but it seems to work fine with the emulator, which would seem a more universal solution than something as challenging as, you know, supporting a bunch of different hardware. I ran it again and trapped a certain line, observed the same screen artifacts as before, but killed it before I could lose my emulator too.
This is the last thing she printed:
W/zygote: Long monitor contention with owner GLThread 260 (8155) at boolean com.mygame.game.screens.Menu$4.keyDown(int)(Menu.java:128) waiters=0 in boolean com.badlogic.gdx.backends.android.AndroidInput.onKey(android.view.View, int, android.view.KeyEvent) for 9.799s
It was trapped in a different method but the gist of it is I've blocked the GLThread.
Android Studio freezes for a few seconds every time. When tries to autocomplete, when loads gradle and even when i just open another directory! My computer has 16GB RAM core I7. I checked it's running processes and there is nothing overloading my computer. I found this log on Android studio just after a freeze action.
Received result Success[value=org.gradle.tooling.internal.provider.BuildActionResult#9ce896] from daemon DaemonInfo{pid=4363, address=[1459bd31-811f-4cf0-8cfe-ad8b357eaff9 port:54982, addresses:[/0:0:0:0:0:0:0:1%1, /127.0.0.1]], idle=true, context=DefaultDaemonContext[uid=014c14d9-e239-44bf-a401-d80b04b94f3c,javaHome=/usr/lib/jvm/java-7-openjdk-i386,daemonRegistryDir=/home/ezequiel/.gradle/daemon,pid=4363,idleTimeout=10800000,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}.
I had a similar issue recently with Android Studio 2.3.3, starting to freeze on a regular base every three to five seconds, regardless of what the actual action was and independently from a running build or any other background activity.
Gradle definitely was not the culprit here, instead it seems that some plugin or configuration made it freeze.
I ended up partially following the steps here: How to completely uninstall Android Studio?, removing everything in ~/Library/Preferences/AndroidStudio2.3 ~/Library/Application Support/AndroidStudio2.3, ~/Library/Logs/AndroidStudio2.3 and ~/Library/Caches/AndroidStudio2.3, which made CPU load go down from 100 to around 15 percent while being idle, making the freezing go away completely.
I'd loved to find out the real reason, considering the fact that this occurred on two different machines (at home and at work), which IMHO doesn't make it a "random" issue specific to only a single, weird configuration.
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.