Announcement

Collapse
No announcement yet.

Ubuntu Touch/Tablet Is Using SurfaceFlinger

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #51
    I don't think Canonical is doing a good choice using Android components for its Ubuntu tablet/phone. The problem with android is that it is developed behind closed doors and every now and then the code is dropped. Google will always have a technological advantage, Canonical will be left out of the development, and google will have the power to just kick Canonical out of the market, since Canonical has not the man power to fork android components and develop them. I hope this is not their long term plan.

    But even in the short term plan, why not choosing something like mer? Plasma active is going to be shipped on the vivaldi tabled and it will be based on mer! I really don't understand this choice.... in any case I hope we will have yet another alternative to the standard android OS..... I really don't like it

    Comment


    • #52
      1. Canonical isn't using Android. It's using the kernel of the phones that come with Android which are supplied by the vendor.
      2. They'd need the same drivers/kernel on their phone anyway.
      3. Have you looked at Plasma Active? It's complete crap with miniscule controls on a touch interface. Designed by idiots.

      Comment


      • #53
        The driver problem should be a non-issue.

        As long as their display server is using egl, the drivers should work.
        FFOS looks to be using their own display server.

        Comment


        • #54
          Originally posted by blackout23 View Post
          3. Have you looked at Plasma Active? It's complete crap with miniscule controls on a touch interface. Designed by idiots.
          Its written in QML....fixing that is literally 10seconds of work. And seriously, "designed by idiots" ? Every decision KDE made since 4.0 has been either the right one, or the case of "Right idea, bad implementation." In which case of the second one they've always gone back and fixed the implementation. (4.10 fixed Nepomuk, and 4.10.1 will fix the fix >_> since someone made a last-second commit to save memory that ended up being buggy)

          Comment


          • #55
            Originally posted by e8hffff View Post
            The problem is Linux was getting no where on mobile device due to the lack of driver support. <SNIP>
            So that's what libhybris* was/is for, disappointing that they didn't go (roughly) the same route as Sailfish, with something that's more closely related to a full Linux/FOSS stack for mobile.
            Seems like they've chosen the cowards path, I'm rooting for Jolla/Sailfish even more now. I still wish Ubuntu well, but it's moved considerably down my interest list.

            Originally posted by blackout23 View Post
            1. Canonical isn't using Android. It's using the kernel of the phones that come with Android which are supplied by the vendor.
            It's more than just that, you make it sound like it's only that, sounds like you need to read the thread again.


            *1st devised by one of Jolla's engineers, now has been forked/built-on heaps, even used in this CM-based Ubuntu.
            Last edited by jalyst; 02-24-2013, 12:28 AM.

            Comment


            • #56
              How have they ported X application to their system with SurfaceFlinger?

              I wonder how they have ported X application to their system with SurfaceFlinger. Because normal Ubuntu consists of X applications.

              If they have created an X server ontop of SurfaceFlinger, then I could use it to display my X programs on my phone screen (Android). Is this possible?

              Or Ubuntu supports only a limited set of applications in their Touch distro?

              Comment

              Working...
              X