Motorola DROID A855 update??

[jeffv2]

If your running a custom rom then the "update" will most likely be a "downgrade"

Sent From My Droid Without Spell Checker

 

[ShaggyFlyer]

So, if we're rooted, just ignore the update? Will it keep trying to push it to us?

Sent from my Droid using DroidForums App

If you're rooted, with an alternate recovery like SPRecovery or Clockwork Recovery installed, and if you have a custom rom installed, then you don't have to worry - the OTA Update WILL fail. It will be looking for certain things, and when it doesn't see them the installation will simply abort. You can, under those circumstances, accept the OTA and just let it fail in the installation. My concern is for the people who've rooted, but haven't installed a custom recovery or custom rom. Those people are in danger of having Motorola's update screw with their phone and possibly prevent future re-rooting. Motorola does not take kindly to people who choose to root their phones and makes every effort to un-do what the people did.

Just be careful out there...

-Mike

Thanks UltraDroid, I guess I'll take my chances with the update. I have my D1 rooted with SPRecovery but, running stock OS. Just haven't grown a pair to install a custom rom yet. Went really slow and careful with root and made it no problem. This forum is the greatest and there's no way I could have rooted with out the helpful info you guys share.
Thanks a bunch, Shaggy

 

[odoyle81]

do you have to add a new entry to build.prop to ignore this update? anyone know the code?

This was the old code, but I don't know what the new release keys should be...

http://androidnexus.com/rooting-and-custom-roms/stop-the-september-frg22d-ota-update-for-the-droid

 

[A2Aegis]

Instead of focusing on 2.2 updates, they should go ahead and work on 2.3 instead.

 

[UltraDroid]

Instead of focusing on 2.2 updates, they should go ahead and work on 2.3 instead.

But 2.3 is Gingerbread, and the chance of Motorola providing that to the original Droid1 is very slim. If you are rooted though, you can avail yourself of several really good Gingerbread custom roms which have been out there for several months now. This goes back to one of my original points: most OTA updates are *worthless* for people who've already rooted their phones and installed a custom rom. The feature enhancements being provided are usually "old news" at the time of delivery, and carry the danger of wiping out your existing root while installing a dubious software "upgrade".

-Mike

 

[jeffv2]

the 2.2.2 update was as simple as recompiling the source.. 2.3 would take a long time.

 

[tnronin]

If your running a custom rom then the "update" will most likely be a "downgrade"

Sent From My Droid Without Spell Checker

Since nobody called you on this info I will take it as good. I have not been prompted to do an OTA and I will do what I can to avoid it now. Unless there is some whiz-bang feature in 2.2.2 I'll stay rooted with CM6. Totally happy with CM!

 

[davros]

Anyone get the release keys?

 

[AngryHatter]

It is an SMS bug fix.

 

[aaf709]

I'm wondering if I'll have to reinstall Swype (at least get a new license).

Your beta should have stopped by itself anyway. New beta started 03/11/2011.
uninstalling both the app and the installer and proceeding from scratch seems to be working for most people.

I've discovered that whenever I've had an update, Swype stops working. Well, that's not entirely true; it works by touching, but not by swiping. When I got the last update I simply deleted the data on Swype and used the installer to generate a new license.

I got the update this morning without any change in Swype. Nothing else to report.

 

[PatG]

Your beta should have stopped by itself anyway. New beta started 03/11/2011.
uninstalling both the app and the installer and proceeding from scratch seems to be working for most people.

I've discovered that whenever I've had an update, Swype stops working. Well, that's not entirely true; it works by touching, but not by swiping. When I got the last update I simply deleted the data on Swype and used the installer to generate a new license.

I got the update this morning without any change in Swype. Nothing else to report.

Got the update yesterday and Swype stopped working. You can type but not swype. What does it mean to "Simply delete he data on Swype and use the installer to generate a new license? Delete a data directory on the phone and run the installer again?

 

[AngryHatter]

Your beta should have stopped by itself anyway. New beta started 03/11/2011.
uninstalling both the app and the installer and proceeding from scratch seems to be working for most people.

I've discovered that whenever I've had an update, Swype stops working. Well, that's not entirely true; it works by touching, but not by swiping. When I got the last update I simply deleted the data on Swype and used the installer to generate a new license.

I got the update this morning without any change in Swype. Nothing else to report.

Same here.
The Swype beta from December had expired on March 9th and I suspect that was the trouble.

 

[furbearingmammal]

Open your Swype Installer, check for an update. Then reinstall Swype. You'll need to get a new license because, surprise, after the phone updated it didn't spec out the same as the first install.

I ran into this problem a lot flashing CM nightlies. Frankly, with all the Swype fails I had, I just went back to the stock keyboard. The Gingerbread keyboard is the best one I've used.

 

[aaf709]

Got the update yesterday and Swype stopped working. You can type but not swype. What does it mean to "Simply delete he data on Swype and use the installer to generate a new license? Delete a data directory on the phone and run the installer again?

OK, I went to Settings>Manage applications>Swype and pressed the "Clear Data" button. Then I opened the Swype Installer (which I had left installed). It'll ask if you want to generate a new license. Log in and do so. Swype should work after that. This is assuming Swype and the Installer are up to date.

 

[PatG]

Got the update yesterday and Swype stopped working. You can type but not swype. What does it mean to "Simply delete he data on Swype and use the installer to generate a new license? Delete a data directory on the phone and run the installer again?

OK, I went to Settings>Manage applications>Swype and pressed the "Clear Data" button. Then I opened the Swype Installer (which I had left installed). It'll ask if you want to generate a new license. Log in and do so. Swype should work after that. This is assuming Swype and the Installer are up to date.

I cleared the data, downloaded a new installer, then uninstalled and re-installed. Unfortunately now I get a Registration of Swype failed. Went onto the site, had them re-send the e-mail, but no joy. Registration is still failing.

Anything I need to do at the website to generate a new license. User ID and password are correct as I can log into the Swype website