@pablocrossa, do you have any news pal?
Sounds like a great idea, though I'm going to need some step-by step instructions and an idea of what conditions show success/failure - and a Prototype. (They don't exist yet.) BUT - this type of thing is exactly what I would like to help test.
@pablocrossa, do you have any news pal?
Hi, sorry for taking so long to respond, I'm very busy with uni deadlines and work
Sounds perfect, thanks Grench, hopefully that lets us run the emulator before all units ship. When I hear prototypes start shipping and I'm over this uni workload I'll figure something out with you
Hi, again sorry for the delay, everything's mostly the same except that I've started dwelving into what's needed to make the Google OpenGL ES 1/2 renderer use the native Pyra OpenGL ES 1/2 libraries, with any shims that might be needed. I also THINK that the updated ranchu fork (as opposed to the ancient Goldfish fork) has gained OpenGL passthrough support, which makes life easier without ugly patches and hacks.
But right now the project's on hold until I have a bit more free time.
Hope to get back to you guys with some more progress soon
I'd be willing to say somewhere between 4-6 Months.More than a month just for prototypes?
What's your estimate for the production units?
Hey, could we have the link to the QEMU and Android image you're using? I wanna run it on my PC.Hi, sorry for taking so long to respond, I'm very busy with uni deadlines and work
Sounds perfect, thanks Grench, hopefully that lets us run the emulator before all units ship. When I hear prototypes start shipping and I'm over this uni workload I'll figure something out with you
Hi, again sorry for the delay, everything's mostly the same except that I've started dwelving into what's needed to make the Google OpenGL ES 1/2 renderer use the native Pyra OpenGL ES 1/2 libraries, with any shims that might be needed. I also THINK that the updated ranchu fork (as opposed to the ancient Goldfish fork) has gained OpenGL passthrough support, which makes life easier without ugly patches and hacks.
But right now the project's on hold until I have a bit more free time.
Hope to get back to you guys with some more progress soon
Hey, could we have the link to the QEMU and Android image you're using? I wanna run it on my PC.
I use Gentoo, not Ubuntu, but I would assume the same packages are available. I am comfy compiling things, as long as it's standard compilation procedure. I just want to be able to use Marshmallow on my PC, and none of the things I have tried so far work.Right now I'm running the standard emulator (with a semi-broken 3D) and the standard vanilla Android 6.0 image built for it, are you comfortable downloading and compiling everything on Ubuntu or would you like me to upload? The generated images will be designed for an Ubuntu system but might work elsewhere
I use Gentoo, not Ubuntu, but I would assume the same packages are available. I am comfy compiling things, as long as it's standard compilation procedure. I just want to be able to use Marshmallow on my PC, and none of the things I have tried so far work.
At the moment, no it's not possible. However, it is in theory and some people started playing around with the idea.Can somebody make a little summary about this topic? I have a friend interested and he asked me about android on pyra.
Hi there
I had some time to work on this over the weekend and decided to temporarily switch my approach; I'm now making the official Android emulator (based on the ancient Qemu with backports...) build on ARM.
I have a build optimised for a Cortex-A15 with FPU+NEON, using the TCG (read: no CPU acceleration) and the host OpenGL libraries (read: GPU acceleration on desktop GL 2, not GLES devices), and soon I will have backported the ARM KVM support introduced in 1.5.0 from version 1.7.0 (some structures within the emulator code align with 1.7.0, so that's where I'm ripping the code out from), which includes GIC support.
I can't get Android to boot because, with GPU acceleration disabled and after waiting 2mins (the emulator window opens with the right skin etc), I still get a black screen. I suspect it's more due to the fact I'm running TCG on TCG on a 2.4GHz Core2Duo, which means the resulting emulator is probably too slow to get anywhere anytime soon (probably about 1% of the speed of the actual CPU AKA not usable at all). I can connect through Telnet though.
This is a call for testers, so if you:
And preferably have:
- Have a Cortex-A15 device
- Have support for NEON and FPU
- Can run an X server on it (even through XVNC or whatever Android users have to do now)
- Can run an Ubuntu 14.04 system (be it native or chroot)
Please get back to me so I can send you the binary and Android 5.1 system images + boot script to test nothing is severely broken. Testing on both TCG and KVM mode would be fantastic, with additional testing against Mesa with the host rendering libraries being a huge help too. If KVM works and the host libraries are not broken then the only step missing is to re-write the translator's GLX code to use EGL and possible intercept some problematic OpenGLES calls that cannot be run native (not a GL expert myself really...) and a basic system would be ready to roll
- A KVM-enabled kernel (but testing in TCG mode would still help)
- Mesa (so we can test the host rendering libs)
Trashy?
Thank you all for the help
Well, he was last seen on May 4, so...@pablocrossa Hey, even if the VM doesn't support 3D, android apps that don't need it will still work right? Like Google Maps, or Words with Friends, or maybe Netflix?
I know, I was hoping I could use what he's done so far, even if 3D doesn't work.Well, he was last seen on May 4, so...
As there are at least two projects for running Android apps under Linux (if arch supported which it is); will any of those work?