Results 1 to 10 of 11

Thread: Wayland On Android Is Continuing To Come Along

Hybrid View

  1. #1
    Join Date
    Jan 2007

    Default Wayland On Android Is Continuing To Come Along

    Phoronix: Wayland On Android Is Continuing To Come Along

    The Wayland port for Google's Android platform is continuing to be hacked on by Collabora. Here's some new details...

  2. #2
    Join Date
    Dec 2011


    Why is it desirable to run Wayland on Android?

  3. #3
    Join Date
    Jan 2009


    Quote Originally Posted by uid313 View Post
    Why is it desirable to run Wayland on Android?
    Run a full linux desktop at an android phone maybe. Like the thing Canonical is trying to achieve. You dock the phone you have an ubuntu desktop, you undock you have an android phone.

  4. #4
    Join Date
    Jan 2011

    Thumbs down Waste Of Time?

    I don't want to be offensive, but isn't this a waste of time?

    Anyone with the skills to port it to Android should be working on getting the the main project up and running first.

    What's the point of Wayland on Android as it's already got a display manager that isn't going to change any time soon.

    Promote proper Linux first and as a secondary then maybe broaden the scope!

  5. #5
    Join Date
    May 2012


    The 2 points I can think off the top of my head are:

    1) Lower the barrier for new Linux mobile OSes to make sure Linux on mobiles strives and to help loosen Google's consolidating Android "monopoly" by eliminating core/sophisticated components from Android which are Google-specific.
    Currently you (only) use the Linux kernel but have to create your own mobile graphics stack ( doesn't cut it) which is a lot of work and usually boils down to a "good enough" boilerplate. Providing a display server (Wayland), and possibly the Weston compositor with plugins, makes it a lot easier to have a 1st class Linux graphics stack based on the mainstream Linux PC stack. The ever increasing power of mobile CPUs and GPUs allows for this, now is the right time to simplify and unify without losing flexibility.

    2) The maintaince for non-Google companies of their own fork/whatever of Android will be easier in case they part ways with Google (e.g. because it acquires Motorola) and try to develop their own Android fork or a new Linux OS not to be dependent on Google at all.
    Last edited by mark45; 06-20-2012 at 11:18 AM.

  6. #6
    Join Date
    Jul 2009


    If you read the presentation, you'll see the explanation of why. A lot of it boils down to the fact that IHVs often only support Android and do not even attempt to support vanilla Linux with the regular GNU userland.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts