The Dragonboard 410c with the android crashes immediately after bootup. I tried the same thing with 2 different new dragonboards. In order to cross check, I again installed a new android through SD card but, issue still persists.
I wanted to run ADB commands through the dragonboard.
Initially it used to crash after ADB root and ADB reboot commands and I had to disconnect and reconnect the adapter to start it again. But now it just flashes and then crashes even before I write the commands.
It would be a great help if someone can help me fix this thing and know the reason behind such indefinite crashes ?
P.S.: No such problems were there with the 201c module.
Related
I am currently working on an Android project but I have a problem.
I'm using Android Studio and the Android Emulator and every time I place a GSM call to the emulator, ADB loses connection to the device and I have to restart ADB to get the device detected again. The call does get placed to the emulator though.
It's causing me problems as I am trying to debug a bit of code that I have written that is fired when a call is detected but because ADB disconnects the emulator every time I can't step through the code in debug mode.
This is an extremely annoying problem, and I've been wrestling with it, ESPECIALLY since the app I am writing initializes upon receipt of a call.
The quickest way to get back up and running, without restarting the emulator, is to have a second terminal window open (or exit the telnet session for a few seconds) and run:
adb kill-server
adb start-server
Or, alternatively:
adb kill-server;adb start-server
...if you'd like to run it at once.
After a few seconds, you'll be reconnected. I've spent several hours searching for a way to actually PREVENT the disconnect in the first place, but I don't think it's possible until they fix the bug.
Have you tried to update your Android SDK? Update it and create new virtual device. Maybe that can help you.
Perhaps try genymotion? Much better emulator than the standard one. http://www.genymotion.com/ At least that way you can rule out the standard emulator, narrow it down to adb
Man,
I was having the same problem. The Genymotion would be a great option but they don't support mobile networking (gsm calls) now.
The first API working for was not 18 neither 19 (both updated) but 16.
So try it with 16 and it is working like charm. I am goin to try 17 too.
Good luck!
When trying to run an android emulator (either from eclipse or the cmd line) it simply starts an empty black box with the title 0: (obviously replacing with the name of the avd!). It never boots - doesn't even get to the boot animation.
Logcat shows absolutely no output and devices shows it as emulator:5554 - offline
This happens regardlessof which avd I start - and they had all previously worked.
I'm running all this on linux.
Edit: interestingly it also now fails to recognise an actual phone plugged in with debugging enabled... Android dev is now effectively impossible on this machine until I fix this...
Edit #2: If I create a new emulator and/or edit an existing one (even if I don't actually change anything) enables it to boot. This obviously enables me to move forward, but there is clearly still a problem with adb (actual devices still won't connect) which I still need to fix.
Edit #3: Scratch that last edit - it seemed to work briefly, but not anymore...
The emulator is a horribly slow piece of junk. Startup times of ten minutes or more are not unheard of. You are better off connecting an actual Android device via USB. If you insist on using the emulator, keep it running between debugging sessions to preserve its state (and your sanity).
Do adb reset in eclipse ddms devices view
and go to adb try this
adb shell stop
adb shell start
Ran into this problem in Eclipse--was getting errors in my XML files--as a result my R variable was unable to resolve. When the new Android Application project is created, another appcompat_v7 project is also created. These two projects are associated. The problem cropped up when I kept my main project open, but closed my appcompat_v7 project. When both were open at the same time, the problem disappeared.
Simple, but there it is.
The emulator won't launch my apps even on a real device! I've tried every solution online, even reinstalling android sdk,ADT plugin. The app run SOMTIMES(4x to be exact) though, like awhile ago, when i got home i tried it again, and it run on my first try then i began working on the code again then i tried to run it, won't run again. Even basic apps like hello world won't run most of the time. I've set the run configuration to let me choose my device everytime, but even the device chooser wont show up(showed up once only), i tried waiting for 30 minutes(also tried the kill-server start-server) but it just wont run! my real device, or the emulator is listed on the DDMS perspective and there's nothing on console. please help, cause I've wasted 2 days for this already.
Have you also tried, taking the USB cable then disabling debugging and then enabling debugging and putting the USB cable back.
I remember this happen to me, so I did what I mentioned and surprisingly it works. Hope it work for you too.
Maybe you should try deleting your emulator and creating a new one. Make sure that all your settings are correct and that you are targeting the right OS version.
I've had quite a few problems with the emulator and wiping them and starting from scratch worked more often than not.
As for the real device, the first real hurdle is getting the right drivers so that your PC can recognize it, after that kill-server start-server usually does it. I'm surprise that didn't work for you.
this is my first time asking a question on stackoverflow.
I'm working on a small app on android just for fun over the school break. My app is working fine and displays logcat just fine when I am running it on emulator. But when everytime I try to run the app on my phone through debugging bridge, logcat never displays at all. I've tried every methods that I was able to find on google including:
going into ddms and selecting my device
using adb logcat -d foo:D *:S which only displays
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
etc
I remember it was working fine quite a while ago but since i have changed to my brand new computer it just don't work anymore. Please help :( im stuck here for like 3 hours now
thank you guys =)
Try some tricks below
Sometimes phone is not recognized by the driver. Run
sudo ./adb kill-server
sudo ./adb start-server
Update ddms, the latest ones are good, and there are fixes for many issues
Run ddms from command line, the one in eclipse is not as good as the command line one.
We cant exactly predict what may be the problem , but try these methods which may workout sometime.
*Use the command adb remount
*select the device within which select your application process
*Use the TAG for your logs and create new filter with that log name.
*Click between your filter and All messages in Log cat.
*Try re connecting the device again.
If still there is problem then please share more information.
I've just solved the issue by using Log.e instead of other log levels. This took me so long time to figure it out, i've reinstalled my eclipse and adb but it didn't help at all.
I don't know if this is just for me but i hope this helps for some of you who are having same trouble as me
use Log.e !!
I have a problem with the Android emulator. After I run my application on a device it disappear from DDMS at some moment with no reason, even if it is still started. The only way to run again is to close the previous emulator and reopen it by running my application.
Do you have any solution for this strange error ? I must say that I can't deactivate my firewall if that is the problem. Also I tried to reset ADB but still doesn't work.
An answer for others that will come here looking for a solution.
You just need to restart ADB (kill-server and then start-server).
More details on how to do so: http://developmentality.wordpress.com/2010/09/13/android-disappearing-emulator-restart-adb-server/