Can't debug app on device
All my devices are working fine. This device, which is Samsung, does not.
When I turn on the phone, the phone appears in the DDMS device list. However, none of the applications / processes show up. This is the only device for which this happens.
Yes, USB debugging is enabled.
Yes, true is debugged in the manifest.
As I said, all other devices are working fine. I can connect another device in 2 seconds and it works great.
The device runs Android 4.0.4.
Any ideas?
source to share
I had a similar issue - Samsung S3 kept opening app, waiting on black screen and crashing.
I solved this by moving all the "drawable-large-hdpi" images to "drawable-xxhdpi".
It turns out the S3 is pulling in those higher resolution images, and so it ran out of memory running out of the app.
source to share
I'm on Android 4.4.4 but just ran into a similar issue. I have a Moto X 2nd gen and a Nexus 7 and neither would allow me to debug even though the devices had USB debugging enabled and the corresponding USB drivers installed. When I connect any device, the device will tell me the message "USB debugging is connected", but the computer did not recognize the device (as a media device or otherwise).
Fixed: (on Android 4.4.4) go to Settings → Storage → (top right dots) → USB computer connection → enable media device (MTP).
I disabled this setting, thinking, "I am not using this as a media device, I just want to debug applications on it" ... but apparently it needs a setting for debugging to work. I have not seen this in the documentation or in any other posts, so I decided to share with you. Hope this saves someone else from wasting time on this.
source to share
I don't know if my letter will answer.
I bought a phone in China yesterday and this is my first Android phone after using Nokia Windows Phone since 2009. I am too lazy to check the model, but it stated something about MTxxxx and I am doing root, but the problem comes with the "USB Debugging" things. So for the last 23 hours I've been looking into this. It doesn't help me at all until I try to start it with two programs; Kingo and Iruota at the same time. And now I am rooting my device at the time of writing here ... on Kingo, he stated that 35% and iroot is just downloading and rooting, but it hasn't been done yet.
Minute 3
My phone is restarting. and now Kingo is 43%, while Iroot stated that I cannot start my android and keep asking to "try again", but I just ignore it. Keep walking with Kingo now ....
Minute 5
Kingo continues to read the root at 45%. Too slow. And now it has restarted my android phone. Now it is 49%.
Minute 7
Kingo is now rooted at 59%. I hope this continues as I eat KFC and type, while at the same time I want to play CS 1.6 ... damn it. Faster Faster! 60% and restart. 3 times since then. After a reboot, it was 64%.
Minute 9
Reboot with 70% rooting.
Minute 11
Restart with 71% rooting. Too slow ... im gaining speed faster than android "rooting .... cool.
Minute 12
Restart with 72% rooting. I think it will reload with every percentage increase? What does 100 - 72 = 28 times mean to restart? I check the battery while it is plugging in so that it charges. Phew ....
Minute 13
Restart with 74% rooting. Perhaps this is the tricky part of rooting I think. Seems like Eminem's dilemma before joining the hip-hop industry. And now restart again with 75% rooting ... meh!
Minute 15
77% rooting and restart .... and 78%, restart again.
Minute 17
79% rooting and rebooting. I kept waiting and writing ... and 80% of rooting is restarted.
... AND IT'S DONE!
source to share