Will Android open up the hardware?

by Vinegar Tasters » Tue, 13 Jan 2009 17:47:21 GMT


Sponsored Links
 According to this post:

 http://www.edepot.com/forums/viewtopic.php?f=7& ;t=1151

It seems pretty logical that opening up the hardware is important.
--~--~---------~--~----~------------~-------~--~----~



Will Android open up the hardware?

by Vinegar Tasters » Tue, 13 Jan 2009 17:49:03 GMT


 Also:

 http://www.edepot.com/forums/viewtopic.php?f=8& ;t=956
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Will Android open up the hardware?

by mathiastck » Wed, 14 Jan 2009 03:31:57 GMT


 Belongs in the Android discuss group.  Makes some OK points but misses
boat.  Java is a good thing, Android on lots of different hardware is
a good thing.



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



Other Threads

1. Debugging code

I think I am missing something when trying to debug my code in eclipse.  I
can run/debug code from the run or debug buttons in eclipse,   but I
remember I used to have some tab on the bottom, logcat I think it was that
would scroll a lot of info about everything the emulator phone was doing.  I
have the logcat tab on the bottom, and I have tried selecting info and
verbose logging modes to get all that good info to show up in the logcat
whenever I run/debug my app in the emulator, but I'm not having any luck.
Can someone suggest what I can do to get this working again?  Thanks.


-- 

2. Using FLAG_ACTIVITY_CLEAR_TOP, but don't restart target activity?

Ok this does work if you add the following to your activity definition
in the manifest file:

   android:launchMode="singleTop"

Thanks








-- 

3. Bluetooth for magic

4. Using FLAG_ACTIVITY_CLEAR_TOP, but don't restart target activity?

5. Using FLAG_ACTIVITY_CLEAR_TOP, but don't restart target activity?

6. using gdb in Android x86

7. namespace in styles.xml