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

4.0.4 OTA Update

With every OTA release I have seen it breaks down something like this:

1) Google release source.

3) Manufacturer spends about 2-3 months adding skins and or drivers.

4) The Carriers screw with it for a month and find bugs and or add crapware. They send it back to the manufacturer.

5) Manufacture screws with it for a month or two and sends back to carrier.

6) Carrier adds more crapware or removes features and starts OTA rollout.

7) Several major bugs are found immediately by the users/developers and the carrier halts the roll out.

8) Carrier and manufacturer scramble and finally agree to work together and send out a patched version in about two - four weeks....

In the rooted comunity:

1) Google releases source.

2) Developers have a stable working rom in 1-2 weeks. (In many cases 2-3 days)

3) The Beta gets released and users immediately identify bugs.

4) Developers fix in a week or two. (In many cases 2-3 days)

5) Stable rooted Stock and custom ROMS hit the internet and the customer gets the up date about six months ahead of the official OTA update....
 
  • Like
Reactions: aysiu
Upvote 0
With every OTA release I have seen it breaks down something like this:

1) Google release source.

3) Manufacturer spends about 2-3 months adding skins and or drivers.

4) The Carriers screw with it for a month and find bugs and or add crapware. They send it back to the manufacturer.

5) Manufacture screws with it for a month or two and sends back to carrier.

6) Carrier adds more crapware or removes features and starts OTA rollout.

7) Several major bugs are found immediately by the users/developers and the carrier halts the roll out.

8) Carrier and manufacturer scramble and finally agree to work together and send out a patched version in about two - four weeks....

In the rooted comunity:

1) Google releases source.

2) Developers have a stable working rom in 1-2 weeks. (In many cases 2-3 days)

3) The Beta gets released and users immediately identify bugs.

4) Developers fix in a week or two. (In many cases 2-3 days)

5) Stable rooted Stock and custom ROMS hit the internet and the customer gets the up date about six months ahead of the official OTA update....

It would probably be fair to point on the advantage of a Nexus even to those who don't root.

1) Google releases source - get it that day.
 
Upvote 0
5) Stable rooted Stock and custom ROMS hit the internet and the customer gets the up date about six months ahead of the official OTA update....

Perhaps I just had an unlucky run, but I went through over a dozen different ROMs over a period of 15 months with my OG droid. The best ones would FC apps a few times a week, the worse numerous times a day. Never had a ROM I would have called stable.
 
Upvote 0
the 4.0.4 was first had as an OTA by a forum member...he pulled it and gave it to the DEVS.

however i have a feeling we will be seeing 4.0.5 pretty soon.

as for the rezound and Razr having ICS by now.....hahahahaha
not a chance. having owned both the Droid X and the HTC thunderbolt, i am VERY familiar with the OTA process for Moto and HTC. and 9 times out of 10, it is delayed.
on the thunderbolt, we had a stable GB update for a few months before the OTA hit...and they didn't fix the ONE BIG BUG (no notification of voicemails) that the dev community pointed out on day one. Seriously, do they even have beta testers?

i call the Rezound and Razr get ICS in LATE APRIL. Getting Blur and Sense to function properly on a new software is not a simple task.

i am thankful to finally have a Nexus device. even though it has its issues, it is still a TON better than anything from LG,Moto, or HTC
 
Upvote 0
So this has probably been asked and answered many times... For someone who is stock unlocked and rooted 4.0.2, will the OTA come? I have heard you will lose root, and that's no big deal, but will it actually push OTA to rooted devices?
Yes, you should still get OTA. And like you said, you can easily re-root your phone.
 
  • Like
Reactions: dhworph
Upvote 0
Is there any advantage to waiting for the official OTA versus updating manually?

Well, the leaked OTA could possibly not wind up being the official OTA that rolls out. While unlikely, it's possible there are bugs in it that Verizon found and is fixing and decided not to push the OTA yet. Just a possibility, but again probably not likely.
 
  • Like
Reactions: jbdan
Upvote 0
Well, the leaked OTA could possibly not wind up being the official OTA that rolls out. While unlikely, it's possible there are bugs in it that Verizon found and is fixing and decided not to push the OTA yet. Just a possibility, but again probably not likely.

or they are patching the root exploit, or changing the bootloader to prevent us from flashing custom kernels :(

or they are filling it up with bloat.

or they are making sure everything works well for us (doubtful)
 
  • Like
Reactions: vandyman
Upvote 0
or they are patching the root exploit,

Maybe, but irrelevant with a locked bootloader. It only makes it slightly more work to accomplish the same thing.

or changing the bootloader to prevent us from flashing custom kernels :(

No way in hell that happens. But if you're worried about it, unlock your bootloader now ;)

or they are filling it up with bloat.

Doubtful, but with root you can freeze/remove them anyway.

or they are making sure everything works well for us (doubtful)

I think of the things you mention in this thread, this is the most likely.
 
Upvote 0
my bootloader has been unlocked, the day i got the device, and rooted the day i got it, im on 4.0.4 now, and it is most likely the last thing i said about vzw making sure everything works is completely wrong. nothing is ever working completely

and yes root will remove bloat... but some of us found out that some vzw bloat was tied into the actual device, and removing it will cause other problems


never say never with vzw they can do whatever they want, even though its a nexus, and the bootloader is not encrypted, dont think that somehow vzw will find a way around it.


and the patching of the root exploit, yes we can always obtain root, but coming from the DX, some of us knew how much of a pain it was to get root on gb.
 
Upvote 0
t

as for the rezound and Razr having ICS by now.....hahahahaha
not a chance. having owned both the Droid X and the HTC thunderbolt, i am VERY familiar with the OTA process for Moto and HTC. and 9 times out of 10, it is delayed.
on the thunderbolt, we had a stable GB update for a few months before the OTA hit...and they didn't fix the ONE BIG BUG (no notification of voicemails) that the dev community pointed out on day one. Seriously, do they even have beta testers?

i call the Rezound and Razr get ICS in LATE APRIL. Getting Blur and Sense to function properly on a new software is not a simple task.

i am thankful to finally have a Nexus device. even though it has its issues, it is still a TON better than anything from LG,Moto, or HTC

http://www.facebook.com/notes/htc/update-on-android-ice-cream-sandwich-upgrades/10150762287733084

HTC announced today that...

"our first round of ICS upgrades will roll out by the end of March for the HTC Sensation, HTC Sensation 4G and HTC Sensation XE, followed soon there after by the HTC Sensation XL."

Then updated to say...


"In addition, we can confirm Ice Cream Sandwich upgrades will be coming later this year to the HTC Rezound, HTC Vivid, HTC Amaze 4G, HTC EVO 3D, HTC EVO Design 4G, HTC Incredible S, HTC Desire S and HTC Desire HD."

Later this year. Ouch. Not 2nd quarter. Not soon (the HTC Sensation XL got the "soon" label") but later this year.

Watch how long Moto takes to get the Razr updated. No chance the Razr or Rezound see ICS before May 1.
 
Upvote 0
http://www.facebook.com/notes/htc/update-on-android-ice-cream-sandwich-upgrades/10150762287733084

HTC announced today that...

"our first round of ICS upgrades will roll out by the end of March for the HTC Sensation, HTC Sensation 4G and HTC Sensation XE, followed soon there after by the HTC Sensation XL."

Then updated to say...


"In addition, we can confirm Ice Cream Sandwich upgrades will be coming later this year to the HTC Rezound, HTC Vivid, HTC Amaze 4G, HTC EVO 3D, HTC EVO Design 4G, HTC Incredible S, HTC Desire S and HTC Desire HD."

Later this year. Ouch. Not 2nd quarter. Not soon (the HTC Sensation XL got the "soon" label") but later this year.

Watch how long Moto takes to get the Razr updated. No chance the Razr or Rezound see ICS before May 1.


Wow, nothing about the Thunderbolt. Glad my wife told me to get the GNex instead of just replacing my busted up Tbolt!
 
Upvote 0
If you look at the fact there ARE bugs in ICS, and Google hasn't even got those resolved on the GNex yet with a maintenance update, you can imagine that ICS is a lot more difficult to integrate on a phone that the OS wasn't developed in partnership with, that has a proprietary skin, and carrier bloat, and considering Google basically admitted by pulling the "supported" title from the VZW GNex that CDMA adds an extra layer of difficulty to the mix, it all means its going to take a while. I personally think three months would be pretty impressive for a VZW phone to get ICS.
 
Upvote 0
If you look at the fact there ARE bugs in ICS, and Google hasn't even got those resolved on the GNex yet with a maintenance update, you can imagine that ICS is a lot more difficult to integrate on a phone that the OS wasn't developed in partnership with, that has a proprietary skin, and carrier bloat, and considering Google basically admitted by pulling the "supported" title from the VZW GNex that CDMA adds an extra layer of difficulty to the mix, it all means its going to take a while. I personally think three months would be pretty impressive for a VZW phone to get ICS.

There are always going to be bugs though. Most of the custom roms are solid and people mainly have issues with kernels. it should not take manufacturers that long to get out a stable rom. Obviously the main reason for the delay is integration of their bloat. On the droid x even with the later builds like .602 and .605 some people were screaming that motorola sucks, the droid x sucks, etc. because they still had issues. There will always be people with issues, but 4.0.3 is stable.
 
Upvote 0
Wow! I haven't heard of this. Could you expand on this, please? (Or maybe just point me to the thread where it was discussed then we can avoid derailing this one.)

rich i know you had the DX... or i saw you in the DX section every now and then

but i dont remember froyo

i remember gingerbread had this, the rom devs figured it out finally but
here is the link:
http://androidforums.com/droid-x-al...emove-gingerbread-gingerblur.html#post2576788

in particular you have some vzw bloat that can be removed(if not all)
motorola bloat however was tied into the os (obviously) i made that mistake in my previous post and i apologize.
in reference:
Safe to remove:

amazonmp3_1.8.32_signed_zipligned.apk
BackupAssistanceClient.apk
Blockbuster.apk
blur_facebook.apk [Social networking integration]
blur_flickr.apk [Social networking integration]
blur_lastfm.apk [Social networking integration]
blur_linkedin.apk [Social networking integration]
blur_myspace.apk [Social networking integration]
blur_orkut.apk [Social networking integration]
blur_photobucket.apk [Social networking integration]
blur_picasa.apk [Social networking integration]
blur_skyrock.apk [Social networking integration]
blur_twitter.apk [Social networking integration]
blur_youtube.apk [Social networking integration]
BlurAlarmClock.apk
BlurCamera.apk [Stock camera]
BlurEmail.apk
BlurEmailEngine.apk [Used by stock messaging app and when adding calendar events]
BlurHome.apk [You lose the new app drawer if you remove this]
BlurUpdater_VZW.apk
BooksPhone.apk [Google Books]
Browser.apk
BuaContactAdapter.apk [Used for Backup Assistant restoring contacts]
Calculator.apk
CarDock.apk
CityID.apk
ClockWidget.apk
Cmas.apk [Emergency app]
ContactsProvider2_0.apk [Used if you have a Google Apps account]
Conversations.apk [Stock texting app; if removed, 3rd party SMS works, MMS does not]
DLNA.apk
DlnaSystemService.apk
Dock.apk
DockService.apk
FileManager.apk
FMRadioService.apk
FriendFeed.apk
Gmail.apk
GoogleQuickSearchBox.apk [Prevents you from using the global search]
HelpCenter.apk
HomeSyncWizard.apk
Kindle-OEM-2.0.5.103970165-20110202.apk
KpiLogger.apk [Unknown]
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
Maps.apk [Google Maps]
MediaGallery.apk [Shortcut to recently-shot pictures in the Camera app stops working]
MessagesWidget.apk
Messaging.apk [Unknown; if removed, stock texting app still works, 3rd party MMS/SMS works]
MotoFMRadio.apk
MSExchangeService.apk [Remove ONLY if you use POP/IMAP email]
Music.apk
MyVerizon.apk
NewsWidget.apk
PhotoWidget.apk
Protips.apk [The little Android guy that gives hints]
QuickContactWidget.apk
Quickoffice.apk
QuickSms.apk [Removes ability to auto-respond via text to declined calls]
Skype_mobile.live.apk
SocialMessaging.apk
SocialShare.apk [Unknown]
StatusWidget.apk
StickyNoteWidget.apk
Street.apk
Swype.apk
Talk.apk [Google Talk]
ToggleWidgets.apk
UniversalInbox.apk
VCast.apk
VoiceSearch.apk [If removed, speech-to-text is also disabled]
VpnClient.apk
VpnServices.apk
VSuiteApp.apk [Voice Commands app; causes multiple FCs when deleting it, must reboot after]
Vvm.apk [Visual Voicemail]
vzw_vnav_DROIDX_rel_PROD_signed.apk [VZW Navigation]
VZWInstaller.apk [Unknown]

WeatherWidget.apk
WorkContacts.apk [Used if you use the Corporate Sync]
YahooContacts.apk
YouTube.apk


and obviously the others:
Unsafe/unknown:

AccountAndSyncSettings.apk
AdminFeedNotifier.apk
AdService.apk
android-syncservice-app.apk
ApplicationsProvider.apk
ArcPhotoworkshop.apk [Used to crop wallpapers or resize images]
ArcVideoEditorLite.apk
AtCmd.apk
AudioEffectSettings.apk
BatteryManager.apk
BatteryReport.apk
Bluetooth.apk
BluetoothMot.apk
blur_activesync.apk [Removal causes Contacts to crash]
blur_email.apk [Removal causes Contacts to crash]
blur_yahoo.apk [Removal causes Contacts to crash]
BlurCalendar.apk
BlurCalendarProvider.apk
BlurChooser.apk
BlurContacts.apk
BlurContactsSync.apk
BlurDialer.apk
BlurPhone.apk
blur-services.apk
BlurSNMessagingEngine.apk
CalendarSync.apk
CertificateManager.apk
CertificateProvider.apk
CertInstaller.apk
ChargeOnlyMode.apk
CompassCalibrate.apk
ConnMO.apk
ContactsData.apk
DataCollection.apk
DataCollectorProvider.apk
DataCollectorService.apk
DatamanagerApp.apk
DataManagerService.apk
DefaultContainerService.apk
DeviceStatistics.apk
DMService.apk
DownloadProvider.apk [Causes force closes in the Market app if removed]
DownloadProviderUi.apk [Causes force closes in the Market app if removed]
DrmProvider.apk
DroidEye.apk
EncryptionSettings.apk
ExtDispService.apk
FirewallService.apk
GlobalUnplug.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GooglePartnerSetup.apk
GoogleServicesFramework.apk
HTMLViewer.apk
IndexingService.apk
LatinIME.apk [Default keyboard]
LocationConsent.apk
LocationProxyDmPlugin.apk
MarketUpdater.apk
MasterClearErrorReport.apk
MediaProvider.apk
MediaSync.apk
MediaUploader.apk
MotHstcmd.apk
MotoAtCmdPlugin.apk
MotorolaSettingsProvider.apk
MotoVzwAtCmdPlugin.apk
NetworkLocation.apk
oma1motService.apk
OMADownload.apk
OMAProvisioning.apk
OverlaySettingsProvider.apk
PackageInstaller.apk
PhoneAddons.apk
PhoneConfig.apk
PicoTts.apk [Text-to-speech]
PNI-Moto.apk
PolicyMgrProvider.apk
PolicyMgrService.apk
Preloaded.apk
ProgramMenu.apk
ProgramMenuSystem.apk
RichTextCommon.apk
Settings.apk [This APK stores the 3G Hotspot App now, so you can't remove the hotspot]
Setup.apk
SetupProvider.apk
SetupSettings.apk
SetupWizard.apk
SoundRecorder.apk
SpellingCheckService.apk
StorageMonitorService.apk
SuggestionsProvider.apk
SuggestionsRuleCheckerCore.apk
SuggestionsServiceScheduler.apk
SystemUI.apk
TelephonyProvider.apk
Term.apk
TtsService.apk [Text-to-speech]
Upgrader.apk
Usb.apk
UserDictionaryProvider.apk
Vending.apk
VideoPlayer.apk
VisualizationWallpapers.apk
VoiceReadoutService.apk
WmdrmDla.apk
WmdrmWebpush.apk
ZoomService.apk


i bolded the vzw apps, i do believe the blockbuster app was added by verizon, but i could be wrong.

this list was put together by binary, and as most of you know is quite intelligent when it comes to these kinds of things.

and just to make it clear, i do not worry about bloat, my nexus is on the stock 4.0.4 rom, and i havent disabled the vzw bloat, will i? nah, not harming me, but when i go to a rom, i do not expect it to be there.

bloat doesnt harm the os, just doesnt benefit me from having it there. :p
 
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