I am having a strange issue ever since I installed eclipse on my mac mini (switched from windows machine). I am developing an opengl app on android and if I launch the app from eclipse, the android-opengl method OnSurfaceCreated() will be called randomly trashing the game (not supposed to happen). If I launch the game from the phone without eclipse this never happens. Also I have to unplug and replug the phone every time I want to build and launch from eclipse or else the phone doesn't appear as a choice. So I am suspecting there is something wrong with ADB. Any ideas? I have a samsung galaxy SIII. Is there a driver I need to install?
This happens to me too on Eclipse installed on my mac. I had to replug the device every now and then. The problem is only of the UI. If you drag a border on the device chooser UI, it will show up. See https://stackoverflow.com/a/26425489/1306419 answer on Just upgraded my OS X to Yosemite, Android Device Chooser not showing device - what to do? .
Also regarding OnSurfaceCreated() issue, please share the error that appears in LogCat.
Related
this the screenshot of my Android Studio, I'm trying to learn flutter but I'm having issues while setting my physical device to it, android studio says loading device for hours and nothing happens, and even I'm failing to initialize ABD
As you can see on the top side of your screenshot, the android studio doesn't recognize your physical android device. Make sure that your phone is connected properly and USB debugging is turned on. also you can install ADB directly if it was not included in the Android SDK.
The boss noticed that my app doesn't work on his 4.1 device, so I tried it out on a 3.0 (we agreed to have API level 11 as minimum) AVD and yes, there were issues but more with the AVD itself after fixing the class not found stuff.
the AVD started in landscape
the keyboard was in chinese (with eclipse - stuck with chinese in android virtual device 's solution not working)
the contacts app crashes (yeah, I need a contact for my app but I can trick that as opening in incoming emulated sms allows me to edit the contact of that sender)
dragging apps to the home screen locks up the phone
even maps.google.com does not work in the browser
the homescreen menu does not work (at all. The buttons show but no matter which one I click, it just doesn't do anything)
… and yeah, there are issues with my app, but how can I assume they are related to my app and not to the totally borked avd?
If these symptoms ring a bell, please let me know as I'm kind of stranded. I already wiped ADT from my Eclipse and ~/.android from my file system and installed all newly to no success.
Edit:
Many of these bugs also appear in 3.2 although 3.2 is not landscaped.
4.2.2 works "fine". It only took 2 minutes to open the apps screen but on the first boot I won't complain.
When I connect an external device through USB it does not appear in the ADVM
I was previously using Eclipse on a 32bit Win 7 build and had no problems, when a device was connected it appeared in the ADVM.
I have since clean installed the machine with 64bit Win 8 and installed Eclipse and the SDKs from scratch.
When I connect a device LogCat records a load of information about the device and what it is doing. but when I open ADVM the device is not present so I can't use it as the run target.
Any ideas?
(I am a dabbler writing silly apps for my kids devices not a fully fledged coder)
What is happening to me is that the name of the device is not being shown, but it will still be the first device when it asks me to choose. Try clicking on the first list item in the "running devices" when you have to pick which one to launch from. If you can pick it (it'll be a blank item), and Run, it should/might work.Try it out, it's exactly what's happening to me. I suspect this could be it just because your LogCat seems to be working.
I have written some codelines with libgdx in eclipse and want to run them on my android device.(It's a tablet)
But i cant find out how to do this.
I even cant run it on the android emulator provided by the android sdk. I get an error that the app stopped unexpectedly.
The app is working fine with the desktop launcher...
I hope someone can explain me how to get it working on the emulator or on my android device.
I saw somewhere that simply connecting my device via usb should be enough that eclipse is able to create an temporary app on the device, but this also didnt work.
Regards
1st of all, download SamsungKies[latest], to get and install proper USB Drivers. Its important that it should be the latest, cuz there was a bug in the previous versions.
Now that you have the drivers, simply connect your device to your machine IN USB DEBUGGING MODE.
Go to your main activity, and run.
If it launches in an emulator, close the emulator, and again in main activity, select run configurations -> Android Applications -> target -> always prompt to pick device.
Run again, and it should install and run in your phone/tablet.
NOTE:The activity closes in emulator because, by default, the emulator doesn't support OpenGLES emulation, its too heavy for your CPU.
i know its kinda late, but i hope it helps others:)
Trying to run the Android Emulator on Windows XP SP3 the Emulator will start, it will get to the point where I can see the "ANDROID" text on the screen on the emulator, then a series of 3 windows command prompt windows will open, the final of which will say "Error Reading Properties" which is similar to the problem here Android-AVD :error loading preferences
However after this dialog shows, XP crashes.
This was consistent across revision 10 and 13 of the emulator (I upgraded trying to get past the problem)
Has anybody had this problem? I haven't been able to reproduce it on any other machine than this one, I've done all the arbitrary updating of drivers etc. grasping at straws trying to make the emulator work...I can't think of what else to do
Forgot to add:
I've run the emulator with the -trace option, but all the files generated are empty.
It turned out to be a problem with my Audio driver. I had seen other people on forums reporting problems using LG headsets etc. and when they unplugged their microphones the emulator worked, but they were having different issues i.e. their system didn't reboot. I had also tried simply unplugging all my audio devices with no success. In the end I started in Windows Safe Mode, the Android emulator complained about no sound available, but didn't crash. So back in plain old Windows I just disabled my audio driver and it worked perfectly.