Fastest way for debugging on the device of JDE

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.

• 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.

• Debugging on the device?

  Newbie here. I'm finally able to debug on a real device, 9330 which shows:

  6.0 bundle 2333 (v6.0.0.524, platform 4.4.0.438)

  I write apps targeting the 5.0 SDK. I guess from the above that the camera itself is version 6.0.0.524, is this correct?  So where can I get the specific Simulator for this?  None of the 4 last digits Curve 9330 simulators match. (I am trying to eliminate all the 'cannot find debug file"nonsense!) is there any detailed white papers on debugging on the correct device?  Also, I try to use Eclipse.

  Thanks in advance!

  All available BlackBerry smartphone simulators are available for download here: http://us.blackberry.com/developers/resources/simulators.jsp

  It may not be a release of Simulator for all versions available for download.  But we are always adding more, so you can keep an eye on this page for updates.

• Looking for wifi on the device icons.

  Hello, I am trying to access the icons used for the wifi on the device. I am referring to those who get green lines depending on the power of the PA (with or without a sign of blocking). Any idea where we can get?

  I think that the device are more active that were previously accessible as well. I have attached those you are looking for (I think) as a zip, got all the icons of 1846 while they were still there

• What is the best way to detect if the device has a touch screen?

  How do detect you if a device has a touchscreen with version 4.7 of the OS?  With the upcoming 9630, that I need to know he can't stand not touch.  Thanks for the help.

  ~ chris

  No Touchscreen.isSupported () not doing it for you?

• authentication open for debugging of the aaa on Powerconnect

  Hello

  We put in place of the switches to use RADIUS. In order to check if all clients authenticate as we think they do, it would be nice to issue a command as they have in Cisco switches "open authentication". This allows 802. 1 x do its work, but allow the customer through anyway. In this way, you can see if the 802. 1 x has failed or succeeded, without worrying about end users.

  Is there a similar function in Dell Powerconnect?

  Concerning

  Kjetil

  I looked through several different options to see if the switch can be manipulated to perform the same action as the open authentication, but I couldn't find a way. I thought that the computer-vlan command would work. But with that VLAN must be different from the authenticated VLAN.

  Page 508 of the user's guide has a detailed example that you can follow.

  http://Dell.to/1HL2Rmk

  Expand each step you need to take to implement. Then during the hours full no implement and test. Be sure to have a backup of the current configuration.

• Skype and Surface Pro - can I activate microphone for Skype, but the device is off?

  I would like to use Skype but don't want the camera on.  I can only find a place to allow the use of both at the same time.  Is there one place other than the camera app where I can turn off the camera?

  Hello

  My problem was that in the camera app and the Skype app is given to the microphone and camera at a time.  I did talk about today with support Surface and found that have the permission to the camera application turn off continue to allow the microphone to work in the Skype app without having to worry about the camera.

  I did follow your advice as well and now know where to go for my personal use.

  Thank you!

• How to fix a sound problem - reading devices no. for the Device Manager on WinXP SP3?

  (1) I can't to Device Manager by following the guide for help on my system.  The steps do not match what is actually showing me my Windows and I can not here the only way I can get to it is to use a link on the help page directly.  Even when I do that, the steps in the help guide still do not match what I see on MY screen.  Is this perhaps an update of this Guide to match my system?

  (2) I need Device Manager to find out what happened on my Audio device.  I have no sound from my speakers.  It happened all of a sudden when my wife was using the computer.  I don't know what she can do both.

  Start/Settings/Control Panel / sounds and Audio Devices Properties shows "No. Audio Device", hence "Volume of the device" is gray.  Audio tab displays 'No peripheral to read '.

  The fastest way to bring up the Device Manager is:
  Start-> Run-> "devmgmt.msc".
  If it detects the sound equipment, but there is a problem with a driver, you will probably see a yellow "!" appears by your audio device.

  If he was working and stopped, you can try to perform a "System Restore" to a point where it worked:

  "How to restore Windows XP to a previous state"
    <>http://support.Microsoft.com/kb/306084 >

  HTH,
  JW

• 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.

• 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.

• Build for the success of peripheral liberation but build for debugging device failed

  Hi, I have created new project with the new SDK of my previous old SDK which is already can build release and debug of the device device.

  I'm just copying the file in the src folder and active and made the minor change due change of myApp.cpp to applicationui.cpp

  (I'm doing this because when create export release build, the size of .bar .bar file is big - I'm already the clean)

  When I build this device release is success but for device debugging failed.

  The error is:

  make: * [Device-Debug] error 2

  make [1]: * [debug] error 2

  make [2]: * [o.le - v7-g/myApp] error 1

  How to solve this problem?

  Something I forgot? or things usually cause this?

  Thank you

  Ah I found the solution.

  Must add the .pro file:

  LIBS +=-lbb

  Maybe on the old SDK don't project any need to add this, but the new SDK project may need this (I don't know). But after that I added this on my .pro, the success of my project build on the device debugging.

  Thank you

• Re-install the symbols for debugging after automatic update OS

  Hey. It's just a word for someone else who has their device automatically updated the software (OS).

  For me, after an automatic update, I had to reinstall the debug symbols in Momentics (2.1.1) for debugging on my device (small BONES change invalidates their). It's a long download.

  So I put my settings-software updates-Options-automatically download and install software updates on Off.

  If I leave, let me know pls.

  See you soon

  Justin D.

  Yes, this is normal behavior. debugging symbols must match the version of the OS.
  You can compile and run applications without them, but debugging is not possible.

• 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.

• Use Preview on the device for Android on Mac - how to operate?

  We use an excerpt on iPad via USB connection on daily basis, but now we need a preview on Android as well.

  I tried the Setup program on the next page, but it does not work for me - I have USB debugging active (it is well hidden on Jelly Bean 4.2.2 on our Nexus 7), but I can't see device in Panel Folio Builder in the Preview menu (Yes, I have Adobe Content viewer as before app)

  http://help.Adobe.com/en_US/digitalpubsuite/using/WS9293e1fb3b977c5c7b1f65ad12f28224932-7F f6.html

  any idea, experience?

  Thank you

  Martin

  Quick search on googled around seems to me, this problem IS in the tools of DPS. They contain too old version of adb, 1.0.26. Accroding to the present notes that you should spend for ever:

  Note: When you connect a device running Android 4.2.2 or later version on your computer, the system shows a dialog box asking if you accept a RSA key that allows debugging through this computer. This safety mechanism protects user devices because it guarantees that USB debugging and other adb commands cannot be executed unless you are able to unlock the device and recognize the dialog box. This requires that you have adb version 1.0.31 (available with the SDK Platform-tools r16.0.1 and higher) for debugging on a device running Android 4.2.2 or higher.

  From: http://developer.android.com/tools/help/adb.html

  As I wrote in the first post, I have the Nexus 7 with 4.2.2... So if you want to provide an excerpt on device on Android, you must upgrade adb tool in the tools of DPS.