Hi all,
There is a software driver for Windows Mobile devices for OpenGL ES
Its here http://www.vincent3d.com/index.html
The thing is that this is NOT hardware accelerated, but the source code is available.
I downloaded GLBenchmark and without it it would not run, but with the file
libGLES_CM.dll
from the above project it runs (I'm currently running it, so I don't know the results, and even if it can render anything)
Thoughts:
Does this file exist on the other phone that had MSM7200 HW acceleration? Chainfire?
If it does, and the only thing it references is QTV.dll and/or Q3dimension.dll
it would most probably work on our TyTN IIs
IT WOULD NOT HELP WITH VIDEO OR SCROLLING OR DIRECT3D, but it would allow games that use OpenGL ES
If it does not exist, then we have to learn how QTV and Q3dimension work (As corecodec did with QTV) so that we can make the appropriate changes on Vincent's driver.
Please, if you are not a developer with C++ experience DON'T POST SPECULATIONS
Thanks
PD GLBenchmark is running but it does not show anything on the screen.
Well, are there other programmers here?
The problem is we don't have the specs for how to 'talk' to the hardware. If we did, maybe, with a LOT of work, we could make it work. But this software driver won't be any help in it
The HWA OpenGL ES driver from the KS20 depends on a LOT of stuff that is different between the Kaiser and the KS20...
Chainfire said:
The problem is we don't have the specs for how to 'talk' to the hardware. If we did, maybe, with a LOT of work, we could make it work. But this software driver won't be any help in it
The HWA OpenGL ES driver from the KS20 depends on a LOT of stuff that is different between the Kaiser and the KS20...
Click to expand...
Click to collapse
In the thread where you where trying to hack the drivers for the KS20 as I recall, you did not try the OpenGL ES dll, you where trying to use the whole video driver, of course you are the one that know ALL you did
Do you have the KS20 files? I want to have a look.
I know it's a lot of work, but we don't have to figure the hardware, we have to figure out Qualcomms dlls. Are those even in our Kaisers?
I other words, I want to do what corecodec did. And I would think that there have to be more programmers here on xda-developers, not just users or cookers.
I don't have much experience contributing to open source programs, but isn't that the way it is supposed to work, programmers united by some need?
I have not developed for Windows Mobile, but I'm willing to give it a shot if someone here is at least a bit interested
From what I have been reading Qualcomm have 2 dlls that talk to the hardware: QTV.dll and Q3dimension.dll
The problem is that we do NOT have a wrapper that translates DirectDraw Direct3D or OpenGL ES calls into these two dlls
Corecodec is using QTV directly, bypassing this situation. Hopefully they will release all the info they have on QTV. Even if they do SOMEONE has to use that info. I want to at least try.
Has anyone played around with the NDK yet?
It looks really promising, I haven't gotten my dev environment setup on my new machine yet.
Hopefully this can and will make apps much faster by being able to bypass the slowness that is java. Apparently there are native OpenGL ES APIs, Quake on Droid anyone?
I do augmented reality by using library QCAR. I also compiled and used opencv library, and coded in C++ in android NDK:
I have this code in my project:
CvCapture* g=NULL;
g=cvCaptureFromAVI("/sdcard/testa.avi");
if(g==NULL)
__android_log_print(ANDROID_LOG_DEBUG, "libnav","error");
else
__android_log_print(ANDROID_LOG_INFO, "libnav"," ok");
But when it run, i always got "error" in DDMS. I don't know whether android supports loading avi file. If not support, can android support flv, how to load it, which function we must use, maybe in opencv or opengl.
The purpose is get frame from video to texture the rectangle in opengl, (utterly C or C++ )
Please help me! i do it for my thesis.
thanks
I've downloaded Google's Chromecast toolchain, but the compiler it comes with is too old (gcc/g++ 4.5.3) for the software (which requires gcc/g++ 4.8 or newer) I wish to compile for the Chromecast.
What is the easiest way to get gcc/g++/etc. 4.8+ that will work with the Chromecast? Or will any ARMv7 cross compiler do?
Any ARMv7 compiler should do, but it may miss some optimizations that are possibly added to google's compiler
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