logcat filter, colon within tagname

by Venu » Tue, 09 Feb 2010 01:42:51 GMT


Sponsored Links
 I have an application(not mine) printing logcat messages with a colon
":" within the tagname. How do i use logcat filter with it, since
logcat filter itself uses ":" as a delimiter to specify the level.

D/App:theservice( 402): posting event 345
D/App:theservice( 402): posting event 920

I can't use
logcat -s App:theservice:W

Plz help :D

--



Other Threads

1. Start a service from Launcher

Is it possible to start a service directly from the launcher by
clicking the application icon?

I have no activity just a single service which I want to start when I
click on the icon, however when I specify my service's intent-filters
it seems that it will not be recognised from the launcher, therefore
no icon is visible in android's launcher.

<application android:icon="@drawable/icon" android:label="@string/
app_name" >

<service android:name="MyService">
        <intent-filter>
                <action android:name="android.intent.action.MAIN"></action>
                <category android:name="android.intent.category.LAUNCHER"></
category>
        </intent-filter>
</service>

</application>

Any clue how to get the icon into the launcher.
--~--~---------~--~----~------------~-------~--~----~

2. Touch Sensitivity With HTC Dream 1 Device Lacking

Fwiw, I have never had a problem touching any of the G1 screens I have
used...  but maybe my hand isn't oily enough or something.

Honestly, though, if the screen isn't working for someone, I would think it
wouldn't work everywhere, so it would be strange for them to explicitly
target a particular app for that complaint.  It's not like the base platform
doesn't use touch extensively itself, so any general screen problems like
"not detecting a finger without pressing hard" would show up anywhere.

When I see a comment like needing to press hard, my first thought is that
this could well be the user trying to interpret something they are doing to
cause things to work correctly, but that very well may not be what is going
on at all.  I would certainly take such statements with a huge grain of salt
-- certainly there is -some- problem, but the given explanation seems
unlikely to me.

At any rate, the G1 screen is what it is, and it pretty typical of a
capacitive touch screen.  A UI needs to be designed to work within the
constraints of the input hardware.  For example, the screen also doesn't
recognize the location of touch events at the edge of the screen, and there
are many things in the base Android frameworks and UI that work around that
(or even take advantage of it).






-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

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

3. Auto launch Service

4. Changing background color on a selected listview item

5. How to access "shared data/settings" across multiple application? ContentProvider or SharedPreferences?

6. attributes for multiple resources in attrs.xml

7. opencore RTSP streaming NAT/firewall issue