I asked this question in another thread before. But the curiousity of mine got the better of me..
I tried to search for updates on Note 7 these couple of days and all the news were about refunds, recall, banned from flights.. nothing on new 'explosions'? Can't be all phones were returned or absolutely no one using. Even if all phones are turned off, there is still a possibility of one catching fire right?
Or did I miss something?
I'm not really saying conspiracy theories. Just coincidentally.. it just cease... touch wood..
i post a linked earlier showing that there are more people using the note 7 after the 2nd recall for some reason.
mission accomplished, as for the fruity co. and the tyrant mighty G, lol
But on a serious "note", pun intended.. really no more new cases? It is getting more and more coincidental isn't it?
XanaviGTR said:
I asked this question in another thread before. But the curiousity of mine got the better of me..
I tried to search for updates on Note 7 these couple of days and all the news were about refunds, recall, banned from flights.. nothing on new 'explosions'? Can't be all phones were returned or absolutely no one using. Even if all phones are turned off, there is still a possibility of one catching fire right?
Or did I miss something?
I'm not really saying conspiracy theories. Just coincidentally.. it just cease... touch wood..
Click to expand...
Click to collapse
I never saw in the press all 23 the cpsc says happened from Sept 15 till the other day so likely they are still happening. Not everyone runs to the verge.
Sent from my HTC6545LVW using Tapatalk
dottat said:
I never saw in the press all 23 the cpsc says happened from Sept 15 till the other day so likely they are still happening. Not everyone runs to the verge.
Click to expand...
Click to collapse
Or because it was not news worthy anymore? There is a case of the phone caught fire when it was off. So I guess it will happen randomly even when every Note users switched it off. Yet, zero reports news. The more I think of it, the more I feel that it is a waste to recall everything single one world wide.
There was one that caught fire a few days ago, I think Oct 10th, in South Korea at a Burger King and got caught on video so, yes they're still having problems and as long as people keep them and continue using them we'll see incidents reported at some point.
br0adband said:
There was one that caught fire a few days ago, I think Oct 10th, in South Korea at a Burger King and got caught on video so, yes they're still having problems and as long as people keep them and continue using them we'll see incidents reported at some point.
Click to expand...
Click to collapse
What i actually meant was cases after those reported earlier. After saying they stop production and recalling.
Because there are so many people intent on keeping their devices, I'm absolutely positive we'll see more reports as time passes. I don't suspect we'll see hundreds or even thousands of them since it's such a random thing so far - happens when it's on, happens when it's off, happens when it's charging, happens when it's not charging, and so on - but even so we haven't seen the last reports, no, not by a long shot.
Personal opinion, obviously, but since people are freakin' stupid that's an absolute guarantee that this situation is far far from over.
br0adband said:
Because there are so many people intent on keeping their devices, I'm absolutely positive we'll see more reports as time passes. I don't suspect we'll see hundreds or even thousands of them since it's such a random thing so far - happens when it's on, happens when it's off, happens when it's charging, happens when it's not charging, and so on - but even so we haven't seen the last reports, no, not by a long shot.
Personal opinion, obviously, but since people are freakin' stupid that's an absolute guarantee that this situation is far far from over.
Click to expand...
Click to collapse
Ok. Refraining from branding others being stupid... i just like to point out that, a substantial number 'randomly' happen over a short span of time, then randomlynothing happen after that. That doesn't translate to random in my limited knowledge.
I think you're trying to figure out randomness a little too tightly there. Is this type of incident predictable to any given level of confidence? No. Does it happen at unpredictable times? Yes. Has it happened in a wide geographical spread aka worldwide? Yes. Has it happened on original devices and also replacement models that use entirely different batteries that come from a completely different supplier? Yes.
By definition that would mean it's a random thing.
As for the "nothing happens" concept, that could be because people are not using their devices - and yes we know it has happened on devices that were entirely powered down and not charging which could lend some credibility towards it being a compression/pressure issue on the battery that causes the thermal runaway condition which can occur over time, not just in an instant when it's desired. Even so, not using a Note 7 can apparently be just as potentially hazardous as using one so, again, returning the device is plain old prudent and common sense.
Anybody that can't see that returning the Note 7 is the best solution possible is - as I've stated - being stupid for their own reasons but stupid just the same.
Some people will believe anything they read, either in mainstream news or rags such as 'The Verge'.
They may well be the ones who are duped.
Re: "Anybody that can't see that returning the Note 7 is the best solution possible is - as I've stated - being stupid for their own reasons but stupid just the same."
Solution? Solution to what exactly?
br0adband said:
I think you're trying to figure out randomness a little too tightly there. Is this type of incident predictable to any given level of confidence? No. Does it happen at unpredictable times? Yes. Has it happened in a wide geographical spread aka worldwide? Yes. Has it happened on original devices and also replacement models that use entirely different batteries that come from a completely different supplier? Yes.
By definition that would mean it's a random thing.
As for the "nothing happens" concept, that could be because people are not using their devices - and yes we know it has happened on devices that were entirely powered down and not charging which could lend some credibility towards it being a compression/pressure issue on the battery that causes the thermal runaway condition which can occur over time, not just in an instant when it's desired. Even so, not using a Note 7 can apparently be just as potentially hazardous as using one so, again, returning the device is plain old prudent and common sense.
Anybody that can't see that returning the Note 7 is the best solution possible is - as I've stated - being stupid for their own reasons but stupid just the same.
Click to expand...
Click to collapse
It can happen to any units, whether manufactured initially or the second batch, using any batteries at any country. Agree. And if a hardware can't be pinpoint, probably it is design flaw. And design flaw means, it can still happen. Agree. No doubt we will have to turn it in.
But just to emphasize what I've mentioned, why the pattern occurs with such intensityat certain point, but stopped at suddenly. Shouldn't it occurs at least at some point of time, somewhere to someone in the past few days? Why the inconsistency in occurrance if it was a hardware/design failure? Either we should have a incidence happening in Southeast asia, or we should expect one in Europe. But it just stop. Whether the phones were operating or returned or still in used dont add up to the equation now. Why this phenomenon ceased after they decide to close down production and recall all back. Unless the phones know through supernatural means that it is time to stop exploding because they are going back to mother ship ( Samsung), I have no other answers which I'm seeking for.
At this point media don't care... phone is destroyed and all that refund, recall **** is more important then just writing about it blowing up OK just combustion over and over is boring. Unless someone goes to hospital you will hear it... and looking that note7 usage increased smth like that can happen... rly sad 2 years for note users in Europe... will be waiting for note8 with my s7e...
XanaviGTR said:
It can happen to any units, whether manufactured initially or the second batch, using any batteries at any country. Agree. And if a hardware can't be pinpoint, probably it is design flaw. And design flaw means, it can still happen. Agree. No doubt we will have to turn it in.
But just to emphasize what I've mentioned, why the pattern occurs with such intensityat certain point, but stopped at suddenly. Shouldn't it occurs at least at some point of time, somewhere to someone in the past few days? Why the inconsistency in occurrance if it was a hardware/design failure? Either we should have a incidence happening in Southeast asia, or we should expect one in Europe. But it just stop. Whether the phones were operating or returned or still in used dont add up to the equation now. Why this phenomenon ceased after they decide to close down production and recall all back. Unless the phones know through supernatural means that it is time to stop exploding because they are going back to mother ship ( Samsung), I have no other answers which I'm seeking for.
Click to expand...
Click to collapse
This is also what I asked in a previous thread, but some guys jumped on easy clichees...
It is strange that we never heard of any issues with any of the phones which were on display worldwide, always connected to chargers and handled by a lot of people in all the possible ways...
Now, after the first recall, we suddenly hear of reports, some saying the phone was not charging or was even turned off. They started the fears that the phone is dangerous, no matter if on or off. Even so no report of any phone going crazy in any warehouse or during the shipping back, despite the 'concerns' of majority of the shipping companies that refuse to ship the phone...
Now, ban the phone completely in the airplanes...
Still, as you noticed, after the last decision, the phones, 'magically', started the be afraid and are behaving well, no matter that the number of Note 7 still in use is increasing so, it is not quite true that the people is shutting them down...
Yesterday I saw a news that an iPhone 7 busted in flames and injured the owner on the face, because he was filming with the phone. Not many sites mentioned the incident...
I might be wrong, but there are a little too more coincidences for such a 'random' issue...
Anyhow, it appears that 'Mission is completed!'...
Let's hope that we see a future for the Note line!
Ok, consider this: since we don't actually know (we meaning you, me, Samsung, and anybody else at this precise moment in time) what's causing these problems which appear to be random in nature and could happen at any given time and yet you're wondering why we haven't seen any new incidents being reported at this time you have to consider something else as well.
You have to consider:
- that Samsung had a 1st recall and got the word out to the world about the potential for the device to catch on fire and burn up causing problems
- that Samsung attempted to resolve the issue but wasn't or hasn't been able to effectively reproduce it with any consistency that we (meaning the general public at large worldwide) have been made aware of
- that Samsung leaned towards it being a battery issue so they switched suppliers for the batteries that were to go in replacement devices
- that Samsung created and distributed a firmware update that when applied to the Note 7 caused the charging circuit to enforce more stringent limitations on not only the amount of current being applied when charging was taking place (to keep the battery from potentially overheating) but also some temperature related adjustments bringing the previous thermal limits down quite a bit (to cause the device to shut down if the thermal limits were breached) and also modified the battery icon from Google's mandated white color to green for a quick identification of "fixed" devices (Samsung had to ask for permission to do that, actually, but Google had no reason to deny it and I think it was a good idea overall in this situation)
- that Samsung then got reports of some of the replacement units also exhibiting the same type of behavior and also failing because of a thermal runaway condition and therefore they initiated a second voluntary recall of the original devices that had the update applied but also the replacement models that shipped with a) a new battery from the different supplier and b) the firmware applied to limit the charging current and the modified thermal limits
- that Samsung worked closely with the Consumer Product Safety Commission here in the U.S. in getting the word out about the 1st and then the 2nd recall, both voluntary as requested by Samsung itself
- that Samsung finally had to toss in the towel on the Note 7, declare it utterly dead for all intents and purposes, and then have the CPSC step the recall up to a mandatory one (at least here in the U.S.)
Now, considering all that information, all those events that have happened since all this started, it's pretty obvious to see that the information has spread far and wide from websites on the Internet to local TV station news broadcasts talking about the Note 7 to comedians and late night TV talk show hosts making jokes about the Note 7 (I just got done watching "Real Time with Bill Maher" and even HE made a joke in his opening monologue related to Samsung and this Note 7 fiasco) to cable news networks mentioning it, and then finally Samsung and carriers contacting customers by email and sending SMS text messages to their numbers with information and alerts about returning the devices.
What's my point?
What has changed in the past week or so if that:
- because of the spread of that information people stopped using their Note 7 devices, completely, most people probably turning them off/powering them down totally and just not messing with them again (this doesn't necessarily protect them from potential problems because at least 2 instances of the Note 7 exploding/burning up were attributed to devices that were totally powered down, I can't confirm that's absolute true and the stories are not false, I'm just saying that there were at least 2 reports worldwide of Note 7 devices having this problem that can't be replicated on demand when they were totally powered off according to the claimants)
- because of the spread of that information people contacted Samsung and their carriers and started returning their devices as requested by Samsung per the recall (a week ago it was still voluntary) - again, they stopped using them
- because of the spread of that information Samsung and the carriers started collecting the recalled units removing them from potential use and powering them down which may be their safest condition but it's not 100% safe for sure without any doubt whatsoever - that's why this recall is happening because no one can absolutely guarantee that any given Note 7 won't exhibit this problem so they have to sweep them all off the planet, plain and simple
I hope that helps with understanding why the number of incidents appears to be lower now as opposed to a week or even 2-4 weeks ago when this really got started. More people know about it, more people got more accurate info, got notifications from Samsung and their carriers about a potential safety hazard with the Note 7, and those people - the intelligent ones that understand this could prove to be a very serious problem if it happens to them - did what they were requested to do and because of that the total number of incidents that have happened is now lower due to those people taking action on their own parts to get things corrected.
I don't see why most people don't grasp this - I still see people blaming Samsung as though it's a conspiracy of sorts just to take away their Note 7's which is utter rubbish from any intelligent angle you can look at this situation from. Things happen, mistakes are made, other phones have had similar problems from time to time but in this situation with the Note 7 it happened almost at the time of release (a few weeks at most) and it happened with a higher frequency aka more people worldwide reporting on it.
If something happens once, it can sometimes be attributed to just a defect in that one unit, a mishap on the production line, someone not paying attention and making a mistake. If it happens to the same product in two or three devices of the same type, it could indicate a problem with the production again but contained to a respectable degree. When it happens a few dozen times, and not only that but when it causes the public to incur some damage to person or property, that's when it becomes a much more severe issue - it's that bridge of going from "oh, my device has a problem..." to "oh, my device just blew up and scorched my leg/pants/table/chair/sofa/bed/purse/backpack/dash of my car/etc..." that things take on a completely different situation.
tl;dr version: Not as many people are using the Note 7 today or in the past few days as there were a week ago, or two weeks ago, and so on. Really, that's the simplest answer of all.
See how that works? Hope this helps...
br0adband said:
Ok, consider this: since we don't actually know (we meaning you, me, Samsung, and anybody else at this precise moment in time) what's causing these problems which appear to be random in nature and could happen at any given time and yet you're wondering why we haven't seen any new incidents being reported at this time you have to consider something else as well.
You have to consider:
- that Samsung had a 1st recall and got the word out to the world about the potential for the device to catch on fire and burn up causing problems
- that Samsung attempted to resolve the issue but wasn't or hasn't been able to effectively reproduce it with any consistency that we (meaning the general public at large worldwide) have been made aware of
- that Samsung leaned towards it being a battery issue so they switched suppliers for the batteries that were to go in replacement devices
- that Samsung created and distributed a firmware update that when applied to the Note 7 caused the charging circuit to enforce more stringent limitations on not only the amount of current being applied when charging was taking place (to keep the battery from potentially overheating) but also some temperature related adjustments bringing the previous thermal limits down quite a bit (to cause the device to shut down if the thermal limits were breached) and also modified the battery icon from Google's mandated white color to green for a quick identification of "fixed" devices (Samsung had to ask for permission to do that, actually, but Google had no reason to deny it and I think it was a good idea overall in this situation)
- that Samsung then got reports of some of the replacement units also exhibiting the same type of behavior and also failing because of a thermal runaway condition and therefore they initiated a second voluntary recall of the original devices that had the update applied but also the replacement models that shipped with a) a new battery from the different supplier and b) the firmware applied to limit the charging current and the modified thermal limits
- that Samsung worked closely with the Consumer Product Safety Commission here in the U.S. in getting the word out about the 1st and then the 2nd recall, both voluntary as requested by Samsung itself
- that Samsung finally had to toss in the towel on the Note 7, declare it utterly dead for all intents and purposes, and then have the CPSC step the recall up to a mandatory one (at least here in the U.S.)
Now, considering all that information, all those events that have happened since all this started, it's pretty obvious to see that the information has spread far and wide from websites on the Internet to local TV station news broadcasts talking about the Note 7 to comedians and late night TV talk show hosts making jokes about the Note 7 (I just got done watching "Real Time with Bill Maher" and even HE made a joke in his opening monologue related to Samsung and this Note 7 fiasco) to cable news networks mentioning it, and then finally Samsung and carriers contacting customers by email and sending SMS text messages to their numbers with information and alerts about returning the devices.
What's my point?
What has changed in the past week or so if that:
- because of the spread of that information people stopped using their Note 7 devices, completely, most people probably turning them off/powering them down totally and just not messing with them again (this doesn't necessarily protect them from potential problems because at least 2 instances of the Note 7 exploding/burning up were attributed to devices that were totally powered down, I can't confirm that's absolute true and the stories are not false, I'm just saying that there were at least 2 reports worldwide of Note 7 devices having this problem that can't be replicated on demand when they were totally powered off according to the claimants)
- because of the spread of that information people contacted Samsung and their carriers and started returning their devices as requested by Samsung per the recall (a week ago it was still voluntary) - again, they stopped using them
- because of the spread of that information Samsung and the carriers started collecting the recalled units removing them from potential use and powering them down which may be their safest condition but it's not 100% safe for sure without any doubt whatsoever - that's why this recall is happening because no one can absolutely guarantee that any given Note 7 won't exhibit this problem so they have to sweep them all off the planet, plain and simple
I hope that helps with understanding why the number of incidents appears to be lower now as opposed to a week or even 2-4 weeks ago when this really got started. More people know about it, more people got more accurate info, got notifications from Samsung and their carriers about a potential safety hazard with the Note 7, and those people - the intelligent ones that understand this could prove to be a very serious problem if it happens to them - did what they were requested to do and because of that the total number of incidents that have happened is now lower due to those people taking action on their own parts to get things corrected.
I don't see why most people don't grasp this - I still see people blaming Samsung as though it's a conspiracy of sorts just to take away their Note 7's which is utter rubbish from any intelligent angle you can look at this situation from. Things happen, mistakes are made, other phones have had similar problems from time to time but in this situation with the Note 7 it happened almost at the time of release (a few weeks at most) and it happened with a higher frequency aka more people worldwide reporting on it.
If something happens once, it can sometimes be attributed to just a defect in that one unit, a mishap on the production line, someone not paying attention and making a mistake. If it happens to the same product in two or three devices of the same type, it could indicate a problem with the production again but contained to a respectable degree. When it happens a few dozen times, and not only that but when it causes the public to incur some damage to person or property, that's when it becomes a much more severe issue - it's that bridge of going from "oh, my device has a problem..." to "oh, my device just blew up and scorched my leg/pants/table/chair/sofa/bed/purse/backpack/dash of my car/etc..." that things take on a completely different situation.
tl;dr version: Not as many people are using the Note 7 today or in the past few days as there were a week ago, or two weeks ago, and so on. Really, that's the simplest answer of all.
See how that works? Hope this helps...
Click to expand...
Click to collapse
I see that you took a long time to prepare all this
Even if it is a lot of good info here, still it doesn't answer few of my questions...
How come it never happened in any showroom, with the phones always charging and handled by a lot of people?
How come it never happened to any warehouse, hypothetically having hundreds of units in one place? Don't tell they were powered off...
How come this hysteria with fireproof boxes and gloves for the returns when we did not hear any single case of a phone catching fire during the shipping?
I could continue mentioning the lack of cases in Canada, Europe, Middle East, etc. but I don't plan to go polemic...
Still, everyone is free to read and understand the news in the way it serves his/her beliefs and concerns about the 'life' in general...
It might be that some people is not ready to 'buy' all that media is 'selling' to us and ask themselves a few extra questions, sometimes good ones, sometimes maybe not...
And, as for the number of phones still in use:
http://phandroid.com/2016/10/14/galaxy-note-7-use-after-recall/
MariusB said:
I see that you took a long time to prepare all this
Click to expand...
Click to collapse
Typed it all off the top of my head as I pretty much always do.
Even if it is a lot of good info here, still it doesn't answer few of my questions...
How come it never happened in any showroom, with the phones always charging and handled by a lot of people?
Click to expand...
Click to collapse
This goes along with my working theory:
http://forum.xda-developers.com/note-7/how-to/note-7-battery-issue-theory-progress-t3480235
related to the fact that the issue is more than likely caused by pressure on the case which is passed on to the battery itself which could result in the anode-cathode contact issue creating the thermal runaway. Just the fact that those showroom devices are handled by a lot of people doesn't equate to people using them in the real world: storing them in bags where they can be subject to external pressure(s) of various kinds, stuffed in a back pocket when people sit down (this happens so often it's scary), and other situations.
Also, consider that those kinds of devices are always plugged in when they're in a showroom or on a demo display which means they're never really charging - they stay in a constantly charged state with a minimal trickle at best. They're not having situations where they use the battery, then it needs to be recharged causing some heat stress, then they use the battery again, have to be recharged meaning heat cycling again, and so on. Typical usage means it's used, it's charged, it's used, it's charged, it's used, it's charged, you get the idea, right? Right?
I am 100% confident that the issues the Note 7 is having are not caused by heat nor are they directly attributable to heat itself inside the device. That's my opinion and I'm not pushing it on anybody.
How come it never happened to any warehouse, hypothetically having hundreds of units in one place? Don't tell they were powered off...
Click to expand...
Click to collapse
Same reason I just stated: if the anode-cathode contact situation happens because of pressure on the battery (which is already barely able to fit inside the Note 7 as it is), packed down tightly, malformed by the packaging it uses, then wrapped on the edges by black electrical tape, crammed into that tiny space then it has pressure applied when the cover is on due to the sticky tape (as thin as it is that still causes pressure on the battery cell) then it must be considered as a potential for this happening. See the article in my theory where it shows info about the probably plate issues and the new production method of the Note 7 to get the symmetric glass top and bottom.
Again, my opinions but that have a basis in actual facts with respect to Li-Ion battery cell technology.
How come this hysteria with fireproof boxes and gloves for the returns when we did not hear any single case of a phone catching fire during the shipping?
Click to expand...
Click to collapse
The Note 7 has exhibited a defect that has caused some devices to combust/explode/catch on fire so there's no "not really all that safe" way to do a recall - you go all the way and use the tools necessary and that means the custom boxes and gloves and everything related. We don't KNOW anything about potential issues with devices being shipped BACK at this point, that information is simply not available so you're speculating that nothing has happened since the 1st voluntary recall and now into the 2nd mandatory one. Samsung isn't necessarily going to advertise yet another failure but this time in a return package sent back to them, the shippers like FedEx and UPS aren't going to advertise they've had problems either - THAT is the kind of hysteria they don't need and to maintain public safety and not blow things out of proportion (pun intended) with respect to facts then all they're required to do is say the recall is underway and they're getting devices returned to them.
I could continue mentioning the lack of cases in Canada, Europe, Middle East, etc. but I don't plan to go polemic...
Click to expand...
Click to collapse
You have no idea if any reports from Canada, Europe, Middle East, etc have actually been made at this point in time because Samsung has not made any public statements with a detailed accounting of all the reports they've received and will probably continue to receive as time passes. Nobody outside of Samsung and the respective carriers worldwide in said countries and perhaps the shippers would be aware of things - if you're going by the number of pictures posted online or the number of YouTube videos to judge the number of actually defective devices that have combust or exploded, you're just doing it wrong.
Still, everyone is free to read and understand the news in the way it serves his/her beliefs and concerns about the 'life' in general...
It might be that some people is not ready to 'buy' all that media is 'selling' to us and ask themselves a few extra questions, sometimes good ones, sometimes maybe not...
Click to expand...
Click to collapse
That's entirely up to them, my opinion is fine, if you want to keep your Note 7 and continue using it, great, more power to you but don't come whining if and when you have issues with it. The Note 7 is dead, warranty service is dead, updates will not be forthcoming (aside from a potential one to brick devices, entirely possible so we'll see what happens), it is a black Pariah at this point and should be avoided - I for one won't tolerate people around me using a Note 7 if one happens to come near me, I'll flat out tell 'em to move away. I don't need more stupidity invading my space than I can tolerate (which is quite a lot, I assure you, but even I have limits).
Think of it this way: do you really think Samsung wants to be spending an estimated $5 billion in the coming weeks and months, losing billions and billions more in now lost sales potential, and then destroying every Note 7 they get back just because it's something to do? Suffering catastrophic damage to their financials for the next few quarters as well as their reputation and the basic demise of the Note brand altogether? I can assure you it's not just something to do, this is serious stuff and it's going to cost them more than their estimates are letting on, a lot more and not only just in a dollar amount and it's already happening.
And, as for the number of phones still in use:
http://phandroid.com/2016/10/14/galaxy-note-7-use-after-recall/
Click to expand...
Click to collapse
Ok, so people continue to use their effectively dead no updates coming Note 7's, so... they'll figure it out sooner or later and move on, that much is a fact.
Anything else?
The Phone Company said:
Some people will believe anything they read, either in mainstream news or rags such as 'The Verge'.
They may well be the ones who are duped.
Re: "Anybody that can't see that returning the Note 7 is the best solution possible is - as I've stated - being stupid for their own reasons but stupid just the same."
Solution? Solution to what exactly?
Click to expand...
Click to collapse
So you are suggesting that Samsung decided TWICE to recall and then cease production of a perfectly healthy functional device and lose multi billions of euros just because of the media ?
Ryland
br0adband said:
I think you're trying to figure out randomness a little too tightly there. Is this type of incident predictable to any given level of confidence? No. Does it happen at unpredictable times? Yes. Has it happened in a wide geographical spread aka worldwide? Yes. Has it happened on original devices and also replacement models that use entirely different batteries that come from a completely different supplier? Yes.
By definition that would mean it's a random thing.
As for the "nothing happens" concept, that could be because people are not using their devices - and yes we know it has happened on devices that were entirely powered down and not charging which could lend some credibility towards it being a compression/pressure issue on the battery that causes the thermal runaway condition which can occur over time, not just in an instant when it's desired. Even so, not using a Note 7 can apparently be just as potentially hazardous as using one so, again, returning the device is plain old prudent and common sense.
Anybody that can't see that returning the Note 7 is the best solution possible is - as I've stated - being stupid for their own reasons but stupid just the same.
Click to expand...
Click to collapse
And I think you don't understand what random means. Clearly *something* is causing this problem, which maybe far from random. It's simply that no-one has managed to figure out what the something is. Maybe EVERY Note 7 may at some point burst into flames. But it is equally possible that this is not the case, and only certain ones might do that. No-one knows yet.
And by the way, do we know exactly how many devices have spontaneously combusted whilst powered off? Probably not, but is it as many as were powered on? No, I think we can say with a high degree of confidence that it is not. We are talking one or two, or 4 or 5 maybe, out of a couple of hundred. If the "anode & cathode coming into contact" theory was correct, then it wouldn't make any difference whether the phone was powered on or off at the time, so this explanation seems very unlikely to me.
Related
THIS IS FRAUD.I talked to a high up rep for 45 minutes yesterday and she said we know it is a known issue but sorry no help for you on your bill.
She then said THIS IS A SAMSUNG PROBLEM so i said well are you selling this phone right now? she said yes.I said are you telling people this phone has these problems? she said nothing then said ill pass your concerns along.
If you want into a sprint store NO REP is going to tell you there is a known issue with this phone so they commit fraud selling a phone they say they know there is a known issue with.
Places recall stuff when there is a problem yet sprint keeps selling IT! not right.
rdcrds said:
THIS IS FRAUD.I talked to a high up rep for 45 minutes yesterday and she said we know it is a known issue but sorry no help for you on your bill.
She then said THIS IS A SAMSUNG PROBLEM so i said well are you selling this phone right now? she said yes.I said are you telling people this phone has these problems? she said nothing then said ill pass your concerns along.
If you want into a sprint store NO REP is going to tell you there is a known issue with this phone so they commit fraud selling a phone they say they know there is a known issue with.
Places recall stuff when there is a problem yet sprint keeps selling IT! not right.
Click to expand...
Click to collapse
Two things:
1) You get a 14 day return policy. Use it if necessary. You have that responsibility/option as a customer.
2) Reps are going to vary. Some simply don't know.
Both reps I dealt with informed me of the issue before purchase. [One is a member of xda]
#1 You get a 14 day window and some people will not figure it out in those 14 days since there are times you can get 5 in 1 day and none for 3 days.People who are not on here may not figure it out for a month.
#2 they sell it on there website with no disclaimer it is fraud if you ask a legal expert i would bet on it.May be a very gray area but i have no doubt it is.
I can tell you about issues with every phone that is out there right now. Do you think a sales rep is going to go through the list with you.
I have no problems with my phone and have never seen an LOS on it. If the rep told me there is a probem with LOS they would have bee lying to me. lol
Yes every phone has issues but a KNOWN ISSUE THIS IS that sprint knows is widespread some issues are for like 10% but not like this where it is close to i would guess 75% to 90% of the phones do it.
This phone did it from launch and sprints knows it is a issue a known issue as sprint calls it which a rep says when they call it a known issue it is very widespread.
And it is not the reps job to tell people IT IS SPRINTS AND THEY SHOULD PUT A DISCLAIMER out on there website since it is a known issue no matter how you cut it.
And why? because they would lose sales.I would love to see any other type of place keep selling a item they know has issues.Would Ford? Honda? heck they recall them let alone stop selling them.
rdcrds said:
#1 You get a 14 day window and some people will not figure it out in those 14 days since there are times you can get 5 in 1 day and none for 3 days.People who are not on here may not figure it out for a month.
#2 they sell it on there website with no disclaimer it is fraud if you ask a legal expert i would bet on it.May be a very gray area but i have no doubt it is.
Click to expand...
Click to collapse
rdcrds said:
Yes every phone has issues but a KNOWN ISSUE THIS IS that sprint knows is widespread some issues are for like 10% but not like this where it is close to i would guess 75% to 90% of the phones do it.
This phone did it from launch and sprints knows it is a issue a known issue as sprint calls it which a rep says when they call it a known issue it is very widespread.
And it is not the reps job to tell people IT IS SPRINTS AND THEY SHOULD PUT A DISCLAIMER out on there website since it is a known issue no matter how you cut it.
And why? because they would lose sales.I would love to see any other type of place keep selling a item they know has issues.Would Ford? Honda? heck they recall them let alone stop selling them.
Click to expand...
Click to collapse
Okay... on one hand you say that it may happen only rarely and on the other hand you throw out numbers like 75% to 90% of phones.
Where did you get these numbers?
Ok known troll of this forum LOS is a issue that can happen 5 times in 1 day then go 3 days without it.It has no set amount of times it does it to anyone.Me it does it 1 time or so per day.It all depends on how much you use your phone.
It is totally random how much it happens to each phone.But weather it happens 1 time a day or 5 or whatever amount it happens to a major amount of the phones.Enough to call it a very known issue by sprint.
troll another thread
rdcrds said:
Ok known troll of this forum LOS is a issue that can happen 5 times in 1 day then go 3 days without it.It has no set amount of times it does it to anyone.Me it does it 1 time or so per day.It all depends on how much you use your phone.
It is totally random how much it happens to each phone.But weather it happens 1 time a day or 5 or whatever amount it happens to a major amount of the phones.Enough to call it a very known issue by sprint.
troll another thread
Click to expand...
Click to collapse
Honestly, if asking you where you get numbers from and pointing out absurdities is "being a troll on xda" then you can sign me and any rational person up for that list.
I'm a troll too... Came from a moment and I hate to tell you guys, but every sammy phone suffers from data lock/LOS... Sorry to be the bearer of bad news...
Sent from my PG06100 using Tapatalk
I wanna troll too.....I dont have any signal problems with mine
rdcrds said:
Ok known troll of this forum LOS is a issue that can happen 5 times in 1 day then go 3 days without it.It has no set amount of times it does it to anyone.Me it does it 1 time or so per day.It all depends on how much you use your phone.
It is totally random how much it happens to each phone.But weather it happens 1 time a day or 5 or whatever amount it happens to a major amount of the phones.Enough to call it a very known issue by sprint.
troll another thread
Click to expand...
Click to collapse
Bro your being a **** and unrealistic , the phone has a problem it will be sorted, I know the PHOTON has had a ton of patches sent out since day 2 when they started having loss of sound in the earpiece, although it sucks having patches but regardless it is still one of the best 2 phones we see #1 being the ET4G! The los is annoying but brief and is being worked on as we rant about the only true negative with this product!
Fraud? Legal experts? hahaha you dont think Sprint and Samsung both have a legal team haha come on to be annoyed is one thing but dont start trying to throw out hints for somebody else to fight your battle
75% - 90%.....lol
Glad you threw out the facts.....You must have been a pretty busy person pulling your metrics and data.
This number is based on few users on XDA who are known to root their phones. If you were truly going to do a test, it would have to be based on untouched never rooted phone. Rooted phones would not even be considered in the data gathered, so that leaves out most XDA users.
You do realize how many of these phones are sold and how many of it's users are actually on this site, right?
rdcrds said:
THIS IS FRAUD.I talked to a high up rep for 45 minutes yesterday and she said we know it is a known issue but sorry no help for you on your bill.
She then said THIS IS A SAMSUNG PROBLEM so i said well are you selling this phone right now? she said yes.I said are you telling people this phone has these problems? she said nothing then said ill pass your concerns along.
If you want into a sprint store NO REP is going to tell you there is a known issue with this phone so they commit fraud selling a phone they say they know there is a known issue with.
Places recall stuff when there is a problem yet sprint keeps selling IT! not right.
Click to expand...
Click to collapse
How old are you?! Have you ever bought anything anywhere?! That's how sales are done buddy. It's up to you to research the product prior to investing in it. The rep will always try to close the sale by exagerating, omitting things. It is not fraud in this country.
90% of statistics are made up on the spot..
A false representation of a matter of fact—whether by words or by conduct, by false or misleading allegations, or by concealment of what should have been disclosed—that deceives and is intended to deceive another so that the individual will act upon it to her or his legal injury.
Fraud must be proved by showing that the defendant's actions involved five separate elements: (1) a false statement of a material fact,(2) knowledge on the part of the defendant that the statement is untrue, (3) intent on the part of the defendant to deceive the alleged victim, (4) justifiable reliance by the alleged victim on the statement, and (5) injury to the alleged victim as a result.
A statement of belief is not a statement of fact and thus is not fraudulent. Puffing, or the expression of a glowing opinion by a seller, is likewise not fraudulent. For example, a car dealer may represent that a particular vehicle is "the finest in the lot." Although the statement may not be true, it is not a statement of fact, and a reasonable buyer would not be justified in relying on it.
[email protected] said:
75% - 90%.....lol
Glad you threw out the facts.....You must have been a pretty busy person pulling your metrics and data.
This number is based on few users on XDA who are known to root their phones. If you were truly going to do a test, it would have to be based on untouched never rooted phone. Rooted phones would not even be considered in the data gathered, so that leaves out most XDA users.
You do realize how many of these phones are sold and how many of it's users are actually on this site, right?
Click to expand...
Click to collapse
The percent of phones is not known. Who will release statistics, Sprint? Samsung? I don't think either. My phone is bone stock and I have had LOS only a handful of times I know of. I get data roaming several times/week at my house and this is while on wifi. Does not wifi count as a data connection? Hope this improves with software update but could become worse till better. If I treated patients like this I would lose my license and be on welfare.
Doc
Stock pulled kernal/root and cwm. Stock rom. No Los for a week now. Also noticed that juicedefender cause the issue sometimes. After getting rid of it. I'm all good.
Sent from my SPH-D710 using xda premium
It's not like you couldn't trade your Epic Touch for any of the other high end phones with money on top. Quit crying and wait for a fix or trade it. Or buy an iPhone 4s. Oh wait, they aren't perfect either. I hear their battery life is poor compared to the 4.
sent from my Epic 4g Touch
When I was a custom kernel, I got LOS around 3x per day as OP does. When I switched back to stock, the number reduced to 0. Same with a friend who I did the same thing with.
Op,
If you are *****ing about LOS, and are on a custom kernel, then I have no sympathy. If you are on a stock kernel, ROM then raise hell brutha
I've never experienced LOS on both my Epic 4g, and my Epic 4g Touch. Weird.
rdcrds said:
THIS IS FRAUD.I talked to a high up rep for 45 minutes yesterday and she said we know it is a known issue but sorry no help for you on your bill.
She then said THIS IS A SAMSUNG PROBLEM so i said well are you selling this phone right now? she said yes.I said are you telling people this phone has these problems? she said nothing then said ill pass your concerns along.
If you want into a sprint store NO REP is going to tell you there is a known issue with this phone so they commit fraud selling a phone they say they know there is a known issue with.
Places recall stuff when there is a problem yet sprint keeps selling IT! not right.
Click to expand...
Click to collapse
For the first time ever, I actually agree with one of your posts. For Sprint to claim that the responsibility is on Samsung is disingenuous and only a tactic to deflect customer anger.
Background
This is by no means definitive, so don't everyone go get your panties in a wad and pitch fits like 12 year olds.
So several days ago I noticed that my GNex was starting to have issues with dropping calls and data connections. Basically, I was dropping data and voice despite having a connection to the network about every 2-5 hours, requiring a reboot. This happened over a 3 day period in a stationary position, in radically different places (like 80-150 miles apart). It was happening on 3G and on 4G so I was pretty confident that it wasn't just a localized outage or the local tower acting up. I'm no expert and certainly no /dev, but I've been around some Android devices a time or two.
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else. As an example, shortly after getting my GNex I installed TweetDeck. I had used Navigation several times to test GPS (first thing I did being a SGS owner) so I knew it worked and worked well. Anyway, immediately after installing and setting up TweetDeck, my GPS crapped. It would see satellites but not connect... even after 30 minutes....even after rebooting, clearing AGPS data, blah blah. Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Solution (For me at least)
With that event in mind, and a crapped out radio, I went looking through my app drawer for apps that access the radio. I picked out Network Info II 0.6.0, Real Signal 3.5 and Network Signal Info 1.51. I rebooted and waited. Here it is three days later, and I have yet to have a single voice or data drop. If I've had one on the data side, I haven't noticed and it certainly wasn't for long.
I don't know how or why. All I know is that I've never had any form of radio trouble and those apps were recently installed, and that without them, the radio issues are gone. Take it for what it's worth, which probably isn't much. But if you're on 4.0.4, with 4.0.4 radios and you're suffering from radio problems, flip through your app drawer and remove or freeze applications that have the sole purpose of polling data from your radios. Who knows, maybe having 3 was 1 or 2 to many.
Thanks for the write up. And I really think the issue with certain apps interfering with OS-level stuff is a big issue, and one that nobody seems to want to notice.
There are a ton of posts, not only on this forum but on others, where people are saying they have so many issues with the Nexus and this and that. What a lot of people don't realize is that, yes, certain apps that are either poorly coded in general or not coded for ICS can potentially interfere with the normal operations of your phone.
A lot of people tend to use/stick with apps that they are used to, right? I came from the G1, the very first Android phone, so I've been using Android for awhile, and I bet that other people are too. Some apps are a staple of people's usage, meaning as soon as they get a new device, those same apps are the first to be downloaded and installed. However a lot of times those apps are abandoned by their developers, never to be touched again.
So of course an app that was coded on Froyo or even Eclair that calls the GPS or the radio or bluetooth stack or something else hardware related can potentially cause issues, especially with ICS being such a radical change from Gingerbread.
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
[email protected] said:
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
Click to expand...
Click to collapse
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Food for thought: Apps have not been updated to work 100% with ICS?
KWKSLVR said:
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Click to expand...
Click to collapse
Alright, so will that app tell me what is accessing that feature or do I need to go through every app to find out and what exactly shoould t say in the access?
Help me out here please because this is starting to annoy me!
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
bk201doesntexist said:
Food for thought: Apps have not been updated to work 100% with ICS?
Click to expand...
Click to collapse
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
I've thankfully been free of radio issues thus far on my GNex, but I want to thank you for this thread.
KWKSLVR said:
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else.
...
Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Click to expand...
Click to collapse
KWKSLVR said:
I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation.
Click to expand...
Click to collapse
Not to jump up on too high of a soapbox, but I couldn't agree with you more.
It's very satisfying to read about people methodically, empirically testing. It's something that seems rare these days.
So thank you!
KWKSLVR said:
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
Click to expand...
Click to collapse
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
[email protected] said:
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
Click to expand...
Click to collapse
When I froze those apps, I picked them because I knew they had access to:
Network communication > view network state > Allows an application to view the state of all networks. The part in bold is the description of what the permission "View Network State" means. That permission is under the "Network Communication" Category. Some apps will have more than that single permission under Network communication, some with have none at all. "Real Signal" has the fewest permissions out of the three I froze, and maybe all three don't HAVE to be frozen, but I haven't tested that yet.
Another random thought. During that time period, I also had a BUNCH of random reboots.
Maybe on other devices 95% user error might be closer.
But, not on my Gnex! What if you bought a completely new phone and have not installed any apps. The first time you open up the stock browser and use it for 5 mins or so on 4G LTE next to the cell tower -75 db stationary and still lose connection of both data and voice with "the triangle of death" on 2 separate GNex with 2 new SIM cards? Is this a bad batch? To me, "bad batch" is when we say 1/100 is a faulty device but this is almost reversed with GNex. We should exchange devices until we find a "good batch"
All I am saying is we all should be a little more compassionate for people like me. A lot of problems are made by users, sure. But it sure isn't 95%....It's more like samsung/google/vzw 60% in this case..
I hope I shed a little light on all the users that did not create user errors yet still have radio problems and VZW keep telling us to wait because issues are going to be addressed with the supposed firmware update that should have come in Feb, now March. Now...I don't know when.
Thank you for your post though, you rock
With anything, even product reviews, the people that have issues always make up the vocal majority. No one talks about how things work the way they should.
If my phone truly dropped 4G as often as it did when I had this application conflict, I'd be in the Verizon store every day until I either had a replacement or got banished from the store. If Verizon told me that it was "normal" and to live with it, I'd pay a visit to management at a different Verizon store and pay an online visit to the BBB. If that didn't do any good and I was really REALLY bored and had nothing better to do, I'd probably draw up a letter to Verizon's legal department about the liability Verizon could have when a consumer can't call 911 in the middle of the night because the radio crashed.
I still think it's an incompatibility hiccup with ICS more than necessarily an issue with Verizon's LTE network. I see GSM owners complaining too. And, as I said in the OP, I can only speak for a "stock" 4.0.4 bootloader/modem/radio experience. I've seen posts from people talking about how their problems have disappeared since making the move from 4.0.2 to 4.0.4. All I can speak of from my own experiences is that I've never had a problem from any version of ICS other than what I experience.
Come to think of it, I think I'll defrost all three of those apps and see what happens, especially since the phone in my hotel seems to be in working order.
OK, in the couple of hours since I've defrosted my cocktail of apps I've:
Opened the Facebook app, watched it poll for GPS and lock, then closed the Facebook app only to have GPS stuck on. Once I went into Settings > Apps > Location Services and tried to uncheck "GPS satellites" it rebooted. After rebooting, the phone showed 4G and a connection to Google's servers but I couldn't browse or use any app that is web based (like speed test, gmail, etc). After about 30 minutes of trying, I rebooted again and everything was fine. I have a feeling it's related to Real Signal looking at the plethora of stuff it monitors and that it's starting up on boot.
That's all I personally care to see. Needless to say, they're all frozen again.
I don't think there is a problem with real signal, I only installed it after having these problems to start with.
Since I got my nexus it works randomly drop voice and data. People would call me and get a fast busy signal. I tried many different radios and they all behaved the same. I switch my network to CDMA only and haven't dropped data or voice in two days.
Sent from my Galaxy Nexus using xda premium
On 4.0.4?
I don't think it's necessarily just Real Signal. I think it's multiple apps polling data from your radios. After a few more days, I'll go through them one by one. So far in my experiences on my setup, there is something up with the combination of those apps.
Again, there's a solid chance that a combination of other apps could give other people similar issues.
I will say this, even if I had problems before installing those apps, this particular cocktail would only make them worse.
It's not ICM
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Woodk1 said:
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Click to expand...
Click to collapse
Yes, indeed.
I am very surprised to not see one yet!
It means all of us with this issue is actually being very patient at the moment.
Again, for anyone who does not have this issue at all, and curious to find out what issue we all are actually describing here by LTE Connection Drop + Voice Drop is:
http://code.google.com/p/android/issues/detail?id=24345
Man, why does everyone always pull the "class action lawsuit" line?
Firstly, you're not going to do diddly squat legally about it, so stop kidding yourselves (and us) when you say that you are.
Secondly, no service you pay for is "guaranteed" to have 100 percent uptime. My Comcast internet connection goes out every 3 months or so anywhere from 5 hours to one day. Do you think I have legal grounds to sue them? Nope. When a thunderstorm rolls in and you lose power for 12 hours, can you sue your electric company? Nope. In fact, I'm pretty sure in most ToS contracts or forms that you sign, it states that they do not guarantee you anything.
LTE is a relatively new technology, and Verizon is the first one to offer it. There's going to be hiccups and growing pains. It's been a year and it's A LOT better now than it was back when it started. 4 years ago we were all happy to get something faster than EDGE speeds, and now we get connections capable of 40/50 Mbps down at times and people are still unhappy.
I understand people's frustrations with the network/switching issues that are occurring between CDMA and LTE. But we live in an age where everyone feels entitled and important enough to immediately sue another company at the drop of a hat.
Here's an idea: If you are faced with severe LTE switching issues and it's a continuing problem, call up customer support. Tell them what is going on and let them help you. Yes, you are past your 14 day return policy, but you have one year of a device warranty, they will ship you out a replacement device. Since your Nexus works fine and your wife's does not, it leads me to believe that it's not a network issue in your area, and either: A. Your wife got two dud Nexus' in a row, which sucks but is not unheard of. or B. Your wife is using some sort of app or service that interferes with the radios. If you still have the issue after the 3rd replacement, call them up again and explain, and they just might be able to give her a different device altogether if the Nexus isn't working out for her.
Dear MMcCraryNJ,
hear my long plea if you have the time. If you don't that is okay.
Firstly, I am so glad you seem to be not affected by this issue on your GNex.
Every single day, I wish I was in your shoes.
On the brighter side though, with LTE Data/voice drop & severe vertical banded screen & one-way-microphone outbound issues, I have come to join in XDA forum. I've also gotten to know countless VZW / Samsung customer service representatives at all levels as well as local store customer service agents.
Secondly, I, and I am sure most of all the other GNex users with above issues, know that no product & service is guaranteed to work perfectly with 100% uptime. Personally, it takes a significant defect of any product for me to call customer service at all. I am one of those, who actually try to live with products that have minor flaws everyday. If GNex did drop my LTE 3-4 times daily, I'll live with out much complaint let alone 3 months that you've mentioned. 3 months of uptime would be heavenly, but I'll actually be perfectly fine with 3 hours uptime. Sadly, my uptime has been 5-10 minutes with LTE. If my one-way-outbound microphone cut off issue happened 1 out of 10 calls, I'll live happily. Sadly, nearly every other call makes my voice into a robot and I have to call back again.
I am personally coming from Droid Eris long long time ago when Android first came out with newest 3G technology back then. Eris wasn't issue free but my satisfaction with what I got was pretty much 95%. You see, as long as a product performs what it claimed to perform 60-80% of the time, I am happy. Claim and advertisement that Verizon made with CDMA Galaxy Nexus in the US as "The latest 4G LTE Pure Google ICS Smartphone meeting the most reliable 4G LTE network in the world" caught my attention, as many others, to actually decide to choose this new phone with my 2 year contract over countless androids that came out in the past 3 years.
Again, our frustration that is described on these post is described in detail here (http://code.google.com/p/android/issues/detail?id=24345) it is not a LTE / 3G switch issue only. Switching issue is very small part of this problem. I will not go into any detail of one-way-microphone cut off issue at all, due to its unrelated nature on this particular post.
Just as you've suggested naively, your suggestions in order that you wrote them in were exactly the steps I thought and took from very first day I purchased GNex back 4 months ago from a local verizon store. I have stopped in at the verizon store to get exchanges of the actual device, SIM card. None of these replacements solved the data/voice drop issue. I am all talking about stock 4.0.2 without any apps installed on any of these GNex. It can't possibly be the bad batch as I received batches that were produced in completely different months. I loved whatever was promised with GNex so much that I was determined to find the one for me as no other devices Verizon offer at the time appeal to me at all. As 14 days has passed, the local verizon literally told me to 1) wait for the update 2) root your device to all different kind of ROMs and Radios 3) call VZW customer service. Which all of the advice I followed, I am still waiting, none of the ROMs and radios solved the issue.
Ever since then, I've been calling VZW and Samsung (when VZW transferred me), and talked to numerous customer service representatives at all different levels. (Level 2 & 3 and at some points I've been transferred and escalated twice to a person really higher up) With my efforts, I was actually able to tag all my calls, and send them screenshots (via e-mail), and follow through to actually make above mentioned issues officially put on VZW technical bulletin. It is a huge improvement, because when I first called about these issues, they told me "They've never heard of these issues.". Now, after all of our efforts, they admit there's over "120 technical bulletin reportings on these issues."
You do think that it is so easy to get a refurbished factory replacement phones with all my history right?
The answer is sadly No. They've been literally telling me to wait a little longer no matter how much I requested them to get me a replacement device. They are indeed very hesitant to keep replacing devices for all of us especially now days where the supposed update is going to resolve these issues. And on my end, I want to see first if the software fixes it, because I am literally burned out to get another screen protector install everything again, etc. Now the official answer is wait....for the update. If they don't keep their last promise of March update to resolve this issue, that is when my patience will run out and I'll jump to a different device. Although, I love this phone....
This is the longest online posting of any sort in my life ever. I hope this somewhat gives you a new perspective on what unlucky GNex user like myself had to go through in the past 4 months due to getting "bad batches"
Trust me, I hate to live in a society where anybody can talk about law suits against anybody. But, this was one of my first moments that I literally felt like I was hopeless & got betrayed by VZW / Samsung / Google. I started to fantasy about way to make them responsible for this poor product and service. All I wanted was at least 60 percent working "4G LTE Smartphone". (4G LTE is turned off due to connection drop, Phone is unusable as business purposes due to frequent one-way-cut off). After $299 and 2 year contract with $75 monthly service bill of 4 months with all the time I spent to help VZW/Samsung with this issue as a customer, my wildest dreams of thinking of participating in a class law suit, which will never happen, actually make me feel a little bit less helpless towards these major corporations as a customer.
Thank you for hearing my plea. I sincerely apologize for the length of this post.
Hope more of us can enjoy this great GNex in the near future.
After all, I love this device, I love this XDA forum and GNex community. I wouldn't want to switch to a different device just yet
About 10 days ago I decided to upgrade my 2012 Nexus 7 to a 2013 model, as I felt the deal on offer was too good to refuse, and there was plenty of life in the tablet yet.
Having kept a close eye on the forums, I was all too aware of the numerous reported display issues, but naïvely hoped that these were no longer such an issue - and that subtle revisions over time would have all but eliminated them.
Initially I thought I was fine, but when setting up Nova Launcher, I did notice on several occasions that a long-press on desktop icons failed to register, and I had to try repeatedly before eventually being able to do such things as rename folders.
Everything else seemed fine, and the display looked good, but I decided to use the “Display Tester” app to double check a few things. Multi-touch seemed fine - 10 touches registered without problem, but the Gamma test screen sent the device crazy - with phantom touches all over the place.
So I read a little more and confirmed others had seen both these issues, but at the end of the day if they only happen rarely, or when displaying some very specific images on screen, should I really worry?
I thought I’d see how it goes, but now I’m finding other subtle issues too. Playing Real Racing 3 for example, where you’ll spend most of your time with the thumb on-screen accelerating, every other race or so the touch de-registers, and you have to lift your thumb off and push it down again to keep the car going... Now I know this never happened on my 2012 Nexus, and it ruins the game play as you invariably don’t notice until other cars start overtaking!
So my question is, is this normal? Were the original issues ever resolved satisfactorily, or do you just live with these issues? I love the tablet otherwise, and would take it back today if I felt confident I’d get a better one, but it concerns me that the one I have may actually be quite “normal” and I may end up with one that’s even worse. It may be fine 95% of the time, but that 5% is really spoiling the experience.
Before returning the device I was considering trying sfhub's fix... Do you think it's likely to help such issues?
Your thoughts on the matter would be greatly appreciated.
Honestly, I think that any issue with a Nexus 7 is to be somewhat expected. My nexus 7 2013 had that fault for about a month when I got it, but I think it slowly went away after about 6 months. Now the only issue with my device is one speck of duct under the screen (which I can live with). But to be honest, it is very subjective. I am pretty sure that the fixes never fix the problem for very long, so you may have to wait this one out. If you play games a lot and this affects you, then return it and replace it. I hope this somehow helps you, I know how annoying it can be to have a faulty device!
I never had any of those issues and bought 2 used off of eBay, one for me and one for my wife. I even broke the screen on one and replaced it myself. And I've never done it before. So I would not say those issues are normal. I think that people who's nexus' work fine don't post about it as much as those with issues. Just my opinion.
Thanks for the feedback... I'm in two minds. On the one hand I have a near perfect device, but on the other it can frustrating, and it shouldn't be (i.e. it's a brand new device - not a refurb. unit). The danger with procrastinating is that as these are nearing the end of their life as "current" products, if I leave it too long I'll have no choice but to send it back to the manufacture, as I won't just be able to switch it in store. I'd be even less confident about a resolution then - especially as the symptoms are relatively rare and specific.
You're quite right though, that people without issues are less likely to shout about it than people with them - so the level of responses also tend to suggest that this isn't "normal" or expected... I feel an exchange may be in order. Worst case, I get one that's not as good - but I'll always have the option to return it.
If its brand new and under warranty, definitely exchange it.
You can also try this. A customer paying good money shouldn't have to, but it can be easier than going through exchanging. TS10 worked great for mine, making touches sensitive like on my first-gen N7.
http://forum.xda-developers.com/showthread.php?t=2428133
Thanks for the feedback - I exchanged it on Friday for another. Was anticipating I might end up with a slightly newer, perhaps subtly revised unit, but ended up with one from an even older batch - July 2013 as opposed to September 2013.
Never mind the age though, this one's definitely better. No lost touches, and altogether more reliable. :good:
Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....
outamoney said:
Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....
Click to expand...
Click to collapse
I'm in the exact same situation as you. I still have the original model Note 7 and have tried multiple times to exchange it for the "safe" model. At this point given the evidence, I believe that both models are equally safe (relatively). New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000. I'm not sure if the failure rate on the updated models went down, but I feel that failure rate in general is about on par with other devices.
I have read about Apple phones in the past catching on fire. The difference is Samsung tried to be super responsible in this situation by taking ownership and the media and such has definitely exacerbated the situation. Apple never took ownership of any of the battery failures that happened with their devices, and mostly blamed it on the user using 3rd party accessories and such.
I may be wrong, but I believe the issue was blown out of proportion. I'm not saying the phone is safe, but I'm also not saying that this phone is way more unsafe than any of the others.
So, given the statistics and history of the two different models, if you disable fast charging on the device I believe the two different models are on equal ground as far as failure rates go. Which are higher than they should be but still fairly low.
jal3223 said:
. New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000.
I may be wrong, but I believe the issue was blown out of proportion .
Click to expand...
Click to collapse
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.
outamoney said:
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.
Click to expand...
Click to collapse
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party
elliwigy said:
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party
Click to expand...
Click to collapse
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.
jal3223 said:
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.
Click to expand...
Click to collapse
they had a lot more reports with v1.. I think it was 90+ then v2 I think is under 10... not sure if time is the culprit or not however
I am going to attempt to install a Galaxy Note 5 battery into my Galaxy Note 7. If I pull this off I will be showing step by step details of how I accomplished the process. This should solve our problems and it is mind boggling why Samsung hasn't considered this as an option. I will take a loss of 500 mah over having to give this phone back any day.
Waiting...
This may be interesting.
But won't you void your warranty?
Watching
Sent from my SM-N930P using XDA-Developers mobile app
I really think something apart from the battery went wrong
Sent from my LG-D855 using Tapatalk
---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------
Chances are that some circuit that's already connected to note 7s battery. Or the circuit that connects battery to device as a bridge from devices ene at some point. I hope it not true, but honestly if it was easy of a battery issue, Samsung would have got it already . Some circuital problem I bliv.
Sent from my LG-D855 using Tapatalk
http://www.phonearena.com/news/The-...ecisely-why-its-batteries-are-failing_id86474
I suspect this might be the prime culprit. Basically, it's a design flaw. In an attempt to make a aesthetically appealing phone, the integrity of the battery is compromised.
I'm with OP. If the Note 7 can be salvaged by reducing the capacity of the battery, I'm in.
Power banks are readily available, a slightly smaller battery is not an issue for me.
BozQ said:
http://www.phonearena.com/news/The-...ecisely-why-its-batteries-are-failing_id86474
I suspect this might be the prime culprit. Basically, it's a design flaw. In an attempt to make a aesthetically appealing phone, the integrity of the battery is compromised.
I'm with OP. If the Note 7 can be salvaged by reducing the capacity of the battery, I'm in.
Power banks are readily available, a slightly smaller battery is not an issue for me.
Click to expand...
Click to collapse
This post is kinda making do much sense right now .. +1
Sent from my LG-D855 using Tapatalk
I think if it was something this simple, they would have replaced the batteries and paid people compensation for the loss of performance compared to sold specification.
good stuff yo! try to record videos when you turn it on
Only 96 out of 1.9 million in the US have had fire issues. Seems like the phone is perfectly fine to me.
DeMi-GoD said:
Only 96 out of 1.9 million in the US have had fire issues. Seems like the phone is perfectly fine to me.
Click to expand...
Click to collapse
96 phones exploded out of 1.9 phones! that's feggin dangerously scary, you need to return your phone! bcos i know better than you! do it now! today! now!
I was about to pull the trigger on a Note 5 battery, but there are some things I wanted to address and think about before I do.
-This phone will never get any updates, ever. That means no android 7.0.
-There will likely be no warranty of any kind if something stupid were to go wrong.
-My house could burn down if this process fails.
-Will this affect my carrier insurance or Jump On Demand with tmobile?
-The gear VR is deactivated due to the danger.
-Me completing this process may encourage others to do so, only for all of us to find out later that it didn't work and they start bursting into flames again. I don't want to be in the middle of all that.
-The phone will essentially be of no value pretty quick here and I don't know how I feel about carrying around something that is worthless while making payments on it.
-They could IMEI block them all after I go through the painfull process of swapping batteries.
Just some things to think about before moving in either direction.
I was about to pull the trigger on a Note 5 battery, but there are some things I wanted to address and think about before I do.
-This phone will never get any updates, ever. That means no android 7.0.
-There will likely be no warranty of any kind if something stupid were to go wrong.
-My house could burn down if this process fails.
-Will this affect my carrier insurance or Jump On Demand with tmobile?
-The gear VR is deactivated due to the danger.
-Me completing this process may encourage others to do so, only for all of us to find out later that it didn't work and they start bursting into flames again. I don't want to be in the middle of all that.
-The phone will essentially be of no value pretty quick here and I don't know how I feel about carrying around something that is worthless while making payments on it.
-They could IMEI block them all after I go through the painful process of swapping batteries.
Just some things to think about before moving in either direction.
I think your real loss is the warranty for your Note 5, which in most accounts, should still be valid.
It is worth an experiment I suppose and if you want to document it, you could always leave a disclaimer first.
Generally, I won't recommend it. But ultimately, it's your decision.
BozQ said:
I think your real loss is the warranty for your Note 5, which in most accounts, should still be valid.
It is worth an experiment I suppose and if you want to document it, you could always leave a disclaimer first.
Generally, I won't recommend it. But ultimately, it's your decision.
Click to expand...
Click to collapse
Well I would just buy the battery from a note 5, not an entire phone.
Awe c'mon man, take one for the team! I was going to remove my battery entirely and strap on several 18650's to the back of it. But that would send the wrong message in public. Somebody would call the bomb squad even though it'd probably be safer than it is right now....
All kidding aside I think you are wise to stop.
I still may do it lol. At this point it could just be an experiment. The problem is there may be no way at all of ever knowing whether it worked. I could go on using this phone untouched and it works for the rest of my life. Think about it 93 of 1.9 million. It may never go up in flames with the note 7 battery let alone the note 5.
I think your smart enough to do it safely. give it a go! you're half way there mate.
never ever ever updates? really? never? not even the slightest chance of a lone wolf dev making a new 7.0 rom?
high chance of your house burning down? is there nothing you can do? maybe charge your phone in a small ceramic square bowl/dish? next to an open window? is there really no safe measures one can take?
warranty issues? has warranty ever been a issues on this forum? some countries void your warranty just for rooting your phone!
worried about upsetting others are you? well just holding on to a note 7 has already upset me, shame on you for upsetting a stranger
the phone is only useless if you don't have a use for it any more. unless your easily affect by what others think of you.
imei block? possibly but you'll get timely warming and a refund if it does happen, and even after months later they'll still accept your phone, bcos there's a hill billy out there who bought his note 7, went deep into the woods for a croc and toad hunt and 6 months later returned only to get all these recall messajars...
We'll see lol