I thought I would post some clarification about the 2.1 OTA update, since there is a shockingly large amount of misinformation being spread throughout the community. If you are running DroidMod, you should accept the 2.1 update. The phone will reboot in to recovery, and SPRecovery will block the update outright. Even if you are not running SPRecovery, there’s really nothing to worry about, because the pre-install checks internal to the update will fail, and the update will not be applied anyways.
Many people have been renaming otacerts.zip to stop the notification from appearing, so I’d like to address that. Renaming otacerts.zip will indeed stop the notifications from being presented to you, but it does so by breaking the updater mechanism in a way that makes it think that the update file is corrupt. This will cause it to re-download the update file indefinitely, which will severely impact your battery life. This is why we didn’t remove the file from the ROM entirely.
So, to put it simply, if you are running any non-stock ROM at all, you can safely “accept” the 2.1 update to stop the notifications; the update will not be able to patch the modified system files, and will not make any changes to your phone.
Anyone familiar with this that can confirm?
__________________
HTC Thunderbolt - Stock... for now
The Following User Says Thank You to BigMace23 For This Useful Post:
I thought I would post some clarification about the 2.1 OTA update, since there is a shockingly large amount of misinformation being spread throughout the community. If you are running DroidMod, you should accept the 2.1 update. The phone will reboot in to recovery, and SPRecovery will block the update outright. Even if you are not running SPRecovery, there’s really nothing to worry about, because the pre-install checks internal to the update will fail, and the update will not be applied anyways.
Many people have been renaming otacerts.zip to stop the notification from appearing, so I’d like to address that. Renaming otacerts.zip will indeed stop the notifications from being presented to you, but it does so by breaking the updater mechanism in a way that makes it think that the update file is corrupt. This will cause it to re-download the update file indefinitely, which will severely impact your battery life. This is why we didn’t remove the file from the ROM entirely.
So, to put it simply, if you are running any non-stock ROM at all, you can safely “accept” the 2.1 update to stop the notifications; the update will not be able to patch the modified system files, and will not make any changes to your phone.
Anyone familiar with this that can confirm?
If this is accurate it should (if people bother to read it) stop all the conjecture, panic and craziness that has been posted. Nice find!
__________________
____________________________
Neil
Currently hooked on GB (rooted, overclocked and deoxed). Tomorrow, who knows
If this is accurate it should (if people bother to read it) stop all the conjecture, panic and craziness that has been posted. Nice find!
Yea I might have to rename that file back to otacerts.zip and just accept it when I get it I guess. I'm interested to see if this can be confirmed, because I would think the official update would overwrite some but not all files and cause problems.
I thought I would post some clarification about the 2.1 OTA update, since there is a shockingly large amount of misinformation being spread throughout the community. If you are running DroidMod, you should accept the 2.1 update. The phone will reboot in to recovery, and SPRecovery will block the update outright. Even if you are not running SPRecovery, there’s really nothing to worry about, because the pre-install checks internal to the update will fail, and the update will not be applied anyways.
Many people have been renaming otacerts.zip to stop the notification from appearing, so I’d like to address that. Renaming otacerts.zip will indeed stop the notifications from being presented to you, but it does so by breaking the updater mechanism in a way that makes it think that the update file is corrupt. This will cause it to re-download the update file indefinitely, which will severely impact your battery life. This is why we didn’t remove the file from the ROM entirely.
So, to put it simply, if you are running any non-stock ROM at all, you can safely “accept” the 2.1 update to stop the notifications; the update will not be able to patch the modified system files, and will not make any changes to your phone.
Anyone familiar with this that can confirm?
Seems odd...how can anything be downloaded unless you see and accept the update?
My understanding of the process is that you receive the notification, and if you accept it, the file is downloaded.
If you don't see an update notification and/or don't accept it, nothing is downloaded. If nothing is downloaded, there's no re-download loop to get into, and no battery issue.
What am I missing here? I've never received any update notification (rooted before 2.01) and have never seen any issue like above that I'm aware of...
Running Droidmod and was getting the ota update constantly. Read that on the dm site, accepted the update, and no more bothersome update notifications.
Running Droidmod and was getting the ota update constantly. Read that on the dm site, accepted the update, and no more bothersome update notifications.
You mean the notification was appearing repeatedly, not that the download was occurring repeatedly, right?
I think it is more like your phone will keep checking for the update or something to that effect. But yea it will drain your battery.
__________________ So I'm guessin' there's questions that need addressin' like how he fresh in the adolescence and wreckin em' Rules & Guidelines, Zero Tolerance Policy.
Seems odd...how can anything be downloaded unless you see and accept the update?
My understanding of the process is that you receive the notification, and if you accept it, the file is downloaded.
If you don't see an update notification and/or don't accept it, nothing is downloaded. If nothing is downloaded, there's no re-download loop to get into, and no battery issue.
What am I missing here? I've never received any update notification (rooted before 2.01) and have never seen any issue like above that I'm aware of...
Incorrect, the update actually downloads itself to your SD Card before it notifies you of an available update, once it is on the card it notifies you and you can apply it.
Incorrect, the update actually downloads itself to your SD Card before it notifies you of an available update, once it is on the card it notifies you and you can apply it.
Thanks...
I'm on Koush's cyanogenmod ROM 5.0.5.7, and it does include otacerts.zip (in system>etc>security). Have to check in his forums to see if there's been any discussion on this issue w/his ROMs.
I've never seen any update prompts for 2.1 or 2.01 (was likely on Bugless Beast back when 2.01 was being released).
Incorrect, the update actually downloads itself to your SD Card before it notifies you of an available update, once it is on the card it notifies you and you can apply it.
If the update gets downloaded to the SD card first, couldn't we just remove the update from the SD card? The notifications should then dissappear once removed from the SD card wouldn't it? Just a guess
okai im on BB0.9.
No update notifications but the update is there waiting for me to download ( under System Updates ).
So just download it and I'll be fine?
No you weren't. We didn't root the Droid until the day 2.0.1 was released OTA and Bugless Beast followed maybe 3 weeks to a month after.
Had to laugh (at myself!) after seeing your post...DUH!!
That's right, of course...I applied the 2.01 update manually as soon as it was posted after the 2.01 OTA started. Boy, time flies, that seems like years ago now...
I'm on Koush's cyanogenmod ROM 5.0.5.7, and it does include otacerts.zip (in system>etc>security). Have to check in his forums to see if there's been any discussion on this issue w/his ROMs.
I've never seen any update prompts for 2.1 or 2.01 (was likely on Bugless Beast back when 2.01 was being released).
Did you ever find anything? Cause there is no Settings>About>System Update option anymore, apparently Cyanogen or Koush removed it.
__________________
Current phone: Droid Charge @ 1200MHz. ROM jumping, waiting for CM to arrive!
Quote:
Originally Posted by UBRocked
Just put your phone in airplane mode and tell him you loaded an iPhone 4 simulator on your Droid.
Did you ever find anything? Cause there is no Settings>About>System Update option anymore, apparently Cyanogen or Koush removed it.
Nope...kind of forgot about this. I have the otacerts.zip file on my Droid, so I'm assuming that will avoid any of the issues related to it not being there, or being renamed.
I haven't got a notification that a update is available, but if i go into settings and check for updates it is there ready to download. Yesterday i went from bb 0.7 with stock kernel to bb 0.9 with adamz LV 800 mhz kernel. today my battery drained way to fast. The first time i took it out of my pocket was 5 hours after i unplugged it and it was at 70%. I used it for maybe 20 to 30 minutes at work surfing the web and it was at 40% when i got home. But when i used it to listen to pandora for an hour after work the battery might have went down 10%. Maybe it was constantly trying to download the file when the phone was idle.
I haven't got a notification that a update is available, but if i go into settings and check for updates it is there ready to download. Yesterday i went from bb 0.7 with stock kernel to bb 0.9 with adamz LV 800 mhz kernel. today my battery drained way to fast. The first time i took it out of my pocket was 5 hours after i unplugged it and it was at 70%. I used it for maybe 20 to 30 minutes at work surfing the web and it was at 40% when i got home. But when i used it to listen to pandora for an hour after work the battery might have went down 10%. Maybe it was constantly trying to download the file when the phone was idle.
I've noticed significantly worse battery life myself lately as well. Just checked and the update is there, but I'm never prompted to download it. (Running BB.9). Curious if there is any truth to what you're saying there?
I've noticed significantly worse battery life myself lately as well. Just checked and the update is there, but I'm never prompted to download it. (Running BB.9). Curious if there is any truth to what you're saying there?
I've noticed VERY bad battery life with my Droid as well (Running BB.8). I have a feeling all Pete did was rename so its constantly draining out batteries. I guess I will be updating to Cygeno soon.
I've noticed significantly worse battery life myself lately as well. Just checked and the update is there, but I'm never prompted to download it. (Running BB.9). Curious if there is any truth to what you're saying there?
i dont think its just BB, im running a desireremix rom and i checked and the update is there also. my battery life was really good about a week ago, and it seems ever since the update is ready for me to download, my battery life is draining really fast as well.
is there someone out there who can address this issue? do i just accept the download or what is the best way to proceed?
Device(s): Motorola Droid
CyanogenMod-5.0.5.7
OC'ed to 1.1Ghz
Carrier: Not Provided
Thanks: 1
Thanked 0 Times in 0 Posts
ive also noticed significant battery loss...im on cyanogenmod 5.0.5.7 so theres no option for it in About Phone but i searched for it and its on my sd card? is there something i can do to get rid of it? can i just delete it? id like the better battery life back...
I think there is some confusion here - let me share my experience and see if it helps. I have been running DroidMod, was getting the prompt to update so found the instructions to rename the otacerts.zip, did that and updates stopped but battery life did seem to suffer. So I followed the instructions to reverse the renaming, accept the update and yes it does not actually update your phone, fails on reboot like it should. Everything is happy now. Hopefully somewhat helpful!
i fixed the update problem so in my about phone it says "system is currently up to date" but my battery life is still worse than what it used to be. DARN i dont know what is sucking all my power away. i swear my personal usage of the phone has not changed one bit, but battery life has decreased a noticeable amount!
otacerts.zip.bak will drain battery life?
