Get net_rim_os not found warning when debugging - java

Whenever I try to debug an app I am developing for the Blackberry 8xxx something,
from within Eclipse, I get this warning about net_rim_os not found.
Then I have to click away a modal, and then another with something almost the same.
I assume this is because I have only 6.x development environment installed, but the phone is 4.5.
The program works on the phone though, as long as I stay away from API not existing on the phone.
How can I make the warning never appear, or even better, install the missing symbols or whatever it is Eclipse is complaining about. It's the Eclipse provided by RIM themselves I am using.

The debugger is looking for the .debug files to support symbolic debugging. This isn't usually a problem on the simulator because it is delivered with the .debug files that match the OS. With a physical device you are faced with the issue that the OS version used on the hardware rarely, if ever, matches a version of the OS for which .debug files are available.
You will be better off compiling with an SDK version that is less than or equal to the version of the OS running on the hardware. If your testing coverage is less than complete you may end up delivering a program with a hidden API incompatability. The best practice is to compile the programs for each version of the OS you are supporting.

Configure Eclipse to use the BlackBerry Update Site. Then download and install the BlackBerry Java SDK 4.5. Configure your project to use that SDK. This will ensure that only APIs supported in 4.5 are available for compilation.

Related

OSX Java App Bundle runs on HFS+ but not APFS

I've been encountering this issue that I find has no information on the web and would like some help as I've been working on this for the last few days with no leads.
Why does my java app suddenly stop working for APFS? It works if I move the app to a non-APFS USB, but when I move the App to the SSD which is formatted to APFS, it stops working.
When I checked the app logs, it turns out that for some reason, certain libraries are not being properly imported/recognized by the app when it is run from the SSD formatted to APFS. Why would it behave differently in an APFS SSD vs an HFS+ usb/hard drive?
I've already isolated the case and found that only the APFS is the common factor. I've tested it in other devices, those that run High Sierra without an APFS drive, and those that run Sierra with an SSD that has not yet been converted to an APFS drive, and only those devices which utilize APFS filesystem formatting are encountering the issue.
Additional Information:
Java App has been properly signed, it is distributed personally but not via the App Store.
App is bundled using AppBundler not JavaPackager.
App runs on previous versions of OSX, and has been distributed and tested working on hundreds of Mac Devices with OSX varying between 10.8 - 10.12
Libraries that somehow don’t get recognize are the apache libraries, like commons-lang-2.6 (We haven’t upgraded to 3 yet), commons-logging (had to output the logs manually onto desktop to see what was happening). Strangely, app was able to import sqlite library properly.
Thanks for looking, and would appreciate any advice!
I’ve managed to fix the above issue, but I’m unsure as to why.
Solution:
Update commons.lang.2.6 to commons.lang.3.6
Currently, I’m hoping that it will not encounter any other issue aside from that, but I can only guess as to what was happening.
I think APFS cached a copy of commons.lang.3.6 and used that library instead of my own, so there was an issue with class loaders trying to find the 2.6 version. Since only APFS would have a cached copy, it would allow my app to run on a USB.
I don’t actually know the correct etiquette for finding out the answer to your own question, so please feel free to correct my post if there’s anything I need to change.

Win7 x64 Bluecove

I'm trying to use Bluecove for an application I'm writing. Version 2.1 of the jar didn't work, so a little Google showed me that it had always had issues with x64, so I turned to the latest 2.1.1 "snapshot", and I still get that the bluecove_x64 dll is missing. Am I doing something wrong, or should I just look for another API?
I encountered this problem after installing a vendor's bluetooth stack and management utilities. My java app which used bluetooth worked fine before this, after the install I got the bluecove_x64.dll not found error. After much searching, I reverted to an earlier system checkpoint (before I tried installing the "newer" bluetooth) and all was back to normal.
On another system, the toshiba bluetooth software had already been installed. I did a system checkpoint (in case the following was to not work), then went into the device manager, and uninstalled every "device" under bluetooth. Be sure to check the "delete driver software" box too, or they will come right back.
After this, the bluetooth device will appear to be gone. Go to the top of the tree, right click, and do "scan for hardware changes". This should install the Microsoft generic bluetooth drives which then work (for me) just fine on Win7_x64. If this doesn't install them, then you may try searching for a download, or another stack.

Which AVD Target is the right one for a Droid X2?

I am a noob to Android (and Java). I have successfully setup Eclipse and the Android Virtual Device (AVD). I am guessing the AVD's Target is the version of Android to be emulated, but I want to make sure. I am trying to develop something for my Droid X2 phone.
As such...
Which AVD Target is the right one for a Droid X2?
Is there an online list someplace explaining each Target?
...I have Googled both unsuccessfully.
Thank you for the help.
According to motorolas website, the Droid X2 ships with Android 2.2 (api level 8).
I'm not sure if there are any updates rolled out yet, so consider this the lowest version you will get for this device.
So target 2.2. or lower.
But just a general advice: If you want to ship your app to other people, it's usually best to target the broadest audience. So I recommend going for 1.6 as a target, that will still run on your phone. You can start to raise the target version when you notice that you need a certain feature (can be easily done from the "project properties" dialog inside eclipse in 5 seconds). If you don't seem to need any higher api features, you are way more compatible to many more devices this way.
Edit: To the targets. See Android API levels. Clicking on a version takes you to the changelog. Theres info whats new. Also notice that anything below and equal 2.3.3 is a phone os at the moment. Anything equal or above 3.0 is a tablet os.

Using Android libs on a desktop Java VM (like OpenJDK or OracleJDK)

I have never tried out the Android SDK and do not own an Android phone. However it seems that certain libraries are excellent, for example the text to speech lib. Is it possible to use this library with a desktop VM and did anybody here try this?
You could get the sources from android.git.kernel.org and try to rebuild them against a desktop environment, but it would be a lengthy project - you need not only the java stuff, but the underlying drivers, native libraries, customized c library, and add-on os functionality to support them.
The android SDK includes a qemu-based phone emulator in which most functionality works as on the device. This should be fine for playing with the capabilities, though is not something you would want to use to deploy them. There is also an x86 community build of android which people put on netbooks or run in virtualbox. Word is that the official android emulator may be moving to something similar since it's substantially faster to run x86 code on a customized os image in a vm than to emulate an arm processor.
There's also something of a simulator which tries to provide enough of the android o/s services to sort of run apps natively on the development machine without a vm, but the google folks have implied its a bit of a hack and not well maintained.

developing Blackberry apps

I would like to create a new Blackberry app and i dont know where to start... I have Visual Studio 2010 Ultimate installed and I was wondering if I could use it to develop BB native apps with it... or I should just go ahead and install Eclipse?? if so, I just went to eclipse.org/downloads and noticed they have MANY options... what do you guys reccomend??
thanks in advance
I've Windows 7 64 bit... should I get the 64bit version or 32??
It's also worth noting that I also have NEtbeans installed but just the php version
With regards to BlackBerry development I think that you will be better off with Eclipse, reason being that there is a BlackBerry simulator plug-in, which I do not think is available for other platforms (there was/is something for Netbeans, however, I never managed to get it work). You might want to take a look here. You should find all you need.
Lastly, with regards to your operating system, one of the major differences between the versions (32 and 64bit) is the amount of RAM you can access, so if you have more than 3Gb of RAM, then, you should get the 64-bit version, if you have less, then the 32-bit version will be just fine.
In order to start developing for eclipse , first you should download eclipse ide(you can select 32 bit version for windows) from eclipse web site , then you have to install eclipse blackberry plugin from blackberry site (you need to signup in order to do this), then its done you can start developing blackberry project from eclipse menu.Here is a blog post that i wrote.

Categories

Resources