Related
as i said in the title when i use wifi i get a about 2-5 mins of use out of it, but then it will cause the pda to shut down, even when i have full battery and its plugged in, and it wont completely turn back on till i plug in a charger, occasionally even this wont help for a while, i also have had some problems with the battery, like sometimes it wont be recognised by the pda so it wont turn on and will show the red light when i try to charge it, could that cause this problem?
Sounds like new battery time.
My last one used to die if I had the backlight on for more than a few mins, it lasted a year (the original battery).
Got a new cheap one from eBay, seems to be going fine with good battery life.
thanks i thought this was the problem so i bought a new battery last week, still hasnt come yet though
Hi
i have the same prob too, but when i plug it into the charger it won't turn off!!!
this is an actual common problem possibly residing to a specific batch load or maybe more. the problem will get worse and in short it's not a battery it's a mainboard problem with a sensor or a part that becomes hypersensative to heat. I think it's part of the same circuit that shuts the device down if the cpu or battery overheats but I can't proove it yet. I've had 2 of these phones so far. 1 3 got t-mobile t swap for an mda vario 2 at the time as the phone wouldn't stay stable for more then a few minutes. same result with 2 like 4 like replacements they sent me. ifinally said enough I want the closest thing tech spec wise to it. the 2nd one was my wifes which she barely used now that shes moved on to a different phone I've started playing a bit with it as it's over 12 months old. and I put it back into the box and up on a shelf as soon as it started doing the rebooting thing like the first one. NO WONDER ORANGE START DISCONTINUING IT AS WELL DID T-MOBILE UK.
UPDATED :
After reading a few of the posts aftr mine, I set out on a mission to determine the more exact reason for this cause. I found the unlike most mobile e.g: sony, lg, nokia etc. this phone would nout power on from the mains adapter without the battery. I figured initially it must have been the manufacture thinking this is not a laptop and the mains adaptr was intendd to charge batteries and then run the device. this also prevents data loss or file system corruption incase your mains charger comes loose from the device while playing. however I found that by putting my finger (when your finger tips are lightly moist and conductive) over the battery terminals on the device it would infact power on and work. now in light of this there are 6 terminals to make conduct with the battery the outter 2 on each extreme end are your + and - . the 2 inner ones are likely then to be battery voltage sensor and battery temprature.
so I said great way to test a theory. I unplugged the mains charger and started downloading files from my pc to the memory card over wireless. this of coarse caused the battery and the device to heat up very quickly. within about 10 minutes it did as expected and shut off. then when pressing the power button could not make it back to the main today screen either it would shut off on the windows mobile splash screen OR it would shut off during the first splash at bootloader.
I then removed the now very warm battery and put my finger on the battery terminals making sure the 2 center pins were touching my finger. voila th device powered on and booted up just fine. I then went back to doing file transfers and it never shut off on me again as lon as I held my finger on the battery terminals. in short I fooled it into thinking the battery was there but but that the temprature was fine. wm6.1 from ranji's 7.1 could tell there was no bettery to charge but the temp sensor was fooled. conclusion: the reason 2 replacement handsets in the past sent to me by t-mobile conitune to fail was not infact an internal problem that was main board related it was the battery incorrectly sending wrong temp info or a faulty battery that was getting to hot and the manufactures own safty device was shutting the device down to cool off the battery. this would be why in the past I would be able to just leave it off and eventallly it would work again. I felt like such a fool but at the same time I felt good that I got 1 traded for a vario and that now all I need to do to fix my mda pro is t get a new battery. I am man enough as you can tell to say wheni was wrong and I was. in light of this new info I would recommend the device to others but if you start getting random shut downs and turn offs during internet over wireless or gprs and the device is wamr ask your provider for a new battery or replace it yourself maybe even with a larger capacity one as it will likely resolve your problem. I know there are other posts i've done about this subject and I HOPE that those that have read them read this update as it applies to all htc universals regardless what branding they fall under.
enjoy in knowing new things
cj
i got my new battery today, all seems well, it even solved a problem or 2 i didnt even think were caused by the battery
cyberjak said:
this is an actual common problem possibly residing to a specific batch load or maybe more. the problem will get worse and in short it's not a battery it's a mainboard problem with a sensor or a part that becomes hypersensative to heat. I think it's part of the same circuit that shuts the device down if the cpu or battery overheats but I can't proove it yet. I've had 2 of these phones so far. 1 3 got t-mobile t swap for an mda vario 2 at the time as the phone wouldn't stay stable for more then a few minutes. same result with 2 like 4 like replacements they sent me. ifinally said enough I want the closest thing tech spec wise to it. the 2nd one was my wifes which she barely used now that shes moved on to a different phone I've started playing a bit with it as it's over 12 months old. and I put it back into the box and up on a shelf as soon as it started doing the rebooting thing like the first one. NO WONDER ORANGE START DISCONTINUING IT AS WELL DID T-MOBILE UK.
UPDATED :
After reading a few of the posts aftr mine, I set out on a mission to determine the more exact reason for this cause. I found the unlike most mobile e.g: sony, lg, nokia etc. this phone would nout power on from the mains adapter without the battery. I figured initially it must have been the manufacture thinking this is not a laptop and the mains adaptr was intendd to charge batteries and then run the device. this also prevents data loss or file system corruption incase your mains charger comes loose from the device while playing. however I found that by putting my finger (when your finger tips are lightly moist and conductive) over the battery terminals on the device it would infact power on and work. now in light of this there are 6 terminals to make conduct with the battery the outter 2 on each extreme end are your + and - . the 2 inner ones are likely then to be battery voltage sensor and battery temprature.
so I said great way to test a theory. I unplugged the mains charger and started downloading files from my pc to the memory card over wireless. this of coarse caused the battery and the device to heat up very quickly. within about 10 minutes it did as expected and shut off. then when pressing the power button could not make it back to the main today screen either it would shut off on the windows mobile splash screen OR it would shut off during the first splash at bootloader.
I then removed the now very warm battery and put my finger on the battery terminals making sure the 2 center pins were touching my finger. voila th device powered on and booted up just fine. I then went back to doing file transfers and it never shut off on me again as lon as I held my finger on the battery terminals. in short I fooled it into thinking the battery was there but but that the temprature was fine. wm6.1 from ranji's 7.1 could tell there was no bettery to charge but the temp sensor was fooled. conclusion: the reason 2 replacement handsets in the past sent to me by t-mobile conitune to fail was not infact an internal problem that was main board related it was the battery incorrectly sending wrong temp info or a faulty battery that was getting to hot and the manufactures own safty device was shutting the device down to cool off the battery. this would be why in the past I would be able to just leave it off and eventallly it would work again. I felt like such a fool but at the same time I felt good that I got 1 traded for a vario and that now all I need to do to fix my mda pro is t get a new battery. I am man enough as you can tell to say wheni was wrong and I was. in light of this new info I would recommend the device to others but if you start getting random shut downs and turn offs during internet over wireless or gprs and the device is wamr ask your provider for a new battery or replace it yourself maybe even with a larger capacity one as it will likely resolve your problem. I know there are other posts i've done about this subject and I HOPE that those that have read them read this update as it applies to all htc universals regardless what branding they fall under.
enjoy in knowing new things
cj
Click to expand...
Click to collapse
just a reply to kick this into attention as will be important to a lot of people I bet
A few hours ago my girlfriend was just looking at her Triumph (was watching for messages so she wasn't actually doing anything on it) when the screen turned off. Now it wont turn back on. Have tried the power button, turning on the bootloader, and removing the battery for 5 minutes. No matter what we can't get the phone to turn back on. Any ideas on what has just happened? The phone is rooted with gingerbreak with titanium backup installed. That's it. We got the phone at Best Buy and this is our second phone. We're probably past our 30 days so this kind of bugs me! Any idea what we can do from here? Any other tricks to try?
As a quick update, Best Buy tells me that an Exchange counts as an original transaction. So I'm only 17 days into my "new" transaction. I can't believe neither of these Triumphs have lasted more than three weeks :\
Did you have it connected to the charger while using it? I have noticed it gets very hot even without the charger being plugged in. It may have over heated. Just a thought. Good luck. Let us know what happens.
Sent from my MOTWX435KT using XDA App
No, the charger wasn't connected at the time. It was just sitting there with the screen on. The Significant Other wonder why it wouldn't turn off so she hit the power button and it didn't do anything. Finally the screen just went black but the backlight was still obviously on so she pulled the battery and put it back in. From there, she pushed the power button and the virgin mobile logo came on and nothing else. She had to remove the battery again. She put the battery back in once more and was able to get the Virgin mobile logo one more time. It froze after the logo and she pulled the battery one more time. After that the phone refused to turn on at all. When connected to the charger it doesn't do anything. Still completely lights out on the phone.
Man that sucks. I hope your able to find a fix.
Sent from my MOTWX435KT using XDA App
Same thing happened to me the other day. I let my Triumph lose all its battery to charge it back up 100% (performing a full battery charge cycle), and it will no longer turn on. even when I have it plugged in the red light indicator will not light up most of the time.
Funny thing is, this is also my second exchange from best buy and luckily im still within 30 days and i have a replacement plan. I really suggest getting the replacement plan (its $30, good for a $300 phone), because unlike best buys other mobile protection plans, you dont pay monthly, you're covered for 2 years, and if you get tired of getting the same phone, they will give you a $300 store credit card.
You know my phone did something similar, my phone died and when i went to plug up the charger i got nothing. I think there might be something wrong with the charging ports on these phones, try wiggling the charger while its plugged in, thats what i did and it finally took a charge
carter6739 said:
You know my phone did something similar, my phone died and when i went to plug up the charger i got nothing. I think there might be something wrong with the charging ports on these phones, try wiggling the charger while its plugged in, thats what i did and it finally took a charge
Click to expand...
Click to collapse
upon closer inspection of the charging port, i noticed the female micro usb port was actually pushed further inside, thus preventing most chargers to work. I found a rocketfish charging adapter from best buy that seems to work perfect while my other cable didnt work at all.
As an update, we went back to best buy and sure enough they count the exchange as a new transaction, so I was only 17 days into my second transaction. They exchanged me another phone on the spot and so now we're on the third triumph. GPS checked out ok and the MEID was the correct length. The screen is the worst of the 3 (some pretty bad backlight bleed out onto the screen itself from the sides). I was picky about it but the gf isn't since you can't even see it unless the screen is completely black. So we'll see how this one holds out!
My guess is as was assumed, the battery wasn't getting charged. When the battery was removed for 30 minutes or more we were able to get the logo to show up and nothing more. My guess was the charger wasn't making contact anymore. We wouldn't want to keep a phone like that anyways but it seems like this might be a problem for these phones.
Every once in awhile mine will not power back on. It happened to me a couple of times shortly after I bought the phone.
I tried pulling the battery a couple of times and powering back up, no go.
What worked... remove battery, press power button for a couple of secs, replace battery, power back up. Has worked every time... so far.
My guess is need to drain some capacitors or that I had invoked part of boot recovery sequence without finishing?
mr2011 said:
upon closer inspection of the charging port, i noticed the female micro usb port was actually pushed further inside, thus preventing most chargers to work. I found a rocketfish charging adapter from best buy that seems to work perfect while my other cable didnt work at all.
Click to expand...
Click to collapse
Have you noticed the "I just broke my Triumph's Screen"- post? We'll If you saw my cracked Triumph, well that's another issue that I just discovered. The battery drained all the way and now it will not take a charge anymore. This is the exact same problem OP is having. Regarding this issue I will open up my phone sooner or later when I get a new one and take pics. I don't mind seeing wth is in there, maybe everything's held up by Elmer's glue lol. I'll make sure to let everyone know hopefully I'll do this within a couple days.
It seems like dead
If Motorola and VMUSA are not serious about resolving issues for Triumph then this phone will be dead anyways - customers won't be buying those. The number of returns are far more than new purchase. It seems like Motorola stopped manufacturing these.
So this phone will either get Ice Cream Sandwich update or it is end of life for this phone.
Anyone come across this? I put it on standby last night after reading a bit of my book on it, and it had around 50% power remaining. This morning, it was totally unresponsive; pressing the power button does nothing at all. I've charged it for 12 hours in the meantime.
I've done the following all with and without the power attached:
- Pressed and held power for 15 seconds through to a minute
- Pressed and held volume up with power to attempt to get into recovery for up to a minute
- Pressed and held volume down with powerfor up to a minute
- Pressed and held power while touching screen (read that one off another forum)
I guess potentially it could be on and in a crashed state and unresponsive to the power, so maybe in a weeks time when it runs out of juice, I'll be able to charge it and power it back up, but in the meantime, I'd welcome suggestions.
A few weeks ago I updated it to the official ICS build that was released, but did the update myself rather than using KIES, as KIES didn't even recognise my Tab's firmware original version. It's been absolutely fine before the update, and since. I only mention it because I've read about the Samsung build of ICS being prone to self bricking itself, but I couldn't determine what the symptoms of this vulnerability were.
Thanks for any help offered,
Will
did you try connecting USB cable and plugging it into your PC? did u get any activity? can ADB recognize your tab?
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Had the same problem while on holidays. Once the battery goes below a certain level, you won't be able to charge it through USB any more. Instead you need to use the wall charger.
I think it's bad enough that the 7.7 doesn't have a micro USB port, but things like that are just stupid and Samsung made a big mistake here. It don't think it's the same with the newer tablets though. It's also not possible to just buy cables or chargers for this strange Samsung port, so when you forget your wall charger at home at some point you won't be able to use your tablet any more.
As long as you charge with the USB cable early enough, you can avoid it though.
A few months ago I experienced the same thing, the Tab just wouldn't turn on anymore.
I tried all there is without any luck.
Contacted amazon and they replaced it with a new one in less than 48 hours.
So far not Problems with the new device.
I have the P6800 and this morning I took it off charge. Put it into standby and only used it for about 20 mins then left in standby all day. It had about 95% remaining when I did so.
Picked it up this evening and the lower left area of the screen was warm and it would not switch on. Didn't think of the ADB idea but will try this next time but I had to reset it and when it powered on tonight after the reset, it was down to 15%. Within about 2 mins of checking stuff it was down to 3%.
Something is running when it is in standby but as I can't switch it on I can't check with BetterBatteryStats or CPUState to know what is wrong.
It does this every day. I am tempted to do a factory reset and reinstall only limited software.
Dave...
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Cluey said:
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Click to expand...
Click to collapse
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
TeeeJaay said:
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
Click to expand...
Click to collapse
hhmmm, interesting.
I was having trouble with wifi just before this happened. Both my GS2 and this have been claiming to connect to my wifi but aren't actually getting an IP address from it.
I can't remember if it was last night or the night before but I manually set an IP address, the signal strength is fine as my abode isn't very big.
After it has recharged I'll have a poke and see what I can find, thanks for the reply.
So my device seems to be working fine again. It had gone SO flat that the date and time were incorrect!
After I could power it on I had a look at Better Battery Stats and nothing looked wrong so I have no idea what happened. None of the apps I'd installed the day before it played up had long wakelocks and weren't running when I turned it off.
For reference they were:
My Tracks
MyTrails
Google Earth
AndSMB
I'd turned both of the GPS tracking devices off before I turned it off for the night.
It hasn't played up since but it hasn't been long so I'll see what happens.
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
A similar thing happens to me every once in awhile. The way i check to make sure everything alright is to see if it boots into download mode. I just leave it plugged in for a couple hours and it eventually comes back on.
someth1ng said:
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
Click to expand...
Click to collapse
this is why my 7.7 is the last tablet/phone from Samsung i'll never trust them they are just bombarding the market with new devices and leaving the old ones to dust
^thats what I thought too but that gs4 is really tempting. I've heard worse about HTC in that regard anyways so that why I'm not going with the one.
Finally.. i bought Sony xperia Z.
I'll sell my galaxy tab 7.7. I.m very disappointed with samsung.
Sent From XPERIA Z
kishd said:
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Unbelievable! ... this trick still works ... thank you very much for you help ...
^^ yo, this 'trickle charge' trick did NOT work on my (long) dead P6800... any other suggestions??
Quite strange because my Samsung GT-P6800 tablet was fully charged, it went completely blank dark as if it was off. To my amazement, SMS keeps dropping and calls kept coming in. Yet it is still as blank as though the tab was off. I pressed the power button and the volume up bottom for it to reboot. It rebooted without the screen coming up. It has been blank for two days now. What could be the cause? And what possible solution can be given?
I posted this on the tmobile site but can't seem to get an answer. I have no idea what to do.
So I've had my phone on for at least 7 days. A notification from Samsung's plus app told me to reboot it because blah blah it helps or something.
So I turned it off.
Now it wont turn back on. Tired holding power plus volume down. Tried booting into recovery. Don't have a Windows PC irght now to plug into and try things , but will install windows on a mac via bootcamp.
When I plug it into any charger. Nothing.
When I set it atop a wireless charger. The wireless charger detects it, meaning it lights up. But the phone itself doesn't give any LED notification.
Phone gets warm while on wireless charging pad also. So it may be charging.
What is going on? Any advice?
Plug it into a charger, hold the vol down and power button for like 30 seconds then the screen should turn on saying its charging, then just power it it on.
Nothing. It gets warm when charging. But nothing.
Am I pressing it wrong maybe?
Strange that usually worked for me when i couldn't turn on my phone normally, can you get into download mode? Vol up + home + power.
Well this sucks i can't turn my phone on now, the battery was depleting somewhat rapidly so i rebooted the phone, once it got to the unlock screen it froze. Now no matter what i try i can't get it to turn on.
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
peachpuff said:
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
Click to expand...
Click to collapse
Same charging from PC?
Tried a different cable?
I have a Lumia 535 that messes up touch if I use my Sammy charger, same if I use my Raspberry Pi charger on my Windows tablet, the touch screen goes mental
Try a different charger / USB lead
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
peachpuff said:
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
Click to expand...
Click to collapse
Too many apps installed... how do these guys get the job in the first place, even as a rep?
It does sound hardware related, I'd probably use your 3 months ext warranty before it expires and the S7 finally commits suicide
Don't think knowledge is a requirement for these types of jobs, phone died again after a reboot and I can't start it anymore, going to the repair center after work.
It would seem not
Hopefully you get someone with at least some knowledge to help this time, likely you'll be needing a new motherboard / phone, unless it's something a bit less drastic like a dodge USB port
I thought it would be the usb port too but i tried using my wireless charger and the light on the charger was on meaning it was charging but it still wouldn't power up, i had it plugged in the whole day today and its completely dead.
Anyway it seems samsung warranty goes by build date + 1 year + 3 months leeway, unless you give them a receipt and then its just one year, so mine was built in feb 2016 so it has warranty till the end of may without a receipt.
Ah well, I suppose at least you get a new phone / board out of it, even thought it's a PITA RMAing your phone
Mine was manufactured 2016.08.16, just two weeks before I got it, so I guess that means November this year without a receipt, but pretty sure I still have the receipt anyway
They replaced the board and all is well now, first time any of my phones failed like this, and it had to be the pricey one.
They did it there and then for you? Was expecting a few days at least, nice job
Yea I've not had any failed phones to date either, hopefully not this one either
I dropped it off at 4 yesterday and it was ready by 7, i was a bit surprised by the speed too, seems they got all the parts in stock.
Can't complain about that service, makes you wonder if they have them in stock and can replace them in such a short time for a reason though... hope it's not a common fault
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
Maybe, but I got it brand new from Google a bit over a year ago (06/2017), making me generally hope it isn't something related to 'natural causes'. I think what bothers me the most about this is that I don't know what went wrong and can't think of anyway to check. Plugging it into a wall plug to charge doesn't do anything and when I plug it into the computer my computer doesn't see that anything is plugged in (as I have installed upgrades via my computer, it definitely has the right drivers and everything to see it...).
The slightly paranoid side of me recalls back a few days ago to an article I was reading about malicious apps using phones to mine cryptocurrency, sometimes leading to those phones wearing down enough that they could even brick. Logically I'm almost positive this isn't happening for two reasons. The first being that I haven't installed anything for about a week (and the phone was working fine until this morning) and secondly because I had an app that monitored my network traffic and there wasn't nearly the throughput I'd expect for that kind of processing. Still, I can't think of what else might have happened...
sdnative1 said:
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
post-mortem said:
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
Click to expand...
Click to collapse
Thanks for the freezer suggestion (I recall that trick for old hard drives, but never used it myself). How long you thinking for that to do anything? I tried about 10 minutes and didn't see any difference (not sure if I should be doing something closer to an hour or more?) I did Google support (online chat) and ubreakifix was one of two other options they suggested. It looks like they're a little bit of a drive for me, but I'll see if I can't stop by in the next couple of weeks. My old Galaxy S5 will have to do in the meantime (which is slow with poor reception at this point, but it functions as a phone, so I've got that going for me
I'll try to update if/when I get details from the repair guys.
If the freezer trick did anything, it would likely be temporary (possibly enough time to get data off of it). It would really just confirm a hardware failure, which at this point is my working hypothesis.
One day my pixel randomly shut down, unresponsive, holding power button did nothing, same when I tried to plug it to a pc or when plugged in.
It restarted when i pressed power + vol- (fastboot mode) for about 40secs - I know, it's a lot, never knew what happened.
Then it just worked normally