Anyone rocking a Motorola Milestone 1?? Your Froyo is ready

[Bateluer]

http://www.engadget.com/2011/03/15/motorola-milestone-achieves-android-2-2-milestone-at-last-froyo/

but Motorola warns that any DRM-locked media you have on your SD card will be lost. Weirdly enough, there's also a caution that "users may experience some adverse effects associated with the upgrade which could include slower operation of some phone functions and applications.

Welcome to last year?

 

[cronos]

Isn't the Milestone really just a GSM Droid?

 

[Bateluer]

Isn't the Milestone really just a GSM Droid?

Pretty much, with an encrypted boot loader. Which is why its been stuck on 2.1/Eclair for the past year. There's some Frankenstein-ish Froyo ROMs that exist, but they're all built with the Eclair kernel from Motorola. Not particularly stable, from what I understand.

 

[Suspicious-Teach8788]

Thank you for making a thread just for me

Pretty much, with an encrypted boot loader. Which is why its been stuck on 2.1/Eclair for the past year. There's some Frankenstein-ish Froyo ROMs that exist, but they're all built with the Eclair kernel from Motorola. Not particularly stable, from what I understand.

You can run from the eclair kernel, but the issue here if you've followed a lot of Moto development, is not so much the encrypted kernel. This applies for the D2 and Dx also, but it's more the proprietary radio and stuff. While custom kernels are nice, Moto's proprietary radio drivers are more of an issue because a lot of times we can boot but fail to get cell signal or wifi is broken. You don't necessarily need an updated kernel to run a new version of Android. For example Gingerbread runes fine on the 2.6.32 kernel. Google included a new kernel not because it was necessary but because they could.

We've had a beta Moto 2.2 kernel since October or so of last year. While it was Beta, it was good enough. CyanogenMod 6 has been stable for at least 5 months now for us. After the beta kernel, we got ourselves some updated kernels. It's not much different. The leaked kernels from Feb and even today's official update are roughly the same, so essentially we've been getting the same 2.2 since October. No they are not unstable at all.

But once again this is just a poor showing from Motorola. Compound this with the fact that the Milestone's 256MB memory is completely insufficient... well... Sadness.

 

[foghorn67]

256 was more than 192 from HTC's mytouch 3g and the G1. So your hate shouldn't be exclusive to Motorola. I know its difficult due to your HTC fetish.

 

[Bateluer]

Thank you for making a thread just for me



You can run from the eclair kernel, but the issue here if you've followed a lot of Moto development, is not so much the encrypted kernel. This applies for the D2 and Dx also, but it's more the proprietary radio and stuff. While custom kernels are nice, Moto's proprietary radio drivers are more of an issue because a lot of times we can boot but fail to get cell signal or wifi is broken. You don't necessarily need an updated kernel to run a new version of Android. For example Gingerbread runes fine on the 2.6.32 kernel. Google included a new kernel not because it was necessary but because they could.

We've had a beta Moto 2.2 kernel since October or so of last year. While it was Beta, it was good enough. CyanogenMod 6 has been stable for at least 5 months now for us. After the beta kernel, we got ourselves some updated kernels. It's not much different. The leaked kernels from Feb and even today's official update are roughly the same, so essentially we've been getting the same 2.2 since October. No they are not unstable at all.

But once again this is just a poor showing from Motorola. Compound this with the fact that the Milestone's 256MB memory is completely insufficient... well... Sadness.

Thanks for the clarification, I don't follow the Milestone development that closely.

 

[Suspicious-Teach8788]

256 was more than 192 from HTC's mytouch 3g and the G1. So your hate shouldn't be exclusive to Motorola. I know its difficult due to your HTC fetish.

Those phones are also lower res. Futhermore, they were considered old phones. The Droid was supposed to be a iPhone 3GS competitor that came 5 months later. So yeah, it's supposed to do just as well.

The fact that it's completely outdated and the memory is insufficient goes to show that either Moto poorly chose an insufficient amount of memory or Android is using too much memory.

And no I don't have an HTC fetish. I don't like their AMOLED screens that much right now, and they don't really have a phone in their lineup at the moment that I want. I did buy a Nexus One and return it.

 

[Bateluer]

Those phones are also lower res. Futhermore, they were considered old phones. The Droid was supposed to be a iPhone 3GS competitor that came 5 months later. So yeah, it's supposed to do just as well.

The fact that it's completely outdated and the memory is insufficient goes to show that either Moto poorly chose an insufficient amount of memory or Android is using too much memory.

When the Droid/Milestone was released, 256MB of RAM was pretty standard for a high end smartphone guys. 512MB-768MB is standard now.

 

[foghorn67]

Those phones are also lower res. Futhermore, they were considered old phones. The Droid was supposed to be a iPhone 3GS competitor that came 5 months later. So yeah, it's supposed to do just as well.

The fact that it's completely outdated and the memory is insufficient goes to show that either Moto poorly chose an insufficient amount of memory or Android is using too much memory.

And no I don't have an HTC fetish. I don't like their AMOLED screens that much right now, and they don't really have a phone in their lineup at the moment that I want. I did buy a Nexus One and return it.

Droid Eris, (HTC Hero)...which were current phones, had the same amount of RAM. Droid Eris was actually released within days of the Droid 1.