Database Info

One S shutting down :(

I just got my new One S a couple of days ago, and I'm one of the lucky few (or many maybe??) that don't have a problem with the chipping of the MAO...
I'm having a different problem though... Or actually i think it's two different problems.
One of them is the following: (and this is probably my own fault for not starting up the battery properly)
I got the phone friday in the mail, but I hadn't yet gotten my micro sim, and I had to leave for the weekend so i left the phone at home and brought my old one on the trip, but i forgot to shut down the One S, and the battery of course died over the weekend, even though I was supposed to fully charge it first to get the battery going..
But here is the problem, and this terrified me!!!
I couldn't get the phone started for like 20 minutes after I plugged it in to the charger.. The power button just made the three buttons in the bottom flash a couple of times, without starting up the phone... Eventually i got it going, but it really scared me.. Now when the phone runs out of battery it still needs around 5 minutes of charging before i can turn it on again... Am I the only one experiencing this?
The other problem, and this is the big one..
Two times the phone have shut down on me without any provocation... I pick it up, and hit the on-button, and the phone boots.. Meaning it was turned off.
And this is NOT because the battery died, as it has been at around 40% battery left.
Does anyone know why this happens? And if there is anything to do about it?
Also am I the only one?

Try a master reset; if it keeps happening, contact whoever you bought it from or HTC and exchange the handset.

P6810 suddenly won't turn on

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?

[Q] Quasi-Pseudo-Semi Bricked?

I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..

Qhastic said:
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Click to expand...
Click to collapse
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.

1BadWolf said:
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Sorry, meant clockwork mod, not cyanogen. I haven't flashed any ROMs on this phone yet.
Do you think the battery issue arose as a result of rooting/installing clockwork mod?

No no..Many phones these days fail to charge when drained because they use software to detect the charger and then allow current to flow.. This is unlike the older nokia phones or current HTC phones.. what you can do is as suggested above.. use a 9V battery or something that ought to do it.

[Q] Weird overheating issue

I've had my Nexus for a couple weeks and noticed early on that it would get incredibly hot in one particular spot on the back and wouldn't charge when I tried to charge it from the wall. I'd suspected my power board of being questionable for some time so I chalked it up to that and made a mental note to replace it. It charged perfectly fine via usb so I just did that.
A few days later I crashed at a friend's place and plugged it into his wall charger without thinking about it. The next morning I was really alarmed to find my phone was boiling hot but it cooled down when I unplugged it and seemed to work fine. It wasn't until that evening when I tried to charge it that I realized it now wouldn't charge via wall outlet OR usb OR connect to my computer and instead this one small area on the back would heat up to painful temperatures within 5-10 seconds of being plugged in. Cue panicking.
So I contacted the retailer I got it from to exchange it and during the time they took to get back to me thought "**** it" and ran down the battery. Then before replying to them I plugged it in again to verify it was still broken and for some reason it was back to normal!? It even seems to charge ok from the wall now.
So wtf happened? This still can't be normal, and I can't have a phone that randomly refuses to charge, but how can I convince them there's a problem? What the hell IS my problem? I can't find anyone else with my specific issue. What's the deal?

Do you have a case on it? If so which one?

Nope! Also, I had stock everything. I was planning to root it but now I can't since I might need my warranty... Been trying to reproduce the error but no dice. Kind of frustrating :/

OnePlus One Charging Issue (URGENT)

Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance

danieljh10 said:
Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance
Click to expand...
Click to collapse
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk

Elius2676 said:
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice, but sadly it's not the cable. Or the charger for that matter. The readings I get from the energy meter are too consistent. After plugging and unplugging several times the phone will eventually pull EXACTLY 3.8 watts. No more, no less, irregardless of battery percentage. As soon as the phone is turned off and plugged in, starts pulling anywhere from 7 - 12 watts, which is normal pull I expect.
Hence why I suspected a dodgy kernel, but no luck :'(

Hello
Hello, I had a not that much similar problem a month ago but i'm sharing and it might help (you never know). I was on a custom CM13 based rom and phone started overheating even when not in use, charging slow. When I let it charge overnight I would find it very hot and almost always stuck and 99%. Clean flashed different roms and the same continued to happen and it really got me worried!
Than I thought before ordering a new battery or charger lets try something really stock. I installed lastest OxygenOS and viola problem went away. (be careful and follow the steps you need to flash OxygenOS, it is NOT recommended you flash it via twrp). After that flashed twrp again and custom roms and havent had that problem again.
Hope it helps

Yeah, I would say your most probable culprit at this point might just be the OS. Try a clean flash and/or a different nightly or release. Try also a different Gapps package (you never know if it's not so much the OS, but maybe an interaction between OS and other software.
Sent from my A0001 using Tapatalk

Thanks for the advice, I've finally managed to free up an evening tonight so I'll try putting the phone back to stock. Hopefully it'll work! I'll post back to let you know if I've had any luck.

Put the phone back to stock Oxygen OS, and no luck. Going to use the Tamper Reset Script and try sending it back to Oneplus. Makes me sad that I couldn't sort it myself :crying: