Craig Wiseman on December 20th, 2011 at 9:04 pm #
You go. Leverage those “user needs” to get your Traveler Widgets!
Nick Halliwell on December 20th, 2011 at 11:43 pm #
Tell Patrick that he should be working and not buying the very latest mobile phone, but its a very nice phone as is the Samsung Note.
Harald Gaerttner on December 21st, 2011 at 6:46 am #
That’s interesting – we have one guy with Android 4.0.1 and a samsung GT-I9000 with no problems.
We are now running 184.108.40.206 201111072101 (which is the one delivered with the 220.127.116.11 update) but he was also running it on our 8.5.2 without problems.
Wouldn’t have been surprised to see different behaviour between different vendor versions but here both are belonging to the Galaxy line.
Patrick on December 21st, 2011 at 8:06 am #
Oi Nick! If I do not sort out the issues, then some Executive will want the device(s) and IT will not be ready to support them. Just part of our process, although Marc does make me seem to be a bit of a consumer junkie.
Marc Champoux on December 21st, 2011 at 11:31 am #
Hi everybody …
Well, “Bad News Everyone”: even after doing this upgrade, we still get the HTTP 500 error on the Galaxy Nexus.
I notified Lotus Support… so I guess I’ll be spending some time on the phone with them. Oddly enough, I also have not yet been prompted to upgrade my Traveler version on my own Droid Razr phone… weird.
Thanks for all the comments!
Jai on April 14th, 2012 at 8:58 am #
Did you have any luck ? Have you been able to resolve the issue.
Post a comment