need suggestion for interface

by cellurl » Wed, 21 Apr 2010 05:05:19 GMT


Sponsored Links
 I want to turn on two different lights using my Android.
Q: How would you do it?

Bluetooth: AFAIK, BT only supports one (1) channel, this won't work
because the user could be on a call at the same time as I need the
channel.

USB: Host mode isn't coming soon, and I can't use a hack. (I hope to
sell this as an accessory product). I need 2-lights, so just turning
on/off the USB 5v won't work...

WIFI: This seems best, Does anyone agree?? Since it already works on
most models. How to do it cheaply.

Speaker: One guy did DTMF over the speaker to run his robot. But, it
won't work like a cradle or wireless...

IRDA: I thought of making a USB to IRDA dongle, but that would
interfere with any cradle.


Am I missing something? I realize the "intent" of Android is to get-2-
the-internet, but Palm had success by promoting attachments like
these, and I hope Android will too....

-jp







--



Other Threads

1. Force Close Question

Hello Group, 

How can I deal with when the user hits the home button when in my app and 
then doesnt go back to it for a while and then they hold home button to go 
back to my app and then the force close appears since all the memory has 
been freed because how the OS is designed.

Is there a way instead of resuming the app that has freed memory and will 
break instantly...just launch it brand new?

Is there a setting in the Android Manifest to force start brand new if freed 
memory?

Thanks group.

-- 

2. Can an application control the open / closed state of the status bar panel?

I have an application which exhibits two different behaviors, possible
related to Android 2.2 vs. Android 2.1 update 1.

The application uses the proximity sensor to determine when the phone
is "near" the ear. If a "near" condition is detected, I get the
applications window and set the LayoutParams to FLAG_NOT_TOUCHABLE and
FLAG_FULLSCREEN. In general, this has the desired effect of preventing
accidental screen touches by the ear from causing any unwanted action.
However...

With my Android V2.2 phones: If I am in the process of sliding open
the Status Bar at the time the proximity sensor detects a "near"
condition, the Status Bar immediately closes and all is good.

With my Android V2.1 phones: If I have the Status Bar partially open,
detect a "near" condition, and then simultaneously (more or less)
revert to a "far" condition while releasing the Status Bar, the Status
Bar is left in a partially opened state. Meanwhile, part of my
application remains visible, but not touchable. I can simulate this at
will with 2.1 phones, but can not do so at all with 2.2 phones.

My questions:

1) Does anyone know why this behavior is different, and if it is
indeed related to different Android versions?

2) Is there a way that an application (such as mine!) can detect if
the Status Bar is opened, or in the process of sliding open, and tell
it to close?

Thanks for any help you can offer.

-- 

3. data upload java script

4. InputMethodManager and it's active View

5. viewgroup and view

6. Android Revolution HD 2.0.9

7. Android saceng is back, with gps