Open GoogleCodeExporter opened 9 years ago
this has probably to do with Issue 12
Original comment by tdomhan
on 29 Apr 2010 at 8:12
I would appreciate if you could try the version attached to Issue 12
Original comment by tdomhan
on 30 Apr 2010 at 9:51
I'm still getting a white screen after the update.
Original comment by PBnJ...@gmail.com
on 1 May 2010 at 12:30
did you try the version attached to issue12 or the update from the market?
Original comment by tdomhan
on 1 May 2010 at 9:40
ah and could you provide me the output of "adb logcat"? a tool that is part of
the
android SDK. (Can be found in the tools folder)
Original comment by tdomhan
on 1 May 2010 at 9:40
I'm not a developer so I'm not sure I have access to those tools. I'm just a
huge fan of AR. I tried both
the version from issue 12 and the update from the market which seemed to have
the same
result....blank white screen. I wish I could be of more help... good luck.
Original comment by PBnJ...@gmail.com
on 1 May 2010 at 12:22
I have a Droid with 2.1 using the apk attached to issue 12, and am experiencing
the same white screen as well.
The logcat is attached here.
Original comment by pat.dalb...@gmail.com
on 1 May 2010 at 6:50
Attachments:
thanks for the log!
maybe it has to do with that:
http://code.google.com/p/android/issues/detail?id=5514#c0
I commented out the parts changing the preview size. Could someone try the
attached apk?
Could furthermore someone tell what the getSupportedPreviewSizes method of the
camera parameters returns on the
droid?
This can be done like this:
[code]
Camera.Parameters params = camera.getParameters();
List<Camera.Size> list = params.getSupportedPreviewSizes();
[/code]
I'm interested in the contents of this list. I would really appreciate that! :D
Original comment by tdomhan
on 9 May 2010 at 8:09
Attachments:
Hi, I have a Motorola Droid with 2.1 and the white-screen crash bug mentioned
above.
Calling getSupportedPreviewSizes() on my phone gives a list of 7 preview sizes:
176x144
320x240
352x288
640x480
720x480
720x576
848x480
The .apk file posted above does not fix the problem, unfortunately. Hope the
list is
helpful!
Thanks!
Original comment by elm19...@gmail.com
on 13 May 2010 at 3:10
i commented out:
Parameters params = camera.getParameters();
//try to set the preview size to this fixed value
params.setPreviewSize(240,160);
try {
camera.setParameters(params);
} catch(RuntimeException ex) {
ex.printStackTrace();
}
then just set my preview size like so:
params.setPreviewSize(320,240);
and no longer have a white screen on my Droid w/ 2.1.
Granted this isn't the best way to set the size, but it's working :)
Original comment by nikko.ai...@gmail.com
on 21 May 2010 at 6:27
Interesting Nikko. So does that mean that Droid does not support a preview size
of
240x160?
In one of my earlier tests on N1 I also used a larger preview size, I chose one
that
had the same aspect ratio as 240x160, and it seemed to work well.
Original comment by suzy...@gmail.com
on 22 May 2010 at 3:38
Correct. The Droid supports the sizes listed in comment #9, from elm19087. The
supported resolutions are hardware dependent, which would explain why 240x160
works
for your N1.
Original comment by nikko.ai...@gmail.com
on 22 May 2010 at 5:16
Hi nikko.aiello,
thanks for testing.
Am I getting this right, with a preview size of 320 x 240 everything works fine?
elm19087 tested a version where all setParameters were commented out. In that
case the
camera should use the default preview size, which should be one that is
supported.
however that version did not work.
I'm going to write a version that queries the available preview sizes, and sets
one that
fits best. The problem is that there are no functions to query those sizes on
Android
1.6. So this is no a trivial task, when you don't won't to raise an VerifyError
on those
phones.
Furthermore there not all framerate previewsize combinations are supported. You
can not
query the framerates supported by a preview size or vice versa.
Original comment by tdomhan
on 23 May 2010 at 2:19
alright, I circumvented the the verfiyerror using reflection. I uploaded the
sources to
the SVN repository. (r139)
The app now queries the available previewsizes /formats and chooses one that
fits best.
Could one of you milestone guys try out, if that works on your phones?
Thanks in advance ;)
Original comment by tdomhan
on 24 May 2010 at 10:24
I was able to build from r139 and install onto my Motorola Droid running 2.1,
where it no longer has the white
screen. I pointed the camera at the printed marker and saw a green cube
positioned as expected. Yee-haw! AR
on the Droid! Thanks to you & all contribs! I've attached a logcat from one of
my runs in the hopes that it will be
of use going forward.
Original comment by pat.dalb...@gmail.com
on 24 May 2010 at 3:54
Attachments:
A white screen appears also in the HTC Magic (Android 1.6)
It's something about camera parameters? Thanks
Original comment by lei...@gmail.com
on 24 May 2010 at 5:26
alright, thanks for testing pat.dalberg. Thanks is indeed great news!
@leiret which version of AndAR are you using? A dedicated issue might be good.
Do you
know how to provide the output of logcat?.
It seems to work on the HTC magic with android 1.5,.. strange.
Original comment by tdomhan
on 27 May 2010 at 7:40
right, the unfortunate thing about 1.6 is that it doesn't offer the preview
sizes.
maybe have a list of optimal sizes, and iterate through it until one sticks??
Original comment by nikko.ai...@gmail.com
on 28 May 2010 at 6:28
well it works on HTC Magic with Android 1.5, I don't think the preview sizes
have
changed with the version upgrade.
the output of logcat would be nice. Can you provide that?
Original comment by tdomhan
on 1 Jun 2010 at 8:58
Here is the output of logcat.
The andar.jar is of date 24/04, and the AndObjViewer is the latest version.
HTC Magic, android 1.6
Original comment by lei...@gmail.com
on 7 Jun 2010 at 8:47
Attachments:
[deleted comment]
AndObjViewer is downloaded from SVN
Original comment by lei...@gmail.com
on 7 Jun 2010 at 9:53
It works fine on HTC Magic 1.6
Original comment by lei...@gmail.com
on 20 Jul 2010 at 10:53
Original issue reported on code.google.com by
PBnJ...@gmail.com
on 29 Apr 2010 at 2:14