Nexus 5 / 5.0 fails on ad tag, no other devices do

[Jon Slenk]

Hi,

I have an ad tag url that fails on our Nexus 5 running 5.0, but the same tag works fine on a Nexus 7 running 5.0, and works fine on other devices such as a Samsung Galaxy something-or-other running 4.3. So it appears to me that the Nexus 5 decoders are different enough to fail on things?! I guess if that is the case, it isn't really something IMA can handle, it is more just a low-level Android OS issue?

All I did was change googleads-ima-android-2.1/BasicExample/app/src/main/res/values/strings.xml's ad_tag_url to this:

<string name="ad_tag_url"><![CDATA[http://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/40797597/test_preroll_only&ciu_szs&impl=s&gdfp_req=1&env=vp&output=xml_vast2&unviewed_position_start=1&url=[referrer_url]&correlator=[timestamp]]]></string>

APK attached.

I think the relevant part of the log is:

I/ImaExample(31196): Event: CONTENT_PAUSE_REQUESTED

I/IMASDK  (31196): Illegal message type setPlaybackOptions received for videoDisplay channel

I/MediaFocusControl(  745):  AudioFocus  requestAudioFocus() from android.media.AudioManager@27c7ce20

D/MediaPlayer(31196): Couldn't open file on client side, trying server side

D/MediaPlayer(31196): getMetadata

D/NuPlayerDriver(  187): start(0xb1b01f80)

I/GenericSource(  187): start

I/NuCachedSource2(  187): ERROR_END_OF_STREAM

I/OMX-VDEC-1080P(  187): component_init: OMX.qcom.video.decoder.avc : fd=-1

E/OMX-VDEC-1080P(  187): Omx_vdec::Comp Init Returning failure, errno 12

E/OMX-VDEC-1080P(  187): Invalid input: -1

I/OMX-VDEC-1080P(  187): Exit OMX vdec Destructor: fd=-1

E/OMX     (  187): FAILED to allocate omx component 'OMX.qcom.video.decoder.avc'

W/ACodec  (  187): Allocating component 'OMX.qcom.video.decoder.avc' failed, try next one.

I/SoftAAC2(  187): Reconfiguring decoder: 0->44100 Hz, 0->2 channels

E/OMXNodeInstance(  187): OMX_GetExtensionIndex OMX.google.android.index.storeMetaDataInBuffers failed

E/ACodec  (  187): [OMX.google.h264.decoder] storeMetaDataInBuffers failed w/ err -2147483648

E/SoftAVC (  187): Decoder failed: -2

E/ACodec  (  187): [OMX.google.h264.decoder] ERROR(0x80001001)

E/ACodec  (  187): signalError(omxError 0x80001001, internalError -2147483648)

E/MediaCodec(  187): Codec reported err 0x80001001, actionCode 0, while in state 6

E/NuPlayerDecoder(  187): Failed to dequeue output buffer for OMX.google.h264.decoder (err=-38)

E/NuPlayer(  187): received error(0xffffffda) from video decoder, flushing(0), now shutting down

E/MediaPlayer(31196): error (1, -38)

E/NuPlayerDecoder(  187): failed to flush OMX.google.h264.decoder (err=-38)

E/MediaPlayer(31196): Error (1,-38)

D/VideoView(31196): Error: 1,-38

E/NuPlayer(  187): received error(0xffffffda) from video decoder, flushing(2), now shutting down

E/MediaPlayer(31196): error (1, -38)

D/audio_hw_primary(  187): out_set_parameters: enter: usecase(0: deep-buffer-playback) kvpairs: routing=2

D/audio_hw_primary(  187): select_devices: out_snd_device(2: speaker) in_snd_device(0: none)

D/audio_hw_primary(  187): enable_audio_route: apply and update mixer path: deep-buffer-playback

E/MediaPlayer(31196): Error (1,-38)

D/VideoView(31196): Error: 1,-38

E/ImaExample(31196): Ad Error: There was an error playing the video ad.

[Bret McGowen]

Hi Jon,

That sounds like it it could be a device media decoder issue. I'll investigate it further and get with the rest of the team to see if we can confirm it's not an SDK issue, or if it is, if we can come up with a workaround.

Thanks,

Bret McGowen

IMA SDK Team

[sandeep singh]

Hi Jon, 

Any update on this issue ?

I am facing a similar issue on Intel Platform Chipset.

Log snippet

<snip>

01-02 13:29:56.137  2501  2501 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1321 com.intel.multidisplay.DisplayObserver.enableHdmiSetting:331 com.intel.multidisplay.DisplayObserver.access$900:52 com.intel.multidisplay.DisplayObserver$2.handleMessage:362 android.os.Handler.dispatchMessage:102 

01-02 13:29:56.221  2220 16127 E ACodec  : [OMX.Intel.hw_vd.vp9] ERROR(0x80001001)

01-02 13:29:56.221  2220 16127 E ACodec  : signalError(omxError 0x80001001, internalError -2147483648)

01-02 13:29:56.221  2220 16124 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 6

01-02 13:29:56.222  2220 16123 E NuPlayerDecoder: Failed to dequeue output buffer for OMX.Intel.hw_vd.vp9 (err=-38)

01-02 13:29:56.223  2220 16120 E NuPlayer: received error(0xffffffda) from video decoder, flushing(0), now shutting down

01-02 13:29:56.223 10395 10413 E MediaPlayer: error (1, -38)

01-02 13:29:56.223  2220 16123 E NuPlayerDecoder: failed to flush OMX.Intel.hw_vd.vp9 (err=-38)

01-02 13:29:56.223  2220 16120 E NuPlayer: received error(0xffffffda) from video decoder, flushing(2), now shutting down

01-02 13:29:56.223 10395 10413 E MediaPlayer: error (1, -38)

01-02 13:29:56.223 10395 10395 E MediaPlayer: Error (1,-38)

01-02 13:29:56.223 10395 10395 D VideoView: Error: 1,-38

01-02 13:29:56.224 10395 10395 E MediaPlayer: Error (1,-38)

<snip>

Can you help us to root cause this issue ?

Thanks 
Sandeep Singh

[Shawn Busolits (IMA SDK Team)]

Hi all,

Jon, do you know if your trafficking changed since you first reported this issue? I tried testing with your tag but it's coming back empty.

Sandeep, could you share your ad tag with us so we can take a look?

Thanks,

Shawn Busolits

IMA SDK Team