returning phone due to Froyo

SeattleYanksFan · Sep 3, 2010

poseidonato said:
Question, after updating to the 2.2, my battery life seems to drain faster and in task manager, preloaded apps keep starting back up. Is there a way to get back to the better battery life?

Stop using the phone.

pucrepeap · Sep 3, 2010

SeattleYanksFan said:
Stop using the phone.

Haha...true. When I first got 2.2 I thought the battery sucked! Then I realized I was so excited to check out what Froyo offered that I was on my phone the whole day.

Sure enough a couple days gone by, my excitement regulated, and my battery/phone having those days to recalibrate and re-familiarize with each other, my battery is as good as ever.

...and don't waste time trying to regulate you running apps with an app killer. You just end up using more juice constantly looking whats going on rather than just letting the phone manage it.

I really think people should step back and give the phone and update time to settle, it seems to make a difference. That and a factory reset.

poseidonato · Sep 3, 2010

I've read plenty of articles saying that the task killers are no longer needed in the new 2.x UI but was more needed in the older ones. The apps if idle should stop draining juice and should just eb regulated by the UI itself.

True, maybe I haven't given it enough time to re-calibrate and realize what the battery life is like but a few of my colleagues said the same thing. Just wondering if there was some settings that were activated that shouldn't have been that I can deactivate.

Thanks pucrepeap.

zemerick · Sep 3, 2010

pucrepeap said:
...and don't waste time trying to regulate you running apps with an app killer. You just end up using more juice constantly looking whats going on rather than just letting the phone manage it.

This: With 2.1 task killers were fairly iffy, and not in proper hands were bad. With 2.2 they are only even usable for their true purpose ( to kill a broken/crashed/frozen/stuck/problem App. Not something running normally, which will start back up. )

I really think people should step back and give the phone and update time to settle, it seems to make a difference. That and a factory reset.

This x10. People saw a couple birds fall out of the sky, and are now screaming that the sky is falling. We need to step back and actually look at the sky that is so far still where it has been, if not a little brighter...and also of course, try and help the birds that did fall out of the sky, so long as they aren't rabid, in which case I vote to just shoot them

makewayhomer · Sep 3, 2010

went to verizon, guy couldnt help, confirmed my phone was effed, but said they were all effed. he was clueless basically

so, can anyone tell me what I can do now? I have never rooted before, need to downgrade from ota froyo to I can root to a workable rom

(the problem is that the cpu is screaming causing battery drain and so battery charging)

SeattleYanksFan · Sep 3, 2010

poseidonato said:
I've read plenty of articles saying that the task killers are no longer needed in the new 2.x UI but was more needed in the older ones. The apps if idle should stop draining juice and should just eb regulated by the UI itself.

True, maybe I haven't given it enough time to re-calibrate and realize what the battery life is like but a few of my colleagues said the same thing. Just wondering if there was some settings that were activated that shouldn't have been that I can deactivate.

Thanks pucrepeap.

I know. I was busting your chops. That said, it could very well be possible people are using their phones a lot more the first few days after getting 2.2 to play with it, update apps, etc.

I never used a task killer in 2.1 and, for the most part, had excellent battery life. 2.2 has been no different thus far, although I've only had it for 1.5 days.

I did a factory reset after getting 2.2 myself, so I can't say how it would've been had I not.

ArmlessRifleman · Sep 3, 2010

makewayhomer said:
people would be happy if:

1) Verizon/HTC communicated better re: the timing of the update
and
2) the update worked.

I don't think that is a lot to ask.

I hate to use the A word, but Apple/iPhone handle both of these things far, far better than. You know when you get an update, and when you get it, the software has been QA'd.

I don't see how any rationale person can not view the entire Froyo/DINC experience as a giant ***********. no one knew when it was coming and now 75% of the traffic on this board is figuring out whats wrong with it and how to correct it

It's a lot easier to push an update to one kind of device than many. Apple has one kind of device and that's it, the iPod Touch , iPhone, and iPad all run the same OS on basically the same hardware. If you took IOS and tried to push it out to multiple different devices, like is being done with Android, you would see the exact same issues with Apple. It get's a lot more complicated when the same update has to be applied to phones made buy different manufacturers with completely different hardware. It get's even more complicated when the phone manufacturers all try to make their own "skins" for these updates (SenseUI, Motoblur, etc.) that need to be updated in order to be compatible with Google's original update.

Basically, what I am trying to say is even though Verizon may be the last one with it's hands on the update, I wouldn't say that the issues people are experiencing are all caused by Verizon. I would bet my bottom dollar that the issues stem from a problem with SenseUI compatibility issues. SenseUI is really a piece of garbage in a pretty wrapper, I would trade it in a heartbeat for a fully updated Bluetooth stack (and I have, thank you CM6).

The whole Android experience would be better off without all of these manufacturer additions to Vanilla.

makewayhomer · Sep 3, 2010

ArmlessRifleman said:
The whole Android experience would be better off without all of these manufacturer additions to Vanilla.

agree, this is the last Android custom flavored phone I will ever buy

ArmlessRifleman · Sep 3, 2010

Terabethia said:
You took that awfully personally...

I was speaking in generals. No names mentioned. No one. Hell, I didn't even hint that I was talking about a specific person.

IN FACT, I clearly said "people in general".

I am just saying... for months we have been reading posts whining about not having Froyo yet. Once it was "official", we started having people whining that they have not yet received the OTA even though they knew it was a random roll out over at least 2 weeks.

And now... we have a ton of threads bitching and complaining that 2.2 is the most horrible thing to ever happen to their phone

The only thing that truly bugs me about the OP's post is that it was nothing but slander and whining. No mention of specific problems or any sort of details. He wasn't here asking for help. He just wanted to complain. And then he goes and gives us the ever so typical Apply Fanboy crap of "Apple would never do this to us!!" (conveniently ignoring the hundred times that they HAVE done this exact same thing but on a larger level).

Like just recently when they the iPhone Dev Team "helped" Apple find a major .pdf exploit in their OS but Apple only pushed out the fix to their newer devices. Now all of the users with "outdated" devices get to have fun giving root access of their phone to anyone running a malicious .pdf file on their webpages. Yeah IOS is so much better...

makewayhomer · Sep 3, 2010

makewayhomer said:
went to verizon, guy couldnt help, confirmed my phone was effed, but said they were all effed. he was clueless basically

so, can anyone tell me what I can do now? I have never rooted before, need to downgrade from ota froyo to I can root to a workable rom[

(the problem is that the cpu is screaming causing battery drain and so battery charging)

just want to make sure this doesn't get lost

zemerick · Sep 3, 2010

makewayhomer said:
just want to make sure this doesn't get lost

Theres an entire sub-forum dedicated to this: Incredible - All Things Root - Android Forums

Honestly: I'm not going to recommend. I think you will likely run into more problems there than you have now. You really shouldn't mess around with root unless you are a decently advanced user. Sure, theres one-click apps, and stuff to make things fairly easy...but when something goes wrong ( and it will. The OTA was a one click app to update to Froyo after all... ), you need the extra knowledge to fix it and not totally brick your phone while you have voided your warranty.

I would recommend going through the various means here to trouble shoot your existing problems as things stand and possibly contacting someone at VZ specifically in Tech Support ( not the people in the stores. The actual Tech Support know very little, but they still know more in the stores..and are more likely to set you up with a replacement phone. )

The choice is entirely up to you, and I wanted to give props for moving past the initial anger,etc. and now seeking actual help and trying to get things taken care of! You've already moved past a lot of people who just throw their hands in the air and quit

ArmlessRifleman · Sep 3, 2010

makewayhomer said:
just want to make sure this doesn't get lost

Here you go buddy. Be really freakin' careful.

Can Unrooted OTA FroYo 2.2 be downgraded? - Android Forums

makewayhomer · Sep 3, 2010

ArmlessRifleman said:
Here you go buddy. Be really freakin' careful.

Can Unrooted OTA FroYo 2.2 be downgraded? - Android Forums

tx, but I think those instructions are for people who have already rooted at some point (I have not)

and

This guide was written assuming you have a basic understanding of ADB

since I dont know what ADB stands for, Im assuming that isn't for me

mobiledevice · Sep 3, 2010

be careful with it

read everything a few times before doing any of it

Achuza · Sep 3, 2010

Some of the people here complain that it takes to long for them to get froyo and then when they finally get it they complain it has issues. You must all remember that every phone is a little different. U should at least cut them slack because you can never fully understand what an update will do because like I said before everyone has different setups. So please stop complaining.

ArmlessRifleman · Sep 3, 2010

makewayhomer said:
tx, but I think those instructions are for people who have already rooted at some point (I have not)

and

since I dont know what ADB stands for, Im assuming that isn't for me

This will work if you haven't been rooted and as far as I know this is the only way to roll back at the moment.

ADB is a tool included with the Android SDK that must be downloaded in order to roll back to 2.1 and root. It is basically an application that you run through your windows command prompt (or your linux terminal) to perform actions on your phone.

If you are serious about rolling back in order to root I suggest looking over at least a few ADB tutorials and familiarize yourself with the command prompt.

If you follow these instructions PRECISELY you should be able to roll back without bricking your device. I did it myself just to see if it worked and then worked my way back to running Cyanogenmod6.

zemerick · Sep 3, 2010

makewayhomer said:
tx, but I think those instructions are for people who have already rooted at some point (I have not)

and

since I dont know what ADB stands for, Im assuming that isn't for me

What about Shell, Super User, Daemon, SDK?

If you don't know any of those, then I really REALLY do not recommend you root. Again, I think you could probably get it done...but I also think the issues that you will have in the future and difficulty you will have fixing them would make it worthless...and all of that is assuming you do not brick your phone at some time.

makewayhomer · Sep 3, 2010

tx, but I'm not sure I'm up to all that, I'm not that techy

I just factory reset my phone again. the only thing I have done it set up my google account. installed system panel light. CPU Clock averaging about 650 with the DINC just idling, same problem as before, which is causing huge battery drain, slow charging, etc

this is apparently just the new way that DINC's run with stock froyo

makewayhomer · Sep 3, 2010

zemerick said:
What about Shell, Super User, Daemon, SDK?

If you don't know any of those, then I really REALLY do not recommend you root. Again, I think you could probably get it done...but I also think the issues that you will have in the future and difficulty you will have fixing them would make it worthless...and all of that is assuming you do not brick your phone at some time.

don't know any of them

pucrepeap · Sep 3, 2010

makewayhomer said:
tx, but I'm not sure I'm up to all that, I'm not that techy

I just factory reset my phone again. the only thing I have done it set up my google account. installed system panel light. CPU Clock averaging about 650 with the DINC just idling, same problem as before, which is causing huge battery drain, slow charging, etc

this is apparently just the new way that DINC's run with stock froyo

This is the way YOUR DInc runs with stock froyo. Mine is doing just fine.

mobiledevice · Sep 3, 2010

makewayhomer said:
CPU Clock averaging about 650 with the DINC just idling, same problem as before, which is causing huge battery drain, slow charging, etc

this is apparently just the new way that DINC's run with stock froyo

my cpu is running at only 700 or so on average, and it feels lightning fast

I'm not sure what your problem is

makewayhomer · Sep 3, 2010

pucrepeap said:
This is the way YOUR DInc runs with stock froyo. Mine is doing just fine.

if you say so...guy at verizon told me mine was working the same as everyone he had seen

mobiledevice · Sep 3, 2010

http://androidforums.com/incredible...root-your-incredible-whatever-its-status.html

makewayhomer · Sep 3, 2010

verizon is sending me a new dinc

zemerick · Sep 3, 2010

makewayhomer said:
if you say so...guy at verizon told me mine was working the same as everyone he had seen

and he probably doesn't even see them unless they have a problem to begin with

Anyways, can you give us some details on your battery performance? The apps usage, unplugged, up and awake time, etc. Also, what battery do you have? How have you actually used it? ( Need this to compare against what the phone said is the usage to find something that doesn't line up with normal. )

BTW: The phone uses a 1000 mhz CPU, so 700 is definitely not screaming

Yes, it can get down to around 250, but that is really all the way down to idle.

returning phone due to Froyo

Android Expert

Well-Known Member

poseidonato

Guest

Android Enthusiast

Android Enthusiast

Android Expert

Member

Android Enthusiast

Member

Android Enthusiast

Android Enthusiast

Member

Android Enthusiast

Member

Newbie

Member

Android Enthusiast

Android Enthusiast

Android Enthusiast

Well-Known Member

Member

Android Enthusiast

Member

Android Enthusiast

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads