navigator_invoke and Dev Alpha

Similar Questions

• webkitVibrate works is not on the latest Webworks and Dev Alpha OS?

  My application uses the navigator.webkitVibrate function, which worked very well on the previous OS Dev Alpha as well as on the Webworks 1.0.2.9 SDK.

  I updated to 1.0.3.8 and also updated Dev Alpha, and now my app is broken. The vibration does not work. Any thoughts? Do you have this change or are additional permissions required in the config.xml file? Thank you.

  OK, I got a response from Github...

  It has been moved:

  navigator.webkitVibrate ();

  ... today is...

  Navigator.VIBRATE ();

  Name of the function changed. I did a text replace through all of the code in my application and recompiled, it doesn't! Thank you very much!!!

• No image appears on the Dev Alpha A

  Hello

  I deploy my application on the Simulator and Dev Alpha, but some picture big can not display on Dev Alpha but still works smoothly on Simulator.

  Someone tell my why?

  Seems real...

  Texture size max for Dev Alpha Simulator has been specified to be 8192 x 8192 pixels pixels.

  See this http://developer.blackberry.com/native/documentation/bb10/understand_the_blackberry_dev_alpha_simula...

  Maybe this isn't the case with real hardware.

  -Dishooom

• Audio dev Alpha C Cup using OpenAL

  Hello

  I have some problem with the audio on my device Dev Alpha C and I was wondering if anyone else has had or similar problems or that he might be able to offer a solution.

  The problem

  When you run our game on a device Dev Alpha C, after a short period the sound effects cut. After that no sound effects are played once again, apart from very occasional snippets of sounds, as the device is trying to play them but quickly to cut again.

  The strange thing is that the same code works fine on the Alpha of A Dev.

  Implementation

  The sound effects are implemented using OpenAL and OpenALUT.  Our music is played using the multimedia rendering engine (and works very well).  I checked for errors from OpenAL, but it is not everything.

  Our installation of OpenAL is quite simple and in fact is the following (note that I cut an error handling form all my code samples for brevity):

  if(alutInitWithoutContext(NULL, NULL))
  {
      device = alcOpenDevice(NULL);
      if(device != NULL)
      {
          context = alcCreateContext(device, 0);
          if(context != NULL)
          {
              alcMakeContextCurrent(context);
              alGenBuffers(MAX_SOUND_BUFFERS, buffers);
              alGenSources(MAX_SOUND_CHANNELS, sources);
          }
      }
  }
  

  Sounds are then loaded by:

  void *data=alutLoadMemoryFromFile(filepath.c_str(), &format, &size, &freq);
  alBufferData(buffers[bufferIndex], format, data, size, freq);
  

  (There are some parameters of sound parameters that I haven't posted because I don't think that is where the error but I can add it if it could be relevant to reprogramming).

  Finally the sounds are played using

  alSourcePlay(sourceNum);
  

  I use SDK 10.1.0.1020 and Dev Alpha C is on the firmware 10.1.0.138.

  If anyone has any suggestions, they would be welcome!

  On the problem of origin, was published a new firmware which seems to fix the problem. You can find it here: https://developer.blackberry.com/blackberry10devalpha/devalpha_update.html.  I tested it on our Dev C Alpha and it seems to work very well - I'm always test so will update if I have problems, but it seems OK so far.

  @beemaster - you might want to consider posting this question as a separate topic, as there is a good chance of people won't find it in this thread.  For what it's worth, we use MP3s in our game very well, even if we don't use of stunts and use the multimedia rendering engine to play, which could explain the observed differences.

• Impossible to test in app dev alpha A

  Hello

  I need to test in-app on my alpha dev A. I purchase followed all of the steps for testing in sandbox mode. But when I try to add the release that it does not show the option for alpha dev and so I get the "Not available for this device" message when trying to download app on app World sandbox mode.

  I need to test in-app. How can I do?

  I've just loaded Alpha-A Dev with the last external beta, 10.0.10.263 and was able to find and install downloaded applications only for Z10 models that dev Alpha was not as a device supported successfully.

  After making the changes on the supplier portal, it may take up to 6 hours for those on the device because of caching.

• installation bar on Dev Alpha: 810/var/tmp/bar_665560 failure: cannot access the Member "META-INF/MANIFEST. MF'

  Can someone tell me what in the world does that mean? Get this error when trying to install my application signed my BB10 Dev Alpha device. This error is new to me.

  I troubleshoot-made with Marco a little offline time. Here were the issues being not package and deploy properly, I hope this will help others as well in the future.

  The problem was just a few things.

  Config.Xml

  -Lack of ownership application in the widget element ID

  http://www.w3.org/ns/widgets"
        xmlns:rim="http://www.blackberry.com/ns/widgets"
          version="2.0.0.0" id="your_app_id_goes_here">
  

  Index.html

  -Lack a script include.  I always use the Web Inspector Network tab to make sure all my includes load.  It's amazing to see how many times I did it personally

  -Lack of script include the WebWorks JavaScript BB10.  Don't forget with BB10, we include this

  -Missing "webworksready" event listener.  In the case of Marco, that didn't alter his app, but we must wait for this event before calling WebWorks API now.

  Practical links

  Example of file config.xml blackBerry 10

  https://developer.BlackBerry.com/HTML5/documentation/code_sample_creating_a_bb_widget_config_documen...

  Examples of 10 blackBerry applications

  https://github.com/BlackBerry/BB10-WebWorks-samples

• Dev Alpha Red LED flashing (10111011) after update 10.0.6.545

  I upgraded my Dev Alpha 10.0.6.545 today and after the update has been done the WiFi is connected but when I tried to browse it wasn't working, so I decided to restart the device to see if, after this, it would work. When I tried to turn on the red light started flashing on the next in the sequence 10111011. I tried to repair the unit by using the Software Desktop 2.4.0 (version 16), which is the same one I used to update the Dev Alpha.

  He began to download the firmware to fix the device, but when it finished and started to install it collapsed it and wasn't moving forward for ~ 1, then I removed the unit and tried again (3 times) and it's the same thing.

  Any ideas?

  Seriously guys, 10 is my new lucky number. On the 10th try to repair it it fixed within 10 minutes.

  You must be persistent for Dev Alpha updated to work as much as I've seen it here by searching on the forums... haha

• BlackBerry Q10 Dev Alpha C - stuck on "essential gestures."

  Hey guys,.

  I accidentally placed an emergency call after loading the last 10.3 OS on my Dev Alpha C through the tutorial from gesturest. He asks me to swipe down from the top where the only option is 'emergency call '. I don't see a way to pass the tutorial of gestures to extinguish the GMS. Can someone help me out here?

  Okay, it looks like I had to do a battery pull and then just keep tapping the button 'try '. Finally he moved me to a screen where I could slip into an application and tutorial actions. Huge PITA, but I hope I am the case of edge here.

  Rion

• BB 10 Dev Alpha Simulator 10.1 beta - screen resolution

  I couldn't get my Android app BAR file to install on the current version of the BB 10 Dev Alpha Simulator (10.0.10.261) so I tried to install the Beta 10.1 Simulator and my app installed first and short big.  The only problem is the screen seems to be much smaller than the 10.0.10.261 version, I read in the release notes that the resolution is only 720 x 720.  Is it possible to change this?  Or can we expect a resolution screen than the final version?

  Thank you

  Jonathan

  I realize now it's the resolution for the upcoming phones of the physical keyboard BB10 (X 10).

• .swf continues to play (Dev Alpha)

  Hey guys,.

  I am a web developer and this is my first Blackberry + AIR experiment.

  I used to implement the .swf into an html file and compile it by webworks, but I discovered that there is another way using the AIR SDK.

  So, I followed the guides online, downloaded the SDK and created 2 .xml files.

  Then I put my .swf in the folder of my project as well.

  Then, I used the GraphicalAid to generate the .bar file.

  During installation I got ' the result::failure 881 application author does not debug author token "which is not the case. However I just sign and then test it in my Dev Alpha camera.

  Here is the new issue:

  The .swf appears as it should, but he continues to play and repeat so as there is no stop() in my actionscript.

  This does not happen in Chrome and it is not yet using the WebWorks method and the older generation of Blackberry 10.

  Maybe there is something wrong with my xml? Here are the parts of my project.xml:

  2. Game.swf
  3. GPU
  4. fake
  5. true
  6. true
  7. fake
  8. fake
  9. fake
  10. standard
  11. fake

  Help me please guys, I don't know what to do.

  Best regards

  Flo

  Yes, it works only for AS3. I'll look into if this is the expected behavior.

• BlackBerry 10 Dev Alpha is not updated to 10.1 to 10.2

  I'm trying to update my device BlackBerry 10 Dev Alpha OS 10.1 to 10.2. I'm refernce documentation for it. I downloaded Autoload-DevAlphaC - 10.2.0.1157.exe try to update. But the command line stops without updating. Then I tried with loading auto-DevAlphaA_B - 10.2.0.1157.exe. Here he updates without any error in the command line. But the device does not start after that.

  Then, I go down to the previous version of the OS using the load auto-DevAlphaA_B - 10.1.0.1485.exe. Now the unit start with OS 10.1

  Why is this happening?

  I don't think that Dev Alpha (A) could be upgraded to version 10.2. I have tried both official and leaked OS but neither can start the device again. So currently my Dev Alpha holds only still 10.1.1485.

  If you really want to try 10.2, try using Dev Alpha B/C or official Z10/Q10.

• After wiping Dev Alpha, it gets stuck

  I recently installed the updated BB10 with the hub. I found that something was wrong with the update that I couldn't connect to BBID little matter what I tried. So, I did a cleanup of security of the device.

  Now when it restarts, it shows a litte with a USB phone to a computer. When I plug it into the USB or the phone or the computer acts as something that happened.

  If I don't touch it, the dev alpha turns off, then when I turn it on again, same thing the usb screen. I need to finish a few apps and test them, I don't know what to do. Can someone help me?

  The automatic charger for Windows and connect the device to the computer windows using a US cable. Run the automatic charger. It starts by itself. If this isn't the case, keep the button of the unit alpha dev for at least 15 seconds.
  The autoloader should now be able to connect to the romantic boot and start updating your device and wipe all content.

• Dev Alpha Crash

  Hi all. My Dev Alpha had five crash in two days... If stay an hour standby... accident!

  I had install only two Apps...

  Help me!!

  

  Can you be more specific as to what 'crash' means?

  This term generally refers to a situation where a program ends abnormally, usually with a visible error or exception dump core any.

  Most (all?) of us with Alphas is certainly another problem frequently, where the touchscreen unresponsive and the camera seems to be frozen.

  Often this occurs at startup, and you need to reset or reboot several times (4 - 5 times) before you can get it to respond.

  Is your 'crash' simply a case of the unit "locking up" like that? If so, I doubt, that there is nothing you can do to improve the situation, with the exception of waiting for the update.

  I let mine all the time now (connected) simply to reduce the probability of what happens, even if I am not sure it helps.

• BB10 dev alpha - stuck in Configuration - does not load the license agreement (r2320)

  I successfully upgraded Dev Alpha A 10.0.09.2320 with automatic charger.

  Device, rebooted, installed new drivers, etc etc, all the other things worked well, BUT

  The device is unable to complete the installation, because it gets stuck on the license agreement page.

  I am connected to wifi. The wifi works. It's worked before. It won't let me even to select a country, it shows an error that the network does not, repels me a page, and I have to disconnect / reconnect to wifi before it allows me to 'sweep left to continue' again.

  Any suggestions?

  I managed to make it work by (sigh) with the help of roaming data connection (after restart). Now it is stuck on the screen of a software update. He has rightly "Software Update" and nothing else on the screen. The Act of working is the Emergency call.

  Update: after another reboot, after you turn off roaming data once again, it gave me an option to start or turn off the phone, but it says something about "blackberry infrastructure? Does this mean that it will work only with BlackBerry Internet Service in the future?

  Edit: so bad, yet another restart that he lets me actually left-scan-ignore the update of the screen without anything do. Sorry for the false alarm, I'll leave it here for anyone to find.

• Momentics Login password for the Dev Alpha BB10 problem

  Hello.

  I deploy my applications dev alpha BB10 using debugging tokens. Device is in development Mode. Computer detects the device. Debug a valid token. Password is defined.

  Question: Quick refuses my password, says that it is "invalid". Does not record.

  However, when I deploy, I started having a "quick Login". When I enter the same password, it says it is invalid.

  I feel

  (1) Momentics crash or config file is corrupted and not to recognize what I type in

  (2) something else?

  Everyone knows about this problem? Do you know a fix?

  Thank you.

  Restarted my computer and it worked!