Database Info

Finally a fully functioning phone

So long story short I lost my phone a week ago, one with terrible gps I should add, I didn't get the standard 5 dollar a month insurance from the death star, the guy at the wireless place offered me some other option where you pay a hundred up front but the deductible was only fifty so I did it thank god.
The insurance was through protect cell. So i filed a claim and they two dayed me phone feddy ex new sim card all. So i activated the phone and what do you know it has constant, i mean extremely constant random shutdown, like every 20 minutes while the battery was over 50 percent. So i the insurance company back and what do you the had the cap on back order so instead of being able to over night me a phone I had to deal with random shutdowns for a few days.
So the new phone finally arrived today and so far no random shutdowns and I did a gps test today and it worked extremely better than ever before. Hopefully this continues. Because I did hear fresh phones are more apt to have a functionable gps.
So to everyone with some sort of issue I suggest using those one year manufacturers warranties until you get a completely functionable phone. I do understand that is a big hassle for most of us and we shouldn't have to do all that to get a working phone but imo its better then having a phone that is lacking in some of its functionability.
Now more testing on custom rom and I am all set, praying gps maintains cuz it's a dealbreaker for me

I got my replacement phone last week (random shutdowns). The replacement had 4 shutdowns in less than 24 hours, the phone I was replacing had 4 shutdowns in 2 months. Called and *****ed that the replacement was within the same IMEI range as the affected phones. They overnighted another phone without waiting for the first or second phone to be returned. Third phone is working fine so far. GPS on Andromeda 1.2 is awesome.

Yea my phone also falls into the random shutdown range sadly, but hey so did my first one and I hadnt had any problems with it. Curious do you have insurance through att or did you get your replacement through warranty?

Fortunately, I live within 25 miles of a AT&T Tech Center - right next to an AT&T Sales Store - and they always have the Cap in stock. I'm on my 4th one, due to hardware issues - all at 0 cost under warranty. They were nice enough to show me that the new phone would boot to recovery, lol.
Happily running Serendipity 5.12, and patiently awaiting Gingerbread.
Thanks to all the devs and members at xda forums for your tireless enthusiasm!

No insurance, all replaced under warranty.

well its day two and I'm now running andromeda, gps is decent but not spectacular. Scheming on an inspire now
Sent from my SGH-I897 using XDA Premium App

Held out since Dec 2010...replacement on the way
There are quite a few threads about the Captivate Shutdown issue, and actually there are a few with some good observations on how to potentially correct it, but ultimately it needs to be replaced
So, what have I tried:
1) Captivate Keep Alive: Works, but battery drain...and non solution.
2) Load Monitor: Works, not a huge battery drain...still, does not fix the underlying issue.
3) Contrary to what many have said, a custom rom/custom kernel does not fix the issue.
4) It does appear some have had success with cleaning battery terminals, and a few have stated Samsung replaced the battery terminals and it fixed the issue.
I called At&t today, 03/08/2011, they asked me for the IMEI code and what color the water damage indicators where (pink or white?). No water damage here, so white please.
They are doing an exchange by mail, since I do not live close to a repair center...I have 14-days to ship the original back. It was quick and to the point. The replacement is a "refurbished device" direct from the manufacturer. Fingers crossed that I do not experience this again on the replacement as others have.
Hope this helps someone sitting on the fence on whether or not to ship theirs back. Remember to unroot, unlag, and otherwise un-fun your phone before shipping back
Enigma

[Q] Should I buy a captivate from ebay knowing shutdown problem

Hi guys,
I just bought a captivate from a authorized ATT dealer, it is a refurbished and I have always been lucky with refurbished products so I did not think twice about getting it. However I won't have a warranty on it, so I am starting to reconsider, thinking that if I have one that randomly shutdown, I will be stuck with a faulty phone and will lose my money since apparently nothing really fixes the problem completely.
So, I have the option to return the phone within 7 days, should I just forget about this phone and just send it right when I get it and just pick another phone. If I had a year to try it, I would keep it, but 7 days... I just don't know what to do, any advice?

Did you already try using setCPU to up the minimum frequency to 200Mhz? Worked for me and many others!

wuddersup said:
Did you already try using setCPU to up the minimum frequency to 200Mhz? Worked for me and many others!
Click to expand...
Click to collapse
No, I am supposed to receive the phone on Tuesday, but I am asking in advance because I only have 7 days to return it and for what I read on the board the problem might not show up right away. If there was a fix that unanimously worked I had no issue keeping the phone but it seems like a lot of fixes only work for a minority. Am I wrong and I missed the fix that is believed to work for most?

Why would you accept a faulty phone when you know for the same price, you could have gotten a phone w/o fault.

Refurbs are warranted for 90 days.

wuddersup said:
Did you already try using setCPU to up the minimum frequency to 200Mhz? Worked for me and many others!
Click to expand...
Click to collapse
Confused on how changing the cpu frequency could prevent showdowns since the problem is faulty ram
Sent from my SAMSUNG-SGH-I897 using XDA App

Like miami said. U should have 90 day warranty on a refurb.
Sent from my SAMSUNG-SGH-I897 using XDA App

I just recieved a refurb on warranty because my "New" Captivated had the dreaded shutdown issue. I tried SetCPU on it but to no avail. Funny thing is it didn't start happening until after the Froyo upgrade... darn closet gremlins. The refurb is an older build date than the one I purchased new and so far so good. I'd imagine that since it is a factory refurb it is up to par in specs since they recognized and addressed the shutdown issue. I wouldn't sweat it.

Well, it is a ebay purchase so the return policy is just what the seller is saying. So how would I get 90 days warranty?
Is it now sure it is a faulty ram? Would newer phone not have the problem then?

im not sure, you are going to have to look it up,
but the shut down issue only affects the older build numbers i believe.
i think... never had the issue so havent specifically read up on it.. just what i think i remember in reading though thousands of posts....
not sure what the build number was....

My build number and imei is in the range of the shutdown issue. It is a refurb from a insurance claim, so maybe that's why I don't have a shutdown problem.
Sent from my GT-I9000 using XDA App

Just my opinion!
I wouldn't even think or touching a refurb captivate from an ebay reseller unless the cost was so low that the risk was worth taking, for a couple of reasons.
I once bought a treo refurb on ebay. The first one would not receive phone calls so it had to go back. The second one worked fine initially, but the phone failed down the line several months later. I wound up using it as a pda and having another phone. Had no recourse because I got it cheap.
My Captivate, purchased from AT&T in August, developed the random shutdown problem. The first random shutdown was sometime in late November. Fortunately, since it was under AT&T Warranty, I got a replacement earlier this year that has been solid so far. But given the history of the Captivate, not only with random shutdowns, but GPS, etc., I wouldn't put any serious money into one without a warranty.
Edit: here's the info about imei numbers - http://forum.xda-developers.com/showpost.php?p=10037509&postcount=24

oh crap... i think this happened to me last night while i was on the phone....
rebooted straight to rom loading screen, no i896 or kernel boot screen...
is that how it behaves? or is that something new?

creepyncrawly said:
Just my opinion!
I wouldn't even think or touching a refurb captivate from an ebay reseller unless the cost was so low that the risk was worth taking, for a couple of reasons.
I once bought a treo refurb on ebay. The first one would not receive phone calls so it had to go back. The second one worked fine initially, but the phone failed down the line several months later. I wound up using it as a pda and having another phone. Had no recourse because I got it cheap.
My Captivate, purchased from AT&T in August, developed the random shutdown problem. The first random shutdown was sometime in late November. Fortunately, since it was under AT&T Warranty, I got a replacement earlier this year that has been solid so far. But given the history of the Captivate, not only with random shutdowns, but GPS, etc., I wouldn't put any serious money into one without a warranty.
Edit: here's the info about imei numbers - http://forum.xda-developers.com/showpost.php?p=10037509&postcount=24
Click to expand...
Click to collapse
I have had refurbished products that worked great in the past, so this is not what really concerns me. But I guess overall people seem to be satisfied with the captivate that I was willing to give it a try, even with the gps problem. At first I thought it was on the first batch of captivates so I though I was fine, but I keep hearing people having a phone bought in Jan 2011 with the problem, so I am a bit anxious.
I paid $240. It is supposed to be manufactured refurbished, so I though it was a good deal considering even used captivates were going way over 300 on ebay. But maybe I just return it without opening it after all.
That too bad because the captivate is the phone that fitted most my needs with a decent price range.

TRusselo said:
oh crap... i think this happened to me last night while i was on the phone....
rebooted straight to rom loading screen, no i896 or kernel boot screen...
is that how it behaves? or is that something new?
Click to expand...
Click to collapse
I'm not sure. Did your phone come directly from Rodgers? Are they known to have the random shutdown issue? I guess you need to find that out first.
My first phone only shut down when it was on idle, never when I was using it, and only once when it was on the charger. As far as rebooting after the shutdown, it behaved differently on different occassions, but it didn't reboot spontaneously. I would pick it up to use it, and it would be off. I would have to long press the start button to reboot.

caribbean_spur said:
I have had refurbished products that worked great in the past, so this is not what really concerns me. But I guess overall people seem to be satisfied with the captivate that I was willing to give it a try, even with the gps problem. At first I thought it was on the first batch of captivates so I though I was fine, but I keep hearing people having a phone bought in Jan 2011 with the problem, so I am a bit anxious.
I paid $240. It is supposed to be manufactured refurbished, so I though it was a good deal considering even used captivates were going way over 300 on ebay. But maybe I just return it without opening it after all.
That too bad because the captivate is the phone that fitted most my needs with a decent price range.
Click to expand...
Click to collapse
I'm guessing you don't plan to use the phone on AT&T, and maybe are not in USA? You might look into seeing if you would have warranty coverage directly from Samsung. In my life, $240 would be a bit much to pay if something goes wrong and you have no recourse. I paid around $200.00 directly from AT&T with 2 year commitment on my existing plan.
The random shutdown issue is well know to both AT&T and Samsung, and phones manufactured since about December seem to have good GPS as well as not have the random shutdown issue.

creepyncrawly said:
The random shutdown issue is well know to both AT&T and Samsung, and phones manufactured since about December seem to have good GPS as well as not have the random shutdown issue.
Click to expand...
Click to collapse
I am trying to figure out if I have some kind of warranty through Samsung. Also, if what you are saying is correct about phones made after Dec, I will wait to see when the phone was made to decide it's fate. Do you have an idea how I can know when the phone was made?
By the way, thanks for your inputs!

Well according to the samsung website, warranty is only for original purchaser. Now I have no idea how that works for att authorized dealer on ebay.

SM-G920I troubles... Need your expert suggestions

its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8

kishore927 said:
its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8
Click to expand...
Click to collapse
Seems like a broken update install. Go to the service center again and list them all the problems thats been happening with valid proof. They will again flash the OS and give it back to you. It might possibly go but most probable that it won't, so repeat the same thing until they take it seriously so that they give you either a refund or replacement or a proper repair! The problem is, Samsung India never does replacements!

Reflash is needed otherwise have Samsung replaced your S6.

update on 30-July-2015
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.

kishore927 said:
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.
Click to expand...
Click to collapse
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.

ultraquantum said:
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.
Click to expand...
Click to collapse
Thanks for the follow up & sorry for the late response.
Yes, after this, I had to go through a difficult time. First they insisted me to go through repair, which i denied. After justifying the problems and pain that I was going through, they offered me a new handset as a replacement. When went to see this new replaced handset, the box is of dirt and a pen mark. It was looking like a potential tampered set. When questioned about this, they responded that they are giving a new handset and the dirt on the box is of mishandling by office boy & delivery person. When Opened the box, i was shocked to see the dirt hand print on the warrant card box also, & more disturbing is that there was dirt on the screen of the phone.
It was hard to believe myself, this was happening to me and for a one month old phone. When I rejected the new handset and demanded my money back. Again they took several days for process and finally did a refund. After nearly 2 months, a happy ending.
As I was in love with S6, did 2500 rupees insurance valid for 2 year, bought tough Armor case from Sipgen & Spigen Screen Gaurd, both together I spend around 3500 rupees. Tough Armor and screen guard are not used at all, now got wasted. Need to find someone who can use the same.
Now, I am back to my SII, which is still a reliable phone for me. SII is loaded with 5.1.1 which is being developed by Lysergic Acid. Thanks for his contribution and support.
S6 & services in India made me to think of moving to iOS. New Samsung devices with New Android features are being developed, but the core OS is not stable. Now, it is time for Android developers to concentrate on OS Stability, battery consumption so that people like me should feel secured when using new phones with new Android versions.

LG V10 Boot Loop of Death

As We Knw ... The LG V10 might have the same bootloop problem as the G4
However now we are hearing that Alot of the LG V10 users are suffering from the same issues with the bootloop as owners of the LG G4 suffered. Many owners of the handset went onto Twitter and Facebook to vent their frustration.
It is said that the only fix that has been effective to date is to put the handset into the freezer or put it in an oven with the oven on minimal heat. It seems that pulling the battery or doing a factory reset doesn’t help.
Unlike the LG G5 where owners only suffered from boot loops in the earlier batches, this time around it has been said that the problems with the V10 arrived ten months after the release of the device. The only good news is that the handsets are under warranty.
"Lately, many of us experienced bootlooping devices. LG had a similar problem with the G4 and it took months until the acknowledged the problem officially and offered uncomplicated repairs. Talking to LG they said it was not yet publicly released that there was a problem with the V10 too "
see on Reddit : https://www.reddit.com/r/lgv10/comments/4yao1s/v10_bootloop_please_report_in_this_sticky_thread/
so if u want sign this Petition : https://www.change.org/p/lg-electro...=des-lg-petitions_share-no_msg&fb_ref=Default

With all the reports of bootloop, it sure seems like more than 5 people would've signed the petition by now!
Sent from my LG-H901 using XDA Free mobile app

mine too . hardware failure. sudden death. i tired putting it in the freezer for 24 hours like i read on one thread and it worked. but after few hours went back to its final death ;(

I'm curious If motherboard was exchanged after Boot Loop is the problem solved or should I be aware of repeating the problem in the near future

Mine just died too after a year. Stuck on LG logo and won't boot.
H960AY model, MB replaced under warranty

Mine just died yesterday, two months out of warranty. I was a moderate (about twice a month) user of battery waster too (which will get a phone hot).
It happened seemingly out of nowhere too. I had it charging for about an hour unplugged it and launched Monster Legends and the screen went black. I had to unplug the battery to get it turned on and then it started looping. It wasn't even hot, it was warm but no where near what it has been in the past.
I put it in the freezer for 5 minutes and it worked briefly after so I figured it was the dreaded boot loop.
I went to tmobile and they gave me 200 credit (they were aware the phone was broke) and I was able to jump to the v20 for 100.
Seeing as the specs are nearly identical it wouldn't be too far out to say that this phone has enough similarities that the G4 problem jumped to the v10.
My manufacturer date was Nov 2015, LG didn't officially acknowledge the soldering issue of the G4 until Jan 2016 so hopefully those of you with a manufacturer date past Jan 2016 will be safe.
Only reason i picked the v20 is because of the capacity, low amount of junkware and removable battery. If it wasnt for that i would have gone back to Samsung, I might still do that when the note 8 comes out.
What really urks me is that the problem came out of left field without any warning so I wasn't able to backup if I needed to. Fortunately google backs up my media automatically so it wasnt a huge loss for me.
Sent from my LG-H918 using XDA-Developers Legacy app

So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.

Dakotahorse said:
So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.
Click to expand...
Click to collapse
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.

Lazarus65 said:
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.
Click to expand...
Click to collapse
I got it back in less than a week, they had it repaired and shipped back out teh same day it arrived lol
Sent from my SAMSUNG-SM-G891A using Tapatalk

Interesting I've heard horror stories about people turning their phones in and then having problems getting status updates or having to wait a month (or longer) to get the phone back.
Of course at the same time people are more likely to complain about it than to compliment.
I was going to send my v10 in but I decided to turn it in to mobile broken and get 200 credit so it ended up costing 104 to update to the v20. I just couldn't afford to go without a phone for a week let alone a month.
Sent from my LG-H918 using XDA-Developers Legacy app

To freeze or bake to revive from bootloop?
Hello everyone, i just received the bootloop of death on my v10 3 days ago & i am seeing where the home remedies worked for many people. I am going to stick a new, fully charged battery in my phone & then try one of these remedies. I need it to stay on long enough to back up my 2,500 photos... does anyone know if putting it in the freezer or oven makes it stay on longer than the other? & also how long did you freeze/bake your phones?
Any advise would be greatly appreciated!!!

If the faulty solder connection is really the reason why this happens I would imagine baking it could potentially actually fix the problem by melting the solder to make a solid connection.
A buddy at work fixed his playstation by setting a blow dryer to hot and putting it on the solder I am not sure where the loose connection is so I wouldn't know if this method would work without knowing where to aim it.
The freeze method works but it worked for about 5 minutes for me but I only put it in for 10 minutes so it might work longer if you put it in longer.
I would just be careful with the bake method and make sure you take out the battery! Also wouldn't put it up too high.
Sent from my LG-H918 using XDA-Developers Legacy app

Thank you i am going to try putting my phone in a ziplock bag & placing it in the freezer. After 15minutes i will insert the battery & try to turn it on while it's plugged into my computer & if it works i'll leave it plugged in while in the freezer to do a backup. If not i plan on putting the motherboard pannel in the oven...

Will be my last LG
I got the bootloop of death late last month. After reading about baking and freezing stories, decided to no bother, stored most things on the SD card anyway. Changed all of my account passwords to be safe. Got it in November of 2015. Verizon was no help. Called LG, said they had extended the V10 warranty by three months from the build date, which means that I missed the cut off by three weeks. Fortunately I have a SquareTrade warranty, got it fixed in less than a week. Also had them replace the screen because of the screen burn/retention issue. Probably my last LG, there's no excuse.

I've just got mine back. after the warranty the phone just froze and and restarted and then it doesn't go anywhere after boot screen. I've sent it to the service center and it is out of warranty and they said it was the MainBoard that need to be changed and that thing cost a lot, luckily, there's this super cool lady from the Philippines and from that invoice after receiving the faulty device she' said that for you to save i will mention here it is still under warranty and "wallah" got the phone back mainboard replaced and paid nothing.

Since it seems to be heat related I wonder if qc2 is a contributing factor since qc2 cannot adjust power output instead the extra juice is dissipated as heat.
Both g4 and v10 have quick charge it's interesting these are the two phones affected by the issue the most.
Sent from my LG-H918 using XDA-Developers Legacy app

It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.

Does anybody suffer bootloop after he/she changed motherboard ?

neptun2 said:
It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.
Click to expand...
Click to collapse
Yesterday I came across two LG V10s that had bootlooped. Both were H961N models and doing a quick check by using its IMEI, I found the manufacturing dates of both the phones being October and November of 2015 respectively.
Mine is also the H961N but produced in January of 2016. Fingers crossed.

I just got mine back today. Looking at the email they sent me about the phone it was a capacitor that failed. Before sending it in I put the phone near a fan with the back cover and battery removed and it booted up for a second before dying. I am also out of warranty by a year and they still took it in for free. Just leave the date blank. So the freezer method does work, but it has to be kept cool or it will shut off again.

Intermittent freeze and no sound when making calls: hardware or software issue?

For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.

davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.

reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.

Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!

No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC

cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.

New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC

cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.

davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,