Re: Camera not working on ICS 4.03 / Maguro

[Ron M]

Same issue on Wingray (Motorola XOOM-wifi).
Can anyone from google please address this issue?

Thanks,
Ron

On Thu, Jan 26, 2012 at 6:33 PM, Ron M <ron...@gmail.com> wrote:
> I posted a similar question as a reply to JBQ "4.03" release thread,
> but I think it is more appropriate to have a new topic for this
> paticular question:
>
> I tried to build both the Master branch, repo synced today, and the
> android-4.03_r1 branch (Applied "repo forall -c git checkout
> android-4.0.3_r1" on my AOSP directory/make clobber/rebuild), after
> extracting both propiatery binaries
> (samsung-maguro-iml74k-de1cc439.tgz
> imgtec-maguro-iml74k-a796ffae.tgz  )
>
> The camera isn't working. I didnt not see the logcat on the Master
> branch build, but when I tried the other build, I saw the following
> crash:
> Is it a known issue? Is there anyway I can make the Camera work with
> AOSP code on galaxy nexus, using the "vanilla" AOSP project code and
> the suggested binaries?
>
> Thanks,
> Ron
>
>
> I/ActivityManager(  207): START {act=android.intent.action.MAIN
> cat=[android.intent.category.LAUNCHER] flg=0x10200000
> cmp=com.android.camera/.Camera} from pid 622
> I/ActivityManager(  207): Start proc com.android.camera for activity
> com.android.camera/.Camera: pid=1175 uid=10007 gids={1006, 1015}
> D/OpenGLRenderer(  622): Flushing caches (mode 1)
> E/CameraHAL(  121): Couldn't get camera properties
> W/dalvikvm( 1175): threadid=11: thread exiting with uncaught exception
> (group=0x40a2d1f8)
> D/OpenGLRenderer(  622): Flushing caches (mode 0)
> E/AndroidRuntime( 1175): FATAL EXCEPTION: Thread-99
> E/AndroidRuntime( 1175): java.lang.RuntimeException: Fail to get camera info
> E/AndroidRuntime( 1175):        at
> android.hardware.Camera.getCameraInfo(Native Method)
> E/AndroidRuntime( 1175):        at
> com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
> E/AndroidRuntime( 1175):        at
> com.android.camera.CameraHolder.instance(CameraHolder.java:66)
> E/AndroidRuntime( 1175):        at com.android.camera.Util.openCamera(Util.java:267)
> E/AndroidRuntime( 1175):        at com.android.camera.Camera$4.run(Camera.java:1100)
> E/AndroidRuntime( 1175):        at java.lang.Thread.run(Thread.java:856)
> W/ActivityManager(  207):   Force finishing activity com.android.camera/.Camera
> D/dalvikvm( 1175): GC_CONCURRENT freed 228K, 3% free 12833K/13127K,
> paused 6ms+3ms
> D/dalvikvm( 1175): GC_FOR_ALLOC freed 10K, 2% free 12887K/13127K, paused 11ms
> I/dalvikvm-heap( 1175): Grow heap (frag case) to 13.278MB for
> 662416-byte allocation
> D/dalvikvm( 1175): GC_FOR_ALLOC freed 2K, 3% free 13531K/13831K, paused 22ms
> D/dalvikvm( 1175): GC_FOR_ALLOC freed 20K, 2% free 13878K/14087K, paused 12ms
> D/dalvikvm( 1175): GC_FOR_ALLOC freed 5K, 2% free 14252K/14471K, paused 12ms
> E/CameraHAL(  121): Couldn't get camera properties
> D/AndroidRuntime( 1175): Shutting down VM
> W/dalvikvm( 1175): threadid=1: thread exiting with uncaught exception
> (group=0x40a2d1f8)
> I/Process ( 1175): Sending signal. PID: 1175 SIG: 9
> I/ActivityManager(  207): Process com.android.camera (pid 1175) has died.
> W/InputManagerService(  207): Window already focused, ignoring focus
> gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@416e3ad8
> D/dalvikvm(  622): GC_CONCURRENT freed 3468K, 41% free 16704K/28103K,
> paused 2ms+4ms
> D/dalvikvm(  622): GC_FOR_ALLOC freed 322K, 42% free 16459K/28103K, paused 22ms
> I/dalvikvm-heap(  622): Grow heap (frag case) to 17.702MB for
> 1644560-byte allocation
> D/dalvikvm(  622): GC_FOR_ALLOC freed <1K, 36% free 18064K/28103K, paused 27ms
> D/dalvikvm(  622): GC_CONCURRENT freed 0K, 36% free 18064K/28103K,
> paused 2ms+5ms
> D/dalvikvm(  622): GC_FOR_ALLOC freed 1687K, 36% free 18006K/28103K, paused 25ms
> D/dalvikvm(  622): GC_FOR_ALLOC freed 1617K, 37% free 17854K/28103K, paused 30ms
> D/dalvikvm(  622): GC_CONCURRENT freed 832K, 34% free 18788K/28103K,
> paused 2ms+2ms
> D/dalvikvm(  207): GC_CONCURRENT freed 802K, 17% free 15286K/18375K,
> paused 3ms+5ms
>
>
>
> I have been t

[Jean-Baptiste Queru]

That's up to Motorola, actually.

JBQ

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private will likely get ignored or forwarded to a public forum with no further warning.

[Ron M]

And what about the Galaxy Nexus, which is the development flagship device?

[Jean-Baptiste Queru]

That's up to TI. I hear there's progress on that front, but I don't
know exactly how far along we are.

JBQ

[Ron M]

So the AOSP officialy does not support Camera, even when extracting
the two propietary binaries?
Can you please confirm, or deny?

Do you think that running device/.../extract_files.sh on a stock
factory image (on googlecode's nexus page, e.g. extracting from
ICL53F) can make some of these features work for IML74K - or would
you expect mismatches?

Is there any place where I can "official" information about the
structure of AOSP vs. Binaries vs. Some other libraries etc. ? Design
consideration maybe?
There is tons of stuff on XDA etc. - but I am not sure how appropriate
it is to discuss it over this forum.

Regards,
Ron

[Jean-Baptiste Queru]

My notes suggest that I haven't tried using my extract-files.sh script
in probably about 6 months, since I moved to using the distributable
self-extractors in late July. extract-files.sh is my own private tool
anyway, used during development of the self-extractors, it's not meant
to be used by the general public, especially because of licensing
issues.

I had tested with the TI self-extractor (which I'm not allowed to
distribute), and I believe that in those conditions the camera works.

Also, while using the steps described at http://goo.gl/8jit8 the
camera works on Maguro. I'd appreciate getting some feedback about
that process.

JBQ

[Ron M]

I am eager to try that and will give it a shot ASAP.
The thing is that I am using my personal phone for that, and am
traumatized after my last unintetional data wipe (forgot that fastboot
oem unlock wipes everything :-( ) .

What would be the easiest backup method (i.e. "ghost", for my Galaxy
Nexus...), straight off AOSP?
Should "adb backup/restore" indeed backup everything needed in
terms of also SMS messages, app data etc.?

Thanks,
Ron

[Jean-Baptiste Queru]

Sadly the world of AOSP is a world of wiping devices clean all the time :-(

adb backup might be one option. rawbu might be another. I'm not
familiar enough with either to be able to tell you anything specific
about them.

JBQ

[Pau Oliva]

Hi Ron,

The best solution for backup/restore I've found to be able to try AOSP
on your personal phone is to use a custom recovery image that allows for
"nandroid backups". You can find links to custom recoveries from Koushik
Dutta here:

http://clockworkmod.com/rommanager

source available here:

https://github.com/CyanogenMod/android_bootable_recovery

These recoveries have an option available to make a backup of all your
partitions on /sdcard, which you can then use to restore them and return
the phone to the exact same state it was before you wiped it to install
AOSP.

Hope this helps!

Cheers,

Pau Oliva