DROID 2.1 Update thread.

[Cory Streater]

This is wrong! You will still get the notification unless you have renamed your tampered with your otacerts file on the phone.

Restore 2.0.1 for rooting, or Unroot/Unbrick your phone using .sbf

FOLLOW THE GUIDE STEP BY ****ING STEP IF SOMETHING FAILS OR DOES NOT WORK STOP AND POST IN THAT THREAD (NOT HERE OBVIOUSLY) AND SOMEONE MIGHT HELP YOU! AGAIN FOLLOW THE GUIDE STEP BY STEP!

Please calm down.

 

[Chris Kerrigan]

My apologies on the rooting comment, I was thinking of something else.

Disregard

 

[anon(7773)]

~sigh~
Why don't people understand that Live Wallpaper does not kill their battery?


I promise, if you look at your battery usage info, it'll be using 3% or a number very close to that.

LWP are only on when your screen is on!

So if you don't ever set a timeout on your screen and you sit and stare at it with your mouth agape for about 3 hrs, yeah, it'll hurt your battery.

Don't sacrifice such beauty for what you think is performance! Because you are dead......dead wrong.

A couple of days ago when I removed my wall paper my keyboard quit lagging, then tonight I read your post and DM_Droids post and decided to try the wall paper again. The keyboard is working fine!! Thanks! If my keyboard lags again I will just reboot and see if that does the trick.

 

[wavechaser]

I could have swore that I read somewhere about an auto-dim feature being added to the google maps navigation for those driving at night so we aren't blinded. I played with it a bit today and it didn't seem to work at all, is there an option somewhere I'm missing?

 

[GenericMessage]

So is cautioning people and correcting people against the rules on this forum dude?

How about I put no warning then someone screws up and bricks their phone totally and completely then they come after me asking questions etc because I didn't warn them. I'd rather caution them in a mean loud way then having to waste my time correcting their mistake because I feel guilty.

Second I was correcting someone. I used one exclamation point oh no!

Chill out.

I would think about editing this........

I wouldn't wanna get the ban hammer swung at me.

 

[GenericMessage]

Any word on just how long some of us are supposed to wait for this update?

And no, I don't want to do the manual one. I've read more problems in this thread with the manual update than with the OTA one.

The Manual and the OTA are the same thing...........

 

[GenericMessage]

A couple of days ago when I removed my wall paper my keyboard quit lagging, then tonight I read your post and DM_Droids post and decided to try the wall paper again. The keyboard is working fine!! Thanks! If my keyboard lags again I will just reboot and see if that does the trick.

Fantastic! Glad to hear it!

 

[Romple]

5-10 seconds to analyze what you said is most likely a lot faster than typing out a long text, especially while busy driving or wasting your life playing WoW.

 

[ms960]

hi guys, I'm sorry if this issue has been addressed earlier but my problem is that i had gotten the OTA update and when it was all done and I slid the unlock button it has a force close window that wont stop popping up that says, "the application launcher(process com.adroid.launcher2) has stopped unexpectedly. Please try again.". So i was wondering if this has anything to do with the fact that i was running some software i downloaded off one of these forums that give my droid the nexus one software. The one with the 3d app menu launcher and 2.1 gallery and music versions as well as the 5 home screens. So if anyone can help i would really appreciate that.

Did you ever resolve this problem?

I got the update notification this morning, and installed it. I'm not having the same problem as you. I slide the unlock button and all I get is a Force Close message (process com.android.launcher2).

My phone is unusable...any help would be awesome!

 

[prometheus]

I didn't feel like reading thru a 1000 posts.... so, sorry if this was covered already...

**this applies to rooted Droids running Droidmod roms**

(may apply to other roms. But, I can't confirm)

If you keep getting the "2.1 update available" popup from verizon -- just select "install now". You'll reboot into SPRecovery and the install will fail. Select "reboot now. Nothing will change and the popup message will stop.

again... sorry if this is old news. It just happened to me this morning and I did a little reading on Droidmod's site and thought I'd share. If this is old news, please ignore.

 

[stayup21]

Did you ever resolve this problem?

I got the update notification this morning, and installed it. I'm not having the same problem as you. I slide the unlock button and all I get is a Force Close message (process com.android.launcher2).

My phone is unusable...any help would be awesome!

So far nobody has responded so we must wait patiently i guess. I don't want to bring it to Verizon and then have them tell me to either leave the phone their overnight or just not be able to fix it. I don't know about where you live but on Long Island every Verizon store sucks and there is a solid chance that the consumer knows more than the employee. Lets hope for the best.

 

[WarER4X]

I could have swore that I read somewhere about an auto-dim feature being added to the google maps navigation for those driving at night so we aren't blinded. I played with it a bit today and it didn't seem to work at all, is there an option somewhere I'm missing?

They already put that change into Google Maps through an update from the Marketplace that was pushed out before 2.1 was released. The night-view changed doesn't actually do anything to the screen dimming; instead, it simply displays Google Maps Navigation with a dark background scheme so that it's not too bright for your eyes. It does it based on the time of day, to determine when it is actually "night time" (same way my Garmin does). I don't know if you can force it to show the night view scheme manually, but if you bring up navigation when it is night time, you will see the difference.

-SR-

 

[WarER4X]

So far nobody has responded so we must wait patiently i guess. I don't want to bring it to Verizon and then have them tell me to either leave the phone their overnight or just not be able to fix it. I don't know about where you live but on Long Island every Verizon store sucks and there is a solid chance that the consumer knows more than the employee. Lets hope for the best.

I didn't have a Launcher2 app installed when I updated to 2.1, but I did install HelixLauncher2 (which is not yet Droid 2.1 compatible) so that I would get an update notification when it was made compatible with Droid. Still, for kicks, I ran the HelixLauncher2 and watched it give me repeated force close notifications. Between force closes, I manged to bring up the settings menu so that I could go to "Manage Applications" and kill HelixLauncher2 (and you can disable it as the default launcher while your there, too). Bottom line is, if you can get away from your home screen, it should stop force closing so that you can do something about it. Of course, if it's messed up enough now so that you can't get it to even go to the homescreen and start force closing, I guess you'll just have to factory reset it or something.

Bottom line is, if your launcher2 keeps force closing on the homescreen, there is still hope. Just get to the phone's settings menu in between force closes and you will be able to fix it without doing anything drastic.

-SR-

 

[ms960]

They already put that change into Google Maps through an update from the Marketplace that was pushed out before 2.1 was released. The night-view changed doesn't actually do anything to the screen dimming; instead, it simply displays Google Maps Navigation with a dark background scheme so that it's not too bright for your eyes. It does it based on the time of day, to determine when it is actually "night time" (same way my Garmin does). I don't know if you can force it to show the night view scheme manually, but if you bring up navigation when it is night time, you will see the difference.

-SR-

I work very close to a Verizon store, so I took it in and showed them the problem. They just swapped it out with a new phone. Kind of a pain reinstalling things, but I can now use my phone again.

 

[wavechaser]

They already put that change into Google Maps through an update from the Marketplace that was pushed out before 2.1 was released. The night-view changed doesn't actually do anything to the screen dimming; instead, it simply displays Google Maps Navigation with a dark background scheme so that it's not too bright for your eyes. It does it based on the time of day, to determine when it is actually "night time" (same way my Garmin does). I don't know if you can force it to show the night view scheme manually, but if you bring up navigation when it is night time, you will see the difference.

-SR-

That's what I meant, the dark background so you can use the nav at night without being blinded.

Mine doesn't have the dark background when I use the nav that automatically activates when you put it in the car dock.

Why is that?

Edit: I just manually searched for a google maps update and found it in the marketplace. Hope that fixes it. That's pretty lame though that I manually have to go out and search for an update like that, I figured those kind of updates would give me alerts on my phone.

 

[stayup21]

I didn't have a Launcher2 app installed when I updated to 2.1, but I did install HelixLauncher2 (which is not yet Droid 2.1 compatible) so that I would get an update notification when it was made compatible with Droid. Still, for kicks, I ran the HelixLauncher2 and watched it give me repeated force close notifications. Between force closes, I manged to bring up the settings menu so that I could go to "Manage Applications" and kill HelixLauncher2 (and you can disable it as the default launcher while your there, too). Bottom line is, if you can get away from your home screen, it should stop force closing so that you can do something about it. Of course, if it's messed up enough now so that you can't get it to even go to the homescreen and start force closing, I guess you'll just have to factory reset it or something.

Bottom line is, if your launcher2 keeps force closing on the homescreen, there is still hope. Just get to the phone's settings menu in between force closes and you will be able to fix it without doing anything drastic.

-SR-

i appreciate the response and i tried to get to the settings menu but i cannot. SO i guess i have to do the factory reset. This is kind of silly but how do you do a factory reset and will i lose anything off my sd card and if so should i remove it first before doing the reset?

 

[wavechaser]

How much RAM does the Droid have? I'm finding it surprisingly hard to gather that information.

 

[Roy Aguilera]

So far nobody has responded so we must wait patiently i guess. I don't want to bring it to Verizon and then have them tell me to either leave the phone their overnight or just not be able to fix it. I don't know about where you live but on Long Island every Verizon store sucks and there is a solid chance that the consumer knows more than the employee. Lets hope for the best.

What they will do is factory restore. You can save some time by doing the same. I'm guessing that you are not root and the apps were just installed as apps and not pushed to system. A factory restore would delete said apps and get you back to not having fcs.
The reason you are getting the fcs is because the old launcher2 does not work with ESE81 and since you had it set as default your phone tries to open and run it.

Try these in this order.

You can try this and see if it works.
-Hit Home (hopefully it lets you pick between home and Launcher)
-Hold down the home key (it will bring up the last 6 apps you used). Hopefully you used the market. If you did, open it and install helixlauncher1.
This will now give you the option to reselect a home. hit home and pick either home or helixlauncher1.
-Last resort would be a factory reset

 

[get quad]

256MB Ram
512MB Flash ROM
256MB Available internal user storage
up to 32GB micro SD card supported

 

[Roy Aguilera]

i appreciate the response and i tried to get to the settings menu but i cannot. SO i guess i have to do the factory reset. This is kind of silly but how do you do a factory reset and will i lose anything off my sd card and if so should i remove it first before doing the reset?

If you cant get to setting, boot into recovery (power off and restart the phone while holding down the x on the physical keyboard). You will see a phone with an exclamation point.

Now
Hit the volume up and camera button at the same time.

It may take a couple of tries but eventually you will get into recovery.

Wipe data and cache.

You will not lose anything on the sd but will lose your settings, texts and have to reinstall your apps.
All paid and free apps are available from the market at no charge to you. You already paid for them.