But compared to rapsbmc (now OSMC), geexbox went commercial far earlier by making a deal with solidrun/cubox. So I expected to get the best experience and a more active development out of it.
We never went “commercial”. We (currently @tomlohave and myself) do this stuff in our spare time. So we decide what we do and when. SolidRun is so kind to offer hosting services and some sample hardware. That’s it.
Are there any efforts to get the cubox/geexbox combo to beat the raspberry/osmc combo in performance as it technically should?
No. I’m not even sure if it’s possible without a major change in the support policy of the chip vendor (Marvell/Vivante). Maybe the reverse engineered Vivante driver (etnaviv) is a possible way to go. But we are talking here about a rather big effort with no guarantee for success on a platform that already reached it’s end of life. BTW, I don’t think that raspberry/geexbox is significant slower than raspberry/osmc.
And are there any efforts to get it to the current version of kodi
Not at the moment. Even though I might have a look at this when I find the time. CuBox support in XBMC is not mainlined. It was developed by former team XBMC member Gimli, Rabeeh of SolidRun and myself. I’m quite positive that it will require several days of work to integrate into Kodi. That is without any functional improvement. For the mainlined platforms (CuBox-i, Utilite, RaspberryPi, PaspberryPi2, Intel) Geexbox with Kodi 15 can be built by just selecting the appropiate configuration. But we do not yet provide images.