• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Droid X Rumor Debunked

This is why the GPL3 was made.

Except Android is licensed under an Apache license which is far more "business friendly" when it comes to customizations. What Motorola has done is 100% compliant with the Android software license.

Not really. Google spends considerable development in Android, Motorola and HTC don't.

You can always tell someone who knows nothing about handheld systems, or even programming in general.

Motorla had to port the Android operating system to their device. They most likely had to optimize and compile it for the specific architecture they chose. Additionally, they had to license and integrate drivers for every single device on the phone (camera, storage, modems, display, sound, touchscreen, etc.). And finally, they had to design the user interface. Every step of the way has to be rigorously tested on both the underlying technical aspects as well as the user interface stuff that you see. The end result is a ROM that is made by Motorola for Motorola devices and has tons of money and time invested in it. Android only provides a framework for the integrator to use, contrary to what all the Android fans think, integrators don't just design their devices, hook up a USB CD drive, insert the Android CD, run a graphical installer, and they're done.

These ROMs are valuable works that probably also have trade secrets about Motorola's hardware in them. It is not legal for you to take Motorola's ROM and stick it on another maker's device, and it's certainly not legal for the other makers to use Motorola's ROM. Motorola has every right to aggressively protect their Android ROM with eFuse.
 
You do realize you can do virtually anything you want even with a boot-ROM locked Android, whereas with the iClone that's not the case, right?

I'm guessing you didn't even bother going into that link.
 
I'm guessing you didn't even bother going into that link.

I didn't click it, no... but I can tell by the URL that it's an article about voiding your warranty for an unsupported (by developers or the manufacturer) OS and not even using the iClone OS at all, thus defeating the point of even having an iClone in the first place.
 
Android 2.2, without waiting for Motorola's update delays. This is a big one - 2.2 is very, very nice.

Future Android updates, without worrying whether Motorola will EOL your phone and cease coding updates for it.

Wi-fi tethering, without paying extra money to Verizon and without the arbitrary (and useless) 2 GB/mo cap.

The potential for further customization beyond what stock Android has to offer.

Being able to get rid of Motoblur. (Even if it is just a collection of widgets at this point.)

FWIW you can eliminate Motoblur just with a root I think... No need for Custom ROM to do that.
 
I didn't click it, no... but I can tell by the URL that it's an article about voiding your warranty for an unsupported (by developers or the manufacturer) OS and not even using the iClone OS at all, thus defeating the point of even having an iClone in the first place.

Defeating a phone's lock mechanism to use custom ROM is also unsupported by Motorola. What's your point? You can restore iPhones just as well as you can restore the Motorola when you need to service them under warranty.

As for the link, it was a site that shows you how to turn your iPhone into an Android phone. So knock it off with the iClone crap.
 
Android 2.2, without waiting for Motorola's update delays. This is a big one - 2.2 is very, very nice.

Future Android updates, without worrying whether Motorola will EOL your phone and cease coding updates for it.

Wi-fi tethering, without paying extra money to Verizon and without the arbitrary (and useless) 2 GB/mo cap.

The potential for further customization beyond what stock Android has to offer.

Being able to get rid of Motoblur. (Even if it is just a collection of widgets at this point.)

Cool. I was pretty pissed I had to pay extra to tether off the phone, how stupid is that :rolleyes:
 
Cool. I was pretty pissed I had to pay extra to tether off the phone, how stupid is that :rolleyes:

He's saying that's what you COULD do if you could custom ROM it.

Being that Motorola encrypted the bootloader though, a custom ROM isn't going to happen.
 
Defeating a phone's lock mechanism to use custom ROM is also unsupported by Motorola. What's your point? You can restore iPhones just as well as you can restore the Motorola when you need to service them under warranty.

As for the link, it was a site that shows you how to turn your iPhone into an Android phone. So knock it off with the iClone crap.

You don't need to use a custom ROM to do what you can't do with an iClone, in any case... a custom ROM is just for a couple of aesthetics or dumping stock features you don't want in most cases (or a new version, early, at times). The iClone is locked down hugely, while the Androids (virtually all of them, but even this Droid X) can be customized a LOT and have anything you want software-wise (not ROM-wise) installed on them.
 
He's saying that's what you COULD do if you could custom ROM it.

Being that Motorola encrypted the bootloader though, a custom ROM isn't going to happen.

PDAnet for the win, in any case...
 
You don't need to use a custom ROM to do what you can't do with an iClone, in any case... a custom ROM is just for a couple of aesthetics or dumping stock features you don't want in most cases (or a new version, early, at times).

Custom ROMs are kindof like reinstalling Windows fresh without Dell crap. You can clean it up yourself just fine, but it's just easier to install it clean without the Dell crap. That's one of the big reasons to Custom ROM.

Other than that little device tweaks (like remapping camera button, etc)...
 
Someone said Motorola and Verizon etc spend a lot of time on building their "experience" on the phones. Why? I'd rather have plain vanilla Android with the speed and better ability to tinker. Plus, not bloatware.
 
Except Android is licensed under an Apache license which is far more "business friendly" when it comes to customizations. What Motorola has done is 100% compliant with the Android software license.

Except not all of it is. This sort of situation is unacceptable because it undermines the whole thing that got Android hype in the first place.

If this becomes standard then the status quo goes right back to normal and people go right back to being told what they can and can not do with hardware that they have purchased. Unacceptable.
 
You don't need to use a custom ROM to do what you can't do with an iClone, in any case... a custom ROM is just for a couple of aesthetics or dumping stock features you don't want in most cases (or a new version, early, at times).

And most importantly, having updates once the manufacturer stops doing them. Which in case of Motorola seems like 1 year or less.
 
Except not all of it is. This sort of situation is unacceptable because it undermines the whole thing that got Android hype in the first place.

If this becomes standard then the status quo goes right back to normal and people go right back to being told what they can and can not do with hardware that they have purchased. Unacceptable.

It's bound to happen. A good example is tethering. The phone companies want to charge for it, yet people creating custom roms can allow you to do it without restrictions. The choices are to lock it, charge more for excessive data or not use android phones at all. What do you really want to happen?
 
You can always tell someone who knows nothing about handheld systems, or even programming in general.

Motorla had to port the Android operating system to their device. They most likely had to optimize and compile it for the specific architecture they chose. Additionally, they had to license and integrate drivers for every single device on the phone (camera, storage, modems, display, sound, touchscreen, etc.). And finally, they had to design the user interface. Every step of the way has to be rigorously tested on both the underlying technical aspects as well as the user interface stuff that you see. The end result is a ROM that is made by Motorola for Motorola devices and has tons of money and time invested in it. Android only provides a framework for the integrator to use, contrary to what all the Android fans think, integrators don't just design their devices, hook up a USB CD drive, insert the Android CD, run a graphical installer, and they're done.

These ROMs are valuable works that probably also have trade secrets about Motorola's hardware in them. It is not legal for you to take Motorola's ROM and stick it on another maker's device, and it's certainly not legal for the other makers to use Motorola's ROM. Motorola has every right to aggressively protect their Android ROM with eFuse.

Well said.
 
Root was not hard, Milestone has root for ages. I give it about maximum 5% chance to get custom ROMs for Milestone or Droid X in 1 year.
 
True, only time will tell. I think the Droid x poses a larger target for those looking to gain access to the boot loader so I'm optimistic. If not it wont be the biggest loss on that device, it will receive 2.2 as an update and the current skin does a good job of filling in the gaps in 2.1

It sucks that they might not update the milestone as 2.2 is a million times better. Not saying much considering most things are a million times better than 2.1, I.e a sharp stick in your eye or being set on fire. Just kidding on that last bit, but android has a long way to go in terms of UI and 2.2 is far from webos and ios, but hey at least we finally have a static phone button that is on all screens.

Take solace in that you still have more screens on your milestone 7 or 9 vs 5 with 2.2 and 3 with 2.1
 
Back
Top