31–40 of 40 posts
Wow.. I am getting old.. I still remember being a kid and read that minicomputers were a cabinet size computer (http://en.wikipedia.org/wiki/Minicomputer) as opposite to microcomputers which were desktops... I guess it's time to upgrade definitions :)
I still don't understand the desire for Android on non-touch devices. At all... The more exciting bit is XBMC being available in Android, in my opinion. I have XBMC on my desktop, laptop, phone, tablet and raspberry Pi. Using a single app, I can play media from any of those devices to another. It's so simple and elegant and it blows my mind everytime I do it.
"I still don't understand the desire for Android on non-touch devices. At all..." I have personal experience with this. My old asus eee 1000 netbook is now an android laptop running ICS. Check out android-x86.org. Its free and easy to set up. It works. It works Very well. I've got a huge catalog of apps, it does what I want it to do, exactly like my phone. Basically whenever I'm doing something on my phone where I wi…
"Raspberry Pi, the credit card sized low cost mini-computer..." Wow.. I am getting old.. I still remember being a kid and read that minicomputers were a cabinet size computer ( http://en.wikipedia.org/wiki/Minicomputer ) as opposite to microcomputers which were desktops... I guess it's time to upgrade definitions :)
Partly because of the ridiculously out-of-date "Computing Studies" Intermediate 2 Scottish Qualifications course I did at school, but it's mostly because I had the privilege of growing up with Windows 3.1, DOS, and QBASIC, as well as an old book from a used book store for beginners about "Programming Microcoputers".
10 INPUT "Hello! What is your name?", A$
20 PRINT "Hello there, ", A$Earlier quoted context omitted.
The ability to run Android apps would be the key. Plus, for an HTPC, Android (tablet UI or Google TV, take your pick) has a much better interface than XBMC, IMO.
But the RPi is an awful HTPC, it's way too underpowered and can only barely cope with 720p decoding. It definitely doesn't cope well with having to do composite overlays like XBMC uses to display controls. The FPS you get in the menus is only also only barely acceptable so even if your content does play the experience is choppy. Yes it's cheap, but it still sucks.
No, it doesn't play my 13GB copy of Tron, but it plays every single 720p MKV I've thrown at it.
Earlier quoted context omitted.
with my pi/raspbmc the 1080p movie playback is indeed smooth but the menus stutter awfully. But the reason for that might be that the menus doesn't fully utilize the opengl es of the pi or something else (bad skin?) so I wouldn't blame the pi yet.
That seems to be a common issue with UI on the Pi... I think a few things are going to need to be rewritten to push work away from the CPU and onto the GPU. Waiting with baited breath for mine to turn up! :-)
However, it was very naive of the grandparent poster to think that slow CPU powered menu screens means that the hardware accelerated video is lacking.
I still don't understand the desire for Android on non-touch devices. At all... The more exciting bit is XBMC being available in Android, in my opinion. I have XBMC on my desktop, laptop, phone, tablet and raspberry Pi. Using a single app, I can play media from any of those devices to another. It's so simple and elegant and it blows my mind everytime I do it.
I still don't understand the desire for Android on non-touch devices. At all... The more exciting bit is XBMC being available in Android, in my opinion. I have XBMC on my desktop, laptop, phone, tablet and raspberry Pi. Using a single app, I can play media from any of those devices to another. It's so simple and elegant and it blows my mind everytime I do it.
Getting Android running is just one step along the way to getting ChromeOS running (and that effort has already started).
Earlier quoted context omitted.
Getting Android running is just one step along the way to getting ChromeOS running (and that effort has already started).
No. It's not. ChromeOS has nothing to do with Android.
Earlier quoted context omitted.
That seems to be a common issue with UI on the Pi... I think a few things are going to need to be rewritten to push work away from the CPU and onto the GPU. Waiting with baited breath for mine to turn up! :-)
Nah, look at the history of XBMC (started on the Xbox), it's a nasty piece of work when rendering to the screen. However, it was very naive of the grandparent poster to think that slow CPU powered menu screens means that the hardware accelerated video is lacking.