Related
Samsung has released an imei range for the problematic random shut down phones. If the last 4 numbers of your imei is lower than 5394 then your phone will have the shutdown problem eventually. SAMSUNG has found that all captivates manufactured before November 6th 2010 have this defect. This press release was published on Dec 20th
ID: myc_spt_iss_wid_sam_189047
Date Published: December 20, 2010
Manufacturer(s): Samsung
Model(s): i897 (Captivate)
Issue Type: Informational
Issue Summary
AT&T and Samsung are working together on a power off issue on the Samsung i897 Captivate. There is a small group of Samsung i897 Captivate devices which may experience power off when in standby mode. All devices manufactured after November 6, 2010 should not have this issue. Most customers are not expected to see an issue, however the following IMEI range could potentially have the issue and AT&T and Samsung want to ensure these customers have the best possible experience and quickly address customer care inquiries should they arise:
IMEIs manufactured before November 6, 2010: 352982040855394 or lower - 5393, 5392, etc.
If customers reports that their device is powering off when in standby mode please assist them with exchanging their device.
SKU: 65187
Critical Must Know/Must Do
Customer/Embedded Base: If a customer has the power off issue when in standby mode please exchange their device. Customers with the launch software version i897UCJF6 are more apt to have the standby power off issue. Meanwhile customers that have devices manufactured after November 6, 2010 should have software version i897UCJH7 which fixes the Power Cycling related to SW issues.
Existing Product: All devices that were manufactured before November 6, 2010 have the potential to be affected.
New Product: Devices manufactured after November 6, 2010 should not experience this issue.
Distribution Center: No action necessary.
Channel Instructions
Company Owned Retail: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.
Dealers: No action necessary.
National Retail: No action necessary.
Direct Fulfillment: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.
Customer Returns and Exchanges: Standard under 30-day returns are in effect for this issue.
Accountability/Responsibility
Distribution Centers: No action necessary.
Channels/Markets: Adhere to Standard Operating Procedures.
Returns Processing Center: Adhere to Standard Returns Processes.
Supply Chain: Please send questions or comments to SCM Product Advisory.
**If your Captivate has already been exchanged at your local device support center ignore the last 4 digits as the units the device support center gives you in exchange are not known to have this defect**
Well, having purchased my phone on launch day, I know it falls into that IMEI range. I wonder if this would make getting a replacement any easier?
Where'd you find this?
polarbee said:
Well, having purchased my phone on launch day, I know it falls into that IMEI range. I wonder if this would make getting a replacement any easier?
Where'd you find this?
Click to expand...
Click to collapse
I bought mine the day after, but I believe that not all phones before November 30 have the defect, just that SOME phones have it
Thanks! I'm in the 77xx, so that's one less thing to worry about!
nbs11 said:
I bought mine the day after, but I believe that not all phones before November 30 have the defect, just that SOME phones have it
Click to expand...
Click to collapse
Oh mine has it but I've mostly been ignoring it because it doesn't happen very often. It's just enough though that if this press release made getting a new (not refurbished) unit easier, I would seriously consider it.
For sure, I got mine in the first week. I have only had troubles with some of the custom roms. And if JH7 "fixes the Power Cycling related to SW issues" then AT&T can use that as an excuse regardless of what this says.
I bought mine on launch day, and so far have never had the problem, my imei falls into the range.
I see an oden to stock and new captivate in my future. I too was holding off, happens maybe once a week. If this if an internal memo, please upload copy of it with parts that name you blacked out.
From a phone
Hmm, mine is much lower (3522) and I get shut down issues.
I guess it's the same thing for the Canadian version... on rogers. My IMEI is also in the affected range... and I do have that random shutdown.
quite annoying... I will go to futureshop ask for an exchange... only 14 days usage!
My first phone was purchased from Amazon around the week of Nov. 20. It had 1009 production batch and JH7 firmware. It got the power off issue. Amazon exchanged me with an earlier production, 1008) and came with the CF6 software. I had to use mini kies to update it. So far (one week), it hasn't had that issue. So, it does seem that the issue happens to some, but not all phones.
Mine starts with 3518xxxxxxxx... I've had 1 maybe 2 shutdowns in 5 months I've had this replacement device... I wonder if I should take my chances with another warranty replacement.
Wow. Mine is really down there at 1093. I've never had an issue with the random shut downs. I will get soft resets after messing with the lbstest app and sometimes it won't unlock completely (lock screen freezes as I swipe).
Bought mine on launch day and I've had a few random shutdowns. How much of a pain is the warranty replacement? Will I have a chance of getting a phone with working gps??
scrubinator said:
Bought mine on launch day and I've had a few random shutdowns. How much of a pain is the warranty replacement? Will I have a chance of getting a phone with working gps??
Click to expand...
Click to collapse
No (and for the optimistic, "probably not").
What is the usual turnaround time by going through Samsung for a replacement? I bought my phone on eBay recently after the launch date so I can't go to AT&T.
Mine is 3541xxxxxxxx; which is much later... should that mean I won't get the shut downs?
And am I understand this correctly? It's a software issue?
(is using Captivate Alive ...)
LOL mine is 35186304XXXXXX and I have not had a single problem this is the third captivate I had and this one was the one I got back from a warranty Exchange. The first Captivate I had on July 30 shut down a few times. The second Captivate I got on August 20 shut down 10+ times a day.
Now I am fine on this one been through 4 roms as well
Mine starts with 351 ends with 1622. Bought in the end of october. Haven't had a single issue yet. Flash roms constantly lol.
So does this mean we can get a new phone or will it still be a refurbished phone? Should we contact Samsung, the AT&T store we got our phones from or an AT&T device support and service center?
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.
Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).
dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.
I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.
I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.
Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...
Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app
Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today
Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app
Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.
Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.
Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?
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,
I've been having problems with my pixel. After about 20 mins after rebooting the phone the mic, Earpeice, and Headphone Jack don't work. It just happened out of the blue one morning and it's stopped working since. I've already completely wiped the phone with twrp and flashed Android P, nothing is working. Any ideas?
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Alaadragonfire said:
It's a hardware issue with the audio codec inside the motherboard. If you got warranty still you can replace it from Google.
Click to expand...
Click to collapse
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
velvet_man said:
Is this confirmed? My Nexus 6P recently died, so I picked up a Pixel secondhand to replace it. It worked fine until I updated it to 8.1 and then all these issues started, which made me think it was software related. I've read a ton of threads all over the internet on this, and I see people replacing the mic/charger port, the headphone jack, and the daughter board and still having the same issues.
I saw somewhere (can't remember where now) that someone finally had this problem fixed by installing the Android P preview. Has anyone else had any success with that? Since I got this secondhand, I can't just get a warranty repair/replacement. I can send it back, but then I'd have to pay almost twice as much to get a Pixel 2, so I'd prefer to get this working if possible.
Thanks
Click to expand...
Click to collapse
It is confirmed unfortunately. Many people had this problem with their devices that are manufactured in 2016 and before January 2017. If you are able to send it back I suggest you do.
I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.
Thanks guys. I sent the phone back. It was a certified refurb through Amazon, so I should get a full refund once they get the phone back in the mail. I want to order another one, but how do I verify that it was made after Jan 2017?
Thanks!
truvatech said:
I have a november 2016 pixel and uBreakiFix (canada & US, but I did it through Canada) replaced the motherboard free of charge even 8 months outside of my warranty period.
I'd consider going to them.
Click to expand...
Click to collapse
I want to second this experience for anybody that finds this thread. My wife's phone was purchased Dec 2016 and lost microphone/speaker last week. Used the help feature to chat with google, they sent us for repair and uBreakiFix replaced the motherboard at Google's expense 8 months out of warranty. I'm very happy to see Google standing behind their device.
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
plittlefield said:
OK, so here's my 2pence worth... I have a Pixel manufactured in 2016 and it has been faultless for 10 months. I have been very craeful with it. I applied the 5 July 2018 Security Update and my microphone stopped working. I tried all the usuals to fix it but nothing. As a last resort I enrolled in the Android P beta program and installed it. My microphone started working again with Android 9. However, with the latest update build PPP5.180610.010 the microphone is buggy again... so I think it's a software driver issue. Anyone else want to confirm this?
Click to expand...
Click to collapse
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Note10.1Dude said:
I don't think so. Flakey hardware - not a complete failure, but bad enough connection that it isn't reliable. Had you done a complete factory reset, I bet it would have worked for a bit. Then, when the signal is bad for long enough the system can't deal with it and the behavior re-surfaces. You could design resilient software to account for the slow failure. At least that is my guess, based on the experience I had (swapping SIMS would fix the phone for a while, sometimes microphone would go out first, sometimes wireless data).
Click to expand...
Click to collapse
Damn, hope not
OK, so what serial number do I need to check for on eBay, so that I get a 2017 manufactured Pixel?
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
plittlefield said:
Yes, 3 weeks is exactly the same time as when I updated to the 5 July 2018 security update, and then my microphone started going funny. Please try going to SAFE MODE and then clear the CACHE from the Phone app.
Press and hold the power button to bring up the power options. Press and HOLD on the Restart icon. Choose SAFE MODE.
Once in SAFE MODE, press and hold the PHONE app icon, and choose the 'i' for information. Choose Storage, then press the CLEAR CACHE button.
Reboot the phone again in SAFE MODE, and try calling your OWN mobile number then leave a message.
Tell me if your microphone is working again.
Click to expand...
Click to collapse
No bro.. I tried like you said..but not working..
udahy.manna said:
No bro.. I tried like you said..but not working..
Click to expand...
Click to collapse
That's a shame.
I can absolutely confirm THAT MY PROBLEM IS A SOFTWARE ISSUE... I have just installed an update to the PHONE app from Google on Android 9 and made 3 telephone calls this morning with NO PROBLEMS at all.
Here's the summary again for those that it might help.
1. Pixel on 8.1.0
2. Update to 5 July 2018 Security Patch
3. Microphone not working
4. Enroll in Android 9 P beta
5. Install Android 9 beta
6. Microphone now working
7. Sometimes microphone fails
8. Reboot in SAFE mode and clear Phone app CACHE
9. Reboot in SAFE mode and make a few calls with microphone working
10. Update to latest Phone app version 22.0.204206752 (31 July 2018)
11. Phone and Microphone working perfectly
That's all I can say really.
Paul
OK, so it's been another trouble free day with the phone, making calls and using Google Assistant with my WORKING MICROPHONE fixed by software... and not a soldering iron
I made and received a dozen calls and asked Google for help with all sorts.
So, things can be fixed without sending it away.
My serial number begins FA69M which means...
FA = Where it's been built
6 = Year of production (2016)
9 = Month of production (September)
M = Day of production (21)
...so it's a pre 2017 Pixel Sailfish which had the problem and now it doesn't thanks to Android 9 beta.
Paul
udahy.manna said:
I am also facing the same issue..my bottom microphone is not working for the past 3 weeks, I have contacted the local authorised centre,they told me that the motherboard need to be replaced..
Unfortunately my phone is 5 months out of warranty and no uBreakifix here in India..
Click to expand...
Click to collapse
Did you fix?
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Sam33t said:
Damn, I've been thinking to buy it, the 128GB model, since I'm not kinda guy who changes cellphone like cloths, just updating for another 2 year or more. I'll be updating the device to Android Pie for the app support. Please advice me if I should buy it or not. I'm fully convinced to buy Google Pixel 128GB model since it is compact has a great camera and it provides a real smooth experience with stock android. only thing holding me back is that MicroPhone Issue that people are complaining about. Please help me make the decision.
Click to expand...
Click to collapse
i had this issue a while back but since ive updated to the december update i havent had any mic, speaker issues at all. its the best phone to me ive had...and ive had alot. i say get it..im gonna get the pixel 2 xl and the pixel 3 as well..