Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Highlighted
Regular Contributor
Posts: 75
Registered: ‎10-19-2011
My Device: Developer
My Carrier: verizon

Test app won't run/debug on 8530 device

I am currently running Eclipse Plugin 1.5.2 on a win7/64 machine. I have built a simple project as a 'Hello Blackberry' project and am targeting Blackberry JRE 5.0 so that it will run on 8530 devices. I have downloaded simulator 5.0.0.337 Verizon which exactly matches my physical device. This quick sample app runs fine in the simulator but will NOT run on the actual device in the following two cases:

 

1. Load Project to Device. If I load the project directly to the device, I see the transfer display and the app is placed in the Downloads folder. When I click it I get and error dialog "module handle 8981 not found"

 

2. Debug Project. If I place a break point on the first instruction in Main() and then navigate 'Debug\Blackberry Device', I get the white screen with 'debugger attaching'. Eventually everything settles down. I go to the Downloads folder and click the app icon. Eclipse Debug preferences throws up a new tab labelled 'CodeModuleManager.getManagerData... line 1238'. The following appears on the console:

 

External Bundle: 'C:/Eclipse/BB_EclipsePlugin_1_5_2/plugins/net.rim.ejde/vmTools\BundleInfo\4ae69c9a.jar'

No debug information found for 'GoogleSearch' (4bbb9ac9).

No debug information found for 'GoogleSearch-2' (4bbb9ac9).

No debug information found for 'GoogleSearch-1' (4bbb9ac9).

No debug information found for 'GoogleSearch-3' (4bbb9ac9).

No debug information found for 'GoogleSearch-4' (4bbb9ac9).

No debug information found for 'GoogleSearch-5' (4bbb9ac9).

No debug information found for 'GoogleSearch-6' (4bbb9ac9).

No debug information found for 'GoogleSearch-7' (4bbb9ac9).

No debug information found for 'GoogleMail' (491d9cb8).

No debug information found for 'GoogleMail-3' (491d9cb8).

No debug information found for 'GoogleMail-1' (491d9cb8).

No debug information found for 'GoogleMail-4' (491d9cb8).

No debug information found for 'GoogleMail-2' (491d9cb8).

No debug information found for 'GoogleMail-5' (491d9cb8).

No debug information found for 'GoogleMaps' (4bc62faf).

No debug information found for 'GoogleMaps-3' (4bc62faf).

No debug information found for 'GoogleMaps-10' (4bc62faf).

No debug information found for 'GoogleMaps-4' (4bc62faf).

No debug information found for 'GoogleMaps-8' (4bc62faf).

No debug information found for 'GoogleMaps-9' (4bc62faf).

No debug information found for 'GoogleMaps-1' (4bc62faf).

No debug information found for 'GoogleMaps-2' (4bc62faf).

No debug information found for 'GoogleMaps-6' (4bc62faf).

No debug information found for 'net_rim_bb_appworld' (4ca51bad).

No debug information found for 'vvmail_8530' (4cbe8915).

No debug information found for 'vvmail_8530-6' (4cbe8915).

No debug information found for 'vvmlib_8530' (4cbe8912).

No debug information found for 'vvmlib_8530-1' (4cbe8912).

No debug information found for 'vvmail_8530-7' (4cbe8915).

No debug information found for 'vvmail_8530-8' (4cbe8915).

No debug information found for 'vvmail_8530-1' (4cbe8915).

No debug information found for 'vvmail_8530-2' (4cbe8915).

No debug information found for 'vvmail_8530-3' (4cbe8915).

No debug information found for 'GoogleMaps-7' (4bc62faf).

No debug information found for 'GoogleMaps-5' (4bc62faf).

No debug information found for 'GoogleMaps-11' (4bc62faf).

No debug information found for 'GoogleMaps-12' (4bc62faf).

No debug information found for 'GoogleMaps-13' (4bc62faf).

No debug information found for 'GoogleMaps-14' (4bc62faf).

No debug information found for 'GoogleMaps-15' (4bc62faf).

No debug information found for 'GoogleMaps-16' (4bc62faf).

No debug information found for 'GoogleMaps-17' (4bc62faf).

No debug information found for 'GoogleMaps-18' (4bc62faf).

No debug information found for 'GoogleMaps-19' (4bc62faf).

No debug information found for 'net_rim_bb_appworld-4' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-6' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-7' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-5' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-8' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-9' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-10' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-11' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-1' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-3' (4ca51bad).

No debug information found for 'net_rim_bb_appworld-2' (4ca51bad).

No debug information found for 'net_rim_bb_appworld_barcode' (4ca51b9f).

No debug information found for 'vvmail_8530-4' (4cbe8915).

No debug information found for 'vvmail_8530-5' (4cbe8915).

No debug information found for 'LSPBestFLASH' (4ba8304d).

No debug information found for 'LSPBestFLASH-1' (4ba8304d).

No debug information found for 'VideoFlashlight' (4b8fd927).

No debug information found for 'bStrobe' (4b989c50).

No debug information found for 'net_rim_bb_facebook' (4af469eb).

No debug information found for 'net_rim_bb_facebook-3' (4af469eb).

No debug information found for 'net_rim_bb_facebook_lib' (4af469dd).

No debug information found for 'net_rim_bb_facebook_lib-1' (4af469dd).

No debug information found for 'net_rim_bb_facebook-4' (4af469eb).

No debug information found for 'net_rim_bb_facebook-7' (4af469eb).

No debug information found for 'net_rim_bb_facebook-1' (4af469eb).

No debug information found for 'net_rim_bb_facebook-2' (4af469eb).

No debug information found for 'net_rim_bb_facebook-5' (4af469eb).

No debug information found for 'net_rim_bb_facebook-6' (4af469eb).

No debug information found for 'net_rim_bb_facebook_resource_large' (4af46a7a).

No debug information found for 'net_rim_bb_facebook_resource_large-1' (4af46a7a).

No debug information found for 'net_rim_bb_facebook_resource_large-2' (4af46a7a).

No debug information found for 'net_rim_bb_facebook_resource' (4af46a7d).

No debug information found for 'net_rim_bb_facebook_resource-1' (4af46a7d).

No debug information found for 'net_rim_bb_facebook_w_help_en' (4af46ad2).

No debug information found for 'net_rim_bb_facebook_help_en' (4af46a1b).

No debug information found for 'net_rim_bb_facebook_resource_en' (4af46a8d).

No debug information found for 'vvmlistener_8530' (4cbe891a).

No debug information found for 'net_rim_bb_appworld_barcode-1' (4ca51b9f).

No debug information found for 'net_rim_bb_appworld_resource_en' (4ca51be1).

No debug information found for 'SecurIDLib' (456c5107).

[0.0] VM:-DA 0

[0.0] attach: success

[0.0] JVM: bklt @243357609: timer

[0.0] JVM: bklt[1] @243357609: idle 10

[0.0] JVM: bklt @243357609: setTimer 5

[0.0] CMM: Test8530(9025) no sig from 0x33

[0.0] VM:NCICv=25

[0.0] VM:NFICv=5

[0.0] VM:NFICv=4

[0.0] VM:NFICv=8

[0.0] VM:NFICv=7

[0.0] VM:NFICv=6

[0.0] Starting net_rim_process_launcher

[0.0] Started net_rim_process_launcher(217)

[0.0] Exit net_rim_process_launcher(217)

[0.0] Detected background switch for net_rim_process_launcher(217) who has NO tunnels open - defocus NOT c[0.0] alled

[0.0] JVM: bklt @243362375: timer

[0.0] JVM: bklt[1] @243362375: idle 15

[0.0] JVM: bklt @243362375: setTimer 15

[0.0] CodeStore.DependencyList.reset() - Cannot find handle from name net_rim_data_provider_resources__en

[0.0] CodeStore.DependencyList.reset() took 14626

[0.0] CodeStore.DependencyList.buildModuleDependencyList() took 12 - [168]

[0.0] FocusHistory: Focus lost; App net_rim_bb_clock; Component net.rim.device.apps.internal.clock.ClockSc[0.0] reen

[0.0] Foreground net_rim_bb_ribbon_app(95)

[0.0] Detected background switch for net_rim_bb_clock(123) who has NO tunnels open - defocus NOT called

[0.0] Detected foreground switch for net_rim_bb_ribbon_app(95) who has NO tunnels open - focus NOT called

[0.0] FocusHistory: Focus gained; App net_rim_bb_ribbon_app; Component net.rim.device.api.ui.MediaControll[0.0] er

[0.0] JVM: bklt[1] @243373265: JvmBacklightSetTimeout 30

[0.0] JVM: bklt[1]: setTimeout 30

[0.0] JVM: bklt @243373265: timer

[0.0] JVM: bklt[1] @243373265: idle 0

[0.0] JVM: bklt @243373265: setTimer 15

[0.0] VM:NCICv=0

[0.0] VM:NCICv=30

[0.0] FocusHistory: Focus lost; App net_rim_bb_ribbon_app; Component net.rim.device.api.ui.MediaController[0.0]

[0.0] FocusHistory: Focus gained; App net_rim_bb_ribbon_app; Component net.rim.device.apps.internal.ribbon[0.0] .launcher.RibbonIconField

[0.0] FocusHistory: Focus gained; App net_rim_bb_ribbon_app; Component net.rim.device.apps.internal.ribbon[0.0] .launcher.RibbonIconField

 

Can anybody point me in the right direction on determining what the issue is and how to correct? Essentially I am trying to build app(s) that target the 5.0 platform and I need to be able to debug the app(s) in Eclipse while connected to the device. I'm sure it's something simple but I'm stumped.

 

Thanks in advance

 

 

Developer
Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: Test app won't run/debug on 8530 device

Are you actually compiling for 5.0, not 6.0 or 7.0?

 

Your compiler level must be <= the target OS level.

 

Regular Contributor
Posts: 75
Registered: ‎10-19-2011
My Device: Developer
My Carrier: verizon

Re: Test app won't run/debug on 8530 device

Hmmm, I a newbie on this topic. I checked the Java Compiler Properties for the project and the JDK Compliance Group shows the following:

 

Compiler Compliance Lever = 1.3

 

Checkbox 'Use Default Compliance Settings' is checked.

 

The following are disabled:

 

Generated .class file compatability = 1.1

Source Compatibility = 1.3

Disallow identifiers called 'asset' = ignore

Disallow identifies called 'enum' = ignore

 

I'm not sure how to interpret your "<=" statement, e.g. how do I compare compiler lever 1.3 to OS 5.0?

 

It does run successfully on the 8530 simulator though.

 

Developer
Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: Test app won't run/debug on 8530 device

The BB JDK level is what I am referring to, not nec. the Java compliler compliance level.

 

JDK 5.0, JDK 6.0, etc. This value must be <= the target OS level.

Regular Contributor
Posts: 75
Registered: ‎10-19-2011
My Device: Developer
My Carrier: verizon

Re: Test app won't run/debug on 8530 device

Well, in the project build path I show a BB JRE 5.0 (not JDK). Is this just a nomenclature issue?

 

Also, I am working directly with RIM as I am paying for an 'support incident' on this issue. They are somewhat surprised at this and believe it to be an OS issue. The problem arises when an artifact is removed when deleting the old app. For example, I can manually delete the app by either the context menu option on the app icon in the download folder or by the Options\Applications function. 90% of the time, either delete operation does NOT remove the icon from the download folder. What should happen is that the operation is supposed to reboot the phone which completes the delete by removing the icon. If I do a battery pull, the phone reboots and the icon is removed. Only in 1 out of 10 has the delete operation initiated the reboot.

 

I'm still curious about the JRE/JDK nomenclature above. Maybe I've included something I shouldn't have?

 

I'll post my final results with RIM when resolved. Thanks!