Related
It always seems like there's something wrong with my evo. This morning I went to pick up my evo after it was plugged in all night (like i do every night) and it was burning hot. I looked at it and it said it was 133 degrees so i unplugged it and turned it off immediately, after it cooled down I turned it back on and it was at 70% battery after it was charging all night, so it wasn't charging at all last night even though the light was on and it was showing a green full charge when I woke up. after I turned it on it was on for about 2 minutes then automatically rebooted and then was on for another 3 min and rebooted again for no reason. my phone reboots randomly alot. this happens to me a few times a day usually 2 or 3 times. sometimes while im doing something important and sometimes when the evo is int even being used.
Does anyone have any idea what my problem might be?
My evo setup is fresh 3.3, no custom kernel. ebay 3000mah battery no case or anything like that for overheating. ive been running this setup for months (just with lower fresh builds) and have random reboots. This is the first overheating issue. The only thing thats changed is I started using a .99 ebay blackberry micro usb but ive been using that for a week and never had a charging issue. my hw v is 3
I'm thinking that maybe the battery has an issue. Have you tried with the old battery? As far as the other problems that you have, it does not look good. Try reflashing, if it does not fix it then it is likely that you need your phone replaced.
fenixjn said:
I'm thinking that maybe the battery has an issue. Have you tried with the old battery? As far as the other problems that you have, it does not look good. Try reflashing, if it does not fix it then it is likely that you need your phone replaced.
Click to expand...
Click to collapse
Im not sure because Ive been using this battery a long time with no problem, even now I plugged in the phone and its charging fine with no problems. If it does this again tonight maybe its the battery, I was thinking maybe it was something to do with that battery being plugged in to long.
Skittles from tampa?
Sent from my Evo beeesshh
I would say it's your aftermarket battery or BB charger. Try and use the OEM accessories.
Sent from my PC36100 using XDA App
DirtyShroomz said:
Skittles from tampa?
Sent from my Evo beeesshh
Click to expand...
Click to collapse
no, but Florida yes
gqstatus0685 said:
I would say it's your aftermarket battery or BB charger. Try and use the OEM accessories.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
what about the rebooting issue? this was there before the aftermarket battery and charger
skittlesV1 said:
what about the rebooting issue? this was there before the aftermarket battery and charger
Click to expand...
Click to collapse
As I said before, try reflashing the ROM and see how it behaves. If the problem is still there AFTER a clean install then it is hardware related, if not then, well keep the ROM
skittlesV1 said:
no, but Florida yes
Click to expand...
Click to collapse
Ahh lol welcome onboard! Yes I believe it's probably the charger and not the battery. $0.99? Great deal, but be careful.
I got the same over heating issue on the stock battery a day ago. It was burning hot when I woke up, and took out the battery with the ac on blast for a minute. It wasnt plugged in, so I was surprised it happened while on the stock battery. Went to my 3000mah battery from ebay, that I have never had any problems at all with.
I was running cm6 with stock kernel. Im guessing it was a freak accident, since no reboots or any after effect from the heat.
On the positive side, I was able to push down the screen due to the heat and fix my light leakage problem
fenixjn said:
As I said before, try reflashing the ROM and see how it behaves. If the problem is still there AFTER a clean install then it is hardware related, if not then, well keep the ROM
Click to expand...
Click to collapse
Is there a chance it might be something to do with apps ive installed?
skittlesV1 said:
Is there a chance it might be something to do with apps ive installed?
Click to expand...
Click to collapse
That is precisely why you need to reflash so you can know for sure if it is a problem with the device itself or just a software glitch.
See if you have too many rotation options checked in cm settings. That made mine reboot a lot. Now just have 90 and no more issues...
Sent from my PC36100 using XDA App
I dont use CM I use fresh
The only external item left is the sdcard. Try another. If it still reboots, then return it for service/replacement. The low battery and heat and reboot can all be caused by a large amp draw. Install alogcat from market and look for messages indicating why. You could also use quicksysteminfo from market, and look at the dmsg's.
I have had a similar problem with my girlfriends Evo. Random reboots until it got to the point where it was just stuck rebooting. After reading this thread, I recognize battery heating as a symptom as well. I ended sending it in to HTC for warranty repair. It turned out to be a bad chip of some type. Having seen a number of threads regarding random rebooting, I wonder if there might not be a defective series of these chips. At any rate, the warranty process was quick and easy. No problems since I got the phone back. This was also an unrooted phone, so I think your ROMs are probably working correctly and it is more hardware issue.
Pierceye said:
I have had a similar problem with my girlfriends Evo. Random reboots until it got to the point where it was just stuck rebooting. After reading this thread, I recognize battery heating as a symptom as well. I ended sending it in to HTC for warranty repair. It turned out to be a bad chip of some type. Having seen a number of threads regarding random rebooting, I wonder if there might not be a defective series of these chips. At any rate, the warranty process was quick and easy. No problems since I got the phone back. This was also an unrooted phone, so I think your ROMs are probably working correctly and it is more hardware issue.
Click to expand...
Click to collapse
judging by all my problems id have to say its a hardware issue, my phone seems like its always at 100% cpu and its awake time is always the same as its uptime and i only get about a 4 hour battery life
skittlesV1 said:
judging by all my problems id have to say its a hardware issue, my phone seems like its always at 100% cpu and its awake time is always the same as its uptime and i only get about a 4 hour battery life
Click to expand...
Click to collapse
you need to reflash bad.
There is nothing hardware related that is going to run you 100 cpu all the time.
skydeaner said:
you need to reflash bad.
There is nothing hardware related that is going to run you 100 cpu all the time.
Click to expand...
Click to collapse
even after I reflash The same things keep happening
Just got my phone yesterday. Running Calk's 2.7 and ICS theme, set dpi to 160, looks and runs awesome. However, it always thinks it's either charging or plugged into USB. the red LED never wants to turn off. how can I remedy this problem?
Possibly try turning it off, booting to recovery, clearing cache/dalvik-cache, and then clear battery stats
Was it like this prior to rooting and custom rom?
Apk, that didn't do it.
yes, it did the same thing beforehand. Except takng out the battery solved the problem once.
Get it exchanged ASAP. This is a defect with the USB port. Has NOTHING to do with software. I was outside of my 14 day return and Sprint made me send it to Samsung to get fixed. $7 jig and two weeks later it was fixed.
With my tech background I would say check the charging port. Could be a metal shaving or *gasp* corrosion!
Sent from my SPH-D710 using XDA App
my phone sort of has the same issue...it charges fine but i cant get it to connect to my computer..my phone thinks it still charging yet i have it plugged in my computer it doesnt give me the option to switch it to usb mass storage..
Got it on Craigslist, no exchange possible.
Dioscorus said:
Got it on Craigslist, no exchange possible.
Click to expand...
Click to collapse
Shouldn't matter. The phone has a one year warranty from Samsung. I bought my wife an Epic on craigslist last year and had it repaired under warranty.
Sent from my SPH-D710 using XDA App
Yup. I had the same problem. I think it is related to the USB port (from reading a few SGS2 threads). I took it to the Sprint Store and they said the USB port looks good. They reset it and it still acted that way. However, 2 hours later the problem is gone. They ordered me a replacement so I'm still going to take it because who knows why the problem starts. I did have Calk's rom and also have the battering monitoring widget by 3C and I had cleared the battery stats multiple times prior to the symptoms starting. Just proving as many clues as possible...
What do you mean by reset?
Funny I see you have this problem (not really funny) because I noticed the same thing last night and just figured it was Rom related.
It sucks... can you give more details about the reset process? Soft reset?
and bump...
Dioscorus said:
and bump...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1344882 and see if it helps.
Sent from my SPH-D710 using Tapatalk
no dice
I had the same problem.
The red light was on all the time, only went out when I got a text. If I pulled the battery the phone would show like it was charging as soon as I put it back in. It would show the battery animation on the screen not plugged in.
After a battery pull the phone would also not boot using the power button, had to boot to recovery and boot from there.
Took it to sprint, they gave me a new battery. Solved the problem only until phone was plugged in to charge. Then started all over again.
Turned out to be a problem with the USB port and they ordered me a replacement.
got it fixed! looks like the pcb on the port was sitting too close to the lower edge of the phone. pushed it up gently and now it seems to be working. thanks for the direction, nivron.
my other concern is that battery life sucks ass. drains really quick (at the rate of ~6%/hr!). again, running calk 2.7 + ics theme. also, taking out the battery seems to reduce the life 20%. what's the deal...
Hmm, now the USB cable needs to be at a certain angle for the phone to charge. Is there any way a Sprint store could furnish a replacement for me?
When my Galaxy Nexus GSM is not plugged in, the battery shows itself as "discharging". Previously this used to be "not charging". I have tried multiple (Jelly Bean) ROMs, different cables, wall and USB chargers. Same problem. The larger issue: my PC no longer recognizes my phone and I have resorted to using AirDroid to transfer files.
Can anyone shed light on this issue?
I have done full wipes, including wiping battery stats.
Mine was always discharging...
And make sure that you got fast charge off if you have that on. That disables MTP capability.
I have exactly the same problem...see my thread...its recent!
Sent from my GT-P1000 using xda app-developers app
I had a similar issue, and then not long after the phone refused to charge. I had to take it to get serviced, and the ended up giving me a refurb instead.
I think it has to do with the temp of the battery, if its too hot and you have it plugged in it will say discharging.
SEALBoy said:
When my Galaxy Nexus GSM is not plugged in, the battery shows itself as "discharging". Previously this used to be "not charging". I have tried multiple (Jelly Bean) ROMs, different cables, wall and USB chargers. Same problem. The larger issue: my PC no longer recognizes my phone and I have resorted to using AirDroid to transfer files.
Can anyone shed light on this issue?
I have done full wipes, including wiping battery stats.
Click to expand...
Click to collapse
First, don't use a charger other than the original. The different volts mess with the NFC chip and antenna. Try disabling NFC and rebooting. Leave NFC off and try to charge. If that doesn't do it I have another option that might work but I'm CDMA so you would have an extra step to change lines in file.
Thanks for the suggestions, guys. I tried disabling NFC but it had no effect. My phone is the international version (the box was in Polish) which is not warrantied through Samsung USA, so I guess I'm out of luck there as well. I'm just gonna hang in there until the next Nexus phone, I guess.
JediNinjafication said:
First, don't use a charger other than the original. The different volts mess with the NFC chip and antenna. Try disabling NFC and rebooting. Leave NFC off and try to charge. If that doesn't do it I have another option that might work but I'm CDMA so you would have an extra step to change lines in file.
Click to expand...
Click to collapse
When will people realize that the difference in voltage won't cause any problems with the phone as long as they're within safe range.
I've been using the charger that came with my G2 (htc) on my nexus for months and have no problems. I would've continued using the original one that came with the nexus but it had an annoying whine to it.
biscuitownz said:
When will people realize that the difference in voltage won't cause any problems with the phone as long as they're within safe range.
I've been using the charger that came with my G2 (htc) on my nexus for months and have no problems. I would've continued using the original one that came with the nexus but it had an annoying whine to it.
Click to expand...
Click to collapse
Really because it sure seemed to be my problem a while back and anytime i use a different one. Guess samsung and google must not know what theyre talking about.
Chargers are rarely the problem, however different usb cables might be the problem instead.
New glitch spotted when phone is of and in the charger it wil chrage for like 2 seconds and then the animation saays the phone is full!but 2seconda later its charging again so on and so on... sort of chargingloop..
But it never charges
Sent from my GT-P1000 using xda app-developers app
Sent from my GT-P1000 using xda app-developers app
Am using samr original charger and cord. Works fine
I have this same issue
My Galaxy Nexus from Verizon has worked flawlessly for several months now. It updated about 4 days ago to JellyBean 4.1.1 and I have been charging the same two wall chargers, car charger, and USB cables every day since I got the phone. I even was using the USB charger to deploy and debug a simple application I am building around noon today. This evening at about 8 PM while on the wall charger I noticed the charging stopped. No lightening bolt icon, status says Discharging, and I noticed one time that it said Not Charging. Neither of the wall chargers work, nor is it recognized by the laptop using the USB cable. It is at 65% charge and is dropping fast. It seems that no one has a fix for this other than replace the phone.
Very difficult for me to believe that the USB port just went bad using the same chargers every day. Hard to blame JellyBean that has run at least 4 days with no issue even though several sites point to a possible charging issue. I even dialed *#*#4636#*#* and checked the battery status, and it's health was good. I have not rooted or placed anything on this phone that is obscure beyond my simple near "hello world" development apps. I have rebooted, and performed a battery pull with no such luck. With the number of posts pointing to a JellyBean issue, and users experiencing the same issue after the upgrade to 4.1.1 I am leaning towards this being a software issue, but it is interesting at the number of posts saying that the their only fix is a refurb phone replacement from the carrier.
Pretty odd occurrence, and extremely frustrating. As I said the phone worked fine all day today. This just started a few hours ago for me.
Update
enviux said:
... No lightening bolt icon, status says Discharging, and I noticed one time that it said Not Charging. Neither of the wall chargers work, nor is it recognized by the laptop using the USB cable. It is at 65% charge and is dropping fast. It seems that no one has a fix for this other than replace the phone...
Click to expand...
Click to collapse
OK I have fixed my issue. and it does appear to have been hardware related. I will preface this with you must be very careful not to break your phone with the solution below. I read several posts about using contact cleaner on the USB port, so I looked at the port on the phone and noticed that the "toungue" inside the reciever USB port appeared to be slightly bent down. With the phone off and battery removed I used a needle to wedge under the toungue and bend it up ever so slightly making sure I would not break it. Pluged in the phone and it still did not charge. (That was last night) this morning with the phone at 55% and thinking it was going to need to go back to Verizion I did it again phone off and battery removed only this time a bit more forcefully out of desperation. I definitely moved the "toungue" up and even had a bit of difficulty getting the USB cord to slide back into the connector. But when it did the Phone is charging again. Appearantly I must of jammed the plug into the phone upside down last night when getting into my car and bent the "tongue" in the USB port. Lesson learned, and hope this helps others.
Means the battery has been recharged and discharged to the point were it holds less of the charge. Basically its an older battery, or its been tappered with with, probably a rom using to much ram or pussing the device a bit too far nightly and ported roms could be the cause I say stick to stock kernal unless you really now what to do
Scrap that wrong fourm I think
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Okay, gonna try and explain this as best I can, bear with me.
2.5 years ago or something I got a Gnex from Verizon, brand new. The phone would act like a ghost was using it, like someone was interacting with the touchscreen. It'd randomly call contacts, send texts (random letters/numbers), all kinds of weird stuff. Video of it on day 1 HERE doing this. Took it into Verizon, got a new replacement. Never had the problem again. 2 or so years go by, not a single problem, unlocked, flash, all that, never had the problem again.
About a month ago, I upgraded to a Moto X and passed this phone on to a family member. At the time was running the latest stable Cyanogenmod ROM, the last for JB. 10.2 maybe? Anyway, that's what ROM was on it, again, no problems. Factory reset the phone to wipe my stuff, left it rooted and unlocked. I gave them the phone, battery, extended battery, and a few cases as well, no charger cause I know they'd twist up and destroy the factory cable. Setting the phone up for them battery starts going low, used their charger. Cable had shorts and crap, scavenged around looking for good charger. Get phone set up for them, and I'm done, handed off.
A day later, they're complaining that the phone is going crazy, like a ghost is using it, and it's randomly calling people, sending texts, opening menus, not charging, etc. Sounds like EXACT same issue I had with my very first Gnex that I exchanged. Figured that was really strange, maybe it was the software. Factory reset to latest factory image 4.2.2, lock BL back up, completely bone stock. Re-setup phone and all that jazz. Phone's acting fine. Decided this time that'd I'd let them have the original stock charger, thinking maybe that'd help with the charging issues too. All seems well....
However, during the reset and all, and after re-setting up the phone, battery is low.... plug it in with a known good charger of mine, but not stock original, and all the sudden the phone's freaking out again. Turn screen off, turns itself back on. Dialing people, opening apps on its own, etc. Figure maybe this Gnex just won't take any charger except it's original. Pull battery, reboot, phone's fine, fine for 10+ minutes. Plug in OEM charger this time, wait a few seconds, unplug, phone goes crazy.
Also interesting, they brought another charger of theirs with a little red LED on, plug it into wall, red LED comes on. Interestingly, if the charger is unplugged from wall with red LED off and I plug it into the phone.... the red LED on the wall charger turns on... that's not right. So.... here's where I'm at now. If I pull battery, reboot, and never attach a charger, the phone acts perfectly fine. The instant I plug in ANY charger, it'll start going wacko and continue to until I pull battery and reboot. At first I thought this was a charger issue, but now... I'm thinking it's battery related. This little experiment of getting the phone to go crazy after plugging in a charger applies to both the OEM and extended battery, regardless of what charger I use.
When I owned the phone, I almost exclusively used the OEM charger, occasionally another charger I had that I know works fine. Gave Gnex to family member WITHOUT a charger, so they were forced to use who know what condition phone charger. I'm wondering if maybe some rogue jacked up phone charger with shorts in it and crap somehow killed the extended battery. Then, they switched to the OEM battery, and again, unknowingly killed that battery too with the same crap charger. So maybe buying a new battery would fix the issue and only using the OEM charger from now on or the other one that was mine that I know works? Or maybe the phone is just broken now? It just doesn't seem right that plugging a phone into the micro-USB should turn ON the red LED on the charger when it's not plugged into the wall, like the power is coming out of phone and going into the LED...
I just refuse to believe that on the exact same day and within hours of me upgrading to a Moto X and passing on my Gnex that had worked perfectly for 2 years in my possession somehow just happens to "break" or "go bad" on its own. Thought it was software glitch/bug in CM, no. Thought it was incompatible charger, no. Maybe the batteries are bad? Maybe the phone's circuitry got jacked up too? Just seems weird that, as far as I can tell, pulling the battery and rebooting fixes it for good until the battery dies. Within 30 seconds of connecting a charger, the phone goes bonkers.
Any ideas? Feel bad, family member probably thinks I dumped a bad phone on them!
Thanks!
What kind of sorcery was that? I honestly don't know what to say about this other than bad timing? I highly doubt a ghost is possessing the phone.
I know a ghost isn't possessing the phone, I just, that's how I best described it when it was going wacko by itself. Plus, interesting topic title, maybe get a few more people to read it and maybe offer some advice or info or something :laugh:
However, I do have a ghost in my house, or a spirit or something. I've seen him, sitting on my couch before. He died in a fire, smoke inhalation, no smoke alarms in the house. House was sold, completely rebuilt, and I am first to live in it since then. Crazy story for a different forum lol
From what I can see, it's just that the screen isn't working properly because of leaked currents from the battery or the charger... Just get the whole screen replaced (it's hard to only replace the glass layer) and should be fine.
Sent from Google Nexus 4 @ CM11
Leaking currents, had it happen to me before from a bad charger. I doubt it's the battery, try an outlet in a different house, they may have bad power.
Sent from my Galaxy Nexus using Tapatalk
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
...and so you should have the screen replaced. I've had Motorola and HTC phones with issues responding to touches when charging, and replacing the screen largely eased the problem (although I still ended up getting a new charger because I don't want it to also damage the newly replaced screen).
Sent from Google Nexus 4 @ CM11
Op may also want to consider relocating... ghost home and ghost phone, that's too much!
LOL
Mike7143 said:
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
Click to expand...
Click to collapse
Could be the battery, could be the USB cables or chargers, could be the USB port on the device, could be the screen. The fact that it only happens when plugged in but with more than one charger and battery makes me suspect the USB port on the device. From my understanding you can buy a replacement. A temporary fix would be to use a charger that charges the battery outside of the phone.
Sent from my Galaxy Nexus using Tapatalk
No ghost... i think
I think its because the charger you use....
I had the same problem, but not with gnx... before gnx I used galaxy i5801...
when I put my mobile in charge, my mobile did some crazy things, like operating itself,...I figured out that the charger I used is not the one I shouldn't use.
every mobile has a charging limits, like voltage restriction..
little difference in voltage could make big difference.
so I changed the charger. problem solved for me.
other than charger.. there are some things can do this, I don't know about all.
I doubt it may caused by your digitizer...maybe is has too much sensitivity, caused by water, dust, pressure, etc....
digitizer and display are not the same.
I faced this one too ( galaxy i5801) before charging problem, but not with gnx.
A digitizer is the part of a touch screen that senses your touch and "digitizes" your gestures into impulses that the phone can understand as commands.
if it continues my last suggestion.... call the priest
Well, I borrowed an OEM standard and extended battery from a friend, neither fixed the problem. My friend did say that similar to my first Gnex, when he first got his, it did the same exact thing, but after a while it stopped and it hasn't done it ever since. I also narrowed it down, or, widened the issue, in that it's not just AC chargers, the exact same stuff happens with a brand new 12V car charger.
Dirty power on the fifth rail of a USB wire. Its either the charger not supplying enough power or a damaged cable.
Sent from my Galaxy Nexus using Tapatalk
My vote is on the screen, due to the digitiser. Replacing the touchscreen could help solve the problem. I was in your family's position when I got a used Motorola Cliq from a friend and the battery was all good, no leaks. Ghosts just started touching it everywhere like a crazed groupie when it went into my possession. No explanation as to why it happened and I didn't look into it that much but replacing the screen is the most likely solution.