Theres not really anything that android gives that debian won'twussie wrote:Ah, but what I want android will give me while Linux won't
That sucks about the DRM issue, I really wish Netflix used HTML5 or another DRM solution other than silverlight. Netflix isn't my only reason for wanting to use Android on my Pi though. It was just the main reason. I intend to create a game console / media center based on my Pi and using the GPIO pins would make it cheaper and easier to interface the controllers I want to use. Perhaps I'll get lucky and the issue will get resolved in the next month or so when the foundation backed ICS port is released. I likely won't be finished with my build until then anyway. Thank you for your help 6677!6677 wrote:Netflix relies on the DRM server being available, in all the current android ports this is missing (some sort of compatibility or licensing issue on the pi). So really you've lost your only advantage
Mhm, you know you can just use the usb ports for controllers rightwussie wrote:That sucks about the DRM issue, I really wish Netflix used HTML5 or another DRM solution other than silverlight. Netflix isn't my only reason for wanting to use Android on my Pi though. It was just the main reason. I intend to create a game console / media center based on my Pi and using the GPIO pins would make it cheaper and easier to interface the controllers I want to use. Perhaps I'll get lucky and the issue will get resolved in the next month or so when the foundation backed ICS port is released. I likely won't be finished with my build until then anyway. Thank you for your help 6677!6677 wrote:Netflix relies on the DRM server being available, in all the current android ports this is missing (some sort of compatibility or licensing issue on the pi). So really you've lost your only advantage
Look into the android ndk, it compiles against the android libraries, however youd have to make and implement the gpio library =/wussie wrote:I'm putting my pi into an old nes, interface the original controller ports directly to the gpio pins, relatively easy to do and cheaper than converting them over to USB using a teensy or other avr. What I want is still possible using USB, and I'll have an open USB port on my hub, but I digress. I wanted to use Android from the start, but after seeing what happened with the first port of ICS figured it was much farther away so started working with raspbmc to get what I want. I know there are dev options for android, especially to interface with an arduino or the ioio, but wanted to know if I could do something with the gpio and port the code over to android for polling the nes controllers.
I'll take a look at it and see if I can get it working for me, thanks!aaa801 wrote: Look into the android ndk, it compiles against the android libraries, however youd have to make and implement the gpio library =/
should be fineaxelbarry00 wrote:Hi again..what do you think about using wiring pi libraries including the C code of these libraries via Android ngk (as you already suggested)? The creator of this library told ( https://projects.drogon.net/raspberry-p ... omment-320) that it works at kernel level (are closer to drivers than api libraries) so,since android works on linux kernel,it should work,right?
It would be a good solution...