pianyu / 0xdroid Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 324 KB

Automatically exported from code.google.com/p/0xdroid

0xdroid's People

Contributors

0xdroid's Issues

[beagle-donut] Vold crashes when accessing /sys/class/mmc_host/mmcX/slot_name

Cherry-pick fix from beagle-cupcake:

http://gitorious.org/0xdroid/system_core/commit/bf95f2225001922879a9e8c882d3e898
dd7bdbe7

Original issue reported on code.google.com by ticktock35 on 19 Oct 2009 at 7:50

Performance tunning for video recording.

Preview is too slow when running video recording.
Rendering preview frame memory to framebuffer seems to be delayed.

We need to increase the performance when running video recording.

In Preview only mode, the cpu is eaten as below, 
  PID CPU% S  #THR     VSS     RSS UID      Name
 1365  29% S    13  28492K   7044K media    /system/bin/mediaserver
  802   4% S    36 287396K  33900K system   system_server

When running video recording, its as below,
  PID CPU% S  #THR     VSS     RSS UID      Name
 1365  91% S    14  30672K   7508K media    /system/bin/mediaserver
  802   3% S    36 287396K  33936K system   system_server

mediaserver nearly run out of CPU unacceptably when recording the video.

Comparing to G1 for reference, 
In preview only status,
PID CPU% S  #THR     VSS     RSS UID      Name
   51   7% S    18  42168K   5828K media    /system/bin/mediaserver

In Recording video status,
PID CPU% S  #THR     VSS     RSS UID      Name
   51  62% S    21  45368K   6040K media    /system/bin/mediaserver
 3322   4% R     1    908K    356K shell    top

Original issue reported on code.google.com by [email protected] on 12 Nov 2009 at 1:46

Enable Overlay-V4L2

omap_vout was implemented in recent git tree. However, it seems to be
working on zoom2 hardware instead of beagleboard. To leverage the power of
TI OMAP graphical overals under Android, omap_vout has to be enabled.

Required kernel configurations:

CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y                                                

CONFIG_VIDEO_MEDIA=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_OMAP_VIDEOOUT=y
CONFIG_VIDEO_OMAP_VIDEOOUT_BUFPOOL=y


But kernel panic with that configuration:

/ # v4l2_test 
not enough args -- using defaults!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 0 [#1] PREEMPT
Modules linked in:
CPU: 0    Not tainted  (2.6.29-omap1-gc271a21-dirty #162)
PC is at 0x0
LR is at omapvout_dss_perform_update+0x64c/0x7e4
pc : [<00000000>]    lr : [<c01e11a4>]    psr: 60000013
sp : cfd89ef0  ip : 00000000  fp : cfd89f7c
r10: cf8c2800  r9 : 00000000  r8 : 00000001
r7 : 00000064  r6 : 000000c8  r5 : cf976520  r4 : 00000000
r3 : 00000064  r2 : 00000000  r1 : 00000000  r0 : c0498640
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5387d  Table: 8fd84019  DAC: 00000017
Process OMAPVOUT-DSS (pid: 1305, stack limit = 0xcfd882e8)
Stack: (0xcfd89ef0 to 0xcfd8a000)
9ee0:                                     000000c8 cfd89f00 00000000 fffffffc 
9f00: 00000000 cf8fdcc0 00000000 000000c8 00000064 c0049e28 00000002 cf820000 
9f20: 00000001 8fa00000 00000000 00640064 000000c8 00000040 00000000 00000000 
9f40: 00000000 00640000 000000c8 000c0018 00000017 cf8fdd6c ceda6ba0 cf8fdd68 
9f60: cfd88000 c01e0b58 00000000 00000000 cfd89fa4 cfd89f80 c0068824 c01e0b64 
9f80: ceda6ba8 cfd89fb8 cfbfdbe0 ceda6ba0 00000000 00000000 cfd89fdc cfd89fa8 
9fa0: c006952c c0068768 cfd89fdc 00000000 cfbfdbe0 c006cac8 cfd89fb8 cfd89fb8 
9fc0: ceda6ba0 c0069480 00000000 00000000 cfd89ff4 cfd89fe0 c006c758 c006948c 
9fe0: 00000000 00000000 00000000 cfd89ff8 c005a668 c006c710 00000000 00000000 
Backtrace: 
[<c01e0b58>] (omapvout_dss_perform_update+0x0/0x7e4) from [<c0068824>]
(run_workqueue+0xc8)
[<c006875c>] (run_workqueue+0x0/0x184) from [<c006952c>]
(worker_thread+0xac/0xc0)
 r9:00000000 r8:00000000 r7:ceda6ba0 r6:cfbfdbe0 r5:cfd89fb8
r4:ceda6ba8
[<c0069480>] (worker_thread+0x0/0xc0) from [<c006c758>] (kthread+0x54/0x80)
 r7:00000000 r6:00000000 r5:c0069480 r4:ceda6ba0
[<c006c704>] (kthread+0x0/0x80) from [<c005a668>] (do_exit+0x0/0x728)
 r5:00000000 r4:00000000
Code: bad PC value.
OMAPVOUT: Q'ing Frame 1
Kernel panic - not syncing: Fatal exception

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 6:40

Evaluate customized AudioHardwareOmap (of libaudio) from omapzoom

omapzoom's Android source tree (
https://omapzoom.org/gf/project/omapandroid ), there is a customized
version of libaudio:

$ ls hardware/ti/omap3/libaudio
Android.mk             AudioHardwareOmap.h    AudioStreamInOmap.h 
AudioStreamOutOmap.cpp
AudioHardwareOmap.cpp  AudioStreamInOmap.cpp  AudioStreamOmap.h   
AudioStreamOutOmap.h

It is known to handle audio mixer better, but future evaluation is needed.

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 6:49

Support unordered .debug_info references to .debug_ranges

As Ash <[email protected]> reported,

"I am trying to create a shared library. My library gets generated
after the following warning. I have been able to use the library
successfully so far, but I am curious to know if something is wrong,
what does this warning mean and how to resolve this.

---

target SharedLib: libmytest (out/target/product/surf/obj/
SHARED_LIBRARIES/libmytest_intermediates/LINKED/libmytest.so)
target Prelink: libmytest (out/target/product/surf/symbols/system/lib/
libmytest.so)
libelfcopy: Warning: Location lists in .debug_info section aren't in
ascending order!
libelfcopy: Warning: Location offset 0x133d3 from CU 411 is not
preceded by the end of a location list, skipping...
target Strip: libmytest (out/target/product/surf/obj/lib/libmytest.so)
"

Jan Kratochvi mentioned that readelf had the same problem:
"
readelf sometimes complains on valid DWARF already produced by g++-4.3+:

readelf: Error: Range lists in .debug_info section aren't in ascending order!
readelf: Warning: Range lists in .debug_ranges section start at 0x60
"

http://sourceware.org/ml/binutils/2009-07/msg00123.html

So, improving libelfcopy might be a proper solution.

Original issue reported on code.google.com by [email protected] on 3 Sep 2009 at 3:12

Imporve the MVC pattern of Launcher

Android Launcher split the into code Model and View, but it is not
completely yet.

I will try to improve it.

Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 6:06

process.com.android.camera stopped unexpectedly if no UVC device is available

What steps will reproduce the problem?
If there is no Camera device found in 0xdroid environment, 
rocess.com.android.camera always 
stops unexpectedly

What is the expected output? What do you see instead?
adb logcat:

I/ActivityManager(  788): Starting activity: Intent { 
act=android.intent.action.MAIN 
cat=[android.intent.category.LAUNCHER] flg=0x10200000 
cmp=com.android.camera/.Camera }
I/ActivityManager(  788): Start proc com.android.camera for activity 
com.android.camera/.Camera: 
pid=917 uid=10000 gids={1006, 1015, 2001, 3003}
D/CameraService(  763): CameraService::connect E (pid 917, client 0xc1f0)
D/CameraService(  763): Client::Client E (pid 917)
D/CameraHardware(  763): PREVIEW SIZE: w=352 h=288 framerate=30
D/CameraHardware(  763): requested size 1600 x 1200
E/MediaPlayer(  763): Unable to to create media player
E/CameraService(  763): Failed to load CameraService sounds.
E/MediaPlayer(  763): Unable to to create media player
E/CameraService(  763): Failed to load CameraService sounds.
D/CameraService(  763): Client::Client X (pid 917)
D/CameraService(  763): CameraService::connect X
D/Camera  (  917): app passed NULL surface
D/CameraService(  763): setPreviewDisplay(0x0) (pid 917)
D/CameraService(  763): 
getParameters(picture-format=jpeg;picture-size=1600x1200;preview-
format=yuv422sp;preview-frame-rate=30;preview-size=352x288)
D/CameraService(  763): setParameters(picture-size=2048x1536;preview-frame-
rate=30;preview-size=352x288;picture-format=jpeg;jpeg-quality=85;preview-format=
yuv422sp)
D/CameraHardware(  763): PREVIEW SIZE: w=352 h=288 framerate=30
D/CameraHardware(  763): requested size 2048 x 1536
V/camera  (  917): startPreview
D/CameraService(  763): startPreview (pid 917)
D/CameraService(  763): startCameraMode(0) (pid 917)
D/CameraService(  763): mSurface is not set yet.
D/CameraService(  763): startPreviewMode (pid 917)
E/V4L2Camera(  763): ERROR opening V4L interface: No such file or directory
E/CameraHardware(  763): startPreview failed: cannot open device.
D/CameraService(  763): stopPreview (pid 917)
D/CameraService(  763): stopPreview(), hardware stopped OK
D/Camera-JNI(  917): release camera
D/CameraService(  763): Client::disconnect() E (pid 917 client 0xc1f0)
D/CameraService(  763): hardware teardown
D/CameraService(  763): removeClient (pid 917) done
D/CameraService(  763): Client::disconnect() X (pid 917)
W/dalvikvm(  917): threadid=17: thread exiting with uncaught exception 
(group=0x4001b1e0)
E/AndroidRuntime(  917): Uncaught handler: thread Thread-9 exiting due to 
uncaught exception
E/AndroidRuntime(  917): java.lang.RuntimeException: startPreview failed
E/AndroidRuntime(  917):    at 
com.android.camera.Camera.startPreview(Camera.java:1360)
E/AndroidRuntime(  917):    at 
com.android.camera.Camera.access$4000(Camera.java:78)
E/AndroidRuntime(  917):    at com.android.camera.Camera$3.run(Camera.java:724)
E/AndroidRuntime(  917):    at java.lang.Thread.run(Thread.java:1060)
E/AndroidRuntime(  917): Caused by: java.lang.RuntimeException: startPreview 
failed
E/AndroidRuntime(  917):    at android.hardware.Camera.startPreview(Native Method)
E/AndroidRuntime(  917):    at 
com.android.camera.Camera.startPreview(Camera.java:1357)
E/AndroidRuntime(  917):    ... 3 more
I/Process (  788): Sending signal. PID: 917 SIG: 3
I/dalvikvm(  917): threadid=7: reacting to signal 3

Original issue reported on code.google.com by [email protected] on 3 Nov 2009 at 1:49

USB OTG mode is not properly set. USB hotplug fails.

Currently, USB OTG device would be detected and initialized when it was
plugged at boot time.  The root cause is that operating mode of musb is not
set properly.

To enable USB OTG mode, use the following command:
    echo "otg" > /sys/devices/platform/musb_hdrc/mode

However, the mode would be soon inactive once unplugged.

Effects: the hotplug of USB mouse, keyboard, mass storage device won't work.

Original issue reported on code.google.com by [email protected] on 3 Nov 2009 at 2:58

Tweak opkg to fit Android OS

We would like to maintain Android base system by the means of opkg, which
implies that every component can be upgraded/downgraded via opkg. It is
important for platform verification and testing. Also, this is known to
manage 3rd-party software components (native, JNI+apk) easily.

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 7:05

Implement generic WiFi HAL for Android

There is a primitive implementation for HAL in Android:
hardware/libhardware_legacy .  However, it is not complete and generic. In
the perspective of integrations, we should implement at least the following
functions in generic HAL: WLAN, BT, Camera, and GPS.

Original issue reported on code.google.com by [email protected] on 12 Aug 2009 at 10:55

Failed to start launcher while loading shared library

Use daily build image (since 2009-08-13 ~ now) to boot Android, the
launcher died while loading shared library. Even if you see the Home
screen, actually it has died.

Here is the logcat message:


D/dalvikvm(  801): Trying to load lib /system/lib/libjni_latinime.so 0x435ea038
D/dalvikvm(  801): Added shared lib /system/lib/libjni_latinime.so 0x435ea038
I/DEBUG   (  720): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** 
I/DEBUG   (  720): Build fingerprint: 'unknown'
I/DEBUG   (  720): pid: 789, tid: 789  >>> android.process.acore <<< 
I/DEBUG   (  720): signal 11 (SIGSEGV), fault addr 0000000c
I/DEBUG   (  720):  r0 bed76520  r1 bed76434  r2 bed76444  r3 001989d8
I/DEBUG   (  720):  r4 446d4000  r5 44800000  r6 44400000  r7 00000000
I/DEBUG   (  720):  r8 bed7654c  r9 41049330  10 41049320  fp 00000000
I/DEBUG   (  720):  ip 00000001  sp bed76368  lr ad33c003  pc 0000000c 
cpsr 20000030
I/DEBUG   (  720):          #00  pc 0000000c  
I/DEBUG   (  720):          #01  pc 0003bffe  /system/lib/libandroid_runtime.so
I/DEBUG   (  720): stack:
I/DEBUG   (  720):     bed76328  bf800000  
I/DEBUG   (  720):     bed7632c  00000196  
I/DEBUG   (  720):     bed76330  bed76480  [stack]
I/DEBUG   (  720):     bed76334  bed76520  [stack]
I/DEBUG   (  720):     bed76338  bed76368  [stack]
I/DEBUG   (  720):     bed7633c  ad33c003  /system/lib/libandroid_runtime.so
I/DEBUG   (  720):     bed76340  bed763e8  [stack]
I/DEBUG   (  720):     bed76344  ff000000  
I/DEBUG   (  720):     bed76348  00000001  
I/DEBUG   (  720):     bed7634c  00000000  
I/DEBUG   (  720):     bed76350  43ca8000  
I/DEBUG   (  720):     bed76354  446d4000  
I/DEBUG   (  720):     bed76358  44800000  
I/DEBUG   (  720):     bed7635c  44400000  
I/DEBUG   (  720):     bed76360  df002777  
I/DEBUG   (  720):     bed76364  e3a070ad  
I/DEBUG   (  720): #01 bed76368  00000001  
I/DEBUG   (  720):     bed7636c  00000001  
I/DEBUG   (  720):     bed76370  bed76434  [stack]
I/DEBUG   (  720):     bed76374  bed76350  [stack]
I/DEBUG   (  720):     bed76378  00000195  
I/DEBUG   (  720):     bed7637c  ff000000  
I/DEBUG   (  720):     bed76380  00000000  
I/DEBUG   (  720):     bed76384  bed76444  [stack]
I/DEBUG   (  720):     bed76388  00000000  
I/DEBUG   (  720):     bed7638c  00000000  
I/DEBUG   (  720):     bed76390  00000000  
I/DEBUG   (  720):     bed76394  00000002  
I/DEBUG   (  720):     bed76398  00000006  
I/DEBUG   (  720):     bed7639c  000001a8
I/DEBUG   (  720):     bed763a0  0000004a
I/DEBUG   (  720):     bed763a4  00000001
I/DEBUG   (  720):     bed763a8  00000012
I/DEBUG   (  720):     bed763ac  00000012
D/Zygote  (  722): Process 789 terminated by signal (11)
I/ActivityManager(  748): Process android.process.acore (pid 789) has died.
I/WindowManager(  748): WIN DEATH: Window{436256b8
com.android.launcher/com.android.launcher.Launcher paused=false}
I/ActivityManager(  748): Start proc android.process.acore for activity
com.android.launcher/.Launcher: pid=810 uid=10002 gids={3003}
I/ActivityManager(  748): Low Memory: No more background processes.

Original issue reported on code.google.com by [email protected] on 20 Aug 2009 at 4:18

com.android.camera crashes when leaving playing a video

com.android.camera will crash when quitting playing a video by pressing the
back key.
This happens in no matter with using libopencorehw.so

The log is for reference as below:

W/KeyCharacterMap( 1133): No keyboard for id 131073
W/KeyCharacterMap( 1133): Can't open keycharmap file
E/KeyCharacterMap( 1133): Can't find any keycharmaps (also tried
/system/usr/keychars/qwerty.kcm.bin)
I/DEBUG   (  732): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** ***
I/DEBUG   (  732): Build fingerprint:
'beagleboard/beagleboard/beagleboard/:1.6/Donut/eng.jeremy.20091021.225156:eng/t
est-keys'
I/DEBUG   (  732): pid: 1133, tid: 1133  >>> com.android.camera <<<
I/DEBUG   (  732): signal 11 (SIGSEGV), fault addr 00000004
I/DEBUG   (  732):  r0 00000000  r1 00000004  r2 00000000  r3 00000004
I/DEBUG   (  732):  r4 00000000  r5 00000004  r6 4208bcd4  r7 4208bce0
I/DEBUG   (  732):  r8 be9db6d4  r9 4208bcd4  10 4208bcc4  fp 00000000
I/DEBUG   (  732):  ip ad3717d4  sp be9db6b4  lr ac41cf3d  pc ac41ce9e 
cpsr 80000030
I/DEBUG   (  732):          #00  pc 0001ce9e  /system/lib/libui.so
I/DEBUG   (  732):          #01  pc 0001cf38  /system/lib/libui.so
I/DEBUG   (  732):          #02  pc 000328ee  /system/lib/libandroid_runtime.so
I/DEBUG   (  732):          #03  pc 0000e234  /system/lib/libdvm.so
I/DEBUG   (  732): stack:
I/DEBUG   (  732):     be9db674  00000000  
I/DEBUG   (  732):     be9db678  001af4a8  [heap]
I/DEBUG   (  732):     be9db67c  000f4240  [heap]
I/DEBUG   (  732):     be9db680  00000000  
I/DEBUG   (  732):     be9db684  8e6b161c  
I/DEBUG   (  732):     be9db688  00000003  
I/DEBUG   (  732):     be9db68c  be9db6d8  [stack]
I/DEBUG   (  732):     be9db690  4208be40  
I/DEBUG   (  732):     be9db694  be9db708  [stack]
I/DEBUG   (  732):     be9db698  420d0bd8  /dev/ashmem/dalvik-LinearAlloc
(deleted)
I/DEBUG   (  732):     be9db69c  420d0bd8  /dev/ashmem/dalvik-LinearAlloc
(deleted)
I/DEBUG   (  732):     be9db6a0  4313c96e 
/data/dalvik-cache/system@[email protected]@classes.dex
I/DEBUG   (  732):     be9db6a4  ad05ddf9  /system/lib/libdvm.so

Original issue reported on code.google.com by [email protected] on 28 Oct 2009 at 7:49

[deleted issue]

[deleted issue]

ZXing (a barcode scanner application) can't work


1. Enable USB Camera support by following Jim's mail,
http://groups.google.com/group/0xlab-devel/browse_thread/thread/e9316dc1b60b5700
2. Build and install ZXing from
http://zxing.googlecode.com/files/ZXing-1.3.zip 
3. Launch ZXing and sooner enough the application would stop due to an
ArrayIndexOutOfBoundsException.

The logcat log is as below:
E/CameraService(  709): Failed to load CameraService sounds.
D/CameraService(  709): Client X constructor
D/CameraService(  709): Connect X
D/CameraService(  709): setPreviewDisplay(0x47ff0)
D/CameraService(  709): getParameters
E/Camera  ( 1836): _getParameters:
picture-format=jpeg;picture-size=640x480;preview-format=yuv422sp;preview-frame-r
ate=15;preview-size=640x480
E/Camera  ( 1836): setParameters()
D/CameraService(  709):
setParameters(picture-size=640x480;preview-frame-rate=15;preview-size=1024x768;p
icture-format=jpeg;preview-format=yuv422sp)
D/CameraHardware(  709): PREVIEW SIZE: w=1024 h=768 framerate=15
V/CameraManager( 1836): Setting params for preview: width 1024 height 768
D/CameraService(  709): startCameraMode(0)
V/CameraManager( 1836): Calculated framing rect: Rect(224, 96 - 800, 672)
I/ActivityManager( 1043): Displayed activity
com.google.zxing.client.android/.CaptureActivity: 642 ms
D/dalvikvm( 1836): GC freed 1490 objects / 115128 bytes in 130ms
I/dalvikvm-heap( 1836): Grow heap (frag case) to 3.773MB for 614416-byte
allocation
D/dalvikvm( 1836): GC freed 35 objects / 9504 bytes in 153ms
W/dalvikvm( 1836): threadid=23: thread exiting with uncaught exception
(group=0x40010390)
E/AndroidRuntime( 1836): Uncaught handler: thread Thread-12 exiting due to
uncaught exception
E/AndroidRuntime( 1836): java.lang.ArrayIndexOutOfBoundsException
E/AndroidRuntime( 1836):    at
com.google.zxing.client.android.YUVMonochromeBitmapSource.getLuminance(Unknown
Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.common.BaseMonochromeBitmapSource.estimateBlackPoint(Unknown
Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.qrcode.detector.Detector.detect$2365e3e5(Unknown Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.qrcode.QRCodeReader.decode(Unknown Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.MultiFormatReader.decodeInternal(Unknown Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.MultiFormatReader.decodeWithState(Unknown Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.client.android.DecodeThread.access$000(Unknown Source)
E/AndroidRuntime( 1836):    at
com.google.zxing.client.android.DecodeThread$1.handleMessage(Unknown Source)
E/AndroidRuntime( 1836):    at
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1836):    at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1836):    at
com.google.zxing.client.android.DecodeThread.run(Unknown Source)
I/Process ( 1043): Sending signal. PID: 1836 SIG: 3
I/dalvikvm( 1836): threadid=7: reacting to signal 3
I/dalvikvm( 1836): Wrote stack trace to '/data/anr/traces.txt'

Original issue reported on code.google.com by [email protected] on 14 Sep 2009 at 9:33

Generate ubifs system image instead of yaffs2

In beagle-cupcake branch, 0xdroid/0xlab-kernel supports ubifs instead of
yaffs2 file system for NAND flash.  ubifs is actively developed and
performs in impressive shape.  However, 0xdroid build process still
generates yaffs2 image, so extra efforts to generate ubifs are required for
deployment.

Check point:
- enable ubifs in mtd-utils
- drop yaffs2 utilities generation
- generate proper ubifs system image

Original issue reported on code.google.com by [email protected] on 12 Sep 2009 at 11:49

Implement Ethernet monitor in Framework

In order to enable USB networking, not only gadget driver but also Android
Framework gets involved.  Specifically, it is required to implement
Ethernet monitor which accept usbnet interface (typically, it is usb0).

There is already existing one done by rowboat:
  http://gitorious.org/rowboat/frameworks-base

Reference:
  http://wiki.openmoko.org/wiki/USB_Networking

Original issue reported on code.google.com by [email protected] on 3 Nov 2009 at 7:25

straightforward Audio hardware initialization

While generating video thumbview and playback, audio hardware is being 
initialized.  However, it 
is not straightforward:

E/ALSALib ( 1055): 
external/alsa-lib/src/control/control.c:909:(snd_ctl_open_noupdate) Invk
E/AudioHardwareALSA( 1055): Unable to attach mixer to device AndroidPlayback: 
No such filey
E/ALSALib ( 1055): 
external/alsa-lib/src/control/control.c:909:(snd_ctl_open_noupdate) Invd
E/AudioHardwareALSA( 1055): Unable to attach mixer to device AndroidRecord: No 
such file oy
W/HAL     ( 1055): load: module=/system/lib/hw/acoustics.omap3.so error=Cannot 
load librard
E/ALSALib ( 1055): external/alsa-lib/src/pcm/pcm.c:2201:(snd_pcm_open_noupdate) 
Unknown 
PCk
I/AudioHardwareALSA( 1055): Initialized ALSA PLAYBACK device default
I/AudioFlinger( 1055): AudioFlinger's thread ready to run for output 0

From the above log, Audio HAL needs to go through some paths which causes 
delays.

Original issue reported on code.google.com by [email protected] on 29 Oct 2009 at 12:31

Web browser crashes

 when using web browser, it will crash, sometimes this also happen when using the
media player. Here is the log:

I/ActivityManager(  747): Starting activity: Intent
{ action=android.intent.action.MAIN categories=
{android.intent.category.LAUNCHER} flags=0x10200000 comp=
{com.android.browser/com.android.browser.BrowserActivity} }
I/ActivityManager(  747): Start proc com.android.browser for activity
com.android.browser/.BrowserActivity: pid=999 uid=10010 gids={3003}
I/ActivityThread(  999): Publishing provider browser:
com.android.browser.BrowserProvider
E/ActivityThread(  999): Failed to find provider info for
com.google.settings
I/ActivityManager(  747): Displayed activity
com.android.browser/.BrowserActivity: 767 ms
D/InetAddress(  999): www.google.com: 64.233.189.104 (family 2, proto
6)
D/dalvikvm(  999): GC freed 2936 objects / 248416 bytes in 119ms
W/SurfaceComposerClient(  999): lock_layer timed out (is the CPU
pegged?) layer=0, lcblk=0x42087020, state=00000013 (was 00000013)
W/SurfaceComposerClient(  999): lock_layer timed out (is the CPU
pegged?) layer=0, lcblk=0x42087020, state=00000002 (was 00000043)
W/SurfaceComposerClient(  999): lock_layer() timed out but didn't
appear to need to be locked and we recovered (layer=0,
lcblk=0x42087020, state=00000002)
D/dalvikvm(  785): GC freed 1316 objects / 69840 bytes in 49ms
W/IInputConnectionWrapper(  785): showStatusIcon on inactive
InputConnection
I/ActivityManager(  747): Starting activity: Intent
{ action=android.intent.action.VIEW categories=
{android.intent.category.BROWSABLE} data=http://www.google.com/m/news?
client=ms-null comp={com.android.browser/
com.android.browser.BrowserActivity} }
I/DEBUG   (  705): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG   (  705): Build fingerprint: 'beagleboard/beagleboard/
beagleboard/:1.5/CUPCAKE/eng.james.20090916.052719:eng/test-keys'
I/DEBUG   (  705): pid: 999, tid: 1016  >>> com.android.browser <<<
I/DEBUG   (  705): signal 11 (SIGSEGV), fault addr 006e007d
I/DEBUG   (  705):  r0 00000007  r1 ffff0fe0  r2 000002f0  r3 ad03ef70
I/DEBUG   (  705):  r4 ad08ce38  r5 457cdea0  r6 ad0646b0  r7 001f34a0
I/DEBUG   (  705):  r8 48483db0  r9 42086df8  10 42086de8  fp 001c5a80
I/DEBUG   (  705):  ip ad08cf5c  sp 48483cf8  lr 006e0065  pc
ad029210  cpsr 80000030
I/DEBUG   (  705):          #00  pc 00029210  /system/lib/libdvm.so
I/DEBUG   (  705):          #01  pc 00029e02  /system/lib/libdvm.so
I/DEBUG   (  705):          #02  pc 0001192e  /system/lib/
libnativehelper.so
I/DEBUG   (  705):          #03  pc 0001199e  /system/lib/
libnativehelper.so
I/DEBUG   (  705):          #04  pc 00012ea2  /system/lib/
libnativehelper.so
I/DEBUG   (  705):          #05  pc 0000e1b4  /system/lib/libdvm.so
I/DEBUG   (  705): stack:
I/DEBUG   (  705):     48483cb8  fffdb182
I/DEBUG   (  705):     48483cbc  ad08ce38  /system/lib/libdvm.so
I/DEBUG   (  705):     48483cc0  fffdb182
I/DEBUG   (  705):     48483cc4  ad08ce38  /system/lib/libdvm.so
I/DEBUG   (  705):     48483cc8  ad08ddb0  /system/lib/libdvm.so
I/DEBUG   (  705):     48483ccc  428617de  /data/dalvik-cache/
system@[email protected]@classes.dex
I/DEBUG   (  705):     48483cd0  001c5a80  [heap]
I/DEBUG   (  705):     48483cd4  00000001
I/DEBUG   (  705):     48483cd8  00000007
I/DEBUG   (  705):     48483cdc  001f34a0  [heap]
I/DEBUG   (  705):     48483ce0  48483db0
I/DEBUG   (  705):     48483ce4  ad03efd7  /system/lib/libdvm.so
I/DEBUG   (  705):     48483ce8  ad08ce38  /system/lib/libdvm.so
I/DEBUG   (  705):     48483cec  457cdea0  /dev/ashmem/mspace/dalvik-
heap/2 (deleted)
I/DEBUG   (  705):     48483cf0  df002777
I/DEBUG   (  705):     48483cf4  e3a070ad
I/DEBUG   (  705): #00 48483cf8  ad0646b0  /system/lib/libdvm.so
I/DEBUG   (  705):     48483cfc  001f34a0  [heap]
I/DEBUG   (  705):     48483d00  457cdea0  /dev/ashmem/mspace/dalvik-
heap/2 (deleted)
I/DEBUG   (  705):     48483d04  48483d7c
I/DEBUG   (  705):     48483d08  48483db0
I/DEBUG   (  705):     48483d0c  ad029e07  /system/lib/libdvm.so
I/DEBUG   (  705): #01 48483d10  001f34a0  [heap]
I/DEBUG   (  705):     48483d14  457cdea0  /dev/ashmem/mspace/dalvik-
heap/2 (deleted)
I/DEBUG   (  705):     48483d18  457cdea0  /dev/ashmem/mspace/dalvik-
heap/2 (deleted)
I/DEBUG   (  705):     48483d1c  001f34a0  [heap]
I/DEBUG   (  705):     48483d20  00000000
I/DEBUG   (  705):     48483d24  ad211931  /system/lib/
libnativehelper.so
D/Zygote  (  707): Process 999 tbinder: 747:752 transaction failed
29189, size52-0
erminated by signal (11)
I/ActivityManager(  747): Process com.android.browser (pid 999) has
died.
I/WindowManager(  747): WIN DEATH: Window{4580d3b8 com.android.browser/
com.android.browser.BrowserActivity paused=false}
W/InputManagerService(  747): Gobinder: 799:799 transaction failed
29189, size88-0
t RemoteException sending setActive(false) notification to pid 999 uid
10010

Reported by <[email protected]>

Original issue reported on code.google.com by [email protected] on 11 Oct 2009 at 6:25

Re-organize Wiki and project resource representation

Currently, 0xdroid project page is hosted in gitorious.org:
    http://gitorious.org/0xdroid

However, it is hard to customize and edit wiki easily.  Migrating existing
Wiki pages to Google Code site might be a better idea to maintain.

Reference:
    http://code.google.com/p/rowboat/

Rowboat is the Android derived project by Mentor Graphics, and it has
really clear resource representation.

Original issue reported on code.google.com by [email protected] on 30 Oct 2009 at 3:32

Make MIO/omapfb work again for beagle-donut

libopencorehw was working on beagle-cupcake branch as MIO module for
OpenCORE.  It doesn't work since migrating to beagle-donut branch.

Original issue reported on code.google.com by [email protected] on 27 Oct 2009 at 5:34

Video scaling support libopencorehw

Since libopecorehw for OMAP3 is introduced in recent git/repo, it would be
great if video scaling could be implemented.  Various scaling types:
(1) Full screen
(2) x2, x3, x4 from QCIF video
(4) Best fit for screen size

Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 3:39

Ringdroid can't actually record

Audio output on 0xdroid seems to work fine, but audio recording doesn't. 
Running Ringdroid ( http://code.google.com/p/ringdroid/ ) generally will
record, but it records silence. Looking at the output from logcat:

W/AudioRecord(  780): obtainBuffer timed out (is the CPU pegged?)
user=00000000, server=00000000

Reported by Jonathan <[email protected]>

Original issue reported on code.google.com by [email protected] on 13 Aug 2009 at 9:41

Noise frames or afterimage will show up before playing videos.

Using libopencorehw.so device specific MIO plugin, click a video to play,
noise frames or afterimage will show up for seconds before playing the
current video.

Sometimes the images from different played videos even mixed up.

This looks like a synchronization issue and this is happen after forwarding
to Donut.

Original issue reported on code.google.com by [email protected] on 28 Oct 2009 at 7:37

Camera HAL and adaptation for OMAP3

Camera HAL is expected to connect Camera interface to a Video4Linux device
on OMAP3 platform.  It is nice if Camera ISP could be used in Camera HAL
underlying implementation:
    http://www.e-consystems.com/images/blog/OMAP35x_Camera_ISP.jpg

Also, OpenMAX's accelerated JPEG processing driven by TI DSP is known to
bring outstanding performance gain with camera service.

Original issue reported on code.google.com by [email protected] on 4 Sep 2009 at 9:00

Enable USB mass storage mounting on Beagleboard

vold is in charge of volume management. It is expected to support SD card
and USB mass storage mounting. On BeagleBoard?, there is an EHCI (USB 2.0)
slot, and it is known to be able to couple with USB mass storage as the
following messages:

usb 1-2: new high speed USB device using ehci-omap and address 3
usb 1-2: New USB device found, idVendor=090c, idProduct=1000
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: USB Flash Disk
usb 1-2: Manufacturer: General
usb 1-2: configuration #1 chosen from 1 choice

However, vold has to be tweaked in order to support.

It's known to work with mountd instead of vold.

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 6:42

Allow Launcher fit different resolution

when changing the display resolution to 640x480 the bottom button
panel disappears and the yellow drag "handle" for the right panel
seems to be outside the screen (probably below the bottom edge).

Reported by Jesper Nordenberg <[email protected]>

Original issue reported on code.google.com by [email protected] on 22 Oct 2009 at 5:31

cannot link libc_common.a since missing function bzero

If build bionic with compiling option -O0 (no optimization), it failed to
link libc_common.a since missing function bzero.

http://gitorious.org/0xdroid/bionic/commit/764bed3ec856deff9811bc1cbe30dda99ce0f
fba
The commit merge optimzed memset by using memset.c instead of memset.S

However, there is a function 'bzero' which was implemented in memset.S but
not in memset.c.

bionic/libc/bionic/spp.c use the function, bzero, and failed while linking
libc_common.a because bzero was gone.

Original issue reported on code.google.com by [email protected] on 21 Aug 2009 at 7:13

skia benchmark: integration and evaluation

To quantize the recent development efforts for skia, bench tool was introduced. 
 It was not 
included in official Android tree, but found in skia trunk ( 
http://code.google.com/p/skia ).  

Actions:
- Integrated in 0xdroid
- Evaluate the benchmark results, especially for ARM NEON tweaks.

Reference output:
$ ./out/bench/bench -repeat 10
running bench          polygon  8888: 226.40   565: 215.90  4444: 201.50    A8: 
861.50
running bench            lines  8888:  48.50   565:  62.90  4444:  49.70    A8: 
168.60
running bench           points  8888:  11.80   565:  12.90  4444:  14.50    A8: 
 11.60
running bench          rrects3  8888:  21.30   565:  19.70  4444:  29.20    A8: 
 62.00
running bench          rrects1  8888: 103.90   565:  67.40  4444:  72.20    A8: 
192.50
running bench           ovals3  8888:  22.30   565:  20.60  4444:  23.30    A8: 
 51.30
running bench           ovals1  8888:  97.60   565:  75.60  4444:  82.80    A8: 
208.20
running bench           rects3  8888:   4.60   565:   2.70  4444:   1.60    A8: 
  0.70
running bench           rects1  8888:  44.10   565:  21.40  4444:  21.90    A8: 
  3.30
running bench    bitmap_index8  8888: 106.20   565:  28.50  4444: 185.50    A8: 
 33.30
running bench  bitmap_index8_A  8888: 277.50   565: 460.20  4444: 387.40    A8: 
325.90
running bench      bitmap_4444  8888: 183.90   565: 690.50  4444: 411.70    A8: 
 87.60
running bench    bitmap_4444_A  8888: 656.90   565: 888.40  4444: 455.80    A8: 
313.50
running bench       bitmap_565  8888: 354.30   565:   9.30  4444: 472.40    A8: 
 49.90
running bench      bitmap_8888  8888:  13.10   565: 144.80  4444: 201.40    A8: 
 31.40
running bench    bitmap_8888_A  8888: 176.90   565: 241.60  4444: 213.80    A8: 
180.30
running bench repeatTile_index8  8888: 424.00   565: 931.90  4444: 526.40    
A8: 285.80
running bench  repeatTile_4444  8888: 633.00   565: 777.20  4444: 709.80    A8: 
384.30
running bench   repeatTile_565  8888: 450.60   565: 198.40  4444: 677.50    A8: 
  1.80
running bench  repeatTile_8888  8888: 562.80   565: 583.90  4444: 335.90    A8: 
244.10
running bench decode_4444_(null)  8888:   0.00   565:   0.00  4444:   0.00    
A8:   0.00
running bench decode_565_(null)  8888:   0.00   565:   0.00  4444:   0.00    
A8:   0.00
running bench decode_8888_(null)  8888:   0.00   565:   0.00  4444:   0.00    
A8:   0.00

Original issue reported on code.google.com by [email protected] on 26 Oct 2009 at 3:41

Extract touchscreen calibration for Android

During Computex 2009, Tick did a hack to enable touchscreen calibration for
Android. It was performed on SMDK6410 platform with kandroid. There is
still room for improvements, but certainly a good reference for
integration. So, cleaning up and submitting patch is preferable.

Original issue reported on code.google.com by [email protected] on 12 Aug 2009 at 10:43

Use GTA02 GSM Passthrough mode as external Android GSM modem

We need the presence GSM modem for Android to verify several functions such
as Bluetooth profile and RIL. It is fairly useful to enable GTA02 GSM
Passthrough mode as external Android GSM modem.

Reference:
    http://unadventure.wordpress.com/2007/10/28/qpe-430-plus-qemu/
    http://sourceforge.net/projects/sercd/
    http://sourceforge.net/projects/cyclades-serial/

http://blogs.gnome.org/thos/2007/10/30/turning-the-neo1973-into-an-expensive-ext
ernal-gsm-modem/
    http://wiki.openmoko.org/wiki/Gsmd/document

The expected usage scenario:

    * Minimal Linux kernel + initramfs runs on GTA02 and performs the
required system initializations including UARTs.
    * Userspace program attempts to redirect UART to GSM modem
(/dev/ttySAC0) connections to USB network.
    * Beagleboard connects to GTA02 via USB wire, and it makes the
communications with each other. 

Quick hacking note:

On Neo

root@om-gta02:/sys# echo 1 > /sys/devices/platform/neo1973-pm-gsm.0/power_on
root@om-gta02:~# nc -l -p 4270 < /dev/ttySAC0 > /dev/ttySAC0 &
root@om-gta02:~# nc -l -p 4271 < /dev/input/event3 &

On beagleboard

    pty 192.168.0.202 4270 &
    nc 192.168.0.202 4271

Where pty.c located at
http://svn.openmoko.org/trunk/src/host/qemu-neo1973/pty.c 

RIL implementation for FreeRunner?/GTA02 :


http://git.koolu.org/?p=platform/hardware/ril.git;a=shortlog;h=refs/heads/donut

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 6:46

Attachments:

gsm-passthrough.png

Introduce customized theme

Although there are already several themes available for Android variants,
such as Cyanogen ROM ( http://www.cyanogenmod.com/downloads/themes ), it
still comes with the following problems:
- No explicit open source compatible license for these art-work creations.
- Relevant Compatibility issue for Home / Launcher application.  Behavior
changes and resource lacks though.

So, to understand these in detail, it is better for us to create new theme
/ art-work.

Guidelines:
* The theme should be finger friendly.
* The theme should look good.
* The theme should be consistent.
* The theme should not break usability.
* The theme should not be slow. (at least, visibily)

The preferable license terms: Creative Commons.  Also, supporting VGA
resolution would be great, and then we can contribute to Android on
Freerunner project ( http://code.google.com/p/android-on-freerunner/ ).

Original issue reported on code.google.com by [email protected] on 22 Oct 2009 at 6:20

Fix signal strength issues with WEXT devices

Recently, Timothy Chick submitted patches to Android for fixing signal
strength issues with WEXT (Linux Wireless Extension) devices.  To
evaluating bcm4325 and sdio8688, it is quite important.

Patch:
    https://review.source.android.com/#change,11689

Original issue reported on code.google.com by [email protected] on 22 Oct 2009 at 4:01

Video recording should work

In used beagle-cupcake branch, video recording doesn't work fairly.
After migrating to beagle-donut,  video recording should be addressed and
expected to work.

Camcorder should work to record the video.

Original issue reported on code.google.com by [email protected] on 3 Nov 2009 at 1:53

System latency analysis

Recent ARM-Linux kernel comes with latencytop (
http://hub.opensolaris.org/bin/view/Project+latencytop/ ) support, and
there is an utility /system/xbin/latencytop in Android environment.  To
analyze the running system in detail, latencytop is neat to discover. 
Consider the following applications at least.
(1) Video playback
(2) Camera preview / recording
(3) Web browsing

There should be a primitive report after finishing this task.

Kernel configuration:
- CONFIG_HAVE_LATENCYTOP_SUPPORT=y
- CONFIG_LATENCYTOP=y

Original issue reported on code.google.com by [email protected] on 27 Oct 2009 at 3:11

[deleted issue]

[deleted issue]

beagle-donut build fails on Ubuntu lucid (10.04)

beagle-donut branch in 0xdroid can not be built on Ubuntu lucid (10.04):

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=1.6
TARGET_PRODUCT=beagleboard
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=Donut
============================================
build/core/copy_headers.mk:15: warning: overriding commands for target
`out/target/product/beagleboard/obj/include/libpv/getactualaacconfig.h'
build/core/copy_headers.mk:15: warning: ignoring old commands for target
`out/target/product/beagleboard/obj/include/libpv/getactualaacconfig.h'
make: *** No rule to make target
`out/host/linux-x86/obj/STATIC_LIBRARIES/liblog_intermediates/liblog.a',
needed by `out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt'.  Stop.

Original issue reported on code.google.com by [email protected] on 18 Nov 2009 at 4:19

[deleted issue]

[deleted issue]

Integrate MadButterfly into Android

Basic MadButterfly integrations for Android:
- SVG rendering on Android Surface directly managed by SurfaceFlinger.
- Event handling via EventHub (at least for input key events).
- Standalone test suite plus (simple) Java interface.

Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 4:08

Add Theme selector

Let Launcher support selecting a theme then read resource from outer package.

Original issue reported on code.google.com by [email protected] on 18 Nov 2009 at 5:55

Ethernet tracker causes system crash during booting

While Ethernet tracker manages usb0, it causes system crash during booting.

adb logcat:
V/ConnectivityService(  795): Handle CONNECT for ETH
V/ConnectivityService(  795): Sending CONNECT bcast for ETH
E/ActivityManager(  795): Attempt to launch receivers of broadcast intent 
Intent { 
act=android.net.conn.CONNECTIVITY_CHANGE (has extras) } before boot completion
W/dalvikvm(  795): threadid=43: thread exiting with uncaught exception 
(group=0x4001b1e0)
E/AndroidRuntime(  795): Uncaught handler: thread ConnectivityThread exiting 
due to uncaught 
exception
I/SystemServer(  795): Starting Audio Service
E/AndroidRuntime(  795): *** EXCEPTION IN SYSTEM PROCESS.  System will crash.
E/AndroidRuntime(  795): java.lang.IllegalStateException: Cannot broadcast 
before boot 
completed
E/AndroidRuntime(  795):    at 
com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerServ
ice.java:1131
1)
E/AndroidRuntime(  795):    at 
android.app.ApplicationContext.sendStickyBroadcast(ApplicationContext.java:731)
E/AndroidRuntime(  795):    at 
com.android.server.ConnectivityService.sendConnectedBroadcast(ConnectivityServic
e.java:533)
E/AndroidRuntime(  795):    at 
com.android.server.ConnectivityService.handleConnect(ConnectivityService.java:66
2)
E/AndroidRuntime(  795):    at 
com.android.server.ConnectivityService.access$500(ConnectivityService.java:48)
E/AndroidRuntime(  795):    at 
com.android.server.ConnectivityService$MyHandler.handleMessage(ConnectivityServi
ce.java:81
5)
E/AndroidRuntime(  795):    at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(  795):    at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(  795):    at 
com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityServic
e.java:92)
D/dalvikvm(  795): GC freed 3217 objects / 225648 bytes in 72ms
I/Process (  795): Sending signal. PID: 795 SIG: 9

Original issue reported on code.google.com by [email protected] on 12 Nov 2009 at 9:30

ffmpeg to OpenCore with OpenMAX interface

Thinker tred to make opencore can play WMV.  It seems that opencore can not
recoganize WMV even we have given codec to them.  OpenCore separates
iplementation of recoganizer and codec nodes. We have codec in OMX,now.
But, we also need recoganizer. It takes time to figure out how to implement
a recoganizer with OMX.

Original issue reported on code.google.com by [email protected] on 12 Aug 2009 at 10:51

USB does not alway work on beagle-cupcake-0x2

The subject is misleading.  It is a matter of USB subsystem.

Original issue reported on code.google.com by ticktock35 on 12 Oct 2009 at 3:01

Add Bluetooth OPP, FTP profiles in beagle-donut

Like I implemented in Android Dev phone, I want to apply it in Beagle board
too. Detailed description is here:
http://i-miss-erin.blogspot.com/2009/10/how-to-have-obex-function-in-android.htm
l

Original issue reported on code.google.com by erinyueh on 23 Nov 2009 at 5:15

Integrated Android Settings for Bluetooth HID (keyboard/mouse)

As the demo video ( http://www.youtube.com/watch?v=v6wdTOHrwQw ) shows, the
Bluetooth HID profile starts to work under 0xdroid, and BT keyboard/mouse
could be connected as uinput that triggers the motion of EventHub. 
However, there is no integrated Android settings for BT HID.

Original issue reported on code.google.com by [email protected] on 3 Sep 2009 at 6:31

mediaserver crashes after finishing video recording

Sometimes mediaserver crashes after stopping the video recording.

Below is a reference log.

E/ALSALib ( 1258): external/alsa-lib/src/pcm/pcm.c:7231:(snd_pcm_recover)
overrun occured
E/ALSALib ( 1258): external/alsa-lib/src/pcm/pcm.c:7231:(snd_pcm_recover)
overrun occured
V/videocamera( 1139): stopVideoRecording
D/CameraService( 1258): stopRecording (pid 1258)
D/CameraService( 1258): stopRecording(), hardware stopped OK
D/AcousticsModule( 1258): Acoustics close stub called.
D/CameraService( 1258): unlock from pid 1258 (mClientPid 1258)
D/CameraService( 1258): clear mCameraClient (pid 1258)
D/CameraService( 1258): Client::disconnect() E (pid 1258 client 0x0)
D/CameraService( 1258): camera is unlocked (mClientPid = 0), don't tear
down hardware
V/videocamera( 1139): Setting current video filename:
/sdcard/DCIM/Camera/video-2000-01-01-00-55-39.3gp
V/videocamera( 1139): Releasing media recorder.
V/videocamera( 1139): Current video URI:
content://media/external/video/media/94
I/DEBUG   ( 1257): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** ***
I/DEBUG   ( 1257): Build fingerprint:
'beagleboard/beagleboard/beagleboard/:1.6/Donut/eng.jeremy.20091110.095311:eng/t
est-keys'
I/DEBUG   ( 1257): pid: 1258, tid: 1276  >>> /system/bin/mediaserver <<<
I/DEBUG   ( 1257): signal 11 (SIGSEGV), fault addr 00000000
I/DEBUG   ( 1257):  r0 a6eac951  r1 00000313  r2 409a0e7c  r3 00000000
I/DEBUG   ( 1257):  r4 00036950  r5 a96a6598  r6 000369d0  r7 409a0e7c
I/DEBUG   ( 1257):  r8 00100000  r9 a9d2b6c5  10 408a1000  fp 00037040
I/DEBUG   ( 1257):  ip 00000000  sp 409a0e68  lr a9684b55  pc 00000000 
cpsr 80000010
I/DEBUG   ( 1257):          #00  pc 00000000  
I/DEBUG   ( 1257):          #01  pc 00004b52  /system/lib/libcamera.so
I/DEBUG   ( 1257): stack:
I/DEBUG   ( 1257):     409a0e28  405d2280  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e2c  40594201  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e30  405940a1  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e34  40594200  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e38  405940a0  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e3c  405d2543  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e40  405d1fc3  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e44  405d2541  /dev/ashmem/MemoryHeapBase (deleted)
I/DEBUG   ( 1257):     409a0e48  00036f44  [heap]
I/DEBUG   ( 1257):     409a0e4c  a9d23671  /system/lib/libutils.so
I/DEBUG   ( 1257):     409a0e50  00036f44  [heap]
I/DEBUG   ( 1257):     409a0e54  a9d236c7  /system/lib/libutils.so
I/DEBUG   ( 1257):     409a0e58  00036950  [heap]
I/DEBUG   ( 1257):     409a0e5c  a96a6598  /system/lib/libcamera.so
I/DEBUG   ( 1257):     409a0e60  df002777  
I/DEBUG   ( 1257):     409a0e64  e3a070ad  
I/DEBUG   ( 1257): #01 409a0e68  00000120  
I/DEBUG   ( 1257):     409a0e6c  00000000  
I/DEBUG   ( 1257):     409a0e70  00000000  
I/DEBUG   ( 1257):     409a0e74  00000000  
I/DEBUG   ( 1257):     409a0e78  00037028  [heap]
I/DEBUG   ( 1257):     409a0e7c  00036f28  [heap]
I/DEBUG   ( 1257):     409a0e80  0003701c  [heap]
I/DEBUG   ( 1257):     409a0e84  00000000  
I/DEBUG   ( 1257):     409a0e88  00000000  
I/DEBUG   ( 1257):     409a0e8c  00036ff8  [heap]
I/DEBUG   ( 1257):     409a0e90  00036ff8  [heap]
I/DEBUG   ( 1257):     409a0e94  409a0eb0  
I/DEBUG   ( 1257):     409a0e98  409a0eb4  
I/DEBUG   ( 1257):     409a0e9c  a9684c55  /system/lib/libcamera.so
I/DEBUG   ( 1257):     409a0ea0  00036ff8  [heap]
I/DEBUG   ( 1257):     409a0ea4  a9d2b34f  /system/lib/libutils.so
I/DEBUG   ( 1257):     409a0ea8  00036ff8  [heap]
I/DEBUG   ( 1257):     409a0eac  00037028  [heap]
E/SW_DEC  ( 1258): PV SW DECODER is used for H.263
I/DEBUG   ( 1257): debuggerd committing suicide to free the zombie!
I/DEBUG   ( 1283): debuggerd: Nov 11 2009 19:22:56
binder: release 1258:1258 transaction 26854 in, still active
binder: send failed reply for transaction 26854 to 1139:1139
W/AudioSystem(  802): AudioFlinger server died!
W/MediaMetadataRetriever( 1139): MediaMetadataRetriever server died!
W/Camera  ( 1139): Camera server died!
W/Camera  ( 1139): ICamera died
E/MediaMetadataRetrieverJNI( 1139): captureFrame: videoFrame is a NULL pointer
V/videocamera( 1139): initializeRecorder
V/videocamera( 1139): Releasing media recorder.
I/ServiceManager(  760): service 'media.audio_flinger' died
I/ServiceManager(  760): service 'media.player' died
I/ServiceManager(  760): service 'media.camera' died
I/ServiceManager( 1139): Waiting for sevice media.player...

Original issue reported on code.google.com by [email protected] on 12 Nov 2009 at 1:15

YouTube is not playable in WebKit.

While using Web Browser (com.android.browser) to Google Video 
(video.google.com) site, 
YouTube video clip could not playable, but the preview image did appear.

logcat:
E/browser (  999): onReceivedError -10 vnd.youtube:K6UX8Dd0G8Y The protocol is 
not support.
D/skia    (  999): purging 204K from font cache [12 entries]

Soon, the preview image is going to hide, and then it left blank.

Original issue reported on code.google.com by [email protected] on 6 Nov 2009 at 4:18

Import ffmpeg-android into 0xdroid repository

In the past, olv hacked ffmpeg to allow it working on Android as service
and rendering video on Android surface.

http://gitorious.org/~olvaffe/ffmpeg/ffmpeg-android
http://gitorious.org/~olvaffe/libswscale/libswscale-android

It's time to move back these efforts into 0xdroid.  Directory
externals/mplayer should be good.

Original issue reported on code.google.com by [email protected] on 18 Aug 2009 at 8:00

Integrate ST LIS302 sensor into Android

LIS302 sensors provide three axis motion sensing in a tiny 3 mm x 5 mm x
0.9 mm plastic package.
    * With power consumption around 1 mW, these devices measure
acceleration of ± 8 g, and feature an SPI/I2C digital interface and two
independent programmable interrupt signals
    * With these interrupts, either two different states or two different
thresholds can be monitored, giving the device more flexibility for
designers to distinguish between states such as free fall and rolling

Task: enable LIS302 sensor in Android
Interface: I2C

Original issue reported on code.google.com by [email protected] on 24 Nov 2009 at 10:25

No incoming call UI in home screen and cannot dial out from Dialer

What steps will reproduce the problem?
1. Reboot beagle board, plug-in NEO GTA02 as external modem
2. wait until camp to GSM network
3. Dial out a call from other phone to Beagle board
4. can see Ring from modem radio log, but no response from UI part

What is the expected output? What do you see instead?
Should appear an incoming call UI

Please use labels and text to provide additional information.
After tracing the radio and UI log, it seems like we queue a list of
request modem commands from framework side. 

I will keep tracing the source code and also verify it in Android emulator
again.

Original issue reported on code.google.com by erinyueh on 12 Nov 2009 at 7:24

Turn off display during idle on BeagleBoard

Android BeagleBoard? porting doesn't turn off LCD panel during idle. Check
the source file: hardware/libhardware_legacy/power/power.c for correcting this.

Original issue reported on code.google.com by [email protected] on 11 Aug 2009 at 7:04

Attachments:

power-enable-lcd-blank.patch

pianyu / 0xdroid Goto Github PK

0xdroid's People

Contributors

0xdroid's Issues

Recommend Projects

Recommend Topics

Recommend Org