You're invited to try Times People

by ivan . turkovic » Sun, 31 May 2009 05:17:09 GMT


Sponsored Links
 Greetings! Your friend ivan.turko...@gmail.com is using TimesPeople to share 
and discover the best of NYTimes.com. 

To join the growing network of Times People users, visit the Times People page
 http://timespeople.nytimes.com/home/signup/ and sign up. If you 're already a 
member of NYTimes.com, you're halfway there; we'll help you link your existing 
account to Times People.

Sign up today to see what other Times People users are recommending -- from
articles to blog posts to interactive graphics, there's a lot to explore.


The Times People Team



--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Browsable Intent

Hello everybody,

I am trying to intercept an intent for http URLs within the BROWSABLE
category. I've tried using the following:

<activity
        android:name=".MyActivity"
        android:label="@string/app_name">
        <intent-filter>
                <action
                        android:name="org.oos.intent.action.VIEW" />
                <category
                        android:name="android.intent.category.DEFAULT" />
                <category
                        android:name="android.intent.category.BROWSABLE" />
                <data
                        android:scheme="http" />
        </intent-filter>
</activity>

as well as specifying the host and the port and most possible options.
And yet I never get the intent to touch my activity.
Am I missing something? Do I require to register any permission? or
something else?

-- 

2. Bluetooth, RFCOMM socket close error ?

Hi all,

Using this list as a valuable source of info, I've been able to
succesfully create an RFCOMM connection and transfer data over it,
using my HTC Desire.
The primary obstacle was the failure of
BluetoothDevice.createRfcommSocketToServiceRecord(), circumvented by
reflection (createRfcommSocket). Search this group or
stackoverflow.com for example code.

So far, so good.
But - after closing down the connection following what I think is
correct procedure (close streams, then close socket, each encapsulated
in try/catch), the next call to connect() blocks until I call close()
from another thread.

In this scenario, Logcat always contains:

E/BTLD    (23644): RFCOMM_CreateConnection - already opened state:2,
RFC state:4, MCB state:5

- despite the fact that I (think I) have closed everything properly.

The only cure I've been able to find is cycling BT off and on, which
is a bit much, I think... Doable from code, but definitely not a nice
thing to do.

Am I missing a point somewhere, or is this a known bug in the BT stack
(possibly HTC specific) ?

BR
Per



-- 

3. how do you guys feel about the develop tools?

4. How to determine size of Layout

5. Android Market paid app download errors

6. Is it posible to use direct buffers in addCallbackBuffer?

7. How to measure FPS