Does Intent use Binder driver to implement?

by nfsnfs » Fri, 26 Mar 2010 14:08:00 GMT


Sponsored Links
 Hi,

Intent and Binder are both IPC mechanisms in Android.
I would like to know: Does Intent uses Binder driver to implement?
May Intent use other part of kernel?
Or Intent has no relationship with kernel....?

Thanks anyway.

-- 


To unsubscribe from this group, send email to 
android-kernel+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.



Does Intent use Binder driver to implement?

by Dianne Hackborn » Fri, 26 Mar 2010 16:47:24 GMT


 Intent is a data container.  It makes no sense in this question.

Now if you are are asking if some APIs using intent do these things...
 well, yeah.  You can call an API with an Intent that will cause a sweeping
set of stuff to happen -- for example with startActivity, which can result
in lots of IPC (both via Binder and other ways) to communicate with the
activity manager, display a window, etc; and forking of a process, and
loading of an application (mmapping), and on and on.




> website: 


Sponsored Links


Does Intent use Binder driver to implement?

by nfsnfs chen » Fri, 26 Mar 2010 19:22:33 GMT


 Thanks for help.

I know it would be a stupid question.
But I still can not figure out how ActivityManager dispatch Intent to
the BroadcastReceiver.
Using Android Framework only or kernel may help...?

If this question is not suitable in android-kernel group, plz tell me.

Thanks a lot!





-- 


To unsubscribe from this group, send email to 
android-kernel+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.



Does Intent use Binder driver to implement?

by Dianne Hackborn » Fri, 26 Mar 2010 20:08:44 GMT


 ell the kernel is involved in most anything, of course, and certainly once
you have more than one process involved.

In this case, follow the trail -- Context.sendBroadcast(). This results in
a call on IActivityManager, which is implemented by ActivityManagerService,
and that is where the main implementation exists.

Further discussion should probably be moved off android-kernel.

On Fri, Mar 26, 2010 at 12:22 PM, nfsnfs chen <nfs...@gmail.com> wrote:




--
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.

--


To unsubscribe from this group, send email to
android-kernel+unsubscribegooglegroups.com or reply to this email with the
words "REMOVE ME" as the subject.



Other Threads

1. android Boot up issue

Hi all,

Iam using imx31 on my custom board.

Iam using the latest PDK(3stack) board ,android bsp as my reference.

I ahve all appliaed the patches provided by freescale and built my android
image with the below command

"make PRODUCT-imx51_3stack-eng "

 I changed BoardConfig.mk to Then turn on BOARD_USES_ALSA_AUDIO := true
and BUILD_WITH_ALSA_UTILS := true,

My Android image got successfully built .

I placed the builded root filesystem  in sdcard and rebooted the device.

The device booted up and got strucked at the android logo.

Kindly provide some pointers on
this issue,


Below is the log.





xc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0
Real TIme clock Driver v1.0
Power Management for Freescale MX31
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
MXC Backlight Device mxc_ipu_bl.0 Initialized.
input: mxc_ts as /class/input/input1
mmc0: new SDIO card at address 0001
mxc input touchscreen loaded
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:00:20 UTC (20)
Waiting 3sec before mounting root device...
mmc1: new SD card at address b368
mmcblk0: mmc1:b368 USD   980992KiB
 mmcblk0: p1 p2
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 112K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
sh: can't access tty; job control turned off
# init: cannot find '/system/bin/playmp3', disabling 'bootsound'
warning: `app_process' uses 32-bit capabilities (legacy support in use)

# ps
USER     PID   PPID  VSIZE RSS   WCHAN    PC         NAME
root     1     0     276   188   c00a8cb8 0000c87c S /init
root     2     0     0     0     c0059c14 00000000 S kthreadd
root     3     2     0     0     c004a4ec 00000000 S ksoftirqd/0
root     4     2     0     0     c006eb80 00000000 S watchdog/0
root     5     2     0     0     c00569dc 00000000 S events/0
root     6     2     0     0     c00569dc 00000000 S khelper
root     11    2     0     0     c00569dc 00000000 S suspend
root     81    2     0     0     c00569dc 00000000 S kblockd/0
root     84    2     0     0     c00569dc 00000000 S cqueue
root     90    2     0     0     c00569dc 00000000 S mxc_spi.0
root     93    2     0     0     c00569dc 00000000 S mxc_spi.1
root     104   2     0     0     c00569dc 00000000 S kmmcd
root     110   2     0     0     c00569dc 00000000 S pmic_spi/0
root     178   2     0     0     c007aed4 00000000 S pdflush
root     179   2     0     0     c007aed4 00000000 S pdflush
root     180   2     0     0     c007eddc 00000000 S kswapd0
root     224   2     0     0     c00569dc 00000000 S aio/0
root     228   2     0     0     c00569dc 00000000 S nfsiod
root     863   2     0     0     c01d6ad0 00000000 S mtdblockd
root     919   2     0     0     c0210ddc 00000000 S hwevent
root     943   2     0     0     c00569dc 00000000 S rpciod/0
root     957   2     0     0     c01fe9cc 00000000 S mxc_ts
root     966   2     0     0     c0217830 00000000 S mmcqd
root     1749  1     740   320   c0047df8 afe0d15c S /system/bin/sh
system   1750  1     812   260   c01ab5f8 afe0c3bc S
/system/bin/servicemanager
root     1751  1     1852  340   ffffffff afe0c11c S /system/bin/mountd
root     1752  1     680   296   c024caec afe0cd4c S /system/bin/de{*filter*}d
root     1753  1     1196  512   c005d6f0 afe0ca2c S /system/bin/rild
root     1755  1     71360 23048 c00a9318 afe0c4e4 S zygote
bluetooth 1757  1     1168  560   c00a8cb8 afe0d32c S
/system/bin/dbus-daemon
root     1758  1     804   308   c02aa778 afe0c11c S /system/bin/installd
root     1760  1     1268  128   ffffffff 0000e774 S /sbin/adbd
system   1771  1755  139392 21416 ffffffff afe0c3bc S system_server
root     1870  1749  888   336   00000000 afe0c11c R ps
#


I had even given the logcat to check the problem but unable totrace it out.


Below is the logcat Log:

/DEBUG   ( 1752): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *
**
I/DEBUG   ( 1752): Build fingerprint:
'freescale/imx31_3stack/imx31_3stack/:1.5/
MAIN/eng.root.20090615.152300:eng/test-keys'
I/DEBUG   ( 1752): pid: 2028, tid: 2028  >>> /system/bin/mediaserver <<<
I/DEBUG   ( 1752): signal 11 (SIGSEGV), fault addr 00000010
I/DEBUG   ( 1752):  r0 00000000  r1 ab757acc  r2 0000adc8  r3 00000000
I/DEBUG   ( 1752):  r4 0000adc8  r5 0000adc8  r6 be945a40  r7 00000000
I/DEBUG   ( 1752):  r8 0000af60  r9 ab762e0c  10 0000adc8  fp be945adc
I/DEBUG   ( 1752):  ip 00000018  sp be945a40  lr ab71a92c  pc ab72899c  cpsr
000
00010
I/DEBUG   ( 1752):          #00  pc 0002899c  /system/lib/libaudio.so
I/DEBUG   ( 1752):          #01  pc 0001a928  /system/lib/libaudio.so
I/DEBUG   ( 1752):          #02  pc 0001ac74  /system/lib/libaudio.so
I/DEBUG   ( 1752):          #03  pc 000187bc  /system/lib/libaudio.so
I/DEBUG   ( 1752):          #04  pc 000129f6  /system/lib/libaudioflinger.so
I/DEBUG   ( 1752):          #05  pc 00012bf6  /system/lib/libaudioflinger.so
I/DEBUG   ( 1752):          #06  pc 00008768  /system/bin/mediaserver
I/DEBUG   ( 1752):          #07  pc 0001fd72  /system/lib/libc.so
I/DEBUG   ( 1752):          #08  pc 0000bc12  /system/lib/libc.so
I/DEBUG   ( 1752):          #09  pc b0001424  /system/bin/linker
I/DEBUG   ( 1752): stack:
I/DEBUG   ( 1752):     be945a00  00000001
I/DEBUG   ( 1752):     be945a04  afe225a5  /system/lib/libc.so
I/DEBUG   ( 1752):     be945a08  ab757ac8  /system/lib/libaudio.so
I/DEBUG   ( 1752):     be945a0c  0000af71  [heap]
I/DEBUG   ( 1752):     be945a10  00000000
I/DEBUG   ( 1752):     be945a14  0000af60  [heap]
I/DEBUG   ( 1752):     be945a18  ab762e0c
I/DEBUG   ( 1752):     be945a1c  0000adc8  [heap]
I/DEBUG   ( 1752):     be945a20  be945adc  [stack]
I/DEBUG   ( 1752):     be945a24  0000af71  [heap]
I/DEBUG   ( 1752):     be945a28  00000003
I/DEBUG   ( 1752):     be945a2c  afb05b9b  /system/lib/libcutils.so
I/DEBUG   ( 1752):     be945a30  0000adc8  [heap]
I/DEBUG   ( 1752):     be945a34  0000adc8  [heap]
I/DEBUG   ( 1752):     be945a38  df002777
I/DEBUG   ( 1752):     be945a3c  e3a070ad
I/DEBUG   ( 1752): #01 be945a40  00000000
I/DEBUG   ( 1752):     be945a44  00000000
I/DEBUG   ( 1752):     be945a48  00000000
I/DEBUG   ( 1752):     be945a4c  00000000
I/DEBUG   ( 1752):     be945a50  00000000
I/DEBUG   ( 1752):     be945a54  00000000
I/DEBUG   ( 1752):     be945a58  00000000
I/DEBUG   ( 1752):     be945a5c  00000000
I/DEBUG   ( 1752):     be945a60  00000000
I/DEBUG   ( 1752):     be945a64  00000000
I/DEBUG   ( 1752):     be945a68  00000000
I/DEBUG   ( 1752):     be945a6c  00000000
I/DEBUG   ( 1752):     be945a70  00000000
I/DEBUG   ( 1752):     be945a74  00000000
I/DEBUG   ( 1752):     be945a78  00000000
I/DEBUG   ( 1752):     be945a7c  00000000
I/DEBUG   ( 1752):     be945a80  ffff4c54
I/DEBUG   ( 1752):     be945a84  ab71a880  /system/lib/libaudio.so
I/DEBUG   ( 1752):     be945a88  fffff294
I/DEBUG   ( 1752):     be945a8c  fffff284
I/DEBUG   ( 1752):     be945a90  000001c8
I/DEBUG   ( 1752):     be945a94  afe0ea2c  /system/lib/libc.so
I/DEBUG   ( 1752):     be945a98  0000adc8  [heap]
I/DEBUG   ( 1752):     be945a9c  00000000
I/DEBUG   ( 1752):     be945aa0  00000000
I/DEBUG   ( 1752):     be945aa4  0000adc8  [heap]
I/DEBUG   ( 1752):     be945aa8  000000dc
I/DEBUG   ( 1752):     be945aac  f189cc56
I/DEBUG   ( 1752):     be945ab0  00000000
I/DEBUG   ( 1752):     be945ab4  0000adc8  [heap]
I/DEBUG   ( 1752):     be945ab8  0000ada0  [heap]
I/DEBUG   ( 1752):     be945abc  0000ad20  [heap]
I/DEBUG   ( 1752):     be945ac0  0000ac58  [heap]
I/DEBUG   ( 1752):     be945ac4  00000000
I/DEBUG   ( 1752):     be945ac8  00000000
I/DEBUG   ( 1752):     be945acc  00000000
I/DEBUG   ( 1752):     be945ad0  00000000
I/DEBUG   ( 1752):     be945ad4  be945ae0  [stack]
I/DEBUG   ( 1752):     be945ad8  ab71ac78  /system/lib/libaudio.so
I/DEBUG   ( 1752):     be945adc  ab71a824  /system/lib/libaudio.so
I/ServiceManager( 1771): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1771): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1771): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1771): Waiting for sevice media.audio_flinger...
W/AudioSystem( 1771): AudioFlinger not published, waiting...
I/ServiceManager( 1771): Waiting for sevice media.audio_flinger...
I/        ( 2029): ServiceManager: 0xabe0
E/AudioHardwareALSA( 2029): Unable to attach mixer to device
AndroidPlayback: No
 such file or directory
E/AudioHardwareALSA( 2029): Unable to attach mixer to device default: No
such fi
le or directory
E/AudioHardwareALSA( 2029): Unable to attach mixer to device AndroidRecord:
No s
uch file or directory
E/AudioHardwareALSA( 2029): Unable to attach mixer to device default: No
such fi
le or directory
I/DEBUG   ( 1752): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *

Regards,
Mueendra.

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:  http://www.***.com/ 
-~----------~----~----~----~------~----~------~--~---

2. CONNECTIVITY_CHANGE - Why is there no broadcast for WIFI on but mobile gets lost?

Hello.

[1]
At the moment I am trying to catch the event when the mobile network
is not available. This works when WIFI is off and I catch the
CONNECTIVITY_CHANGE broadcast. But when I enable WIFI and lose the
mobile network (network is not available) no broadcast gets sent.

Is this a bug or why does that happen?

[2]
Another thing that I have recognized while testing is the following
behaviour.

WIFI on, Mobile on -> starting airplane mode -> stopping airplane mode
-> broadcast gets sent for WIFI enabled and connected and mobile
disabled and disconnected. But no broadcast gets sent when the mobile
network is available after that. (while WIFI is still on)

http://paste.pocoo.org/show/IEENaOK7AJHR1cEdHMfR/

Is this a bug or is this normal behaviour?

To sum up is there a method to reliable follow the state of the mobile
network? (when is it available and when does it get lost)

Thank you for your help.

Regards.
--~--~---------~--~----~------------~-------~--~----~

3. Is there any dev accreditation for Android?

4. How to set context menu header title in XML?

5. How to use sdcard in virtualbox

6. how to use functions provided by libnetutils.so

7. android.bat error unsupportedclassversionerror