I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.
jchadana said:
I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.
Click to expand...
Click to collapse
Did you make any mods or change any settings?
Also, did you try using a different kernel? (Devil / Semaphore)
You might also flash back to Serendipity and see if the problem persists. If it doesn't then of course it's an issue with CM but if it continues I would say its a hardware problem or potentially a bad charger. Personally I've never used either CM9 or 10 but nearly every rom I've used is based off of them and I've never had this issue. So unless you've done something weird with the settings as BWolf suggested then I would lean towards hardware.
Thank you for the suggestions. I've flashed a couple of kernels (Devil and Semaphore) and the problem continues. I'll test the battery and charger next.
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.
jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
yqren said:
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.
Click to expand...
Click to collapse
Try upping your minimum voltage to 200Mhz.
BWolf56 said:
Try upping your minimum voltage to 200Mhz.
Click to expand...
Click to collapse
tried it, but it doesn't work.
thanks
Same problem here. CM9 had been doing it fairly regularly. I wiped everything and did a fresh CM10 install before bed without installing any other apps or changing settings and it shut off over night. I'm flashing back to stock now too confirm whether that fixes the issue
Related
hi guys, i'm getting really pissed off right now
i''ve got my phone for 3 months now and it worked like charm till the last month
every time my phone shutdown randomly , and when i restart it, my battery level is under the 10%
even if i charge it the whole night till 100%, after i use it a few minutes it shutsdown and the battery will be very low.
sometimes it doesn't even turn on anymore.
i can't use my phone now only when its charging because it doesn't shutdown then.
I've tried everything that i could think of, i've recalibrated the battery , installed different roms but i got the problem with every rom.
i've even tried it with a ics rom but still got the same problem
someone please help me
my phone had the same problem i have flash any costum rom but nothing and then i have flashed a stock original rom for fix that....and then retry a costum rom.
have you try to wipe /system /sdcard /data /cache /delik-cache and then flash a stock original rom with odin ?
Rajito said:
hi guys, i'm getting really pissed off right now
i''ve got my phone for 3 months now and it worked like charm till the last month
every time my phone shutdown randomly , and when i restart it, my battery level is under the 10%
even if i charge it the whole night till 100%, after i use it a few minutes it shutsdown and the battery will be very low.
sometimes it doesn't even turn on anymore.
i can't use my phone now only when its charging because it doesn't shutdown then.
I've tried everything that i could think of, i've recalibrated the battery , installed different roms but i got the problem with every rom.
i've even tried it with a ics rom but still got the same problem
someone please help me
Click to expand...
Click to collapse
I have the exact same problem, am about to buy a new battery tomorrow unless someone else has another solution? This might not be the proper forum but in here at least many i9001 users will read it.
I've had this problem for about a week, was very annoying while on holiday. I've tried using BroodROM BE 1.0, Stock KQE and now back to stock KPG.
Try ebay - you can easily find decent batteries for 5$ there.
pedrsantiago said:
Try ebay - you can easily find decent batteries for 5$ there.
Click to expand...
Click to collapse
Well yes I'm going to try a different battery soon but the odd thing is after my battery charge seems to drop down to 5% or so, it starts charging to about its original charge level without a charger connected. So it's basically 80%->drop to 5%->charge back to 60% without charger.
i'll try now to do a hard reset, go back to stock rom, then reinstall an costum rom,
will tell you if it works!
Plz mods remove/delete this sheeyat.. this is
Galaxy S Plus I9001 Android Development
i have used TeamWin Recovery for wipe all partition becouse with hard reset don't wipe /system and internal sd.
Rajito said:
hi guys, i'm getting really pissed off right now
i''ve got my phone for 3 months now and it worked like charm till the last month
every time my phone shutdown randomly , and when i restart it, my battery level is under the 10%
even if i charge it the whole night till 100%, after i use it a few minutes it shutsdown and the battery will be very low.
sometimes it doesn't even turn on anymore.
i can't use my phone now only when its charging because it doesn't shutdown then.
I've tried everything that i could think of, i've recalibrated the battery , installed different roms but i got the problem with every rom.
i've even tried it with a ics rom but still got the same problem
someone please help me
Click to expand...
Click to collapse
I thought I was the only one with this problem. I charge my battery to full and it starts draining normally. Then, when around 30-80% battery remaining, it turns off. It only turns off when you use it for a while, when the screen is off it stays on normally. After rebooting it turns off within a minute or so. This continues for a few reboots with the battery level remaining roughly the same. Eventually after a few boots it shows 3-4% of battery, after which I of course have to charge. Also tried calibrating and tried different roms but it still remains. I ALSO SWAPPED MY BATTERY WITH A FRIEND BUT IT DIDN'T HELP! It worked like a charm for him but I still got turn offs with his battery.
If i were you Guys, i would install stock rom and hand in my phone under warranty ( of course if you still have it ). Because if this occurs even when u swap battery, let samsung play with you phone then
Its not your battery..restore your phone to the way it was and give it to samsung
i'm getting pissed of now, even with the stock rom it randomly shutsdown.
i don't have any warrenty so i can't give it back to samsung
In case anyone's still wondering, in my case it did turn out to be a fried battery. If anyone else is experiencing the same issues I was, just check your battery to see whether or not it is swollen. If it's bigger than it should be, that probably means it's fried and you should replace it. I'm happily running custom roms without any trouble again now, and battery life is awesome!
Sent from my GT-I9001 using xda app-developers app
Rajito said:
i'm getting pissed of now, even with the stock rom it randomly shutsdown.
i don't have any warrenty so i can't give it back to samsung
Click to expand...
Click to collapse
Sorry Rajito, but you are having a serious problem, i think the motherboard is the problem, my friend had the same problem with his I9000 S simple. You shoud go to a service !
Hi guys,
I also have this problem, my phone randomly turns off and when I turn it on, it shows much less remaining battery percentage than before. (please see attached image) After turning on the value is increasing, sometimes from ~5% to 30-40% or more...
Now I have CM10 Jelly Bean flashed, but CM9 did the same sometimes but much more rarely than on JB. Today the phone 'died' three times until noon.
aToS88 said:
Hi guys,
I also have this problem, my phone randomly turns off and when I turn it on, it shows much less remaining battery percentage than before. (please see attached image) After turning on the value is increasing, sometimes from ~5% to 30-40% or more...
Now I have CM10 Jelly Bean flashed, but CM9 did the same sometimes but much more rarely than on JB. Today the phone 'died' three times until noon.
Click to expand...
Click to collapse
Yeah that's the exact same problem I had. In my case it turned out to be a fried battery, see if it's swollen or not, if you lay your battery on a table it should stay still and not wobble around. If the battery's not flat but swollen that means your battery is fried. In this case good news because you can easily replace it
avreijnen said:
Yeah that's the exact same problem I had. In my case it turned out to be a fried battery, see if it's swollen or not, if you lay your battery on a table it should stay still and not wobble around. If the battery's not flat but swollen that means your battery is fried. In this case good news because you can easily replace it
Click to expand...
Click to collapse
unfortunately it is absolutely not swollen, its fully flat :\
besides this I put out the battery now and put it back and it is showing only 2% percent of battery so maybe my battery is wrong
UPDATE: after uninstalling the pro version of Battery Indicator there were no random shutdowns at all, but the free version is fine o.0
So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??
Griff43081 said:
So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??
Click to expand...
Click to collapse
SoD.
There are quite a few things that can trigger it (like deep idle) but first I'd need to know what changes/mods you made.
So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).
Griff43081 said:
So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).
Click to expand...
Click to collapse
Did you go back to stock and factory reset first? Also, did you restore any system app or data with TiBu?
Are you running with stock kernel? If so, you could try flashing Semaphore.
I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.
Griff43081 said:
I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.
Click to expand...
Click to collapse
Kernels for GB are quite different than for JB 4.2. When you flashed CM10.1, it most likely also flashed their stock kernel. This is what I meant by stock kernel.
any possibility that you've got a battery that is failing? or if the third pin is dirty, the power management chip could do that, even if the battery isn't fully charged. when the battery was at 7 percent after 'charging', what was the battery level before charging.
have you cleaned the batt terminals on both battery and phone?
hope this is helpful.
Sent from my SGH-I897
To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?
Griff43081 said:
To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?
Click to expand...
Click to collapse
Indeed, new battery time!
When using the phone the battery indicator immediately drops from whatever it was at down to %0 and the phone shuts off.
When I start the phone up into recovery (Philz) it still shows the original battery percentage that was reported before the phone shut off. I rebooted the phone back up into system several times and sometimes I am able to use it for a minute or two and then it will repeat all over again: the battery drops back to %0 and the phone reboots, other times it says %0 immediately after bootup and shuts off right away.
It's intermittent, so sometimes I can go for a week or two if I'm lucky without it happening, but sometimes I can only go a few hours without being interrupted by the shutdowns. The only thing that seems to have helped me is charging my phone a little bit more and then it stops for a while, but I don't always have a charger with me so I would like to get this issue resolved if possible.
I know my battery is charged. I was able to sit there flashing my phone over and over trying to fix the issue and the phone kept working 45 minutes and even an hour later. Sometimes reflashing my ROM after wiping system, cache, etc. seems to fix the issue, other times it doesn't work.
I have done the EB40 mod to my phone, but I haven't had any issues with it. It's possible that this problem could be related to that as well, but I'm fairly confident that my battery is in good condition.
This issue has been occurring for quite a while and I have done full wipes and reflashed several times with multiple different ROMs and kernels to see if the issue was related to a certain ROM or kernel. All of the ROMs I have tried were very heavily based on CyanogenMod I believe, so if it turns out to be software rather than hardware then that seems to be the common link.
I need my phone for my job so this is something I really need to get sorted out. I have to use my phone for debugging and testing applications.
I have searched all over the web but no one I have found in any forum was having quite the same issue as me.
Does anyone know how to solve this issue? A suitable workaround if no other solution could be found would be somehow preventing the phone from rebooting when the battery reads %0 if that's at all possible.
Here's a screenshot of my battery history from today when this happened. Notice how the battery level goes right back to where it was after rebooting.
https://docs.google.com/file/d/0B6RpWzK5OKf4SFp1TWd1aUJ4ZlU/edit?usp=drive_web
Some additional info:
My battery is still at %52 as I type this and it's still running without a problem. Battery life is great in the CyanogenMod nightlies when I'm not having this issue.
I am running the October 12th nightly. The issue started while I was using arrrghhh's kernel, and it persisted even after wiping /system, and /cache and then using just the normal kernel that comes with the October 12th nightly.
Try a different rom?
Sent from my PACMAN MATRIX HD MAXX
I have tried flashing quite a few different ROMs and this has happened on all of them. CyanogenMod, PAC, JellyBam, and ProBAM come to mind.
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
penser said:
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
Click to expand...
Click to collapse
No. Would that really be necessary?
I wiped /system, /data, /boot, /cache, dalvik-cache, basically everything.
This sometimes does resolve the issue temporarily, but it comes back after a while.
UPDATE: I read somewhere that this may be an issue with the battery not being properly calibrated after installation. I don't think I've ever drained the battery all the way down since I got the EB40, so I figured I'd try it.
I tried completely draining it and charging it up to %100 with the phone off and I haven't had any issues so far. Sometimes it went for a week without having issues before though, so I'll be keeping an eye on it in case there are any more issues.
Hi,
A few days ago I upgraded my Note from a very ancient (stock) Gingerbread ROM to (stock) Jellybean. I hadn't been getting OTA updates because the Gingerbread was originally German rather than UK, so quite a long time had passed without any updates. Anyway, because of the no OTA, I used Odin. Everything went fine and I had a nice few days of usage, although the battery consumption seemed to suddenly be quite high, mainly due to additional wakelocks from the new Google Search it looked like. The night before last at about 3% the phone turned itself off, which is unusual as normally the battery will run itself lower than that. BTW, it's an official battery bought just a few months ago to replace the one before, which was getting old.
Yesterday evening when I went to use the phone it was dead. Completely unresponsive. It wouldn't charge either. (The battery had been at about fourteen percent I think, so it should have still had a lot of juice left.) Turning it on would leave it stuck on the Samsung logo only. Recovery mode didn't work, but I could get download mode up, so I installed the Philz kernel as people have said, and then did a reset using that, and all was okay again and after reflashing the ROM I could use the phone again, although because of the reset I had to set everything up again.
Just wondering what people think caused it. Just a weird coincidence, or something else? As far as I'm concerned, the problem has been sort of mitigated for now, but definitely not fixed, because what's to stop it happening again? Has anyone heard of strange things going on with Jellybean? I know there's an issue with flashing/resetting from ICS, but I never used that so I don't think that's an issue, and it looks like it was just a soft brick only. Still, a bit weird and worrying. Does anyone have any ideas?
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
XxPixX said:
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
Click to expand...
Click to collapse
I didn't take the battery out though. It was low but not dead.
Since then it has happened once again, a few days ago, this time at 93% full. I was doing nothing at all taxing to the phone. I was just in a shop listening to an mp3 with the screen off, and then it stopped and the next thing I saw was the bootloop. Luckily (thanks to the new kernel?) I could just delete cache/dalvik and be back up and running again without having to reinstall everything. Today my screen temporarily went a weird purple colour like in this thread: http://forum.xda-developers.com/showthread.php?t=2216867 . Sounds like it's just dying in general really, rather than anything else. My phone contract upgrade date is in two days. Purely a coincidence of course. Weird how phones tend to last about the length of a mobile phone contract. Until then I'm just running on power saving mode and hoping for the best.
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
this should not be in the general sections, but in the Q/A help section...
have you tried reflashing the stock img?
I had some major issues like that after updating to 5.0.1. I'm on cm now but if you flash back to stock it should fix things too
Sent from my Nexus 6 using Tapatalk
Harmanpreet Singh said:
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
Click to expand...
Click to collapse
Stock Nexus 6, or are you using custom stuff?
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Harmanpreet Singh said:
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Click to expand...
Click to collapse
Happened to me too today.got n6 on 11th Dec.initially reboots started then after 2 weeks of observations I turned off ambient display and now random shut downs..
Phone turned off on 14 % battery just when I picked up an incoming call..then again turned off when there was a call..really fed up of this issue..
Don't know if its a hardware or software issue..
backup your phone, reflash stock img completely, and test without restoring apps.
[email protected] said:
Happened to me too today.got n6 on 11th Dec.initially reboots started then after 2 weeks of observations I turned off ambient display and now random shut downs..
Phone turned off on 14 % battery just when I picked up an incoming call..then again turned off when there was a call..really fed up of this issue..
Don't know if its a hardware or software issue..
Click to expand...
Click to collapse
I've never had a random reboot but I have had the random shutdown issue. This was running stock 5.0.1 with stock kernel. Also had the same occurrence on CleanRom with stock kernel (this is basically a stock rom/kernel with a few tweaks. Another user recommended flashing LeanKernel which I did and haven't had a problem since. This random shutdown was happening roughly once per day. I have been running strong for almost a week now I'd say. I always am the guy to run custom roms and kernels myself anyways but I actually don't mind the stock rom so flashing the kernel was no big deal to me. There are a few threads on this subject if you search the forums. I too am hoping this isn't hardware related since it's always a pita dealing with RMA.
Is there anything new onto that? Any possible solutions? Same issue for me, generally happens during calls ... :/
hmm strange, i never had any shutdowns, could be either your rom or kernel your on. make sure the kernel your using with ur rom is compatible
Harmanpreet Singh said:
stock out of the box nexus... happens usually while playing high end games. Happened twice during calls :/ 3rd week into the phone . Usually the battery saver turns on moments before phone shuts down . some times just goes poof.
Click to expand...
Click to collapse
I was just looking for this.
Mine started doing the same.
I have the battery saver set to 5%, but it never turns on!
The phone shuts off between 10% and 5%.
The battery saver turns on for only for a few seconds(if at all) and the phone shows the powering off animation.
Connecting the charger and turning the phone on, after booting shows 8% already.
Its not normal, because i remember having my phone at 1% without any problems for tests when i got it in November...
For the last few weeks i never went lower than 25% so i don't know when this started, but since i found this out(5 days ago), i tried it every day and it happens like clockwork. Flashed the factory image back has no effect( i was on stock anyways).
Hoping not to have a replacement to save the cost of my dbrand and screen protector...
I give it one more week and if it doesn't change i call Moto. I have MotoCare so replacement should be easy.
Harmanpreet Singh said:
I am facing serious shutdown issues . My nexus 6(MB,64GB) keeps shutting down unexpectedly . This happens while playing a game or even while calls. Any suggestions ??
Click to expand...
Click to collapse
Same here ....
Hi guys,
My 2 month old nexus 6 is powering down unexpectedly. Random shut downs (not reboots). Thought it was snap chat was the culprit (read a few articles how some 3rd party camera apps can cause lollipop to power down) but the phone shuts down even after uninstalling all suspicious apps.
Any advice or suggestions will be highly appreciated
Devs please help
I'm starting to really wonder if these "turbo chargers" are causing major degradation to the batteries. The phone will shut down when the battery *voltage* drops below a specific threshold, regardless of what the percent display is actually at.
Another thing to consider is that adding a significant load to a battery will cause it to read a lower voltage, even if that load does NOT immediately deplete the battery, those who notice this happening when running a very demanding game could be experiencing this. I would suspect though, that this will only be an issue if the battery level is already fairly low.
Any update on this?
5% is still my dead-spot and nothing i tried helps...
I just ordered my nexus but my s5 (current phone) randomly reboots. We figured it was due to volte. Turned that off on the s5 and no issues so far. Was really tired of it and the reason I'm going to nexus. That and the bigger screen
Sent from my SM-G900T using Tapatalk
Same issue here...
It must be caused by a bad batch of battery defects, Factory reset or re-flash factory image won't fix it... To get a replacement from Google seems to be the right way...
Davzone said:
I was just looking for this.
Mine started doing the same.
I have the battery saver set to 5%, but it never turns on!
The phone shuts off between 10% and 5%.
The battery saver turns on for only for a few seconds(if at all) and the phone shows the powering off animation.
Connecting the charger and turning the phone on, after booting shows 8% already.
Its not normal, because i remember having my phone at 1% without any problems for tests when i got it in November...
For the last few weeks i never went lower than 25% so i don't know when this started, but since i found this out(5 days ago), i tried it every day and it happens like clockwork. Flashed the factory image back has no effect( i was on stock anyways).
Hoping not to have a replacement to save the cost of my dbrand and screen protector...
I give it one more week and if it doesn't change i call Moto. I have MotoCare so replacement should be easy.
Click to expand...
Click to collapse
I use to have this issue. However, it has not happened since I started using Franco kernel. Multiple people have had the problem resolved by changing kernels. That leads me to believe that it is software related rather than hardware. Other benefits of flashing Franco for me is I can now use the built in led for notifications and I am using double tap to wake.
joshpdavis80 said:
I use to have this issue. However, it has not happened since I started using Franco kernel. Multiple people have had the problem resolved by changing kernels. That leads me to believe that it is software related rather than hardware. Other benefits of flashing Franco for me is I can now use the built in led for notifications and I am using double tap to wake.
Click to expand...
Click to collapse
My battery issue happened after I kept using Franco for a while...then I switched back to elementalX or stock kernel, nothing resolved...
if the back cover doesn't peel off or the battery doesn't start to expand, it might be a good sign that it is just a software issue.
Otherwise, battery defect could be happening already, as in my case...
Changing kernels fixed my issue which was the phone shutting down on its own randomly. I guess some of you are experiencing a different problem.
Davzone said:
Any update on this?
5% is still my dead-spot and nothing i tried helps...
Click to expand...
Click to collapse
Just a little update.
I did an advanced replacement with motorola.
Did it over chat on sunday, received the new phone on wednesday from texas.
Deposit was 500+tax.
The phone was brand new unopened box. Cloud White 64GB
The package had a box and a prepaid label to send the bad phone back.
The box was too small to fit a nexus 6, so i had to modify it a bit.
It was probably for the moto X or smaller.
Sent the phone back on Friday, they got it on Monday, and my money was back.
Everything looks great, the new phone can go down to 1% no problem.
The new turbo charger does not have the electrical noise that the old one has.
That may caused the battery problem. Using it since last Wednesday, and no problems so far.
The advanced replacement was great and easy, if i have to i would do it again, although in 3 months its gonna be a refurb device not a now.
Mine was in mint condition, had dbrand on and no scratches. The person who will get it after me will be happy with that refurb device
And i am happy with my new phone.
If the HTC M9 will have a GPE edition i might switch