'SPURV' Project Brings Windowed Android Apps To Desktop Linux (androidpolice.com)
mfilion shares a report from Android Police: A new "experimental containerized Android environment" from a company called Collabora allows Android apps to run in floating windows alongside native applications on desktop Linux. You can read all the technical details at the source link, but put simply, 'SPURV' creates a virtual Android device on your Linux computer, much like Bluestacks and other similar tools. There are various components of SPURV that allow the Android environment to play audio, connect to networks, and display hardware-accelerated graphics through the underlying Linux system.
The most interesting part is 'SPURV HWComposer,' which renders Android applications in windows, alongside the windows from native Linux applications. This is what sets SPURV apart from (most) other methods of running Android on a computer. For this to work, the Linux desktop has to be using the Wayland display server (some Linux-based OSes use X11). Pre-built binaries for SPURV are not currently available -- you have to build it yourself from the source code. Still, it's an interesting proof-of-concept, and hopefully someone turns it into a full-featured product.
The most interesting part is 'SPURV HWComposer,' which renders Android applications in windows, alongside the windows from native Linux applications. This is what sets SPURV apart from (most) other methods of running Android on a computer. For this to work, the Linux desktop has to be using the Wayland display server (some Linux-based OSes use X11). Pre-built binaries for SPURV are not currently available -- you have to build it yourself from the source code. Still, it's an interesting proof-of-concept, and hopefully someone turns it into a full-featured product.
>"A new "experimental containerized Android environment" from a company called Collabora allows Android apps to run in floating windows alongside native applications on desktop Linux."
I have heard this kind of thing many times before and tried many of them with limited success. Something always seems to be wrong or broken or missing. AndroVM, Virtualbox, Archron, Android-X86, Genymotion, Anbox, I keep holding out hope.
>"For this to work, the Linux desktop has to be using the Wayland display server"
Yuck. Oh well, guess this one uninteresting.
The ads. Think of the ads on another OS in the OS.
Domestic spying is now "Benign Information Gathering"
Spurv? Does it use Spurving bearings?
Weston, the reference compositor for Wayland, has a special feature where you can use it to run Wayland clients under X.
What's wrong with Virtualbox? I use it every day.
I don't respond to AC's.
Seems all attempt to run Android Apps Windowed Android Apps To Desktop Linux are containerized and windowed. I would like to see uncontainerized or unwindowed ones.
OK, right. Just like "some cars don't use Telsa chargers".
Is there some agenda to inverting the tried-and-true and the new-but-woefully-incomplete-and-incompatible here?
Last time I looked, about 10 years ago, Psi had all of those features and many more. I tried Conversation a couple of years ago and found it somewhat lacking in comparison to the features that desktop X11 XMPP clients had had a decade earlier.
I am TheRaven on Soylent News
As an android developer, I can see this is potentially quicker for testing than an emulator or a connected phone.
It's a bit of a niche use, but it's a use.
A windowed app in 2019? That's heresy! Everything must run full screen and tabbed to waste as many pixels as possible. Multi-tasking confuses users and windows? No... Those can move and then you become overwhelmed and lost. The ideal interface should be a large button in the middle of the screen labeled: "Do what you think I want, I'm the product, not the user."
Mind the frickin' laser...
As an android developer, I can see this is potentially quicker for testing than an emulator or a connected phone.
It's scarcely faster, and you still have to test in the emulator, if not on an actual phone. You can't count on the emulator providing accurate results, let alone something like this.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
I'm not talking about detailed testing. Just running and checking during develop. It takes long enough to upload to a device that the wait becomes tedious. And generally I just want to do a few basic checks when I develop. Are the UI components in the right place and the right colour? If I press a button does it do what I expect it to? Does it crash in a simple use-case?
Perceived size of an application's display is proportional to the ratio between the screen size and the viewing distance. If I'm sitting 3.3 times as far from a 30" TV as I'd put my eyes from a 9" tablet, the display on the two will project to the same size on my retinas. This is why CSS's px unit is defined as 1/2688 of the viewing distance (based on a 96 dpi display 28 inches away), not as literal pixels.
But you're correct that the desktop use case doesn't put the 30" quite that far away. Phone apps on a tablet have the same problem.
> For this to work, the Linux desktop has to be using the Wayland display server (some Linux-based OSes use X11)
MOST Linux-based OSes *still* use XOrg, and Wayland is still considered beta quality software that lacks support for remote access. FAIL.
https://en.wikipedia.org/wiki/...
.
== WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
Hm.. so hard to guess. Lets try something outlandish. How about because there are usefull apps on android? But, really, why do you have to ask?