IM+ for #Android beta is updated to 3.0.3

by harunjo » Mon, 19 Jul 2010 23:24:14 GMT

Sponsored Links
 Masih boros battre sekitar 17% makan resource.. ;t=1194

IM+ for Android beta-testing

Postby Victoria  Mon Jul 19, 2010 9:21 am
We are glad to inform you that IM+ for Android beta-testing is finally

How to participate in beta testing?

1) First of all please download IM+ v.3.0 beta to your Android device: ... 3_beta.apk 
2) Please register on our forum, if you are not registered yet.
3) Please edit your signature and add your mobile device model and OS
version to it:
4) Start providing feedback.
You may post bug reports and here on this forum or submit them from IM
+ "About" / "Feedback".

As usual, most active beta-testers will be awarded by license codes
for Full version.

What's new in beta version?

- Skype* and Facebook chat support
- Improved UI and usability
- Text-to-speech (play messages as spoken audio)

What to test?

That's what we would like to check:
- how new services - Skype and Facebook - work;
- if there are any compatibility issue with diffent device models;
- if some issue reported for previous versions persist or not:

We would also appreciate your feedback concerning application
usability and interface.

CAUTION: This version is BETA, so we do not guarantee its stable work.
You install and use it at your own risk.
If beta version doesn't work for you properly, you may switch to the
latest release version 2.0.2.

* That's how Skype chat works in IM+ for Android beta:
- Group chats are not supported yet. This functionality will be added
to further updates.
- After 5 minutes of inactivity Skype service disconnects.
Victoria Slinyavchook
Head of QA and Customer Care
SHAPE Services 

I have HTC Nexus One, OS 2.2


Other Threads

1. Mirroring a RelativeLayout

I would like to take a RelativeLayout which has a bunch of sub views,
and mirror it along the X axis. I have followed the rotateView code
from the map example, but that one is subclassing a ViewGroup, not a
RelativeLayout (what's the difference by the way?)

The mirroring needs to be permanent, so while an animation would be
possible it is not desired (and during testing it also produced weird
side effects - the main view would flip but the child views would not
stay pinned correctly).

Here is my current code

public class MainScreen extends Activity {
    public void onCreate(Bundle savedInstanceState) {
        FlipMainScreen ms = new FlipMainScreen(getApplication());
        TextView testText = new TextView(getApplication());
        testText.setText("Mirror test");

public class FlipMainScreen extends RelativeLayout {

    public FlipMainScreen(Context context) {

    protected void dispatchDraw(Canvas canvas) {;
        canvas.scale(-1f,1f, getWidth() * 0.5f, getHeight() * 0.5f);

    protected void onLayout(boolean changed, int l, int t, int r, int
b) {
        final int width = getWidth();
        final int height = getHeight();
        final int count = getChildCount();
        for (int i = 0; i < count; i++) {
            final View view = getChildAt(i);
            final int childWidth = view.getMeasuredWidth();
            final int childHeight = view.getMeasuredHeight();
            final int childLeft = (width - childWidth) / 2;
            final int childTop = (height - childHeight) / 2;
            view.layout(childLeft, childTop, childLeft + childWidth, childTop
+ childHeight);


The text view displays but it is not mirrored. Rather, it is centered
on the screen if I use the onLayout override.

How can I make the RelativeLayout flip completely, including all the
child views ?
(user interaction is obviously not required in that state)


2. service process priority: startService() vs bindService()

Hi there,

I would need your help to clarify what is the priority
of a process hosting a Service when the service is
either started (startService() ) or bound (bindService()):

When the Service is started, the Android doc is quite clear saying:
"If the service has been started, then its hosting process is
considered to be less important than any processes that are currently
visible to the user on-screen, but more important than any process not
=> it means that the process is ranked as "Service process" level (Cf.
Processes and Threads android doc)
As far as i understand, this priority level should warrant us the
process will only be killed in a very
constraining RAM configuration, and makes it suitable for long time
running background thread..
Is my understanding correct?

My concern deals with the bound case..
Android doc says:
"If there are clients bound to the service, then the service's hosting
process is never less important than the most important client. That
is, if one of its clients is visible to the user, then the service
itself is considered to be visible. "
So if my most important client gets stopped and goes in the background
(or even worse, is destroyed), the Service process is then ranked in
the same way?? It would then mean that it does
not keep ranked as "Service process" level (started case) and will be
about to be destroyed by
the system at any time..
So what the point of launching a background thread in a bound
Service?? What's the difference between a simple thread launching from
an Activity?

Am i missing a point? Any comments?



3. Can i manipulate JavaScript events or functions in WebView ?.

4. Long server process...solution

5. My Android device is port scanning, Port 137. Anyone heard of this?

6. Google Nexus S - Secure storage

7. Creating separate versions of apps for tablets