Slashdot Mirror


Firefox OS Phone on Display at LinuxFest NorthWest (Video)

Jakob Perry organized the first LinuxFest Northwest when he was still a student. He got off to a good start: now LFNW has been running for 14 years, and has retained its flavor as a low-key, friendly conference. Exhibitors from Linux distributions from tiny (CrunchBang) to huge (Red Hat) were on hand for 2013, and enough speakers and topics to fill about 80 different sessions over the two days of the conference. Not all of it's about Linux per se, either: the EFF and FSF were represented, along with a BSD table, and a local astronomy group with a great name. At this year's event I ran into the first Firefox OS phone that I've had a chance to play with in person. Firefox OS integrates Linux by way of the Android kernel, but is otherwise its own beast. Ubuntu and Mozilla contributor Benjamin Kerensa was on hand to talk about what makes it tick, and to give a demo of the all-HTML5 interface.

49 of 96 comments (clear)

  1. When does 2.0 come out? by master_kaos · · Score: 1

    My bet is next month. Got to release new versions of the phones faster than android manufacturers, right?

    1. Re:When does 2.0 come out? by Anonymous Coward · · Score: 1

      2.0?

      They should be at 15.0 by the end of the week.

  2. Re:Layers on layers on layers by kthreadd · · Score: 3, Insightful

    I don't think a phone would be very useful if all it had was the Linux kernel. You would need a userland, and using one as a base that is already established means a lot of people already know how to use and develop for the platform.

  3. Re:Finally, the visual proof by uncle+brad · · Score: 1

    Quite the opposite, Mozilla/Firefox has had to become leaner and meaner to run (acceptably) on these devices.

  4. Fast forward to 7:45 for the actual phone demo by theurge14 · · Score: 4, Informative

    Demo isn't really a demo, he doesn't open up anything or scroll much, just shows off a bunch of icons.

    1. Re:Fast forward to 7:45 for the actual phone demo by dpak1170 · · Score: 1

      Whats the point of a demo without showing the actual phone capability. It was more of a sales call lol.

  5. Re:Layers on layers on layers by Anonymous Coward · · Score: 3, Funny

    Another layer on top of Android on top of Linux.

    Mozilla needs to focus on their core business. The number of Firefox bugs fixed remains lower than the number being reported, and the internals, which date back to the Netscape era, need replacement.

    So, the "layers" here are 1. Kernel. 2. Userland. 3. UI. Which one of these do you consider unnecessary for the purpose?

  6. I hope it will become available in europe by Anonymous Coward · · Score: 1

    A phone that isn't tied to Microsoft or Google or Apple is a GOOD thing.
    Yes maybe the hardware won't be able to compete with the iphone, the galaxy 4 or winphone but on the other hand you sure as hell won't have google/microsoft/apple right up your ass tracking your every move.
    Remember for those companies, the phone is not the product being sold (although you pay a hefty price to buy it), you're the product being sold. So anything that trumps this vicious circle is good.
    I'll give firefox phone a chance, even though I have a galaxy s3.

    1. Re:I hope it will become available in europe by Isaac+Remuant · · Score: 1

      Google doesn't negatively influence Mozilla in any way, though. And Firefox's usage of Google as a default search engine makes them a nice amount of money (Apple has an agreement as well).

      Competing in the mobile market won't suddenly cut funding. Let's not pretend otherwise.

      --
      "Science can amuse and fascinate us all, but it is engineering that changes the world. " - Asimov.
  7. tattoo by thetoadwarrior · · Score: 1

    I don't object to the idea of getting a tattoo but really, a product logo? That's going to look really dumb in 10 years when he's tired of ubuntu, they go under or change their logo.

    1. Re:tattoo by Isaac+Remuant · · Score: 1

      What about the nostalgia factor? The original logo, etc.

      I wouldn't tatoo myself ANYTHING but I don't see how that is bad...

      --
      "Science can amuse and fascinate us all, but it is engineering that changes the world. " - Asimov.
    2. Re:tattoo by thetoadwarrior · · Score: 1

      True, it's probably not an issue if you live in your mom's basement.

    3. Re:tattoo by ci13urn · · Score: 1

      Obviously you don't know what tattooing is about for some people. Many people are not doing it for fashion, but as a merit badge or mile marker in life. Ben has contributed a lot of his time and energy to the Ubuntu community in Portland, OR; organizing parties to package installers for version releases as well as bug hunting events, which I am sure he doesn't get paid to do. So that tattoo is much more than a logo to him... in 10 years he'll look at that tattoo and think, that was awesome.

    4. Re:tattoo by thetoadwarrior · · Score: 1

      i'm not saying he doesn't have a good reason to think that's a good idea but really, turning yourself into a billboard is a bit silly. I suspect the people defending him would feel different if he was a Jersey shore jock with a Louie Vuitton tattoo but it's pretty much the same thing.

    5. Re:tattoo by ci13urn · · Score: 1

      Ha! Maybe if he worked/lived Louie Vuitton...

  8. Re:Introducing the new Slashdot Phone! by Dan93 · · Score: 1

    Damn, nothing about 3D printers, Arduinos or Raspberry Pi?

    They've gotta save SOMETHING for the Slashdor Phone 2

  9. Re:Introducing the new Slashdot Phone! by tech.kyle · · Score: 1

    If I'm not mistaken, the PostgreSQL booth was running some demos on a RasPi and donated 8 of them to the second-day raffle. I bought $10 worth of tickets, but didn't win any.

    --
    If we colonize Mars, it won't be the World Wide Web anymore. UWW?
  10. Re:Finally, the visual proof by aristotle-dude · · Score: 1

    Quite the opposite, Mozilla/Firefox has had to become leaner and meaner to run (acceptably) on these devices.

    *WHOOSH*

    The key is in the title of the comment.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  11. Actually ran pretty slick by tech.kyle · · Score: 5, Informative

    I got to play with it there. I didn't know I was holding something newsworthy. As a Galaxy S3 (with CM10.1) user, I thought it ran very well considering it was on what appeared to be some older mid-range hardware. Everything seemed quite smooth and snappy.

    --
    If we colonize Mars, it won't be the World Wide Web anymore. UWW?
    1. Re:Actually ran pretty slick by Lennie · · Score: 1, Interesting

      That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).

      It has been shown that FirefoxOS can use less resources than Android that way.

      Which is good because their target market is not the first world countries, but countries like Brazil, Mexico, Poland, Spain. Where smartphones are not as widespread (in Spain and Poland it might be certain parts of the country or markets), mostly because of the price of the phone itself. Prices may drop, but especially parts like touchscreens are very expensive and will probably remain that way.

      Because this is a new market for smartphones, FirefoxOS actually has a chance of getting a proper share of the market in those countries.

      FirefoxOS might be a little less flashy than the first-world competitors, but they pretty much have no marketshare in those countries anyway. And will probably not have much of a marketshare any time soon.

      --
      New things are always on the horizon
    2. Re:Actually ran pretty slick by exomondo · · Score: 1

      That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).

      What extra layers?

    3. Re:Actually ran pretty slick by roca · · Score: 1

      Android's entire Java stack --- Dalvik, SurfaceFlinger, stuff like that.

    4. Re:Actually ran pretty slick by exomondo · · Score: 1

      That doesn't really save you much, given that you can write with the NDK or write web apps you can mostly avoid Dalvik if you want to anyway, but it's still there if you need/want it, limiting to html apps seems pretty silly outside of targeting the extreme low end of devices.

    5. Re:Actually ran pretty slick by Anonymous Coward · · Score: 1

      Spain not a first world country? Are you serious?

    6. Re:Actually ran pretty slick by kllrnohj · · Score: 1

      That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).

      FirefoxOS runs *on top of* Android, it *adds* layers, not removes them. And the very few "layers" that are actually removed (dalvik) are replaced with *slower* layers (JavaScript)

      It has been shown that FirefoxOS can use less resources than Android that way.

      No it hasn't. And if FirefoxOS with the insanely inefficient and not in the same universe as lightweight HTML5/CSS/JavaScript can use fewer resources than a lightened Java runtime with a specialized rendering pipeline I will be shocked. If that happens either Google is incompetent or Mozilla employs actual wizards.

      Seriously people, stop with the "lightweight HTML5" bullshit. HTML is the heaviest, slowest layout & rendering pipeline that exists in widespread usage bar none. Slowest devices (smartphones) + slowest layout & rendering technology ("web technology") != fast, lightweight device.

    7. Re:Actually ran pretty slick by kllrnohj · · Score: 1

      Android's entire Java stack --- Dalvik, SurfaceFlinger, stuff like that.

      SurfaceFlinger is still there, it's why you can see shit on the screen at all. You can't remove that layer. You can *replace* it, but you can't remove it. And good luck finding a replacement for SurfaceFlinger that is lighter and faster than SurfaceFlinger.

      And no browser runs on top of dalvik anyway (browser UIs might run on top of dalvik, but the engine itself does not), so removing that doesn't get you anything.

    8. Re:Actually ran pretty slick by caspy7 · · Score: 1

      That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).

      FirefoxOS runs *on top of* Android, it *adds* layers, not removes them. And the very few "layers" that are actually removed (dalvik) are replaced with *slower* layers (JavaScript)

      Why are you correcting him when he was right? Did you bother to look it up? FxOS is running on a Linux kernel the same as Android. It is not running on top of Android. You said that it does not remove layers and then immediately cited a layer that was removed.
      Here is an overview of the Android architecture, can you tell me which layers *didn't* get removed? (I'll give you a hint, there's only one)
      http://en.wikipedia.org/wiki/File:Android-System-Architecture.svg

    9. Re:Actually ran pretty slick by kllrnohj · · Score: 1

      Why are you correcting him when he was right? Did you bother to look it up? FxOS is running on a Linux kernel the same as Android. It is not running on top of Android. You said that it does not remove layers and then immediately cited a layer that was removed.
      Here is an overview of the Android architecture, can you tell me which layers *didn't* get removed? (I'll give you a hint, there's only one)
      http://en.wikipedia.org/wiki/File:Android-System-Architecture.svg

      I'm correcting him because he is wrong, just like you are. FxOS runs on top of Android's userspace. It literally boots Android, then launches Firefox. This is not a "both run on the Linux kernel" thing, especially since FxOS doesn't run directly on the kernel to begin with. No, FxOS is instead just a native Android application, compiled against Android's userspace.

    10. Re:Actually ran pretty slick by exomondo · · Score: 1

      No, FxOS is instead just a native Android application, compiled against Android's userspace.

      I thought it had it's own userspace running on the Android kernel with Android drivers, or are you saying that Gonk wraps up the entire Android system with Gecko and Gaia sitting on top of that?

    11. Re:Actually ran pretty slick by kllrnohj · · Score: 1

      The entire "Gonk" layer is actually just Android. Complete with all the typical Android services - SurfaceFlinger, InputFlinger, AudioFlinger, etc...

    12. Re:Actually ran pretty slick by kllrnohj · · Score: 1

      Gonk is Android in a literal sense. When you build FxOS the first step is actually downloading and building AOSP, as that's the "gonk" layer. It uses repo and lunch and the rest of the Android build chain as well.

      Here's the manifest file for the FxOS emulator build: https://github.com/mozilla-b2g/b2g-manifest/blob/master/emulator.xml

      You can see plain as day it's pulling in a huge amount of Android code, including the framework.

      Not that this is a bad thing, this is the point of open source. Just that the claims that FxOS is somehow lighter than Android is horseshit, because it sits on top of Android.

    13. Re:Actually ran pretty slick by Lennie · · Score: 1

      Yes, that is the great advantage of FirefoxOS, even if the project fails, we'll have a lot more standards at W3C which allow HTML5-apps to do all kinds of things HTML5 wasn't able to do before.

      --
      New things are always on the horizon
  12. Re:Introducing the new Slashdot Phone! by tech.kyle · · Score: 1

    Update, it was the "Seattle Postgres Users Group" booth.

    --
    If we colonize Mars, it won't be the World Wide Web anymore. UWW?
  13. Re:Layers on layers on layers by Lennie · · Score: 3, Informative

    There is no Android in FirefoxOS.

    They do support running on the same Linux kernel though, so they can make use of the same drivers that were already developed for devices that can run Android.

    Actually, it has been shown FirefoxOS can run on less powerful devices than Android can.

    --
    New things are always on the horizon
  14. Re:Layers on layers on layers by exomondo · · Score: 1

    What's the point of it though? Why not run it like Facebook Home on top of Android and utilise the Firefox browser? At least that's as easy for users to install as any app and underneath is completely compatible with all existing Android functionality. I see no reason this would end up any different than Tizen or webOS or any of those abandoned mobile OSes. So the question is why would somebody choose this over an Android phone?

  15. Tracking? by IMightB · · Score: 1

    Is it going to spy on/track everything you do and report back to it's corporate overlords like iOS and android?

    1. Re:Tracking? by caspy7 · · Score: 4, Informative

      From what I've seen (the non-profit) Mozilla is probably one of the most trustworthy organizations on the net. Protecting users is a part of their mission and they've historically gone out of their way to make sure user info is protected and is not monetized.
      As an example, Firefox Sync (which is actually open & could be implemented on any device or browser) encrypts bookmarks and passwords with extremely high encryption on your device before sending it to the server. The key is only stored on your device such that even if a governing body forced Mozilla to give up your data they still could not decrypt it.
      Recently they've become very unpopular in some circles (ok, just one primarily) by choosing to block third-party cookies from sites you've never visited. This prevents tracking cookies from ad companies (following you and your activities around the net).

      So as far as phone makers, I'd put them at the bottom of the list of folks I'm concerned about tracking me.

    2. Re:Tracking? by Isaac+Remuant · · Score: 1

      does Firefox do that? Do you know what Mozilla stands for? Research that and you'll have your answer.

      --
      "Science can amuse and fascinate us all, but it is engineering that changes the world. " - Asimov.
    3. Re:Tracking? by PuZZleDucK · · Score: 1

      Short answer: "No!"

      Long answer: "You do know what Firefox is right?"

      --
      Can a person program a new solution to a problem? Why should anyone be able to stop such a thing? -Richard Stallman
    4. Re:Tracking? by dzfoo · · Score: 1

      Yet, they were vehemently opposed to Microsoft's strategy of blocking third-party cookies by default, and wrote some sort of manifesto on how "user choice" meant letting advertisers fleece those naive enough to not know how to change the default.

              dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    5. Re:Tracking? by dzfoo · · Score: 1

      The Mozilla Foundation is desperately looking for new ways of acquiring revenue that does not depend on large grants by fickle corporations. Especially when their core competency is being made largely irrelevant by those grantors. Guess the fastest, most common--and apparently very easy to justify morally--way to monetize user access on the Web?

      Come on, guess...

      --
      Carol vs. Ghost
      ...Can you save Christmas?
  16. Re:Layers on layers on layers by roca · · Score: 2

    The reason not to run the Android user-space is footprint. If you use Android apps and a browser, you have two parallel platform stacks --- rendering, compositing, VM, networking, UI, etc both running on a phone at the same time. Getting rid of the Android Java stuff means you can use the Web and local HTML5-based apps at the same time with only one stack. Saves a lot of memory and simplifies the software design considerably.

  17. Re:Layers on layers on layers by exomondo · · Score: 1

    If you use Android apps and a browser, you have two parallel platform stacks --- rendering, compositing, VM, networking, UI, etc both running on a phone at the same time. Getting rid of the Android Java stuff means you can use the Web and local HTML5-based apps at the same time with only one stack. Saves a lot of memory and simplifies the software design considerably.

    All that does is limit you to html apps, which is what webOS was trying to do, on Android in the end Google made the NDK available because they realized that the abstracted environment wasn't flexible enough but you can still run HTML apps. Even the first iteration of iOS was supposed to be based around web apps and that idea was abandoned, but you can still run HTML apps. So given that HTML apps can already run on any modern smartphone I still fail to see what the appeal of Firefox OS is supposed to be unless it's about just targeting the really low end.

  18. Hope it fails by readingaccount · · Score: 1

    The last thing we need is another mobile operating system. We already have iOS, Android and Windows Mobile, and it's hard enough to get cross-platform support for apps at times, much less having a fourth or fifth entry in the market.

    Nothing against the Firefox folks, but just as in Linux, there are problems with having too much choice.

    1. Re:Hope it fails by readingaccount · · Score: 1

      Do you really need to use profanity to make your point, coward?

    2. Re:Hope it fails by readingaccount · · Score: 1

      Precisely! I'm glad someone understands my position.

      I know you're being sarcastic but yes, choice is bad (see the infamous TED video about the illusion of choice). Diluting things over too many options makes things more complicated for users. Better to have a small handful of strong options which are still having to compete with other, making the whole set stronger over time. New concepts can always be introduced within that small set of options.

  19. I wonder by ThatsNotPudding · · Score: 1

    I wonder if FirefoxOS can look up the definition of Balkanization.


    /runs away

  20. Re:Layers on layers on layers by exomondo · · Score: 1

    It is about targeting the low end, but then again don't underestimate what you can do with emscripten and asm.js.

    That's a great argument for javascript and webgl - which we already have on Android and iOS - but still doesn't suggest why Firefox OS is a good idea for anybody.

  21. Re:Layers on layers on layers by Lennie · · Score: 1

    When you get rid of everything else on the phone, but just the browser. You use less resources to view the same pages.

    It's that simple.

    --
    New things are always on the horizon