All Note 4 users on Verizon are asking the same question I am. When will we get Marshmallow? It's been a while and I was hoping to get some insight as to when this will be. I am desperately seeking this update. Any ETA when?

Getting the newest update is always exciting. While we don't have an exact date, you can always keep up to date here http://vz.to/1PABezYJosephT_VZWFollow us on Twitter @VZWSupportIf my response answered your question please click the 'Correct Answer' but...

Your answer was not really useful at all. The link tells me I received my last update on 02/05/16. I already know I have that 1. The question is when is Verizon going to release 6.0 to us? Quite making excuses and give us a date for release.

Verizon isn't always last is the problem. Like Ann she linked above. Some people finished faster than others. Carriers don't touch the code. They give the stuff in advanced to manufacturers and then the manufacturers incorporate the new things into their base rom. When they are finished they submit it for testing. Pass it is pushed out. Failed it goes back to the manufacturer for fixing. Manufacturers love this deal. Carriers get blamed for delays. Manufacturers get more money due to these options which allows them to sell less product to break a profit quicker. Apple products for example make no such deals as to partly why iphones are more expensive. Doesn't also include the fact Apple has physical stores, physical employees, and inventory at these stores.

That's why updates around the world doesn't happen at the same time. Look at Canada, Australia, and each US carrier. Even Some Asian countries. It's not so uniformed like Apple. Don't let Apple trick you either. Carriers are part of ADC as part of Apples agreement with them. Carriers must test and certify using ADC. Apple finishes updates at different times, but doesn't push updates until all their devices are finished to give the illusion of timeliness.

Here's something to back up what manufacturers said and you can check it out yourself. Say Sprint pushed the update first. Then 2 weeks later you get soak test. It fails and go back to Samsung and then a week later you get an update. Now if they were the same build shouldn't Sprint be getting that update? Manufacturers have different teams and different build based on the number of agreements they made and they do not finish at the same time nor do they have the same builds.

sublimetalmsg wrote: I have been wondering the same thing. Most of my friends have their update on other carriers so i googled and apparently Verizon slowest at updates in the world. Which is a huge bummer to me since i like everything up to date. I wonder how many customers switch for this reason alone. Verizon Wireless isn't always the slowest to release updates. The Note 4 actually got an update recently in February. Since this update wasn't Marshmallow, one could conclude that the Samsung team working on the update hadn't started on the Marshmallow update yet. An example of VZW not being last is Note 5 T-Mobile Galaxy Note 5 And S6 Edge+ Receive Android 6.0 Marshmallow OTA Updates which saw the Marshmallow update on the Verizon model second after Sprint with T-Mobile after the Verizon model. AT&T is still waiting for their update.

I agree. I asked the same question on Facebook yesterday, and they posted the same [removal required by the Verizon Wireless Terms of Service] link.ANSWER THE [removed] QUESTION.

This was meant for the Verizon response earlier. LOL

Here's what I mean by proprietary and why it is ASL and not GPLThis is the reason why Google does testing prior to release. They want to test all their apps work, and that they comply with the licensing agreement so they can keep their proprietary apps on the device. Yes this is ONE of the reasons Google is in trouble in Europe as they see it as Anti-competitive.http://www.cyanogenmod.org/blog/the-current-stateKey notes listedThis also means that big companies likes Google, HTC, Motorola, and whomever else can add their own pieces to it and share these pieces under whatever license they choose.The issue that’s raised is the redistribution of Google’s proprietary applications like Maps, GTalk, Market, and YouTube. These are not part of the open source project and are only part of “Google Experience” devices. They are Google’s intellectual property and I intend to respect thatThese you can download and use but they are proprietary, and you can't reverse engineer or modify them without chance of litigationRunning Builds | Android Open Source ProjectDownloading proprietary binariesYou can download official binaries for the supported devices running tagged AOSP release branches fromGoogle's Nexus driver page. These binaries add access to additional hardware capabilities with non-open source code. To instead build the AOSP master branch, use the Binaries Preview for Nexus Devices. When building the master branch for a device, use the binaries for the most recent numbered release or with the most recent date.

JohnC118 wrote: "Some people finished faster than others. Carriers don't touch the code. They give the stuff in advanced to manufacturers and then the manufacturers incorporate the new things into their base rom. When they are finished they submit it for testing. Pass it is pushed out. Failed it goes back to the manufacturer for fixing." You have that so wrong its laughable. Google makes the code.. releases it to the manufacturer, the manufacturer will test to make sure it works on their devices.. the manufacturer then releases it to the carriers. The manufacturer doesn't make individual builds for different carriers, that's up to the carrier to incorporate their bloatware. The carrier doesn't send its added bloatware to Samsung for them to test, that's hysterical. Verizon it last on updates 99% of the time because they can. They have by far the largest most reliable network and therefore the most customers so that is their leverage to get away with it. They most likely want to wait and see what issues the other carriers have before having their customer support dealing with things. They basically don't care what customers think about waiting for updates. Do you really want to go into this?http://www.htc.com/us/go/htc-software-updates/Just one of the many MANUFACTURERS who says YOU ARE WRONG.If you look at it in short just look at step 7 and step 8... especially step 8 where is says"HTC Incorporates carrier modifications into code"Do you THINK manufacturers would give multiple carriers around the world their proprietary code and ALLOW them the modify it? Name one manufacturer that has. If you bring Google up... Even they protect their proprietary code, and yes Android is Open Source... To a point... You can keep your code proprietary. Android isn't GPL for that very reason.FYI Sony, Motorola, and HTC showed their update process, and they are so similar the only difference is the names of each process. So I don't see how LG, and Samsung would do something drastically different when they are more protective of their code than any other company. There's a lot of people on the open source community will tell you this.So laugh all you want because... You and a lot of people are wrong, and the manufacturers have said you are, and show you the proof which people have ignored for the past 3 years. Shows how ignorant and childish you are.

Re: When will the Marshmallow update be released for the Note 4?

Accessibility Resource Center

end of navigation menu

Ask a question

3.2M Members 5,752 Members online 269K Discussions 43.9K Solutions

An Accepted Solution is available for this post.

Again.. Baloney reply.. Stop the lies and canned replies..

Add thoughts to the community

Start a new topic or ask questions in the open forum.

New conversation
Make a suggestion
Just for fun

Discussions

Mobile

5G / LTE Home Internet

Fios

Accessories

Entertainment

Level Up

Help

Tutorials

Archives

Add thoughts to the community

Browse discussions within categories