IBM/Lotus Traveler on 4.2 misbehaving

[DaveyBoy]

Apologies if I've posted this in the wrong place. I'm a first time poster on android central, though as a webOS "refugee" I'm a long-time user of mobile nations.

Anyway, I got a second hand Samsung S2 as a backup phone, since I refuse to go Apple, and my main phone's days are numbered. My employers use Lotus Notes, making Lotus Traveler available for mobile devices, and on my Pre I've been able to use this to integrate my calendars all into one through EAS, as well as integrated mail and contacts. However trying the same thing on Android isn't giving me anywhere near the same experience.

First off, the stock ICS installed on the phone refused point blank to even talk to the Traveler server. So, since the phone is out of warranty anyway, I loaded up another ROM (I chose JellyBam - I realise it's controversial) and after installation I could create a "Corporate" account and use the email app. However, while I expected it to take control of the phone's security, I didn't expect it to incessantly request me to update my PIN/password. It's every couple of minutes and it's driving me crazy. It's also extremely picky about which appointments it syncs. And sometimes it just stops syncing completely and I have to delete the account and start again. I tried the Lotus Traveler app, but that was worse - not only does it not integrate the calendar, but it keeps on downloading a new copy of itself every few hours eating into my data allowance. I have tried another couple of ROMs and had exactly the same problem, so it's not just JellyBam

I did pose the problem to my company's helpdesk, but Traveler is provided purely as-is and no support is given - so if it doesn't work, then hard cheese.

Does anyone here have any knowledge of this, or maybe things I can try to get things working smoothly. While I'm a novice in android, I'm not a complete tech no-nothing (a webOS user can't afford to be!).

Thanks in advance.

 

[dwtc]

I set up Traveler on my Galaxy S2 (running CM10.1 nightly builds), and every few hours it would forget my password and erase everything that it had previously synced and it says for a while that it can't connect to the server. When I put my password back in it would re-sync and work fine for an hour or so, then forget the password again. All the re-syncing takes a toll on the battery (and uses a lot of data), not to mention it's pretty damn inconvenient to have to re-sync every hour just to be able to see your email/calendar.

I went back to the stock Samsung/AT&T firmware (ICS), and it's mostly working very well, except that the mail & calendar widgets don't refresh to show new mail very often at all, so I don't use them.

But I miss CM10.1, so I'd love to figure out how to make that work with Traveler. I'm not sure if it's the fact that I was using 4.2, or if it was because it was a 3rd party ROM or if it was because the phone was rooted. I think I'm going to try rooting my phone and see if rooting breaks it. Then I'll probably create a nandroid backup and try CM again.

I'd love to know if anyone can tell me if rooting or 3rd party ROMs will screw up Traveler. Maybe the server administrator can specify parameters, like not allowing rooted devices or something. I know that the Traveler app hasn't forced me to use a PIN or password or anything.

 

[InfinitiGuy]

My rooted Nexus 4 with CM10.1 Nightly works fine with Traveler. Junos Pulse just gives me a warning every week that my device is rooted but doesn't affect anything.