I have looked through many forums recently, and I have yet discovered at starcraft game for the pocket pc. I have finally realized that pocketDOS won't do the trick, because it is build upon 8-bit architecture while starcraft/warcraft was build upon 16-bit plus extended memory requirements.
After that I discovered that someone got warcraft II working on a PPC. To do this they used stratagus for pocket pc and then converted the original warcraft-game in wargus. I looked further and I discovered stargus (starcraft) which is also running on the same engine (stratagus).
AND...I wonder if someone on this forum would make stargus work with the stratagus pocket pc engine??
I even think people would pay to have starcraft on their PDA
PS: I'm a noob on programming myself so don't yell if i am totally wrong here..and my English is probably bad
Starcraft is a Win32 x86 32bit at-least 800x600 protected mode application using DirectX - I don't think it will run on any WiMo 640x480 PPC within the next 10 years unless someone finds impressive amounts of spare time to emulate an entire x86 Win32 environment along with DirectX...
there goes my dream...
thanks for the help anyway...
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*
Hi,
I was asked to post my question here instead of the chromecast help forum.
I recently installed Linux Mint 16 (cinnamon), Google Chrome (along with the Chromecast plugin) 64 bit version on my machine. The cast tab, feature doesn't work well. There is a severe lag when browsing pages and online video streaming (I would say it looks like a slide show). When I cast a local video file (.avi for example), some times the video is good but the sound comes out of my laptop instead of the TV.
I know the cast worked well in my previous Linux Mint 13 version which was 32 bit. I installed a Linux Mint 16 (32 bit) version to confirm that Mint 16 didn't introduce any issue and it worked like normal.
Since I knew it was working fine on my 32 bit versions, I tried installing a 32 bit chrome along side my existing 64 bit version. After much tinkering with libraries and firefox dependencies, I got it to work like normal. But recently I started to encounter the same issues (on the 32 bit version) that I see on the 64 bit version. I am not sure what needs to be done. Youtube casting works fine from the 64 & 32 bit chrome version. I want to keep Mint 16 64 bit and want to find a solution to this.
Casting a tab works very well on my wives Windows 8 machine, via iPad and iPhone.
OS: Linux Mint 16 (cinnamon) 64 bit
Router: Belkin
TV: Sony Bravia
Looking forward to your comments.
Raghav
Tab casting is for chumps. Install Plex or there is a chrome app. Forget what its called but search for it yourself. Either one will give much Better results than tab casting.
Sent from my Nexus 5 using Tapatalk
I'm used to running Debian Testing on my laptop and the stability it is quite stable; however, my Pi has a couple bugs.
1) Chromium package not found with aptitude or apt, but is referenced. I've rebooted my Pi and updated my sources, but that didn't fix the problem.
2) I'm using my Pi as a home media server and a print server. The problem right now is that my Pi won't display any video from Kodi. The screen goes black and the time for the show works, but no video is playing.
I've done research on Stackoverflow, but I haven't encountered these same problems. I'm hoping to avoid a reinstallation, and any help would be great.
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page. Also check OpenAuto Pro.
Whoa, nice work. Would this also have a audio EQ/Crossover interface for the Pi?
Can you post a Windows binary build please? Thanks
Daved+ said:
Can you post a Windows binary build please? Thanks
Click to expand...
Click to collapse
Is this at least possible OP? Noobs here, Thanks in advance.
Will this work as standalone or does it need the app?
"Do not use while driving" Well where is the fun in that?
look like someone may able create Open AA instead and resolve blocking issue by google..i guess
Time to give my ride a sweet upgrade
Will raspberry survive high or low temperatures?
I'm trying to compile it, but I got a bit rusty in building under linux.
Code:
[ 6%] Building CXX object CMakeFiles/autoapp.dir/src/autoapp/Main.cpp.o
In file included repos/android-auto/openauto/src/autoapp/Main.cpp:19:0:
repos/android-auto/openauto/include/f1x/openauto/autoapp/USB/USBMain.hpp:22:40: fatal error: f1x/aasdk/USB/USBWrapper.hpp: No such file or directory
#include <f1x/aasdk/USB/USBWrapper.hpp>
Did I forget something when configuring with cmake?
f1x said:
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page.
Click to expand...
Click to collapse
Hi! First of all, thank you for bring us this post! Amazing I've the same question as another guy here, Could you post the Windows binaries or link to the step by step to get it running under windows?
Thanks a lot in advance!
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
bluethoot
What can you do with the bluethoot feature ?
xbenjiiman said:
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Click to expand...
Click to collapse
Thanks for your feedback. Great to see it working .
Zaf9670 said:
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
Click to expand...
Click to collapse
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
brett1996 said:
What can you do with the bluethoot feature ?
Click to expand...
Click to collapse
What do you mean?
f1x said:
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
Click to expand...
Click to collapse
I wasn't sure how much of Android Auto is "open" to use. I haven't invested too much time looking into these forks like Auto and Wear but I know they're not quite as public as standard Android. At least that is the take I have gotten over the past few years.
Hopefully it's something that won't require some sort of specific hardware. Best of luck! I hope to test this out on my Pi 3 in a few weeks myself. I'll be sure to keep tabs on the project!
I promise I'm not one of those XDA ETA/update zombies.
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
MasterCLC said:
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
Click to expand...
Click to collapse
Only Raspberry PI 3 has been tested so far in case of embedded platforms. Code itself is portable for any Linux-based or Windows platforms. If hardware acceleration of video decoding is supported by underlying backend used in Qt multimedia library (GStreamer for Linux and DirectShow for Windows) then OpenAuto will run smoothly without additional effort. If hardware acceleration is not supported by underlying backends then it must be implemented in OpenAuto (like in case of Raspberry PI 3).
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
MasterCLC said:
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
Click to expand...
Click to collapse
Screen is the official one from PI Foundation (7''). Basically any screen should be suitable to run OpenAuto (as long as it is supported by the OS that hosts OpenAuto). The same for other hardware.
Dude! You're my hero, I've been playing around with so many ways to get this working, yours seems to be the perfect solution, I'll take it for a test drive tomorrow