Android Studio - Running on physical device

LostBoy101

Hey I've been using Android Studio for a college project and apparently I'm having issues with getting my main project running on the physical device.

I have all the drivers installed on my HTC One M7 device and Android Studio recognizes it (debug able is enabled). For example I run it on a very basic "Hello World" project and it comes up just fine on the physical device. However when I run my larger project (my college project) it tends to bring all sorts of garbage in the logcat. (screenshot below)



I have a login activity at the launcher of the app so I presume that might be causing it all sorts of problems?

Atomic Pineapple

What's the actual problem? The logs just some some wake locks?

LostBoy101

Atomic Pineapple wrote: »

What's the actual problem? The logs just some some wake locks?

It goes on beyond the wake locks, starts releasing some garbage text about connecting to socket.

If I run a very basic simple hello world on my device, it runs just fine and pops up with no problems. I found it quite strange it won't do the same for my larger app.

LostBoy101

OSI wrote: »

Have you tried running the app on the emulator and seeing if you get the same errors?

Nope I didn't receive the same errors and here is the full logcat in the emulator.

02-17 20:50:55.172 1927-1927/com.cranium.name.craniumapp I/art﹕ Not late-enabling -Xcheck:jni (already on)
02-17 20:50:55.602 1927-1927/com.cranium.name.craniumapp W/ResourcesManager﹕ Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources.
02-17 20:50:55.602 1927-1927/com.cranium.name.craniumapp W/ResourcesManager﹕ Asset path '/system/framework/com.android.location.provider.jar' does not exist or contains no resources.
02-17 20:50:55.850 1927-1939/com.cranium.name.craniumapp I/art﹕ Background partial concurrent mark sweep GC freed 283(38KB) AllocSpace objects, 0(0B) LOS objects, 38% free, 6MB/10MB, paused 97.907ms total 307.024ms
02-17 20:50:56.020 1927-1944/com.cranium.name.craniumapp D/OpenGLRenderer﹕ Render dirty regions requested: true
02-17 20:50:56.021 1927-1927/com.cranium.name.craniumapp D/﹕ HostConnection::get() New Host Connection established 0xa61afbf0, tid 1927
02-17 20:50:56.044 1927-1927/com.cranium.name.craniumapp D/Atlas﹕ Validating map...
02-17 20:50:56.130 1927-1944/com.cranium.name.craniumapp D/﹕ HostConnection::get() New Host Connection established 0xa61b0120, tid 1944
02-17 20:50:56.178 1927-1944/com.cranium.name.craniumapp I/OpenGLRenderer﹕ Initialized EGL, version 1.4
02-17 20:50:56.207 1927-1944/com.cranium.name.craniumapp D/OpenGLRenderer﹕ Enabling debug mode 0
02-17 20:50:56.585 1927-1944/com.cranium.name.craniumapp W/EGL_emulation﹕ eglSurfaceAttrib not implemented
02-17 20:50:56.585 1927-1944/com.cranium.name.craniumapp W/OpenGLRenderer﹕ Failed to set EGL_SWAP_BEHAVIOR on surface 0xa61775c0, error=EGL_SUCCESS
02-17 20:50:57.180 1927-1927/com.cranium.name.craniumapp I/Choreographer﹕ Skipped 66 frames! The application may be doing too much work on its main thread.
02-17 20:50:58.397 1927-1927/com.cranium.name.craniumapp I/Choreographer﹕ Skipped 72 frames! The application may be doing too much work on its main thread.
02-17 20:51:07.965 1927-1944/com.cranium.name.craniumapp W/EGL_emulation﹕ eglSurfaceAttrib not implemented
02-17 20:51:07.965 1927-1944/com.cranium.name.craniumapp W/OpenGLRenderer﹕ Failed to set EGL_SWAP_BEHAVIOR on surface 0xa61775c0, error=EGL_SUCCESS

The_B_Man

Make sure u have the latest version of the SDK installed from SDK manager, and are using the latest Google Play Services.
Also, is your actual phone up to date?

LostBoy101

The_B_Man wrote: »

Make sure u have the latest version of the SDK installed from SDK manager, and are using the latest Google Play Services.
Also, is your actual phone up to date?

Aye my SDK manager should be up to date and the Google Play Services as well. Aye my phone software is running Android 4.3 and seems to be up to date.

However I found the app I was trying to run installed on my phone so I presume I go ahead and uninstall it then try again?

LostBoy101

Hey folks I finally managed to solve this problem. What I did was place android:export=true in my launcher activity as apparently when running my on device it completely ignored the launcher activity.