• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help froyo has issues...i want to go back to 2.1 please help

afine1

Well-Known Member
Jan 6, 2010
176
1
issues i have found.

1. My browser is very slow to respond to movements. zoom in out seems to work ok but moving pages left right up down sucks. pages are very laggy.

2. why did they remove the .com button from the keyboard.

3. a lot of apps dont work anymore. handcent, home++, pure calander, etc. (maybe because they have to be updated by the developers)

there are many other issues but these are only a few examples.

i just want to go back to 2.1. can someone please help. i will update again with the ota. hopefully by then the developers are ready with updates.

here is some more.

maybe this is because i set the power key to end calls, but the power key does not power off the phone anymore. to do this i had to pull the battery out.
 
The original question afine1 asks is a good one. It doesn't sound like she needs to roll back now but what if you did want to do it?

If you do a factory reset you will unfortunately still have 2.2 after the reset.

Since I haven't upgraded yet what is the procedure for backing up 2.1 and then doing a restore if necessary?
 
Upvote 0
if it is flash that is doing this then to hell with flash. i cant believe that they would add something that would ruin the browser experience.

flash is still in beta, so it's going to have stability and performance issues. how much it's going to be improved we will have to wait and see till it's official.
also, you don't have to uninstall it. instead you can make it only load when you want it to.
go to>browser settings, select enable plug-ins, and set it to "on demand."
now when there is flash content on a webpage, it will only load when you click on it.
 
Upvote 0
flash is still in beta, so it's going to have stability and performance issues. how much it's going to be improved we will have to wait and see till it's official.
also, you don't have to uninstall it. instead you can make it only load when you want it to.
go to>browser settings, select enable plug-ins, and set it to "on demand."
now when there is flash content on a webpage, it will only load when you click on it.

i did this, thanks. but are there other plug-ins that have been running prior that are also "on demand" now?

The original question afine1 asks is a good one. It doesn't sound like she needs to roll back now but what if you did want to do it?

If you do a factory reset you will unfortunately still have 2.2 after the reset.

Since I haven't upgraded yet what is the procedure for backing up 2.1 and then doing a restore if necessary?

yes this is the root question of my post.
 
Upvote 0
i did this, thanks. but are there other plug-ins that have been running prior that are also "on demand" now?



yes this is the root question of my post.

I don't know of a way to see all the plugins you have installed. i also don't know of any other plugins.

unless you are rooted and proficient with modding your phone, i don't think it's possible to go back to 2.1. xda would be a better source for this kind of info: Nexus One - xda-developers
 
Upvote 0
It's entirely possible to go back to original build or even 2.1update1.

if you flash the original, the phone will auto update to 2.1update1

I am of the opinion that if your 2.2 is messed up or not to your liking then the way you got it on the phone in the first place was not the best way. Or maybe the optimal way. There's so many here and on xda that flashed this or that, recovery update this or that, flashed ontop of other stuff, etc.... No wonder there are some messed up phones out there.

if you set browser to desktop string in the about:debug settings.
set on demand in browser settings
set animations to off in display settings
then things are really nice.
but this depends on how you went about getting 2.2 in the first place I think.
2.2 is better than 2.1update1, this should be a given. If it's not then your phone is messed up.

fresh install is the only way to go in my book.
fasttboot erase everything and get back to the 79 build
let the phone auto update to 2.1update1
manual install 2.2 with stock recovery.
reflash custom recovery and install root zip from cyanogen. (2.6.33,34)
(launcherPro) install here if desired.
Done deal. No issues.
I'm not ripping on you OP. It's just that there's so many out there that the boards are flooded with messed up phones and bad info.

flash works fine, 10-20 seconds of choppiness, then it clears up for me. Audio sync is good. tested cnn.com..... even a phone call interrupt stops the player in the browser while you're on the phone, and then resumes when you push the end call button. ((wifi)
 
Upvote 0
another issue in froyo is the volume/vibrate thing. the original let you turn up/down volume, then a vibrate mode then silent mode. now the vibrate mode is gone. you can manually turn it on or off but you have to now go through menus to do this. what a PITA. you either have ringer on or off now with the volume rocker. there is the option to to use it to go to vibrate but then you lose the silent option. pretty dumb in my opinion.

why is this dumb you ask. 1. it takes away a basic option and 2. when you set the vibrate on it comes on in silent mode...vibrate on is not silent.
 
Upvote 0
Really confused as to why someone would want to go back. Froyo is way faster than Eclair. I love it.


Because Google broke a bunch of apps. Apparently app compat testing is not something they do or care about.

AAC audio streaming? Broken
Touchdown Exchange? Broken
DroidLive? Broken (now fixed, but no AAC)

Oh, and the new radio image breaks video playback if you roll back to 2.1. So if you go back, you need to re-flash your radio.

In the end I don't care how fast some dumb ass benchmarks scores are, if my apps don't work I don't care to use it.

GOOG needs to learn how to work better with their developers. You don't go and change shipping APIs or their behavior out of the blue without very good reason. That's a newb mistake. But we all know that GOOG is pretty much a newb when it comes to supporting a development community.

I'll wait for Cyanogen to get it right. Because it seems Google cannot.
 
Upvote 0
Because Google broke a bunch of apps. Apparently app compat testing is not something they do or care about.

I'll wait for Cyanogen to get it right. Because it seems Google cannot.

At the speed updates are released I'll bet the vendors didnt need long to get their apps tweeked. Maybe thats why google didnt intend a general release for a couple more weeks?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones