Quote:
Originally Posted by danmcf321
I posted a support case on Freedom Inputs support site, but have not heard back from them yet. It's only been a couple of days, but I really need to get this worked out. Here's my situation:
I run a Blackberry Enterprise Server v4.1 and am trying to load the Freedom input drivers on a Blackberry 8320. I set up a wireless push install point on a server for the Freedom Input software. The app never seemed to be pushed (which I am not that concerned about as I had a similar problem with another wireless app before). I then tried to install it through the desktop manager. When I browse to the share point on the BES, and try to load the application btkbd42.alx. I receive the following error: "No additional applications designed for your device were found".
I think the install point is OK. I loaded the software on my Pearl 8100 from the install point and the Freedom Universal worked with out a problem.
I then tried to install the software OTA, which installed the software and paired with the Freedom Universal, however I receive the keyboard injection error due to my BES policies.
I think what would be the best fix would be to be able to install from the Desktop Manager off of my installation point. Does anyone have any ideas, or know of anyone at Freedom Input that I can contact?
Thanks,
Dan
|
Hi Dan,
If you want to PM me the Ticket number I can take a look for you. I thought I would respond directly here as well as there are a couple of things in the reply that might be useful for others as well.
The problem with the software not pushing to the handheld is due to the BES not having the hardware ID for the newer BlackBerry's (it was a lot of fun discovering this with a company that had just bought a bunch of keyboards for their employees Curves.....).
Take a look at the BlackBerry KB article linked below for more information on this:
BlackBerry Search Results
With the OTA install it is possible that the version you have on the handheld from the OTA site is a different version to the one that is set up on the BES. This means that in effect the BES see's it as different software so the software configuration you made would not apply to it.
I'm not sure why it wouldn't let you install it from the desktop manager though. The only thing I can think of is that it either didn't see the .ALX file or that it thinks the keyboard drivers are already installed (could be possible given the above bug with wireless pushes from the BES to new handhelds).
Two things to try are fixing the hardware ID issue on the BES, removing the OTA drivers and then having the software pushed from the BES
Also on a lot of 4.2 devices you can just change the settings on the handheld regardless of how it is set on the BES (does depend on exactly how everything is set up). Have a look at the link below for more info:
Keystroke Injection Settings "Trackball" - Powered By Kayako SupportSuite
PM or email me the ticket number and I can respond directly if you are having any more problems.