soup_menu's forum posts

#1 Posted by soup_menu (202 posts) -

@atomicedge: The "Unfortunately Giant Bomb Video Buddy Has Stopped" message just generically indicates that the app has crashed. If you're getting that when you're not casting then you've most likely stumbled upon a different bug. I'm not seeing any new crashes in the developer console though, so if you're encountering one please report it.

#2 Posted by soup_menu (202 posts) -

@fractology: @sogeman: Pre-4.2 tablets and set-top boxes are going to drive me to drink. In fixing the fullscreen issue for 10"+ screens I inadvertently reintroduced the fullscreen issue for 7" screens. It's looking like there isn't going to be a one-size-fits-all solution to be had here, so I've created a new build with a compromise: the UI should now work correctly out of the box for the vast majority of devices, but for those with pre-4.2 devices with the old tablet UI (like @row) there's a new option in the settings menu. I would have preferred it just work for everyone, but since there are a number of off-brand set-top boxes whose behavior may not conform to expectations this seemed like the most workable compromise.

This new build should be available in the Play Store in just a few hours. Sorry for the inconvenience.

@rongalaxy: Right now I'm using Android's built-in video player controls which don't support that drag-to-scrub functionality. It's definitely a nice feature, but it's probably not something that will end up in GBVB in the foreseeable future. Some third party apps like MX Player do support it though, so if you were willing to forgo GBVB's ability to remember how much of a video you've watched you could long-press on the play button to send the video to another app. As for showing file sizes before starting the download, that information isn't made available through the API, so there isn't a good way to get it besides starting the transfer.

#3 Posted by soup_menu (202 posts) -

@kingpk: Cool. Thanks for following up.

@kingoficeland: Woah! That's a lot of Quick Looks! :) (Thanks for the donation!)

@sogeman: No worries. Happy to hear it's working correctly now.

#4 Posted by soup_menu (202 posts) -

@kingpk: The list of categories is sorted alphabetically, so "Unfinished" is going to be last--is there any chance that it was just positioned offscreen? If you've scrolled the menu to the bottom and it's really missing then it may have been an intermittent API issue. Starting with 2.0 I'm no longer hardcoding the categories and am instead relying on the API to provide them. If for some reason the list received from the API didn't include Unfinished then the app wouldn't show it. The app refreshes itself on launch (though only if it's been at least 6 hours since the last refresh) and Unfinished is currently being returned by the API, so if there was an issue it should fix itself soon if it hasn't already.

@atomicedge: I saw your crash report show up in the developer console this morning. I hadn't realized that you were sending video to a Chromecast, not playing it locally, so once I started looking in the right place I was able to reproduce the issue (incidentally, it's not dependent on ART). The cause is a bug in Google's Chromecast library, but I'm testing a fix that should take care of it. Hopefully I'll have it out in the Play Store soon, but until then the best workaround would be to not background the app with the Chromecast remote control interface visible. If you back out to any other screen in the app you should be fine.

#5 Posted by soup_menu (202 posts) -

@row: That's progress! Here's one more APK that should work like mode 3 from the last build. If that does the trick then we should be all set.

#6 Posted by soup_menu (202 posts) -

@row: Drat. I figured that was the case, but I couldn't help but hoping. If you're willing to do a bit more testing, I've uploaded a new APK that adds a drop-down next to the quality drop-down. Each option causes the app to use a different combination of ways to put the app into a full-screen mode and, with a bit of luck, at least one of them will work.

#7 Posted by soup_menu (202 posts) -

@atomicedge: If the player gets removed from memory while it's in the background it should be able to recreate itself when you go back to the app, but it's entirely possible there's something going on that I haven't accounted for. Reporting the crash if/when it happens again would be awesome.

Thanks for the DLC purchase! Much obliged.

#8 Posted by soup_menu (202 posts) -

@row: At the risk of asking a stupid question: that clean install was done by sideloading the APK I linked in my last post, not by installing from the Google Play Store, right?

If so, was there any change in behavior? Maybe it's now drawing the video on the whole screen even if it's not properly hiding the system bar?

If there's been no change at all, maybe the device is a bit more non-standard than I thought (that you can hide the system bar at all indicates that the manufacturer has tinkered with the OS at least a little). Does the main interface show the video details on a separate screen from the list of videos or are they shown together with the list on the left and the details on the right?

#9 Posted by soup_menu (202 posts) -

@row: Perfect! It looks like your device is using the old 10" tablet (and larger) UI that was introduced in Android 3.0 and phased out in 4.2. I had a hunch that might be the case, so I banged together a new build for you to try. You can grab the APK here.

If that works (and, at the risk of jinxing it, I think it probably will) I'll upload it to the Play Store. Please let me know once you've had a chance to give it a try.

#10 Edited by soup_menu (202 posts) -

@atomicedge: Google doesn't consider ART ready to ship as the default runtime yet, so I wouldn't be shocked if it were somehow to blame. That said, I just switched my Nexus 7 over and couldn't reproduce the issue, so other elements could be involved.

Have you allowed Android to report the crash? I'm not seeing anything in the developer console.