can execute my app automatilly when android is up?

by tstanly » Thu, 06 Aug 2009 14:43:55 GMT

Sponsored Links
 hi all,

I want to change the start point of my machine,
that is,when start on Android,
it can run my app instead of "home" firstly,

if it possiable?


can execute my app automatilly when android is up?

by brian.schimmel » Thu, 06 Aug 2009 15:40:22 GMT

 I think "home" is not the first application that is started, but it is
the first visible one. So you have two options:

1. Your application can replace the home screen, but then it should do
everything that a home screen does. You have to declare an
IntentFilter with the Home category, see #CATEGORY_HOME

2. You can register your app to be executed on startup, additional to
"home". There is a matching "broadcast action" decribed here: #ACTION_BOOT_COMPLETED


Sponsored Links

can execute my app automatilly when android is up?

by tstanly » Thu, 06 Aug 2009 16:47:11 GMT

 thanks for your reply,

for your first point,
i try to do it by edit the AndroidManifesr.xml,

edit the <intent-filter/> tag for...

 <action android:name="andrroid.intent.action.MAIN" />
 <category android:name="android.intent.category.HOME" />

but not work?


On 8 30 "brian.schimmel" <>


can execute my app automatilly when android is up?

by peter » Thu, 06 Aug 2009 17:04:07 GMT

 you should register a broadcast receiver in your AndroidManifesr.xml
and set intent filter about mobile power on action

your class extends from BroadcastReceiver should fire up your activity
of application


Other Threads

1. debug application key and beta testers

I'm building/signing my application with a debug key. Likewise, I'm
accessing Google Maps with an API key generated by the debug app key.
Now I've got a couple of beta testers and Google Maps isn't working
for them. Is it time to get a real application key and a new Maps key
or is there another way to run the beta phase?


2. Memory Resource Controller cgroup

I am trying to use the Linux Kernel's cgroup Memory Resource
Controller for our Android HW.
Currently I enabled the kernel options:

Thereafter I was able to mount the memory cgroup and I also placed
some constraints on a newly created group. Then I added some value to
memory.limit_in_bytes and started some new processes that where added
to the group's "tasks" file.
But every time I check the group's memory.usage_in_bytes value it
reports 0.

The memory layout of our HW looks like this:
# cat /proc/meminfo
MemTotal:         431952 kB
MemFree:          232788 kB
Buffers:            5236 kB
Cached:            93512 kB
SwapCached:            0 kB
Active:            91424 kB
Inactive:          76064 kB
Active(anon):      69228 kB
Inactive(anon):        0 kB
Active(file):      22196 kB
Inactive(file):    76064 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:             0 kB
HighFree:              0 kB
LowTotal:         431952 kB
LowFree:          232788 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:         68752 kB
Mapped:            43776 kB
Slab:               7228 kB
SReclaimable:       3048 kB
SUnreclaim:         4180 kB
PageTables:         7464 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      215976 kB
Committed_AS:    2713716 kB
VmallocTotal:     401408 kB
VmallocUsed:      108384 kB
VmallocChunk:     278524 kB

Does the Memory Resource Controller not work with low memory? When I
do the same steps on my Ubuntu machine it works great.


3. Arti symbol 1x "D" di Samsung Moment & Sync di CDMA lambat

4. detecting home screen, idle of device

5. bindService() does not create local service, but returns true

6. licensing service on android

7. Android based application for healthcare