Announcement

Collapse
No announcement yet.

Google Working On Android Based On Linux 3.8

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

  • Google Working On Android Based On Linux 3.8

    Phoronix: Google Working On Android Based On Linux 3.8

    Google recently opened up a public code repository that contains their experimental work to re-base Android off the recently released Linux 3.8 kernel...

    http://www.phoronix.com/vr.php?view=MTMxMzc

  • #2
    Nice

    Because now Nexus 7 with latest Android 4.2.2 still use old 3.1.10 kernel built on November 29, 2012.

    I hope they already rebase it on more modern Java, because they still use Java 6 which is boring.
    Java 7 is much nicer.

    Comment


    • #3
      Originally posted by uid313 View Post
      Nice

      Because now Nexus 7 with latest Android 4.2.2 still use old 3.1.10 kernel built on November 29, 2012.

      I hope they already rebase it on more modern Java, because they still use Java 6 which is boring.
      Java 7 is much nicer.
      The fact that its 3.1 isn't really related to whether Androids kernel changes are mainlined. Those changes are easy enough to port to any modern kernel version. The real problem is NVIDIA and other ARM makers usually develop against one kernel version and don't update for a year or two.

      Comment


      • #4
        Originally posted by uid313 View Post
        Nice

        Because now Nexus 7 with latest Android 4.2.2 still use old 3.1.10 kernel built on November 29, 2012.

        I hope they already rebase it on more modern Java, because they still use Java 6 which is boring.
        Java 7 is much nicer.
        lol. you are always dissin' java 6.

        i actually found all the new things they've been roping into java has made it a lot more convoluted and uglier. it's like they want to turn it into something unintuitive like PHP or C++.

        jmo of course.

        edit: before you know it they'll be adding "unsigned ints"

        Comment


        • #5
          Originally posted by johnc View Post
          lol. you are always dissin' java 6.

          i actually found all the new things they've been roping into java has made it a lot more convoluted and uglier. it's like they want to turn it into something unintuitive like PHP or C++.

          jmo of course.

          edit: before you know it they'll be adding "unsigned ints"
          I wouldnt call that a bad thing, when you consider it probably adds more power while getting rid of the amateur devs who release crappy apps.

          Comment


          • #6
            fast tracking 3.8 this could mean only one thing....android wants f2fs!

            Comment


            • #7
              sound pretty unlikely they would ship it in Android 5.0, with only 3 months to go before Google I/O, no?

              I think it may be for Android 6.0, and probably because 3.7 and later 3.8 contained 64 bit ARMv8 support, and also the F2FS file systems like others have said.

              Comment


              • #8
                mistakes

                there are lots of mistakes in this article.
                Jelly bean uses the following kernels
                3.0 kernel for Galaxy Nexus
                3.1 kernel for Nexus 7
                3.4 Kernel for Nexus 4 and Nexus 10.

                Comment


                • #9
                  Originally posted by chris200x9 View Post
                  fast tracking 3.8 this could mean only one thing....android wants f2fs!
                  Yeah I'm kind of thinking the unified arm work, and f2fs

                  Comment


                  • #10
                    Originally posted by johnc View Post
                    lol. you are always dissin' java 6.

                    i actually found all the new things they've been roping into java has made it a lot more convoluted and uglier. it's like they want to turn it into something unintuitive like PHP or C++.

                    jmo of course.

                    edit: before you know it they'll be adding "unsigned ints"
                    C++, particularly when combined with Qt is far more intuitive than the utter braindamage that is Java

                    Comment


                    • #11
                      Why don't they just target 3.9?

                      Comment


                      • #12
                        Originally posted by e8hffff View Post
                        Why don't they just target 3.9?
                        Maybe because it isn't ready, and they're working only with stable stuff.

                        Comment


                        • #13
                          Actually I was hoping they would drop their power management patches and they have! If one looks in /kernel/power the only file not in linus's tree is suspend_time.c and that's encouraging. Hopefully this code has been tested and is as power efficient as Android's current code if not more so.

                          PS: It will be interesting to see what google does with F2FS too.

                          Comment


                          • #14
                            Is there an easy overview somewhere with the diff sizes between the Android kernel and Linus' branch with the corresponding version number and how this has evolved over the kernel releases?

                            Also, it would be interesting to see those diffs divided into the different directories/functional units of the kernel sources.

                            In a way that would give an indication of how long they have to go to run on an almost pure mainline kernel.

                            Comment


                            • #15
                              Originally posted by chris200x9 View Post
                              fast tracking 3.8 this could mean only one thing....android wants f2fs!
                              Or that they want to rebase both Android and ChromeOS on 3.8

                              Comment

                              Working...
                              X