Related
I just got off the phone with VZW. Apparently, they've stopped rolling out the OTA because of "software issues," though he didn't specify beyond that. So, for all of you who have been waiting for the OTA over the past few days, off the top of his head, the tech guesstimated it'll be around a month before they begin rolling it out again. Lame.
Edit: You can still install the .217 leak...but if the update has been pulled for software issues, that obviously means .217 is no longer the official OTA.
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
alex94kumar said:
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
Click to expand...
Click to collapse
Yeah, I've been mashing the "systems update" option habitually now for a couple days, but also avoided just manually updating to the .217 leak for this very reason. Either way, it is kind of disappointing.
honestly, if I were you, I would jump on either the 217 leak, or if you want a custom rom that's slightly themed and has extra features/no bloat, go with Eclipse
It wasn't supposed to be released for the general OTA, they did that on accident, only people who were signed up for the motorola feedback network test were supposed to get it, but for some reason they pushed it to all devices. It should be officially pushed in a week or so, because it appears the soak test isn't showing up any major issues.
Sent from my DROID4 using xda premium
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Rafterman414 said:
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Click to expand...
Click to collapse
As mentioned above, there was no planned general release yet. Moto did a release for "a few thousand" phones, of which only a small portion are official MFN soak testers. The test will end soon, and it looks like no show-stopper issues have been found, so, if things go as usual, the general release will roll out, probably in groups, over the next several days.
Sounds like the OP spoke to someone in VZ who really didn't know why the release wasn't available and made something up. (And I bet you never thought a VzW rep would do that!)
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
highlandsun said:
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
Click to expand...
Click to collapse
When your in at the dialer screen just push menu then search it goes to your contact list. So its a matter of hitting 2 buttons but you can get to it from dialer. I also miss the other way but im getting used to this and it doesnt bother me anymore
Sent from my DROID4 using xda premium
It's happened to me twice now in the last two days that I was unable to hear the people calling me. Switching to speaker mode or rebooting the phone fixed this. Actually only rebooting. Alternating between speaker and normal mode is just a temporary fix as long as I'm in speaker mode. Plug in the headset and it works. Take it out en again no sound... I think it happens after I use BT.
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Lum_UK said:
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Click to expand...
Click to collapse
Well, we can certainly dream, but given a choice between unlocking the bootloader and shrugging apologetically and insisting nothing can be done, I'm dead sure Verizon will require Motorola to do the latter. :crying:
Installing OTA right now on my wife's D4
Sent from my DROID BIONIC using xda premium
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Rafterman414 said:
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
tcrews said:
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
Click to expand...
Click to collapse
If you had a nickel for every time you had to tell somebody that you could probably retire! LOL
Droid 4 - AOKP K1L0
Update fails anyway
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this? I pressed the volume up button and it says:
Verifying current system...
assert failed: apply_patch_check("/system/app/music2.apk", "cbb199983ab1cb9beee6b20ec4db659ccd49d757", "25d8789a15715fdd931ef2a2ee93b637bfef06b0")
E:Error in /cache/Blur_Version 6.13.219.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.
Saloobian said:
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this?
Click to expand...
Click to collapse
Just install from a PC via FastBoot.
ROM: http://sbf.droid-developers.org/cdma_maserati/list.php
Instructions: http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
Note. Do not download one of the two ROMs that post suggests, use the 217 ROM from my link above. Do not attempt to downgrade via this method either, it will not work. You might also want to skip steps 6-9 if you don't want to reset your data. Not sure how well this will work after an upgrade.
The soak test is over and "the software is officially released and will be rolling out in stages"....
Sent from my DROID4
:good:
Fantastic! I restored to stock and downloaded the update again, and it's currently installing without a hitch! Thanks!
The last debug build that was released (As far as I am aware).
WARNING: This is be a full debug version and logs everything. I am scripting up a way to disable debug logs and remove the developer crap. Will not upload until I have that, you don't want this if it's all on, it's barely useable and I dont' want this on since it can be traced back to the origin.
Build= userdebug-4.0.4-7.7.1Q-144_SMQ_S1-25-27-test-keys-Verizon-US
Version also released to devs: userdebug-4.0.4-7.7.1Q-144_SMQ_S1-30-32-test-keys-Verizon-US
Full RSDLite flash version is COMING SOON. PM me if you want a crack at the files before I drop them or want to help me strip these down, I need to remove the developer ID code so that the "originator" is not identifiable.
I can strip the specific .IMG files out - Has unlocked bootloader.
TBH has some considerable experience with test keys builds for other Motorola devices and we would love a chance to take a look at these files.
We also have a number of OTA updates for various test keys builds that we cant use unless we have a full XML zip build to start from.
I am still waiting for my dev edition M to be shipped by Motorola. It was supposed to arrive today but has been delayed till the 24th for unknown reasons.
cellzealot said:
TBH has some considerable experience with test keys builds for other Motorola devices and we would love a chance to take a look at these files.
We also have a number of OTA updates for various test keys builds that we cant use unless we have a full XML zip build to start from.
I am still waiting for my dev edition M to be shipped by Motorola. It was supposed to arrive today but has been delayed till the 24th for unknown reasons.
Click to expand...
Click to collapse
PM me an e-mail address and I will send you a login to access the files on the condition that they are not to be released until we can confirm the ID is not being included.
PM sent thank you.
I am still waiting for my dev edition M to be shipped by Motorola. It was supposed to arrive today but has been delayed till the 24th for unknown reasons.
Click to expand...
Click to collapse
Are you positive that its actually going to be released? I thought There has to be a massive call for it? reason I say that is because I talked to a verizon rep today and he was straight up with me. I'm from rochester NY and he told me he wasn't even sure if it'll happen. I just went ahead and bought it anyways. I'm loving it right now. But please enlighten me!
Sent from my XT907 using Tapatalk 2
jarzy00 said:
Are you positive that its actually going to be released? I thought There has to be a massive call for it? reason I say that is because I talked to a verizon rep today and he was straight up with me. I'm from rochester NY and he told me he wasn't even sure if it'll happen. I just went ahead and bought it anyways. I'm loving it right now. But please enlighten me!
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Of course its going to be released its been purchasable for almost a week they are just having issues shipping so it got delayed a week. You should return it ASAP if you want an unlocked bootloader.
mattlgroff said:
Of course its going to be released its been purchasable for almost a week they are just having issues shipping so it got delayed a week. You should return it ASAP if you want an unlocked bootloader.
Click to expand...
Click to collapse
I Know my bad I read deeper into it after posting this sorry. But for $550 and no contract? You can be my guest lol. Plenty of phones have done well without an unlocked boot loader. Even if root cannot be accomplished for a while, I'm almost positive were gonna get cm10 soon its just a matter of time. I'm happy with the phone as is anyway. I guess time will tell.
Sent from my XT907 using Tapatalk 2
PM sent also, two days ago...source is out now.
interloper said:
PM sent also, two days ago...source is out now.
Click to expand...
Click to collapse
Developers familiar with the Moto Builds are using the files. Since it's pre-release files don't expect miracles but they might help them to understand a few things. It's a small step but a step nontheless.
interloper said:
PM sent also, two days ago...source is out now.
Click to expand...
Click to collapse
So now that the dev edition is out and the international/unlocked edition is beginning to ship, any suggestions on where we can get source and/or stock images/SBFs?
dew.man said:
So now that the dev edition is out and the international/unlocked edition is beginning to ship, any suggestions on where we can get source and/or stock images/SBFs?
Click to expand...
Click to collapse
I have the fastboot xml. See attached file.
kent_lkc said:
I have the fastboot xml. See attached file.
Click to expand...
Click to collapse
Are you planning on releasing them?
..........
Are you planning on releasing them?
Hi guys. I did something a little dumb. I was on a marching band trip, and on the bus ride, I thought, "Oh, while I'm in the middle of no where, why don't I OTA to Jelly Bean? That'll give me something to do." So I figure out PCA and get it all set up, and when I reboot and check for updates it says Heck yeah theres an update. So I select to do it over 4G, thinking sweet, I don't even need wifi.
Well, it doesn't ever download, because it wants to wait for non peak hours. Sure, thats fine, I can wait till I get home I guess.
When I get home, it connects to wifi and sits there. It doesn't do anything. Its not even peak hours, might I add, its like, 2 in the morning. Me being a very impatient person, I think "Im sure rebooting will fix this" (because you know, when your semi legit phone hacks dont work its a great idea to kill power). When I turn it back on the notification is gone. I go back to Check for Updates and it tells me Currently downloading update.
Well, I go to bed, it sits on the plug all night supposedly downloading this update, but when I wake up, nothings happened, and it still says Downloading update. Keep reading, it gets worse.
I think to myself, Oh snap, I messed it up by rebooting. Whatever, I'll just run PCA again, factory reset, and check again. So I do that, and when it finally settles down I check for updates and it straight up says "Check for update is not available at this time. Try again later."
And that's it. No matter what I do, I can't get off this message. Does anyone have any idea what I can do?
Thanks,
Peter.
The update was taken down after just a couple of hours. A link to it is in the cheesecake thread.
Sent from my Atrix HD MAXX 4.1
It could have been deleted from the server while you were reaching home. You can go to general section and there's a thread title "cheesecake". Someone has shared the zip which you can easily apply it via stock recovery.
Sent from my MB886 using Tapatalk 2
deeje00 said:
The update was taken down after just a couple of hours. A link to it is in the cheesecake thread.
Sent from my Atrix HD MAXX 4.1
Click to expand...
Click to collapse
Aw dude bummer! But thanks for the reply. Any idea why it would say there was an update?
That I do not know. But no bummer just download the zip from cheesecake.
Sent from my Atrix HD MAXX 4.1
ripin150 said:
Aw dude bummer! But thanks for the reply. Any idea why it would say there was an update?
Click to expand...
Click to collapse
Because there was one. It was taken off of the server, though. You can find it in the Cheesecake thread in general but it's not completely finished. There are some small bugs and other missing things but it's nice to have if you know how to do it.
Anyone else still stuck on 4.4?
I have decided not to root my phone or flash any rom that has not been directly issued to my phone by Google. I'm still too happy with my device to mess around with that.
Therefore, I decided to create a thread for the people who are still using 4.4 because they haven't got the update yet. I'm in Malta... Anyone else?
What's better than the mutual anticipation for something new, right?
Sidenote: will the update fix Google Now not working on some devices?
Owner of a Nexus 5
Sent from my iPad using Tapatalk
iwillthinkofsomething said:
Anyone else still stuck on 4.4?
I have decided not to root my phone or flash any rom that has not been directly issued to my phone by Google. I'm still too happy with my device to mess around with that.
Click to expand...
Click to collapse
I think you should at least consider rooting, the benefits of that are countless. I just re-wiped my phone to stock+root so I can just sideload the 4.4.2 update.
Why not sideload it?
Sent from my Nexus 5
ohthesepaws said:
I think you should at least consider rooting, the benefits of that are countless. I just re-wiped my phone to stock+root so I can just sideload the 4.4.2 update.
Click to expand...
Click to collapse
dicecuber said:
Why not sideload it?
Sent from my Nexus 5
Click to expand...
Click to collapse
My laptop is not available at the moment. I am getting it repaired.
Owner of a Nexus 5
Sent from my iPad using Tapatalk
ohthesepaws said:
I think you should at least consider rooting, the benefits of that are countless. I just re-wiped my phone to stock+root so I can just sideload the 4.4.2 update.
Click to expand...
Click to collapse
I am also using 4.4 stock + root. Do u know how to update to 4.4.2?
koolthing said:
I am also using 4.4 stock + root. Do u know how to update to 4.4.2?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2557523
iwillthinkofsomething said:
My laptop is not available at the moment. I am getting it repaired.
Owner of a Nexus 5
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Then just wait. Like 2 weeks for Google to roll out the updates. No point in this thread
Sent from my Nexus 5
I'm still on 4.4 too. I heard you can install it without rooting though.
Badd_blood said:
I'm still on 4.4 too. I heard you can install it without rooting though.
Click to expand...
Click to collapse
you need adb. that's all.
I am also waiting, I am fully stock, and both my old and new Nexus 7 got the update to 4.4.2 but my Nexus 5 nothing yet, wonder why ?
arimus said:
I am also waiting, I am fully stock, and both my old and new Nexus 7 got the update to 4.4.2 but my Nexus 5 nothing yet, wonder why ?
Click to expand...
Click to collapse
Because it hasn't rolled out to everyone yet. Give it time if you don't want to sideload it.
I am on 4.4 and I could have done sideloading, but I don't care much. Been doing enough nightlies with i777 (ATT SGS2) until last month when it died. I like the pure G experience more than I thought (I thought I would go for CM11 immediately after I get N5 then Omni) and I see not much issue with 4.4. I don't use my phone to take a pic much - I have Fuji XE-1 and Canon 5D for that.
I will get it when I get it. Who knows.. Google might have really started nightlies and 4.4.3 is around the corner.
Edit: Well, it looks like they have decided to give it to me just now.
I just got my 4.4.2 ota update yesterday. Chose not to sideload like I did for the 4.4.1 update. My N4 got the ota update on Mon night (it's stock, not rooted). To some degree, it's all just a crap shoot.
Sent from my Nexus 5 using xda app-developers app
arimus said:
I am also waiting, I am fully stock, and both my old and new Nexus 7 got the update to 4.4.2 but my Nexus 5 nothing yet, wonder why ?
Click to expand...
Click to collapse
There are just different roll-out schedules. Let me put it this way, I was on custom recovery and rooted, and saw I had 4.4.2 update (was on 4.4). So not wanting to mess anything up I went complete stock, though when I rebooted I saw I no longer had it regardless of pressing the update button a million times. So I just ended up side loading it. The reason why it probably was not there, is probably this:
Why is clearing Google Services Framework data is a bad idea?:
There is a myth that has been around for a few years that clearing data in Google Services Framework will get you the OTA faster. Android Engineer Dan Morrill has taken to reddit to explain why NOT to do this and why the method I've described in this thread is the best way to get your update quickly.
Quote:
Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient. -Dan Morrill
Click to expand...
Click to collapse
I am assuming it was no longer valid for me because my ID changed when I wiped my phone. So with that being said, your choices are to either wait, or side load.
4.4 as well ..I'll get the update eventually. No rush here.
Sent from my Nexus 5 using XDA Premium 4 mobile app
From the sheer number of posts showing problems with sideloading, I recommend waiting for the OTA update. Why risk so many issues and buggy software just to get an update a few days earlier?
rikudo said:
From the sheer number of posts showing problems with sideloading, I recommend waiting for the OTA update. Why risk so many issues and buggy software just to get an update a few days earlier?
Click to expand...
Click to collapse
common miss-conception.
sideload is just a different channel to put the damn OTA zip on your phone. there is no higher / lower rate of issues than getting the actual OTA, you will be in the same boat.
Got tired of waiting in Dallas yesterday. I know...patience is a virtue but no a strong point of mine. Wanted to check the camera out so I side loaded both updates early last night.
My N5 has been working like a champ. Camera and speaker are definitely improved!
Sent from my Nexus 5
rikudo said:
From the sheer number of posts showing problems with sideloading, I recommend waiting for the OTA update. Why risk so many issues and buggy software just to get an update a few days earlier?
Click to expand...
Click to collapse
There are no problems with sideloading if one hasn't messed with their phone. Issues arise when one tries to sideload the OTA and they have modified files in /system.
I was using 4.4 ( unrooted ) totally original system, and got 4.2.2 update a few hours ago. I'm in Hamilton ON, Canada.
Lucky me, just got my Note 4 yesterday and checked for software updates just now and low and behold I'm receiving Lollipop, its a 1161.38mb download..
you sure it's lollipop? i know my note 4 received two updates in the past month.
Getting an update on SM-N10A(stock. not rooted) on ATT network. . Its a 1161.38 MB file. Will update on which version does it get updated to shortly.
Update 1: 2.20PM CT: LOL. Installation failed. Try again in 21 hours. Sigh!
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
AT&T started rolling out 5.0.1 this morning to Note 4.
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
sherpa said:
AT&T started rolling out 5.0.1 this morning to Note 4.
Click to expand...
Click to collapse
nice. hopefully not much longer for the canadian releases.
SeraldoBabalu said:
nice. hopefully not much longer for the canadian releases.
Click to expand...
Click to collapse
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
spexwood said:
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
Click to expand...
Click to collapse
You can manually change your date/time to sometime tomorrow and get the update today.
TheIgster said:
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
Click to expand...
Click to collapse
They will just point you here.
HTML:
http://communityforums.rogers.com/html/assets/OSUpgrade.html
And tell you it's TBD. My old co-worker who now works at Rogers looked into it and apparently Samsung isn't releasing that information. As he said it's policy it classify devices that don't get support as TBD as to not piss off customers. Aka it's a coin toss if they are going to release it.
AT&T isn't the same as our devices. The closest we can get is T-Mobile. If and when TMO gets the update we won't be far behind. At least we shouldn't.
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
What are these phone updates of which you speak? Yes, I'm on Verizon.
cyprian64 said:
What are these phone updates of which you speak? Yes, I'm on Verizon.
Click to expand...
Click to collapse
lol...yeah, I guess it's not just those of us in Canada. Really missing my Nexus 5 right now with updates right away straight from Google.
TheIgster said:
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
I was referring to the 5.0.1 update. It's very possible they will just lazily skip it and go for 5.1
If thats the case we most likely won't see a LP update this year. Remember Samsung had the oportunity to start LP in June and it has taken them 9 months just to get to this point. Considering no Canadian Carriers have been informed of the update even arriving, meaning they have not tested them and that in turn could create another month or two of testing. It's also been disclosed that Samsung has no plans on working on 5.1 at the moment. Let's assume that they wait to give us 5.1 instead of pushing 5.0.1 out. Since they have not even started 5.1 we can assume they might start in two months (Highly doubt it would be that quick). Then if we take the first time frame we add another 9 months plus the fact they wait a month after they build (check the build logs) we are at a total time frame of 12 months out for a single update. Skipping 5.0.1 would mean a total of 21 months of development time before the first actual LP update.
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
airwa1kin7 said:
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
Click to expand...
Click to collapse
Sure hope you're wrong. LOL. I would be pretty pissed off if they don't send out a Lollipop update this year.
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
Yep, it sure was
Showing as Android version 5.0.1
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
You'd think that right
How can one of the newest flagships not be on a higher priority?
Sent from my SM-N910W8 using Tapatalk
Are more bloatwares included in this update?
sherpa said:
You can manually change your date/time to sometime tomorrow and get the update today.
Click to expand...
Click to collapse
Oh I know. It's OK though. I was at work with no wifi anyways (and I dont work a desk job either). I have the update downloading now though.
LTE-X said:
Are more bloatwares included in this update?
Click to expand...
Click to collapse
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Captpt said:
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Click to expand...
Click to collapse
Just updated to lollipop and I am experiencing memory leak. I performed a factory reset and is doing much better now.