How to autorun program when Android start running?

by bluestar » Wed, 22 Jul 2009 20:09:31 GMT


Sponsored Links
 I have one program and I used adb to connect FR to execute it.
I hope this program would auto-execute when entering Android OS of FR
How to add it to initial schedule? Modify init.rc or some files?

Thanks for your big help.
--~--~---------~--~----~------------~-------~--~----~



How to autorun program when Android start running?

by Micah » Wed, 22 Jul 2009 22:00:30 GMT


  http://developer.android.com/reference/android/content/Intent.html #ACTION_BOOT_COMPLETED



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


Sponsored Links


How to autorun program when Android start running?

by bluestar » Thu, 23 Jul 2009 09:58:23 GMT


 Dear Sir:

        The reference is for android application.
        My program was linux program and I used adb to connect FR to
execute it.
        The commands are like below

          1. after connecting to FR
          2. #cd /data/app
              #./myprogram

        I hope these program would auto-run after entering Android OS.
        Could you have one sample code to provide?

        Thanks for your big help.




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



How to autorun program when Android start running?

by Lazarus 101 » Thu, 23 Jul 2009 16:06:16 GMT


 Try using Runtime.getRuntime.exec("/path/to/yourprogram") in the
BOOT_COMPLETED receiver





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



How to autorun program when Android start running?

by bdjhsl » Fri, 07 Aug 2009 10:38:35 GMT


 But, to use BOOT_COMPLETED, your applicaiton must first run and
register that event, right? So, ins't this a chicken and egg problem??

Thanks







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



How to autorun program when Android start running?

by Mark Murphy » Fri, 07 Aug 2009 18:28:01 GMT


 


Register a <receiver> for BOOT_COMPLETED in your manifest.

Visit:

 http://commonsware.com/AdvAndroid/ 

and download the source code to that book. You will find a project in
there named SysEvents/Boot, which shows the implementation of a
BOOT_COMPLETED receiver.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

Android Development Wiki:  http://wiki.andmob.org 

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



Other Threads

1. Unable to inatall Android x86 on eeepc/acer aspire one

Hi,
I'm a newbie with Android, I'm trying to get a working image for acer
aspire one.

I have built an image as described in -
http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/BuildAndroidForX86Platforms

After getting my install USB, I booted the aspire one from the USB,
now -
The install starts to run, but there is an
"Unable to open persistent property directory /data/property errno: 2
"
"init: untracked pid 883 exited sh: can't access tty: job control
turned off"
messages.
but it seems to continue running until it gets to -
"Creating journal inode: done"
"This filesystem will be automatically checked every 20 mounts..."

Ant that's it - no Android no nothing :-(
I'm I messing something?
BTW - on eeepc as well - I get the "Unable to open persistent ..."
And it gets to
"Attached scsi generic sg2 type 0", and stays there.

Please help

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. How to get past "waiting for for device /dev/block/sdb2" on eee PC 1000HE?

I have created a standard VESA x86 Android build (eg. without the
intelfb mods) and created the bootable USB installer but I can't get
past the message "Waiting for device: /dev/block/sdb2" when it boots,
I'm using 1000HE which has a single harddrive instead of the 2 SDD
drives in the earlier 1000 series, when I boot Ubuntu from USB and use
fdisk -l it shows the hard-drive partitions as sda1 thru sda4  and the
USB drive as sdb1 so I'm assuming the standard layout of sda being the
destination drive and sdb the USB drive, with sdb2 as the ext2
partition on the USB key is correct for this machine.

This machine currently has XP on it, did I need to delete the existing
partitions to prepare it for this?

Has anyone had this problem and solved it?  I've seen a few posts
around mentioning the same error but no obvious solutions. I'd
appreciate any pointers.

Thanks!



--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. How to go to suspend state after timeout like windows mobile in Android system?

4. About overlay and Pmem

5. memory leak in com.android.camera

6. Obtaining Frequency from Mic on Android

7. Sharing data between an Android service and an application.