I have configured Blackberry plugin in eclipse
a) Eclipse with blackberry plugin pre-loaded - 32 bit
b) JDK 1.7 -
32 bit
c) Blackberry simulators
d) jre 7
It is configured properly and app is running fine when i run the app first time.
Later if i made any changes in code and run the app again then loader appears on the simulator which is running but nothing happens. (loader got dismiss as well)
App simply wont run until i close the simulator and relaunch it.
Please help regarding this. Initially it is working fine on 32 bit machine
Related
I'm trying to port my Android app to BB10 using the BB Android Runtime SDK. I've packaged the app OK and created a BAR file, but cannot get it installed on the BB 10 Dev Alpha simulator. I've tried both running the app from Eclipse using Run As->BlackBerry Android Launch, and using the BlackBerry Tablet OS Graphical Aid 'Install' option, and in both cases I get this output :
Info: Sending request: Install
Info: Action: Install
Info: File size: 1709216
Info: Installing ...
Info: Processing 1709216 bytes
In Eclipse I also get the error 'Failed to deploy project ...'. In the BB graphical aid I just get the above output in the 'Operation Output' window. From seeing other posts it seems I should be seeing further log entries such as 'Info: Progress 0%...', 'Info: Progress 50%...' etc. which I don't see. Any ideas what the problem might be?
My experience is double check if the application has already existed. If yes, you have to remove/uninstall it first from the simulator (by long-click on the application's icon and click the recycle icon at the top-right).
Solved this by completely uninstalling VMPlayer and the BB10 simulator, cleaning my registry and then reinstalling. Still no idea why it wasn't working.
Have installed the brand new BB 10 Dev Simulator version 10.1 - the one that allows selecting to boot into Z10 or Q10 device, and I can now deploy my app every time on Windows. Can only assume the problem was caused by bugs in the previous simulator version.
I'm using Eclipse Juno (build 20120920-0800) on openSUSE 12.2 to code Android applications.
I have installed the SDK by uncompressing it into my home directory (if I install the SDK via YaST package I can't download stuff unless I'm root). I installed ADT from Eclipse Marketplace, configured the path of the SDK and configured a couple of emulator configurations.
I can run and debug fine on my phone, and I guess the same applies to my tablet even if I haven't tried yet.
The real problem is that I can't run the emulator. Clicking on the bacarozzo debug icon prompts me to run the application on the device but doesn't show me available emulators.
If I open the device manager I'm shown with the virtual devices I created but I can't just start any. The progress bar reaches the end, I see no emulator screen and if I try to delete the emulator I'm warned that the instance is running... (OK in the screenshot there is only one, I already managed to delete the other)
I urge to test some GUI features in an outdated version of Android. I have done all the field tests of the business logic code in my program on a JB device and I know for sure that code works on any device.
Now I only need to be backward-compatible with preferences and layouts.
How can I start the emulator in Linux?
Just by luck I managed to run the emulator from console
djechelon#RAYNOR:~/android-sdk-linux/tools> ./emulator-arm -avd Emulator_cell
It came to life and Eclipse debug is detecting it as active device
I have been working for a year with eclipse, but after I upgraded to the Android SDK Tools v20, the emulator doesn't work (absolutely nothing happens). I have everything installed as always, but when I run the emulator, it doesn't appear anymore (althought just after installing SDK Tools v20 it worked twice).
I have even installed again the SO (Linux Mint), after I tried everything I read here, at curiously, the emulator worked 4 or 5 times. The symptoms are these:
-when I run the app, nothing happens in my laptop, but if I put the mouse over the green triangle for running the app, it says: run (already running)
-I've tried to kill the server with adb but doesn't work
-If I list the devices with adb devices, it doesn list any device, even if eclipse says that is running the emulator
-I've tried two different versions of Eclipse: Juno and Galileo, but it's the same
-I've tried to run an emulator independently, but it doesn't work
-I've created several AVD, with different APIs and characteristics, but nothing happens
Does anybody has any solution to this?
Thanks
Good idea to make :Project ->clean
Window ->AVD Manager -> pick your virtual device ->Edit-> Snapshot(make sure is disabled) ->Edit AVD (try again, if still not working , then try to launch the emulator directly from AVD Manager -> Start).
Once the emulator is starting then you can check back the snapshot option again.
If nothing of that works, then try to uninstall/Install SDK again.
I was debugging blackberry apps from Eclipse. It works fine at the beginning but since some days ago, I could no longer get the app onto any emulator or device.
The packaging and signing shows NO error. After it displays the "debugger attaching..." screen, I could not find the app anywhere on the emulator or device. I have tried to reinstall the eclipse and JDEs a few times. One observation is that it had about 280 files to sign. Without any changes in the code now it has 540 files to sign.
I just got a new computer and am trying to set up my developing environment but I'm having trouble getting eclipse to connect with my phone. I have a HTC Aria android device and I was able to use it with eclipse on my old Windows XP computer. On my new Windows 7 64bit computer though, its not working.
When I run my program, I see my HTC device in the device chooser, however, its state is "offline" and it randomly disappears then reappears. I can select it, but I cannot push "OK" to run on the device. I've tried reinstalling my driver and updating it through HTC's website, but nothing has changed.
Any ideas?
I ended up reinstalling my OS, installing Eclipse Indigo 64bit, and then installing my phone driver. Works perfectly now. Have no idea what was wrong before