Related
Hey guys.
In the market for the One X. Thing is, I don't wanna get one with the WiFi issue. Is there info somewhere on the serial numbers of the bad batch of phones? Is there any way to know that the one I'm getting is good or not?
max_3000 said:
Hey guys.
In the market for the One X. Thing is, I don't wanna get one with the WiFi issue. Is there info somewhere on the serial numbers of the bad batch of phones? Is there any way to know that the one I'm getting is good or not?
Click to expand...
Click to collapse
As of a tally taken two weeks ago there were 160 people in the Wi-Fi thread that reported their phone was suffering from the issue. If you double it for people with the issue not documenting it in the thread, that's 360 phones out of about 5K owners on the forum. That's less than 10%.
If you look at the pictures of the phone disassembled, the issue appears to be from how the phone is seated in the chassis at the factory. The connectors are on the body of the phone while the antennas they are connecting to are on the chassis. In the Wi-Fi thread, people are told to "press on the back of the phone to see if it affects the Wi-Fi signal." The connectors use dynamic tension vs. springs. Since the part of the phone where the connectors are located wouldn't experience compression under typical use, that's an acceptable design choice. People artificially creating compression to "test" their phones could be causing the problem their testing for. The fix HTC is putting in place is simply spacers to prevent compression; real and artificial (people pressing on their phones). I have an early March-build phone that's been dropped six times and the Wi-Fi's as good today as when I got it. It's better than the i9100 it replaced and a G-Tab 10.1 I’m still using.
In anything mass produced, precision of assembly improves as more are built. So you could make the assumption later built phones are less likely to have defects. You’ll see references to HT23 and the like. The “3” in HT23 signifies “March” and so on. But the design of the Wi-Fi connectors aren't being changed and, based on the number of devices affected, you have a far greater chance of getting a phone with great Wi-Fi than one with a problem. There are plenty of differing opinions so educate yourself and make your own decision.
BarryH_GEG said:
As of a tally taken two weeks ago there were 160 people in the Wi-Fi thread that reported their phone was suffering from the issue. If you double it for people with the issue not documenting it in the thread, that's 360 phones out of about 5K owners on the forum. That's less than 10%.
If you look at the pictures of the phone disassembled, the issue appears to be from how the phone is seated in the chassis at the factory. The connectors are on the body of the phone while the antennas they are connecting to are on the chassis. In the Wi-Fi thread, people are told to "press on the back of the phone to see if it affects the Wi-Fi signal." The connectors use dynamic tension vs. springs. Since the part of the phone where the connectors are located wouldn't experience compression under typical use, that's an acceptable design choice. People artificially creating compression to "test" their phones could be causing the problem their testing for. The fix HTC is putting in place is simply spacers to prevent compression; real and artificial (people pressing on their phones). I have an early March-build phone that's been dropped six times and the Wi-Fi's as good today as when I got it. It's better than the i9100 it replaced and a G-Tab 10.1 I’m still using.
In anything mass produced, precision of assembly improves as more are built. So you could make the assumption later built phones are less likely to have defects. You’ll see references to HT23 and the like. The “3” in HT23 signifies “March” and so on. But the design of the Wi-Fi connectors aren't being changed and, based on the number of devices affected, you have a far greater chance of getting a phone with great Wi-Fi than one with a problem. There are plenty of differing opinions so educate yourself and make your own decision.
Click to expand...
Click to collapse
Thanks a lot! Really appreciate the info.
Update: Star this Android issue if affected: http://code.google.com/p/android/issues/detail?id=58401
I'm noticing intermittent bouts of erratic multi-touch on the Nexus 7 (2013) 16GB. I exchanged one device already hoping that it was a HW defect, but my second device behaves in exactly the same way.
Chrome, Dolphin, web-view, maps (especially maps) will often jump all over the place during pinch-to-zoom. Sometimes it works fine, but too often, it jumps zoom levels erratically. Edit: This also manifests as double taps and/or "ghost taps" when using the keyboard.
I've installed YAMTT (Yet Another Multitouch test) and I've observed the touch points disappear, change direction and even suddenly register a 3rd touch. None of my other devices do this.
I'm reluctant to exchange the device yet again, but I haven't read about anyone else who's witnessed this. Am I alone in observing this behaviour?
Edit: Here is a terrible video attempting to highlight what I'm seeing in YAMTT: http://www.youtube.com/watch?v=_ZRiMiNzs0U
And another video in Google Earth (fixed): http://www.youtube.com/watch?v=14cPiiM3Pwg
Someone else experiencing the issue: http://www.youtube.com/watch?v=Xpl26UgcuSs
FINAL UPDATE: I exchanged the device again and the issue is gone (so far). My advice: if you're experiencing this issue, return it. If it continues to happen, return it again until it works.
As a side note, for those experiencing the mushy/hard to press power button, that issue was fixed for me as well.
Final Update Part 2: I am sad to say the issue is still present after all. I'll admit that it is less prevalent than with my first two N7s and the "jumps" are less severe. However, it's still there and I'm not prepared to live with it. Therefore, I am returning the device to get my money back. I'll keep up to date with this issue, and I'll likely buy it down the road when a clear resolution presents itself. I know it would be a great tablet without this problem.
To recap my experience:
First N7 had erratic multi-touch, stiff power button, keyboard and other touch screen issues. Exchanged.
Second N7 had a good power button, but the erratic multi-touch and keyboard issues were still present. Exchanged.
Third N7 had a perfect power button and no keyboard issues, but the erratic pinch to zoom was still present (though less severe). Returned.
it happen to mine while typing nothing a software update can't fix or even better custom rom
Speedy Gonzalez said:
it happen to mine while typing nothing a software update can't fix or even better custom rom
Click to expand...
Click to collapse
You're probably right. I was just concerned that no one else had mentioned it. I find this behaviour quite annoying.
Does the issue go away if you actually held it with the other hand (going by video)? Sounds like the behavior of the 1st gen N7.
mi7chy said:
Does the issue go away if you actually held it with the other hand (going by video)? Sounds like the behavior of the 1st gen N7.
Click to expand...
Click to collapse
I'll try that, thanks. I have the original Nexus 7 as well and never noticed this issue. Could you elaborate a little? Was the issue eventually resolved?
JayBomb999 said:
I'll try that, thanks. I have the original Nexus 7 as well and never noticed this issue. Could you elaborate a little? Was the issue eventually resolved?
Click to expand...
Click to collapse
It's designed to be used on a grounded surface either held in hand or on a grounded surface. It's an electrical behavior so I doubt software would change that. Please try held in hand and report back.
JayBomb999 said:
I'm noticing intermittent bouts of erratic multi-touch on the Nexus 7 (2013) 16GB. I exchanged one device already hoping that it was a HW defect, but my second device behaves in exactly the same way.
Chrome, Dolphin, web-view, maps (especially maps) will often jump all over the place during pinch-to-zoom. Sometimes it works fine, but too often, it jumps zoom levels erratically.
I've installed YAMTT (Yet Another Multitouch test) and I've observed the touch points disappear, change direction and even suddenly register a 3rd touch. None of my other devices do this.
I'm reluctant to exchange the device yet again, but I haven't read about anyone else who's witnessed this. Am I alone in observing this behaviour?
Edit: Here is a terrible video attempting to highlight what I'm seeing in YAMTT: http://www.youtube.com/watch?v=_ZRiMiNzs0U
And another video in Google Earth: http://youtu.be/14cPiiM3Pwg
Click to expand...
Click to collapse
I've got this a little bit, glad I'm not the only one with the problem, mine only does it when I hold it above me and use it lol. Everything else is fine with mine so I'm keeping it.
Are you sure this is a software issue?
I remember back when I had an HTC Desire, it had multitouch issues but the fault lay with the digitizer and no update could fix it.
mi7chy said:
It's designed to be used on a grounded surface either held in hand or on a grounded surface. It's an electrical behavior so I doubt software would change that. Please try held in hand and report back.
Click to expand...
Click to collapse
I've tried gripping in both hands, from the bottom bezel, on the table and on the couch. Still, I see this behavior. It's not constant, but it's prevalent enough that I don't know if I'm going to keep it.
It sucks because otherwise I really love it.
I dunno. I'm seeing weird anomalies with mine. Moving 2 fingers around, a random 3rd pops up.
Hopefully just software woes. The Galaxy Nexus did this, N7 did this, and now the new N7. Its rare. Haven't had a problem.
Sent from Nexus 7 FHD from XDA Premium HD
I just ran the same tests you did using YAMTT and did not have any of the same problems. I haven't noticed any mutlitouch issues either.
JayBomb999 said:
...
And another video in Google Earth (fixed): ...
Click to expand...
Click to collapse
I found this thread looking for someone else who was having the problem I was - my device was doing exactly the same thing in Google Earth. Thanks for posting it!
Oddly enough now that I've found this thread, the device isn't doing that anymore. It's tracking perfectly in Earth and also in YAMTT.
It tracks fine when being held in one hand, on a grounded or not surface, when touched with one hand or two.
Very odd.
I had this issue with my 1st n7 2nd gen (which i bought yesterday). I returned it to bestbuy and got a new one which seems to be fine.
GreenXSniper said:
I had this issue with my 1st n7 2nd gen (which i bought yesterday). I returned it to bestbuy and got a new one which seems to be fine.
Click to expand...
Click to collapse
I've already exchanged it once and each had this issue. I think I'm going to try again tomorrow. I'll report back.
I had a similar issue with google earth on my 1st gen N7. I can't test it anymore, tho, because its sitting at the bottom of a lake. But it would randomly zoom out or in like crazy or jump halfway across the world.
I have this issue extremely annoying. My keyboard double presses letters at times, zooming I have ttrthe problem, trying to long press a link I also get it unregistering touch
I hope this. Is. Software I don't waqmt to return this. Otherwise perfect device. You can see it happoening as I try to type
This actually happened to me for the first time about an hour ago. As said before, I hope this is a simple software bug, and not some serious hardware issue. Quite frankly, I have a feeling that going through a return is going to be messy, as I've bought mine from my local Gamestop.
From a GNex
carfreak715 said:
This actually happened to me for the first time about an hour ago. As said before, I hope this is a simple software bug, and not some serious hardware issue. Quite frankly, I have a feeling that going through a return is going to be messy, as I've bought mine from my local Gamestop.
From a GNex
Click to expand...
Click to collapse
The gentlemen that posted the following video said he exchanged his device and the problem went away: http://www.youtube.com/watch?v=Xpl26UgcuSs
I know it's only one person, but this leads me to believe it might be a hardware/quality issue. I have exchanged mine once for this issue already (Best Buy) and it was extremely easy. I am going to exchange one more time and will report back my findings.
nba1341 said:
I have this issue extremely annoying. My keyboard double presses letters at times, zooming I have ttrthe problem, trying to long press a link I also get it unregistering touch
I hope this. Is. Software I don't waqmt to return this. Otherwise perfect device. You can see it happoening as I try to type
Click to expand...
Click to collapse
I didn't mention the keyboard issue. I too am seeing ghost taps when typing.
Hmmm. No ghost taps here. I've been on xda a lot since I got this.
Not good though. Could just be a bad batch. Seems like the dead spots would be caused by a hardware issue... Bad connections or something.
Sent from Nexus 7 FHD from XDA Premium HD
As to why phones were "exploding". It seems the original reason they had of a battery manufacturing fault is now incorrect and it seems theres a more inherent design fault? Incredible that the biggest phone manufacturer in the world, with all their engineers couldn't figure it out.
B3501 said:
As to why phones were "exploding". It seems the original reason they had of a battery manufacturing fault is now incorrect and it seems theres a more inherent design fault? Incredible that the biggest phone manufacturer in the world, with all their engineers couldn't figure it out.
Click to expand...
Click to collapse
They either haven't figured it out, or they HAVE, and it's something in the hardware (motherboard, etc) that it's too late/costly to reengineer.
Read a story that mentioned it might be the SoC, designed it to push more power to the battery then it could end up handling. Really liked this phone.
Sent from my Samsung Note 7 using Tapatalk
macawmatt said:
Read a story that mentioned it might be the SoC, designed it to push more power to the battery then it could end up handling. Really liked this phone.
Click to expand...
Click to collapse
If it was that wouldn't they just push a update to limit the fast charging? Or the soc I gotta assume that's all handled by software.
I don't think it's a coincidence that the battery was the smallest and crammed into a tiny space, more than any other phone. There's got to be something in that, perhaps any sort of pressure on the back was causing some sort of battery failure.
All sorts of theories today. Too thin of separators in the batteries. Curve edge of the screen causing it. Fast charging. Some new battery fault etc. I don't think Samsung found the problem.
They better. I hate them so much now... They wasted months of my life, wanting and not getting this phone. Some of you had at least a chance to test it out feel it.... All I got is 10 min. with demo unit. If they keep it to them self a lot of ppl will think they have no clue and the same problem could happen to S8. What phone to get now until S8E is out. I need excellent maniera, water resistance and of course big screen...
It sounds like they don't know yet and can't replicate the problem in their testing. But I don't know if we really know much of the whole story. There could be multiple reasons we never get a clear answer. I think the recall was forced upon them not only to limit litigation, but from the governmental agencies. It is sad that by far the best overall phone ever made to date has been killed off. There really is no other phone that combines all the great things the N7 has going for it.
htcplussony said:
All sorts of theories today. Too thin of separators in the batteries. Curve edge of the screen causing it. Fast charging. Some new battery fault etc. I don't think Samsung found the problem.
Click to expand...
Click to collapse
I agree with you. Canning the entire product is such a drastic move. If they knew what the problem was, ANY fix would surely cost less to engineer in, than they huge damage to their reputation, to their competitive position in the market (no flagship product available) and the hard cash costs of product write off.
But if they just can't figure out what's causing this problem, what could they possibly do? Could they say "you know, we don't know what the problem is, but just keep using them and sorry about the occasional fires". Obviously not. How about do *another* recall and risk Version3 phones catching fire too? Clearly they can't do that either.
Then consider the following: This problem is *rare* - 1 in 100,000 units perhaps? And it didn't show up in any pre-production tests nor QA checks. Add in the fact that they thought it was the battery, and then found out that it was not.
All this leads me to believe that they haven't yet figured out with 100% certainty what the problem is.
It must be something that renders the design faulty meaning they'd have to remanufacture the device to fix it something that probably generate quite a wait time for people to exchange it. So canning it is a better option.
The two things I think are most suspect is
a) overheating either via charging or just using the SoC to the max and causing heating issues.
b) casing is designed in such a way that puts undue pressure on the battery.
Either way it's a expensive fix, sure you could firmware update it to slow the charge speed or down clock the processor but then you've got a whole other issue of false advertising. You paid for X and got Y.
Sent from my LG-H901 using XDA-Developers mobile app
evo4g63t said:
It must be something that renders the design faulty meaning they'd have to remanufacture the device to fix it something that probably generate quite a wait time for people to exchange it. So canning it is a better option.
Click to expand...
Click to collapse
Not necessarily.
As I said above, what if they can't be certain what the problem is? What should they do then? The only option in those circumstances would be the course of action they have taken.
This is imho the most likely scenario. Clearly, they didn't think there was anything wrong with it when it was launched, and after extensive r&d and product testing. They thought the product was fine.
And now they are faced with trying to identify *with certainty* what's causing 1 unit in around 100,000 to fail, when all they get back to test are charred remains. They could not risk a second failed recall, based on not being 100% sure what the problem is, so their ONLY option in those circumstances would be to withdraw the product.
One things for sure, when they eventually do find out what caused it, a whole department is getting sacked! I bet there's a lot of nervous Samsung design heads just now.
teegunn said:
It sounds like they don't know yet and can't replicate the problem in their testing. But I don't know if we really know much of the whole story. There could be multiple reasons we never get a clear answer. I think the recall was forced upon them not only to limit litigation, but from the governmental agencies. It is sad that by far the best overall phone ever made to date has been killed off. There really is no other phone that combines all the great things the N7 has going for it.
Click to expand...
Click to collapse
Now they have 2 million phones they can test and replicate the problem. I foresee huge electric bills for them charging and discharging 2,000,000 phones.
Chippy_boy said:
Not necessarily.
As I said above, what if they can't be certain what the problem is? What should they do then? The only option in those circumstances would be the course of action they have taken.
This is imho the most likely scenario. Clearly, they didn't think there was anything wrong with it when it was launched, and after extensive r&d and product testing. They thought the product was fine.
And now they are faced with trying to identify *with certainty* what's causing 1 unit in around 100,000 to fail, when all they get back to test are charred remains. They could not risk a second failed recall, based on not being 100% sure what the problem is, so their ONLY option in those circumstances would be to withdraw the product.
Click to expand...
Click to collapse
Another theory is that in the first instance they jumped over a few tests to get the phone out before the iPhone 7, then in the first recall they didn't actually fix anything, just did a firmware update (how else would they have replacement devices within 1 WEEK?). The update turned out not to be enough, whatever was wrong with a certain percentage wasn't fixed by making them charge slower or less.
And now you can't really do a second recall and expect people to trust the same device. They are saving face, call it a loss, and move on.
Do any of you think that this is full of crap though? Samsung has NOT completed their investigation yet, and until they do, for all anyone knows, the devices could have failed due to mistreatment by their users. Out of FOUR MILLION phones, only 35 explode, and of the replacement units only 7? Lets say the first generation was bad, and only count the replacements. 7 out of 4 million. That is a 0.000175% chance of your phone exploding. So, they discontinued the line for less than an even 1% chance, without waiting for the investigation to be completed? COME ON. PLUS, some of the people who had exploded note 7s REFUSED to return them.
PhoenixJedi said:
Do any of you think that this is full of crap though? Samsung has NOT completed their investigation yet, and until they do, for all anyone knows, the devices could have failed due to mistreatment by their users. Out of FOUR MILLION phones, only 35 explode, and of the replacement units only 7? Lets say the first generation was bad, and only count the replacements. 7 out of 4 million. That is a 0.000175% chance of your phone exploding. So, they discontinued the line for less than an even 1% chance, without waiting for the investigation to be completed? COME ON. PLUS, some of the people who had exploded note 7s REFUSED to return them.
Click to expand...
Click to collapse
What I want to know, of the ones that have malfunctioned, were they damaged prior? Dropped, thrown, etc. That would definetly play into the battery cells being smashed together regardless if they are on or off. I don't buy into the heat thing entirely, because I've taken mine into the sauna 3 times and it's still fine. I'm debating what to do. I love this phone. My first note. I'll be near a best buy Friday, so I'll go in and see if anything pegs my interest and goes from there. I'd be happier if I knew when they were going to release something with a stylus. Absolutely love that thing.
taz1458 said:
What I want to know, of the ones that have malfunctioned, were they damaged prior? Dropped, thrown, etc. That would definetly play into the battery cells being smashed together regardless if they are on or off. I don't buy into the heat thing entirely, because I've taken mine into the sauna 3 times and it's still fine. I'm debating what to do. I love this phone. My first note. I'll be near a best buy Friday, so I'll go in and see if anything pegs my interest and goes from there. I'd be happier if I knew when they were going to release something with a stylus. Absolutely love that thing.
Click to expand...
Click to collapse
I also say theres another possibility. There's been incidents with USB-C cables in the past.. cheap cables.. (the kind you buy in gas stations and pharmacies). They've caused the ports to get damaged and devices (of all types) to explode because wires inside are hooked up incorrectly. How do we know that this wasn't caused by someone using a faulty third party accessory?
PhoenixJedi said:
I also say theres another possibility. There's been incidents with USB-C cables in the past.. cheap cables.. (the kind you buy in gas stations and pharmacies). They've caused the ports to get damaged and devices (of all types) to explode because wires inside are hooked up incorrectly. How do we know that this wasn't caused by someone using a faulty third party accessory?
Click to expand...
Click to collapse
My point exactly. That was the rumor the first time. I got the Samsung cables, so I'm not worried about that. Just really wonder if dropping them, damaged the case, which put pressure on the battery and short circuited it.
Here's the thing, SAMSUNG themselves cannot replicate the situation. No matter HOW they tamper with the phone. I guarantee you they're not using these bad third party cables, or trying to operate a device with partially compromised firmware from a failed root attempt, or other things they tell their end users NOT TO DO. I guarantee you they're testing the phone (other than dropping it and water tests) within the specs of what they tell users is okay to do with the phone.
Here's the other thing, the video of a 'note 7' supposedly catching fire in someones home... 1: its in black and white, 2: its a security camera in someone's living room. 3: YOU NEVER SEE THE ACTUAL PHONE ON THE CAMERA. For all we know she's holding a smoking piece of toast. Plus, consider that an overheating li-ion battery is a chemical reaction and that smoke usually means the battery has been punctured. HOW and WHY is she still holding it?
In hindsight, considering my Note 4 would overheat DRASTICALLY on the Gear VR Innovator Edition so much so that the Phone would produce a message to warn to let it cool down, Samsung Engineering should have seen this coming.
Maybe it was a Godsend, INTRUSIVE IRIS Scanner and all.
Or maybe it WAS a conspiracy, like nothing really was at fault, the powers that be saw something in the Note 7 they were not in favor of letting the public/consumer get their hands on.
We may never know. But rest assured something seems not quite right about the whole fiasco. Even a social engineering experiment.
Interesting read guys... I have my note 7 now for 6 weeks. Had the first one too before the switch. Both of them worked/work fine. No overheating. I am not sure if only exinos cpu variants are catching fire. Over here in germany there are no fires at all. It is sad that this phone is canned, and for the remaining working ones, there will never be a a software update at all. This phone is by far the best phone ever. Truly.
Gesendet von meinem SM-N930F mit Tapatalk
When you look into the Note 7 recall and all of the information we have available, you have news outlets taking a biased point of view on the units. They have put words into both Samsung and the CPSC's mouth saying that the recalls are MANDATORY, that the Note 7 production has been permanently halted, and that the issue is the battery itself. In the meantime, Samsung themselves have announced that they CANNOT replicate the issue themselves, and the changing out of the battery would generally suggest that it was not the battery causing the problem. Plus, due to media coverage the issue has been severely exaggerated. According to the CPSC, only 96 units out of 1.9 million units sold in the US have been reported as overheating. In the two months since the release of the phone that is a 0.005% failure rate. That means the phone has a 99.995% chance of being perfectly fine. In terms of normal production, that would be considered a success by most companies. Samsung also has not announced anywhere on their site that production has been halted permenantly. They've said temporarily while they investigate. The investigation is NOT COMPLETE.
Now, if you take the battery out of the equation as the primary point of failure, there are three other points of possible failure that would be the most common cause to make the battery ignite. Those are software tampering, hardware tampering/error and the USB-C port/accessories.
Software: a partially flashed firmware could easily damage the charge rate systems to cause damage to the battery itself or damage the battery's protection board to the point where it can cause problems.
Hardware Tampering/Error: How many idiots have you seen on youtube sinking their Note7s to the bottom of a lake/river/pier, or drop testing them from heights that they are not rated for. Then count the # of people who replicate what other people do on youtube.. (Ghost pepper challenges anyone?)
USB-C Port/Accessories: USB-C has been under some controversy itself lately. Cheap USB cables have been sold that when used on devices damage not only the USB-C port, but also the power systems due to the cables being improperly wired. As well, the Note7 comes with USB-C accessories, one of which is a USB-A to a USB-C port adapter. This is used to use the unit AS a backup battery, or to attach flash drives to the unit and NOT to charge the unit. Many people have USB-A to USB-A cables. Imagine if someone used one of the faulty USB-C cables to charge the unit, or tried to use that adapter with a USB-A to USB-A cable to charge the unit. With only 96 cases reported of overheating, it's well within the number of people who don't understand technology enough to get the proper cables and/or use the unit up to spec. If the cable is not CERTIFIED by the USB-IF it could very well be a bad cable and have caused the issue.
What I'm saying here is look at the proof, look at the history of the devices you're attaching to the phone, look at human behavior, look at what the media's doing. We have people in this world who actually think TRUMP would make a good president. We have people in this world who snort condoms up their noses. It makes it completely possible that all 96 reported cases are 96 cases of users doing the wrong thing with their phones. It is very likely that out of 1.9 Million units sold in the US (according to CPSC), 96 of the people who bought Note 7s are simply idiots. (Plus there's a video of an idiot supposedly holding a Note 7 while the phone is catching fire. When a LI-Ion Battery overheats you can't hold it. not in your hands without receiving severe burns. Information below attached so you can see it all directly from the sources for the information on the Note 7 instead of from media locations.
Also, don't forget, some of these people with the phones who have overheated REFUSE to return them to Samsung for investigation. There is only one reason to refuse to turn in a destroyed device. If you tampered with it yourself.
Samsung Recall Info (showing its voluntary): http://www.samsung.com/us/note7recall/
Verizon Recall Info (showing they're still investigating as of 10/10): https://www.verizonwireless.com/support/samsung-galaxy-note7-recall-faqs/
CPSC Information: https://www.cpsc.gov/Recalls/2017/S...-Additional-Incidents-with-Replacement-Phones
USB-C Cable Information: http://www.androidcentral.com/usb-c-problem-isnt-going-away-anytime-soon
More USB-C Info: http://www.laptopmag.com/articles/how-to-find-safe-usb-type-c-cables
Update: Just spoke with a supervisor at Verizon, and they are AWARE that this is a blown out of proportion recall and issue. As of the current moment, they are supporting the phone INDEFINITELY, until Samsung verifies what the problem is and completes the investigation. Then depending on the investigation result, they will decide what to do. I encourage people to call their carriers and talk to supervisors who have more information.
I ansolutely agree with you, around 100 devices in 2 million +, is better than many other quality standards around, and as you pointed out, many people handle devices in very bad ways
Well said. This is why I'm not getting rid of mine. BTW, you accidently put billion instead of million the first time.
---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------
Maybe the whole thing is a conspiracy by another company like LG or Apple. Paying people to do this to their phones then paying the media to overhype and overexaterate the whole thing. I don't think it's a coincidence this happened to the best phone Samsung has ever made. Let me rephrase that, the best phone ever created.
Think about this, how rediculous would it be if samsung found out it was an uncertified cable causing the entire problem, and that they took a multi-billion dollar loss over the cable. This is why all of this crap should not be happening until the investigation concludes.
Updated first post with: Also, don't forget, some of these people with the phones who have overheated REFUSE to return them to Samsung for investigation. There is only one reason to refuse to turn in a destroyed device. If you tampered with it yourself.
Fixed billion replaced with million
Update with information from Verizon in first post.
NOW we're talking! Finally my kinda people! Where have you been the past couple of days? Now the dust is settling and the initial "shock" has subsided people are starting to think with clarity. Excuse the pun, but 'Think Different'
Keep it going, I LIKE this!! I was getting so lonely here getting called a conspiracy nut and such. Thank you my people!
I agree. My phone is perfect and I would keep it except I would like to receive updates and such. At&t told me it has a one year warranty. That I don't have to turn it in. I'm struggling real hard with this. I love this damn phone and nothing else compared to it. I think it's just another case of reefer madness.
My theory is that the playdoh like battery is just in a foil like cover, so it's easily squished. They have mentioned possible assembly problems with squishing it inside the phone being the cause, but I wonder if perhaps a high G drop on a floor might distort it sufficiently that, after a number of charge/discharge cycles, may develop those crystals which will fuse internally between squashed plates causing the battery run away we have all seen.
I doubt it is external to the battery as surely between battery and main phone assembly there will be short circuit protection (generally the metallic canister style batteries have this built in, but with a sealed phone and soft battery, this protection is probably the very first thing the phone battery cable plugs into).
I only dropped my N4 twice, my N7 never (ok, it hit ground inside a Gear VR when my son was being silly), but I have seen others who are far less careful with phones that may have dropped and distorted the battery putty enough to be more prone to internally fusing.
Although at least 2 photos show the phone in (melted) protector cases which should reduce the shock loading, perhaps these ones had the extra squished assembly with the SDI batteries which already had less internal tolerances than the Chinese one?
Sent from my SM-N930F using Tapatalk
Another funny development that was brought up in another thread... The only video of the unit catching fire is a surveillance video from above... where you cannot actually see what device is spewing the smoke. The only reason its believed to be a note 7 is because someone SAID it is.
Thread cleaned.
Be respectful at all times.
Keep off topic disagreements to Private Message.
Regards
Razvan
Forum Moderator
finally!! some clarity i have 2 note 7 ... one from the first production and other of the second!... and everything fine ... i never trust samsung chargers..... so i instead use blackberry folding type chargers ... and never experience overheating anything ...
w1n73rf3ll said:
finally!! some clarity i have 2 note 7 ... one from the first production and other of the second!... and everything fine ... i never trust samsung chargers..... so i instead use blackberry folding type chargers ... and never experience overheating anything ...
Click to expand...
Click to collapse
The problem is obviously not the charger. I've charged it many times from below 10% all the way to 100 on the samsung unit, and it has never caused a problem. My best guess is that it wont fail because I am using a certified cable.
Perhaps samsung should go the apple route and put a chip in their chargers so only certified chargers work.
With the invention of fast charging technology it is pretty risky to use cheapies.
Sent from my LG-H901 using XDA-Developers mobile app
I've only had my Pixel XL for about 5 weeks. Yesterday was the first hot summer day when I used it in my non-air-conditioned car with the GPS navigating and music playing via Spotify and the Pixel XL shut down 3 times because of extreme overheating. Is this an issue with the phone? I've never owned any phone that ever did this before. If the Pixel XL is going to do that all summer it's going to be pretty useless.
Pixel support made me downgrade from Android O to Nougat because if there is anything wrong with your phone and you are running Android O they use that as an excuse to get rid of you and move on to the next sucker who bought one of these things. I seriously doubt that Android O had anything to do with it.
Support sent me a long and ludicrous list of ways to keep the Pixel XL from overheating. If you spend 900.00 on a premium phone you shouldn't need to baby it to keep it running. I'm thinking about getting a One Plus and just canceling my Fi Service if this keeps happening.
Anyone else have experience with the Pixel XL shutting down because of overheating?
Here are the tips from Pixel Support if the phone keeps overheating on Nougat:
Hi Joe,
Thanks for contacting Google Support!
This email is in regards to the chat conversation we are having right now, as discussed, once you roll back to Nougat update, please follow the recommendations below if the issue persists.
Your device may warm up with use. Letting the device ‘take a break’ from use or limiting/turning off features (even those running in the background) could remedy the situation. Here are some tips/suggestions:
Media apps (music, video games)
1) Close or turn off other apps and features that you're not using; they may be running in the background.
2) Discontinue using the media temporarily until the temperature normalizes.
User-installed apps
1) Put the device in safe-mode to disable 3rd party apps and see if the issue improves.
2) Try uninstalling recently installed apps to pinpoint the app causing the issue.
Display brightness
1) Manually setting the brightness to be very bright may contribute to higher device temperature.
2) Consider setting to auto brightness to manually reducing the brightness setting.
GPS / 3G / WiFi - prolonged data connectivity
1) Turn off feature when not in use.
2) Stop or limit use and allow device to cool down if it gets warm.
Exposure to direct heat
1) Remove from heat and keep away from direct heat or excessive sunlight.
Poor ventilation
1) Expose the device rather than keeping it tucked away in poor ventilated/tight areas (layers, small pockets, bags).
Cases
1) Don't use a case that covers the front and back of the device.
2) Use official case (available on Google Store in some countries).
Chargers
1) Don't use unofficial chargers which can overcharge and degrade the battery.
2) Use official charger (available on Google Store in some countries).
Daydream View
1) Daydream View requires high performance from the device. The device's temperature should stay within safe limits.
2) Remove any protective cases from the device to improve thermal ventilation.
3) If your device feels too hot, stop using Daydream View and allow the device to cool down.
Android Wear
1) Power off the device for 5-10 minutes and turn it on again.
2) Try using the watch for another day to see if your issue improves. If your watch is still warm after a day, reply to this email and let us know.
Thanks,
Madasu
The Google Support Team - Supervisor
Why are you complaining exactly?
You were beta testing O when this occurred right?
Ish happens when you beta test.
thats what beta testing is for.
We should all be thanking you because when we all finally install the release for O we will probably not have that issue.
Thanks
I'm complaining because the current version of Android O is stable enough not to cause the phone to repeatedly overheat and Pixel support has tried to blame Android O for problems I had with this phone when I was still on Nougat--like awful phone reception in many parts of the city, which wasn't a problem with the same carrier on my Nexus. Is that clear enough? I did some research and Pixels overheating is frequently mentioned as a problem for this phone before Android O was ever released. If this is a premium phone it should behave like one.
Applications available from the play store may not have been optimized for O yet, so while it may seem like a stable build it is marked as a beta because it is still a WIP. It's like asking for support here on a custom ROM, would you go complaining to the dev about their latest nightly not playing nice with whatever? No, the dev would ask you to try replicating the issue on the last known stable build so they can begin to determine where from there things went wrong.
With all that said, I also recommend trying this using Nougat and see if your issue persists before anything else. All the overheating issues I have seen are either from using daydream or a defective device that needed to be RMA'd
Phone overheated and shut down again --on Nougat this time. Pixel support says that doesn't mean there is anything wrong with my phone--they consider this acceptable and normal behavior for their 900.00 phone.
Yes well regardless of the price there are conditions in which electronic devices cannot survive.
You seem to be subjecting your phone to one of those conditions.
You arent the first one to experience overheating.
Many people have experienced over heating with devices a lot more expensive.
I for instance blew a hose on my jeep and drained the radiator, thank god it was a steel block and I didn't do any irreparable harm.
Jeeps dont have the luxury of a cut off system for over heating like your phone does.
parakleet said:
Yes well regardless of the price there are conditions in which electronic devices cannot survive.
You seem to be subjecting your phone to one of those conditions.
You arent the first one to experience overheating.
Many people have experienced over heating with devices a lot more expensive.
I for instance blew a hose on my jeep and drained the radiator, thank god it was a steel block and I didn't do any irreparable harm.
Jeeps dont have the luxury of a cut off system for over heating like your phone does.
Click to expand...
Click to collapse
You're making excuses for Google which makes you either an employee or a moron. It's June. If Summer is a condition that this phone can't function under then it's crap. No excuses are possible --its just crap.
jhs39 said:
You're making excuses for Google which makes you either an employee or a moron. It's June. If Summer is a condition that this phone can't function under then it's crap. No excuses are possible --its just crap.
Click to expand...
Click to collapse
This is where I leave you.
Good luck.
like I mentioned earlier, you may have to RMA. Complain all you want, until you contact Google to get your device replaced you're beating a dead horse. Dude, we're people just like you trying to help you figure out what's up if you want to act like that go for it. It's your problem, not mine. Good luck.
I've contacted Google. This phone is 6 weeks old and was purchased from the Google Store. I not only have the standard warranty but I purchased the extended warranty because of the shabby way owners of the Nexus 6P were treated by Google and Huawei. I thought I was protecting myself by paying extra for the extended coverage--but if Google maintains that my phone is operating normally no warranty on the world will do me any good.
I've owned 100 dollar phones and 300 dollar phones and the Nexus 6p was a 600 dollar phone. I have lived in Chicago all my life and used all of these phones in the same city under the same exact conditions. I have never owned a phone before the 900 dollar Pixel XL that repeatedly overheated and shut down under the same conditions. And its only June! What is this phone going to do in July when it gets hot out every day?
It's disappointing that this XDA thread seems to be filled with Android fanboys who think it's a-ok for a 900 dollar phone to overheat and shut down as soon as the first hot summer days come along. I would have thought no reasonable person could possibly find that acceptable. Instead nobody on XDA offers useful suggestions, nobody on XDA offers support, understanding or empathy and as far as I can tell nobody on XDA seems to think the way my phone is behaving is unacceptable.
My conclusion is that the Pixel XL was only purchased by Android fanboys because of its prohibitive price, unlike previous Nexus devices that I owned, and that Android fanboys are every bit as useless and annoying as those of the Apple variety.
The XDA threads for Nexus devices are filled with smart people who provide useful feedback and help. The XDA threads for the Pixel XL are something different altogether. Dealing with people here is no better than dealing directly with Google.
if you purchased the extended warranty, then use it @jhs39 we can't call google for you
jhs39 said:
I've contacted Google. This phone is 6 weeks old and was purchased from the Google Store. I not only have the standard warranty but I purchased the extended warranty because of the shabby way owners of the Nexus 6P were treated by Google and Huawei. I thought I was protecting myself by paying extra for the extended coverage--but if Google maintains that my phone is operating normally no warranty on the world will do me any good.
I've owned 100 dollar phones and 300 dollar phones and the Nexus 6p was a 600 dollar phone. I have lived in Chicago all my life and used all of these phones in the same city under the same exact conditions. I have never owned a phone before the 900 dollar Pixel XL that repeatedly overheated and shut down under the same conditions. And its only June! What is this phone going to do in July when it gets hot out every day?
It's disappointing that this XDA thread seems to be filled with Android fanboys who think it's a-ok for a 900 dollar phone to overheat and shut down as soon as the first hot summer days come along. I would have thought no reasonable person could possibly find that acceptable. Instead nobody on XDA offers useful suggestions, nobody on XDA offers support, understanding or empathy and as far as I can tell nobody on XDA seems to think the way my phone is behaving is unacceptable.
My conclusion is that the Pixel XL was only purchased by Android fanboys because of its prohibitive price, unlike previous Nexus devices that I owned, and that Android fanboys are every bit as useless and annoying as those of the Apple variety.
The XDA threads for Nexus devices are filled with smart people who provide useful feedback and help. The XDA threads for the Pixel XL are something different altogether. Dealing with people here is no better than dealing directly with Google.
Click to expand...
Click to collapse
Whelp with that said. Go pound sand. If you can't get Google to replace you're faulty device because you're a little push over, then that's you're problem. Don't get mad at everyone else for not knowing whether or not you're phone is actually busted.
My pixel gets hot under very specific and limited circumstances. I RMA'ed my first one for this reason and now my second one does the same thing. Also, I got this second one on June 6th, little over a week ago.
So the conditions that make my pixel get very hot, very fast is this. Looking at XDA on Chrome, gets my phone HOT. It stutters, lags, and battery nosedives. A few other non mobile optimized sites warm it up, or sites with alot of ads, but XDA is basically un-browsable on it on Chrome. I'm on the O beta, and also using Chrome beta, but it acted this way on N too. So I just stay off the website and only use the app.
It's kinda annoying but everything else seems to work fine, so I'm not going to RMA another one.
I ride around with my Pixel XL in a black car, connected to my head unit, running Android Auto, Maps, and Spotify. The only thing I'm not doing that you probably are is running the screen at full bright.
I can give that a whirl to see if I can duplicate it, but as of right now I've never had an overheat shutdown.
Some questions:
Where do you have your phone mounted?
What kind of mount?
Is your phone in a case?
Do you have the same overheat problem if you place the phone in a different location with the same apps running? (say, in a cup holder or dash cubby?)
UPDATE: One hour of driving. Black car. Black interior. Mostly sunny. 85F ambient temp. Nougat 7.1.2 (5/17). Verizon network. Cell, WiFi, Bluetooth, and GPS radios enabled. Maps running. Spotify streaming via BT. Phone plugged into quick-charger. Screen full bright (100%). No holder in this car, so it was kept in the center console. No case. White phone. Windows open.
Result - did the phone get hot? Yes, it got hot, but not uncomfortably so. Did it overheat? No. Did it shutdown or display any other thermal alert? No, it did not.
So, either your phone is generating a hell of a lot more heat than mine, or something about where you have it mounted or the mount is causing a lot of heat buildup. If you've window mounted or dash mounted, consider vent mounting. Especially if you've a black phone and the sun's beating on it through the windshield. Also, if your mount either covers a great deal of the phone or has foam padding pressing against the back, consider switching out the mount for one that doesn't. That ****'s just an insulator and lets heat build up.
Mine has been very hot unplugging it from the usb cable for android auto in my vehicle but I haven't experienced anything yet like on the 6P. While I loved the design and some features that it had over the Pixel...that thing was a farking overheating throttling all the timepiece of shiite.
I tried the Pixel XL on Android O and the phone overheated. I tried Nougat and the phone overheated. I tried a custom Rom (DU) and the phone hasn't overheated yet, but the normal temperature of the battery when I'm in my air conditioned apartment iand the phone is completely idle s between 90-100F. Is that normal for this phone or should I press Google for an RMA? The only. othervthing I can think of is taking off the case and seeing if that makes a positive difference but I've been using Spigen cases on my last few phones and never had a problem with them.
Any constructive feedback would be appreciated. Anyone know what the normal operating temperature on this phone should be?
The reason of overheating may have to do with the SD821. If that is the case then there is no work around. The reason why I didn't buy the Pixel XL was because of the SD821. However i will buy the Pixel XL 2 with either SD835 or SD836.
dieselhazza said:
The reason of overheating may have to do with the SD821. If that is the case then there is no work around. The reason why I didn't buy the Pixel XL was because of the SD821. However i will buy the Pixel XL 2 with either SD835 or SD836.
Click to expand...
Click to collapse
Well that sucks. I know the processor in my Nexus 6P was supposed to have overheating issues but I thought that had been solved with the processor used in the Pixel.
Pixel Support offered to RMA my phone but they will send a refurbished one in its place and since the phone isn't even 6 weeks old and I paid 900 for this thing at the Google Store getting stuck with a refurb so fast seems like a rip-off. The Pixel XL already seemed like a ripoff at 900 for a new one--but for a refurb?
A replacement might not even be any better if the CPU is to blame like you suggest. I'm tempted to just sell this thing, go back to using my 6P until the inevitable boot loop of death and then get a One Plus. I will definitely never buy another Google device after getting burned twice in a row.
Instead of bashing Google, let's try to resolve this issue.
I would try installing an app to see if you have any wake locks. What's great about Android vs iOS is we have deep sleep. So when that phone shuts off your CPU goes down exponentially. If you are having heat issues, it could be your phone failing to go into deep sleep. I am on a non rooted phone and I get over 7 hours of screen on time and my phone lasts me easily a day and a half. Do you have anything synced? I check all my stuff manually besides Facebook and Snapchat. I would turn everything else off. Also I had a battery case and they all caused my phone to have wakelocks. I have read if you do not use the charger that comes with the device aka car chargers not from Google for the pixel, then I would assume that would give you heat issues. Are you having any other problems besides heat?
Dj21Oh said:
Instead of bashing Google, let's try to resolve this issue.
I would try installing an app to see if you have any wake locks. What's great about Android vs iOS is we have deep sleep. So when that phone shuts off your CPU goes down exponentially. If you are having heat issues, it could be your phone failing to go into deep sleep. I am on a non rooted phone and I get over 7 hours of screen on time and my phone lasts me easily a day and a half. Do you have anything synced? I check all my stuff manually besides Facebook and Snapchat. I would turn everything else off. Also I had a battery case and they all caused my phone to have wakelocks. I have read if you do not use the charger that comes with the device aka car chargers not from Google for the pixel, then I would assume that would give you heat issues. Are you having any other problems besides heat?
Click to expand...
Click to collapse
The primary problem is that the phone seems to run hot even when it's completely idle. Pixel support claims to have no information regarding what an acceptable temperature range is for this phone so I have no way of knowing whether my phone is running warmer than it should. They did offer to RMA my phone but admitted they would be sending me a refurbished one in return. The phone was 900 dollars and I bought it from the Google Store less than 6 weeks ago. I don't think they should be sending me a used phone. Any charger is going to make the phone warmer because that's the nature of the quick charge technology. GPS use according to the list Google sent me will make the phone warmer. GPS use also drains the Pixel battery quickly, so it's pretty much impossible to use the GPS on a long drive without also using a car charger at some point. I'm using the exact same car charger I used with my Nexus 6P and had zero overheating issues with that phone--at least that I'm aware of. The phone definitely ran much cooler than my Pixel does but the boot loop of death that plagues that phone is likely caused by too much heat for the solder to withstand over time--similar to the LG phones that also permanently bootloop. It's possible Google is trying to avoid a similar issue with the Pixels and that they are programmed to shut down before damage can occur. The problem is that I need a phone where I can reliably use the GPS and a car charger simultaneously on a hot day. The Pixel left me stranded because the phone kept overheating and I had to keep pulling off the highway to let it cool down so I wouldn't get lost. Google considers cool down periods for the Pixel normal and says so in the long list they e-mailed me of all the things that can cause the Pixel to overheat. I don't think Google should have sold this phone in the first place if they thought there was a good chance that it would overheat and shut down if you were using the GPS and a car charger at the same time. I'm still thinking about selling this phone and buying something cheaper and more reliable. I didn't pay a fortune for this phone only to be told by Google that it's fragile and needs to be treated with kid gloves.
I've tried to use the phone without a case. I tried a custom rom and kernel. I tried Greenify. I tried Naptime. The phone just continues to run at a high temperature no matter what I do. Maybe I do need to RMA the phone but getting stuck with someone else's used phone after paying so much for this thing really pisses me off. If I had a problem with a Samsung phone they would replace it with a brand new one in full retail packaging. Google should do the same.