Related
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
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.
I'm back again XDA. Even more G3 problems!
So since the last time I posted, I've replaced the board on my G3. Everything was great up until the SIM reader quit out. Switched to an HTC One M9 and boy is it terrible. So I use the G3 for music, games, etc. Didn't bother rooting or anything. Running VS9854BA. It's always on Airplane mode with WiFi enabled, I try not to let it overheat since the WiFi went to **** on my last board. And what do ya know, as I was typing up a comment on Facebook the thing just freezes up, makes some ****ed up screeching noise, and tries to restart. I get boot looped and notice a red and blue led. So I pull the battery, hold down the power for a bit and throw the battery back in. It boots up. A few minutes later the phone freezes and does the same thing. The battery level was around 80% on this battery. I try another OEM battery and it works fine for the rest of the night. However, the phone is now doing the same thing with that battery. I've only had issues with non official batteries in the past. For example, one battery I have will make the phone reboot after using the camera. Anyways, I'm iffy on purchasing a new battery. I don't want to pay $6-10 on a POS that was made in 2014. And I don't want to gamble on buying a $15-20 OEM battery from LG, as it may still be old and degraded; or won't even solve the problem. I tried contacting LG to see if I could get any insight, or to see if they are selling newer manufactured BL-53YH batteries and have yet to hear from them. I have noticed most people have issues with LG phones two months after their warranty ends. I was surprised to see the G3 last a few years and would like to get some more time out of it. If my 2011 galaxy nexus still works flawlessly, so should the G3. In the meantime I put a little noctua thermal paste on the EMMC and was baffled by the temperature decrease in cpu z. It still doesn't fix anything though. Any thoughts here? Should I gamble and buy the battery or is this hardware failure?
TLDR: LG devices may be time bombs and their support sucks.
There seems to be a lot of bootloop/battery issues this week. I hope device is not a "time bomb".
Sent from my K00C using XDA-Developers Legacy app
n00dle24 said:
I'm back again XDA.... Should I gamble and buy the battery or is this hardware failure?
TLDR: LG devices may be time bombs and their support sucks.
Click to expand...
Click to collapse
"...as I was typing up a comment on Facebook..."
Maybe it's just the universe trying to tell you that Facebook sucks?
Kidding aside - it sounds like your phone is dying a slow death. Normally if you had just the restart issue I would suggest a new battery(even with the reboot at 80% - old batteries get weird), but with the sim issue combined with the screeching noise red/blue light reboot - which usually delivers a green screen kernel panic reboot - it sounds like the weirdness that occurs when a G3 dies.
If it were a bad battery I think it would just shut down, reboot to the LG logo, and then bootloop(that's what mine did when it failed); but failing G3 batteries do some weird things sometimes. To t-shoot a bad battery I guess you could try plugging the phone in and using it while charging to see if any troubles occur; if not, then invest in a battery. I can't say that is a fool proof way to check the battery though...the best way is always to replace it.
If it's (what is believed to be) a solder issue on the board - which a lot of G3 users have reported as the phone has aged - you can try the paper trick to create enough pressure on the chips to complete the solder connection or even using some heat to try and get some solder to reflow, but those are generally only temporary fixes...the issue usually comes back in time. It may be worth it to try the paper trick to help you troubleshoot your issues - if the trick fixes it briefly then you know it's a hardware issue and you can make a decision from there. If you have one of these solder issues it's just best to move on.
So flip a coin: replace the battery for @$20, or say eff-it and get a new phone; sounds like a tough decision...glad I'm not making it - yet.
*If you don't know what the paper trick is just search the G3 forums...screen flicker threads usually mention it and there are other threads out there too.
Hi! , my google pixel xl (2 years old) a few days ago started in an infinite bootloop, I never rooted it or unlocked its bootloader, I could solve it by heating the pixel for 5 minutes with a hair dryer, but this solution only lasts for 24 hours.
I can access the recovery and bootloader mode.
I was in charge of investigating, and this problem has the nexus, which is solved for a short period by heating it with a hair dryer, this apparently stops the nuclei that cause the loop and revives.
In nexus cell phones a file was created to flash, which deactivates these nuclei.... is there something similar for the google pixel xl?
My Doubt is:
Did anyone else suffer from this problem?
What do you recommend me to do?
Thank you very much
+1 i'm the same with Google Pixel
Mine started experiancing this as well a few weeks back. Also before experiencing this issue the phone had been oem locked and running stock os Although for me it was to freeze my phone to have it boot. The list of this complaint seems to be increasing around the same time.
Sent from my Nexus 7 using Tapatalk
It's onboard UFS failure.
I had this exact behavior on one of my pixels, but it got so bad that a portable floor heater would not even let it boot.
The only real way to fix it is to repair the UFS chipset on the device.
djared704 said:
It's onboard UFS failure.
I had this exact behavior on one of my pixels, but it got so bad that a portable floor heater would not even let it boot.
The only real way to fix it is to repair the UFS chipset on the device.
Click to expand...
Click to collapse
Sounds like a cracked solder joint on a flat pack or one of the PCB components.
Lol, let me guess they use no lead solder... lead is your friend.
Hi, I’m having a problem with my Huawei Mate 20 that I bought in 2019. The screen brightness is too low even when set to 100%. This started happening two days ago after I spent the day outside in the sun (i don't know if hot temperatures influenced but has already been 2 days so is strange). When I got home, I charged my phone and opened some apps, but it started crashing and the screen went black. I tried force rebooting it multiple times but the screen remained black. I thought it might be a battery issue so I charged it for an hour and a half but still nothing. After 40 minutes, I accidentally pointed a lamp at my phone and could see that it was working perfectly but the brightness was very low. A similar thing happened to me in 2020 but I can’t remember how I fixed it. I tried searching for solutions online and on XDA developers but none of them worked for me except one that involved ADB which I can’t try because for some reason I can’t connect my phone to my PC with USB debugging. My warranty has expired like 2 years ago so lol... and I haven’t received a response from Huawei support yet (i emailed them yesterday)
Welcome to XDA.
It was heat damaged. Anything above 125F can do it. Exposure to direct sunlight on a hot day is especially bad.
I did this accidentally to my Samsung S4+ years ago. Very faded out and got worse the more I used it.
Oddly after sitting unused it got slightly better. After I got a new phone it sat for months unused, it improve further still. After 3 years it appears to operate normally now. The crystals seem to have reverted back. Peculiar critters.
Yours may or may not do the same. There may be a way to accelerate the process. Mine sat in both hot and cold environments during that time.
Putting a charge on the crystals by using the phone is probably what hindered their recovery.
Either replace the display or let it rest. Using it will likely make it worse...
blackhawk said:
Welcome to XDA.
It was heat damaged. Anything above 125F can do it. Exposure to direct sunlight on a hot day is especially bad.
I did this accidentally to my Samsung S4+ years ago. Very faded out and got worse the more I used it.
Oddly after sitting unused it got slightly better. After I got a new phone it sat for months unused, it improve further still. After 3 years it appears to operate normally now. The crystals seem to have reverted back. Peculiar critters.
Yours may or may not do the same. There may be a way to accelerate the process. Mine sat in both hot and cold environments during that time.
Putting a charge on the crystals by using the phone is probably what hindered their recovery.
Either replace the display or let it rest. Using it will likely make it worse...
Click to expand...
Click to collapse
Hi black, thank you for the warm welcome and for responding to me. In fact, now that I think about it, the last time this happened to me, I had exposed it to a lot of sunlight. Would it be a good idea to place it in a cooler or shadier location to speed up its recovery? And approximately how long should I let it rest? About a week?
Luke221 said:
Hi black, thank you for the warm welcome and for responding to me. In fact, now that I think about it, the last time this happened to me, I had exposed it to a lot of sunlight. Would it be a good idea to place it in a cooler or shadier location to speed up its recovery? And approximately how long should I let it rest? About a week?
Click to expand...
Click to collapse
Cooling it might hinder it's recovery. Not really sure. I was surprised when mine eventually recovered. Not saying this will be your outcome.
Also it may take way longer then is practical
If you need to pull data leave it sit for as long as you can wait.
It's back lighting is working, right?
blackhawk said:
Cooling it might hinder it's recovery. Not really sure. I was surprised when mine eventually recovered. Not saying this will be your outcome.
Also it may take way longer then is practical
If you need to pull data leave it sit for as long as you can wait.
It's back lighting is working, right?
Click to expand...
Click to collapse
Lol, it looks like i just ****ed up my phone. Before I started this thread on the forum, for pure curiosity, I tried to activate the torch but it didn’t work despite multiple attempts. I hope it’s not a hardware issue ()
Luke221 said:
Lol, it looks like i just ****ed up my phone. Before I started this thread on the forum, for pure curiosity, I tried to activate the torch but it didn’t work despite multiple attempts. I hope it’s not a hardware issue ()
Click to expand...
Click to collapse
It can easily happen; protect from drops, water... and heat.
The battery may have failed if the phone died completely.