Thanks for the recs. I need Jabber, so ebuddy is out. I'll try slick. Hopefully on my N75 I can send at least a couple messages before the battery dies ;-p
I've tried Eqo, but their symbian client(beta) is buggy and doesn't work.
I'm thinking of trying Slick next, and maybe Gizmo5 after that since I don't really need VOIP or anything.
Battery drain is pretty much intrinsic to an IM app, isn't it? Having to remain online all the time is what's draining. Does EBuddy not do this?
not really because slick demands more for instance it shows when someone is typing to you, that alone tells you it never breaks the connection. Where on ebuddy i've seen times is would be from 3.5g back to 3g for like few minutes the go back to 3.5g so i dont' know if its checking to see messages every now in then but my batt don't die as much. but i dunno
not really because slick demands more for instance it shows when someone is typing to you, that alone tells you it never breaks the connection. Where on ebuddy i've seen times is would be from 3.5g back to 3g for like few minutes the go back to 3.5g so i dont' know if its checking to see messages every now in then but my batt don't die as much. but i dunno
IM protocols are not streamed.
When an IM client notifies you that someone is typing, it was generated by a single command. The client isn't getting streamed constantly. Slick doesn't support Jabber notification, so I imagine it only works on AIM/MSN? Also, each protocol is different on what it requires to stay connected. All of them don't require an active connection, but some require faster keep alives than others. The nice thing is that Slick talks *directly* to the IM servers instead of through some no-bodies gateway server system like all the other IM clients for S60.
eBuddy uses your web browser and Slick is an S60 app, so it really isn't the same thing. Slick could probably be doing some extra work that eats up power, because the network traffic should actually be *less* on Slick than using eBuddy, which uses HTML. The Slick developers need to run the new power app from Nokia and fix their app.
When an IM client notifies you that someone is typing, it was generated by a single command. The client isn't getting streamed constantly. Slick doesn't support Jabber notification, so I imagine it only works on AIM/MSN? Also, each protocol is different on what it requires to stay connected. All of them don't require an active connection, but some require faster keep alives than others. The nice thing is that Slick talks *directly* to the IM servers instead of through some no-bodies gateway server system like all the other IM clients for S60.
eBuddy uses your web browser and Slick is an S60 app, so it really isn't the same thing. Slick could probably be doing some extra work that eats up power, because the network traffic should actually be *less* on Slick than using eBuddy, which uses HTML. The Slick developers need to run the new power app from Nokia and fix their app.
Wow, that's fantastic info. I know the dev for Slick generally knows what he's doing, so I'm surprised it's inefficient power-wise, but the direct IM really is nice. Jabber works in the new version, too, but whenever the app is running, the connection icon stays in the online state, and battery drains as if I were actively browsing the web.
Reply With Quote
Originally Posted by william.gunn
Bookmarks