Motorola Droid 2.1

[christim]

i need help on root its asking me choose your bashrc (for adb shell) Linux/mac OS X Color bashrc or Windows Non- colored bashrc. i dont know wich one to pick

The answer to this is listed many times within the thread where you found out about that app. I like this answer better: Do you like colors?

 

[windstrings]

Can't edit for some reason.

7. Does it screw up all your existing apps that are already installed and presently run on the 2.0.1 platform?.. If so are you limited to the apps from places other than the market?

 

[christim]

I realize this thread is now purely for entertainment and humor sake, but my input is to say forget 2.1 as Google has released it. Of MUCH MORE concern is bug fixes and basic functionality.

2.1 should be:

1. BT voice dialing
2. Gmail app able to display inline images
3. UI speed improvements

Don't forget:

4. Exchange (ActiveSync) fixes
5. Official App2SD support

6) Flash (ha, post to short? I usually have the other problem!)

 

[DROIDMASTER]

2.1

Hopefully since google has released the "2.1 update 1" to the nexus hopefully this is the bug fix and they will issue a download for "2.1 update 1" for the droid. I'm crossing my fingers... and toes!

 

[BostonBill]

i need help on root its asking me choose your bashrc (for adb shell) Linux/mac OS X Color bashrc or Windows Non- colored bashrc. i dont know wich one to pick

Conventional wisdom seems to be
If you use windows pick non colored
If Mac pick color

 

[gregsjh13]

but I'm scared
:icon_eek:
----runs away-->

im telling you its worth it..i have multi touch and everything i have ever wanted...im running 800 mhz

1. Are you noticing the battery gets sucked down much quicker?
2. Does the CPU still have the ability to "rest" when not in use or does it just run at 800mhz all the time?
3. Normal is 550, your at 800mhz.... thats a serious percentage jump.. most processors I've ever seen are not stable and are at risk of toasting with that percentage of a jump?
4. If you root how hard is it to "undo" should the 2.1 update come out?
5. Is there an advantage to getting the OTA 2.1 update "should it ever come out" over rooting?
6. Is there a disadvantage to rooting?

I hope this is not considered off topic.. considering the deliemma we are all in, its a real consideration to discuss.
Our Mods, Verizon, and even Google said we would get it....... by 1/21 "I think it was" since that never happened this is a worthy discussion.

the battery is infact better and 800 mhz is very stable..i dont get any chrashes the muti touch is amazing and all it takes is a simple 2.0.1 drag to the sd card in order to unroot.As for 2.1 i can get it now if i really wanted to and there is NO disadvantage to rotting I LOVE IT..my droid is 30 percent faster.

 

[gardobus]

1. Are you noticing the battery gets sucked down much quicker?
2. Does the CPU still have the ability to "rest" when not in use or does it just run at 800mhz all the time?
3. Normal is 550, your at 800mhz.... thats a serious percentage jump.. most processors I've ever seen are not stable and are at risk of toasting with that percentage of a jump?
4. If you root how hard is it to "undo" should the 2.1 update come out?
5. Is there an advantage to getting the OTA 2.1 update "should it ever come out" over rooting?
6. Is there a disadvantage to rooting?

I hope this is not considered off topic.. considering the deliemma we are all in, its a real consideration to discuss.
Our Mods, Verizon, and even Google said we would get it....... by 1/21 "I think it was" since that never happened this is a worthy discussion.

Can't edit for some reason.

7. Does it screw up all your existing apps that are already installed and presently run on the 2.0.1 platform?.. If so are you limited to the apps from places other than the market?

I know it wasn't directed towards me but I'll answer this using my experience with Bugless Beast 4.7 so far.

1. & 2. Battery seems the same or even better. While I am running at a max of 800, I also set it to drop down all the way to 125MHz when it is in standby. You can also set profiles so it runs at different MHz depending on if its charging, <100%, etc.
3. So far 800 is very stable and has given me no issues. The phone doesn't feel any warmer than usual to the touch. Also, many people are already running theirs at 1GHz. I don't have the balls to do that yet but if they can do it, I should be okay at 800 lol
4. Unrooting requires you to download one file and flash it. Done. There is a thread here somewhere. In one step you can remove root/recovery/ROM and go back to all stock so that you can get OTA updates and the original OS.
5. The advantage of OTA updates are that you get them right away. If you want to stay rooted, you'll have to wait for someone to root 2.1 and build a ROM out of it. I don't think this takes long most the time though.
6. So far I can't find one besides not getting OTAs right away.
7. Every app I had installed before I put BB4.7 on my phone is still on there. You can still install apps from the Market like you would before. Sometimes you get better results from wiping everything and starting fresh but you don't HAVE to, you can keep your stuff.

Hope that helps you out I am SO glad I rooted/flashed my Droid and won't be going back any time soon.

 

[swallman]

Interesting thread over on Motorola Support Forums (https://supportforums.motorola.com/message/111268#111268)

Sounds like they are definitely working on 2.1

Question:

So come on Motorola, just tell YOUR CUSTOMERS what the status is. Do you have the 2.1 update from Google? Are you working on it? Are you waiting for 2.1.1? You must have an internal release date...why not offer us a clue. "Within a week". "Within two weeks". "Before the end of the month". Or maybe "We've passed the update onto Verizon and it is now up to them to push it out".

Reply:

Well of course we are working on it. We announced that it's coming so I think it stands to reason that we're working on it, right? More I cannot say.

 

[windstrings]

Well I appreciate the info on rooting, I'm sure it give many of us something to think about besides just fussing at each other.

Much of the stuff you said was over my head..... I would have to educate myself for sure.

As much as I would love to know how to root and unroot etc.. its a lot to think about..... I'll let that info jell while I peek around on those threads and see if I start feeling froggy or whether I want to wait.

I think many of us would love some piece of positive confirmable info about the date of 2.1 "or not" so we don't get in over our heads trying to root.....

Rooting is not for everybody... I know that for sure.....
While others just need some encouragement and would do fine.

But if I get froggy enough, I just may take the plunge.... it would be an adventure..... something many of us thrive on or else we wouldn't be so crazy waiting for the 2.1 OTA.

Thanks to the Mods for indulging and allowing the diversion of thought.

I will have to do some reading..... I love a challenge... but I have to know enough to make an intelligent jump... I don't go around jumping off cliffs unless I"m pretty sure I can fly.

 

[DavidDroid]

First?

No just kidding, but seriously, I had no clue, interest, or desire whatsoever for a 2.1 update until I came to these forums. Now I am gripped every hour of the day hoping and pleading to the Google Gods that 2.1 is released. So thanks droudforums for ruining my life based only on speculation. /spambutnotreallycauseIthinkthisthreadshouldbelocked

 

[windstrings]

Interesting thread over on Motorola Support Forums (https://supportforums.motorola.com/message/111268#111268)

Sounds like they are definitely working on 2.1

Question:

After reading that link, its apparent the closed lips are due to people throwing fits when they don't get what they are expecting.....
So until they know for sure, they won't say.

It sounds like the 1/22 date was the original date but something delayed the date.

YOu would think they could just make a simple announcement that says the date is postponed but stay tuned.

But it seems they take the attitude that most people are happy and mentioning an update only gets everybody in an uproar... they would rather us not even know about them and let them be a surprise.

Otherwise they get lots of phone calls, complaints, and disgruntled people when they promise things and can't deliver.

They don't like the pressure.... can't say I blame them.

But they can't even throw us a bone without it being a problem..... we are such savages you know!....... sadly... thats the truth!

 

[windstrings]

Humm... well I don't have the guts yet..... just one thread alone has almost 1000 post on the Hack section.

Seems this rooting to 2.1 is by not means and exact science and many folks are still having issues while others are doing great..... its a lot to learn "thats an understatement"

Without a confindence it hard to tackle. That thread has gone on for so long you can't tell whats new and what old..... you would have to literally study the whole thing to understand what to skip "because its old info" and what to apply.

Is there someone thats already done the rooting to 2.1 that started with no knowledge at first that can offer some encouragement, because right now it seems suicide to just start wiping out a perfectly good working Droid in hopes to make it better.

 

[MarkO]

If I root my phone and apply 2.1 will I get pinch feature on maps, or is that still not available?

 

[TexasRules777]

If you head over to droid-life.com they show how to get pinch and zoom maps without rooting.

 

[karnaak]

Its likely that 01/22/10 was going to be the day that Motorola and VZW were going to push the 2.1 update; however, they may have backed off with guidance from Google in regards to the addition of multi-touch for the core OS apps (like the N1 just got).

Google may have informed them that they wanted multi-touch to be available, and instead of VZW and Moto pushing out one update followed by a second, they decided to retract the update and release it with all the features the N1 has as of the OTA push yesterday.

Or I could be wrong...