Blackberry 10 Development - blackberry-10

I am developing an application in Blackberry 10. I have installed QNXMomentics for development, and Dev alpha Simulator for debugging. For running application in QNX need to specify the IP Addess from device or simulator. But on my simulator it does not showing the menu, Only the welcome screen is showing in the simulator , What the problem here

In context of your problem, Richard gives you idea about how to connect you simulator or device to your IDE you can find out one more option there is AUTO DISCOVER.
On startup of your loading your simulator on VM player their are two option for selecting screen type:
BB10DevAlfaKeyboard
BB10DevAlfaKeyboardSafe
Try 2nd option.
(*This setting for simulator debug only)
Your blackberry simulator device get stuck on welcome screen, I think this happens because of your PC hardware configuration little bit low, for first time it will take time
you have to wait till you didn't get HOME SCREEN of your BB Os 10 on your simulator.

On the simulator home screen, at the top, near the time you should see an icon that looks like a person with a gear inside. Selecting that icon will show you the IP addresses assigned to the device.

Or Run->Debug configuration...->Add new target->auto discover

Related

How Do You Diagnose MAUI Splash Screen Issues

I use a custom PNG for the splash screen in my MAUI app. It works fine on all of the IOS emulators I run the app on. It works fine on the Android emulator it runs on. However, when I connect my physical Android device to my computer and deploy to it, the splash screen does not appear.
I've tried looking at the device log, but there are literally thousands of entries in there which make it problematic for troubleshooting. What are the recommended debugging or diagnostic steps I can realistically use to track this down?
EDIT:
I managed to grab the device log entries during the splash screen loading and thought I would paste them here to see if anyone can make any more sense of what's going on. Here's a color coded version of it that I formatted in Excel:

iPhone 5 issue : random behaviour when debug mode is on

When I connect my iPhone 5 with xcode5, then on Iphone Home screen Tap long, after some time, its give worried behaviors. Sometime open any random app installed in my iphone, sometime open browser.
When run app, and press long, any random event occur like some time push new view controller,some time textfield becomeFirstResponder, some time any random keyboard value prees..
Is this OS issue ??
Its not related to xcode. I have noticed the same issue in OS apps as well. For ex. iMessage etc. Random keyboard were pressing.
Looks like OS issue. Quick way to resolve this issue is just restart you device and also upgrade your OS version to more stable version.

BlackBerry 10 Dev Apha Simulator Size Issue

I want to do some magic with BB. So I decided to go with BlackBerry Cascades. For that I downloaded Native SDK (772 MB) and Simulator (242 MB) and Photsjop plug in. I installed Native SDk and simulator and I opened the Simualtor in Vm.
Till here there is no issues., but when Simulator opens Size of Simulator is too large like there are scrollers to see the complete Simulator. How to fix the size of simulator with according to the vmware size.
I changed the Value in Controllers.exe, but it doesn’t get differences. So please let me know, how to solve this issue.
Hi You can resize you Vmware simulator according to your monitor screen size.following is the steps for that.
1. Go to where the simulator Vmware is installed (in my case: C:\Users\\Documents\Virtual Machines\BlackBerry10Simulator-BB10_0_06)
Go to the "controllers" folder
Run "controller.exe"
Select Connection > Connect
Type the simulator's IP address and press Connect (verify it says "Connected to 192.168.xxx.xxx" on the bottom of the screen)
Go to Device > Change Zoom Level; enter 40% or percentage then Apply.
Sometimes controller doesn't work as you expect.
I use following way to change simulator's zoom. Connect to the simulator using telnet with login/password devuser/devuser. Then put the command ves-zoom <zoom_value>
Where zoom_value is the percentage value of desired zoom.
Look at Simulator Configuring to clarify.

External Accessory Framework...EADemo issue

Exploring External Accessory Framework to connect iOS device via bluetooth. I downloaded Apple's EADemo project here: http://developer.apple.com/library/ios/#samplecode/EADemo/Introduction/Intro.html
But how do I test it? I'm new to XCode and Objective-C, so assume nothing. I opened the project file. I have it set to iPhone 5.1 Simulator at the top left. I click on the 'Product' menu...then I click on 'Run'. That opens the iOS simulator and it says no accessories connected. How do I get it to detect other bluetooth devices? If I go to general settings in the iOS simulator, bluetooth is set to off. If I move the switch to 'On'...it just spins and spins and spins and does nothing.
Can anyone help?
Thanks!
Yeah, you can't test EADemo with the simulator. Only works with actual devices.

iPhone simulator running invisible

iPhone simulator is running on my Mac but it's not showing the simulator. Two days back I had installed the Mac OS X 10.5.6 update. Xcode is launching the aplication in simulator, and it's running, as I can see the outputs on the gdb console window. But the simulator is not shown.
Try to remove ~/Library/Preferences/com.apple.iphonesimulator.plist
Had the same issue. The simulator was running somewhere way off screen. Could see it using expose, but couldn't move it.
Rather than using "Detect Displays", which didn't work for me, I changed the screen resolution and that popped it back into place.
Have you previously had an external monitor connected? Perhaps Mac OS X saved the simulator window off-screen the last time it was run?
In the System Preferences, select Displays and click the "Detect Displays" button while the simulator is running. That should force the simulator window to appear on-screen.
Nothing worked except the good old IT joke, Turn it off & on again! (Completely restarting the whole machine worked for me).