Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Verizon Joins Linux Mobile Foundation

Posted by Soulskill on Fri May 16, 2008 07:22 AM
from the progress-is-progress dept.
An anonymous reader brings news that Verizon Wireless has announced plans to use a Linux-based software platform for phones on its network. Verizon is the first US mobile carrier to join the Linux Mobile Foundation, the goal of which is to "collaboratively develop a comprehensive Linux-based mobile software stack that can be modified easily and used at no cost on a wide range of hardware devices." Many had expected Verizon to go with Android, but according to the Register, Verizon feels Android "isn't as open as it would prefer." Continuing: "Yes, Google bills Android as open. And, yes, it's backed by the Open Handset Alliance, another industry consortium calling for the open development of mobile apps. But [Verizon spokesman Jeffrey] Nelson argues that at this point, Google is calling the shots. 'Google said "Here's the plan. Sign on the dotted line if you support." It may end up being collaborative. It may end up being collegial. But it need not be.' He actually has a point. But maybe Verizon just wants more control over the situation. It should be noted that the company made sure it has a place on the LiMo board. In any event, Verizon says that customers will be free to attach any device and any application to its network by the end of the year - provided those devices and applications met certain minimum specifications. So, in theory, you'll have free rein to attach an Android phone even if you don't buy it from Verizon."
+ -
story

Related Stories

[+] Mobile: Verizon Embraces Google's Android 148 comments
An anonymous reader writes "BusinessWeek has up an article on Verizon's decision to fully support Android. After passing on the iPhone, the company says they're going to open their network to more devices, move their network to GSM-based radio technology (LTE), and now support Android. 'In an open-access model, though, Verizon Wireless won't offer the same level of customer service as it does for the roughly 50 phone models featured in its handset lineup. Though the company will insist on testing all phones developed to run on its network in the open-access program, Verizon plans only to ensure the wireless connection is working for customers who buy those devices.'"
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.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Verizon feels Android "isn't as open as it would prefer."
    Translation: Google won't let use lock Android phones down, so we made sure we had a place on the LiMo board to ensure that we can continue to control everything the way we've always done.

    • More translations:

      provided those devices and applications met certain minimum specifications
      Minimum specifications: we can lock the device down.
      • Re: (Score:3, Insightful)

        It's all bad with VZW locking down their phones. By not letting every single phone have every single feature, people actually have to pick and choose phones based on how easy they are to hack to get the phone working with what they want.

        By hanging onto the theory that people buy ringtones for $4.99 because there is no easy way to copy over the MP3 files because you disabled bluetooth OBEX... That's just crazy talk.

        It's about time they were talking about openness. They've been a closed book for too many year
        • Re: (Score:2, Informative)

          because they'll find a way to text for less than what they're paying now.
            • Re: (Score:3, Insightful)

              I couldn't disagree more. These are American consumers we're talking about here. They care more about what color their phone is than how much more they get screwed as compared to cell phone customers in any other civilized country.

              I'd say they don't care about something until it costs them money, but here they don't know that there's any other way, since most Americans think other countries are fictional.
                • I would have marked it insightful again if I still had mod points. He may be going a little far, but it's absolutely true that the general public in the US doesn't care enough to do anything about it. How do you think we got into this situation in the first place?
        • The days when you could open a phone and modify it without phear were a lot of fun. A new age of phreaking is upon us!
    • Android may be open source, but the fact that it's based on Linux is more or less irrelevant to the programmer. The native API is Java-based, Android applications run under the JVM, and you can't expect to run anything but Java applications on Android. It's not a "Linux phone", it's a "Java phone" that happens to use Linux in its implementation.
      • yes and no. Remember running Java means you run Java byte code. If you are willing to write a compiler you can turn any language you want in to Java byte code(It might not be nice but it can be done). So the phone should be able to run Python, Ruby, Smalltalk and several others. http://en.wikipedia.org/wiki/JVM_Languages [wikipedia.org]
        • If you are willing to write a compiler you can turn any language you want in to Java byte code

          There's an accumulated 35 years worth of software written in "C" for the UNIX API that includes pretty much all the software that I'm personally interested in running, one way or another.

          Writing a compiler for a subset of C that would make even a fraction of these programs work would probably be a bigger job than creating Android was.
      • by Cyberax (705495) on Friday May 16 2008, @08:30AM (#23432266)
        Wrong.

        You can already easily use native libraries in Android, even though it is officially unsupported. Android has a perfectly good security system which makes it possible.

        In future, it should even be possible to extend the Dalvik VM (its sources are not available right now).
        • Mod parent up. See, for example, this thread [google.com].
        • You can already easily use native libraries in Android, even though it is officially unsupported.

          I can use native libraries in Mono, too... that doesn't mean that the fact that Mono runs on Linux makes a .NET application a Linux application.

          The Android API may well be a better one than the UNIX API for a cellphone, by the way, so I'm not saying that this is necessarily a drawback to Android. What I'm saying is that it doesn't matter all that much to the developer whether the OS below the Android runtime is Linux, Windows CE, Windows PE, whatever the Symbian OS is called this week, Palm OS 5, BeOS, or Amiga.DE.

          The whole "Android is Linux" meme is just muddying the waters... Android isn't using Linux as anything but an implementation tool. Android isn't about Linux. Android is about Android.
          • Not exactly, currently, Android depends on *nix security system. Some features (powersaving, graphics, sound) also require cooperation between Android and the kernel.

            It's not much, of course. But you can also argue that you can run Symbian OS applications on Windows if you care to port its API and binary loader.
            • Not exactly, currently, Android depends on *nix security system. Some features (powersaving, graphics, sound) also require cooperation between Android and the kernel.

              That's interesting when one is considering the quality and details of the implementation, but unless it's exposed through the API in a way that depends on the fact that it's Linux under the hood that doesn't change my point. Android provides an Android environment, not a UNIX one.

              But you can also argue that you can run Symbian OS applications o
      • by tobiasly (524456) on Friday May 16 2008, @09:17AM (#23432932) Homepage

        The native API is Java-based, Android applications run under the JVM, and you can't expect to run anything but Java applications on Android. It's not a "Linux phone", it's a "Java phone" that happens to use Linux in its implementation.

        Partly correct, except it won't use the JVM. It will use a different virtual machine called Dalvik, so that they can get around Sun's ridiculous JME licensing, MIDP profiles [betaversion.org], and everything else that sucks about running midlets on phones today (such as the overzealous security restrictions that keep me from easily running a program I wrote on my own phone.)

        • Re: (Score:3, Insightful)

          That's the nice part about running Java on the phone most people don't seem to get. By having the Java wrapper they only have to secure Java from doing anything wrong not try to secure random code that will be running as compiled. Why Java and not C++ or [insert favorite language here]? Because Java came with a wrapper (the JVM) and it's the biggest language right now(This might just sound like me showing a preference but TIOBE backs me up on this. http://www.tiobe.com/index.php/content/paperinfo/tpci/index [tiobe.com]
      • You have to recompile your Java apps and library to work on Android, since they're using a different Java bytecode. They've also developed a whole new GUI toolkit apparently.

        They do have some performance reason for the change, but it's hard not to suspect some politics.
    • Re: (Score:3, Interesting)

      The anti-Tivoisation is perhaps the most controversial clause of the GPL3, but as embedded Linux becomes more common, perhaps also one of the most important. It will be interesting to see how this sort of thing is affected in the longer term.

      In the short term, they can probably stick with GPL2 software easily enough, if they feel they need to. But if and when a critical mass of FOSS is being released under GPL3, it will be harder to achieve full lockdown of the platform.

      • 1) The Linux kernel itself is and shall probably forever remain GPLv2. At least that's what Linus says, and since he's in charge, well, that's it. GPLv3 code can't be added by third parties (GPLv2 and v3 are incompatible).

        2) I predict a "L/GPLv2 and later" fork of large parts of the GNU project, particularly glibc, fileutils, binutils, etc.

        So, no, I don't think the anti-tivoisation clause will end up stopping Verizon in the near term or long term. Remember: Verizon is on the board of LiMo, so they, at
  • Verizon? (Score:5, Insightful)

    by adpsimpson (956630) on Friday May 16 2008, @07:24AM (#23431646)

    Of course, this will only be of any benefit to the users if they leave the 'modified easily and used at no cost on a wide range of hardware devices' aspect open to the users.

    Judging by the past performance of Verizon, they will do anything possible to lock it down and maximise their profit stream/control over the platform.

    At least it should make the devices more hackable though! :)

    • Yeah, I discovered this week how much Verizon wants you to mess with their phones. Try loading BREW apps on a LG VX9900 (enV) using BitPim sometime.
    • Re:Verizon? (Score:5, Insightful)

      That's why I'm an AT&T customer now.

      I was interested in the XV6800 (an HTC Windows Mobile device), but Verizon was delaying it for months and months after Sprint released the same device for "network certification issues".

      I learned my lesson the hard way what "network certification issues" means from Verizon delaying the Treo 650 by 6-9 months from Sprint release - It means "the phone's software hasn't been crippled to our satisfaction yet".

      So if the phone you want is released on Sprint but Verizon is delaying it for "network certification issues", find another phone or switch providers, because the phone you get from Verizon will NOT have the features and functionality that the Sprint variant has.
  • Hans: Can you hear me now?
    Linus: (pretending it's a bad connection) What?
    Hans: Can you hear me now?
    Linus: What? What?
    Hans: Can you hear me now!!!!???
    Linus: Sorry Hans, I can't hear you. Why don't you "have a talk" with that stupid Verizon guy.
  • will be free to attach any device and any application to its network by the end of the year - provided those devices and applications met certain minimum specifications.
    So finally the US caught up with us....
    • No, the US is merely saying something that makes it *look* like a bastion of freedom and democracy and ice-cream-covered puppy kisses and unicorn farts. In reality, the moment that someone releases a free application for a Verizon phone that enables some cheap and wonderful functionality, the higher-ups at the company will shit themselves in outrage and find a way to make sure that their flag-waving freedom-pimp network is able to triple your charges the next month for having the audacity to use your phone
        • Yeah, my post is a bit wonky in that regard, but if you take a wee glance at the one I'm replying to I think it's a bit obvious why I wrote it the way I did.

          I'll try to be clearer after I've had coffee...
    • IIRC (and the "C" could be faulty), didn't Google recently force the winner of the FCC's recent spectrum auction to abide by an open-access rule that Google (rightly) weaseled into the bidding rules?

      As long as the devices use that chunk of spectrum, Verizon may not have had a choice.

  • Very confusing (Score:5, Interesting)

    by Oxy the moron (770724) on Friday May 16 2008, @07:33AM (#23431702)

    I've been a Verizon customer now for about 5 years. The coverage is excellent here (Indianapolis) and the price is decent, so I've stuck around.

    Really the only complaint I've had with them thus far is that basically every phone they sell is locked down and/or has it's interface completely changed when compared to the original phone, or the same phone sold to another carrier. Additionally, they are very choosy about how you can connect to their data network.

    This "customers will be free to attach any device and any application to its network by the end of the year" seems like a complete 180 to that mindset. The only way I see them pulling that is if some huge charge is added to your data plan to allow it. They already nickel and dime you if you want to tether a phone instead of using their air card.

    It just seems fishy to me.

    • As an employee for VzW I agree to that the phones are horribly locked down. If you know what you are doing though they are easily hackable. I for one am looing forward to the "open" phones. I do believe that with the new software they will be even easier to hack. This is why I have Verizon phones as well. Yeah, I can't txt you a ringtone, but 5min with a cable and a computer and I can open the phone and you can D/L any thing you want to it. LGs are the best, IMO, to mess with(9900)
      • What program do you use, something provided by Verizon or something else? All the ones I have grabbed do not support my model of phone (LG ENV)
        • BitPim [bitpim.org] lists the VX9900 (enV) as supported, but I haven't had enough time lately to really get into trying it out. If you run across something that works better let me know.
      • Except that the LG phones (and several others) have proprietary connectors, require special versions of USB cables, etc. Why can't they all just use a mini-USB connector? It would make the phones much easier to manage and you wouldn't have to go buy a new cable every time you got a new phone.

        • Why can't they all just use a mini-USB connector?

          The answer to this question is right there in your post: "you wouldn't have to go buy a new cable every time you got a new phone."

    • I have the same complaint about the phone. I love the service, I haven't dropped a call yet. I got an excellent deal on my phones when I started my contract, as well.

      Then, when I started playing around with Bluetooth for the first time, I realized how much I couldn't do. My girlfriend and I had the same make and model phones, but we couldn't transfer files between them. In fact, I had to install BitPim (love it) on each computer just so we could transfer wallpapers and ringtones without having to pay for
      • Re:Very confusing (Score:5, Informative)

        by r_jensen11 (598210) on Friday May 16 2008, @10:17AM (#23434070)

        I'd love to see cell phones become like cell phone numbers: you can them whereever you go. Hardware should be carrier independent. It's not like my ISP makes me buy a computer which only works with their network. My TV works with any cable provider. But my cell phone?

        Um, you can, more or less. It's called GSM. You can use any GSM phone that supports 850/1900 with any GSM carrier in the US. Most GSM phones sold in the US are 850/1800/1900, which means that you can even use those in other places like Europe. Just pop out the SIM card, put in a new one that you buy once you get to your destination, and viola, no roaming/international charges.

        This is the sole reason why I'm sticking with T-Mobile. I get a Verizon discount at work, but for the value of the discount, it only brings the phone bill down to what I'm paying with T-Mobile. I'll use the discount on FiOS and a landline, maybe TV as well, but Verizon is staying hella far away from my mobile.

  • by QuantumG (50515) * <qg@biodome.org> on Friday May 16 2008, @07:45AM (#23431782) Homepage Journal
    A friend and I were trying to have a conversation with an old friend via loudspeaker on a Symbian based phone. If you've ever tried this, you know how difficult it is to hear the each other. What's especially annoying is that we had more than one phone on hand, but setting up a three way call is painfully difficult and expensive, but more importantly, it's completely unnecessary. There's no reason why any number of handsets can not be linked via bluetooth and only one make the call to the third party.

    This is one example of the creative ways communications problems can be solved.. but only if you have an open platform.

    • Re: (Score:3, Interesting)

      What's to stop you from implementing this on a Symbian platform?

      The SDK is free and I'm fairly sure you can do that sort of functionality. Of course, you have the SymbianSigned gauntlet to go through, and you will if you want to do that sort of thing, but I would say it's possible.
  • itsatrap (Score:4, Funny)

    by pipatron (966506) <pipatron@gmail.com> on Friday May 16 2008, @08:16AM (#23432100) Homepage
    itsatrap? anyone?
    • itsatrap? anyone?

      Yeah, I've been with Verizon for years and this sounds way too "nice guy" for them. It would be incredible if it was true, and maybe Verizon is feeling the pinch from iPhone subscriptions and the prospect of future Android defectors, but I doubt it. Think Microsoft OOXML vs. ODF: I think its similar.

  • will be free to attach any device and any application to its network by the end of the year - provided those devices and applications met certain minimum specifications.

    For a fee.

    Yep, Verizon built a US$20 million lab to 'certify' products submitted for use on their network, and expects to recoup that investment by charging for their certification services. So unless someone with reasonably deep pockets is gonna back your whatsmawhoseits it won't going on Verizon's network. Compare this to, say, T-Mobile whose policy is pretty much if it takes a SIM plug it in and they'll be happy to bill you for it.

    What is Verizons real goal?

    Getting out of the phone business.

    No carrier likes to be in the phone business - it costs money for all of those stores & racks of phones & inventory management and huge support overhead, not to mention the complex subsidy plans that everyone loathes. So Verizon's plan is to outsource it all to the phone manufacturers. Sure, buy any Verizon 'certified' phone (same as the rest of the world using GSM enjoys) and plug it in. Got a problem?? Call whomever you bought it from, or the manufacturer, just not Verizon.

    It's an easy way for Verizon to expand the offerings on their network, at no risk or cost to Verizon, while shifting the overhead of supporting those phones elsewhere. Verizon will charge for the service, that lovely pricey plan, just now you'll be buying from their list of 'certified' products, not their Verizon-branded phones.

    Expect in a few years to walk into Verizon stores with minimal selection of phones, just enough range to cover the basics for those too out-of-the-loop to buy their phone elsewhere. Or even a sublet strategy where phone manufacturers pay for square footage and supply their own staff to sell their brand phones.

    But innovative homebrew startups etc.? Not on big red it'll be expensively certified products paying for the Verizon privilage thankyouverymuch.

  • ...to replace my Treo 650. I've got a 'two-year upgrade' due, and I like PalmOS, despite its limitations. But a Linux-based phone - assuming it wasn't totally locked-down by Verizon - would be even better. Maybe I'll hold off a while. :->
    • Off-topic, well kind of, but supposedly the next version of PalmOS is going to be based on Linux as well. On another note I have Alltel and I would love a Centro but I am a bit worried about signal and also being able to use the features (web based) I want as Alltel doesn't offer the Centro yet. Does anyone know how compatible the PRLs from a 755p would be for use with a Centro?

    • Re: (Score:3, Informative)

      I think Nokia [nokiausa.com] might sell you one.
      • Re: (Score:3, Informative)

        Nokia has almost no cdmaOne/CDMA2000 phones. They're a GSM/UMTS shop.

        In addition, previously only Sprint had an ESN whitelist that would prevent them from activating phones not sold by them. I have heard that Verizon also does this now in order to prevent feature-superior uncrippled phones from using their network (bypassing the overpriced replacements for the features removed from Verizon's version of said phones - see Treo 650 Bluetooth DUN as an example.)
        • Nokia has almost no cdmaOne/CDMA2000 phones

          Keyword *almost*.

          Oh, you want a *choice*. I see ;)

          I would also imagine that this would change, if there were a sudden market for them. I notice that Nokia CEO claims [infoworld.com] the market isn't viable (for them) and that's the reason - of course that was a couple of years ago, so things are undoubtedly different these days.

          If this move is as it seems, then I guess it will change a lot of things. I guess we'll have to wait and see.

        • Nokia has almost no cdmaOne/CDMA2000 phones. They're a GSM/UMTS shop.

          Then look for Nokia's other countries that use CDMA. I know that Japan uses/used CDMA (don't know if they completely got rid of it now that they're 3G.) Hong Kong uses CDMA as well, and their Nokia site is in both Chinese (I'm guessing Mandarin, but I really have no clue) and English. Just go to http://www.cdg.org/worldwide/index.asp [cdg.org] and check out what other countries use CDMA, and then check out those countries' pages for Nokia or any other large company like SonyEricsson