My failing update on my HD2 went from 10 total steps to 9 today???. And my phone popped up and told me there was an update this morning (which it hasn't done since 7008)? Still fails but the failure code and the response is different.
thuddome said:
My failing update on my HD2 went from 10 total steps to 9 today???. And my phone popped up and told me there was an update this morning (which it hasn't done since 7008)? Still fails but the failure code and the response is different.
Click to expand...
Click to collapse
Are you really trying to update WP7 on an HD2 using MSFT's regular update methods? Wow.
In case you wasn't aware or was miss informed ... WP7 on the HD2 tells Microsoft that its and HD7 then it checks the version of wp7 against their servers and if its older zune will say that your wannabe HD7 (i have an hd2) needs to be updated but once the process starts up at some point it finds out that your so called HD7 isn't exactly who it says it is due to both hardware and software differences and Zune stops the update telling you something and puts your hd2 the way it was..
The only way an HD2 running WP7 can ever be updated is when DFT or anyother Developer ports the Newer WP7 updates to the HD2..
other then that you can never use an official update on it
Okay it was actually the corrected update for the Samsung devices. And yes I did try the update, why not....
I don't care about the update so much for the cut and paste, etc. What they need to fix is the bluetooth. And yes I had an HD7 for about 3 weeks and realized my HD2 was better for a lot of reasons. The bluetooth on WP7 is terrible. I talk on the phone most of the day for work and I have the best headsets on the market and none of them work well with WP7, including when I had the HD7. Everyone complains of them cutting out, etc. I tried the various registry tweaks to no avail so far. It's not the hardware, I've tried 2 phones and about 4 different headsets.
As far as the HD2 failing on update, you are right, it's a driver issue. No need for the lecture, I kinda know a little bit about it....
I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.
This is a very common scenario: Manufacturer creates a tablet, releases it in the market, but then shies away from providing support or even fixing any issues by providing an OTA update.
I'm suffering from one such issue (the last lollipop OTA upgrade in my Asus Fonepad ME175CG broke after which tablet drains the entire battery in just a couple of hours). Its not just me, but everyone who have bought this tablet and made the OTA upgrade is suffering from the same fate. The most troublesome aspect of this is that the OEM stopped giving new updates just after this last buggy OTA update.
Of course, like most of you people, I may have to forget about it and keep saying, "OEMs can do whatever they want", but that isn't going to stop me from trying. Call me a socialist or SJW, but the least I want to do is make sure that the OEMs think twice before giving out a half-baked OTA update that breaks an existing working device. And I believe that it can happen if enough people will sign this petition:
https://www.change.org/p/asustek-pl...ium=email&utm_campaign=share_email_responsive
Hi guys & gals,
I have a stock, unrooted, bootloader locked LG Nexus 5X, which can't find the OTA update to Android Nougat.
I wanted to give it some time, because I thought maybe the 5X updates came later, but it's been quite a few days already and I've read that most people have received their OTA updates already.
Do you have any idea what the problem could be? I check my system of updates a couple of times per day, but nothing, it keeps telling me it's up-to-date.
Could it be possible that the update will not come for weeks after the release?
Thanks!
I gave up waiting just enrolled in beta updated N then un enrolled from beta all good
Sent from my Nexus 5X using Tapatalk
Instead of enrolling in beta, I flashed with factory image after cleaning it i.e. factory reset.
So far, it's buttery smooth.
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
jordylicht said:
Hi guys & gals,
I have a stock, unrooted, bootloader locked LG Nexus 5X, which can't find the OTA update to Android Nougat.
I wanted to give it some time, because I thought maybe the 5X updates came later, but it's been quite a few days already and I've read that most people have received their OTA updates already.
Do you have any idea what the problem could be? I check my system of updates a couple of times per day, but nothing, it keeps telling me it's up-to-date.
Could it be possible that the update will not come for weeks after the release?
Thanks!
Click to expand...
Click to collapse
there is absolutely no problem apart from this being a nuisance for the imaptient. checking for updates more than once a day (which the system does automatically) does absolutely nothing to your position in the rollout-queue and since google sticks to their staged rollout policy, it is indeed not unlikely for a nexus to not officially receive an OTA until two or three weeks have past (unsure about the specifics).
shufal said:
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Click to expand...
Click to collapse
sure, impatiently waiting for an update to reach one can be nerve wrecking. staged rollouts as google is practicing them are, besides other reasons, to ensure critical bugs that may have slipped through don't mess with every unit out there at once. it's not like google wouldn't have the bandwidth to provide the updates to every nexus at the same time.
you should also consider, that apple has not only full control over the hardware of their limited lineup of devices, but also is the only one working on their code, which is quite different to the way android is handled.
jordylicht said:
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
Click to expand...
Click to collapse
the update is out since the day N was officially released, no promise broken. it's simply not your turn yet to receive it automatically. android one devices, in terms of updates, work exactly like nexus devices afaik, so nothing to worry about when one gets the OTA earlier than a nexus. fortunately google made it quite simple this time to skip the line by enrolling in the beta program for a few minutes.
Broken303 said:
there is absolutely no problem apart from this being a nuisance for the imaptient. checking for updates more than once a day (which the system does automatically) does absolutely nothing to your position in the rollout-queue and since google sticks to their staged rollout policy, it is indeed not unlikely for a nexus to not officially receive an OTA until two or three weeks have past (unsure about the specifics).
sure, impatiently waiting for an update to reach one can be nerve wrecking. staged rollouts as google is practicing them are, besides other reasons, to ensure critical bugs that may have slipped through don't mess with every unit out there at once. it's not like google wouldn't have the bandwidth to provide the updates to every nexus at the same time.
you should also consider, that apple has not only full control over the hardware of their limited lineup of devices, but also is the only one working on their code, which is quite different to the way android is handled.
the update is out since the day N was officially released, no promise broken. it's simply not your turn yet to receive it automatically. android one devices, in terms of updates, work exactly like nexus devices afaik, so nothing to worry about when one gets the OTA earlier than a nexus. fortunately google made it quite simple this time to skip the line by enrolling in the beta program for a few minutes.
Click to expand...
Click to collapse
Who else work on 'Stock Android' besides Google? Samsung? LG? You are bull****ting when you say 'which is quite different to the way android is handled' when we are talking about Google releasing OTA for its own 'Nexus'.
By the way, I am tired of hearing Google ensuring critical bugs may slip through OTA but in reality that never happened. And even if OTA brings any bug, Google always fix it in the next schedule which sometimes took 6< months..
I love Nexus (already hating the branding of Pixel) and I will complain whatever I think Google has the ability to fix.
shufal said:
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Click to expand...
Click to collapse
Those who want it immediately have a path to get it immediately. There was some friction over needing to unlock bootloader to get it immediately in the past because of the factory images, but now with the full (rather than differential) OTAs they provide, you no longer need to have unlocked bootloader.
So your complaint now boils down not to Google providing it immediately but how convenient their "immediate" format is.
IMO most people who want it immediately can be satisfied with the full OTA or factory image. A very small number of people that want it immediately won't be able to use one of those 2 methods and will just wait their turn.
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
jordylicht said:
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
Click to expand...
Click to collapse
Your Nexus 5x was among the first to have Android N available. You could have manually downloaded the full OTA or factory image if you wanted.
The "backup" complaint you have is a red-herring. You don't need to back up if you use the manual methods. The FULL (vs differential) OTA doesn't erase data and the factory image can be made not to erase data by removing one flag from the batch file. Now you might want to backup before the update installs, just to be safe, but that holds even for the differential OTA you get over the air, so it has nothing to do with manually downloading an update.
The scheduling of your automatic download is a separate issue. Nexus has always randomly scheduled downloads. It can take up to 3-4 weeks for everyone to see the update.
I'm sure you will agree that there is a big difference between having Android N available but not being scheduled to download it yet vs other platforms which may not make Android N available at all or won't have it available to download for *anybody* months after it was released.
Google is saying your phone will have the software available, not that their scheduler will have your phone download the update immediately upon availability. They however give you a method to download it immediately if you want to.
Do scheduled OTA update happen on weekends and holidays?
Sent from my Nexus 5X using XDA-Developers mobile app
agouracaguy said:
Do scheduled OTA update happen on weekends and holidays?
Click to expand...
Click to collapse
Yes, algorithm does some undefined random selection process. It doesn't care about weekends or holidays and there is no human involved that might care.
I hope this is the best place to ask this question since it's largely concerned with "upgrading".
Earlier this year I'd had enough of my Apple iPhone and its endless buggy updates which the phone would railroad you into installing and had no way to disable that. I elected to go for an Android phone. After spending a while looking I went for a Samsung Galaxy S8 which came with Android 7 and was literally flawless, the first such phone I'd had since iOS 8.6. Hurrah
However the phone has a major fault confirmed by the manufacturer. One key thing I checked was that I wouldn't be in the same position as with Apple, forced into installing updates. I am actually a software developer and one with a very limited tolerance of buggy things. I also understood that with Android you can't undo updates without invalidating the warranty. I have no problem with being informed they're available. Once. I can then review whether I want to risk it or not. I don't want to risk Oreo since there are plenty of reports of reduced battery life among other things and it brings nothing new of any significance and once it's on there it can't be taken off again.
So I checked the features and menus on the S8 before I bought it and went ahead.
This phone was great for about 3 months until the Oreo update was released. At which point the device began nagging. There are various settings which should, among other things, stop it downloading updates automatically and a developer mode option that should stop it updating. However as confirmed by Samsung these options simply do not work, it is a defect out-of-the-box and they are ignored. The phone will do what it wants not what you want.
So I'm now back where I was with Apple albeit the device is otherwise bug-free and superb. I have an uncancellable dialog box coming up repeatedly trying to railroad me into installing the Oreo update it should not have downloaded anyway. This is destroying what was a superb device. I've expended ages resetting it already. There aren't enough hours in the day. Android 7 is great. It isn't my primary device, that being my PC. I just want something that runs a few apps and checks email and that's about all. I don't want a "Samsung Experience"
Samsung refuse to fix this, but as they've confirmed it's a fault I can get a refund from the retailer now. However I still need a phone. My question is:
Is it absolutely necessary to invalidate the warranty on a brand new phone out-of-the-box to stop this behaviour since they're all like it? (e.g. "rooting" is the only option)
Or, does anyone know more than Samsung do about their phones and can advise how the phone can be repaired by me (have done factory reset, denied internet, set not to update etc., as Samsung confirm, this part is broken and doesn't work). I could for instance block Samsung's IPs if I knew what they were but that will only work on WiFi here, not on mobile data. As I understand it the package that needs disabling is called "Software Update" but that isn't possible (again without invalidating the warranty which I'd rather not do since it's almost new).
I know how to scupper Microsoft's Windows Updates but that's because that's what I work with and I know the OS quite well and what they're up to. But I don't know how the Android OS works nor should I need to, really. Another reason for my reluctance to forcibly replace the OS.
Don't mind a pop-up box informing me updates are available with a button "Do Not Install" coming up when the update is released. What I don't want is what this phone and Apple phones do which is to suggest they know better than you do and eventually force you into installing them.
Or, which Android phones behave properly and don't have this sort of fault? That respect the user's settings and do not do whatever they like? I'll need to choose a new one anyway so this would be really useful.
Thanks for reading all that