GoogleCodeExporter
commented
9 years ago Need app launcher solution..Original comment by jgdes...@gmail.com on 17 Apr 2014 at 6:24
Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago Need app launcher solution..Original comment by jgdes...@gmail.com on 17 Apr 2014 at 6:24
GoogleCodeExporter
commented
9 years ago Original comment by ala...@google.com on 17 Apr 2014 at 8:39
GoogleCodeExporter
commented
9 years ago Original comment by ala...@google.com on 23 Apr 2014 at 11:07
GoogleCodeExporter
commented
9 years ago We've found an effective workaround for this problem, basically in the
onPictureTaken callback you have to completely teardown your camera including
all previewCallBacks, PreviewDisplay, etc. Then you recreate and start your
camera again.
mCamera.takePicture(new ShutterCallback() {
public void onShutter() {
}
}, new PictureCallback() {
public void onPictureTaken(byte[] arg0, Camera arg1) {
}
}, new PictureCallback() {
public void onPictureTaken(byte[] data, Camera camera) {
// Do some processing...
stopCamera();
initCamera();
startCamera(mCamSH);
mCamera.startPreview();
}
}); Original comment by npilking...@ethos.com on 1 May 2014 at 5:53
GoogleCodeExporter
commented
9 years ago Sometimes glass gets freezed with frequent usage of camera service. It tends to
hard reboot the glass manually. I might think, it's the problem in camera
release call. I hope it might be a bug in gdk camera api. If I'm wrong, let me
suggest the possible way to fix the same.Original comment by ssenthil...@gmail.com on 7 May 2014 at 2:18
GoogleCodeExporter
commented
9 years ago We are currently facing the same issue.
The workaround proposed works sometimes, but globally we need to reboot very
often.
It's a pain in the ass.
Any other idea how to fix it ?
Original comment by willie.r...@gmail.com on 16 May 2014 at 1:48
GoogleCodeExporter
commented
9 years ago I'm experiencing the same problem. The workaround doesn't seem to prevent the
problem altogether. I'm looking forward to a permanent fix!Original comment by hannings...@gmail.com on 29 May 2014 at 4:21
GoogleCodeExporter
commented
9 years ago This is affecting us too. Given the camera is a core feature of Google Glass,
this issue appears to be impossible to work around and it has negative user
side effects (system crash) - any chance we could get it bumped up a priority
level? :)Original comment by nickge...@gmail.com on 29 May 2014 at 4:40
GoogleCodeExporter
commented
9 years ago I agree with the above comment. The workaround we found and posted here works
just long enough to get through a demo of our project, but does not resolve the
issue for prolonged normal use.
It feels like this issue should get bumped up since the the camera is a really
important part of the Glass experience.Original comment by npilking...@ethos.com on 29 May 2014 at 4:58
GoogleCodeExporter
commented
9 years ago This seems to be a similar (if not the same) issue as Issue 369
(https://code.google.com/p/google-glass-api/issues/detail?id=369&q=camera&colspe
c=ID%20Type%20Status%20Priority%20Owner%20Component%20Summary).Original comment by gerald.m...@gmail.com on 25 Jul 2014 at 8:02
GoogleCodeExporter
commented
9 years ago I may be having the same issue, although my logcat doesn't show all these
services dying. For me, the app freezes yes, but then sometimes the display
just goes blank (sometimes still 'backlit', sometimes not). The Glass does not
respond to any input, neither via touchpad nor buttons. The only way I can
regain control of the Glass is by forcing shutdown by holding down the power
button. If I don't do this the Glass quickly gets very hot.Original comment by cxlab....@gmail.com on 7 Aug 2014 at 8:58
Original issue reported on code.google.com by
horikawa...@gmail.comon 17 Apr 2014 at 7:21