Audio plugin.

by dmoti » Tue, 22 Jun 2010 04:28:20 GMT


Sponsored Links
 I'm developing an Audio plugin for the android platform.
The plugin suppose to process all audio from the device.
I've already implemented an alsa plugin which work with android too,
but I must change alsa configuration files and install a dynamic link
library.

My question is: is it possible to create an OpenCore plugin that will
do the same?
Is all audio play in an android platform must go through OpenCore?
If so, can I create and build an application that will work (after
compilation of course)
on any android platform ?

thanks,
-md

--



Other Threads

1. Search suggestions causing inconsistent behavior in application after triggered from Quick Search Bar

I'm running into an issue with the Quick Search Bar that I'm hoping
someone can help me with.

My application includes a Searchable activity used to provide search
behavior within my application.  That search activity is designed to
trigger a separate Intent when the search item is clicked on so as to
cause a different Activity to handle the viewing.  When used within
the application, the search behavior works perfectly every time.

My application also includes a ContentProvider used to provide search
suggestions and is also configured to allow use in the Quick Search
Bar.  When used within the application itself, use of the search
suggestions works fine every time it is used.  When triggered from the
QSB, the initial search suggestion brings up the viewing activity just
as it should.  After that point, however, any use of the search
suggestions from within the application (i.e. bringing up the search
and selecting a search suggestion) fails to trigger the viewing
application.  In fact, I've put debug statements in every single
"onXXX()" method within the Searchable activity and I never see any of
them get triggered.  On the flip side, when I trigger a standard
search at that same point (i.e. enter a query string and hit enter,
rather than navigating to a search suggestion), the search dialog
comes up, as expected, and selecting an item from that list
successfully triggers my application.

I'm currently at a loss trying to determine why this would be
occurring.  Any ideas

As as some additional information, my manifest contains the following
in regards to the searchable activity
(".activity.SearchableActivity"), the suggestions provider
(".content.TestSuggestionProvider") and the activity used to display
the content (".activity.TestDisplayActivity"):

        <activity
            android:name=".activity.TestDisplayActivity"
            android:label="@string/app_name"
            android:launchMode="singleTask"
            android:finishOnTaskLaunch="true"
            android:theme="@android:style/Theme.NoTitleBar.Fullscreen"
            android:screenOrientation="landscape"
            android:configChanges="orientation|keyboardHidden">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category
android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
            <meta-data android:name="android.app.default_searchable"
android:value=".activity.SearchableActivity" />
        </activity>

        <activity
            android:name=".activity.SearchableActivity"
            android:launchMode="singleTop"
            android:theme="@android:style/
Theme.NoTitleBar.Fullscreen">
            <intent-filter>
                <action android:name="android.intent.action.SEARCH" />
                <category
android:name="android.intent.category.DEFAULT" />
            </intent-filter>
            <meta-data android:name="android.app.searchable"
android:resource="@xml/searchable"/>
        </activity>

        <provider
            android:name=".content.TestSuggestionProvider"
            android:authorities="com.test.provider.suggest"
            android:syncable="false"
            />

And the following is the XML used to further define the settings of
the searchable activity:

    <searchable xmlns:android="http://schemas.android.com/apk/res/
android"
        android:label="@string/search_app_label"
        android:hint="@string/search_app_hint"
        android:searchSettingsDescription="@string/
search_app_settings_description"
        android:includeInGlobalSearch="true"
        android:voiceSearchMode="showVoiceSearchButton|
launchRecognizer"
        android:searchSuggestAuthority="com.test.provider.suggest"
 
android:searchSuggestIntentAction="android.intent.action.VIEW">
    </searchable>

Any thoughts?  At the moment I'm at a complete loss
-- 

2. Huawei SmaKit S7 Sporting a 1Ghz Snapdragon?

We got a look at Huawei 7-inch Android tablet at
Computex<http://phandroid.com/2010/06/04/huawei-s7-shows-up-yet-again-still-no-date-or-price-video/>that
passed recently, but we were still unsure on its specifics. For
starters, pricing and availability are still unknown and we haven gotten
many details about what motivating this supposed champ under the hood.

<http://phandroid.com/wp-content/uploads/2010/06/smackit-huawei-s7.jpg>

According to 
Smarthouse<http://smarthouse.com.au/Home_Office/Notebooks_And_Tablets/X5K3D5B6>an Australian technology outlet we should learn these details and
more
on June 24th when Huawei will be holding a press event for the tablet in
Australia. One new detail is that it sporting a 1GHz Qualcomm Snapdragon
processor to keep the lights on and that it will come with 3G connectivity
and elephony functions.(You thought the Dell Streak </dell-streak> was a
ridiculous size for a phone?)

I guessing those unctionscould be VoIP-based, but anything could be
announced. Wee set our calendar so as not to forget to revisit this story
when the time comes.

Read full article at
http://phandroid.com/2010/06/11/huawei-smakit-s7-sporting-a-1ghz-snapdragon-huawei-press-event-on-june-24th/

Desire with Froyo....brrrrrrr....

-- 
"Indonesian Android Community [id-android]" 

3. question about 'rild'

4. android GPS

5. Writing a loop to set multiple TextView properties

6. OOT: Paging Sindhu.....?

7. A slightly altered pattern for extending the life span of a broadcast receiver (Not entirely verified yet)