So a few days ago I started out with trying to put xbmc on my ADT-1. It worked pretty well out of the box, but there were a few issues. I've now also tried SPMC to spot the differences.
I'm not planning to do active xbmc development, I just want it up and working decently on my box. Here's what I think needs to be done for a reasonable experience.
- Required: Fix heavy stuttering, playback stopping, crash
This might already be fixed with the pull request I did earlier, seems to affect all L devices when using MediaCodec.
- Required: Gamepad support
On the ADT-1 gamepad (also going to be available with the Nexus Player) only the back and home buttons work. It does work with SPMC, but for the life of me I can't seem to figure out which commit in SPMC fixes this problem.
- Nice: Multithreaded ffmpeg support
Already in SPMC, a bunch of commits relevant ?
- Nice: Allow daydreams to function
Already in SPMC (
https://github.com/koying/SPMC/commit/cd...6cdbd7f4c3 ? )
So why not just use SPMC ? I'm not really sure why to use one over the other. It seems SPMC has some nice fixes that would be nice to have, but it also seems to be significantly less stable. I would think the idea is for the main branch to support these things as well ?
koying is a member of the team here as well, so stuff tested in spmc usually comes back
I have a Nexus 5 with the latest preview build, and xbmc runs pretty good on it (no stuttering)
(2014-10-28, 16:47)Kib Wrote: [ -> ]koying is a member of the team here as well, so stuff tested in spmc usually comes back
I have a Nexus 5 with the latest preview build, and xbmc runs pretty good on it (no stuttering)
Haven't tested on the Nexus 5 as that is still on 4.4 for me, but both my Nexus 7 and the ADT-1 on L completely fail to play a lot of files without that patch...
I don't mind cherry-picking and building for myself for now, but I need the right commits first (primarily re: gamepad). At the moment, neither xbmc nor spmc are properly usable on my ADT-1, each having what the other is missing though.
(2014-10-28, 19:54)Koying Wrote: [ -> ]Not sure what you mean exactly about the gamepad. Are some buttons not working?
I don't think SPMC has something specific for this...
The ffmpeg MT PR is already in Kodi: https://github.com/xbmc/xbmc/pull/5200
The daydream PR: https://github.com/xbmc/xbmc/pull/5449 (needs rebasing)
Gamepad does completely nothing on xbmc built from source, works fine with SPMC from Play...
Re: ffmpeg MT, I saw the setting under Video->Acceleration in SPMC, but that setting is not present in xbmc. Always enabled then in xbmc?
In case this could lead to some bright ideas, here's what happens when I use the Gamepad with xbmc/source:
dpad left:
V/XBMC ( 2283): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -524287
V/XBMC ( 2283): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -1048575
dpad right:
V/XBMC ( 2283): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -917503
V/XBMC ( 2283): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -1048575
dpad up:
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -983039
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -1048575
dpad down:
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -786431
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -1048575
left stick: left/right/up/down/press
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -2/2/-1/1/9
right stick: left/right/up/down/press
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad -4/4/-5/5/10
button: a/b/x/y/leftshoulder/rightshoulder
V/XBMC ( 2812): Debug Print: ERROR mapping joystick action. Joystick: Gamepad 1/2/3/4/5/6
left trigger and right trigger buttons output nothing
Tip with instructions taken from
http://www.androidauthority.com/enable-d...ar-534854/
How to enable developer options and ADB debugging on Android 5.0 (Lollipop) latest developer preview
Enable developer options
- Scroll down and click on Settings.
- Scroll down and click on About.
- Scroll down a last time to Build Number. Tap on build number repeatedly (should be about 7 times) until a bubble appears saying you’ve unlocked the developer options.
Enable ADB debugging
- Return to the Settings menu using the steps above.
- Scroll down to the bottom and you’ll see the developer options.
- Open developer options and ADB debugging should be the third option. Enable it.
From there you’ll have the developer options and ADB debugging enabled for whatever you may need it for. You’ll also find a number of other options under the developer options that you may find useful eventually.
I first read about this this other thread about ADT-1:
http://forum.kodi.tv/showthread.php?tid=198998
(2014-10-22, 05:01)seven5 Wrote: [ -> ] (2014-10-22, 04:42)radiohead7778 Wrote: [ -> ] (2014-10-22, 04:23)seven5 Wrote: [ -> ]So, I'm trying to connect correctly to the ADT-1 and still having issues though, :/ I'm gonna try to usb debug cable next.
One problem I have is that the ADT-1 is updated to the lastest version of Lollipop, and there's no more Developer Options present in the settings. So I can't follow these instructions:
Code:
Note: Make sure you have enabled USB debugging in Settings > Preferences > Developer options > Debugging > USB debugging, so that you can use the Android Debug Bridge (adb) to connect with the ADT-1 device.
I'm thinking maybe this is the issue. ADB debugging just isn't enabled.
go to settings>about and click on the build five time then exit to the home screen then settings again and you will have dev. settings
then enable debugging in the developer options>debugging>usb debugging
That did it. Thanks!!!
(2014-10-28, 21:22)chainfire Wrote: [ -> ]In case this could lead to some bright ideas, here's what happens when I use the Gamepad with xbmc/source:
My fault:
https://github.com/xbmc/xbmc/pull/5600
Thanks for finding it out.
why are you spamming every thread with this?
(2014-11-05, 14:50)Martijn Wrote: [ -> ]why are you spamming every thread with this?
That info is not the same as my previous posts, this are not only updates but is news from today, see
http://android-developers.blogspot.ca/20...on-tv.html
They are not even the same links, this one is for a other blog post newly made available as of today, not even from the same author.
This is news about the minimum requirements to distribute and have apps published for Android TV in Google Play store and get an app to shown in the launcher.
Maybe you just missed that I linked a different post from the same blog? This specific blog post I linked to now is specifically about Android TV distribution
All very much related to the thread topic I think.
It would definitely be great to have Kodi get updated to the Android TV standards even if it doesn't get released onto the play store although I really hope after the Kodi name is completely changed over they'll release it onto the play store.
Is the fix for heavy stuttering and crash making it to nightlies anytime soon?, Its the only bug that really bothers me in the beta right now everything else works amazing
edit: chainfire any chance you can share your build?
Any chance this will be merged... ever? Been a while now.