Debugging on the device?

Similar Questions

• Not be able to debug on the device

  Hi friends,

  I'm not able to debug device now. I have the same version of Simulator, sim even package version as I have on mobile. I've been able to debug a few minutes back, but I had not changed anything just removed app and new thought of debugging to display the value in another function. Even after removing the application, all objects remain in the persistent storage.

  Please help me

  Hi friends I am successfully able to solve. The only thing to do is to clean the Simulator, even if you want to debug on the device. Now, I am able to debug each time that the device suceesfully. Timeout paradigm for everything by retrieving the coordinates that we should create a timer so that elapsed, he should leave the idea of recovering the coordinates.

• Fastest way for debugging on the device of JDE

  Hi all

  I'm new to the development of BB and struggling to find a way to debug on device effectively.  My application has a lot of comm of bluetooth in him so most debugging should occur on the device instead of Simulator (please, correct me if this is not true).  Here's my development/debugging process.

  1. change the code

  2. generate the code

  3. the signal code

  4. connect device to Desktop Manager via the USB cable

  5. delete a previous version of my application

  6. load the latest version of my application

  7. connect to the device using JDE

  8. install a device app

  My quesitons are...

  1 should I sign the code whenever I have rebuild?

  2. is there a more effective way to get the latest version on the device instead of uninstalling then reinstall via Desktop Manager (it takes forever).

  There MUST be a better way.  Thanks in advance to all those who answer.  =)

  1. Yes, you sign cod every time after reconstruction you have for debugging on the device.

  2. you can load application in the device in various ways. If you use the Desktop Manager, you need to go if the steps you mentioned.

  But most developers use javaloader (JDE bin directory) to get the latest version in the device during development.

  To do this, run the following command from the bin directory:

  JavaLoader-u load applicationName.cod

  Also take a look at the article for details on loading the application on the device.

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800708/800647/How_To _...

  Concerning

  Bika

• Debugging on the issue of the device!

  Beginner again. My Java application with my new Plugin Eclipse 1.5.2 on win7/64 and loving debug so far and I have used a simulator 9330. I've implemented a new program feature that works fine on the Simulator, but when I Pack the app and deploy on a device 9330, it explodes with an error "index out of range". In order just to shoot this, I just use the option "Debug/Blackberry Device" and set breakpoints in the code of my program. This allows me to pass her and is very well. I found that the problem is on my side of the fence (code/design) but when I'm debugging on the device itself I do not see the values of the objects/properties, I get "

  " when I try to INSPECT an object.property.

  The big question: is it possible to debug on a device and see all the object.property values that scroll us? If yes how?

  Thanks in advance!

  Yes, it is possible but requires the files for your device BlackBerry OS .debug.  When you have started debugging you should have been prompted to download files of debugging.  Did you say yes to that?  If yes then automatically download the required files.  If you click on no, you will not be able to use debugging features.

• Debugging application on the device

  Hi people,

  I have 3 Questions for you:

  I have a weird on my application error, when I run it on the device of BB, but it's not when I do it on the emulator, I try debugging on the device (right click on the tree to approx. eclipse-> Debug as-> Blackberry device) then I get an error message indicating that the application must be signed.

  (1) I need I sign the application before debugging on the device?

  (2) I will pay the fees for signature keys. These keys are useful for all classes, signed? I mean, when I get the keys can I use any class signed?

  (3) which means that the PIN on the signed registration key?

  Thank you.

  Bruno.

  Yes, your application must be signed for debugging on the device.

  When you get the keys, you can use them to sign all your apps BB, as many times as you want.  Yes, they are good for all classes.

  The PIN in the registration form is a number YOU provide - make sure you save the number one safe place, that you will need when you get the key in order to activate them.

• Cannot launch the application on the device.

  Hello, friends

  I want to check my application on the device. I have correctly installed app on the device via the command but it doesn't start.

  I do not know what a question...

  I can verify any newspaper in the unit?

  Generate the debug of the device configuration and then debug directly on that unit is the easiest way.

  You can also the output of slog2info (via an SSH session) might give you an idea

• Launch application on the debugger device restarts the device

  I'm trying to debug an application on the device. I had some initial success, but lately that the machine restarts when the debugger tries to run the application. The application is installed, and I can run from the device after restarting the device, but so far I can't get it to work under the debugger.

  
  

  Configuration

  Feature: 9700

  OS: v5.0.0.602

  Eclipse: Galileo (3.5.2)

  BlackBerry Java plug-in: 1.1.2.201004161203 - 16

  BlackBerry SDK: 5.0.0.25

  -rich

  I think that I found a solution to this problem. I tried the suggestion to remove the application Options. Applications on the device. It turns out that it has not completely removed the application. Some library modules remained behind. I was able to remove these Desktop Manager. It is a bit heavy treatment, but it's me unblocked for debugging on the device.

  I hope that RIM will provide us with a better debugging experience in the future. It would be nice if the reset of the device were not necessary, but I guess that's in some scenarios. For the latter, the debugger must tolerate the delay in the connection because of reset. It would also be nice to be able to attach the debugger to a running application. IIRC, it was available in the old JDE SDK.

• Errorlog for application on the device

  is it possible to view a log of errors of the application once on the device?  My application does not work when the phone, but does on Simulator.

  Debugging on the device, by connecting the device to your IDE.  Sorry don't know how to do this on Eclipse, I always get this using the JDE, there is video that describes this process.

  You can view the error log by using the combination of keys ALT-L-G-L-G standard from the home screen.

  Sign here of the usual problems and level of operating system, make sure that the level of the OS on your device is > = your package JDE/component.

• Debbuging in the device (Pearl)

  Hello! I´d want to debug my application on the device instead of that we play on the Simulator. How can I do? When I try to launch the Eclipse debugger gives me the following message:

  number 1: File not found

  The 'net_rim_app_manager.debug' file is missing. Please select the missing file.

  I press on "don't ask again.

  Numer 2 Error

  Found no debug information for the module 'net_rim_cldc '. Several debugging features will not work correctly.

  This error pops up with the module: net_rim_os as well.

  Any suggestion?

  the version of the OS and the JDE must match exactly to enable live debugging on the device.

• Debugging the performance of the device with Java Plugin for Eclipse

  I'm trying to debug my application on the device running with the java plugin for eclipse (4.7), I've updated lately. The first eclipse of the done thing, ask my code signature password, then load the application on the device and the discovery of the time that the device is not connected, because she did a reboot after loading the application. How can I prevent eclipse from loading the application on the device?

  http://supportforums.BlackBerry.com/T5/Java-development/launching-application-on-device-from-debugge...

• debugging on the actual device different subversions jde - firmware

  I want to debug my code on a device connected via usb. I know that I need the same type in JDE and the device.

  For example, JDE 4.5-> device must have firmware 4.5.

  Although I checked the debugger tells me it can't find net_rim_app_manager.debug and many others. When I browse with browse for the files of simulator of the JDE debug files it is not like that and told me

  Bad debug information: \simulator\net_rim_app_manager.debug(4846a5e2)-net_rim_app_manager(494996a0)
  

  My regognizes JDE-attachment-device usb. When I ignore the mistakes I see some, but not all of the messages in the debug window. If the connection is ok.

  My firmware installed JDE Simulator Version DO match the firmwareversion of the unit BUT not the firmware-sub-version number. I mean the numbers after the second point (4.5.XXXX) is the reason for the error message?

  If Yes,

  -How and where can I get the EXACT match firmware-subversion for my device?

  -How can I do a real device debugging with the latest firmware?

  If none, I miss something else?

  my JDE:4.5.0

  my camera - 4.5.0.Simulator - JDE: 8310

  my JDE - 4.5.0.Simulator - Firmware: 4.5.0.44

  my real device: 8310

  my real device Firmware: 4.5.0.124

  Thanks for help

  Anil

  OK, after some research and debugging, I found the solution in this post

  http://supportforums.BlackBerry.com/Rim/Board/message?board.ID=java_dev&message.ID=3769&query.ID=266...

  a little summary here (including the above mentioned display comments). In this example, we assume that you are using JDE 4.5.0.

  • Check that you have installed the latest BlackBerry-Desktop-Manager. So you can be sure, that your device connected by usb is detected
  • Versions have to mach exactly! When you have the 4.5.0.102 firmware on your JDE-Simulator, you MUST have firmware on your real device 4.5.0.102. RIM provides many different simulators with a different firmware for debugging http://www.blackberry.com/developers/downloads/simulators
  • Install the corresponding correct Simulator and follow the Instructions of BB JDE 4.5.0 Guide Chapter development
    "Install the .debug computer files".
  • Connect your real device via USB
  • Compile your code in RIM JDE
  • If you use sensitive APIs-> sign your code
  • Load the cod files compiled on your actual device with JavaLoader.exe
  • Debugging-> attached to him-> Pocket-> USB ()
  • No, you can debug, breakpoints, out of the console, etc...

  Note: Although I have installed now the exact match versions. The debugger tells some files that it "does not find" them which is:

  net_rim_theme_120_green_320x240_b.debugnet_rim_theme_120_green_320x240_b-(1-13).debug
  
  net_rim_theme_120_today_320x240_b.debug net_rim_theme_120_today_320x240_b-(1-13).debug
  
  net_rim_bb_smime.debug
  

  I think that these debug files are relatively large for most applications, so you can ignore it.

  A good indicator to see that there is really a version mismatch is the first file, it cannot find "net_rim_app_manager.debug".

  Anil cordially

• Device debugging for the camera application

  Hello

  I would like to perform device debugging for my camera application.

  Problem is that my application seems to work fine on the emulator, but I do not get the desired result on the device.

  But when I try to debug the application I can't access the camera. Whenever I try to access the camera or any other multimedia file I get a warning that I need to first unplug the unit.

  Any suggestions would be very helpful.

  Thank you

  Saket

  Hi, if you want to access a file media, first of all, go to options > memory > mass storage Mode support > power off.

  and now try to debug your application.

  PD: Sorry for my English.

• Not able to make the device debugging on Blackberry pearl 8100.

  Hello

  I'm doing device debugging for 8100 and borrowed device via USB to the PC and attach a debuuger using JDE but the device no is not displayed under Debug-> attach to-> handheld.

  Thank you

  Odile Shorff

  Hi Mark,

  Thanks for the help I guess that the drivers had been corrupted, it uninstalled the Device Manager and put it back in place worked.

  Thank you

  Anne Laure Shroff

• Debug the device - missing .debug files - debugger does not slaughter

  Hello world

  I'm trying to debug on my bold 9700.

  If I attach the debugger to the jde to my device through debugging--> join to---> Pocket I can see debug messages in the output window of the jde. But the debugger does not stop at breakpoints also I get error messages while the debugger is endearing to the device. Missing files 'net.rim.cldc' etc.

  Searching the Internet has proved I have the specify a location where the debugger can find the ".debug" missing files.

  I hope someone can tell me where to download these files f *. I'm tired of searching...

  Thanks in advance

  Harry

  Hello. Debug files are provided with BlackBerry simulators, so you can install a BlackBerry Simulator that corresponds to your version of BlackBerry device software.

  BlackBerry simulators can be downloaded here: https://www.blackberry.com/Downloads/entry.do?code=060AD92489947D410D897474079C1477

  Best regards, Dmitry.

• The device Debug - cannot find the app after firing the debugger

  I develop for BB 9000 (bold), on the Eclipse platform. I have the eJDE 1.0.0.67 installed with the OS pack 4.6.0.19 and 9000 Simulator.

  Regular debugging works fine. The device is identified by the debugging options screen after connecting the usb cable. When you pull the debugger of the device, the camera screen whitens and displays the message "attach debugger". On the Eclipse console, I see that the device has been attached ("' attach: success '"), and I get the endless list of "no debug information is found for FOO". After that, the device display the clock again and nothing happoens. My App is not raised, and there is not anywhere on the device.

  The debugger however is attached, as I can see the list of threads running on the device, and I get all outputs from the regular camera journal.

  What I am doing wrong? How do I launch my application for debugging?

  the debugger does not start your application.

  If the OS on JDE and device versions do not match, you may not be able to use breakpoints.
  SYSOUT etc. is always available.