Cannot open the Camera

Can you try downloading and replacing ducati-m3.bin binary from next location?

http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries

check the section for Blaze or Blaze tablet depending on what version you are using.

The binary is located in /system/vendor/firmware/ducati-m3.bin in your target device.

You can use ./adb push to upload the file.

You can dump error logs using the information from

http://omapedia.org/wiki/Debugging_RPMsg

Hi Manuel,

Thanks for your reply. Since I built the file system using lunch full_blaze-userdebug, it is a read only file system and doesn't let me push the ducati.bin file.

I am rebuilding the file system using lunch full_blaze-eng and then will try pushing this file. 

Where in the file system should I place the ducati binary on my host machine so that the new file system builds with the updated Ducati file?

Also meanwhile, I got adb to work and this are the error messages. It seems there is no camera to connect to? Did I miss out somehow to build the camera?

01-02 02:59:23.648: I/ActivityManager(187): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera bnds=[60,370][219,481]} from pid 396
01-02 02:59:23.812: I/InputReader(187): Reconfiguring input devices. changes=0x00000004
01-02 02:59:23.812: I/InputReader(187): Device reconfigured: id=8, name='syn_tm12xx_ts_2', surface size is now 864x480, mode is 1
01-02 02:59:23.812: I/InputReader(187): Device reconfigured: id=9, name='syn_tm12xx_ts_1', surface size is now 864x480, mode is 1
01-02 02:59:23.859: I/ActivityManager(187): Config changed: {1.0 0mcc0mnc en_US layoutdir=0 sw320dp w320dp h550dp nrml long port finger qwerty/v/v dpad/v s.23}
01-02 02:59:23.867: D/OpenGLRenderer(272): Flushing caches (mode 0)
01-02 02:59:23.867: D/OpenGLRenderer(272): Flushing caches (mode 0)
01-02 02:59:23.906: V/CameraHolder(670): open camera 0
01-02 02:59:23.906: E/CameraService(126): CameraService::connect X (pid 670) rejected (invalid cameraId 0).
01-02 02:59:23.906: E/CameraHolder(670): fail to connect Camera
01-02 02:59:23.906: E/CameraHolder(670): java.lang.RuntimeException: Fail to connect to camera service
01-02 02:59:23.906: E/CameraHolder(670): at android.hardware.Camera.native_setup(Native Method)
01-02 02:59:23.906: E/CameraHolder(670): at android.hardware.Camera.<init>(Camera.java:302)
01-02 02:59:23.906: E/CameraHolder(670): at android.hardware.Camera.open(Camera.java:264)
01-02 02:59:23.906: E/CameraHolder(670): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
01-02 02:59:23.906: E/CameraHolder(670): at com.android.camera.Util.openCamera(Util.java:267)
01-02 02:59:23.906: E/CameraHolder(670): at com.android.camera.Camera$4.run(Camera.java:1100)
01-02 02:59:23.906: E/CameraHolder(670): at java.lang.Thread.run(Thread.java:856)
01-02 02:59:23.984: D/OpenGLRenderer(396): Flushing caches (mode 1)
01-02 02:59:23.992: D/OpenGLRenderer(396): Flushing caches (mode 0)
01-02 02:59:24.000: D/dalvikvm(482): GC_CONCURRENT freed 184K, 3% free 9213K/9479K, paused 2ms+4ms
01-02 02:59:24.210: V/camera(670): surfaceChanged. w=480. h=640
01-02 02:59:24.273: I/Process(187): Sending signal. PID: 670 SIG: 3
01-02 02:59:24.273: I/dalvikvm(670): threadid=3: reacting to signal 3
01-02 02:59:24.273: D/OpenGLRenderer(396): Flushing caches (mode 0)
01-02 02:59:24.273: I/dalvikvm(670): Wrote stack traces to '/data/anr/traces.txt'
01-02 02:59:24.398: I/ActivityManager(187): Displayed com.android.camera/.Camera: +628ms
01-02 02:59:26.531: D/dalvikvm(187): GC_EXPLICIT freed 200K, 17% free 11520K/13767K, paused 7ms+14ms
01-02 02:59:26.992: I/InputReader(187): Reconfiguring input devices. changes=0x00000004
01-02 02:59:26.992: I/InputReader(187): Device reconfigured: id=8, name='syn_tm12xx_ts_2', surface size is now 864x480, mode is 1
01-02 02:59:26.992: I/InputReader(187): Device reconfigured: id=9, name='syn_tm12xx_ts_1', surface size is now 864x480, mode is 1
01-02 02:59:27.046: I/ActivityManager(187): Config changed: {1.0 0mcc0mnc en_US layoutdir=0 sw320dp w576dp h294dp nrml long land finger qwerty/v/v dpad/v s.24}
01-02 02:59:27.054: D/OpenGLRenderer(272): Flushing caches (mode 0)
01-02 02:59:27.062: D/OpenGLRenderer(272): Flushing caches (mode 0)
01-02 02:59:27.156: W/SurfaceTexture(123): [com.android.camera/com.android.camera.Camera] cancelBuffer: SurfaceTexture has been abandoned!
01-02 02:59:27.226: W/InputManagerService(187): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4144a308
01-02 02:59:27.289: D/OpenGLRenderer(670): Flushing caches (mode 1)
01-02 02:59:27.343: D/dalvikvm(670): GC_EXPLICIT freed 204K, 6% free 10218K/10823K, paused 2ms+4ms
01-02 02:59:27.453: D/dalvikvm(272): GC_FOR_ALLOC freed 6292K, 43% free 9729K/16903K, paused 21ms
01-02 02:59:27.460: I/dalvikvm-heap(272): Grow heap (frag case) to 12.505MB for 3072016-byte allocation
01-02 02:59:27.500: D/dalvikvm(272): GC_CONCURRENT freed 8K, 25% free 12720K/16903K, paused 2ms+2ms
01-02 02:59:27.593: D/dalvikvm(272): GC_FOR_ALLOC freed 0K, 25% free 12720K/16903K, paused 22ms
01-02 02:59:27.601: I/dalvikvm-heap(272): Grow heap (frag case) to 15.661MB for 3317776-byte allocation
01-02 02:59:27.640: D/dalvikvm(272): GC_CONCURRENT freed 0K, 6% free 15960K/16903K, paused 4ms+3ms
01-02 02:59:29.476: D/dalvikvm(187): GC_EXPLICIT freed 191K, 17% free 11501K/13767K, paused 7ms+7ms

Thanks,

Palak

I usually use one of these 3 procedures

1.For 4AI.1.7 the file to modify is located in

/mydroid/device/ti/proprietary-open/omap4/ducati_full_blaze.tgz

you need to compress ducati-m3.bin binary in a tgz file and use the same name.

you can find the tools in

/mydroid/out/host/linux-x86/bin/

2.To modify a system.img follow the instructions in next link,

http://omapedia.org/wiki/Android_eMMC_Booting

an extra comment for boot.img modification, the bootargs by default are taken from .config file, if you need to use the ones fro the boot.img use CONFIG_CMDLINE_FROM_BOOTLOADER=y and CONFIG_CMDLINE_EXTEND=n, for boot.img you can use umulti.sh to recreate the image (http://omapedia.org/wiki/Using_EMMC_on_OMAP4_devices).

http://omapedia.org/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes#Preparing_eMMC_images

3. when the Blaze boots with Android system running you can call ./adb root command and ./adb remount to put it into rw mode, the root directory is read only (init.rc) but you can modify and create file inside other folders when using root user. Sometimes from the computer it is needed to run the commands twice or use sudo command to get correct configuration for example 4AI1.7.

For the part of the shared log, you can try using the prebuild binaries to check if system is ok.