Motorola DROID X source code released

mobile

Yay, open source! Anyone interested in the DROID X source code? If you are, the files are posted on Motorola’s developer site. The code weighs in at a hefty 280 MB and was actually released several days ago on July 28th. If you’re ready to get down and dirty with lines and lines of code, let the custom ROM creation begin!

[Via Droid-Life]

Read

22 Comments
  • chris

    What a coincidence!Same day as Sammy released the source codes for the Galaxy S lines.

    • chris

      “line” i meant.

      • http://www.Teh-Nook.com Deya

        You mean, 2 days BEFORE Samsung? It was released the 28th, not the 30th.

      • chris

        I stand corrected.My mistake,

  • grrr

    We would already have froyo if it weren’t for that damn locked bootloader.

    • WalterSobchak

      And those damn meddlin’ kids!

  • PAPINYC

    Big Red won’t be happy about that; they preach, “Droid Does” but, they quietly practice “Droid Doesn’t”.

    And, EVO gets FROYO Tuesday…….!!!@@@

  • blakerboy

    What’s the point of custom ROMS if the bootloader is locked? Doesn’t that pretty much eliminate the possibility of flashing unsigned, unofficial zips?

    • Steven

      Yeah, how the hell did BGR miss this plain-as-day fact?

  • http://halo3.com p.mcgee

    i hOpE My m0m BUyS mE ThIs F0n3 sO i CaN USe tHe SoUrcE COd3 w00t w00t

  • Swagger

    Can’t wait for 2.2 on my EVO. Don’t worry X-Men,you’ll get some froyo love soon.

    Now that the EVO is getting 2.2, BGR definitely will not do a review. They couldn’t dare say any phone that isn’t on Red or Blue is the shit. Holla!

  • G

    DROID SUCKS

  • Perspective

    If you care about this at all, and you’re not a professional or aspiring developer, step away from the computer, and get a date.

    • Haha

      Good one.

  • AT

    LOCKED BOOTLOADER

  • mikestorm

    With all the bootloader hate, clearly I misread the article. I THOUGHT it read “source code released to DEVELOPERS” but it must have read “consumers”. Otherwise, people would be griping about not being able to use something that wasn’t intended for them in the first place which, well, does not compute.

  • PAPINYC

    @Swagger

    Holla! [EVO] :)

  • Mark Hernandez

    Oversimplification is the cause of all misunderstanding.

    Was ALL the source code for EVERYTHING for the Droid X released?

    Please tell us some more informative facts, like?

    What parts of the source code were released?

    What can people actually affect if they were to work with what was actually released?

    What parts of the source code for the finished object were NOT released? What roadblocks might that impose?

    What effective value is there in releasing the source code to developers? Give us a for instance.

    Until the real-live practical value of such an action is made clear, it’s a meaningless action, wouldn’t you say?

  • Nathan Snyder

    Alright, the way I’m going to look at it, there must be some code that the eFuse is looking for on boot. Since they are planning to update to Froyo, it can’t be looking for the EXACT ROM that is installed on the Droid X. It must be looking for a specific line of code or something to verify that it’s legitimate. If developers can determine which line it is, then they should be able to create custom ROMs. I think the first thing is to just make some slight variations to the ROM and then try to flash it to see if it bricks or not.

    Any other thoughts?

  • metsfaninct

    Now if someone could fix the wifi. I am on day three with the droid x and the wireless keeps dropping and doesn’t come back till i reset. My network is N with wpa2 aes and i refuse to dumb down my security for a new phone.

    • Brab

      In another review I read for the X, they said they had problems with wireless N networks. If there’s a way you can make it use the g band then it should work fine.

      I can’t help you with that though. Just relaying information hahaha.

  • http://twitter.com/strifejester Justin Ellenbecker

    Old topic but people you need to realize the bootloader affects the kernel not roms

blog comments powered by Disqus