Database Develop

XBMCbuntu

I was wondering, Since we have an alpha of Ubuntu, and an Ubuntu installer, anyone try setting up XBMCbuntu? When I get the chance I'll see whats needed to run regular Ubuntu and see if theres enough support in it to run the XBMCbuntu

There isn't. You might be able to kludge it to the point it boots XBMC, but it's pointless. The GPU isn't working in Ubuntu so video acceleration is non-existant. The audio doesn't work either, so you'd be able to lag through low-res videos without sound. Not a great experience. Ubuntu right now is NOT for multimedia, it works great for office, productivity, and programming but not multimedia.

The XBMC guys are focusing all their ARM dev into the Raspberry Pi at the moment. Would be kinda cool, though especially if the TP had HDMI out.

I believe they're working on a xbmc for Android, so hopefully we will have one soon

The current version (which you have to compile from source as no APK has been released to the non-dev community) runs pretty decently on the Touchpad. I haven't tried playing any videos with it, yet. I'll check and report later.

You can find unofficial builds of the Android XBMC build online and it actually seems to work fairly well. The XBMC interface has been adapted a bit to work with touch interfaces and overall it's quite nice. I had issues playing music, but had limited success streaming DVD ISO's from my server and playing other types of video content.

*deleted*

Chromecast on Pi

Can it be done? I know that chromium was ported, and chromium odds was being worked on. Can you kitbash one of these into one of those?
Sent from my SPH-D700 using xda premium

We are working on a similar product:
http://forum.xda-developers.com/showthread.php?t=2359972
to make Pi to support iOS devices and Android devices using AirPlay Mirroring and Miracast.
This is not a port though, I think it should be better as chromecast won't support AirPlay mirroring.
A direct port should be possible too if chromecast source code is available, I would guess it has miracast emulation.

seems it's well possible to emulate Chromecast.
I spent a few days to emulate Chromecast inside rPlay, finally it can find the rPlay (on Raspberry Pi) as a chromecast device, and it can send youtube URL redirection. still long way to go, but seems possible.
Attached is a screenshot of Youtube on Nexus 7, the Chromecast button is shown, when clicked, it will show rPlay as the device.

huisinro said:
seems it's well possible to emulate Chromecast.
I spent a few days to emulate Chromecast inside rPlay, finally it can find the rPlay (on Raspberry Pi) as a chromecast device, and it can send youtube URL redirection. still long way to go, but seems possible.
Attached is a screenshot of Youtube on Nexus 7, the Chromecast button is shown, when clicked, it will show rPlay as the device.
Click to expand...
Click to collapse
Guess that's the best lead we could find thus far, as well as some assurance that this (https://github.com/dz0ny/leapcast) can also redirect Youtube links.

I think it will only be a matter of time until this is fully working like the chromecast

yes, the initial implementation is available in our rPlay software, beta version is available.
We will add more and more chromecasting features to it, in addition to airplay mirroring,
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=23&id=10991
Toadyus said:
I think it will only be a matter of time until this is fully working like the chromecast
Click to expand...
Click to collapse

Also if possible please add option to stream/play local media files which official chromecast lacks.:good:

Is the Chromecast protocol open? If not, has anyone asked Google why not?

Very Cool. Hows the progress
This is very cool. How is it going? Does the Pi have sufficient performance?
D.
huisinro said:
seems it's well possible to emulate Chromecast.
I spent a few days to emulate Chromecast inside rPlay, finally it can find the rPlay (on Raspberry Pi) as a chromecast device, and it can send youtube URL redirection. still long way to go, but seems possible.
Attached is a screenshot of Youtube on Nexus 7, the Chromecast button is shown, when clicked, it will show rPlay as the device.
Click to expand...
Click to collapse

kurchatovian said:
This is very cool. How is it going? Does the Pi have sufficient performance?
D.
Click to expand...
Click to collapse
I am also amazed . I'm curious if it's going good too

deathbearer said:
Also if possible please add option to stream/play local media files which official chromecast lacks.:good:
Click to expand...
Click to collapse
Yatse and bubble UPNP already do this with XBMC on the Pi.
I can easily send YouTube videos to the pi using the share feature in Android and Yatse remote app. Similarly with local content.
Sent from my HTC One using Tapatalk 4

I'd say the main thing holding my Pi back is silverlight drm. Otherwise I'd be perfectly happy with my xmbcrpi.

Is it Possible to Run Android 5.0 / Android TV on Raspberry Pi 2?

Hello i'm kind of new to this so please don't be to harsh .
To run Android TV, android 5.0 would need to be ported first thus me titling this "Is it Possible to Android 5.0 / Android TV on Raspberry Pi 2?" However my main subject / me making this post is to see if Android TV on Pi 2 is feasible.
I was thinking would be possible to run Android TV on the new Raspberry Pi? I ask this because the specs of the new Pi 2 are quite impressive and I can totally see this becoming popular as I can imagine a lot of people would go out and buy a Pi just to run android tv on it (me being one of them) . This would be great as not only would it provide a large install base for Android TV (which in turn up the developer support) it would make it so almost anyone can have a cheap chrome cast type of device with a functional GUI. I don't know if this is possible but doing some research I can't see any reason why it would't work and it would make for such a cool and inexpensive android tv box! :good:
Possible short comings would be:
Lag due to low clock speed
Lack of a remote (possible use of a bluetooth controller or a smart phone app to control the box using wifi)
Poor Gaming capabilities?
Probably a few more.

Thomas_Bam said:
Hello i'm kind of new to this so please don't be to harsh .
To run Android TV, android 5.0 would need to be ported first thus me titling this "Is it Possible to Android 5.0 / Android TV on Raspberry Pi 2?" However my main subject / me making this post is to see if Android TV on Pi 2 is feasible.
I was thinking would be possible to run Android TV on the new Raspberry Pi? I ask this because the specs of the new Pi 2 are quite impressive and I can totally see this becoming popular as I can imagine a lot of people would go out and buy a Pi just to run android tv on it (me being one of them) . This would be great as not only would it provide a large install base for Android TV (which in turn up the developer support) it would make it so almost anyone can have a cheap chrome cast type of device with a functional GUI. I don't know if this is possible but doing some research I can't see any reason why it would't work and it would make for such a cool and inexpensive android tv box! :good:
Possible short comings would be:
Lag due to low clock speed
Lack of a remote (possible use of a bluetooth controller or a smart phone app to control the box using wifi)
Poor Gaming capabilities?
Probably a few more.
Click to expand...
Click to collapse
My research indicates this would be difficult, however, if a Chromecast type Media Center is what you're looking fo, I have good news. There are 2 OS downloads that are essentially XBMC ports for Pi 2.
http://www.raspberrypi.org/downloads/
I bought a Pi 2 today and am waiting for them to provide a delivery date. I intend to use it with one of these XBMC OS'S.

Thomas_Bam said:
Hello i'm kind of new to this so please don't be to harsh .
To run Android TV, android 5.0 would need to be ported first thus me titling this "Is it Possible to Android 5.0 / Android TV on Raspberry Pi 2?" However my main subject / me making this post is to see if Android TV on Pi 2 is feasible.
I was thinking would be possible to run Android TV on the new Raspberry Pi? I ask this because the specs of the new Pi 2 are quite impressive and I can totally see this becoming popular as I can imagine a lot of people would go out and buy a Pi just to run android tv on it (me being one of them) . This would be great as not only would it provide a large install base for Android TV (which in turn up the developer support) it would make it so almost anyone can have a cheap chrome cast type of device with a functional GUI. I don't know if this is possible but doing some research I can't see any reason why it would't work and it would make for such a cool and inexpensive android tv box! :good:
Possible short comings would be:
Lag due to low clock speed
Lack of a remote (possible use of a bluetooth controller or a smart phone app to control the box using wifi)
Poor Gaming capabilities?
Probably a few more.
Click to expand...
Click to collapse
Probably the same conclusion as this:http://forum.xda-developers.com/hardware-hacking/raspberry-pi/rd-android-4-4-4-t2816952

XBMC for RPi already supports CEC through the HDMI... So most of your remote problems are solved there. A wireless Bluetooth keyboard/touchpad also solves the problem.

Yes, I can confirm that, I'm using osmc(aka raspbmc) for more that one and a half years and the performance is a quite good, even if I have allot of other things running on my pi...
CEC is supported, but be careful if you own a LG webos tv you should not us this, cause will slow down your tv and make it unresponsive, as far as I know only webos TVs are afected(2014 models).
But anyhow if raspbmc has a good performance on the old rpi B, I think should perform way faster on the new pi2.
I'm planning also to upgrade my pi..

From what is being reported on the Kodi forums, the Pi2 does very well with it. There is already a branch of OpenElec for it, and I think also one for RaspBMC/OSMC with a lot of the add-ons under recompilation during this week to give full support. But it's certainly getting full support from the dev community there, which is great.
But as noted even the Pi1 does very well anyway with Kodi, my overclocked B+ with OpenElec 5.0.1 works fine with it and no issues at all that I encounter day to day. Nice and smooth, and fully supports CEC from my (dumb) LG HDTV. And if you prefer, there's decent remote control for Android/iOS (Yatse) and web-based remote built into Kodi itself.
I'd certainly recommend it as an excellent alternative to AndroidTV.

The Android porting issue is the lack of graphics chip support

I'm wanting to see this as well, namely because Android TV also offers direct support for Netflix, Hulu, Plex, and others. While you can potentially get these with an xbmc based build, it will not work well with remotes.

Rakeesh_j said:
I'm wanting to see this as well, namely because Android TV also offers direct support for Netflix, Hulu, Plex, and others. While you can potentially get these with an xbmc based build, it will not work well with remotes.
Click to expand...
Click to collapse
The Pi supports CEC, so if you've got a suitable TV and the two are connected by HDMI then you're fine to go. I run my OpenElec set-up on my Pi1 using the remote of my LG dumb TV, and it's a doddle. It does have a wireless keyboard and mouse connected to it for it's other life as a Raspbian programming box for the kids (Scratch/Minecraft/Python) but I don't recall the last time I took up either when it was running in its OpenElec identity...
There is certainly an implementation of Plex for OpenElec. Not sure about the others, as I don't use any of them.

DarrenHill said:
The Pi supports CEC, so if you've got a suitable TV and the two are connected by HDMI then you're fine to go. I run my OpenElec set-up on my Pi1 using the remote of my LG dumb TV, and it's a doddle. It does have a wireless keyboard and mouse connected to it for it's other life as a Raspbian programming box for the kids (Scratch/Minecraft/Python) but I don't recall the last time I took up either when it was running in its OpenElec identity...
There is certainly an implementation of Plex for OpenElec. Not sure about the others, as I don't use any of them.
Click to expand...
Click to collapse
That isn't the problem. The remote itself works ok, and the device can see the events. The problem is the individual applications require different key bindings. I've done all of that crap where you configure different profiles and whatnot to bind different remote presses depending on the app, but it breaks all the time and maintaining it sucks balls.
Not doing that again. It's better just to have one cohesive interface that each app responds to identically. Android TV provides exactly that.

Two years ago, tried a hand at Android 2.3 on the Raspberry Pi after seeing an article on Cnet.
:silly:
Utterly terrible failure. They have then proceeded to pulled the article down.

YES, it's possible, GUI at 10-15fps with SW rendering. Slow but useable.

confused
I don't understand. Broadcom has released the sourcecode for the gpu including register-level documentation.
http://blog.broadcom.com/chip-desig...ves-developers-keys-to-the-videocore-kingdom/
The downloads are at the bottom of the http://www.broadcom.com/support/ page.

ddfault said:
I don't understand. Broadcom has released the sourcecode for the gpu including register-level documentation.
http://blog.broadcom.com/chip-desig...ves-developers-keys-to-the-videocore-kingdom/
The downloads are at the bottom of the http://www.broadcom.com/support/ page.
Click to expand...
Click to collapse
Actually, the problem is not that(the stack was adapted to GNU/Linux, see github.com/simonjhall/challenge but with memcpys), it is just that it depends on a Linux 3.0 kernel driver for full functionnality(HW layers). That driver is still not ported to modern kernels(the official RPi kernel is 3.19!)
It is fully doable. On IRC with the primary developer of Replicant, he said that porting Mesa/VC4 with adding Android support would take a few time with mostly buildsystem changes .(he ported llvmpipe)

CFP with a comment
I would like to use Android version 4.2.2 Jellybean! on my RP2+, Please understand i don't really quite understand everything you guys are saying, I just would like a straight answer, can it be done? My pi is version 2+ 512MB ram not the four core version.
THANKS!
Clancey A

tyrian869 said:
I would like to use Android version 4.2.2 Jellybean! on my RP2+, Please understand i don't really quite understand everything you guys are saying, I just would like a straight answer, can it be done? My pi is version 2+ 512MB ram not the four core version.
THANKS!
Clancey A
Click to expand...
Click to collapse
No. Check back in 6 months, maybe someone will have Lollipop running on it by then!

Android TV on Raspberry Pi 2... That's a dream...

Well, I have a question...
Got the Raspberry Pi 2 with 512MB of ram, and I've tested the beta Android found here, and it's usable (just usable, it has lag, and many things can be done to it to became perfect). Why doesn't anyone try to port that Android on Raspberry Pi 2? Now we have a 900Mhz Quad Core CPU and double the ram...

Could you please provide mode details?
What' the issue with the Wi-Fi?
How is the general performance of the Lollipop?
Do you have Play Store installed?

khrystyan27 said:
Could you please provide mode details?
What' the issue with the Wi-Fi?
How is the general performance of the Lollipop?
Do you have Play Store installed?
Click to expand...
Click to collapse
"not worth much without hardware acceleration", i would say its totally useless.

Chromiumcast OS

Since Chromecast OS is basically a cut-down version of Chrome OS, shouldn't the code be in Chromium OS codebase?
If so, we should build a Chromiumcast OS and port it to those MiniPC's on them market (if we have the kernel sources and drivers).
Can anyone check the possibility of the above?
However, since Chrome OS uses a different kind of boot image, we should ask Chainfire for help, since he is working on the Chromebook Pixel, as it has such a boot image.
It is funny thought, Google puts Android on a Chromebook, and we may put Chrom(ium) OS on Android devices.
Update 1: Sorry for posting this here, XDA Labs isn't letting me reply to my own thread, but why not port it?
We should make it a full Chromium OS (with the abilities to make a local owner account and recieving casts, as well as casting to another device), while we're at it.
Update 2: Apparently it's a known XDA Labs server API issue, they're working on though, for now I need to wait for there to be a 2nd page to be able to post seperately from the opening post.
If it's just a webpage, then how about packaging it for the different systems (Windows, OS X, Linux, Android, Ubuntu Touch, Firefox OS, iOS, Windows Modern (8/8.1), Windows Universal (10), Sailfish, Unix, Chrome OS, etc.)?
Yes, I'm aware that half of these technically (via ports, for example) are either Linux or Unix (and that Linux is a port of Unix).
I would have included SkyOS, however it appears to have been discontinued before even graduating Alpha... several years ago.

It's not really a cut down version of Chrome OS but more of a cut down version of the Chrome Browser sans any ability to run Chrome OS Apps.
Similar to the chrome browser you find in an Android Phone.

It has nothing to do with what the OS is based on, the important part isn't the OS, but the actual cast receiver application. I was tinkering around with it for a little while and ended up with a not-entirely-functional APK file that implemented a cast receiver, using actual google code and libraries. Installed it on a Nexus 7, which was discoverable as a cast receiver on the network. More important thing to work on led to ignoring the project for a while.

doitright said:
It has nothing to do with what the OS is based on, the important part isn't the OS, but the actual cast receiver application. I was tinkering around with it for a little while and ended up with a not-entirely-functional APK file that implemented a cast receiver, using actual google code and libraries. Installed it on a Nexus 7, which was discoverable as a cast receiver on the network. More important thing to work on led to ignoring the project for a while.
Click to expand...
Click to collapse
The Cast Receiver is usually not much more than an HTML5 webpage.

Asphyx said:
The Cast Receiver is usually not much more than an HTML5 webpage.
Click to expand...
Click to collapse
The cast receiver is a LOT more than a webpage.

doitright said:
The cast receiver is a LOT more than a webpage.
Click to expand...
Click to collapse
you can browse them all in just about any browser.
Want proof
Look at the linkage in the whitelist and go to the URLs for any receiver...
Example....
https://www.gstatic.com/cv/cast/apps/receiver/webrtc/stable/receiver1.html
They may call them HTM5 Applications but when it comes right down to it there is no difference between that and a webpage. Only in rare cases will they put security that denies a browser from loading them and in most cases if it fails to work it is only because they require and use some firmware code (i.e. Video Player) to function.

Asphyx said:
you can browse them all in just about any browser.
Want proof
Look at the linkage in the whitelist and go to the URLs for any receiver...
Example....
https://www.gstatic.com/cv/cast/apps/receiver/webrtc/stable/receiver1.html
They may call them HTM5 Applications but when it comes right down to it there is no difference between that and a webpage. Only in rare cases will they put security that denies a browser from loading them and in most cases if it fails to work it is only because they require and use some firmware code (i.e. Video Player) to function.
Click to expand...
Click to collapse
That web page does absolutely nothing.

doitright said:
That web page does absolutely nothing.
Click to expand...
Click to collapse
Except load the receiver app that is waiting for linkage information from the app that was supposed to launch it when it connected to the CCast!
99.9% of the work is done at the controlling device not the receiver app.
That is the only thing the CCast actually loads the rest is sent to that receiver by the Controler app!
When you connect to the CCast from an app that's all the CCasts loads. Once loaded you can then send content to that Receiver.
Here is the receiver app Plex tells the CCast to load when you first connect their App to the CCast....
https://chromecast.plex.tv/production/index.html
The receivers are nothing more than webpages with various media players and java applications.

Asphyx said:
Except load the receiver app that is waiting for linkage information from the app that was supposed to launch it when it connected to the CCast!
99.9% of the work is done at the controlling device not the receiver app.
That is the only thing the CCast actually loads the rest is sent to that receiver by the Controler app!
When you connect to the CCast from an app that's all the CCasts loads. Once loaded you can then send content to that Receiver.
Here is the receiver app Plex tells the CCast to load when you first connect their App to the CCast....
https://chromecast.plex.tv/production/index.html
The receivers are nothing more than webpages with various media players and java applications.
Click to expand...
Click to collapse
Just keep telling yourself that it actually does something. :good:

doitright said:
Just keep telling yourself that it actually does something. :good:
Click to expand...
Click to collapse
There really is no teaching the ignorant....
That page is the only thing the CCast loads!
The rest is done on the mobile device and that receiver does nothing without the mobile device connecting to that page you say does nothing...
Tell me did you try reading the source code of that page or was that too difficult for you?

Asphyx said:
There really is no teaching the ignorant....
That page is the only thing the CCast loads!
The rest is done on the mobile device and that receiver does nothing without the mobile device connecting to that page you say does nothing...
Tell me did you try reading the source code of that page or was that too difficult for you?
Click to expand...
Click to collapse
Let me make this very clear;
1) Install https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en
2) Run it.
3) hit the chromecast button. Oh, there is none! Too bad.

doitright said:
Let me make this very clear;
1) Install https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en
2) Run it.
3) hit the chromecast button. Oh, there is none! Too bad.
Click to expand...
Click to collapse
Took you long enough to find the ONE RECEIVER APP (and it is the ONLY APP) that doesn't get loaded from the WEB because it is part of the CCast Firmware!
I find it interesting that in a discussion of RECEIVER APPS you show something from the play store where there are no receiver apps to try and prove your wrong point.

Just look at the Chromecast firmware, there's custom ROMs here. In theory you could just look at it and experiment...

I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?

moriel5 said:
I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?
Click to expand...
Click to collapse
That would be awesome!

I think it could be a perfect combo to turn a Raspberry Pi into a casting device. Chromium OS already exists for Raspberry Pi, but it still has to be improved. http://www.chromiumosforsbc.org/

DaniPhii said:
I think it could be a perfect combo to turn a Raspberry Pi into a casting device. Chromium OS already exists for Raspberry Pi, but it still has to be improved. http://www.chromiumosforsbc.org/
Click to expand...
Click to collapse
I agree, but I would love if someone managed to remove the mandatory Google login, otherwise I won't use it.
Deleted my account some time back, don't want to open another one.

moriel5 said:
I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?
Click to expand...
Click to collapse
I was searching online for this b/c i figured someone would have done it by now. I'd really like to see android TV on chromecast

x000x said:
I was searching online for this b/c i figured someone would have done it by now. I'd really like to see android TV on chromecast
Click to expand...
Click to collapse
But the Google log-in should be optional, not mandatory.

RPi Openauto Project - Can't get music to work, can anyone help please?

Hi,
I'm currently building a Raspberry Pi (3) Android Auto project for my 55 year old Land Rover. I'm using Openauto installed on Raspbian (rather than using Crankshaft) so I can also add reversing cameras, ultrasonic sensors and so on, more easily.
Anyway, I the system so far:
RPi 3b running Raspbian Stretch
7" Touchscreen
USB soundcard with mic input.
It took a while but I finally configured the audio and it's working, at least Google Assistant and I think Navigation prompts (but it's difficult to assess that, the system isn't installed yet so it isn't going anywhere). The problem I am having is I can't get music at all. The music apps work, and I can use BBC iPlayer Radio no problem. I just can't get either Google Play Music or Pulsar working with locally stored files - There isn't any sound output at all. Mike input works, I tested the soundcard in Raspbian and it outputs audio now (after finding a guide and editing configs, it didn't work at first out of the box)
I'm not an expert on Linux or Android, I'm following guides so consider me a beginner if you would please! Also, if this has been covered before, I do apologise for bringing it up again, any and all help is very much appreciated. I also apologise if it is forum etiquette to introduce oneself before asking questions, I don't mean to be rude.
And here I was thinking the most difficult step would be figuring out how to mount/fit everything into the old bus...
Many thanks,
Ste