Stories
Slash Boxes
Comments
Search

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Android's "Non-Fragmentation Agreement"

Posted by Zonk on Tue Nov 13, 2007 10:03 AM
from the i-hate-it-when-my-agreements-fragment dept.
Businesses Google The Internet Cellphones Communications Programming IT Technology
superglaze writes "The biggest doubt cast over Android (whose SDK was released yesterday) has been the fact that much of it is licensed under Apache. There have been worries that manufacturers might fork the code road in a non-interoperable kind of way. I.e., they would have no obligation to feed back code to the wider Open Handset Alliance, or even tell the other members what alterations have been made. However, it turns out that Google made all the members sign a 'non-fragmentation agreement' to make sure everything works with everything. In theory at least. 'All of the partners have signed a non-fragmentation agreement saying they won't modify [the code] in non-compatible ways ... That is not to say that a company that is not part of the OHA could not do so.' Google's spokesperson highlighted the historical dangers of working with Java, the programming language that lies at the heart of Android. 'One of the current problems with mobile Java development is that Java has fragmented ... Java virtual machines have fragmented, but all the members of the OHA have agreed to use one virtual machine that can run script in Java'"
+ -
story

Related Stories

[+] Google's Android Cellphone SDK Released 283 comments
AchiIIe writes "The android SDK has been released to the wild. As expected it features the Linux Kernel, low level libraries such as FreeType, OpenGL, SQL Lite, WebKit (as a web browser), a custom Java Bytecode interpreter that is highly specialized for the CPU. A common java API is provided. A video has been posted with an the overview of the API." SM: Several readers have also written to mention the Android Developer Challenge offering $10 million in prizes for cool mobile apps.
Submission: Android's "non-fragmentation agreement" by superglaze (1112971)
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Android's "Non-Fragmentation Agreement" 50 Comments More /

 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • How is this google vs apache? I don't understand (its early and I'm feeling fuzzy headed so forgive me). Google is using an apache license to release this... other than that I don't see asf involvement in the project. Maybe I'm missing something here? This article talks about all the involved parties signing an additional agreement separate from the license agreeing not do what MS did to Java before being sued.

    So... how is this google vs apache?
    • I'm not sure how exactly it is Google vs Apache, too, but the Apache License is not the only way ASF is involved in this story: Google's custom Java VM, named Dalvik, is heavily based upon Apache Harmony.
  • I took a look at the SDK yesterday and some of the videos - having done windows mobile development it looks like it will be almost as easy and have a number of similar features.

    My concern with all of this though - is that there is no hardware available.

    One of the things about emulators is that they run really fast, much faster than the actual hardware runs - so it's hard to tell how responsive an application will be. So given that google has been plowing ahead on development but not been testing on real har
    • You have a valid point, however Google /have/ been running Android on mobile handsets. You can see videos of them in action on the main site.

    • Perhaps they want to avoid symbians mistake? (Score:4, Interesting)

      by SmallFurryCreature (593017) on Tuesday November 13 2007, @10:54AM (#21336673) Journal

      Symbian was developed on hardware, on the lowest hardware then available so that it would be sure to run on everything. This made the design obsolete at launch and now it is so archaic(?) that people really resent that original decesion.

      Perhaps Google wants to avoid this. Wants apps that push the hardware requirements so that the Android phones will HAVE to be powerhouses, and it doesn't get trapped in the symbian or even MS trap of having to work on the cheapest shit some company can throw together.

      Apparently (I only have this from hearsay) symbian phones often miss basic hardware capabilties that drive a pc programmer up the wall because he suddenly has to code for features that have been present in PC's from the dawn of computing.

      All google now has to do, is convince mobile phone makers that it is in their best interest to make their phones capable of actually running the software currently being developed.

      Don't forget mobile tech moves fast but is expensive. If the companies could get away with yesterdays tech they would. That ain't good for us consumers, we want them to be pushed so we finally get some fully capable smart phones and not the same crippled yunk they have pushing on us.

      • Re: (Score:3, Insightful)

        by Sancho (17056)

        Perhaps Google wants to avoid this. Wants apps that push the hardware requirements so that the Android phones will HAVE to be powerhouses,
        Gosh, I really hope not. Battery technology just isn't there for powerhouse phones :\
    • "almost as easy" Are you saying that J2me is easier than this? or... are you comparing to a different embedded sdk?
    • Run your emulator in another emulator, maybe two or three levels deep. Emulators, not virtualizers. That should make it run slowly enough for you.

      (I'm sure there's a way to simply slow down the one emulator, but I just had to post the Rube Goldberg solution...)

    • Re: (Score:3, Interesting)

      by babbling (952366)
      There is no "speed that real hardware runs at," since each phone running Android software will be different, just like every PC is different. Think of Android as a PC in your pocket that has mobile phone capabilities.

      I haven't looked at the SDK, but from what I have heard you can configure the emulator a bit to reflect the capabilities of different types of phones.

  • One of the current problems with mobile Java development is that Java has fragmented ... Java virtual machines have fragmented

    Whoa, he-llo? That's a rather interesting (and bold!) statement to be making there. I don't know if Google has noticed, but J2ME phones all run the same code and the same APIs. Issues between phones almost always come down to working around JVM implementation bugs. Which isn't that huge of a deal when you consider that "porting" then becomes a straightforward matter of applying a min

    • Re:Revisionism? (Score:4, Informative)

      by Anonymous Coward on Tuesday November 13 2007, @12:06PM (#21337869)

      but J2ME phones all run the same code and the same APIs. Issues between phones almost always come down to working around JVM implementation bugs
      This is just plain wrong. Once you start looking at graphics, audio, keyboard input, bluetooth, gps, network, photo or video capture or anything beyond very basic apps, you reach the murky world of JSRs, which are bits of java that may or may not be included in a particular j2me installation. If they are included, many of them have lots left up to the implementation to decide, for example MMAPI leaves it up to the implementation whether to support MIDI sound, whether to support playing audio directly from code rather than from a file, whether to support recording, what file formats to support etc. You can't even reliably play audio files across platforms, let alone do interesting things like get at the camera, get video frames etc.

      Nokia phones for example, most will let you grab a single frame from the camera, some won't, but you can't grab multiple video frames without a 1/4 second delay per frame, whereas motorola phones, many will not let you at the camera at all, but those that will, will let you record multiple frames properly, except for a few which will only let you take single frames.

  • Sounds to me like they don't want anyone forking it.

    This is not as bad as Tivo ... or is it?

    Non-fragmentation my you-know-what.

    • Re:Oh, FORK!!! (Score:5, Informative)

      by ajs (35943) <ajs&ajs,com> on Tuesday November 13 2007, @10:31AM (#21336391) Homepage Journal

      Sounds to me like they don't want anyone forking it.
      Read it again. The members can't fork the development. Non-members can. They're just trying to prevent the situation where, 5 years down the line, NTT says "thanks for all the hard work Google, but now that we've achieved brand loyalty, we're going to stop working on our competitor's OS." The idea is to make the cell phone OS a commodity and let cell phone makers focus on higher level features that will work on any phone.

      • Re:Oh, FORK!!! (Score:4, Interesting)

        by tomhudson (43916) <hudson@nOspAM.videotron.ca> on Tuesday November 13 2007, @10:41AM (#21336497) Homepage Journal

        Riiight - but who are these potential non-members? Its not like you can have half you development team be members, and the other half non-members.

        And its not like there's a huge field when it comes to cell phone manufacturers. There's not thousands of different manufacturers, so google starts out with a de facto quasi-monopoly.

        So even if a fork came along that was better, the companies can't use it.

        No wonder Microsoft is afraid google will be the next Microsoft - they're using Microsofts' playbook.

    • Forking - and even just the threat of forking - can be powerful forces for coordination. Reducing the freedom to fork tends to centralize control and reduce the size of the community for a project, while also restricting potential innovation. From Stephen Weber's The Success of Open Source (pp. 169-170):

      Forking, like speciation, is an essential source of variation and ultimately of radical innovation. Too much forking would undermine the open source process in the obvious ways that people worry about a

  • GPL solves these problems (Score:4, Funny)

    by dmoen (88623) on Tuesday November 13 2007, @10:34AM (#21336415) Homepage
    I agree that the use of the Apache licence is the biggest problem with Android.

    If Android had just used the GPL (which prohibits forking), then this problem would have avoided. There are lots of examples to back this up. For example, if Emacs had used the GPL, instead of the Apache licence, the XEmacs fork would never have occurred. And if Gnome and KDE would both switch to using the GPL licence, then the projects would just magically merge into one, and we wouldn't have the duplication of effort and lack of standards that you currently see on the Linux desktop.

    Oh, wait... (consults Google). Never mind.

    • Re: (Score:2, Informative)

      by domatic (1128127)
      What? The GPL does NOT prohibit forking. There are dynamics associated with it that tend to discourage forking but it certainly is not prohibited.
  • ...it is largely because cellphone mfgs are so tightly wedded to telecoms that they have little interest in offering a platform that attracts 3rd party development.

    Open up the network, as Google is proposing, and mfgs have to compete more in terms of coherent feature sets and what 3rd party apps they can attract.
  • Can a kind Slashdotter educate an ignorant soul about the gist of the Apache license? I sincerely would like to know.

  • I don't know about you others, but I seriously think that Android is over hyped. Yes, it's Linux based platform for mobile devices, but so what? There's already Maemo, but you don't see it hyped to death. Yes, the Android can also run Java ME applications, so what? All mobile phones can run Java ME applications...

    And one last thing... there are no devices yet! No nothing! And you know what, there probably won't be even many of them. If you look at the alliance that Google has put together, the only serious

    • Re: (Score:3, Insightful)

      by m2943 (1140797)
      How serious Motorola is about Android when they have just made an serious investment into an Symbian company?

      Motorola is already shipping lots of Linux phones (far more than Symbian), but they have almost no developer community. Android might be the answer to their problems.

      Motorola just bought half of UIQ from Sony-Ericsson

      I think UIQ is a short-term fix for them. I also don't think UIQ is going to make it in the long term. For Symbian, Series 60 is going to be the de facto standard.
  • So long as the person fragmenting the platfrom hasn't used a Java obfuscator then it would be incredibly easy to decompile the bytecode back to Java source.

    • Re: (Score:3, Informative)

      by AKAImBatman (238306)

      it would be incredibly easy to decompile the bytecode back to Java source.

      #1 Who cares? Only young'uns with little experience with how the industry works actually care about someone "stealing" their (incredibly boilerplate, easy to duplicate, hard to integrate into my own project) source code. Did you know that it's easy to "decompile" your HTML, Javascript, Actionscript, PERL, Python, Ruby, Shell scripts, and even Assembler too?

      Oh noes! Do not want!

      #2 The "Java" that runs on the phone isn't Java at all. Ja

  • 'All of the partners have signed a non-fragmentation agreement saying they won't modify [the code] in non-compatible ways

    To me that reads as they could close off the code and fork it into a proprietary monster as long as everything is still 100% compatible with the Google framework (user apps run correctly, etc).

    So you still can't modify the source code on your phone and run the changes. I bet they are still going to lock down the phone software with DRM (Example.. Motorola A1200)

  • "We've built some interesting applications for Android, but the best applications are not here yet, and that's because they're going to be written by developers,"
    It seems that most of Skyne^WGoogle's code has been written by robots so far. WATCH OUT!

    • Re:Java? Fragmented? (Score:5, Funny)

      by jdeisenberg (37914) on Tuesday November 13 2007, @10:19AM (#21336233) Homepage
      I'm going to lose all my karma points, but here goes...

      From this (and other comments in the previous postings about Android), one might get the impression that the people at Google are a bunch of idiots who just didn't do any basic research. Why, if only they had read Slashdot occasionally, they'd know that Java is slow, has 10^6 different versions, is very slow, is inferior to C++, is extremely slow, takes up too much memory, is abominably slow, is a programming language that no real programmer uses any more, and in general is teh sux0rz. <grin/>

      • Re: (Score:2, Insightful)

        by crush (19364)
        Agreed 100% about the unfair commentary that there usually is on Java. But, Google are behaving rather bizarrely by on the one hand warning about the problems of forking and then on the other releasing their own JVM Dalvik instead of using JavaME [infoq.com]. So they're going with Apache's dodgy non-GPL approach and further causing fragmentation of the Java platform right when sun is doing the right thing by releasing a GPL'ed Java and Red Hat and others have stepped up to the plate to integrate the OpenJDK work with

        • Re:Java? Fragmented? (Score:5, Insightful)

          by omeomi (675045) on Tuesday November 13 2007, @10:35AM (#21336437) Homepage
          behaving rather bizarrely by on the one hand warning about the problems of forking and then on the other releasing their own JVM Dalvik instead of using JavaME.

          You've never written a JavaME (J2ME) app, have you? Getting a J2ME application to work properly on all phones is a huge nightmare. Just when you have it working on your phone, and all of your coworkers phones, you try it on your wife's phone, and find that it completely doesn't work. There's plenty of fragmentation just within J2ME, and it's made worse by the fact that it's almost impossible to test an application on every different phone that's out there. If Google can come up with an SDK that makes "write once run anywhere" a reality in the mobile world, I'm all for it.

          • Re:Java? Fragmented? (Score:4, Interesting)

            by crush (19364) on Tuesday November 13 2007, @10:49AM (#21336603)
            That's fine, but you're avoiding the central point: Google are causing further fragmentation and forking within Java at a time when there are significant efforts being made to re-unify and stabilize the platform. Also they've chosen a license which has the potential to allow leachers to benefit from any work anyone does on the distributed code. A pity that they didn't put their efforts into improving J2ME instead.

            • Re: (Score:3, Insightful)

              by rubycodez (864176)
              or we could say you're missing the point, java is so very fragmented already one more little fragment in the broken heap of glass won't make any difference at all. java: write once, run well only in the IDE of the developer.

              • Re:Java? Fragmented? (Score:5, Insightful)

                by dintech (998802) on Tuesday November 13 2007, @11:14AM (#21337017)
                'Write once, run anywhere'. Hmm, I'm a java programmer and have been for 10 years. I know, as every java developer knows and realises, it actually means 'write once, run on the important places'. Meaning something that works on your desktop PC will also work on the Solaris server you intend to deploy it to.

                Mostly people who use 'but I thought you said run ANYWHERE' argument should actually try to think about what that would mean in real terms. For example, should you expect a huge Swing application or something like Weblogic 9 to run on your 8 year old J2ME phone? Be sensible please...

              • Re: (Score:3, Interesting)

                by EmperorKagato (689705)
                There are Java profiles that work across most cellphones. Most of the new phones implement the profiles with ease.

                • Re:Java? Fragmented? (Score:4, Interesting)

                  by forgotten_my_nick (802929) on Tuesday November 13 2007, @11:35AM (#21337349)
                  No idea why you got modded off topic. You are correct. Normal J2ME commands will work across all phones. It is when you get into graphics or messing with screen resolution that you have to be aware of different devices. That is why you can get emulators for different screen/phones and test.
                  • That is why you can get emulators for different screen/phones and test.

                    The emulators I've found don't adequately emulate the various limitations of these phones. You're probably right that basic J2ME commands will work across most phones, but writing games, for instance, can be a huge headache.

                  • Re:Java? Fragmented? (Score:5, Interesting)

                    by crush (19364) on Tuesday November 13 2007, @12:27PM (#21338221)
                    Whoever modded him offtopic was either being childish or desperate to hide the information. Probably just a fanboy.

                    Reading further on this, the interesting thing about Dalvik is that it's a non-Sun-controlled JVM. The thing about JavaME (aka PhoneME) is that although it (like JavaSE and JavaEE (Glassfish)) is released under GPLv2 [linuxdevices.com], there is no exception clause [java.net] (there is for JavaSE). This means that you can only run GPLv2 code on PhoneME. Obviously Google and it's partners didn't like this, so they wrote their own JVM. In order to avoid infringing on Sun's IP they've made the bytecode unique to Dalvik. So Java goes in ---> Dalvik bytecode comes out, runs on Dalvik. Very clever.
            • A pity that they didn't put their efforts into improving J2ME instead.

              Improving J2ME would mean updating he basic standards of what it takes to be considered a J2ME phone. Right now, the standards are so out of date as to be completely useless, so you end up writing for what you think will work on most current phones, and then testing to find out...available emulators don't adequately emulate phone limitations, and not all manufacturers publish all of the relevant implementation specifications, so testing

              • Re: (Score:2, Interesting)

                by crush (19364)
                As I've said before, I think you're missing the point. And having read a bit more about Dalvik I think that Google needed their own fragmented platform because the GPLv2 (sans-exception) license of JavaME/PhoneME meant that if they want to encourage partners to write proprietary, non-Free code then they had to get their own JVM. See my post here [slashdot.org] for more information. This is a license war. It has fuck all to do with technical excellence or the ease-of-development on the platform. The only reason I care i
      • the impression that the people at Google are a bunch of idiots who just didn't do any basic research

        They did do research, which is why they replaced most of the Sun bloat with native C libraries.

        they'd know that Java is slow, has 10^6 different versions

        They know that; it's one of the reasons they created Android in the first place.

        Java is slow

        They know that, too, which is why only the high-level apps are written in Java and why they replaced the JVM with Dalvik.

    • Re: (Score:3, Insightful)

      by gEvil (beta) (945888)
      Isn't the scenario above EXACTLY what this non-fragmentation agreement should help to avoid? Seems like a reasonable way to ensure device compatibility to me. If a non-OHA entity fragments the code, that's fine, because their code/app/SDK/whatever isn't guaranteed to run on all of the devices anyway. If some hobbyists want to create their own derivative platform for device X, they're perfectly free to do so. Seems like all of the benefits of the open source model to me.
    • to develop in non-java. Of course, it may not work on ALL handsets (in fact, all but certain that it will not). But if you do the work in Java, AND use their API, it is being guaranteed to work across all of the handsets. So, what is your gripe?

    • I'll stick to a basic phone, and follow the *NIX philosophy, "just does one thing, and do it well", thank you very much.

      You have perfectly described Apple philosophy, not *NIX. *NIX is more like "do as many things as you want to do". The fact that Apple uses *nix to a large extent, and has put it on a phone, while at the same time some of these same tools help run huge render farms, workstations on different architectures, datacenters, embedded devices, routers, etc.. ad nauseam -- just goes to show the versatility of *NIX.

    • Re:Google versus Apache (Score:4, Insightful)

      by kevin_conaway (585204) on Tuesday November 13 2007, @10:24AM (#21336291) Homepage

      In a strange kind of way, this is Google versus Apache. Or, commercial versus non-commercial. I know that this is a ridiculous simplification but it kind of smells that way to me.

      How exactly? I don't see it that way

      Google releases all their open source under the Apache license. I'm sure they have various reasons for choosing the Apache license, but I'd wager a major one is that it is very business friendly. They most likely understand what a pain it can be to include OSS products that are licensed under a different licensing scheme in a commercial product.

    • In a strange kind of way, this is Google versus Apache.

      I really don't think it is. This is Google taking the Apache license and then fixing a major perceived weakness in it, at least within the context of their application (creating a single, uniform, mobile platform). And even then, they're not really restricting the software; they're just getting the people who are part of their trade group to agree not to stab each other in the back.

      It's not Google "versus" anything or anyone, except perhaps maybe the closed-source phone manufacturers. Certainly not Apache.
      • Well, if the licensing of the SDK is anything to go by [livejournal.com] it seems more like it's a case of Google vs. Free Software.

        • Re: (Score:3, Insightful)

          by Kadin2048 (468275) *

          Well, if the licensing of the SDK is anything to go by [livejournal.com] it seems more like it's a case of Google vs. Free Software.

          Well, we always knew that there were going to be parts of the software stack that aren't going to be Free software. The FCC won't allow the parts that control the radio, for example, to be user-modifiable. So there have to be some big locked-down chunks, just because it's a cellphone.

          If Google actually said that the "full stack" would be OSS, then shame on them. But it seems like they're going to be way more open than anyone else, and possibly as open as they can be while still getting FCC approval for the

          • Re: (Score:3, Informative)

            by Danny Rathjens (8471)

            But it seems like they're going to be way more open than anyone else, and possibly as open as they can be while still getting FCC approval for the device.

            How can you possibly say that when http://openmoko.org/ [openmoko.org] exists?
            And I don't think openmoko had any problems with FCC approval and are truly open. "free software" is not all that relevant the type of "locked-down chunks" you are talking about - like 911 location service - since they are "locked down" in the hardware chips (by simply not having certain things controllable via serial interface) and not by any software.

    • So why do people keep adopting it.

            For the same reason people keep voting for the same old corrupt politicians?
    • I could go into all the reasons you're shortsighted, wrong, and really a fanboy -- is sucking up to Linus so much better than sucking up to RMS?

      But I have a bigger question. What the fuck does the GPLv3 have to do with Android?

      Someone slap this tool with -1 offtopic, please.
    • There are two stages to the competition with the prize money split evenly between them. Details for the second stage will be released later.

All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2009 Geeknet, Inc.