Thanks for the additional precisation about Cloud Reco.

AlessandroB wrote:

@ yogendra and ALL interested in i9082 black background issue:

The issue has been identified in the incorrect location of the following lines of code in the _renderFrame() function:

#ifdef USE_OPENGL_ES_1_1        
    glDisable(GL_TEXTURE_2D);
    glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_NORMAL_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);
#else
    glDisableVertexAttribArray(vertexHandle);
    glDisableVertexAttribArray(normalHandle);
    glDisableVertexAttribArray(textureCoordHandle);
#endif

Currently those lines are located AFTER the "for loop" (near the end of the renderFrame function) and on some devices produce a GL error;

the solution is to move those lines inside the "for loop", immediatly after the glDrawElements() call.

That should solve it (as we verified with our I9082)

 

thank you soooo much...

for those who are facing this in cloud reco sample.

move these lines :

to just below this line  renderAugmentation(trackableResult);  in renderframe()    

@ yogendra and ALL interested in i9082 black background issue:

The issue has been identified in the incorrect location of the following lines of code in the _renderFrame() function:

#ifdef USE_OPENGL_ES_1_1        
    glDisable(GL_TEXTURE_2D);
    glDisableClientState(GL_VERTEX_ARRAY);
    glDisableClientState(GL_NORMAL_ARRAY);
    glDisableClientState(GL_TEXTURE_COORD_ARRAY);
#else
    glDisableVertexAttribArray(vertexHandle);
    glDisableVertexAttribArray(normalHandle);
    glDisableVertexAttribArray(textureCoordHandle);
#endif

Currently those lines are located AFTER the "for loop" (near the end of the renderFrame function) and on some devices produce a GL error;

the solution is to move those lines inside the "for loop", immediatly after the glDrawElements() call.

That should solve it (as we verified with our I9082)

Hi, thanks for sharing this info;

concerning your observation:

Removing the mUILayout is not a sloution, as this is the layout that actually holds the GLSurfaceview, on which the graphics are drawn.

addContentView(mGlView, new LayoutParams(LayoutParams.MATCH_PARENT,
                        LayoutParams.MATCH_PARENT));

I am seeing a very similar (if not the same) issue on both the HTC OneX and Sony LT26i (android 4.0.4, api-15) and on the LG Nexus4 (android 4.2, api-17):
The background remains black. while tracking and foreground rendering works perfectly. (Well i'm using some quite bad trackables, but both the names and the modelviewprojection-matrices are fine if i nurse the position of the images a little). I am rendering a textured sprite on top of the target. My app is based upon the ImageTargets example and the native code uses Vuforia 2.0.31 (2.0.30 has the same issue)

Using a Samsung Galaxy Nexus phone, the camera background works fine (android 4.2.1, api-17)  - and two days ago with api-16 before i upgraded it, although the code was slightly different then...

I'm getting some irregularities in the logcat with the Nexus4 when i start and stop the camera:

Hi, thanks for the info;

actually, one hypothesis is that the UI layout (overlay layout) used in ImageTargets and CR samples may be responsible for the issue on that device;

could you do the following:

open ImageTargets.java, find all occurrences of a variable called mUILayout;

just remove (or comment out) the lines of code that refers to mUILayout (so, essentially, remove any sage of such variable in the code);

then run again and see if it makes any difference...

adding one more thing:

after few seconds of run following error comes in this device only in cloudreco sample.

please look into this.

AlessandroB wrote:

ok, could you change it to LANDSCAPE (just to exclude that issue) ?

sorry to say but black in LANDSCAPE also

ok, could you change it to LANDSCAPE (just to exclude that issue) ?

i already using:

 int screenOrientation = ActivityInfo.SCREEN_ORIENTATION_PORTRAIT;

Thanks yogendra for the test; 

actually, CloudReco and ImageTargets have a few commonalities that might indicate where the issue is; 

may I ask you to go to ImageTargets.java and in the initApplication() function replace this line:

And then run ImageTargets again; does it make any difference on your device ?

AlessandroB wrote:

@ yogendra (and to anyone interested in the Samsung I9082 device issue),

we have done some testing and we were able to reproduce the problem in ImageTargets, but not in other samples;

it would be nice if you could mae the same kind of test, so to have a confirmation from your device too, i.e. run a few more samples from the Vuforia SDK and tell us which one shows the black camera issue and which ones don't.

i tried imagetarget,videoplayback and cloudreco samples.

Bad News:

camera frame black in  imagetarget and cloudreco samples.

good news:

camera working fine in videoplayback sample

any idea what is going on?

I don't know if it is related, but I have tried on my LG Nexus 4 the Image Targets and User Defined Targets examples this far and I have the black screen. Just building an empty project with only the ARCamera prefab in it gives a black screen.

However, if I hold pressed the power button and the switch off menu appears, I get the Camera image rendered correctly in the back.

@ yogendra (and to anyone interested in the Samsung I9082 device issue),

we have done some testing and we were able to reproduce the problem in ImageTargets, but not in other samples;

it would be nice if you could mae the same kind of test, so to have a confirmation from your device too, i.e. run a few more samples from the Vuforia SDK and tell us which one shows the black camera issue and which ones don't.

I would like to report a very similar issue. 

I am using a Nexus 4 as device, with Android 4.2.2, Unity 4 and Vuforia 2.0.31.

In order to clarify a bit more the problem, here is the description: when I run my application I get a black screen after the splash screen. I can not see the Camera view on my app. However, everything works. When I find a trackable, the hidden objects show. In my app, OnTrackingFound() launches a small animation of a car moving and entering the scene. After 5sec it stops and a menu is shown. This menu uses NGUI. The depth value of the NGUI Camera is put to be rendered on top, but what I get is my menu masked by the objects.

This is what I see in my app with Nexus 4:

This is what should be seen (and is seen in a Samsung Galaxy SII or any other device I have tryed):

In addition to this, when I use the Dalvik Debug Monitor to capture screen shots, I get the correct image in all devices. Same, when I tap the "menu" key or hold the "switch on/off" hardware button and let the switch off menu be shown, I can see the camera view working correctly.

I copy here a piece of the log that may be useful:

Maybe a good idea.

Thank you for your quick reply, should I copy my issue in this other thread?

@ haitzika,

thanks for the report: this is similar (or same) issue reported in this thread:

https://developer.vuforia.com/forum/unity-3-extension-technical-discussion/android-422-no-camera-display

You may want to follow the progress there as well (currently under investigation).

We are still looking at it, but it may take some time.

AlessandroB wrote:

Thanks, I will use that info and let you know.

any solution? it's giving me headache...:(

Thanks, I will use that info and let you know.

AlessandroB wrote:

Hi, I would still need one piece of information, i.e. what CPU is your device equipped with:

in order to get this information from your device, you can do this:

• open the cygwin console and type:
  • adb -d shell
• this will open a shell on your device
• then type the following:
  • cat  /proc/cpuinfo

The shell will display some info, could you then copy-paste it here ?

 

cpu information:

Hi, I would still need one piece of information, i.e. what CPU is your device equipped with:

in order to get this information from your device, you can do this:

• open the cygwin console and type:
  • adb -d shell
• this will open a shell on your device
• then type the following:
  • cat  /proc/cpuinfo

The shell will display some info, could you then copy-paste it here ?

AlessandroB wrote:

BTW: could you check your logs and see if you get any error message that might help us investigate the issue ?

 

 i checked logs but there is no error regarding any camera issue.

i am using latest version of vuforia. 

BTW: could you check your logs and see if you get any error message that might help us investigate the issue ?

Also (and most importantly): what version of Vuforia are you using ?

AlessandroB wrote:

Ok, thanks for the model details; I will investigate the issue and report back as soon as I have some findings.

since it's one of the popular phone currently ,it's very critical .

Ok, thanks for the model details; I will investigate the issue and report back as soon as I have some findings.

AlessandroB wrote:

I see. Can you post the full details of that device (please check the device Settings), including model number and Android version please ?

 

model : Samasung Galaxy Grand (I9082)

android version: Android OS, v4.1.2 (Jelly Bean)

plz help me out...:(

I see. Can you post the full details of that device (please check the device Settings), including model number and Android version please ?

yes ...other views are there but camera  preview is completely black.

and this is the only samsung device behaving like this...i don't know what to do?

Hi, just to make sure I correctly understand: 

do you see the 3D teapot models (which prooves the markers are detected and tracked) on top of a black background (i.e. no video background behind ) ?