Related
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
tiwas said:
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
Click to expand...
Click to collapse
Lol I'm sorry for you.
My device never rebooted itself.
And freezed only once. The only unreliable behaviour I noticed was Marketplace - widely documented problem - and Weather Channel quit working once...
So I have no idea what causes that.
But it may be an app, badly written.
You're probably looking at a hardware problem. This happened to a number of HD2s too. I'd take it back to the store you bought it from, explain the problem, and use your warranty to get a new one.
Well, the reason I'm asking is that there are a lot of people in the Trophy forum reporting this behavior - in addition to me. If it doesn't happen to other devices, it's probably a design flaw, but I'm not taking my phone in until I can back it up
tiwas said:
Well, the reason I'm asking is that there are a lot of people in the Trophy forum reporting this behavior - in addition to me. If it doesn't happen to other devices, it's probably a design flaw, but I'm not taking my phone in until I can back it up
Click to expand...
Click to collapse
What do you need to backup. All your purchases can be re-downloaded for free. Contacts, emails, pictures, videos, etc. can be resynced. That's the beauty of the 'cloud'.
tiwas said:
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
Click to expand...
Click to collapse
My LG optimus 7 rebooted randomly like yours. Now back in repairs, I'll suggest you send it back while it's still under warranty
Mine has rebooted itself a few times and I have a Samsung Focus. Personally I think its a memory management issue. Generally happens after running a lot of apps and the phone hasnt had a reboot in a while.
randude said:
Mine has rebooted itself a few times and I have a Samsung Focus. Personally I think its a memory management issue. Generally happens after running a lot of apps and the phone hasnt had a reboot in a while.
Click to expand...
Click to collapse
WP7 clears any memory aps use after the phone exits a program. And without multitasking, memory is not an issue. It's a hardware issue... usually with the internal processor.
I don't think it's a software flaw either, as a lot of people don't have this problem. Also, there are no programs running in the background, so that clears that issue. I suspect the phone developers have been in a hurry and have just pushed out handsets that are really just beta versions.
My LG Optimus 7 reboots from time to time, too.
My TMOUS HD7 has done this like 3 times in about a month and a half if that makes a difference to anyone. T-Mobile replaced my HD2 when it was doing this and the newer HD2 never did it.
Do you guys have bluetooth enabled? Just hit me yesterday that my problems started when I turned bluetooth on...
My bluetooth is off and I have this problem.
Ok, might be coincidence, but my phone seems to have stopped rebooting after I turned BT off. Not a single one in the last four days
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.
rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.
JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
They all say 'Android is updating' everytime you power the phone on ;-)
oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.
drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.
I heard that they are updating the baseband, not the software version...
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.
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