D droid Member Licensed User Longtime User Oct 11, 2013 #1 I am a new user. I installed the SDK and am trying to write MyFirstProgram. I can't get past launching and starting the emulator. It never starts. I read the other threads and followed Erel's link in one of the replies to reinstall the android sdk. In the cmd window, adb devices returns nothing. Getting frustrated. If anyone has a clue, I will be grateful. Thanks.
I am a new user. I installed the SDK and am trying to write MyFirstProgram. I can't get past launching and starting the emulator. It never starts. I read the other threads and followed Erel's link in one of the replies to reinstall the android sdk. In the cmd window, adb devices returns nothing. Getting frustrated. If anyone has a clue, I will be grateful. Thanks.
NJDude Expert Licensed User Longtime User Oct 11, 2013 #2 The emulator is very very very very....slow, if is not working then you might need to reinstall the SDK, get it HERE Upvote 0
The emulator is very very very very....slow, if is not working then you might need to reinstall the SDK, get it HERE
D droid Member Licensed User Longtime User Oct 11, 2013 #3 NJDude. Yes it is. But I have found the solution. I recreated the AVD, overriding the original one I had created before reinstalling the sdk. The emulator has now appeared. Sorry for the panic. I just wasted half the afternoon on this before I posted. Hopefully it's smooth sailing from here. Thanks : o ) Upvote 0
NJDude. Yes it is. But I have found the solution. I recreated the AVD, overriding the original one I had created before reinstalling the sdk. The emulator has now appeared. Sorry for the panic. I just wasted half the afternoon on this before I posted. Hopefully it's smooth sailing from here. Thanks : o )
D droid Member Licensed User Longtime User Dec 4, 2013 #4 NJDude said: The emulator is very very very very....slow, if is not working then you might need to reinstall the SDK, get it HERE Click to expand... I've now owned B4A for nearly a month and have yet to be able to use it. I know I'm doing something wrong because all the posts rave about how easy this program is to use. At Erel's suggestion, I installed Genymotion and created an emulator. When I run it I am prompted to locate the ADB. On my PC, the ADB executable is located at C:/Android/platform-tools/. However, Genymotion says it cannot find the ADB in this folder. The Genymotion install guide also contains the following statement: "adt-bundle\sdk\platform-tools" is not a valid value. where the parts of the path prior to ...\platform-tools is apparently where ADB gets placed if you follow the Genymotion link to find and install ADB . So, is the ...\platform-tools part of the path what Genymotion doesn't like? If anyone has a clue as to what I should do at this point, I'd appreciate it. I'd sure like to try B4A before my licence expires. Thank you. Upvote 0
NJDude said: The emulator is very very very very....slow, if is not working then you might need to reinstall the SDK, get it HERE Click to expand... I've now owned B4A for nearly a month and have yet to be able to use it. I know I'm doing something wrong because all the posts rave about how easy this program is to use. At Erel's suggestion, I installed Genymotion and created an emulator. When I run it I am prompted to locate the ADB. On my PC, the ADB executable is located at C:/Android/platform-tools/. However, Genymotion says it cannot find the ADB in this folder. The Genymotion install guide also contains the following statement: "adt-bundle\sdk\platform-tools" is not a valid value. where the parts of the path prior to ...\platform-tools is apparently where ADB gets placed if you follow the Genymotion link to find and install ADB . So, is the ...\platform-tools part of the path what Genymotion doesn't like? If anyone has a clue as to what I should do at this point, I'd appreciate it. I'd sure like to try B4A before my licence expires. Thank you.
D devlei Active Member Licensed User Longtime User Dec 4, 2013 #5 I also struggled with the standard emulator, and even more with Genymotion, but found BlueStacks to be really simple. It can be downloaded at the following link: http://bluestacks-app-player.en.softonic.com/ . I'm not sure that it runs on Win 8, but definitely on Win 7. Don't give up on B4A just because you can't get the emulator working initially - it has something to do with your installation/settings. BTW, don't you have a device you can use for testing. Setting up a device via the B4A Wireless bridge is straightforward (assuming you have a device and wireless). Upvote 0
I also struggled with the standard emulator, and even more with Genymotion, but found BlueStacks to be really simple. It can be downloaded at the following link: http://bluestacks-app-player.en.softonic.com/ . I'm not sure that it runs on Win 8, but definitely on Win 7. Don't give up on B4A just because you can't get the emulator working initially - it has something to do with your installation/settings. BTW, don't you have a device you can use for testing. Setting up a device via the B4A Wireless bridge is straightforward (assuming you have a device and wireless).
Erel B4X founder Staff member Licensed User Longtime User Dec 4, 2013 #6 Note that the emulator is part of Android SDK, not Basic4android. Why don't you use a real device instead? You have several options to connect the device to the IDE. Upvote 0
Note that the emulator is part of Android SDK, not Basic4android. Why don't you use a real device instead? You have several options to connect the device to the IDE.
D droid Member Licensed User Longtime User Dec 5, 2013 #7 Erel said: Note that the emulator is part of Android SDK, not Basic4android. Why don't you use a real device instead? You have several options to connect the device to the IDE. Click to expand... OK. I'll use a real device for now and save the emulator struggle for the future. Thanks. Upvote 0
Erel said: Note that the emulator is part of Android SDK, not Basic4android. Why don't you use a real device instead? You have several options to connect the device to the IDE. Click to expand... OK. I'll use a real device for now and save the emulator struggle for the future. Thanks.
