Related
I don't know what caused this.
I got my G1 today. It worked for probably 2-3 hours perfectly fine.
I had an app freeze (either Barcode Scanner or Lock 2.0) and had to do a full hard reset.
Now, whenever the phones screen darkens or I put it to sleep manually, it WILL NOT come back up.
I have factory reset three times now to try and get this to work.
When the screen is black, all buttons on the phone still light up and so does the LED indicator up top. I had my phone set to use a locking pattern screen at one point during one reset to test out and when the screen went black, I was still able to try and log in by doing my pattern. It unlocked, but still showed nothing on the screen.
Please help!
I've tried:
Turning Wi-Fi off
Turning 3g Off
Disclaimer: Yes, I've searched. I can find other users with the same problem but none of them seem to have a solution.
Phone is NOT ROOTED and has the factory ROM.
Update 1: Update: It only freezes/blacks out when I try to wake the phone from one of the front key buttons.
If I'm sliding to unlock, it seems to be fine.... (but if I've already tried to open from the front it doesnt)
Update 2: If I mash all the buttons in random orders for about a minute or two it seems to come back. Anyone have any idea?
Update 3: I'm thinking this has to be an issue with none of the buttons waking the phone up when closed. If I lock the phone with the "END" key, and then click the front "END" Key again, nothing happens. If I slide the phone open, and click it twice - the phone wakes up.
Update 4: Confirmed update 3. Phone will not unlock via front keys unless it's slid open (or open enough to trigger).
I would really, really appreciate help with this.
Hate to bump this, but I've added some detail on the top and bottom. Have to leave for work, hopefully someone might have an idea by the time I get back.
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Karolis said:
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Click to expand...
Click to collapse
Removed the SD card and rebooted the phone.
No change ( still acts the same way ).
Did you factory reset after or was it an instant change?
I don't mind losing data to fix this.
supremeteam256 said:
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
Click to expand...
Click to collapse
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
zeabrid said:
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
Click to expand...
Click to collapse
If you use the official update you don't have to have root. There are some links on here. I'll see if I can find it for you.
https://android.clients.google.com/updates/signed-gfh-CRB43-from-CRB21.c88b03d2.zip
That should be it, but can't confirm since I'm on my work computer.
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
The link didn't work, btw.
derfolo said:
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
Click to expand...
Click to collapse
Zero water damage.
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
derfolo said:
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
Click to expand...
Click to collapse
Do you have a link to a guide that teaches how to do this (with the stock rom)? I can only see a few that're spread out.
I'm not entirely sure my phone can boot into safe mode/disk mode, so we'll see about that.
Another update: When I boot into safe mode, the same problem exists.
Edit: Just emailed HTC.
This can officially no longer be considered a software issue.
I just rooted and installed a standard ROM. Same issue.
It happens all the way at boot now, just realized this.
HTC emailed me back and told me to call them directly. Will do that tomorrow.
if I find a solution I'll post it immediately.
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
zeabrid said:
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
Click to expand...
Click to collapse
Yea it defitenly sounds like a hardware issue and needs to be fixed. Glad your getting it fixed and you'll be covered no problem.
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
zeabrid said:
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
Click to expand...
Click to collapse
To be honest I don't know the answer but would like to say they would pay for it. But they would have to let you know of the charge before they apply a charge to a credit card.
wow its weird cause im just having a similiar issue now.. in landscape mode.. phone and back light work perfectly. but one i close the screen everything goes virtually blank, everything is running perfectly just the screen light wont turn on..
will try some of your previous methods.. hopefully it works on mine..=/
thanks, for the info zeabrid
Today I went to the AT&T store to complain about the GPS issues on the Captivate. The associate (after looking the device over), gave me a flier/form and told me to take the phone to the local AT&T warranty center. The flier seems to indicate that the warranty center folks would either fix the issue or replace the device if they agree that my phone has an issue and is not (water) damaged etc.
Anybody have any experience with this?
I don't have any experience while owning a Captivate and going to the Warranty Center...
But when I had my Samsung Impression, and the phone display (it was a touchscreen with a slideout keyboard) completely stopped working, it wouldn't register any touch at all, I took it to them, they turned it on, tested that it truly didn't work, and they gave me a new phone (might have been refurbished) on the spot. Walked out with a smile on my face and went on with my day.
Same experience with two LG Xenons with bubbles under the screen. On the spot replacement within 10 minutes after they verified that the moisture sensor was clear.
Sent from my SAMSUNG-SGH-I897 using XDA App
Refurbished phones are the replacement. Very easy to deal with.
I had the same thing with my wife's Bold - warranty center didn't really try to fix it, just did the replacement. You have to make sure to do the data wipe before the exchange, and they can't do much in terms of data transfer. Process itself is very quick and straight-forward.
For my captivate GPS I just did a mail replacement. Gives me the time to swap everything at home with no pressure.
Funny you should ask. I'm currently dealing with a warranty exchange via phone and mail. I called customer support and told them about the random shutdown issue. They transferred me to the "Android" department. The Android department has heard about this so-called random shutdown issue so they sent me a replacement (refurb) phone after asking me questions like "Has your phone ever been dropped?" "Are there any damages to the screen?" "There is a square sticker right next to the 3 golden battery connector prongs. What color is it?" (FYI. If your phone gets wet, that white square will turn to a different color! Mine is still white. Never been in water. Anyway...)
They sent me the phone yesterday and today I turned it on. There was a new problem. It randomly takes me back to the Home screen when I'm just casually browsing the web, flipping through my apps, etc. It doesn't force close the app or system that I'm on. I just boots me out of whatever I'm doing and shows me the Home screen. So, I called to tell them about this problem. It is now in a box that it originally came in and it's waiting to be shipped out. They will give me another Captivate in the mail by Friday.
jaykishora said:
Today I went to the AT&T store to complain about the GPS issues on the Captivate. The associate (after looking the device over), gave me a flier/form and told me to take the phone to the local AT&T warranty center. The flier seems to indicate that the warranty center folks would either fix the issue or replace the device if they agree that my phone has an issue and is not (water) damaged etc.
Anybody have any experience with this?
Click to expand...
Click to collapse
The Warranty Repair Center in my town doesn't stock Captivates. They'll take a look at the phone to see if it was damaged or submerged, then tell you to call the 800 number. Or, you can skip driving in to a warranty center and just call the 800 number. The people there will talk you through some basic troubleshooting, then ship you a replacement (ground is standard, you can pay for an upgrade to overnight). You have 10 days after that to return your phone.
As for your GPS problems.... if you've upgraded to JH7 and can get a solid lock out in the open under a clear sky, well... Sorry to disappoint, but your replacement phone is probably going to have just as many problems with the GPS. I do (and I'm on my 4th Captivate), so do 7 of my friends and coworkers who have Captivates, and so do about 90% or more of the people reporting on the forums.
According to AT&T and Samsung, the JH7 update 'addressed the GPS issues'. And it did make it better... Before, it would just about never lock on. Now I can usually get a lock within 10~20 seconds and it'll show me where I should be.... until I go for a drive.
The test is this: install My Tracks and go for a drive around town. Once you're done, take a look at your track.
If you've got a softtop convertable or a fiberglass roof, you're good.
If you've got the phone far forward on the dash and have a large, steeply raked windshield, you're good.
If you've got a large sunroof, you might be good.
Otherwise, you're stuck with a measured 50m~100m accuracy (it reports 15m~30m, but don't believe it) if you can even maintain lock.
Good luck!
RexEscape said:
Funny you should ask. I'm currently dealing with a warranty exchange via phone and mail. I called customer support and told them about the random shutdown issue. They transferred me to the "Android" department. The Android department has heard about this so-called random shutdown issue so they sent me a replacement (refurb) phone after asking me questions like "Has your phone ever been dropped?" "Are there any damages to the screen?" "There is a square sticker right next to the 3 golden battery connector prongs. What color is it?" (FYI. If your phone gets wet, that white square will turn to a different color! Mine is still white. Never been in water. Anyway...)
They sent me the phone yesterday and today I turned it on. There was a new problem. It randomly takes me back to the Home screen when I'm just casually browsing the web, flipping through my apps, etc. It doesn't force close the app or system that I'm on. I just boots me out of whatever I'm doing and shows me the Home screen. So, I called to tell them about this problem. It is now in a box that it originally came in and it's waiting to be shipped out. They will give me another Captivate in the mail by Friday.
Click to expand...
Click to collapse
Mine was doing this too. I disabled plugins and a problematic page would render. Might be something to try just for the heck of it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Very easy to deal with IMO. I am on my 3rd captivate.
1st one experienced random shutdowns, 2 days later received second one in mail and wouldn't get any network signal, 2 days later my 3rd and hopefully last captivate was on my doorstep.
All you have to do is send in your old unit. I was satisfied with the android people over at ATT.
Dealing with AT&T is MUCH more pleasant then dealing with Samsung for your warranty support. They're quick, they're nice, and they get you in and out in about 30 minutes.
z28james said:
Mine was doing this too. I disabled plugins and a problematic page would render. Might be something to try just for the heck of it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, I don't think it's that. It wasn't just on the Browser. It was also doing it while I was just flipping through the apps or reading an email using the stock email, or SMS, or looking at Settings. Anything I was on, it booted me out and took me to the Home screen. I returned it. I'm getting my 5th Cap today.
Thanks for all the replies. I'll post my experience if it turns out to be any special or interesting.
One other question. My phone is currently rooted. Should I spend effort unrooting it or it should be fine?
Unroot it and/or flash it back to original JF6 using ODIN One-click. If you've installed Froyo, do a Master Reset so it'll delete traces of 2.2 folders and whatnot. Backup first!
Pleasant experience
I went to the AT&T warranty center last weekend and was in and out of the store in less than 10 minutes with a new Captivate in hand. It was an extremely pleasant experience.
Just want to say that this replacement device (new and not refurbished) locks the GPS in about 10 sec inside the car and even faster under the sky and remains spot on. This leads me to believe that it may be some batches of device with buggy hardware with GPS issues.
Thanks
100% of the phones you get at the device support centers are refurbished sport. I'm a manager at one. If they told you it was new you have been whamboozled
Sent from my SAMSUNG-SGH-I897 using XDA App
RexEscape said:
Unroot it and/or flash it back to original JF6 using ODIN One-click. If you've installed Froyo, do a Master Reset so it'll delete traces of 2.2 folders and whatnot. Backup first!
Click to expand...
Click to collapse
I'm a manager at one of the at&t device support centers. Odin one click flash to original software is the only way to pass our inspections. We're not dumb. We can see if you've monkeyed with it in exactly 3 clicks
Sent from my SAMSUNG-SGH-I897 using XDA App
Walked in, gave them a Captivate that refused to charge, boot, or respond in any way, walked out with one that works.
Took maybe 30 minutes tops.
danalo1979 said:
100% of the phones you get at the device support centers are refurbished sport. I'm a manager at one. If they told you it was new you have been whamboozled
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
When I asked specifically whether the device was refurbished, I was told that it was new unit, as the refurb units have some red sticker on the device (when you take the battery out). Either way it does not matter to me as this unit works perfectly including the GPS.
jaykishora said:
When I asked specifically whether the device was refurbished, I was told that it was new unit, as the refurb units have some red sticker on the device (when you take the battery out). Either way it does not matter to me as this unit works perfectly including the GPS.
Click to expand...
Click to collapse
Looks like you were lied to.
Unless if you were still under your 30 days, which would put you under the buyer's remorse program [completely apart from Warranty], then you'd be receiving a new model.
+ most Warranty Captivates are affected by the random shutdown issue, as they aren't scrapped if they're under the affected IMEI range.
You're using a refurbished Captivate, all in all.
My first phone was rooted and then the random crashes started. It got so bad I couldnt turn the phone on unless I did a battery pull then with the charger plugged in and finger banging and milking a cow at the same time.
I finally got it into download mode and went back to stock. I went to the tech center explained what happened and she replaced it right on the spot and gave me a NEW phone, battery and charger. BUT she gave me my old battery cover. :-(
Sent from my Captivate.
Ok, first off I just want to say I have searched around the forums for a similar problem in hopes for a solution and to avoid reposting a question.
For information about my phone, see below the problem description.
Here is the problem:
This just started today, the phone will not play any ringtone or notification sound. I can confirm the speaker itself still works by playing music or choosing ringtones. Alarms do still work, just not call tones or notification tones(even using default ones).
Now that is only part of the problem, along with that, is the fact that when a text message is received, I can view it and dismiss it (Using Handcent as Default). But 30 seconds to a minute after getting the message, or usually while replying to it, the screen will go black and the capacitive buttons stay lit up. No button presses are registered and the only way to gain access into the phone is by removing the battery and putting it back in.
I am also not getting every message sent to me, some will come through while others don't.
Another unrelated issue:
If I wait an extended time between listening to music, usually 20+ hours, for the first minute or so I hear a little bit of static and then it clears up and doesn't happen until the next day.
Info about the phone:
I bought the phone new on eBay at the end of September, the 28th.
The only modification done to it is doing the latest VooDoo lagfix from the link below(I did this within two weeks of having the phone, and it worked fine):
http://forum.xda-developers.com/showthread.php?t=784170
Aside from that, the phone is completely stock running the latest OTA update.
I am using a GoPhone SIM card that has never given me any issues before.
Kernel Version: 2.6.29 voodoo_lagfix_3.0_v1.10
Firmware: 2.1-update1
Build: ECLAIR.UCJH7
Baseband: I897UCJH7
My Background
This is only my second Android phone, coming from the myTouch 3g. I have had the same SIM card for years. Now I have the Captivate, and this is the first time it has given me this kind of problem. I have experience flashing ROM's and all that, I just wanted to wait for an official update for the Captivate to see if GPS gets improved.
I hope I have provided enough information to diagnose the problem, let me know if there is anything else you need to know and thanks for your time.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
codyrt said:
[*]I bought the phone new on eBay at the end of September, the 28th.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
Click to expand...
Click to collapse
Probably why it was sold on Ebay in the first place. Just a shot in the dark, maybe the speaker connection is loose? There are a few threads about taking the phone apart if you are so inclined.
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Swyping...please read slowly!
cappysw10 said:
Just a shot in the dark, maybe the speaker connection is loose?
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Click to expand...
Click to collapse
I did think something like that at first, but every other sound works fine and when it is supposed to(startup sounds, games, etc.). And I would think if it's a loose connection that shaking the phone or moving it around would make sound cut out, but it doesn't.
I figured the manufacturer warranty wouldn't apply, but I have gotten warranty replacements in the past on other electronics from eBay. So maybe a little fibbing will be in order to receive another unit.
I'm thinking it is something software, I have no clue what, I haven't made any major software additions or changes since yesterday. But if all else fails I will try changing to a different ROM and if that fails, get a replacement from Samsung.
I would try flashing again.....and running that kernel....kinda makes your phone far from stock...
For some reason the issue has stopped. I only did a few things, I powered off the phone, turned it on with the 3-button combo, and then restarted the phone from that menu. After the restart, I reassigned the notification tones and ringtones to what they were(my personal choices, not system sounds) and it seems to work.
I will probably wait a few days to see if it occurs again, and if it does, I will move on to a ROM from the Dev section because I am convinced its just some apps conflicting with each other.
newter55 said:
and running that kernel....kinda makes your phone far from stock...
Click to expand...
Click to collapse
I figured that was a minor modification, so i just counted it as stock, but I see what you're saying.
is there ANYTHING (other then re keying my volumes buttons) to make them any better.. some times (less then 15% of the time) they are fine... the rest of the time...they just plain suck.. some times it literally takes 10-20 seconds of pressing the back button for it to actually work sitting there tapping rubbing anything for them to do anything... of the few gripes i have with my captivate its the BIGGEST (followed probably by battery life and lagginess when installing apps, but that can be forgiven just dont bother using the phone while its installing apps lol)
I'm so sick of the buttons.. i've had the phone since well july 18 i think... the first day it was released i ordered it the say it went on att's web site..
i've very tempted to install something like button savior or something.. but dont like teh idea of those on this "small" of a screen.. those arnt bad on my nook color but....
i have also tried a few different roms.. firefly,cog,CM7 a bit ago,perception.. using continum now. love the netflix app lol
I have problems too with my back button on my captivate, it lacks sensitivity.. I wonder if this is a hardware issue... I'm running stock for now since my captivate has no 3 button combo either..
I got my captivate at the end of July so probably first batch like yours and the only problems i have is either lagging witch would only be a second or two with heavy usage or not hitting them good so you probably do have an issue
Maybe dust or a small separation from the top of phone to the actual part where it recognises the touch, i know moisture can get in there and make three buttons hit many times randomly
Sent from my SGH-I897 using XDA App
Perhaps contact your local cell phone store (the one who sold it to you). Im sure you could just send it in for repairs :S
but beware.. ive read things about them screwing you over with rommed/rooted phones. I had no issue with that however
i got mine in September. I actually got two for my fiancee and I. The back buttons are a pain. Have you all experienced the search button popping up after you tried to hit the menu, back or home button? Happens to me all the time.
I first thought it was the Defender Otterbox since it comes close to covering them up but I took it out of its case and it still happens.
Wonder if I can claim this as a hardware issue and replace it? Anyone have any luck replacing a phone due to buttons?
I think I saw were someone was able to get it warranty replacement/ repaired because of the capacitive buttons acting up. It never hurts to try
Sent from my SGH-I897 using XDA App
We had two day one phones, build 1006. Never had amy issues until this month started seeing random shutdowns. Our capacitive buttons were fine, but we never used cases. We called att for replacements. We both got build 1102, and they have been fine so far. I would suggest call att or visit att service center if there is one near you to swap it out. I would also suggest using Odin one click to return to stock before returning them.
Sent from my Captivate running Cognition
Had my Nexus 6 for 4 months now - originally had it on stock for a couple of months, it would constantly power off, usually when battery was less than 20% or when trying to access the stock camera or random apps.
So to try and resolve the issue I rooted the device and have now tried practically every ROM available and still have the same problem
Currently running SaberMod 5.1 with Vindicator kernel and the problem still happens.
Tried PA, CM12, PAC, Vanir, Chroma, Euphoria, LiquidSmooth, Terminus....you name it I've tried it.
Will probably be returning it to supplier but before I do would like to know if anyone has had similar issues - is this because of a bad batch of Nexus 6 phones? I guess it's hardware/battery related - but wondered if any software fixes were available?
I have started to face the same problem, mine shuts off usually below 10% but it's only a month old, so disappointed with nexus 6,not only was it effing expensive, it's not the premium device that Google boasted about with so many bugs, which include the speaker crackles and random shutdowns
Totally agree, why pay for a premium device to be plagued with problems?
I was going to try and find if there was a fix but might just return the device.
Really disappointed I expected a lot better for such a high end device.
FWIW, I've had the 6 since November 26th and don't have any issues. I'm sorry you've had issues but that doesn't mean the whole lot is bad. RMA and get a new one. There are issues with every device after it's launched, go to any forum and you'll see what I mean. You can't label the whole line defective just because of a few isolated problems.
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
thx1971 said:
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
Click to expand...
Click to collapse
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Diocat said:
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Click to expand...
Click to collapse
Thanks for getting back to me with this - I guessed there was an issue but didn't want to return the phone unless I was totally sure, so thank you again for clarifying this.
I am not happy to be returning it but looks like this is my only option.
I have the very same problem with my N6 bought in December 2014. Have tried factory reset multiple times without luck. I just gave it for service. The guy there said they would try reflashing the firmware and if that doesn't work I'll be given a replacement. I'm from India btw.
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
drkboze said:
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
Click to expand...
Click to collapse
Almost exactly what happened to mine: http://forum.xda-developers.com/nexus-6/help/refused-repair-moto-uk-device-rooted-t3077271/page2
TL;DR:
Dear xxx,
Thank you for contacting Motorola.
I have now heard back regarding your Nexus 6 unit. After carrying out the initial repair the engineers at our repair centre then discovered a more serious fault with the battery on the phone as it started to swell during their testing.
Click to expand...
Click to collapse
So if your phone is randomly shutting down when their is plenty of battery, and/or does the optimising 0/xxx apps at start up - get ready to RMA because you don't want a swelling battery and a possible explosion/fire...
I've submitted the device to their service centre and awaiting replacement.
Sent from my iPhone using Tapatalk
My device has been returned and will be replaced, no questions asked, as it is a recognised faulty phone.
So to re-iterate, all I was wanting to clarify was if there was a bad batch of Nexus 6 phones and whether or not mine could be one of them - and it looks like that seems to be the case.
I wasn't in any way saying the whole line of phones are bad but it's good to clarify that there is a bad batch out there and the suppliers are willing to replace them
Same exact symptoms
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
rocket808 said:
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
Click to expand...
Click to collapse
Yes on all points there. The random turn off when doing anything, app optimisation (very long) wifi passwords gone (very annoying) and restart again while optimising. And the resultant swelling battery..
It seems very few of us have experienced this, thankfully, but very worrying, I certainly wouldn't get another moto device after this.
Sounds like the very common battery calibration problem, which can be reset by following a set of instructions in the bootloader. Look around for them.
Bumping this as I think I've found the root cause of this problem. Are you guys using Google Fit? The replacement that I got was working fine till two days ago when I initialized/started using Google Fit. Device turned off twice. Then I disabled the app and the shutdown hasn't happened till now. If you guys are using Google Fit, try disabling the app and monitor it for a couple of days.
Well I managed to get a replacement phone from GiffGaff and guess what - same issue again!
Battery overheats, crashes on Camera App, resets WiFi, random app crashes
Have tried several ROMS including Android M to see if there is an improvement but unfortunately not - will try disabling Google Fit now and see if that helps but so far I'm really disappointed.
This device is supposed to be top of the range flagship Google model but for me it is a resounding fail.
I have got the same problem , but i cracked the top of my screen when i had the phone after a month , when i called Motorola they said they could take to repair but would cost £120 to fix screen as they cant send back with screen damage. Really frustrating as i know the screen isn't the fault. Anyone got any ideas ?
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
goinovr said:
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
Click to expand...
Click to collapse
Boot into fastboot, find bootloader logs and hold power for ~10seconds (till it resets by itself), best done on full battery, may help, if not you can try to calibrate the battery (requires root tho). If all this fails only thing left is to change the battery. Takes about 20mins and costs like 20-25usd (easy to do by yourself