Post Reply Tablet rebooting...
67042 cr points
Send Message: Send PM GB Post
35 / M
Offline
Posted 11/26/15 , edited 11/26/15
My tablet is rebooting every time it plays a video on Crunchyroll. The video starts playing at a very low quality, but that seems to go away after 5 to 10 seconds. No issues for a bit. Then, at some scene change (after the OP, before the first chapter, or, half way through at the scene split, or, after the last section before the ED, etc), my tablet will just reboot.

This happens during every single video, and, happens at the exact same spot during that specific video. For example, during Shippuuden 437, it reboots right after the OP ends, every time. During Shippuuden 436, however, it reboots between the break in between parts 1 and 2, every time.

This has happened now for a couple of weeks. It also only happens when I am logged in. I am a Plus member, and the spots where the tablet reboots is exactly where the advertisements play when I am not logged in. So it seems to have something to do with your advertisement services.

Tablet Model: Nexus 10
Streaming Via: WiFi
Service Provider: Many different providers (work, home, etc)
Android OS: 5.1.1 Lollipop (stock), also happens on CM12.1 builds
App Version: All. See notes below...

I've logged out and back in. I've uninstalled and reinstalled. I've done a full factory reset on Android. I've even replaced the Android OS with a different ROM and version. Nothing seems to help.

This happens under 1.1.9, and, 1.1.8 versions of the Crunchyroll application. The logs show nothing. Literally, nothing.

Under 1.1.7, however, things get interesting. On 1.1.7, while playing Shippuuden 437, I get the message "There was a problem playing the video. Please try again, or contact support if the problem persists." right after the OP ends. It does not play the video beyond that point, the error keeps coming back even after retrying. The logs, however, are flush with buffer overflow exceptions.

I/ExoPlayerImpl( 3384): Init 1.4.2
I/SwrveSDK( 3384): user event queued
D/mali_winsys( 3384): new_window_surface returns 0x3000
V/WindowManager( 411): Adding window Window{144f7423 u0 SurfaceView} at 8 of 16 (before Window{14e769dd u0 com.crunchyroll.crunchyroid/com.crunchyroll.video.activities.VideoPlayerActivity})
I/ActivityManager( 411): Displayed com.crunchyroll.crunchyroid/com.crunchyroll.video.activities.VideoPlayerActivity: +405ms
I/SwrveSDK( 3384): Sending queued events
I/SwrveSDK( 3384): Sending 1 events to Swrve
I/OMXClient( 3384): Using client-side OMX mux.
E/OMXNodeInstance( 131): getConfig(32:Exynos.AVC.Decoder, ConfigCommonOutputCrop(0x700000f)) ERROR: NotReady(0x80001010)
D/libexynosv4l2( 131): try node: /dev/video6, minor: 6
I/libexynosv4l2( 131): node found for device s5p-mfc-dec: /dev/video6
I/libexynosv4l2( 131): open video device /dev/video6
I/OMXClient( 3384): Using client-side OMX mux.
I/SoftAAC2( 3384): Reconfiguring decoder: 0->44100 Hz, 0->2 channels
I/SwrveSDK( 3384): Events sent to Swrve
E/ExoPlayerImplInternal( 3384): Internal runtime error.
E/ExoPlayerImplInternal( 3384): java.nio.BufferOverflowException
E/ExoPlayerImplInternal( 3384): at java.nio.Buffer.checkPutBounds(Buffer.java:183)
E/ExoPlayerImplInternal( 3384): at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:356)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.extractor.RollingSampleBuffer.readData(RollingSampleBuffer.java:287)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.extractor.RollingSampleBuffer.readSample(RollingSampleBuffer.java:193)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.extractor.DefaultTrackOutput.getSample(DefaultTrackOutput.java:142)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.hls.HlsExtractorWrapper.getSample(HlsExtractorWrapper.java:186)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.hls.HlsSampleSource.readData(HlsSampleSource.java:298)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.MediaCodecTrackRenderer.feedInputBuffer(MediaCodecTrackRenderer.java:600)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.MediaCodecTrackRenderer.doSomeWork(MediaCodecTrackRenderer.java:501)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:417)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:205)
E/ExoPlayerImplInternal( 3384): at android.os.Handler.dispatchMessage(Handler.java:98)
E/ExoPlayerImplInternal( 3384): at android.os.Looper.loop(Looper.java:135)
E/ExoPlayerImplInternal( 3384): at android.os.HandlerThread.run(HandlerThread.java:61)
E/ExoPlayerImplInternal( 3384): at com.google.android.exoplayer.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)
E/VideoPlayerFragmentExoPlayer( 3384): Video error: Lost connection to video
W/System.err( 3384): com.google.android.exoplayer.ExoPlaybackException: java.nio.BufferOverflowException
W/System.err( 3384): at com.google.android.exoplayer.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:238)
W/System.err( 3384): at android.os.Handler.dispatchMessage(Handler.java:98)
W/System.err( 3384): at android.os.Looper.loop(Looper.java:135)
W/System.err( 3384): at android.os.HandlerThread.run(HandlerThread.java:61)
W/System.err( 3384): at com.google.android.exoplayer.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)
W/System.err( 3384): Caused by: java.nio.BufferOverflowException
W/System.err( 3384): at java.nio.Buffer.checkPutBounds(Buffer.java:183)
W/System.err( 3384): at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:356)
W/System.err( 3384): at com.google.android.exoplayer.extractor.RollingSampleBuffer.readData(RollingSampleBuffer.java:287)
W/System.err( 3384): at com.google.android.exoplayer.extractor.RollingSampleBuffer.readSample(RollingSampleBuffer.java:193)
W/System.err( 3384): at com.google.android.exoplayer.extractor.DefaultTrackOutput.getSample(DefaultTrackOutput.java:142)
W/System.err( 3384): at com.google.android.exoplayer.hls.HlsExtractorWrapper.getSample(HlsExtractorWrapper.java:186)
W/System.err( 3384): at com.google.android.exoplayer.hls.HlsSampleSource.readData(HlsSampleSource.java:298)
W/System.err( 3384): at com.google.android.exoplayer.MediaCodecTrackRenderer.feedInputBuffer(MediaCodecTrackRenderer.java:600)
W/System.err( 3384): at com.google.android.exoplayer.MediaCodecTrackRenderer.doSomeWork(MediaCodecTrackRenderer.java:501)
W/System.err( 3384): at com.google.android.exoplayer.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:417)
W/System.err( 3384): at com.google.android.exoplayer.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:205)
W/System.err( 3384): ... 4 more
E/VideoPlayerActivity( 3384): Video error: what: 0 extra: 0, extraextra: aHR0cDovL3d3dy5jcnVuY2h5cm9sbC5jb20vbGl2ZXBsYXlsaXN0L3ZpZGVvXzIwMjQ2NDUubTN1
E/VideoPlayerActivity( 3384): OD9rZXk9ZVU1NU5qQklSazgyUTJ4RE56SkRUR0ZqVkZwcFJtcHJObTR3UFY5N0ltd2lPakUwTkRB
E/VideoPlayerActivity( 3384): d0xDSnZJam9pWlc1VlV5SXNJbk1pT2pRd056RTFPQ3dpYzJ4cGMzUWlPaUpjTDNabE1qQXpNemsx
E/VideoPlayerActivity( 3384): TTF3dklpd2lkQ0k2TVRRME9EVTBOams0Tml3aWRTSTZJall4TWpJMU5UWWlMQ0oySWpveGZRJmNs
E/VideoPlayerActivity( 3384): aWVudD1jb20uY3J1bmNoeXJvbGwuY3J1bmNoeXJvaWQ=
E/libexynosv4l2( 131): failed to ioctl: VIDIOC_DQBUF (22 - Invalid argument)
E/libexynosv4l2( 131): failed to ioctl: VIDIOC_DQBUF (22 - Invalid argument)
V/WindowManager( 411): not Base app: Adding window Window{28461b4c u0 com.crunchyroll.crunchyroid/com.crunchyroll.video.activities.VideoPlayerActivity} at 7 of 14
D/mali_winsys( 3384): new_window_surface returns 0x3000
W/OUYAF ( 3384): Not running on Ouya hardware: manta
I/art ( 797): Explicit concurrent mark sweep GC freed 71075(4MB) AllocSpace objects, 102(1656KB) LOS objects, 40% free, 12MB/20MB, paused 901us total 64.703ms

From the looks of things, 1.1.8 and 1.1.9 are similarly buffer overflowing in such a way that it's taking the whole Android stack down with it. I'll happily file a bug with the Android team if I can figure out what the hell your app is doing. But it clearly is something on your end, since the app works fine when I'm not logged in.
Der Zoodirektor
25855 cr points
Send Message: Send PM GB Post
35 / M / Germany
Online
Posted 11/26/15
Forwarded your log to the devs.
Tlabi 
16028 cr points
Send Message: Send PM GB Post
26 / M
Offline
Posted 11/26/15
The same thing is happening to me, on my Nexus 10, except it seems mine crashes randomly after under a minute of streaming. Never had issues before, only recently. Not making progress via the support team either. We need an update ASAP.
67042 cr points
Send Message: Send PM GB Post
35 / M
Offline
Posted 11/27/15
@shinryou Thank you

I'll make this really easy for you, too. Have your devs email me (or PM me here - but email is preferred), and I'll gladly set them up with remote access to my tablet. I'm an Android developer who can actually help them debug this, if they wish.

I'll also let them play with my physical tablet if they think that would be of help, and do their own testing/debugging on it. I would assume they already have one for testing purposes, but maybe that's a bad assumption on my part. I can drop by the SF office for a few hours during the week at their convenience with it if that would be helpful. I've been wanting to drop by anyway, just for a tour anyway.
67042 cr points
Send Message: Send PM GB Post
35 / M
Offline
Posted 11/27/15
Additional information:

Android 6.0 on my Nexus 10 also has the same issues as 5.1 does, with the rebooting. Still no log entries just prior to the reboot.

This issue doesn't happen on my Android TV (Android 5.0.2, Crunchyroll 1.1.9, Ethernet (not WiFi), Comcast). It behaves exactly as expected (aside from the interface issues on Android TV).

I'll check my other devices as time permits...
Der Zoodirektor
25855 cr points
Send Message: Send PM GB Post
35 / M / Germany
Online
Posted 11/27/15 , edited 11/28/15
It's always weird that the devices created close to the source of Android are the most buggy :D

I have some Pipo X9 here, Android 4.4.4/Win10 dual boot HTPC on x86 hardware, all smooth, for example.
67042 cr points
Send Message: Send PM GB Post
35 / M
Offline
Posted 11/28/15 , edited 12/4/15

shinryou wrote:

It's always weird that the devices created closed to the source of Android are the most buggy :D

I have some Pipo X9 here, Android 4.4.4/Win10 dual boot HTPC on x86 hardware, all smooth, for example.


The Nexus 10 is an odd beast, though. Here's the results of my testing so far for 1.1.9. I didn't bother with 1.1.8 or lower.

Android Devel TV (ADT-1): 5.0 - No issues (except known interface stuff)
Nexus 4: Android 4.4, 5.0, 5.1 - No issues
Nexus 5: Android 4.4, 5.0, 5.1, 6.0 - No issues
Nexus 6: Android 5.0, 5.1, 6.0 - No issues
Nexus 7 (2012): Android 4.4, 5.0, 5.1 - No issues
Nexus 7 (2013): Android 5.0, 5.1, 6.0 - No issues
Nexus 9 - 5.1, 6.0 - No issues
Nexus 10 - 4.4, 5.0, 5.1, 6.0 - Reboots when logged in (only) due to potential buffer overflow
OnePlus One: 4.4, 5.0, 5.1, 6.0 - No issues
Huawei Ascend Mate 2: 4.4, 5.0, 5.1, 6.0 - No issues.
Huawei P8Lite: 4.4, 5.0, 5.1, 6.0 - No issues.
nVidia Shield: 4.4, 5.1 (no 5.0 release) - No issues. Will be a while before 6.0 works on this handheld

Of all the devices that I have tested on, however, the Nexus 10 is unique in one respect - it has an Exynos 5250 Dual Core CPU in it, which could be causing issues with parts of the Tremor Video client when it's told to skip something (as it should be for Premium users). I do not have another Exynos 5 device to test against, and there actually isn't another Exynos 5250 device powered by Android that has ever been made. All Samsung's smartphones with an Exynos 5 SoC are using a 54xx Octocore (extremely different 8 core big.LITTLE quad A7/A15+ architecture vs a dual core Cortex A15 design), or, in 3 other devices that saw VERY limited distribution (aka, nobody's ever heard of them), a 5260 Hexacore (much more similar to the octocore design, with the same big.LITTLE A7/A15+ cores in a 4/2 config, than the dual core 5250 despite the similar model numbers) chip.

In other words, that CPU is pretty esoteric, and, being an Exynos, not well documented. While nothing should EVER be able to crash the whole Android stack like this, bugs do happen (usually in the drivers or kernel, when it comes to supporting the hardware underneath), and I'm not sure what support actually exists in AOSP for the Exynos line specifically. I know we had a HELL of a time getting Exynos 4 support in CyanogenMod back in the day. We're still using blobs from Samsung firmware for performance reasons in some places because the AOSP code isn't as graceful, and of course Samsung won't merge their driver code so all we can do is reverse engineer stuff and pray to $deity.

Anyway, I hope this info helps your devs. I'll poke at it more as time permits, and if there's anything specific you'd like me to try, don't hesitate to speak up. I would like to see this issue fixed here, and then the root caused shipped back up to AOSP so we can fix the underlying bug in the whole stack.

78005 cr points
Send Message: Send PM GB Post
32 / M
Offline
Posted 12/14/15
My nexus 10 crashes as well. It also has weird video glitches. Sometimes the bottom of the screen will glitch out to where it is just a mess which is a pain as it blocks my subs. The glitch goes away if something new pops up on the screen in the area of the glitch, or goes away entirely if the entire screen changes. I've seen the rebooting issue as well. Weirdest one I've seen is that during monogatari videos, it'd randomly skip forward in the video by several seconds. Using app version 1.1.9 stock lollipop 5.1.1 without root.
67042 cr points
Send Message: Send PM GB Post
35 / M
Offline
Posted 12/19/15
Well, software version 2.0.1 has resolved the crash on the Nexus 10 for me. Kudos to the devs...
Der Zoodirektor
25855 cr points
Send Message: Send PM GB Post
35 / M / Germany
Online
Posted 12/19/15
I'm happy to hear that your issue has been resolved.
You must be logged in to post.