I recently updated a Domino server running Traveler on Linux 64 to 9.0.1. The Domino upgrade went off without a hitch. After much trying and searching for answers I couldn’t get the Traveler installer to run in either console or GUI mode. Finally opened a PMR to be told it was a known issue and would only install in silent mode.
One problem solved and another created.
It turns out there are a few glitches in Traveler 9.0.1. I discovered them when I tried to add a user to the Traveler server and it kept rejecting his credentials. As a test I opened a browser on the desktop and went to https://myserver.xxx/traveler. There the credentials were accepted but I got the message that the user ID could not be matched to a mail file!
Another call to support yielded another “known issue” and a hotfix. Haven’t gotten back to the user’s phone yet but the normal Traveler page comes up in the browser so I think we have resolution.
As part of my testing I noticed that the same “user ID could not be matched to a mail file” comes up on another Traveler 9.0.1 server running Windows 32 Domino. Fortunately the hotfix covers all platforms.
Hope this might help others.
After some false starts Blackberry is now rolling out BBM for iPhone and Android. Chris Miller did a good post on the details: http://www.idonotes.com/IdoNotes/idonotes.nsf/dx/setting-up-blackberry-bbm-for-ios-devices.htm
The good news: If you had BBM contacts who have switched to
the dark side other devices you can now reach them again.
The bad news: If you use multiple devices you can still only have one device associated to BBM at a time. You register the non-BB device using email address or Blackberry ID and then a PIN is generated for the device. So it seems BBM is still addressing a device PIN not a user.
As noted in my earlier post Blackberry 10 devices will only connect to Traveler over SSL (port 443). Our existing production server runs on port 80. When I posted this as an issue several people suggested that we should really run on SSL for security reasons.
I had never put up a Domino server with SSL/https enabled but decided to give it a try on a test server. I’m glad I did. Setting up SSL and the Domino Certificate Authority is not a lot of work but there’s a lot that can go wrong. It took me a couple of tries with IBM support on the line to get it working for behind-the-firewall access. Then I had to get my firewall folks to get me access from the outside.
But now I have my new Blackberry Q10 connected to Traveler 9. Mail, Calendar and Contacts all show up on my device. The initial sync took much longer than we typically see with iOS devices but once it was caught up I seem to get email on the device pretty much simultaneously with it appearing in the Notes client.
I’m still getting used to the Q10 and some tasks don’t seem an intuitive as they did on the old Blackberry interface, but I had many years to learn that. The Q10 is replacing a Curve with Blackberry 6 so it’s a big change even keeping the keyboard and many of the Blackberry shortcuts and conventions.
I got a long-awaited Blackberry Q10 from AT&T last week. My first reaction was disappointment. Before I could even start testing/playing/using I had to get past two big problems:
- The intent to connect the Q10 to our Notes Traveler server for email, contacts and calendar had to be put on hold. There is an unpublicized limitation where it will only connect via SSL, and we have our Traveler set up for http. This is fixable but a nuisance.
- I have a had terrible time closing application windows.
The gesture for closing a window is a swipe up from the very bottom of the screen. This is fairly important because there is no home button or other hard key navigation available on the Q10. I’ve found a quick flick from just to the right of the center of the top row on the keyboard seems to work most of the time, but it took me days to find the right motion, All of the other gestures work fairly reliably for me.
This leads into one source of disappointment. I was anxious to get a Q10 because I don’t do well with touch devices. This may be related to poor circulation in my finger tips. At any rate the prospect of having to type on a touch screen turns me off.
The hard keyboard on the Q10 is quite good. It’s slightly different than the Curve/Bold design but should be fine once I’m used to it. But as noted above there are no hard navigation keys — no home button, no escape button (the one I miss most), no menu button. You can set the power button to wake the phone from screensaver.
So the hard keyboard is a solution for typing but not for those who just dislike touch. There is a lot of touch control in Blackberry 10. And I’m really not having trouble with any of it except the close window gesture, but it’s not what I was expecting/hoping for.
Some other impressions:
I set up my Notes mail via IMAP. That seems to be working fairly well. I can also access iNotes Ultralite and that works quite well. The iNotes is important because IMAP does not handle calendar and contacts, just the email itself.
The Q10 comes with clients for most popular social media systems already installed. I set up my Twitter, Facebook, LinkedIn and Foursquare accounts. The navigation on some of these, especially Facebook and Foursquare is a bit odd. This is a shame since those services seemed to have finally fixed that issue for older Blackberries and iPhones.
Contacts on the Q10 was populated with all of my connections from those services. Of course in most cases that does not include phone number and work email.
The display is very nice, especially when compared to my Curve. The browser works well and seems to handle both standard and mobile pages.
Phone numbers anywhere on the device, even in web pages, are live and clickable to make a call. I don’t think any non-Blackberry device offers that, but iOS definitely does not.
I’m reserving judgement on the camera. The controls will definitely take some getting used to. Again, the camera suffers from not having physical zoom and shoot buttons.
Bottom line: The Q10 is not the device I was hoping for but it’s still the only true smartphone with a hard keyboard so I’m willing to take some time to try to make it work. Will post more if there’s more learning ahead.
Video can add a lot to a web page but it has some drawbacks. Just wanted to point those out.
- You can’t skim video to gauge relevancy, to find a juicy quote, or to skip to the conclusion
- Browsers on phones
- Harder to say “read the third paragraph” (Yes you can say “start at 48 seconds in” but it’s not the same)
- Can’t copy a juicy quote
- Visitors may have audio turned off or in use for other things
- Low bandwidth situations still exist (3G broadband cards anyone?)
- Visitor may not want to share your content with everyone in earshot
You get the idea. Make sure video will work for all your visitors all the time before you make it the only way to get content from a page. And seriously consider if having a video start automatically when a page loads is a good idea.