The official blog on Trillian development.
Trillian for Android: LED improvements, BiDi support, fixes! (1.0 Build 137)
Next up in today’s updates is a refreshed build of Trillian for Android. As with today’s BlackBerry update, Trillian for Android now receives much-improved support for bidirectional scripts. We’ve also fixed a handful of the remaining quirks that have been reported and believe we have finally resolved the issue preventing the LED from working correctly. You can now pick from a handful of supported LED colors to help notify you of newly-received messages. The new beta is available for direct download and will be made available through auto-update shortly.
Finally, we’ve also released a new version of 4.2 to address an ongoing ICQ connection issue. If you’re a user of 4.x and are experiencing problems, please visit our download page to get the new build and let us know if it resolves your issue. We’ll be rolling this fix into the next 5.0 build as well.
Enjoy the build!
November 2nd, 2010 at 9:41 pm
Nice! Keep up the good work guys! I’m trying to get my Evo friend onto Trillian
November 2nd, 2010 at 10:13 pm
Great work! Trillian is the chat app I use daily. You guys plan on adding push notifications (C2DM)?
November 2nd, 2010 at 11:32 pm
Any plan for msn file transfer feature?
November 3rd, 2010 at 1:09 am
@Ownatik – Yeah, they are, a couple builds ago.
November 3rd, 2010 at 1:23 am
At least one good thing came of november 2nd, 2010
November 3rd, 2010 at 8:37 am
e! Keep up the good work guys! I’m trying to get my Evo friend onto Trillian
November 3rd, 2010 at 10:43 am
Awesome! Each update feels like Christmas all over again!
November 3rd, 2010 at 12:16 pm
What should I do to activate Push? When I am suspending Trillian I’m never getting any notifications on new messages
November 3rd, 2010 at 1:54 pm
@m106 – To enable C2DM (Push) support in Trillian simply enable battery saving mode in the settings on a device that has Android 2.2+ installed. Do not suspend Trillian as that actually shuts it down, preventing any sort of receiving of messages.
November 3rd, 2010 at 1:57 pm
Awesome app for a beta. It would be great if there was an option for on-going notification when trillian was running in the background.
November 3rd, 2010 at 3:08 pm
Awesome build guys — every is working great on the Nexus One!
This post explains how to activate push notifications. They also explain it further in the comments:
http://blog.ceruleanstudios.com/?p=1612
November 4th, 2010 at 4:05 am
Still not show WLM status/personal message from users that use WLM for BlackBerry
November 4th, 2010 at 9:43 am
I still sometimes have to hit the notification message or the shortcut twice to open the app while it is running on my Evo.
November 4th, 2010 at 5:17 pm
[...] Cerulean Studios has released an update to the Trillian for Android app. Improvements include a better UI, bug fixes, and resolved LED issues that hindered the user from seeing new message notifications. http://www.ceruleanstudios.com [...]
November 6th, 2010 at 1:20 am
Nothing connects for me, everytime I login it shows all my buddies as offline via wifi and cellular network.
I’m using Samsung Galaxy Epic.
Love the interface though
November 6th, 2010 at 8:50 pm
Lovely client, but personal/status message for WLM accounts still not working.
November 7th, 2010 at 2:54 am
A bunch of the items that are flagged as fixed in the changelog don’t seem to be working still. I still need to hit the notification message twice to open the app. i still get the “you are not connected to windows live messenger” message sometimes. The LED colors don’t work, it only blinks green for me. I even get the self re-opening chat sometimes (rare). On the bright side, I think Trillian is using a lot less battery life – I’m still trying to figure out how much is due to the C2DM update and how much is Froyo, but it’s good news.
I am running Android 2.2 on an HTC Desire.
November 7th, 2010 at 4:28 am
Awsome job. I have only one suggestion to make. To logoff you need to press menu button then more then sign off.could you switch button signoff with button “accounts” or “add contact” which are not used nearly as often as sign off so that you can just click menu button, then signoff. Keep up good work
November 7th, 2010 at 4:57 pm
I tried Meebo as well as Trillian on my Droid. Meebo’s interface is a bit nicer, but I actually do like the simplicity of Trillian, and moreso I like how it uses a little less RAM than Meebo and seems to be a little better on battery life when left in the background as well (I’ve noted Meebo uses about 11mb of RAM while Trillian fluctuates between 9 and 11. I know it’s not a huge difference but every little bit of RAM counts especially on the Droid since it has just 256mb RAM). Keep up the good work!!! Is it possible to optimize it to use even lesss RAM?
November 10th, 2010 at 7:12 am
Any chance of rolling out an ICQ patch for Trillian 5 for Windows? Its really frustrating to have lost such a large piece of functionality. I’m reluctant to roll back to v4 but your forcing my hand!!! I don’t want to wait for you to fix the rest of the feature set in 5 before you can release an update – I’d rather just have a patch now, if only to get rid of the error console window which can’t be closed!
November 10th, 2010 at 7:43 pm
Build 137 of trillian im is not stable on android. please revert!
November 10th, 2010 at 8:15 pm
Hi Trillian team,
Have you any plan to publish a version for Windows Mobile 5, 6 and Windows Phone 7 ?
If so, please let me know it’s almost when.
Regards,
Taher
November 12th, 2010 at 2:21 pm
I notice that whenever I am logged onto Trillian from my mobile, even after long periods of time when the phone is not in use (screen off, etc), Trillian never changes my status to ‘Idle’ or ‘Away’. I personally would like it that my status is ‘Idle’ when the phone’s screen is off.
November 13th, 2010 at 7:45 pm
“12233 Scott Werndorfer FIXED [ANDROID] self reopening chat tab”
I still get the same chat window opening at reconnect. Very cool app otherwise.
November 18th, 2010 at 8:42 pm
Every time I try opening a message from another screen, app closes on me saying session invalid and makes me log in again, missing the last message
November 19th, 2010 at 11:37 pm
Will the Android app be available on the App Market?
ATT doesn’t allow unknown apps, and I’m not able to root mine.
November 20th, 2010 at 9:15 am
Like James and Gareth said, this build 137 is very UNSTABLE. The app closes with this errors:
Stack :
=======
java.lang.RuntimeException: Canvas: trying to use a recycled bitmap android.graphics.Bitmap@43a0f358
at android.graphics.Canvas.throwIfRecycled(Canvas.java:957)
at android.graphics.Canvas.drawBitmap(Canvas.java:1046)
at android.graphics.drawable.BitmapDrawable.draw(BitmapDrawable.java:325)
at android.widget.ImageView.onDraw(ImageView.java:842)
at android.view.View.draw(View.java:6740)
at android.view.ViewGroup.drawChild(ViewGroup.java:1640)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.View.draw(View.java:6743)
at android.view.ViewGroup.drawChild(ViewGroup.java:1640)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1374)
at com.ceruleanstudios.trillian.android.TabCustomActivity$TabsView.dispatchDraw(TabCustomActivity.java:331)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.ViewGroup.drawChild(ViewGroup.java:1638)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.View.draw(View.java:6743)
at android.widget.FrameLayout.draw(FrameLayout.java:352)
at android.view.ViewGroup.drawChild(ViewGroup.java:1640)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
at android.view.View.draw(View.java:6743)
at android.widget.FrameLayout.draw(FrameLayout.java:352)
at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1842)
at android.view.ViewRoot.draw(ViewRoot.java:1407)
at android.view.ViewRoot.performTraversals(ViewRoot.java:1163)
at android.view.ViewRoot.handleMessage(ViewRoot.java:1727)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(Native Method)
Cause :
=======
**** End of current Report ***
Where can i download the build 136? This is unusable!! (Samsung Galaxy Android 2.2.0 or 2.2.1 )
November 22nd, 2010 at 9:13 pm
Hey Guys,
Just noticed you folks changed the status bar icon. Don’t mean to be nit-picky, but I was digging into the Android Guidelines myself and found that the new border around the Astra logo doesn’t adhere to Google’s suggested guidelines. It also looks oddly larger when most other apps looks similar.
http://developer.android.com/guide/practices/ui_guidelines/icon_design.html#statusbarstructure
I feel dropping back to the original icon would be better.
P.S. I’m sure you folks had a reason for this, so ignore me if there’s a good reason.
December 29th, 2010 at 11:08 pm
great job. blackbery version is solid
poor android