One of the atrix's I have seems to have a recurring problem, where periodically, it's found to be off - and will not turn or respond in any way unless the battery is pulled and replaced. Then it turns on just fine.
Anyone have any idea what the likely cause of this is? Is it likely to be a software or hardware issue?
It's unlocked and rooted, running 2.3.4 fruitcake.
Any help is appreciated!
I am having the exact same problem. Sometimes the back of the phone is hot when it happens, but not everytime. Trying to decide if I should return the phone amd get a replacement. It is only a few weeks old. Anyone have any ideas.
TTousey said:
I am having the exact same problem. Sometimes the back of the phone is hot when it happens, but not everytime. Trying to decide if I should return the phone amd get a replacement. It is only a few weeks old. Anyone have any ideas.
Click to expand...
Click to collapse
Either it's a defective phone, a defective battery, or an app is pulling all the juice. I find the majority of the time this happens, once I get the phone up, the battery level is very low. Is this the case with you as well?
Also, if you have two Atrix's, you can try swapping the battery and seeing if the problem stays with the same phone or not.
What it sounds like to me is an issue called "kernel panic" that captivate users experienced. Most referee to it as charge death or sleep death. The phone kind of goes into this sleep mode and the CPU slows way down. The OS tries to up the clock speed to wake itself back up. With the captivate, I had a burning electronics smell under the cover. You said you had a custom rom...... are there any "known" issues that might cause it? Have you tried using setcpu to make sure the minimum clock speed isn't the problem? I know I don't have an atrix, but I should be getting one soon. I have the Infuse 4g right now.
Sent via the Interwebs
bzmotoninja83 said:
What it sounds like to me is an issue called "kernel panic" that captivate users experienced. Most referee to it as charge death or sleep death. The phone kind of goes into this sleep mode and the CPU slows way down. The OS tries to up the clock speed to wake itself back up. With the captivate, I had a burning electronics smell under the cover. You said you had a custom rom...... are there any "known" issues that might cause it? Have you tried using setcpu to make sure the minimum clock speed isn't the problem? I know I don't have an atrix, but I should be getting one soon. I have the Infuse 4g right now.
Click to expand...
Click to collapse
I find that fascinating. This is the first I've heard of anything like it. And the only thing being run is a Fruitcake build - as close to stock as you can get for a ROM. But I've got the same fruitcake build on other Atrix's that don't have any problems, so I think we can probably rule that out.
Is there any way to diagnose whether this is what's happening without making any changes? Or is that the only way?
Also, is this problem known to have its roots in hardware or software?
Some have issues in hardware others arose from botched roms. Shouldn't really say botched, but not installed right. I know with the other phones I have had, they recomend that you wipe, install, factory wipe, then reboot. All in cwr. Like dalvik, and such. Have you swapped the batteries yet? Or maybe, make sure you get the battery to an actual 100%. Charge to full, turn off, plug in, charge again to full. Reboot to recovery and wipe battery stats. If all else fails, call at&t and tell them your battery is failing. They should send you another.
Sent from my SGH-I997 using XDA App
Anything yet?
Sent from my SGH-I997 using XDA App
I don't have many apps on the phone and this started happening almost immediately after I got the phone; before I had any apps loaded. Thus it sounds like it might be the phone or the battery. I don't have another phone to check the battery out. Might have to take the phone back and see if they will give me a new phone or battery.
bzmotoninja83 said:
Some have issues in hardware others arose from botched roms. Shouldn't really say botched, but not installed right. I know with the other phones I have had, they recomend that you wipe, install, factory wipe, then reboot. All in cwr. Like dalvik, and such. Have you swapped the batteries yet? Or maybe, make sure you get the battery to an actual 100%. Charge to full, turn off, plug in, charge again to full. Reboot to recovery and wipe battery stats. If all else fails, call at&t and tell them your battery is failing. They should send you another.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
I'll see if I can get another battery and see if the problem continues to occur. Thanks!
Related
I'm having an issue with my phone battery level detection.
It won't charge past 97%. I noticed it lately within the last few days, i would charge my phone, but when i would grab my phone for the day and take it off the charger, it instantly dropped down to as low as 95%. But, when i plug in the AC cable, it says 100% charged.
Anyone have any info about this? Also, i powered the phone down and charged it fully with the AC adapter, and the highest level i got was 97%.
Also, i have seen the phone has a lag issue, gps issue, no word about froyo, and no notification led. Most of those were fine for me, but since i've had the phone, most of the battery has been used for cell stand by even though i've been in areas with excellent reception. And now with this battery level discretion, i'm a little worried about my decision. I only have tomorrow to return the phone and now that idea is gaining more and more weight for me.
geoffcorey said:
I'm having an issue with my phone battery level detection.
It won't charge past 97%. I noticed it lately within the last few days, i would charge my phone, but when i would grab my phone for the day and take it off the charger, it instantly dropped down to as low as 95%. But, when i plug in the AC cable, it says 100% charged.
Anyone have any info about this? Also, i powered the phone down and charged it fully with the AC adapter, and the highest level i got was 97%.
Also, i have seen the phone has a lag issue, gps issue, no word about froyo, and no notification led. Most of those were fine for me, but since i've had the phone, most of the battery has been used for cell stand by even though i've been in areas with excellent reception. And now with this battery level discretion, i'm a little worried about my decision. I only have tomorrow to return the phone and now that idea is gaining more and more weight for me.
Click to expand...
Click to collapse
1.) I would say exchange your battery (I have never heard on that issue)
2.) There is something called a lag fix.. So search next time..
3.) There is also a GPS fix.. So once, again.. search
Defiantly keep the phone.. Download a ROM called Bionix 1.3 With Lagfix& OC/UV (1.4 will be released tomorrow)
Download a program called SetCPU and OV it to 1.2 (It will make the phone much faster)
Tada, you have what you should of had
download and install rom manager.. install clockworkmod, boot into recovery, wipe battery log..
I know there's a lag fix but why should we need that in the first place? I personally haven't needed a lag fix, but I haven't heard anything from Samsung about fixing it.
Also for the gps, flashing patches is still pretty hit or moss for a lot of people and even then, I've seen a lot of people that have their compassion still messed up. My question is not along the lines of "why isn't Samsung doing more to fix this issue across theory US galaxy s line?"
I mean, I've seen probably 3 official updates to "fix" the gps/compass issue, and the only one I haven't heard about the results is the fascinate. And I haven't heard ANYTHING from T-Mobile about fixing ANY is the issues that the vibrant has, on than "they're working on it".
It's word, if it wast for me reading the new engadget post today polling about people's epic and listing the problems it's facing (which most seem to echo across the galaxy s line) coupled with this battery issue, I wouldn't have second guessed my phone decision. But when o saw this, and my battery, it gave me a bad taste similar to what I faced in the slide community.
I love this phone, don't get me wrong. I'm just worried about Samsung and T-Mobile management calls.
pinoiryder said:
download and install rom manager.. install clockworkmod, boot into recovery, wipe battery log..
Click to expand...
Click to collapse
I already have that installed. Would it get rid of my phone rating battery in cell standby or fix the part where I only can charge to 98%?
I'm going to try charging from a computer use to see if it's a charger problem or phone problem.
Edit: I am running JAC's kernel for the past 2 days, I wonder if that has anything to do with the charging discrepancy? Also, I'm not running it overclocked.
Sent from my SGH-T959 using XDA App
geoffcorey said:
I know there's a lag fix but why should we need that in the first place? I personally haven't needed a lag fix, but I haven't heard anything from Samsung about fixing it.
Also for the gps, flashing patches is still pretty hit or moss for a lot of people and even then, I've seen a lot of people that have their compassion still messed up. My question is not along the lines of "why isn't Samsung doing more to fix this issue across theory US galaxy s line?"
I mean, I've seen probably 3 official updates to "fix" the gps/compass issue, and the only one I haven't heard about the results is the fascinate. And I haven't heard ANYTHING from T-Mobile about fixing ANY is the issues that the vibrant has, on than "they're working on it".
It's word, if it wast for me reading the new engadget post today polling about people's epic and listing the problems it's facing (which most seem to echo across the galaxy s line) coupled with this battery issue, I wouldn't have second guessed my phone decision. But when o saw this, and my battery, it gave me a bad taste similar to what I faced in the slide community.
I love this phone, don't get me wrong. I'm just worried about Samsung and T-Mobile management calls.
I already have that installed. Would it get rid of my phone rating battery in cell standby or fix the part where I only can charge to 98%?
I'm going to try charging from a computer use to see if it's a charger problem or phone problem.
Edit: I am running JAC's kernel for the past 2 days, I wonder if that has anything to do with the charging discrepancy? Also, I'm not running it overclocked.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If you have such a problem with it then just take it back & quit whining.
All we are trying to do here is make the phone better, Your right you SHOULDNT need a lag fix in the first place.. but apparently YOU do
Like I said about the not charging all the way thing, just take it to your tmobile store & get a new battery.. Not to mention that they actually did say that froyo would be released after G2 witch is going to be sometime next month I beleive
I haven't seen the need for a lag fix myself and sorry is this entire thread sound like a rant/whine-fest. I do love what's been done for the phone in the face of it's adversity. And for the most part, I am pretty optimistic about Samsung/T-Mobile fixing the issues this has. I more just writing it all down at once to get it out if my system.
Sent from my SGH-T959 using XDA App
geoffcorey said:
I haven't seen the need for a lag fix myself and sorry is this entire thread sound like a rant/whine-fest. I do love what's been done for the phone in the face of it's adversity. And for the most part, I am pretty optimistic about Samsung/T-Mobile fixing the issues this has. I more just writing it all down at once to get it out if my system.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think that Samsung/T-Mobile wants the devs here to fix the issues jk
But yeah, there just got another update leaked.. JI6
Master™ said:
I think that Samsung/T-Mobile wants the devs here to fix the issues jk
But yeah, there just got another update leaked.. JI6
Click to expand...
Click to collapse
i see that. i also see that tmobile twittered about an OTA soon and not to flash the JI5. that's really more than i've seen from them about the phone lately, albeit still extremely ambiguous.
Also, i just unplugged my phone from USB computer charging. It charged to 100% but when i unplugged my phone it went back down to 97%. So it's not charger related. I'll be going into tmobile tomorrow and seeing if i can say whether it's the battery or the phone by testing out a different vibrant and charging my battery in there.
Also, i am getting kinda pissed that my phone "appears" to get extremely poor reception. It goes from strong signal to nothing, but still saying tmobile in the same place.
geoffcorey said:
i see that. i also see that tmobile twittered about an OTA soon and not to flash the JI5. that's really more than i've seen from them about the phone lately, albeit still extremely ambiguous.
Also, i just unplugged my phone from USB computer charging. It charged to 100% but when i unplugged my phone it went back down to 97%. So it's not charger related. I'll be going into tmobile tomorrow and seeing if i can say whether it's the battery or the phone by testing out a different vibrant and charging my battery in there.
Also, i am getting kinda pissed that my phone "appears" to get extremely poor reception. It goes from strong signal to nothing, but still saying tmobile in the same place.
Click to expand...
Click to collapse
I'm talking about JI6 not JI5...
My vibrant has done the same thing once. I thought it was weird. Hasn't done it since though. I really don't care about one or two ticks on the battery guage. I use battery indicator pro though because the built in battery meter sucks.
i use a flashed version of the battery status reader as well as battery indicator. And it doesn't go up to 100% unless i'm using the charger. but once it's off the charger, it drops to 97%.
geoffcorey said:
i use a flashed version of the battery status reader as well as battery indicator. And it doesn't go up to 100% unless i'm using the charger. but once it's off the charger, it drops to 97%.
Click to expand...
Click to collapse
im having the exact issue, ive already gone thru clockwork and wiped the batt stats n still the same problem, it says 100% charged, take it off the charger and drops down to 97%.... i was tempted to swap a battery for a dude i was unlocking his phone for (he didnt know it was uber easy lol, so i made $10 for my hard efforts) but i didnt... im calling tmobile so they can send me another one as i type..
rel500 said:
im having the exact issue, ive already gone thru clockwork and wiped the batt stats n still the same problem, it says 100% charged, take it off the charger and drops down to 97%.... i was tempted to swap a battery for a dude i was unlocking his phone for (he didnt know it was uber easy lol, so i made $10 for my hard efforts) but i didnt... im calling tmobile so they can send me another one as i type..
Click to expand...
Click to collapse
I went to my local tmobile store, they swapped batteries. They also told me they couldn't do anything since i was out of the 14 day exchange period. The thing is though, i bought the phone outright, and when you do that you have a 30 day return period.
But they also didn't have any vibrants in stock so i had to go to the nearest corporate store. I got there, and they were puzzled as to why i was having an issue, saying that "it lasts for the stated amount of time, so i'll most likely have to charge you a $10 restocking fee" crap. They ended up doing a 1 time courtesy exchange. I'll see how this vibrant goes. I also checked to make sure it wasn't hardware locked (it go into recovery with the volume keys).
I don't think it's a battery issue, as I've seen it quite often. Mine does this sometimes as well but it doesn't really bother me. Someone posted that there was a fix you could do using ADB from the computer, but it was a month or so ago and I'm too lazy to look for it.
gravis86 said:
I don't think it's a battery issue, as I've seen it quite often. Mine does this sometimes as well but it doesn't really bother me. Someone posted that there was a fix you could do using ADB from the computer, but it was a month or so ago and I'm too lazy to look for it.
Click to expand...
Click to collapse
well after swapping my battery for a new one and experiencing the same issue, i know it's not battery related. it's phone related. I want my phone to charge fully, not almost fully.
Its been doing this for a while. I'll go to check it and it's off, but the battery hasn't died. Last night it did this so my alarm didn't go off for work this am. Everything is stock on my phone. N
stock everything so please don't ask what rom/kernal/whatever ..
Any suggestions? I can't be late to work again because this phone is for ****
If you are absolutely sure that your phone is completely stock, then the problem is probably your battery. Does this only happen when the phone is not plugged in?
It does it when its on the charger too. Like I woke up this morning and found it off but it was on the charger when i found it like that. i havent flashed anything or changed any roms or kernals which is why I say its stock. otherwise people ask me what rom im using or whatever.
It could possibly be a lose battery. Generally people will notice it when there is movement to the phone i.e. shaking it or dropping it. If the phone is completely still when it randomly shuts off chance are that a lose battery is not your issue. Still its worth looking into. Most people fix a lose battery with a small piece of cardboard wedged between the battery and case.
Good luck!
Probably not a loose battery. I just had it charging for the past hour and went to check it to find it turned off. Any suggestions as to why it happens when its just sitting there charging?
My phone did the same thing, and with my wife having the same phone I was easily able to rule out battery. Since your complety stock it sounds like a problem with the phone. If your with Tmobile give them a call and see if they will replace it, they did for me.
Sent from my SGH-T959 using XDA App
My phone is already a year old tho. i think my warrenty is gone,
(At least in my case) the warranty didn't matter. I had a 100% bricked vibrant and I told them that "it just happened" and no one was the wiser. I got a replacement and all I had to pay for was shipping. So my advice, tell the T-Mobile rep: my phone is broken through no fault of my own and I want a replacement.
Edit: that stuff happened like a year ago so I don't know if that policy still applies. Hope this helps though.
I did download Load Monitor and made the settings a certain way. so far it hasnt shut off. We will see if I am late to work again tomorrow.
even some stock Samsung roms (like kb5 and ka5) lately have had the same turning off problem for me as well. i think it has to do with some of the older vibrant's when the hardware (battery) becomes charged or is depleting slowly, triggers a software issue like a discharge error forcing an emergency shut-down to prevent damage. the only thing i can recommend it to take the advice of previous posters and get a replacement or upgrade if you are nearing the end of your contract.
just a few things to consider.
Have you tried, I know this sounds odd, a drastic ROM change? Not just switching between Froyo ROMs, but moving to a Gingerbread ROM like MIUI? Could help isolate the problem if it keeps happening under a different OS.
my problem is gone now that i use custom roms. the same could help you thread starter.
Edit. i know you refer to developers as op's but do you do the same to a thread starter?
Pretty sure OP stands for "Original Poster", as in the person who started the thread. Developers start a lot of threads which is probably why you thought it referred only to developers.
Since installing Load Manager my phone hasnt shut off by itself. Seems to have fixed the problem!
My brother bought a second hand SGS2 (I9100), and it has some weird glitch affecting the battery reading.
Even though the phone is fully charged, when the phone goes to standby mode (sleep), after a few minutes, or seconds, it suddenly "thinks" that the battery is not charged, so it turns itself off. When you turn it back on, is says we need to charge it, but after 15 to 30 seconds, it reads the battery properly, and goes back to the right battery %. If the phone doesn't go to standby, then the battery glitch doesn't affect, it doesn't say it is not charged, and it can be used with no problems for hours.
I've reset it to factory reset, but it hasn't solve the bug. We have tried also changing for another battery (I have one as well), but is not that, the battery is perfect (both of them). We changed the ROM a couple times, also changed the Kernel and root it, but the issue does not go away.
Can anybody tell me with the info provided if it is a hardware issue (hope not) or if it can be on the software? I've searched the forums but didn't find others with the same issue.
Thanks in advance for any help you can give us to figure it out.
Run a battery calibration app
Sent from my GT-I9100 using Tapatalk 2
rahul1031992 said:
Run a battery calibration app
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my GT-I9100 using xda premium
While you're at there, resetting the fuel gauge chip a few times wont hurt either.
ldve said:
My brother bought a second hand SGS2 (I9100), and it has some weird glitch affecting the battery reading.
Even though the phone is fully charged, when the phone goes to standby mode (sleep), after a few minutes, or seconds, it suddenly "thinks" that the battery is not charged, so it turns itself off. When you turn it back on, is says we need to charge it, but after 15 to 30 seconds, it reads the battery properly, and goes back to the right battery %. If the phone doesn't go to standby, then the battery glitch doesn't affect, it doesn't say it is not charged, and it can be used with no problems for hours.
I've reset it to factory reset, but it hasn't solve the bug. We have tried also changing for another battery (I have one as well), but is not that, the battery is perfect (both of them). We changed the ROM a couple times, also changed the Kernel and root it, but the issue does not go away.
Can anybody tell me with the info provided if it is a hardware issue (hope not) or if it can be on the software? I've searched the forums but didn't find others with the same issue.
Thanks in advance for any help you can give us to figure it out.
Click to expand...
Click to collapse
About 2 weeks ago, a guy reported a very similar (probably exact) problem.
After many troubleshooting, the problem was hardware related.
Visit the, thread, try all the proffered solutions, and if your problem is not solved, then it's a confirm hardware issue. : forum.xda-developers.com/showthread.php?t=1843783&highlight=battery
Swyped from my Galaxy SII
Dont wanna sound rude or anything, but s2 is still not a cheap phone (for most of people atleaset) , meaning,
when ur buying smartphone 2nd hand, the seller will have to agree on me turning on phone, playing with it for 20 mins, check everything and so on..
Display, RAM, everything, meet somewhere where is wireless so you can download android system tester off market etc etc
Because i am almost sure this is HW problem mate. I suggest you call him right away, and hope he still has the same number
loop4444 said:
Dont wanna sound rude or anything, but s2 is still not a cheap phone (for most of people atleaset) , meaning,
when ur buying smartphone 2nd hand, the seller will have to agree on me turning on phone, playing with it for 20 mins, check everything and so on..
Display, RAM, everything, meet somewhere where is wireless so you can download android system tester off market etc etc
Because i am almost sure this is HW problem mate. I suggest you call him right away, and hope he still has the same number
Click to expand...
Click to collapse
Not rude at all! My brother review the phone, but didn't seem to have any issue at the beggining, started to fail like a week later.
We can return the phone at any time, is just that they don't have another one to give us right away, and most likely they'll take it for a review before we can get either a refund or another unit, so we wanted to explore all the options ourselves first.
I'm sure he'll be returning the phone soon as we pretty much ran out of options.
Jokesy said:
About 2 weeks ago, a guy reported a very similar (probably exact) problem.
After many troubleshooting, the problem was hardware related.
Visit the, thread, try all the proffered solutions, and if your problem is not solved, then it's a confirm hardware issue. : forum.xda-developers.com/showthread.php?t=1843783&highlight=battery
Swyped from my Galaxy SII
Click to expand...
Click to collapse
Thanks a lot Jokesy, you have been very helpful as I followed the thread and it is the exact same issue.
After a few days, the problem got even whorse as everytime is even harder to turn it on because it reads low battery. We can only turn it on, most of the time, through Recovery, as the key combination for Download Mode doesn't even respond. Sometimes doesn't respond at all. We just need to turn it on one more time to flash the stock ROM to return it.
ldve said:
Thanks a lot Jokesy, you have been very helpful as I followed the thread and it is the exact same issue.
After a few days, the problem got even whorse as everytime is even harder to turn it on because it reads low battery. We can only turn it on, most of the time, through Recovery, as the key combination for Download Mode doesn't even respond. Sometimes doesn't respond at all. We just need to turn it on one more time to flash the stock ROM to return it.
Click to expand...
Click to collapse
Wow! then it is a hardware problem too. Since you said it will be returned, I think it's the last option too.
Good luck and hope you get a normal unit
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.
Hi,
Wondering if anyone can help me...I'm at a total loss. Any ideas would be greatly appreciated.
About a month ago my i717 Note started having issues where I'd be using it and suddenly just power off without warning. When I try to reboot it without being connected to wall charger, it very rarely boot back up, usually dies again mid boot.
If it's actively being powered to the wall/USB the issue has never happened...Most of the time after this happens the battery will indicate that it is actually completely drained ie 0% batter life...however sometimes once it's plugged in it will show some other % that isn't even low battery.
This issue occurs even though I could have 90% battery life prior to the crash. My battery stats in settings shows normal discharge, then just a straight veritical line to 0% followed by the normal recharging...
I have 2 batteries, both Samsung OEM so I cannot think both my batteries happened to crap out at same time.
I had been on Black Jelly for many months without any sort of issue, then suddenly this. I have tried these things, to no effect at all:
- delete batterystats.bin in /system/data
- added several layers of tape on the bottom of battery to ensure has full/tight contact with pins
- loaded several different ROMs
- Completely wiped (Factory Reset, Cache, Data, System...and eventually even did Internal and External Memory wipes from TWRP)
- Odined back to Stock 4.1.2 image
The last application I loaded was Google Hangouts and was also the application I first noticed the issue. I video chat with my parents with it and first noticed it happen there which thought was odd since phone never warned me for low battery...however now it happens all the time despite all the steps I took above plus I don't have Hangouts loaded on the phone atm.
I am currently running Stock 4.1.2 and it's still happening there. As is I cannot use my phone for probably more than 5 minutes without this happening. If I can't solve this I'm going to have to go back to my Cappy which just makes me sad since my Note had been a good phone previously.
Since it's happening across ROMs and after total wipe (if there is any more wiping I should do that might help let me know), plus Odin back to Stock I feel as though it must be some sort of crazy hardware issue. I've only ever seen this happen when I'm actively using the device...it hasn't happened when in in sleep mode (ie screen is off).
Any ideas?
TIA
I agree this happening with 2 batteries is hard to believe, but I will ask anyway.
How old are the batteries? They are notorious to go south after about a year.
Are they swollen at all.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
I agree this happening with 2 batteries is hard to believe, but I will ask anyway.
How old are the batteries? They are notorious to go south after about a year.
Are they swollen at all.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply...
They both 2+ years old now. No bulging they would appear to be in good shape. I've never had excessive battery drain before, and currently when the issue is not happening the battery life is ok. IE if I don't use my phone at all, battery drain is about what I'd expect. I haven't seen the issue happen when it's sleeping, just if I'm actively using the phone.
Sometimes the issue doesn't happen, and it'll discharge all the way down to 0% normally...it's so random and frustrating...I do know that if I use my phone non-stop for probably about 10 minutes it's going to happen though, usually in less than 5 minutes. Again, I don't see the drain, it looks like normal discharge and I'll go from 75% -> phone off in the blink of an eye. Oddly if I then plug it in the battery charging icon you get (when is powered off) sometimes indicates it's actually not empty.
Also of note when it does happen the phone isn't hot, I can handle the battery fine. Also I have the OEM wall charger for the extra battery, so I know that the battery should be getting fully charged from that (so isn't a USB charge issue on the phone itself).
Is there a good battery stats app I can try? The battery stats in sys settings doesn't show anything hogging.
Thanks again.
All those apps are going to do same thing and I don't put a lot faith in them. 2 years is a long time for battery. Mine went south at about a year and went bad in a hurry. Running KK doesn't help either, it's a real battery sucker on our notes.
You are not the first to run into this issue with those symptoms. I believe more often than not, resolved with new battery. I just got one myself from Amazon for $9. Ravpower 2750 I think. There is a thread in accessories.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
All those apps are going to do same thing and I don't put a lot faith in them. 2 years is a long time for battery. Mine went south at about a year and went bad in a hurry. Running KK doesn't help either, it's a real battery sucker on our notes.
You are not the first to run into this issue with those symptoms. I believe more often than not, resolved with new battery. I just got one myself from Amazon for $9. Ravpower 2750 I think. There is a thread in accessories.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough I may try that...
The other thing that happened that maybe points to hardware is that previous to all this happening I got a bunch of errors when Play would try to auto update my apps, saying there wasn't enough space. I was on vacation at the time, so I didn't have any time to try to figure it out. Then this battery thing started happening. Not sure how it could be related, but maybe my RAM is fubar.
I'm getting my Cappy back from a friend so I may try that first, I kinda miss that phone...
Thanks again
Madtowndave said:
Fair enough I may try that...
The other thing that happened that maybe points to hardware is that previous to all this happening I got a bunch of errors when Play would try to auto update my apps, saying there wasn't enough space. I was on vacation at the time, so I didn't have any time to try to figure it out. Then this battery thing started happening. Not sure how it could be related, but maybe my RAM is fubar.
I'm getting my Cappy back from a friend so I may try that first, I kinda miss that phone...
Thanks again
Click to expand...
Click to collapse
Well, another thing that needs to happen every now and again, is going completely back to stock. Re root and everything. Completely clean the pipes. It does wonders.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Well, another thing that needs to happen every now and again, is going completely back to stock. Re root and everything. Completely clean the pipes. It does wonders.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah that's where I am right now...100% stock 4.1.2 and still doing it.