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.
Hey XDA Fans,
I'm actually at a position where i want to get rid of my MediaPC. At the moment i can do everything i want with only 1 missing thing. My current setup is, my PC is 3 rooms away and the TV has the ChromeCast. I also have a 5 meter USB cable routed through my rooms close to the TV with a recevier for a wireless Keyboard (mainly because there is no good WiFi Keyboard at the moment). So I can cast my Desktop or Browser to the TV and controll it. But ....
The big Problem, I need a way to start the Chrome Cast via any command, so I can press a Hotkey on my Keyboard to start the streaming so i do not have allways to go to the PC to start the streaming. And this is what I'm looking for currently.
I was looking through the API of Google Cast, but there is no API for Windows/.Net (was mostly clear but hoped for), only for Android and Chrome. So yeah as u guys might allready understand, I'm looking for a way to Start Desktop/Browser Streaming to my ChromeCast with a BatchFile, Scripting, Coding, which i can start via a Hotkey. Do not missunderstand me. If I or u guys could give me a hint with and API with these possibilities I'm able to code it myself. That's not the Problem, but as far as my research went I wasn't able to find anything on myself. So I'm here to maybe get pointed to sth.
Tia Synergi
PS: Sr for my bad english if u guys weren't able after reading the top few lines to understand what I'm looking for tell me I can try to explain it again x)
http://www.ghost-mouse.com
You can record your mouse movements and keyboard keystrokes with ghost mouse. Maybe it will help you.
Heres my situation
I have a 2001 BMW 740i e38. I would like to keep the original display, but integrate a Raspberry Pi as the brains. I found a website that sells an interface that seems to take car of most of my needs.. http://pibus.info/index.html
Heres the question
Is there a way connect with my android via USB for music player, google maps, etc?
This is my first time trying a project of this magnitude, but I have been flashing devices since the HD2, so I do have the ability to at least follow step by step instructions with some mild trouble shooting.
Any help greatly appreciated.
PS
I also have an unused ATT Note II that would be really great to integrate into the system as a touch screen interface, maybe built into the armrest.
Thanks
On the releases page of my Github Project you can download a test build to auto-cast your system audio to the Chromecast.
Run app.exe and it'll auto cast your system audio to the first Chromecast it finds!
Try it out, let me know what you think, and how to improve it!
Direct download link
p.s. I also made Videostream.
Thank you
nice one acidhax. how have you been since videostream? i noticed your no longer on that project.
The program works as expected, no issues with installation or use (Win 8.1 x64).
I noticed that the volume level is fairly low when casting to a Chromecast Audio, is there a way to change the volume that's broadcast that I've missed?
Also, would it theoretically be possible to run multiple instances of the app and have them find two separate Chromecast Audio devices, whilst broadcasting at the same time, or would the current setup create two different individual broadcasts, resulting in un-synced playing? No longer necessary as they've released multiroom, however am still curious as to whether there are volume control options.
Thanks!
Hi,
Interesting project! Can you provide support for command-line pipe support? I like to use with "Shairport4w" (http://sourceforge.net/projects/shairport4w/). This program has the option "Redirecting sound" that can launch and external tool that accept data (raw PCM audio) over default input pipe. As this project is based on NodeJS I hope this can be achieved.
What you think?
Troubleshooting Help
Very cool project. Rookie question but I am getting stuck here:
Example app listening at (ip address here)
Spawned Ffmpeg with command: ffmpeg =list_devices true -f dshow -i dummy pipe:1
VIRTUAL DEVICE FOUND
What should I be doing next?
not working for me nothing connect to my chromecast . no sound nothing only sound of my PC . windows 7 .
edit: sorry it work . did you know how to increase the volume of the chromecast ? thanx you
I have a Bluetooth speaker and but my TV has no Bluetooth . is there a way I count reroute the audio from the Chromecast to the Bluetooth speaker without using any cable or reroute to my computer - since my computer is wirelessly connected to the speaker by Bluetooth?
Any help will be appreciated
I use Plex almost all the time and I don't usually enjoy my movies since my tv sound is bad.
acidhax said:
you can download a test build to auto-cast your system audio to the Chromecast.
Run app.exe and it'll auto cast your system audio to the first Chromecast it finds!
Try it out, let me know what you think, and how to improve it!
p.s. I also made Videostream.
Click to expand...
Click to collapse
Nice! It's working for me on the new Chromecast. How do you 'stop' the app to get back to the Chromecast backdrop?
Also: Thank you so much for making Videostream - it's hands-down the best app for Chromecast!
Hi everyone, first time poster so I'm sorry if this isn't the right forum to post in, but I felt like it was the closest I could think of.
I'm trying to find a way to mimic how the chromecast causes a tv to switch to the input of the chromecast dongle. I have an Android Box that came rooted and has HDMI-CEC capability. What I'm looking to do is somehow use Tasker to trigger the CEC-switch activity/intent/whatever to have my tv (turn on) and switch to the HDMI source of the Android Box (the box will be left on 24/7 and tasker will continually run as background service on the box). Basically, I'm trying to imitate the chromecast's cast action to bring me to my Android Box's input and ultimately it's home screen.
That's where I'm stuck at the moment. Things I've thought might work:
1. Wake-On-Lan (Doesn't seem to wake the box, even when I've checked to make sure the power button made the box sleep and not perform a full shutdown) Tried-Unsuccessful
2. AutoCast to have the box cast to itself, but it doesn't have chromecast/miracast/etc built-in as far as I can tell according to the specs and see anything about cast ability while browsing through its menus.
3. Using Android's HDMI-CEC library in a Java Action in Tasker to imitate the CEC switch sources intent/activity. However, I just recently learned that Google decided to lockdown their API for HDMI-CEC interactivity, so that scrubs that idea.
4. The best bet, and what gave me the idea to post here, is this App Cast Receiver that was created by another user on these forums that seems to accomplish something close to what I'm trying to do in allowing an android device to imitate a chromecast device. If I were able to use this couldn't I then use the AutoCast app I mentioned above to have the Android Box cast to itself, then stop the AutoCast app a few seconds later (after giving the box's CEC capability enough time to make the tv switch sources)? But, unfortunately it appears the app has since been deserted and won't work with the newer chromecast sdk. Maybe someone has an alternative app?
Since this is my first Android Box I'm not quite sure how Tasker actions function when ran from the box. Example: Would a Wake Screen Action trigger a switch of HDMI inputs?
So, after exhausting all my ideas after coming up with nothing in my searches I figured I'd ask the community here since this seems to be a pretty dev/mod-heavy community (and I love it). I'm not sure if this would be better suited for the Tasker or AMLogic Android Box forums on here. If so, I'll happily move the post if a mod cannot do so for me.
TL;DR: Looking for some way, be it app or otherwise, to imitate chromecast behavior (utilizing CEC) in order to make tv switch source to a running Android Box's homescreen.
Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/
jlongman said:
Hey! tell me more about 3, I was looking to have a Raspberry Pi act as a go-between to simulate CEC with a non-CEC TV by receiving my remotes IR codes and sending either CEC codes to the ChromeCast or using the CC API to pause/stop play - but only reverse engineered versions are available on Pi.
The Pi has built-in CEC support so you can use `apt-get install cec-tools` and then play with the `cec-client` to do some interesting stuff. The ChromeCast in my case has an invalid address so I don't seem to be able to activate pause play. (I see a logical address of 4 but also an address of `f.f.f.f`, ie invalid).
Anyways, it may be worth playing with a Pi and seeing if HDMI-CEC will do what you want, and then seeing if you can get a CEC library for android and just recreate the Pi work. Less hoops to jump around.
I don't know enough about the Android side. The CC API has an Android implementation so I would think you'd be able to do everything you want, iff it does the switching. I've done very little development on Android (a meteor app and an Android native camera library work), unfortunately. (If the Pine64 supports CEC I may end up going down this route).
I've posted more about my interest here: on reddit /r/Chromecast/comments/5znpuk/i_want_to_use_a_raspberry_pi_to_control_the/
Click to expand...
Click to collapse
Here's the link to Android's documentation for the HDMI-CEC Control Service. But, like I said it's been locked down and only allows system-level access now.
I don't have any Pi at my disposal (plus my Android Box also has built-in CEC-capability/functionality) and since my situation doesn't actually involve chromecast I never thought to look at their api/sdk. But, I was able to finally solve my problem with a painfully simple, yet not that intuitive or logical method. The way my box's os/firmware appears to work is by firing the cec signal to switch inputs only on its boot_complete and wake_from_standby procedures. My solution just simulates pressing the Standby button twice in a row via Shell command (with Root option checked) from within Tasker. Logically, I thought after the first press the box wouldn't respond to the second press due to already being in standby mode (because of the first button press). But, it turns out both simulated presses occur (maybe keyevents are queue?), allowing me to put the box in standby momentarily and immediately bring it out of standby, which triggers the wake_from_standby procedure and in turn causes the input to switch (or my tv to turn on then input to switch).
My thought with the Pi and CC API was that you would use the PI to monitor the HDMI-CEC bus as the output is controlled by the CC - assuming it switches the input to itself but my TV doesn't support HDMI so maybe that's a bad assumption - and then use that knowledge to replay using the Android HDMI-CEC API. And not understanding what you meant by the API being locked down. That kind of sucks - I was hoping Android would be another bridge platform if the Pi failed me.
Well congrats on a working solution. Cheers!