android - Commonsware camera preview demo: no preview after device on/off -


i see bug: when camera in preview mode, , user presses on/off, camera preview stops , not start.

an obvious suggestion see other people do; have consulted https://github.com/commonsguy/cw-advandroid/tree/master/camera/preview/ , see demo has same bug (android 4.0.3).

a direct link java source: https://github.com/commonsguy/cw-advandroid/blob/master/camera/preview/src/com/commonsware/android/camera/previewdemo.java

question: how can 1 fix bug? preview mode must working after device on/off.

upd: bug not show if first change activity , press on/off on activity.

upd2: after on/off, startpreview() invoked, see message system:

d/@@    (13428): startpreview() cameraconfigured=true camera=android.hardware.camera@412f66f0 e/camhw ( 2135): preview window null!

which means bad happen in depths of system (although message may device-specific).

udp3: after on/off, no method surfacecallback invoked. maybe makes difference.

upd4: [seen not @ camera demo] if switch different application (by long-pressing home , choosing list) , switch back, camera works again.

it not solution, workaround: invoke setcontentview() in onresume().

it can either

protected void onresume() {     super.onresume();     setcontentview(r.layout.xxx);     // ... }

or

private view cachedcontentview; protected void oncreate(bundle savedinstancestate) {     super.oncreate(savedinstancestate);     cachedcontentview = docreatecontentview(getlayoutinflater());     // ... } protected void onresume() {     super.onresume();     setcontentview(cachedcontentview);     // ... }

both of them work.

i still have no idea causes problem , the difference between original example , library.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more